[help] Stuck in bootloop - Nexus Player Q&A, Help & Troubleshooting

So, here is the deal,
I was rooting my nexus player though the normal process (by flashing the root.img via fastboot, just like in the tutorial) and everything was looking good, so when the device rebooted I looked for the superSU app but it wasn´t there. So I went to the play store dowloaded the superSu app directly from there (thinking better kind of a noob move ). It installed and asked to update the binaries, I accepted ( through normal, not with the custom recovery), after a while it notified me that the process was unsuccessfull and asked me to reboot and try again later, so I did it.
After that the device entered in a bootloop, and now I have nothing but access to the bootloader and the stock recovery...
ps: I had successfully installed the Cyanogen recovery, before it happened
ps2: Sorry by the bad english, it isn´t my main language

Flash the supersu maybe? From recovery?

There is talk about this in a few threads and it has work arounds

I did it!!
So, I took the weekend, to cool my head and today I came up with a fairly simple answer, I used the Nexus Root Toolkit by Wugfresh ( http://forum.xda-developers.com/showthread.php?t=1766475 ), and the process couldn´t be simpler. I just put the NP in bootloader, opened the toolkit and used the option to flash stock.

Related

[Q] Problem with TWRP in rooted and unlocked nexus 10

Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..
All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app
same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.

Can't root

I have installed CWM, TWRP, Philz touch, I am unlocked and obviously have a custom recovery, BUT I CANNOT ROOT for the life of me. I've download 20 different versions of SuperSU and Superuser. Half of them just flat out fail to flash in recovery, the others succeed but I still never have root when I reboot. I've used Philz SuperSU flash option, it succeeds but then I never have root. I've tried downloading the various superuser apps from the market, sideload via USB, NOTHING WORKS. I cannot for the life of me get this goddamn thing to root. I've flashed hundreds of roms before across dozens of android devices, I have NEVER ran into this problem before. I have flashed and rooted dozens of roms to THIS device before, but now I cannot root anymore.
Does anybody have a solution? God I hate android sometimes.
RunNgun42 said:
I have installed CWM, TWRP, Philz touch, I am unlocked and obviously have a custom recovery, BUT I CANNOT ROOT for the life of me. I've download 20 different versions of SuperSU and Superuser. Half of them just flat out fail to flash in recovery, the others succeed but I still never have root when I reboot. I've used Philz SuperSU flash option, it succeeds but then I never have root. I've tried downloading the various superuser apps from the market, sideload via USB, NOTHING WORKS. I cannot for the life of me get this goddamn thing to root. I've flashed hundreds of roms before across dozens of android devices, I have NEVER ran into this problem before. I have flashed and rooted dozens of roms to THIS device before, but now I cannot root anymore.
Does anybody have a solution? God I hate android sometimes.
Click to expand...
Click to collapse
Hi, RunNgun42...
Probably you're missing something completely bleeding obvious... sometimes you can be too close to a problem, such that you can't see the wider picture.
Anyway, if you have TWRP or CWM installed, then this should work.
------------------------------------
Chainfire SuperSU
http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
SuperSU XDA discussion thread
http://forum.xda-developers.com/showthread.php?t=1538053
------------------------------------
I've just test flashed the above linked Chainfire SuperSU v1.89 via TWRP 2.6.3.1 on my own Nexus 7 and it flashed without problems.
It might help others, for them to help you, if you could report any displayed error messages... even the most (seemingly) trivial messages may be sufficient to 'nail the problem' and thereby resolve it.
Hope this helps... and good luck rooting.
Rgrds,
Ged.
GedBlake said:
Hi, RunNgun42...
Probably you're missing something completely bleeding obvious... sometimes you can be too close to a problem, such that you can't see the wider picture.
Anyway, if you have TWRP or CWM installed, then this should work.
------------------------------------
Chainfire SuperSU
http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
SuperSU XDA discussion thread
http://forum.xda-developers.com/showthread.php?t=1538053
------------------------------------
I've just test flashed the above linked Chainfire SuperSU v1.89 via TWRP 2.6.3.1 on my own Nexus 7 and it flashed without problems.
It might help others, for them to help you, if you could report any displayed error messages... even the most (seemingly) trivial messages may be sufficient to 'nail the problem' and thereby resolve it.
Hope this helps... and good luck rooting.
Rgrds,
Ged.
Click to expand...
Click to collapse
I have the same problem and it isn't so simple. I try to get root with CF-AutoRoot and flashing ZIP file. Nothing work.
I explain the issue. Updating to 4.4 (official OTA) get into bootloop. I flashed system and boot.img from 4.3 factory image to return. When I try to update again, it das bootlooped again. Then, I decide to do the same with 4.4 factory image (only system and boot) and I successfull update N7. Then, I didn't get to root anymore. I update to 4.4.1 and 4.4.2 and the same problems.
In addition, I have experimented slow charge (I see some others talk about that since 4.4.2 update).
I think that this are one of the bests tableta, but now we see that is not so good.
Enviado desde mi Nexus 7 mediante Tapatalk
Ok so I had to basically redo EVERYTHING from scratch using Wug's Toolkit. We're talking like the day I unboxed the phone. New bootloader, new boot.img, new recovery, new rom, new root. Finally everything working now, but dang. I have no idea what happened. Best I can surmise is that the boot.img got messed up somehow. Granted I already did all of those things but not in that order. I literally treated the phone like a new phone and just went through the rooting process from start to finish all over again.

[Q] Need help removing CWM from N4

Ok guys, so I'm gonna need some serious help here! (rookie speaking)
My N4 is currently on stock 4.4.4. I got the 5.0 OTA update, downloaded it, but then when it was time to apply it the phone went into clockworkmod fastboot (I never realized it was there, once I asked a friend to root my phone but he just told me he couldn't finish the process).
So, I am currently struggling with trying to remove CWM altogether. I use ubuntu 12.04, have adb access and did successfully order it to go into reboot bootloader, but that was it. Couldn't get past that. I also did try to, through CWM's boot interface do a sideload, which I commanded via terminal with the .zip file I downloaded from the google developer website for my phone, but at the end it just said "installation aborted". How do I even get past that? Or how do I get the flash-all.sh script to run successfully? I'm stuck! (and obviously not very knowledgeable on this).
Any help is welcome, not afraid of bricking (lol, jk, yes I am).
UPDATE: As I was typing the aforementioned post, I tried all the format options within CWB recovery mode and now the phone is forever stuck on the google logo screen. I think I've officially bricked my phone. Any workaround this or is gone forever?
The firmware update to 5.0 will wipe out CWM and remove Root if you had it. Please see [INFO] Nexus 4 OTA Help-Desk
Also for your reference, should you need it Understanding the Android world before rooting your LG Nexus
If you do at all consider rooting again, please see [Guide] Ultimate Nexus 4 Root Guide
If you are still stuck, please post in [HELP THREAD] nexus4 Ask any question. and one of the experts will be happy to help.
FIXED
Was able to wipe everything out and flash a stock recovery image from google after borrowing a friend's computer with Windows and using SkipSoft Unified Android Toolkit v1.2.8.
Now successfully running Lollipop on my N4, relocked bootloader and don't plan on unlocking it ever again! Phew!

win droid tool kit

Hi I am using the windroid toolkit trying to root my new x pure. I got thru the first two steps ok, with a message thats its ok to move on to step 3, root access by flashing superuser.... everytime I try to flash super user I get a message that the phone is in the wrong state? I am still in the fastboot mode, start option. Is that correct? I tried rebooting the phone into the recovery mode by selecting the power and up volume keys, but that did not work? Im confused.......If I got by the 2nd step, should team win be in the recovery? thanks for any ideas here......
Why do you need a toolkit to root?
update,,,, the toolkit was on youtube and looked like an easy way to go thru the unlock, install recovery, root process. It worked fine and fast for the first two sections. I have an unlocked bootloader and teamwin recovery. I went to a different video that showed how to flash superuser into the recovery. I did that and now the phone is stuck on the Android M bootup screen. I am able to boot into the fastboot flash mode and teamwin recovery, so Im not completely bricked. Just stuck on the boot screen. Turns out the flashing superuser method does not work on Marshmellow... Anyone know how to fix this?
Did a bunch of searching and after a very long night I was able to return to stock, 5.1.1. Phone is back to normal and rooted. Lots of info here....just need to find it.....
Garyalp said:
Did a bunch of searching and after a very long night I was able to return to stock, 5.1.1. Phone is back to normal and rooted. Lots of info here....just need to find it.....
Click to expand...
Click to collapse
You can update to Android M 6.0 and then you should flash SuperSU 2.62-3 through TWRP to gain root, after rooting with this version or SuperSU, you should be able to update to a new version of SuperSU, I have update to SuperSu 2.65 with no issue. This was the easiest way that I have found to root our phone running Android M 6.0.
Thank you for that information. Wish I had it from the beginning, would have saved a bunch of trouble. Turns out I spoke to soon. I am having the wi fi issue that some have had. I have gone from a stock 5.1.1 to 6.0, unlocked bootloader, teamwin recovery, soft brick, back to 5.1.1, now rooted. Not sure exactly where the phone is. The bootloader remained unlocked thru the reflash to stock 5.1.1. I noticed that the mac address and Ip address are both, "unavailable", when I go to: settings/wifi/ advanced. Most likely the reason wifi is inop. Is there a way to find the mac and Ip address? Which modem should I be on, now that Im 5.1.1? Will a factory reset bring them back or does that just clear user data? As you can tell I know just enough to be dangerous....lol.
mcx6 said:
You can update to Android M 6.0 and then you should flash SuperSU 2.62-3 through TWRP to gain root, after rooting with this version or SuperSU, you should be able to update to a new version of SuperSU, I have update to SuperSu 2.65 with no issue. This was the easiest way that I have found to root our phone running Android M 6.0.
Click to expand...
Click to collapse
exactly what I did, works great.

HELP. Phone stuck on black screen after installing SuperUser.

Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
UPDATE #2
So I did what abhi212b told me to do and flashed the stock rom. Everything is fine now.
I'll try rooting it again a bit later. Thanks for the help.
UPDATE #3
I tried rooting my phone again, and it went flawlessly this time! Rooted successfully.
What an emotional rollercoaster lol.
Push the power button for at least 2-3 minutes. Worked for me and others in the past.
SSJGod said:
Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
Click to expand...
Click to collapse
Like the poster above stated, hold the power button until the screen shuts off. YOUR PHONE WILL AUTO REBOOT!!! The instant the screen turns off, begin holding the volume down button. When you see the fastboot screen pop up, begin flashing your N images again, or use a custom ROM (which are generally much faster, easier to mess with, and easier to recover from).
Ex didn't flash properly.. That is what I can estimate! If u root on stock kernel, it breaks the device.
As said above go to bootloader (works on any screen... Power and volume down) and then to twrp maybe (flash twrp from fastboot). And then restore any previous nandroid u have.. If not u will have to flash stock via fastboot and then flash ex kernel. When u flash, restart and go to about phone and see if the kernel shows elemental x.. If yes, go to twrp and root it via suoersu, phhh's superuser or magisk su.. Whichever u like.. That should be fine!
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
SSJGod said:
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
Click to expand...
Click to collapse
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Thank you, will try this now.
Only the last SuperSU Beta defaults to systemless install. Any other ones require writing of a .SuperSU file to force systemless before rooting.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
SSJGod said:
Thank you, will try this now.
Click to expand...
Click to collapse
If you have not done this already, you can give it a try by flashing the stock boot.img via twrp and see if that boots the device.
I am not sure that it will work since, i have not tried it.
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
just_magikkal said:
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
Click to expand...
Click to collapse
I think that is the kernel issue.. you should try EX.. and then use SuperSU or maybe use Magisk SU..
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Had the same problem as OP and this fixed it, thanks a lot man!
Good to hear now the phone is alive!

Categories

Resources