I am trying to update my Bootloader. I am on version 3.51. When I go into fastboot, fastboot devices lists my device. When I attempt to flash anything, it hangs at <waiting for device>.
Not sure exactly what to do. SDK is updated, along with tools.
I am on Ubuntu 16.04.
EDIT: Issue resolved after installing eclipse, and redownloading latest SDK
Thread closed per OP request.
Related
I got an N7 about a month ago on sale and the first thing I did was unlock the bootloader. I decided I was going to use it as a "learning" tablet. (I'm still in learning mode, with aspirations of dipping my toes into development - that's a ways away, though.) I flashed TWRP followed by a couple of roms, and then I decided I was going to test my ability to flash a factory image. So I flashed 4.4 (this was last week before the 4.4.2 images went up). And since I was on the back on the OTA path, I figured, "I have an unlocked bootloader. What's the worst thing that could happen if I took this update?" So I did.
And now I'm confused. If I remember correctly, with 4.2.2 (what it came with out of the box), the bootloader had an option to run in "fastboot mode." In 4.4.2, my options are basically Dead Android screen or (if I power+vol up):
Reboot system now
Apply update from ADB
Wipe data/factory reset
Wipe cache partition
Fastboot stopped recognizing my tablet (adb still works, though not in recovery - I didn't think it was supposed to, so I'm surprised to see it as an option). I know there were issues in the past with the USB drivers on x64 machines, but I've tried on both 32-bit XP and 64-bit Win 7 and both machines will recognize that there is an N7 when booted normally, but say there are issues with the drivers when booted into recovery. I searched and saw people using pdanet as a workaround for installing the USB drivers, but those posts were largely from 2011/2012 timeframe - I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat? Even so, ADB doesn't recognize my tablet in recovery, so even if I wanted to sideload something I can't - did Asus release newer USB drivers that I should be using?
Any help anyone can provide would be greatly appreciated.
Thanks!
miss_sticks
miss_sticks said:
I have the latest version of Android-SDK and thus the latest (I think) USB drivers, so I'm at a loss. Did Google/Android do away with Fastboot in KitKat?
Click to expand...
Click to collapse
Are you sure to have updated all the drivers for your N7 after update of your SDK?
Weird thing about N7 is that one sometimes needs to re-installi all the drivers after flashing of another firmware. I've flashed a factory image (4.3) via fastboot on two N7s within the same hour. First N7 had 4.2.2 before, After flashing 4.3 on it, I took another N7 with 4.2.0 and- I had to re-install the drivers.
I never had such a situation with Samsung devices.
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.
tetakpatak said:
Just to make sure you're doing proper ADB prompts (I see you can get this far on your own):
Code:
adb
adb devices
[I]List of devices attached
[B]<your device's serial number should now be diplayed here> [/B][/I] device
adb reboot-bootloader
fastboot devices
[I]the following output should be returned at this point
[B]<your device's serial number should now be diplayed here>[/B] [/I] fastboot
If on the place in this code where bold letters are your device serial No doesn't appear, you have a driver problem (it isn't installed properly)
Sorry for posting ADB/fastboot prompts, I don't know which orders have you done.
Click to expand...
Click to collapse
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)
miss_sticks said:
D'oh! Thank you so much for your help! I kept doing "adb reboot recovery" not "adb reboot-bootloader." Once I did that, everything was fine. I'm going to the corner to hang my head in newbie shame now. (But at least I'm now successfully running TWRP again.)
Click to expand...
Click to collapse
OK, cool. Don't be ashamed, one just has to learn it
From that point on, (as you are in fastboot mode) your each prompt must begin with
Code:
fastboot (.....)
instead of "adb"
just got the device today
followed the tutorial on unlocking the bootloader using the comebuy upgrade tool and checked the box for erasing "CEFS" and upgraded the firmware.
shell is now rooted.
however, rebooting to bootloader and trying any fastboot command gets "waiting for device"; fastboot devices shows nothing.
wth???
i'm an experienced dev / user, but i'm not going to be happy if this device i just got for developing purposes is locked down to where i can't do that.
also, trying to install the FFOS_to_android.zip that's widely available also does not pass signature verification in the recovery...
anyone got any ideas how i can unlock this thing???
stayboogy said:
just got the device today
followed the tutorial on unlocking the bootloader using the comebuy upgrade tool and checked the box for erasing "CEFS" and upgraded the firmware.
shell is now rooted.
however, rebooting to bootloader and trying any fastboot command gets "waiting for device"; fastboot devices shows nothing.
wth???
i'm an experienced dev / user, but i'm not going to be happy if this device i just got for developing purposes is locked down to where i can't do that.
also, trying to install the FFOS_to_android.zip that's widely available also does not pass signature verification in the recovery...
anyone got any ideas how i can unlock this thing???
Click to expand...
Click to collapse
If you google "fastboot command gets "waiting for device"; you may find your answer, most likely driver problem, I use Linux so drivers aren't necessary for me.
vampirefo said:
If you google "fastboot command gets "waiting for device"; you may find your answer, most likely driver problem, I use Linux so drivers aren't necessary for me.
Click to expand...
Click to collapse
i got it figured out. i use both linux and windows; mainly linux. in linux fastboot was acting the same way. it's not now. still have to use sudo though...
i had to dd your recovery, then rebooted to bootloader and ran fastboot oem unlock and it was done.
i was initially very frustrated though.
since i got that figured out i've been trying to port my touchnav recovery to the device but i've been getting an error when i try to fastboot boot it.
funny you replied cause i'm curious what you're using to build your recovery. are you just using the last jb repo or something newer?
stayboogy said:
i got it figured out. i use both linux and windows; mainly linux. in linux fastboot was acting the same way. it's not now. still have to use sudo though...
i had to dd your recovery, then rebooted to bootloader and ran fastboot oem unlock and it was done.
i was initially very frustrated though.
since i got that figured out i've been trying to port my touchnav recovery to the device but i've been getting an error when i try to fastboot boot it.
funny you replied cause i'm curious what you're using to build your recovery. are you just using the last jb repo or something newer?
Click to expand...
Click to collapse
In Linux you need to make user rules if you don't want to use sudo to fastboot, my .50 recovery is a straight pull from CyanogenMod's 4.4 tree.
other recovery straight pull from CyanogenMod's 4.3 tree
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results. Different USB cable/port?
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
dextroamphetamine said:
So my dad went out and bought a nakasig/tilapia it's running Android 4.2.1 and bootloader is 4.13. Having just updated my razor/flo via fastboot everything was setup and working. "adb reboot bootloader" reboots the nakasig/tilapia into fastboot mode and "fastboot devices" shows the nakasig/tilapia serial number. Every other fastboot command just hangs there and does nothing. "fastboot oem unlock" does not prompt me to unlock bootloader. "fastboot reboot" doesn't even reboot the tablet. I use Linux so I figured I would try Windows following the thread sticky'd in this forum http://forum.xda-developers.com/showthread.php?t=2175086 same problem adb works fastboot will list the device but can't do anything with it. "fastboot getvar all" did give me an error however "FAILED (command write failed (Unknown error))" all the other commands just hang there doing nothing saying nothing. Having tried Windows and Linux setups which I have used on my other Nexus devices without issue I am starting to think its an issue with the bootloader maybe I need some older version of fastboot.
Is there a way to flash bootloader from inside Android or Recovery? I can use Towelroot to root the tablet then flash TWRP from Android and boot into TWRP but I don't think you can flash a bootloader from there or unlock the bootloader can you?
Edit: according to http://forum.xda-developers.com/showthread.php?t=2068207 the nakasig/tilapia bootloader is encrypted so you can't flash or unlock it without fastboot.
Click to expand...
Click to collapse
cmstlist said:
OK so you have a 2013 N7 that does not have this problem, but your dad's 2012 does. Two different pieces of hardware.
Click to expand...
Click to collapse
Correct.
cmstlist said:
Could it be a driver issue? Sometimes when the drivers are not talking to it correctly you get these flaky results.
Click to expand...
Click to collapse
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
cmstlist said:
Different USB cable/port?
Click to expand...
Click to collapse
Tried every cable and port I have. Different computers even.
cmstlist said:
Theoretically there is a flash all command you can use to flash an update of the whole thing including the bootloader without it being unlocked. However if you are getting write errors then you should really be cautious because that could just fry it instead of fixing it.
Click to expand...
Click to collapse
NONE of the fastboot commands work except "fastboot devices"
dextroamphetamine said:
Correct.
ADB and fasboot use the same drivers don't they? While in Anroid adb works fine I can adb shell I can adb push/get I can adb reboot.
Click to expand...
Click to collapse
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
cmstlist said:
No, AFAIK they're different drivers, and different devices often require a distinct driver install too.
Click to expand...
Click to collapse
Got any sources on that info?
WOW
weird! really weird!
I really don't know what the issue, the fact that it happens on Linux and on Windows makes me think to an hardware realted issue, unfortunately..
As long as I know adb and fastboot do not use exactly the same drivers, but you download and install them together, so it should n not be a problem, this one..
The only think I can suggest you atm is to try with Linux by logging in as superuser (su). On my slackware with my "normal" user adb works as usual, but if I try to use fastboot the terminal says me No permissions..
I hope someway your distro has the same issue, even if your fastboot devices success!
So login as superuser and try to use fastboot. If you do not install it in /bin partition you should have to locate its directory and then use
./fastboot devices
or any other command but with ./fastboot instead of fastboot..
hope it helps.. I really hope!!
For that matter, on a whim... when you open a command prompt in Windows to adb to your device, try running Command Prompt as an Administrator. Sometimes Windows is weird like that.
Please keep questions in the Q&A section. Development sections are for development only.
Thread moved to Q&A.
Thanks,
Darth
Forum Moderator
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
akhil520c said:
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
Click to expand...
Click to collapse
Fastboot flash recovery twrp.img
Sent from my ZenFone Max Pro M1 using Tapatalk
If you can't install TWRP on pie, try reverting to Oreo with AFT and then flash TWRP in fastboot. Also make sure you have unlocked the bootloader whether by the official tool or the unofficial method. THIS WILL DELETE ALL DATA SO BACK UP.
Thanks arko. Is there Asus Flash Tool available for Linux also? Will try and revert. Thanks :svetius
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
akhil520c said:
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
Click to expand...
Click to collapse
Windows 10 ? Its bcuz Driver Signature Enforcement
Disable it and reinstall adb and fastboot drivers, it will work for sure.
Windows driver security wouldn't accept drivers without proper Signatures,so like i said, just disable it and you are good to go.
:good:
Tried steps you mentioned, doesn't work. In fastboot mode, #fastboot devices gives me no output. Looks like my pie ROM is buggy. Basically, I need to install lineage on the phone.
Hi all,
Finally got everything done in about 5 mins I booted up Ubuntu Mate (32 bit) on my other laptop, and found I'd already installed adb and fastboot on it from the repositories (not from google). I booted my phone in fastboot mode, and tried the #fastboot devices command, and voila, my phone got detected! After that, it was a matter of a few minutes, following the installation instructions (of twrp and lineage) from the lineage website. Thanks for all your inputs and help
P.S: I realised (again), after more than 2 decades, that windoze mighty sucks lol.
Anytime I type the command fastboot reboot fastboot it just takes me to the help list and not fastbootd.
If this is already answered mind linking me to said thread?
Most likely your using an outdated version of fastboot. Check in the Rom threads or root guides here and links to the latest version are there.