I have a nexus 4, I've previously been able to root it and I've run CM10 and pac roms on there, with no problems. I've also previously flashed CWM recovery, no problems.
However, since I've flashed it back to stock Android 4.3, I now cannot access any form of custom recovery,
When I go into the bootloader and select recovery, the device shows a green android fella lying down, with a red triangle and exclamation mark.
I have tried to use Nexus Root Toolkit v1.7.2 to flash custom recovery, when it says it's booting into recovery temporariily, the phone just shows the google logo and nrt says "Waiting for device".
I've also tried locking and re-unlocking, no change,
Tried flashing permanent and temporary recovery, same problem.
I've tried things on forums but none of them seem to work...
(USB debugging enabled, MTP disabled... adb sees the device, just not when google logo is showing.)
Also, when in android 4.3, SuperSU says "there is no SU binaary installed, and SuperSU cannot install it. This is a problem!"
Any help?
Thanks
I think the best way is to restore it again to stock. If you are using Windows use Wug's Nexus 4 Toolkit. Just don't forget to back up.
Then Root your phone,
Install Flashify
Download TWRP
Install TWRP via Flashify (root required)
Sent from my Nexus 4 using Tapatalk
UnwiredDroid said:
I think the best way is to restore it again to stock. If you are using Windows use Wug's Nexus 4 Toolkit. Just don't forget to back up.
Then Root your phone,
Install Flashify
Download TWRP
Install TWRP via Flashify (root required)
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I have restored to stock, that's what I'm running.
I'm using that same toolkit.
I've tried re-rooting the phone, but when it tries to boot to TWRP temporarily, it goes back to the google logo and is stuck there, computer doesnt list it as an adb device. I have to holddown power and reboot, but noting has changed.
://
Related
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
GatorsUF said:
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
To enable ADB to go:
Settings-> About Tablet-> Click Build Number for Easter Egg Multiple times! BOOM!
I am not sure if there's a way of rooting without PC and custom recovery.
hello guys,
I had 4.4.1 rom+kernel stock, rooted and custom recovery, after the OTA to 4.4.2 lost my root and recovery.
tried re-root with wug's but it gets stuck on "pushing root file to you device".
got superSU application but cant remove it because its system application.
Is there a way to root it?
thanks.
Same here except i had cwm touch latest. It seems i have lost my recovery too. If i try and boot into the recovery menu i get the open hood android with a red triangle.
No custom kernel only custom recovery.
Sent from my Nexus 7 (2012)
I lost my custom recovery too. But I just reflashed it (adb reboot bootloader, then flashed a downloaded custom recovery via fastboot), and then reflashed SuperSU as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
santoshgs said:
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
Click to expand...
Click to collapse
I was in the same situation after my OTA of 4.4.2
I had nexus root toolkit, tried to put in twrp with it failed.
Then updated to the latest nrt and then I could flash the latest twrp, havent tried cwm.
and eventually got the root back using nrt
7thAkash said:
I was in the same situation after my OTA of 4.4.2
I had nexus root toolkit, tried to put in twrp with it failed.
Then updated to the latest nrt and then I could flash the latest twrp, havent tried cwm.
and eventually got the root back using nrt
Click to expand...
Click to collapse
Ah, glad that it worked! ^_^
santoshgs said:
I'm having the same problem. Root undone, and recovery went back to stock. Custom recovery doesn't stick after reboot.
Click to expand...
Click to collapse
Found the solution to my problem. Used CF Auto Root instead of manually flashing SuperSU again. Cheers guys!
http://download.chainfire.eu/363/CF...merhead-hammerhead-nexus5.zip?retrieve_file=1
Same thing happened to me. just use fastboot to flash CWM, then before you reboot go into the recovery. then next time you reboot it will still be there. For some reason if I flash the recovery then reboot without entering recovery it will loose the recovery.
Once you have the recovery back, just flash the SuperSU binary through CWM.
Also, IMHO, dont use toolkits... you dont really know whats going on when you use those. Learn to use ADB & fastboot. They are really simple to use and you will be better able to help yourself when you have problems in the future.
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.
Hi, recently I updated my rooted nexus 4 to 4.4.4 jellybean, which then unrooted it. I still have SuperSU installed, but once I try to run any root apps, it says I am not rooted. Looking around, I need to reroot the device, but my custom recovery TWRP has been uninstalled. I tried to install twrp with GooManager but it wouldn't download. The best option seems to be to reroot the device, but I cannot make a nan droid backup as no recovery installed. I have one but its fairly old, and I will lose a lot of data. What I need is a way to install custom recovery but I'm not rooted :/
You know this is the nexus 10 forum right?
What you need to do is flash a recovery via fastboot and then reroot.
Sent from my Galaxy Nexus using XDA Free mobile app
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?