Related
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Trickee360 said:
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Click to expand...
Click to collapse
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
veeman said:
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
Click to expand...
Click to collapse
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Trickee360 said:
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
got it. thanks much
Will only boot to stock recovery
veeman said:
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
You can just root again and you will have root access.
I lost root too, so I just opened wugtoolkit and hit root. no unlock needed so no loss of programs either.
jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
Any news about this. I stay in the same problem.
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
jayyo said:
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
Click to expand...
Click to collapse
So, the bootloader 3.41 is the problem?
Southmad said:
So, the bootloader 3.41 is the problem?
Click to expand...
Click to collapse
For some people, yes. No idea why.
veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Would that image work ok for Galaxy s3? Or there is no difference at all, just matter the 4.1.2 android version?
Cuz i updated my device throught Kies (cuzz from the device itself it didnt allow, stating that the image has been modifyied :angel: ) and after that even with the persistent mode on Super SU the root is gone
Hi
A while ago i flashed leaked android 4.3 from here:
http://forum.xda-developers.com/showthread.php?t=2368401
and suddenly i realized that i have lost root access. I can't get into recovery (TWRP)
What should I do? Please help!
why do you think that you wouldnt lose root after flashing stock? and you didnt lose your recovery, it got replaced by stock recovery, as always when you flash stock. you need to flash your custom recovery of choice via fastboot, then flash the su binaries via your newly reflashed custom recovery. thats all. a simple search would have found you the answer, because mamy people get stuck there after every single new android version. to prevent this from happening, do some research before flashing anything.
simms22 said:
why do you think that you wouldnt lose root after flashing stock? and you didnt lose your recovery, it got replaced by stock recovery, as always when you flash stock. you need to flash your custom recovery of choice via fastboot, then flash the su binaries via your newly reflashed custom recovery. thats all. a simple search would have found you the answer, because mamy people get stuck there after every single new android version. to prevent this from happening, do some research before flashing anything.
Click to expand...
Click to collapse
TWRP is still there because when small update comes (3.9 MB) is doesn't install. Instead it reboots into TWRP
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Danokan said:
Verizon LG G2
Rooted
Installed TWRP
Without thinking (doink) tried to install the latest OTA.
OTA failed.
Now I cannot reboot into TWRP.
Installed ClockwordMOD and installed its own custom recovery. Still won't boot into any custom recovery.
Phone works fine other than that.
How can I get back into custom reccovery?
Note: When I turn phone off and try to reboot into custom recovery it takes me to the "reset" screen.. and then IT RESETS the phone.
When I try to boot into recovery from Clockwork or TWRP app it gives me the android robot with the open tummy and red triangle.
Click to expand...
Click to collapse
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Amro90 said:
The OTA update installed the KitKat bootloader, which hasn't been hacked for custom recovery yet.
Use this to downgrade the only the bootloader and install custom recovery: http://forum.xda-developers.com/showthread.php?t=2715496
You have to root frist. You can use IORoot25 to root the KitKat rom that you have now: http://forum.xda-developers.com/showpost.php?p=48709232
Click to expand...
Click to collapse
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Danokan said:
Ok.
The KITKAT rom didn't install properly..
Phone says 4.2.2
Super user and apps that need root to work are working properly. Looks like the bootloader is the only thing that got hit.
Click to expand...
Click to collapse
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Amro90 said:
Oh. Not sure if AutoRec works if you are still on 4.2.2. Sorry bout that.
If it doesn't work, you can always just manually flash the complete firmware using this guide: http://forum.xda-developers.com/showthread.php?t=2432476. Surest way to get back from failed flashes. You can flash the full 4.2.2 or 4.4.2 KDZ and then start over again. That method wipes everything though.
Click to expand...
Click to collapse
YIKES.
Well.. it got the TWRP recovery loaded alright.
But it won't boot into anything else...light is flashing but screen is black.
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Danokan said:
HELP
I am screwed here.
#1. Tried the "unbrick stock" solution. Can NOT get it to work. I tried it all 3 ways given and it gets to the LG driver start... and then it says I am up to date. I tried to change the country, the language, upgrade recovery, can NOT get it to work.
#2. I can get TWRP to load. But I can't get my computer to recognize my phone so I can move a rom over
#3. I can't get ADB to recognize my phone.
HEEEEEEEEEEEEEEEEEEEEEEELP
Click to expand...
Click to collapse
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Hartendief said:
save yourself the hassle flash stock 4.4.2 KK, use IORoot25 to root and then use Autorec to install Custom recovery.
Time needed 1 hour.
Click to expand...
Click to collapse
How do you propose I flash it?
SOLVED
FIXED
http://forum.xda-developers.com/showthread.php?t=2448960
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
sfobrien said:
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
Click to expand...
Click to collapse
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Lenster45 said:
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Click to expand...
Click to collapse
Since you took the OTA your bootloader may be locked. After you get it unlocked I gave you where to get the recovery you need, the one you have is not KitKat friendly.
Lenster45 said:
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
Click to expand...
Click to collapse
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
charesa39;53763629
EDIT: Oh said:
Strange, had a friend who took the OTA awhile back and it locked the bootloader. It was a JB version maybe they changed it with KitKat ? ( he could have locked it prior to my getting it going who knows) Thanks for the info, have never used an OTA since I got my N10 when it first came out.
Click to expand...
Click to collapse
charesa39 said:
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
Click to expand...
Click to collapse
That did it. Thanks
Hi,
Could you add a [SOLVED] tag to the title, as it is now solved ?
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
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.