Related
Making this thread because it's an extremely common problem and there are 4 terribly named threads about it that are difficult to search.
The Nexus 7 stock bootloader 3.34 has a couple bugs:
1. When booting to fastboot with any sort of USB plugged in, your buttons on the side may not respond. In this case, pull the cable and hold down power + Vol Down until it reboots. The buttons should now respond and you can plug USB back in if you wish.
2. The bootloader has problems booting to recovery. It might hang at the Google screen. In this case, get back into the bootloader, connect to a computer and
> fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
then use the buttons to boot into recovery. Don't worry, your nandroids are safe.
Why does this stuff happen? Called the Google Nexus Support line and they're aware of the bug in the bootloader. Until this is fixed, don't flash strange ROMs without a computer nearby to get you out of a soft-brick situation.
BE AWARE that if you flash back to stock from the Google image after getting back into recovery, the next time you boot up, your recovery will be GONE. Try to flash a stock image from XDA instead that doesn't overwrite the recovery and save yourself a headache.
That is all.
Thanks.
All hail jbdubbs
jbdubbs said:
Making this thread because it's an extremely common problem and there are 4 terribly named threads about it that are difficult to search.
The Nexus 7 stock bootloader 3.34 has a couple bugs:
1. When booting to fastboot with any sort of USB plugged in, your buttons on the side may not respond. In this case, pull the cable and hold down power + Vol Down until it reboots. The buttons should now respond and you can plug USB back in if you wish.
2. The bootloader has problems booting to recovery. It might hang at the Google screen. In this case, get back into the bootloader, connect to a computer and
> fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
then use the buttons to boot into recovery. Don't worry, your nandroids are safe.
Why does this stuff happen? Called the Google Nexus Support line and they're aware of the bug in the bootloader. Until this is fixed, don't flash strange ROMs without a computer nearby to get you out of a soft-brick situation.
BE AWARE that if you flash back to stock from the Google image after getting back into recovery, the next time you boot up, your recovery will be GONE. Try to flash a stock image from XDA instead that doesn't overwrite the recovery and save yourself a headache.
That is all.
Thanks.
Click to expand...
Click to collapse
i thank you deeply for getting rid of my worries , THANK YOU THANK YOU . I THOUGHT I LOST MY BABY :8 YOU GOT BACK MA HOPE
I have bootloader 3.34 and a softbrick. I booted without the USB connected, went to recovery and it hangs. So I was going to flash the recovery, but when I plug the USB in, after I have already booted into the bootloader with the buttons working, everything seem to freeze. My command prompt just says "waiting for device."
When I unplug it, it does not response anymore until i restart it without the USB.
joseph_gee said:
I have bootloader 3.34 and a softbrick. I booted without the USB connected, went to recovery and it hangs. So I was going to flash the recovery, but when I plug the USB in, after I have already booted into the bootloader with the buttons working, everything seem to freeze. My command prompt just says "waiting for device."
When I unplug it, it does not response anymore until i restart it without the USB.
Click to expand...
Click to collapse
Same problem here... Plus, I just flashed a new kernel and now can't get the recovery -or- Android to boot. Trying to run recovery just sits on the startup screen with the unlocked padlock and does nothing. For android, it has been sitting on the Android boot-animation screen for over two hours.
So:
1. Can't connect to PC with bootloader.
2. Can't boot recovery.
3. Can't boot Android.
Any suggestions other than buy a new Nexus-7? :crying:
joseph_gee said:
I have bootloader 3.34 and a softbrick. I booted without the USB connected, went to recovery and it hangs. So I was going to flash the recovery, but when I plug the USB in, after I have already booted into the bootloader with the buttons working, everything seem to freeze. My command prompt just says "waiting for device."
When I unplug it, it does not response anymore until i restart it without the USB.
Click to expand...
Click to collapse
I solved my own problem. I just uninstalled and reinstalled the drivers on my computer using mskip's toolkit
Problems with bootloader and fastboot
I'm having a problem with this step...
1. When booting to fastboot with any sort of USB plugged in, your buttons on the side may not respond. In this case, pull the cable and hold down power + Vol Down until it reboots. The buttons should now respond and you can plug USB back in if you wish.
the problem is that whenever the USB cable is plugged in, the buttons don't navigate through the options.
however, whenever the usb is NOT plugged in (and rebooted bootloader) the button work just fine.
I don't have a recovery currently installed.
The issue is not with drivers on the computer, happens while usb plugged in both windows and linux or simply just plugged into a wall outlet to charge.
I need to get into fastboot but i'm having this issue with the bootloader (corrupted?).
any help would be appreciated.
Okay so I seem to have run into a little problem I was planning on updating cleanrom up to 1.2.5 but was on cwm. I had managed to switch over successfully to twrp 2.2.0. I went ahead and used goo manager to download the updated zip of 2.2.1 and tried flashing it thru twrp. Now I am stuck in google bootloop and cant get into recovery or more importantly bootloader. I have been trying last 30mins to hold power and both volume buttons but it either keeps rebooting back to the google screen or not doing anything at all just have to repress to to turn it off but it will turn back on automatically. I tried hooking it up to my usb and labtop but it looks like it wont even recognize it. I just fully charged it so I am good for now just a little worried cant get out of this mess.
I ran into a problem like that with clockwork recovery it kept on rebooting in recovery but I could still go into download mode I was at work away from my computer so I had no choice but to keep trying that three button magic until it finally restored a backup I had on my external card.just keep on trying to pull the battery then try to go into recovery. You might 've gotten a bad download
Sent from my SGH-T999 using xda premium
problem is I cant get into recovery. or the green screen to get to bootloader. It just completely stuck in a bootloop on the google screen mocking me... I am really contemplating opening it up and taking out battery but is that a good idea? Or is there anything else I can do?
so I pulled off the back cover but really dont want o disconnect the battery might mess something up but I cannot get the device to shut off.
disconnecting the battery does nothing it shuts it off and keeps it off but when I connect it to the charger the battery symbol pops up for a second and then goes completely blank. I went ahead and tried again to boot into bootloader pressing power vol up + down and all combinations of power vol -, power vol +
power turbo press vol +/- but no luck still in google screen.
If you're in a bootloop you need to connect your Nexus 7 to a computer. Then you will be able to access recovery via the Power button and volume buttons.
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
clago87 said:
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
Click to expand...
Click to collapse
It's supposed to do that when you're trying to go to recovery from bootloader without the USB cable plugged into a computer, may need to have the drivers installed on said computer. It's an issue with the nexus 7 bootloader and every one of them does it. What your experiencing is perfectly normal if you tried to go to recovery from bootloader with the bolume buttons and then got the google screen bootloop.
If it doesn't work when you plug it in and try, then try unplugging it, manually rebooting with it plugged in first, or vice versa
Update: I can get on Team Viewer and remotely reboot you into recovery through the PC if you want, or at least give it my best shot.
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
clago87 said:
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
Click to expand...
Click to collapse
Have you installed the right drivers on the computer you're using, for ADB and the device drivers, when you unlocked and rooted?
Answer to your question is yes try that. But I wouldn't be disconnecting and reconnecting it, I can't recommend that and then learn tomorrow that static zapped something important.
yea I am getting nothing by connecting to pc. I have all the drivers adb and fastboot installed when I rooted and unlocked couple weeks back but it looks like device is not being recognized or read at all by the pc.
connecting to the pc holding the volume + button gets it recognized for a second and tries to install a driver apx but unsuccessfully.
I am not making any progress whatsoever kinda sucks starting the weekend like this. I have gone thru some bad stuff with my atrix but nothing like this were I cant even access my bootloader boot into recovery or even fastboot. Should I try and get it to just stay off and see if overnight it works its own magic? Hate going to sleep witht his on my mind but I think with a clear mind in the morning something good will happen.
I can get it to stay off by holding both vol+ and vol- but trying to turn it off with just the power button just keeps it turning back on/off...
so I slepted on it thru the night let the tablet rest but went back this morning and I still cant get into bootloader or recovery. Is there anything I can do?
Has anyone else had this problem where they cant boot into recovery or bootloader? It's like the power button and vol keys are unresponsive even though they still work to turn on the device.
are you sure that you flashed the right recovery? but you should still be able to get the bootloader. are you pressing power + volume down(volume down, not both volume buttons. i noticed you wrote both volume buttons) to get into the bootloader?
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
clago87 said:
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
Click to expand...
Click to collapse
good luck!
yea, only power button and the volume down button.
quick question before I connect the battery does it make a difference whether or not I have it plugged in charging or connected to the PC while trying to boot into bootloader?
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Was it stock (including recovery) or modified?
I would try to fastboot the TWRP over and then boot into that (Power & Vol+). But then... I seldom run stock.
SoNic67 said:
Was it stock (including recovery) or modified?
I would try to fastboot the TWRP over and then boot into that (Power & Vol+). But then... I seldom run stock.
Click to expand...
Click to collapse
No, it wasn't stock and I dont know what happened.. I was running the latest CM13 and rebooted this morning and it freezes up with the ASUS logo and saying "Fastboot Mode!!!" at the top... I've tried flashing twrp via fastboot but not getting anything.. I need a copy of the stock firmware with the boot system and recovery image in it but I'm having a hard time finding it.
BiasedThunder said:
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Click to expand...
Click to collapse
I too had this issue. Tried lot of key combinations. Didn't work. My solution was to connect to PC and run
fastboot continue
Then it booted normally. Everything stock.
Hope this helps.
BiasedThunder said:
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Click to expand...
Click to collapse
Phones boots into fastboot mode in two situations
1. Pressing vol up and power button simultaneously for rebooting
2. Your phone doesn't have recovery AND any OS installed
I guess your vol up button is constantly in pressed state.
Second situation cannot occur unless you wipe your system and recovery manually. So you are in the first situation
Your phone's vol up button is constantly in pressed state or electrically shorted may be due to water entering the case
Solution: You will have to open your phone's case and clean the area near the volume button. I guess you had opened the case/body and didn't fit it properly.
sziraqui said:
Phones boots into fastboot mode in two situations
1. Pressing vol up and power button simultaneously for rebooting
2. Your phone doesn't have recovery AND any OS installed
I guess your vol up button is constantly in pressed state.
Second situation cannot occur unless you wipe your system and recovery manually. So you are in the first situation
Your phone's vol up button is constantly in pressed state or electrically shorted may be due to water entering the case
Solution: You will have to open your phone's case and clean the area near the volume button. I guess you had opened the case/body and didn't fit it properly.
Click to expand...
Click to collapse
something happened when it rebooted and it lost recovery.. I fastboot flashed the new TWRP and reflashed the rom and all seems fine now.
Thanks for the quick responses!!
even I've witnessed a similar problem.. please help me.....out
BiasedThunder said:
No, it wasn't stock and I dont know what happened.. I was running the latest CM13 and rebooted this morning and it freezes up with the ASUS logo and saying "Fastboot Mode!!!" at the top... I've tried flashing twrp via fastboot but not getting anything.. I need a copy of the stock firmware with the boot system and recovery image in it but I'm having a hard time finding it.
Click to expand...
Click to collapse
Can any one please suggest where to find the stock firmware with the boot system....Please help me out here
Hello the second situation is happening to me. What can i do? In desperate
Help Me
Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?
grafikermc said:
Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?
Click to expand...
Click to collapse
Reinstall twrp from fastboot & install rom
I tried rooting Moto G4 Plus and just after flashing the supersu and rebooting, it got bricked. Nothing shows except LED blink while connecting to PC/charger. Also, it won't detect in the device manager as a qualcomm device/qhsusb bulk or anything... I seriously need your help. Please help.
PS: I surfed over various related threads and all of them required the device to be detected on PC.
1) are you able to power off your device, then hold down the power and volume down keys? Does that boot you into the bootloader?
Or can you hold the power button for 1-2 minutes to force a hard shutdown, then attempt to boot into the bootloader?
2) did you flash a custom kernel before attempting to root? On stock Nougat for our device, you need a custom kernel.
The device is already in the switched off stage. When I press and hold the power button, nothing happens. When connected to USB cable, the front LED blinks. Nothing more. It doesn't return any sound or indication while connecting to PC. I tried installing various Qualcomm drivers to get it detected on PC. The Windows device manager shows nothing.
I tried this tutorial to root my device. I missed flashing the elementalx kernel during the root process. it caused the brick.
technorajeev10 said:
The device is already in the switched off stage. When I press and hold the power button, nothing happens. When connected to USB cable, the front LED blinks. Nothing more. It doesn't return any sound or indication while connecting to PC. I tried installing various Qualcomm drivers to get it detected on PC. The Windows device manager shows nothing.
I tried this tutorial to root my device.
Click to expand...
Click to collapse
That tutorial should work, provided you flashed the ElementalX kernel before rooting.
Hmm, what happens if you try to boot by holding down both the power button and the volume down key at the same time? You should still be able to boot into the bootloader (with the AP fastboot secure mode).
What TWRP and SuperSU did you try to flash?
echo92 said:
That tutorial should work, provided you flashed the ElementalX kernel before rooting.
Hmm, what happens if you try to boot by holding down both the power button and the volume down key at the same time? You should still be able to boot into the bootloader (with the AP fastboot secure mode).
What TWRP and SuperSU did you try to flash?
Click to expand...
Click to collapse
I used twrp and supersu as exactly as mentioned in the root thread (twrp-3.2.1-0-athene.img & phh's supersu).
The key combo doesn't work either. No response. Is there any way to get it detected on PC?
I previously had it happened on my Yureka and I had to short the board to get it detected as a qcomm device.
technorajeev10 said:
I used twrp and supersu as exactly as mentioned in the root thread (twrp-3.2.1-0-athene.img & phh's supersu).
The key combo doesn't work either. No response. Is there any way to get it detected on PC?
I previously had it happened on my Yureka and I had to short the board to get it detected as a qcomm device.
Click to expand...
Click to collapse
That's odd, as that key combo should get you booting to the bootloader (as in the tutorial), which should then get your device detected via fastboot. Did your bootloader look similar to this when you were flashing TWRP?
https://plus.google.com/photos/106899236533864901773/album/6441285188929274337/6441285190332216978
If your device is still on, try a hard shutdown (hold power button 1-2 minutes until shutdown, verify it's off by connecting power, you should see the charging symbol come on), then boot by holding volume down and power at the same time.
You could also try a hard reboot https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/110630/p/30,6720,9687
I just found that the volume down key is broken. I hope that's the reason it won't boot to the bootloader. Let me fix it first and try your suggestion.
And yes, the bootloader menu was the same as shown in this pic.
Thanks a lot for your time bro. Much appreciated.
echo92 said:
That's odd, as that key combo should get you booting to the bootloader (as in the tutorial), which should then get your device detected via fastboot. Did your bootloader look similar to this when you were flashing TWRP?
https://plus.google.com/photos/106899236533864901773/album/6441285188929274337/6441285190332216978
If your device is still on, try a hard shutdown (hold power button 1-2 minutes until shutdown, verify it's off by connecting power, you should see the charging symbol come on), then boot by holding volume down and power at the same time.
You could also try a hard reboot https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/110630/p/30,6720,9687
Click to expand...
Click to collapse
I just disassembled the phone and flipped the volume rockers so that the volume down should work fine. Then pressed and hold vol - & power button. Violaaa. Got into the bootloader. On TWRP, Just wiped data and flashed the ElementalX followed by SuperSU. It's working super fine now. A billion hugs for your support.
I got a replacement device from OP and I was unlocking the bootloader and rooting it. The guide i used had the incorrect patched boot image and everything went bad quick.
I can't go anywhere except fastboot now, can't boot to OS, no OS installed.
TWRP WAS booting from fastboot, I pushed the rom from there and flashed it...said no OS installed after, I installed it on both slots.
I can't get into EDL mode, the volume keys work...I think, but the second I let go of them when it's plugged in it defaults back to fastboot immediately. I tried the bat file that people use, says it worked, phone stays in fastboot.
I even tried holding the volume keys the entire time but the MSM tool wouldn't read it enough to flash anything, although it did read it enough to register some data, but was stuck on "waiting for device".
I am in need of some major help. Now I can't even temp boot to twrp, getting an error failed authorization. I'm afraid I really messed things up.
I have 5 days to send my old device back. Please help!
May be a longshot, but does the stock recovery work? Maybe try sideloading the full OTA zip from there?
Sent from my IN2025 using Tapatalk
For EDL mode, you need to hold the buttons then plug it in while continuing to hold the buttons. It won't work if the phone is already plugged into a usb port and then you try and get into EDL.
Really hard to brick a OnePlus device in my experience.
FernBch said:
May be a longshot, but does the stock recovery work? Maybe try sideloading the full OTA zip from there?
Click to expand...
Click to collapse
Recovery doesn't work. I was able to get to one of the steps to approve going into fastboot, advanced, reboot to fastboot, but not anymore.
Mike02z said:
For EDL mode, you need to hold the buttons then plug it in while continuing to hold the buttons. It won't work if the phone is already plugged into a usb port and then you try and get into EDL.
Really hard to brick a OnePlus device in my experience.
Click to expand...
Click to collapse
I was doing just that. It seemed to work initially but after I plugged it in and released the buttons it went back to fastboot and disconnected from MSM.
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Please read this https://forum.xda-developers.com/showpost.php?p=82508527&postcount=67
and this https://forum.xda-developers.com/showpost.php?p=82658631&postcount=85
both work for me.
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
I ended up using the fastboot ROM flash all.bat from this thread: https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
I am now booting into the OS and the stock recovery came back. So good news is the phone isn't bricked.
Glad you sort it out
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
lazyd2 said:
Make sure MSM is ready keep vol up/down pressed, connect cable and immediately press Start in the tool. Have done it like this 3-4 times with my Pro
Click to expand...
Click to collapse
It work, thanks
You're a life saver