Hi,
I had rooted my N7 with the Wug's toolkit back when i received it. I did not select CWM at that time (i was crazy).
Since rooted people cannot apply the OTA 4.1.2 update, I have been trying various methods to get into recovery (a common problem with rooted devices).
Nothing seemed to work so I decided to re-run the process of root from the toolkit. during the process, whenever the toolkit rebooted to bootloader, my device would just stay on the fastboot menu. the toolkit showed as if it was pushing the binaries etc and doing its thing, and then rebooted the device back to normal (i had opted the CWM this time to right my wrongs).
After the process, when i checked for Super User, it failed to install updates. Upon checking with 'root checker', it said this device is not properly rooted.
I can boot into CWM recovery now but is doesn't allow me to install the update manually.
Another weird thing is that although i'm still on 4.1.1 JRO03D, the system update prompts have gone and on manually check for updates in settings, it says that my system is up to date!
Please help!
This is the WRONG section.....again....
I had the same problem, you should flash the old bootloader with a toolkit, search for a guide...
Related
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Just reflash the superSU.zip from here http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in CWM and you should be rooted again. You will not loose any data so no need to backup. Download OTA Rootkeeper from Play to regain root after installing future OTA`s.
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
AAhrens said:
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
Click to expand...
Click to collapse
Try cmd and type: adb reboot recovery. If you see the androidian (stock recovery) you have to reflash the TWRP img file in fastboot mode.
Will this reset my phone? Or does only rooting do that?
You will not loose any data.
Sent from my Nexus 4 using xda premium
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Let me guess, you used a toolkit to root?
a) You did the full OTA, so you lost your custom recovery.
b) flash images through fastboot and skip the recovery.
c) Only after you flash a custom recovery. If your recovery is sitting in the same folder as fastboot and named "recovery.img, simply cd into the fastboot folder in a command prompt and type
fastboot flash recovery recovery.img
d) Not unless you lock or relock your bootloader.
OP, you need to do some more research and uninstall the toolkit from your computer. You know just enough to cause yourself problems, but not enough to know why they happen or how to fix them.
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Rizy7 said:
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Click to expand...
Click to collapse
Thanks all, was able to get it fixed by re-rooting!
My device was fine and rooted until 4.3 dropped and just like when 4.2 dropped I lost root access.
I downloaded the Nexus Root Toolkit and ran through the Root process. There were a couple of times where the on screen messages weren't going forward such as push files to device, etc. but when I rebooted the device it seemed to be ok and it went into TWRP.
After it went into TWRP it said Rooting but nothing happened. I hit reboot, system, then it asked if I wanted to root. I swiped for yes.
I rebooted my device and started Super SU. It says my device isn't rooted.
Can anyone assist me with this. I'm almost thinking this isn't worth it if I have to jump through hoops every time there is an update.
Thanks.
Nevermind I fixed it. I had to install SuperSU 1.5 manually in recovery in order to get it to work.
Will tht work on my razor hd maxx xt926..same issuie had root.then over the air ota update 4.3 took my root accsess..tried reroot several ways..no luck.got it to install a diff su app..but when reboot..says su not installed .everytime I reboot the symbal # pops up says update binary .try to says same .su not installed..plz tell me step by step how u went in recovery to manually install.how reboot in recovery?.then update from playstore?.or flash again?and re root?
Sent from my SCH-I545 using xda app-developers app
http://techglimpse.com/steps-root-custom-rom-android-nexus/
So I updated my tab because there was an incremental update. I lost root and twrp after that, so I used wugs toolkit flash twrp and root my device. My question is, the process installed busybox and whenever I install it (coz wug said so during the process) the binaries do not seem to be found as it continuously nags me to update when I already did so. Also, it doesn't seem to be installed on system/xbin. Need help
Hi all,
I have put myself/phone in an interesting situation, which I am hoping the community can help me with.
I recently bought an LG G2, dold with stock 4.4.2. I proceeded to root it, and tried installing custom recovery.
I first installed ROM manager, which didnt work.
I then tried flashing twrp through adb using loki, which gave me a 'this is not a loki file' error.
I eventually realized that they had closed the Loki loophole in stock 4.4.2.
At this point, trying to enter recovery wouls give me a 'secure booting failed' error, making me have to reboot the phone again.
I then unrooted my phone, and factory reset it. I realized Clockworkmod recovery (which ROM manager installed) persisted despite the data wipe, so I unchecked that option in ROM manager and wiped it again.
My thinking was that I vould now downgrade to 4.2.2, install custom recovery there, then flash 4.4.2 whitout losing root or recovery.
Problem: I can't do any of this, because I can't reroot my phone with ioroot25. It fails as when it reboots inti recovery it gives me the 'secure booting failed' error.
Thanks for any help. I simply want to root my phone and if possible, have a functional recovery in order for me to flash some mods. At least being able to have it rooted again would be sweet.
Hehh...
Last thing you can do is try to flash with LG Flash Tools Method or LG Support Tool
Flash stock recovery either via fastboot / or dd(on linux). Then you can proceed further.
Or ^ kdz via download mode.
I have a similar problem. I restored the stock recovery via adb using a dd command. Then I unrooted in order to accept the latest OTA. The OTA fails with a "suspected root" error. Download mode still has "ROOTED" in red letters. At this point I gave up on the OTA and wanted to get back to where I was.
IOROOT25 doesn't work because when the phone reboots to recovery mode, I get the broken android with the red triangle but nothing else on the screen at all. There are no options, nothing. Eventually it reboots. I've done a factory reset to no avail. Recovery seems corrupted.
I need instructions for flashing the stock recovery with no root.
I managed to get my recovery rewritten using the LG Mobile Support Tool on a different computer. Then I was able to root again using ioroot25. I'm not sure why I couldn't run on my own laptop, but it's fixed now.
I just got a new Nexus 7 (2013). I did all the OTA updates until I got on the latest 5.1.1 (LMY48G). I was able to unlock bootloader using Wug's Nexus Root Toolkit. I then tried rooting using the same tool but the process would freeze once it reached the step of temporarily booting TWRP. The window timed out while waiting for device. The tablet did boot to TWRP recovery. However, when I went to reboot to system from TWRP, I got a message saying No OS installed. I was able to reboot back to system despite the message.
At this point, I used Wug's tool to Flash Stock + Unroot. I then tried using CF- Auto Root which worked fine with me. I was now rooted but when flashing to recovery, I got the dead android. I tried downloading TWRP app from Google Store to updated recovery through that method. I did get TWRP flashed but again I still have the No OS Installed message when going to reboot. Finally, I used use Wug's tool to delete TWRP and go back to stock recovery (dead android). Then I tried flashing TWRP through Wug's tool but ended up with same result of getting No OS installed.
Any ideas why I would be getting this message when I am able to reboot back to perfectly working system? Has anyone else experienced a similar problem and been able to get TWRP working correctly?