I just got my Shield TV Pro and have successfully unlocked the bootloader and achieved root.
I understand that upon updates I will likely have to root again. However, does the bootloader stay unlocked permanently now that I've done this?
How do I get back to Twrp when I choose to do a Nandroid backup? I used my PC to unlock bootloader and root via ADB. I won't need it to access Twrp each time will I? Can I get to it through the hardware recovery method? (Unplug power, plug back in and hold power on 3-5 seconds, immediately release when you see menu pop up)
Tenacious--M said:
Can I get to [TWRP] through the hardware recovery method? (Unplug power, plug back in and hold power on 3-5 seconds, immediately release when you see menu pop up)
Click to expand...
Click to collapse
Yes, but strangely this does not work unless the micro-USB cable is plugged in. You can also reboot to recovery with an ADB command (adb reboot recovery) and there are a few apps like ROM Toolbox that can do it (root required of course.) And yes, your bootloader stays unlocked unless you lock it again manually.
Related
What's wrong:
I cannot go in bootloader mode with the hardware keys.
When I press vol up + trackpad + power i get 3 short vibrates and charging led flashes, screen stays off.
I can access bootloader if I use reboot bootloader from a adb shell.
This is what happened:
I have bootloader 0.84.2000 PC10110000 (eng hboot) and rage method root on desire-z with stock rom (1.34.405.5).
I also flashed godspeed OC kernel
I wanted to protect myself from losing root and s-off if I would do the ota update.
I have read that gfree would accomplish this.
So I decided to do this, but I made the mistake of doing this within recovery.
I ran gfree, but my sdcard wasn't mounted, So after a reboot I didn't find the backup of my radio partition, this way I lost my original radio config partion.
When I rebooted, I wanted to check my S-off was still persent or not. and I couldn't get into the bootloader.
I got 3 short vibrates and a flashing red/orange charging led.
I can access recovery and bootloader from adb shell with reboot recovery/bootloader.
I know what I did wrong, but don't know how to fix it.
yelti said:
What's wrong:
I cannot go in bootloader mode with the hardware keys.
When I press vol up + trackpad + power i get 3 short vibrates and charging led flashes, screen stays off.
I can access bootloader if I use reboot bootloader from a adb shell.
This is what happened:
I have bootloader 0.84.2000 PC10110000 (eng hboot) and rage method root on desire-z with stock rom (1.34.405.5).
I also flashed godspeed OC kernel
I wanted to protect myself from losing root and s-off if I would do the ota update.
I have read that gfree would accomplish this.
So I decided to do this, but I made the mistake of doing this within recovery.
I ran gfree, but my sdcard wasn't mounted, So after a reboot I didn't find the backup of my radio partition, this way I lost my original radio config partion.
When I rebooted, I wanted to check my S-off was still persent or not. and I couldn't get into the bootloader.
I got 3 short vibrates and a flashing red/orange charging led.
I can access recovery and bootloader from adb shell with reboot recovery/bootloader.
I know what I did wrong, but don't know how to fix it.
Click to expand...
Click to collapse
try vol-down + power
Here's a post explaining whats going on:
Here's someone else with your same problem:
skiptomylou11 said:
I got a question.
I did this last week, and it seemed that it was done successfuly. The problem is that I tried to boot into recovery by pressing Volume + and power and I got three vibrations and the LED light just flashed red. I had to battery pull to be able to get the phone going again.
So that means I can only access recovery through ROM Manager, which makes me uneasy because it means that if I get a boot-loop I could potentially be screwed...
Click to expand...
Click to collapse
Here's the explanation:
steviewevie said:
That's not how you boot into recovery. The good news is that you have proved you have radio S-OFF, because unless you have that then you don't get that flashing amber light state. You put the phone into a different recovery mode where I believe a PC can talk to the OSBL, but currently we don't have any documented procedures on how to use that mode.
You can get into recovery by holding Volume *Down* and Power, then you'll get into HBOOT. Then you can choose the "Recovery" option and it will boot you into Clockwork Recovery (assuming you've got that flashed).
Click to expand...
Click to collapse
So actually all of us who have used gfree have this same function, wouldn't actually call it a problem, just another unexplored utility.
Here's a link to where I found the awnser:
http://forum.xda-developers.com/showthread.php?p=9715282&highlight=volume+power#post9715282
post #223 and #224
Hey
Thx for your response, I tried the vol down and power and it worked.
I'm glad to see my phone is still ok.
This thread can be closed if needed.
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.
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 was messing with my P10 Lite and I accidentally wiped the Vendor partition (not sure if I wiped anything else) with TWRP. After the phone rebooted it said something about a critical error during boot and went into erecovery. It gave me two options( I don't remember the second one) and I chose factory reset. It started doing it's thing but I guess something went wrong because it wasn't able to boot and it started to bootloop.
I managed to get into fastboot once. The bootloader and FRP should be unlocked but I am not sure as I think I semi accidentally used the command to relock the bootloader in the hopes of it doing the automatic low level factory reset. After that restart, the phone wanted to boot up but after the Huawei logo it went into the EMUI logo which I've shown in the pictures. Now I can't use any button combination and can't enter any menu. I also can't shut down the phone as it bootloops into the EMUI logo after I press the power button. I opened the phone and turned it off by detaching the battery cable but after holding the power down key and plugging the usb cable into the phone it still boots into the EMUI logo right after the Huawei logo.
I guess not being able to enter fastboot is the major issue and after hours of googling I am yet to find a solution.
Edit: I am a newb!
Please help!
Why did you delete the vendor partition, you could try plugging the phone into your computer and checking if you can do anything with fastboot while it's showing emui logo?
Alaunus said:
I was messing with my P10 Lite and I accidentally wiped the Vendor partition (not sure if I wiped anything else) with TWRP. After the phone rebooted it said something about a critical error during boot and went into erecovery. It gave me two options( I don't remember the second one) and I chose factory reset. It started doing it's thing but I guess something went wrong because it wasn't able to boot and it started to bootloop.
I managed to get into fastboot once. The bootloader and FRP should be unlocked but I am not sure as I think I semi accidentally used the command to relock the bootloader in the hopes of it doing the automatic low level factory reset. After that restart, the phone wanted to boot up but after the Huawei logo it went into the EMUI logo which I've shown in the pictures. Now I can't use any button combination and can't enter any menu. I also can't shut down the phone as it bootloops into the EMUI logo after I press the power button. I opened the phone and turned it off by detaching the battery cable but after holding the power down key and plugging the usb cable into the phone it still boots into the EMUI logo right after the Huawei logo.
I guess not being able to enter fastboot is the major issue and after hours of googling I am yet to find a solution.
Edit: I am a newb!
Please help!
Click to expand...
Click to collapse
Dload method. Put sd card in other phone or some card readers and put appropriate files.
nemanjsb said:
Dload method. Put sd card in other phone or some card readers and put appropriate files.
Click to expand...
Click to collapse
I've already tried that. I've placed the appropriate files into my SDcard but I can't use any button commands including volume up+down+power. When I press them my device just boots into the EMUI logo and nothing happens.
Edit: It boots into the EMUI logo even if I only press the power button. Pressing volume down + usb also boots me into the EMUI logo
DaarkZek said:
Why did you delete the vendor partition, you could try plugging the phone into your computer and checking if you can do anything with fastboot while it's showing emui logo?
Click to expand...
Click to collapse
I measured once and not trice before cutting... I was also not paying enough attention/in a hurry...
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Aalesund said:
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Click to expand...
Click to collapse
Ok, it seems like not all is lost about my phone. I managed to get into fastboot. In my situation, pressing volume down + usb cable while the battery was plugged into the phone did not work. That was before I opened up my phone's case and disconnected the battery cable.
As I mentioned before, I had opened my phone and disconnected the battery cable because that was the only way to shut it off.
What I did after I disconnected the battery cable was the following:
1 - Hold volume down and don't release it
2 - Plug in USB
3 - Plug in the battery cable into the phone's mobo.
That booted me into fastboot. Right now, the phone says my bootloader in unlocked and my FRP is locked. What would be the best way to flash the new stock OS on my phone?
Aalesund said:
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Click to expand...
Click to collapse
I have downloaded THIS and THIS for the new OS but by talking with Alexxxx1 in THIS discussion I learnt that Huawei has implemented a security patch in their latest update, which I've most likely installed, that prevents you from rolling back your OS version. That means I need to install the .386 version, which should be the last if I am not wrong, instead of the .378 correct? Though I heavily dislike patches like this I guess I can't do anything about that...
Hi,
I'm not very experienced with those root things and followed a tutorial to do so.
I unlocked the bootloader, had TWRP installed and root. This worked. Now I wanted to remove Root and TWRP and go back to the original state. I couldn't find the stock recovery file, so I installed the P996A04V1.3.0B13_MR2_sd_ssl.zip via TWRP from the SD Card. Till here it worked. I could enter the stock recover and boot the phone.
Then Android wanted to install a security update. I allowed it and this is where the problem started.
The install process stood still on 25% for minutes. I thought it stuck and pressed and hold the power button to reboot that I can wipe the memory. But nothing happened. But the installation Process continued suddenly. I had the feeling that this power key worked like a skip key. So maybe it didn't install a file where it was stuck.
After the installation reached 100% the screen switched to black and nothing worked anymore. I couldn't restart the phone or anything but I think the phone was doing something cause it consumed electricity. When I checked the phone hours later I noticed it was empty.
I can reach the unlocked bootloader now, but none of the selections works. Doing nothing to boot or select Recovery lead to black screen and stuck. Then I have to wait until the battery is empty again. Fastboot, Power Off just restart the phone and I end in the Bootmenu again. I can't even fully charge the phone. As soon as it has enough power to start the Bootmenu appears. So I don't see the display of the charging process.
I don't understand how this could happen. I tried different key combinations when the phone had enough electricty to start. The phone always restarts and end in the bootmenu. Only when I press all three keys it's standing still on the ZTE Logo screen but as soon as I release the keys I end again in the bootmenu.
How can I force another Update?
regards
Let' start with the basic questions:
Do you have proper backup of your data?
Which Android Version did your Axon had before it went unusable?
You could try to reflash TWRP.
Boot your phone into bootmode.
Download a proper TWRP Image on your PC (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Open a cmd shell (press the windows key and type 'cmd' -> press enter)
Navigate to the folder where the TWRP Image is stored ('
Code:
cd C:\Users\[I]YOUR_USER_NAME[/I]\Downloads\
')
Type: '
HTML:
fastboot flash recovery [I]TWRP_IMG_NAME.img[/I]
'
Afterwards you could try to reboot into recovery mode.
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Stevie123 said:
I don't have a backup. But there isn't something imortant on the phone that I want to keep. I can do a full reset and reinstall, too.
Android must have been the latest offical availabe what's in the file. Was it Android 8? V1.3.0B13
The fastboot mode doesn't work. The screen turns black and the LED blinks red but only for a moment. Then the phone restarts and I'm in the bootmenu again. Windows doesn't recognize it as device.
Is there a way to force it to do an update from my SDCard without it needed to be connected to a PC?
Click to expand...
Click to collapse
I don't know of any.
But you could boot into EDL Mode (Press and hold Both Volume button and then press the power button) and flash a Stock EDL rom from the Download Center i have linkd before.
It's not visible for the PC. The only thing I see is the charging screen when its total empty and you can't even boot as. As soon as it has enough power to switch to the normal screen the bootloader appears and when I do nothing the screen turns black and nothing happens. I don't even know if it is charging. The LED is off.
Follow this guide to unbrick it and then use MiFlash and flash an EDL ROM
https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229