Sideloaded June OTA successfully. Now trying to flash custom boot img in bootloader and it says "Waiting on device" in CMD after running flash command and doesnt do anything on the Bootloader screen on phone. I have tried rebooting several times and I have the latest ADB and Fastboot.
Anyone else have this issue or know what to do? Thanks
chasehammer said:
Sideloaded June OTA successfully. Now trying to flash custom boot img in bootloader and it says "Waiting on device" in CMD after running flash command and doesnt do anything on the Bootloader screen on phone. I have tried rebooting several times and I have the latest ADB and Fastboot.
Anyone else have this issue or know what to do? Thanks
Click to expand...
Click to collapse
Just the usual.....try different cord and different port.
Tried that, it actually will not allow me to flash or sideload now since the OTA installed.
Flashing does nothing, when I tried to sideload the entire image zip it fails at 0% and says error: no message.
Does your SDK need to be updated now?
Hope it's not it's related. I just got my new phone(4a5g) last week, and already did ota to June. Have not unlocked it yet.
Related
Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.
Okay, I have the Nexus 6 (T-Mobile), rooted stock. I also have the Nexus 10. On both, I tried to sideload the 5.0.1 OTA update... and it failed in the exact same manner.
Obviously, I'm doing something wrong, but I have no idea what.
I did the Nexus 10 on a Windows 7 box, and I'm trying the Nexus 6 on a Linux machine. Same. Exact. Problem.
What I'm doing is this:
adb reboot bootloader
Arrow up to recovery, hit the power button to select
Hold down the power button and press the up button
Select "Sideload from ADB" (can't remember the exact wording, but basically, that)
adb sideload <verylongfilename.zip>
The update starts... and gets to 48% on my computer, and then ends. (I don't mean that it pauses or hangs, I mean it "finishes" -- it's done and back at the prompt). On the phone, at that time, it says "system has been remounted r/w; reflash device to reenable ota updates"
So that's where I'm at. On my Nexus 10, I ended up wiping it and just doing the full stock image install to get 5.0.1 -- that worked fine. On my phone, though, I really don't want to lose my entire setup just to get the bump from 5.0 to 5.0.1.
Can anyone tell me what the heck I'm doing wrong? It has to be something I'm doing or something I have configured wrong or ... I don't know. But the process clearly works for many, many people, and the fact that I have the same problem with two different devices on two different computers... it has to be my process, or something I've done to my devices.
Both devices are rooted stock, with stock recovery.
Any help you guys can provide would be greatly appreciated!!
you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.
simms22 said:
you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.
Click to expand...
Click to collapse
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?
commonplace said:
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?
Click to expand...
Click to collapse
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.
simms22 said:
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.
Click to expand...
Click to collapse
I was following directions found elsewhere (AndroidCentral and another site). I see now that adb sideload is not the answer, and that fastboot flash IS.
Phone = upgraded. Thanks for steering me in the right direction!
I had rooted 5.0 and read on Google+ that update over the air would not work. I used this guide to update to 5.0.1 and lost no data, nor had to reinstall anything.
http://forum.xda-developers.com/nexus-6/help/help-5-01-wipe-t2970924
I have not received the OTA update to Marshmallow yet and getting impatient so I'm attempting to sideload the update myself. I've installed the SDK and drivers. The device is listed when I use 'adb devices' at the command prompt and it allows me to boot into the bootloader. But from there it disconnects from my computer and I'm not able to push the update to the device. I get "error: device '(null)' not found". Any advice?
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Didgeridoohan said:
In the bootloader you use fastboot, not adb...
I rarely use adb, but I do believe you need to be booted into Android or the recovery (a custom one).
Edit: some reading for you: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Click to expand...
Click to collapse
Ok, but all the instructions I'm finding online to sideload the OTA say to type "adb sideload [the full name of the file].zip". This is after enter Recovery Mode and select "apply update from adb"
I typed "fastboot devices" and my device came up in the bootloader. I click into Recovery Mode and the computer makes the disconnect sound. That's where I'm cut off.
Have you tried unplugging and plugging in the usb again after entering recovery?
Didgeridoohan said:
Have you tried unplugging and plugging in the usb again after entering recovery?
Click to expand...
Click to collapse
I ended up trying NRT and caused even more problems at first, so I ended up just flashing the update instead of sideloading it. I was freaked out for a while because it was stuck in the boot sequence but as of right now, it's working and I have 6.0.
Yay!
ok, sideloading is for twrp recovery. but thats not needed anymore as you can just move files in and out of twrp without adb. flashing factory images is only via fastboot while you are in bootloader. adb and fastboot are different.
Hi all,
Any help I can get would be greatly appreciated. I have a Sprint HTC One M7 that was previously rooted. Currently it is relocked with S-On, but at some point an OTA update was downloaded and now my phone keeps restarting itself and boots to this "android is upgrading..." screen. It keeps doing this loop over and over. It restarts itself, and then goes to this "android is upgrading..." I've spent hours in the forum this afternoon and I've tried numerous things and nothing seems to be working. Everything I've tried keeps giving me errors. At this point I would simply like to go back to the stock ROM and have a working phone. Can anyone help?
FYI...
I've tried using the .exe method from an RUU, but that isn't working because when it reboots to bootloader at the very beginning of the process my phone boots to android and I get the "android is upgrading..." message.
I've tried extracting the rom.zip and sideloading it, but I can't sideload because installing the TWRP.img recovery fails every time.
I've tried a factory reset and that fails. Again, I get the "android is upgrading..." loop.
Basically, everything I've done to run RUU fails because my phone reboots to android instead of rebooting to the bootloader, and everything I've tried to work around that problem fails.
I'm currently running 6.23.651.7 and I'm trying to flash 6.23.651.10.
Again, any help would be massively appreciated. I'm desperate...
johnnycr said:
I've tried extracting the rom.zip and sideloading it, but I can't sideload because installing the TWRP.img recovery fails every time.
Click to expand...
Click to collapse
You can't flash a rom.zip extracted frin a ruu.exe using TWRP, it must be flashed using fastboot with the phone booted in RUU mode.
Basically, everything I've done to run RUU fails because my phone reboots to android instead of rebooting to the bootloader
Click to expand...
Click to collapse
Holding power and volume down doesn't work? This should get you in bootloader mode. If your phone can't boot to a stable bootloader there is nothing you can do. Once in bootloader there are many options to unbrick your phone.
alray said:
You can't flash a rom.zip extracted frin a ruu.exe using TWRP, it must be flashed using fastboot with the phone booted in RUU mode.
Holding power and volume down doesn't work? This should get you in bootloader mode. If your phone can't boot to a stable bootloader there is nothing you can do. Once in bootloader there are many options to unbrick your phone.
Click to expand...
Click to collapse
I first tried flashing the rom.zip using fastboot, but when the phone is supposed to display the HTC logo screen my phone just reboots and goes back to the "android is upgrading..." page.
I can get into bootloader when I hold power and volume down, but I haven't been able to successfully do anything from there. I tried flashing TWRP so that I could attempt to sideload a ROM, but I got an error when flashing TWRP.img.
johnnycr said:
I first tried flashing the rom.zip using fastboot, but when the phone is supposed to display the HTC logo screen my phone just reboots and goes back to the "android is upgrading..." page.
I can get into bootloader when I hold power and volume down, but I haven't been able to successfully do anything from there. I tried flashing TWRP so that I could attempt to sideload a ROM, but I got an error when flashing TWRP.img.
Click to expand...
Click to collapse
What is the error when flashing twrp?
fastboot oem rebootRUU doesnt work?
Is your bootloader still relocked? If it is, you can't flash custom recovery. The only thing you can do is run RUU in that state
alray said:
What is the error when flashing twrp?
fastboot oem rebootRUU doesnt work?
Click to expand...
Click to collapse
Well, I was just going to try and do this again, but now my PC can't even find it when I run "fastboot devices." I have the SDK and ADB driver installed, so I don't know why it can't find it all of a sudden.
I can't install the RUU by running the .exe, because when I do and it gets to the "waiting for bootloader..." screen my phone reboots and loads android and goes to the "android is upgrading" screen. So I need to flash the RUU via fastboot, but now my PC isn't recognizing my device in CMD...
Okay... so I finally got adb and fastboot working again. When I run "fastboot oem rebootRUU" the phone reboots to Android and goes to the "android is upgrading..." screen.
Update: So... I was able to successfully use adb and fastboot to unlock my HTC One again. I then tried to flash a custom recovery via fastboot, but I kept getting "FAILED (remote: signature verify fail)". I tried flashing TWRP, CWM, and stock HTC recovery and got the same failed message for each one. I'm just trying to find a way to break this stupid boot loop... HELP!
Update: So, my phone even restarts itself when I boot into safe mode... not good. Can anyone help me out?
Hi Community,
I was rooted and got some nasty popup virus, then I factory reseted through settings. Everything was fine, then I entered in my software "superuser" and he said he would reinstall something, then booom bootloop!
I tried factory resetting through fastboot didnt work;
I tried flashing stockrom, latest rom, downgrade rom and the error is the same:
Verifying update package...
E: footer is wrong
Update package verification took 0.2 s (result 1).
E: Signature verification failed
E: error: 21
Installation aborted
ADB doesnt recognize my device!!! guess because after rebooting I never re authorized usb debugging mode or oem..
What Can I do now? any help appreciated
Hey, just try this Guide: https://forum.xda-developers.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750
Everything is described there.
If your Device is on Android One, don't take the Rom from the thread but from this link: https://androidfilehost.com/?fid=673956719939834159
If you have further issues feel free to ask again
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
irongas said:
AdB dont recognize my device fastboot sees im plugged in but adb wont see the device
Click to expand...
Click to collapse
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
screwyou00 said:
I believe you don't need adb to recognize your device if your flashing OEM firmware from the bootloader (and you have the bootloader unlocked). As long as you can boot into the bootloader you should be able to flash the stock firmware. I got my Moto x4 into a bootloop and was able to revert it back to the stock firmware even though my phone didn't have usb debugging enabled and my PC wasn't authorized for my phone. Follow these commands
Click to expand...
Click to collapse
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
irongas said:
thanks for the response, but i cant load any commands, because I cant connect my pc to the phone. Ive got an option called "apply update from sd card" and "Apply update from ADB" when i try the first it gives error 21, when i try the second it comes to a blank screen asking me to "Now send the package you want to apply to the device with "adb sideload <filename>" and I cant, because there is no connection..
Click to expand...
Click to collapse
Did you install Motorola fastboot drivers?
The menu what you talk about is Recovery. Look if there's an option to boot to bootloader. If not go down to reboot the device and keep VOL-Down pressed so it reboots to bootloader. There you can just use fastboot commands.
sleeptab said:
Did you install Motorola fastboot drivers?
I did, I used to workaround with adb and sending commands, but the command prompt would recognize my device, now, even in bootloader when I plug it in bootloader says: usb plugged in, but the pc wont see my device... im almost crying here lol
Click to expand...
Click to collapse
RESOLVED!
hEY i JUST looked in device manager and there was a driver issue, then I reinstalled the driver from the pc adb phone, and it came back to liiiife!!! I just followed the second sequence and boom its working
Thank you a looot guys!!! sorry being such a noob! =)
Have a nice one!!