Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 (WILL ALSO WORK FOR 4.2, just use the correct file that I link to) on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Thank you =) will try
-Google
I hope people actually watch and learn from this tutorial instead of waiting around for some point and click tool powered by unicorn blood and hamsters. It's an excellent tutorial and gets you in touch with your device by using the exact tools Google provided you to use for this exact thing.. Use them, they are invaluable.
This means we can't use the old method of putting update.zip file in the root folder and let the system upgrades by itself.
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
Click to expand...
Click to collapse
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
I've been plugged in to both a charger and the PC. Come on, if I've fired off adb recovery reboot, doesn't that automatically suggest that I'm connected to the computer? I press Power+Volume Up and it does NOT instantly go to the screen it should, but brings up a Google logo and sits there forever.
styckx said:
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
Click to expand...
Click to collapse
Doesn't work in either case, it just hangs until the hard reboot kicks in.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
Click to expand...
Click to collapse
Omega360 said:
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Click to expand...
Click to collapse
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
ShannonMS81 said:
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
Click to expand...
Click to collapse
THIS WORKED!!!!!!
OMFG!!! I burned the time I was going to watch the making of Prometheus Blu-ray trying to get this stupid thing to work! Where were you hours ago, man?!?!? Thank you!!! Better late than never.
Glad you got it.. BTW.. I did-misread what you said and yes, you would have had a USB cable in. All these posts are running together of people asking for help and having issues. Mah poor brain is getting em all mixed together.
Nexus 7 needs a coffee maker attachment!
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
Great video! I might just be using this in the near future. I plan on waiting for the factory image (I just like having a full install on my devices when possible) instead of using just the zip file (that is if I dont get the update). Although if the update isnt showing up sometime soon then this is going to work for me just fine.
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
can't enterthe stock recovery since i instaled CWM. removing it would bring the stock back ?
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
While in stock recovery and in the "apply update from adb" screen, type in the command window "adb devices". It should say:
<your device serial number> sideload
If it does not, check the drivers in device manager. You may need to manually install it. I had to on mine.
Cheers qbking77, worked a treat.
First time I pushed using adb & after following your tut life is good. Thanks again!
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
You may be using an older version of adb that does not support the sideload command.
Jwoc12 said:
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Click to expand...
Click to collapse
It should say 8sdgfs3JKSDBFkjk3 device or something like that. If it does not, you need to install the the correct driver.
My computer did not recognize my tablet at first. I went to this thread and installed PDAnet which installed the driver.
http://forum.xda-developers.com/showthread.php?t=1809195
Hi there,
First of all thanks for offering help to us. I have a HTC one m7 (rooted)
Actually before the mobile went on BRICKED state, the camera flash light was ON for almost 5 minutes. In normal OFF condition it shows a charge symbol, when it is connected to charge source and the red LED is ON. when i press ( POWER + Vol down), it shows up Bootloader mode but it hangs when i select any of the OPTIONS ( fastboot, factory reset, simlock etc ). when i press power button for long time, in screens comes a normal htc logo, and screens goes off after the HTC logo. In this situation if it is connected to PC, then it detects the device as Qualcomm Download mode ( QDL ).
I tried all possible process , but nothing could survived it. Is there any possible way to revive it ?
Thanks.
Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck
marshhhh said:
Hi there,
First of all thanks for offering help to us. I have a HTC one m7 (rooted)
Actually before the mobile went on BRICKED state, the camera flash light was ON for almost 5 minutes. In normal OFF condition it shows a charge symbol, when it is connected to charge source and the red LED is ON. when i press ( POWER + Vol down), it shows up Bootloader mode but it hangs when i select any of the OPTIONS ( fastboot, factory reset, simlock etc ). when i press power button for long time, in screens comes a normal htc logo, and screens goes off after the HTC logo. In this situation if it is connected to PC, then it detects the device as Qualcomm Download mode ( QDL ).
I tried all possible process , but nothing could survived it. Is there any possible way to revive it ?
Thanks.
Click to expand...
Click to collapse
Doesn't look good at all. There is 2 reasons (afaik) why the HTC One enters qualcomm download mode
1- you have flashed something wrong to your phone (bad firmware, incompatible rom etc....)
2- If you have not flashed anything that resulted to this situation, probably some hardware defect.
option 1 is (possibly) recoverable, see this thread http://forum.xda-developers.com/showthread.php?t=2770684
option 2 your phone must be sent for repair, most likely for a motherboard replacement.
with a defective bootloader, there's not much you can do. Are you still able to use fastboot commands? Is your phone s-on or s-off?
HTC qdl mode
alray said:
Doesn't look good at all. There is 2 reasons (afaik) why the HTC One enters qualcomm download mode
1- you have flashed something wrong to your phone (bad firmware, incompatible rom etc....)
2- If you have not flashed anything that resulted to this situation, probably some hardware defect.
option 1 is (possibly) recoverable, see this thread http://forum.xda-developers.com/showthread.php?t=2770684
option 2 your phone must be sent for repair, most likely for a motherboard replacement.
with a defective bootloader, there's not much you can do. Are you still able to use fastboot commands? Is your phone s-on or s-off?
Click to expand...
Click to collapse
First of all, thanks for your kind Reply
- Its not because of flashing a wrong FIRMWARE...
- I tried HTC unbricking project ( By dexter93 ). I tried on Ubuntu 64 and 32 bit OS but couldnt solved...
- It shows up BOOTLOADER MODE when ( PWR and Vol - ) buttons are pressed but PC cant recoznized the device. PC recoznize the device only in QHUSB Mode. so can't use fastboot commands...
- Its S-OFF
Thanks...
Hi all just a question . HTC m7ul s-on tried to restore device to stock with a help of xda guide ...but now I get to bootloader and can move with volume up-dowm button but power button won't select anything ...power button works to power on device but just sits on a white htc screen for a minute then screen goes off ....when connect to laptop the laptop see the phone as a ZEUS FLASH DEVICE
Is my phone dead or can I revive it
Thanks
leegreggs said:
Hi all just a question . HTC m7ul s-on tried to restore device to stock with a help of xda guide ...but now I get to bootloader and can move with volume up-dowm button but power button won't select anything ...power button works to power on device but just sits on a white htc screen for a minute then screen goes off ....when connect to laptop the laptop see the phone as a ZEUS FLASH DEVICE
Is my phone dead or can I revive it
Thanks
Click to expand...
Click to collapse
Your phone being detected as a "zeus flash device" is for sure a drivers issue. Try to uninstall anything related to whaterver "zeus" is from your computer and then install the latest HTC drivers, boot the phone in bootloader / fastboot usb mode and post the output of "fastboot getvar all".
Hi I can't get into fastboot mode . as when I boot into bootloader with power and volume down , I can move through items with volume button but when I press power button to select fastboot nothing happens its as if the bootloader freezes , I have to hold vol up and power to turn off then get into bootloader again but still power button not working in bootloder but works to get in to bootloader
Hello,
Since few days, i've some problems.
My htc one m7 turn off himself and when i tried to start it, i'm stuck on the htc logo and then the phone turn off...
So i do power-on + volume - and i'm in the HBOOT. But when i select fastboot or others commands, nothing happend : i've still the same screen and i can't do anything (except turn-off the phone with power button).
ADB and Fasboot don't detect my phone (but sometimes i've the windows 7 sound).
It's a stock ROM (from SFR), never root / delock bootloader and it is S-ON.
Sorry for my English (i'm french).
Thanks
My device turns on but the display doesn't (I'm pretty sure the display isn't damaged since the display turned on twice after this problem started)
I need HELP urgently since that is the only phone I've got
Device details:
it runs on Lineage OS 17.1
Rooted (Magisk)
Twrp installed
I've tried entering recovery mode but it doesn't work
Tried recallibrating the battery but that doesn't work either
The phone turns on and I can see it in adb devices when connected to PC
I also tried to reset the device using adb but I guess I've disabled Root access over adb (in developer options)
try rebooting to recovery from adb
kouseralamin said:
try rebooting to recovery from adb
Click to expand...
Click to collapse
*thank you for replying*
tried doing so.. the phone boots into twrp recovery mode but the display doesn't turn on
Usmaan66 said:
tried doing so.. the phone boots into twrp recovery mode but the display doesn't turn on
Click to expand...
Click to collapse
And what happens when you start the bootloader mode (Fastboot) via ADB or press and hold the power button and volume down ?
Usmaan66 said:
*thank you for replying*
tried doing so.. the phone boots into twrp recovery mode but the display doesn't turn on
Click to expand...
Click to collapse
How can you know that the phone boots into twrp recovery mode if the the screen doesn't turn on?
In addition, if you can share a photo of your phone screen while in TWRP or in fastboot or anything that shows on the screen; that would be easier for me to understand the situation.
kouseralamin said:
How can you know that the phone boots into twrp recovery mode if the the screen doesn't turn on?
In addition, if you can share a photo of your phone screen while in TWRP or in fastboot or anything that shows on the screen; that would be easier for me to understand the situation.
Click to expand...
Click to collapse
i got to know that it is in recovery mode by typing adb devcies in cmd and it shows my device id and it shows 'recovery' beside the id
and now the device isn't entering recovery mode by this command 'adb reboot recovery'
kouseralamin said:
How can you know that the phone boots into twrp recovery mode if the the screen doesn't turn on?
In addition, if you can share a photo of your phone screen while in TWRP or in fastboot or anything that shows on the screen; that would be easier for me to understand the situation.
Click to expand...
Click to collapse
I'm sorry i cant click the picture since i dont have any other phone
(I'm replying through my PC and it doesn't have a webcam)
FBK2904 said:
And what happens when you start the bootloader mode (Fastboot) via ADB or press and hold the power button and volume down ?
Click to expand...
Click to collapse
it enters fastboot mode but there isnt any change in the display
Usmaan66 said:
it enters fastboot mode but there isnt any change in the display
Click to expand...
Click to collapse
Bad for you ... I think your HTC-One-M7 display is in Android heaven now:crying::angel:
3 options:
- change display (if that was it).
- Buy a new HTC-One-M7 (the cheeper way).
- Buy a different mobile phone model (if you want).
Greetz,
Frank
Usmaan66 said:
it enters fastboot mode but there isnt any change in the display
Click to expand...
Click to collapse
Seems a hardware issue.
Drop it from the height of approximately 34000 meters like You're on K2.
Then land on the earth again. In case if you find your phone again it will be like a box pack brand new.
Screen
Hi! I have the same problem sometimes: phone boots, but touchscreen doesn`t work. Same: Lineage 17.1 + magisk canary + TWRP. No GAPPs.
For solve it I doing next: immediately after boot when bootanimation finished - unlock the phone.
After this touchscreen keep working.