Nexus 7 - Will not autodetect in UBPort Installer
-
Hi there,
I was super excited to find out that I could put Ubuntu onto my Nexus 7, but im having a few issues i hoping you fine folks can perhaps help with?
Currently I have:
-
Enabled Developer Options
-
Installed the UBports Installer (0.2.2-beta) on Windows 10
-
installed ADB Tools
When running the UBPort tool, I select Nexus 7 2013 WiFi and then when it says reboot to bootloader which I do... nothing happens. Thats it. Nadda. Nexus sits on bootloader screen, and the UBPort tool does nothing but also sit on the please reboot bootloader.
Bootloader details are:
-
Fastbootmode
-
Product Name - flo
-
Variant - flo 16G
-
HW Version - rev_e
-
Bootloader Version - FLO-04.08
-
Signing - Yes
-
Secure Boot - enabled
-
Lock State - unlocked
Hopefully you fine folk will be able to point me in the right direction!
Cheerio.
-
-
@daedalus do you have
fastboottools installed as well?Edit: I don't have any experience with the windows version of the installer but the usual advice in the Install group is to use https://forum.xda-developers.com/showthread.php?t=2588979 before using the installer.
-
Hi @advocatux thanks for the quick reply!
I installed the ones that were noted here as the dev said it was a more updated version. That said it didn't have the 15 second install. So installed the one you mentioned, and sadly a no go still. FASTBOOT MODE is in red on the Bootloader screen if thats of any help?
-
@daedalus IIRC you have to uninstall the old drivers before to avoid any kind of conflict. Rebooting your computer after the "15 seconds install" is usually recommended too.
-
@advocatux thanks again. Looks like its not actually detecting the Nexus is plugged in. Got USB debugging enabled, and MTP turned on. Don't think im missing anything...?
-
@daedalus One more thing to check have you granted permission for the adb connection. You should get a pop-up asking for permission for the connection. Can't remember now if it's on the device or pc/laptop think it's the laptop.
To test open a command prompt and type adb devices that should start the daemon and detect your device. If not check everything again and try a new usb cable as well. -
@Lakotaubp on the device
-
@daedalus check what @Lakotaubp said and also the device screen has to be unlocked
-
@advocatux Thank you aged brain failure
-
@advocatux @Lakotaubp thanks for that. Have tried as you've stated and running it in CMD or PowerShell (.\adb devices) it detects and displays the device ID. The tool itself doesn't seem to detect it though.
Might spin up a VM with Ubuntu on it, and see if have better luck with that perhaps.
-
@daedalus don't forget to try with a different USB cable. You wouldn't believe how many installations has failed due to that reason.
Edit to add: if the only issue is that the installer doesn't recognize your device, you can select it manually
-
@advocatux Yeah, i've selected it manually, but no joy. I think that its defintely not detecting it, so somehow causing the process to fail.
Will grab some additional cables at work today, and try different ones. The one I use if good quality, so you just know thats going to be the issue!
-
@daedalus Installing Lineage first has help a few people out if you wanted to try that way, but try the vm first.
-
Sorry for the delay.
Seemed to be an issue with Windows. I Spun up Ubuntu in a VM, and it worked like a charm.
Cheers for all the help, very much appreciated!
-
@daedalus Glad you got it sorted. Enjoy
