Database Users

[Q] Nexus4 stuck on Google Logo, won't boot into custom recovery

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.
://

lost root after 4.4.2 upgrade, cant re-root

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.

Unrooted, can't reroot, corrupted recovery on 4.4.2

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.

TWRP won't load after initial install, and root doesn't work.

I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!

I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.

DirtyHennessy said:
I had the same issue from 7.0 and forward. SUpersu causes a bootloop even on a fresh rom. You could give Magisk a try it worked for me at least.
Click to expand...
Click to collapse
Thanks! I will try that.

Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Have you made sure to update your radio, bootloader and vendor to the most recent version? Make sure to also try flashing twrp again but do everything through fastboot flash commands on your pc.

Seamus1 said:
I've had my 6P since Nov of 15, and I have always run it with a stock rom that is rooted. I've used Heisenberg's guide since day one, and never run into any considerable trouble.
Today though, after not updating the rom for a while, I am running into two issues. I went from angler nmf26f to the most current one, n2g47o.
Thing 1 - after I install twrp through fastboot, I can load into it and everything is fine. However, after I reboot, I can no longer load it again. When I go into the bootloader and select Recovery, after a few moments I get a screen saying 'No command'
I have reinstalled twrp a few times but it has done nothing to help.
Thing 2 - Root is no longer working. I have installed the newest SuperSU through twrp and while the app is present on the phone, it says root undetected.
Any of you folks run into anything similar? The phone/rom works fine otherwise. Thanks!
Click to expand...
Click to collapse
Flash root in TWRP before your first boot into the stock rom. On Nougat 7.0+, stock recovery replaces TWRP on boot if you do not. This solves both of your problems. When you clean flash and install a custom rom, with or without root, TWRP will remain. If you just use stock unrooted, then you should flash root before first boot each month when you update.
Sent from my Nexus 5X using Tapatalk

SuperSu 2.80 & 2.81 broke root for most phones - including mine. I had to flash 2.79 SR3 to get root again. Chainfire released 2.82 this morning but I haven't tried it yet.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

If you boot to twrp first time mount system and use the filemanager to delete recovery-from-boot.p under system. Use magisk instead of supersu for root.

Having Problems Trying to Root / Flash TWRP

Hey all, I've spent my entire night trying to get root on my new OnePlus 5 so that I can transfer all of my data from my Nexus 6p over through TitaniumBackup, but for some reason I am having weird issues.
I've followed Funk Wizard's guide on unlocking the bootloader and getting a custom recovery to root, but that's when weird things began to happen. I flawlessly was able to get TWRP running the first time through since it was similar setup to how I got everything working on my Nexus 6p. Once I tried booting back into the ROM though after flashing Magisk, the boot failed and rebooted back into recovery. This kept happening no matter what I tried to do. TWRP also was failing to flash the full Oxygen OS zips as well. I tried flashing stock recovery over TWRP to see if that would let me flash the zip, but then it stuck me back in TWRP afterwards despite overwriting it. I updated the TWRP to the "last latest build" which allowed me to flash the zip and boot back into my ROM successfully. However, then I tried going back into the recovery, it defaulted to the stock one again rather than the TWRP I had before. I reflashed TWRP but it keeps getting the stock OnePlus 5 recovery consistently. I am unsure of what to do. :\ I have to switch back to my old battery-failing phone for the time being. I'm not sure what I'm doing wrong.
Drivers work; manually forced the ADB driver for fastboot. Device just OTA'd to 4.5.3 a few moments ago; I am still getting the same issue. I also tried the latest TWRP but it still achieved no results whatsoever. All of my flashing is done through fastboot.

Hi I red your problem tho I am new here I successfuly rooted my OnePlus 5.
I think that the problem is either not using proper rooting zip's or bad drivers so I will tell you how I rooted mine.
I reccomend using this tool so you will be sure 100% that you have the ADB, Fastboot and necessary Drivers.
https://forum.xda-developers.com/showthread.php?t=2588979
Those are the files that I used(The Magisk zip file and the recovery):
https://mega.nz/#!AA8FGLZR!63Q4HGrAoIlNlwR_NVj8Rbq4RKoPKaEnHLtHuEW3o94
I do not remember from where I downloaded them, neither I can find them from my messy history cuz I searched a lot for them around the internet, so I upload them for you!
Magisk link:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
So basically I went to my phone's settings unlocked Developer options by spamming the build number so I can get there and enable OEM unlocking and USB debugging. After that I rebooted my phone into fastboot mode like I just normally turned it off and hold the power button and VOL+ key. after that I connected my OnePlus to the PC using the DASH cable. You should download beforehand the TRWP and latest Magisk.zip so you can root it using Magisk I have not tried using SuperSU. So you basucally flash the TWRP using the "fastboot flash recovery twrp-3.1.1-0-oneplus5.img" command in my case and you transfer the Magisk Manager and zip file on the phone later so you can root. Then you just flash Magisk's latest zip file or use mine. I do not remember if I manually installed the Magisk Manager APK file tho I have it downloaded on my PC gonna zip them real quick with the recovery and uploade them.