I received my new 5X the other day and have been trying to root it. I got the bootloader unlocked and Super SU is on the phone, but this is where the problem begins. I booted the phone into bootloader mode then scrolled down to recovery. I press the power button so I can swipe SU and complete the rooting, but instead the Google name appears and then I get the dreaded android on his back with the red traingle and exclamation point. Can I fix this without having to reset the phone and start over completely? Thanks.
You have to flash a modified boot image to root. How did you miss this? http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
/data will not be touched, so just follow the instructions and then flash SuperSU in TWRP
I did my rooting on my Mac and his tutorial is on a PC.
Austexcat said:
I did my rooting on my Mac and his tutorial is on a PC.
Click to expand...
Click to collapse
It's the same process. In fact if you setup SDK correctly, its easier.
Edit: the SDK rather.
Sent from my Nexus 5X using Tapatalk
Related
I picked up the Galaxy Nexus from Verizon yesterday and attempted the unlocking and rooting procedure on droid-life.com. It looked like it was working, but now I can not get into recovery. When I try, I end up stuck on the screen with Andy and a red yield sign. I can get into the bootloader and run fastboot from my computer. The phone does still boot up completely.
I've seen posts about using Terminal Emulator and flash_image to restore the recovery, but Terminal Emulator says it can't find su. So something must have failed with the rooting.
Is there any information I can gather to help with this? Any help would be greatly appreciated. I'm out of ideas. My only other rooting experience was on my OG nearly two years ago and it went flawlessly.
Download the image in this thread and flash via fastboot. Make sure to delete /system/reboot-from-recovery.p afterwards.
Android screen with red exclamation point is the stock recovery image. Press power and either up or down volume to get into the recovery.
But yes, you'd want to flash clockwork mod like the guy above me said. Also rename or delete that file he wrote, otherwise on every boot, your recovery will go back to stock recovery.
Sent from my Galaxy Nexus
Oh. I hadn't found any documentation on the stock recovery so when I saw Andy open with a red yield and exclamation sign, I assumed it was bad. Thanks for the help!
EDIT: Got it thanks.
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
CasuallyDressed said:
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
Click to expand...
Click to collapse
You have 2 choices.
1) Start from square 1 and try to install L again using the instructions you have or other instructions that can be found right here on XDA (i wouldnt because you arent installing the actual OTA but rather the developer version which has bugs and such and you will end up having to do number 2 when L comes out anyways.)
2) unbrick your device by reflashing it to stock. there are plenty of ways to do this, look for unbricking on the forums here and you should be ok.
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
metalblaster said:
You have 2 choices.
1) Start from square 1 and try to install L again using the instructions you have or other instructions that can be found right here on XDA (i wouldnt because you arent installing the actual OTA but rather the developer version which has bugs and such and you will end up having to do number 2 when L comes out anyways.)
2) unbrick your device by reflashing it to stock. there are plenty of ways to do this, look for unbricking on the forums here and you should be ok.
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
Click to expand...
Click to collapse
1) I can't update using the instructions as it hangs at 'Erasing user data'.
2) I've tried to unbrick and flash back to stock using NRT but it just goes back to FlashBoot and never finishes.
Dunno if I'm allowed to, but...
BUMP!!
metalblaster said:
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
Click to expand...
Click to collapse
You're absolutely right! Always, always make a backup/nandroid before flashing a different rom. But if you don't and like to live dangerously you should at least have the sdk installed and know how to use adb/fastboot! One thing though about restoring a backup, it does not restore the bootloader. Android L uses bootloader version 4.04 and KitKat uses 4.02. The first L preview used the same bootloader as KK but the new preview does not. I have no idea what kind of bugs or worse would result from restoring a KK nandroid onto the 4.04 bootloader. Maybe nothing but I purposely didn't try to find out if it would cause any problems. Couple nights ago I checked out the preview for maybe an hour then went back to 4.4.4. I flashed the 4.4.4 factory image using a modified flash_all batch file then restored on top of that. I guess I could have instead fastboot flashed the bootloader then went straight into recovery to install my backup. Just something to think about, bootloader versions.
CasuallyDressed said:
1) I can't update using the instructions as it hangs at 'Erasing user data'.
2) I've tried to unbrick and flash back to stock using NRT but it just goes back to FlashBoot and never finishes.
Click to expand...
Click to collapse
You said previously "The tablet will now only display 2 screens: Google with unlocked padlock, or recovery." Unlocked padlock means your bootloader is unlocked and your device now can have images flashed to it. Recovery or bootloader screen? You need to be able to get into the bootloader screen. Press and hold the volume down button, while still holding down the volume button press the power button for a few seconds release the power button and it should go into the bootloader screen. There are a couple toolkits that might help, Wug"s and One-Click Restore come to mind. I've never used them so I wouldn't be any help as far as they go. I can try to help if you want to use the sdk. Do you have the android sdk installed?
i had the same problem , i tried one click restore and it works fine
Wow don'T!!!!
CasuallyDressed said:
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
Click to expand...
Click to collapse
Don't delete your user data before backing it up!
See WugFreshs Threads on XDA!
So I used ATGAdmin's guide here: http://forum.xda-developers.com/showthread.php?t=2381582
Used "Dead_Nexus7.bat" and it fixed me right up. Plus, I love the "Look you dumb motherf**kers" attitude he has in his video.
I appear to be all sorted anyway! Thanks to those who suggested 'One Click Restore', it set me on the right path.
Hello all, I have searched for more than a couple hours and just seem to be getting nowhere. Here's the deal: I have an HTC One M8 with TWRP, root, an unlocked bootloader and S-ON. I want to install Lollipop, but can't take the OTA.
I know a little bit about what I'm doing, I tried to flash a rooted stock ROM but it didn't take. I wiped all directories but the internal storage. Also wiped the Dalvik, `but I could not get the update to take. I tried a few other things but out of fear of bricking my phone I wasn't very adventurous. I flashed the backup I made beforehand and it worked fine.
I think I have the wrong file...? Could my S-ON be the problem?
Sprint HTC One M8 (HK edition)
Android: v4.4.4
Sense: v6.0
Kernel: 3.4.0
Baseband: v1.08.20.0916
Build:3.31.654.2
All I want to do is flash lollipop. Will I have to lock the bootloader and go back to stock recovery to do it? Can I use adb sideload to install it via adb?
Thank you for your time.
http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10
ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10
Click to expand...
Click to collapse
I'm pretty sure my phone is toast.
PLEASE HELP, it worked just fine before I took your advice...
I relocked the bootloader and verified it multiple times before doing this. I made sure everything was exactly the way it was explained in the instructions, all files were correct.
I put the phone into fastboot, which I verified with adb.
I ran the Sprint_HTC_One_M8_HK_4.20.654.10_RUU .exe file and followed the instructions.
Both the program and pphone are currently frozen. They have been this way for almost 2 hours now.
The phone is stuck at the black HTC splash screen and the installer says
Updating...(0/7)... #(<--- these dots are still in motion like its installing)
Updating the ROM image on your Android phone...
[color=redPlease do not remove the USB connection from the Android phone or launch any programs during the update process.[/red]
Remember, this operation will take about 10 minutes.
Click to expand...
Click to collapse
I haven't done anything, its still plugged in.
I don't know what to do, can I just unplug it and flash my bavkup with TWRP?
PLEASE HELP I'M FREAKING OUT.
ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10
Click to expand...
Click to collapse
not_important said:
I'm pretty sure my phone is toast.
PLEASE HELP, it worked just fine before I took your advice...
I relocked the bootloader and verified it multiple times before doing this. I made sure everything was exactly the way it was explained in the instructions, all files were correct.
I put the phone into fastboot, which I verified with adb.
I ran the Sprint_HTC_One_M8_HK_4.20.654.10_RUU .exe file and followed the instructions.
Both the program and pphone are currently frozen. They have been this way for almost 2 hours now.
The phone is stuck at the black HTC splash screen and the installer says
I haven't done anything, its still plugged in.
I don't know what to do, can I just unplug it and flash my bavkup with TWRP?
PLEASE HELP I'M FREAKING OUT.
Click to expand...
Click to collapse
Ok, the phone is not recognized by adb but is still recognized by fastboot, can I reboot it into TWRP by using
Code:
fastboot reboot recovery
then just flash the backup I made before all this crap started?
*EDIT* RESOLVED
Never mind, I resolved it myself. I just typed
Code:
fastboot reboot
and hit enter. It booted right up.
not_important said:
Ok, the phone is not recognized by adb but is still recognized by fastboot, can I reboot it into TWRP by using
Code:
fastboot reboot recovery
then just flash the backup I made before all this crap started?
*EDIT* RESOLVED
Never mind, I resolved it myself. I just typed
Code:
fastboot reboot
and hit enter. It booted right up.
Click to expand...
Click to collapse
I looked through it and all user made folders are gone, but all user downloaded apps are still there. I also noticed that superSU root access was off, but the 'apply on boot' option was turned on, could this be what crashed the updater?
Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!
My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.
Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised
thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything
I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device
I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140
Thanks, Mike01680. trying now
When i go into sideload i can see the device listed on adb devices!
Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Do you have TWRP installed?
webhook said:
Do you have TWRP installed?
Click to expand...
Click to collapse
No
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Rooting pixel phones are pretty straight forward and not much difficulties. Two different approaches:
1. If you are an experienced user and 100% sure what you are doing, then go back to your rooting process step by step to make sure you didn't miss anything.
2. If you are not sure that you have done everything correctly, then I would suggest you that you follow the steps which describe in this thread, believe it still the most detail explanation for rooting the pixel phones even today. https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356231/
Also posting your question on this thread could get you quicker response.
If after your trying of everything you still couldn't get it done, then describe your entire process when you ask for help without people have to guess what could went wrong.
PS: The only information which you shouldn't follow with that thread is "NOT" to use the latest platform tool, stay with version 33.0.3, version 34.0.1 has problem.
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Stupid question also could be the wire your using and usb port
If you guys are bootlooping after flashing Magisk patched image...
You should use the Google's official Android Flash Tool to reset your device to a working state...
Then you should use badabing2003's PixelFlasher to root; it automates most of what's needed to root, and it has checks and protocols to make sure files are correct, versions are correct, and the right procedure happens in the right order -- taking out a lot of guesswork or mis-steps that might be happening that is causing bootloops.
Many/You would be surprised how many times PixelFlasher succeeds where many have failed; almost miraculously and/or inexplicably! It's why it's become rather famous tool for Pixels...
Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
fluxfield said:
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Click to expand...
Click to collapse
Previously rooted with Magisk modules?
Incompatibility with newer updates is more often than not the cause of bootloops.
Rebooting into safe mode will disable them.
Press and hold volume down when the bootloader unlocked warning screen appears. Then let go as soon as you feel a vibration.
You will boot into safe mode and modules will be disabled.
Then reboot normally and go into Magisk and re-enable only safe modules such as USNF.
Test the others one by one until you find the culprit. Usually it will be a font changing module or an AOSP mod .
It's pretty straightforward provided you have an unlocked bootloader, USB debugging and platform tools, The latest works for root alone btw.
In terminal
Code:
adb devices
Authorise adb in the popup window
Code:
adb reboot bootloader
If fastboot isn't recognising your phone install the USB driver
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Code:
fastboot reboot
Profit.
Assuming you've patched the right boot.img file from the .zip within the factory image zip file and you're using magisk from github.
fil3s said:
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Click to expand...
Click to collapse
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
simplepinoi177 said:
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
Click to expand...
Click to collapse
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
fil3s said:
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
Click to expand...
Click to collapse
aaahh...i see now...
sorry, i just made that assumption because you put the fastboot command to installing/flashing the image right after the sentence -- i made the mistake of connecting the two...
i should've known better as i was already initially confused as you don't install the driver AS a fastboot command...!