Database Users

[Q] Can I root 4.3 without flashing customer recovery

I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.

rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
This is still possible but the command for booting into custom recovery changed.
This helps.

rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
The short answer is no, you need a custom recovery to install superuser. The long answer is you can flash a custom recovery and install superuser and then flash back the stock recovery. If that doesn't work then your out of luck.

kzoodroid said:
The short answer is no, you need a custom recovery to install superuser. The long answer is you can flash a custom recovery and install superuser and then flash back the stock recovery. If that doesn't work then your out of luck.
Click to expand...
Click to collapse
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.

rajendra82 said:
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
Click to expand...
Click to collapse
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted

ajay_zalavadia said:
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
Click to expand...
Click to collapse
Follow @efrant's guide. Section E is enough assuming you are on stock android.
That will do the trick.

rajendra82 said:
I had rooted my Nexus 4 when on 4.2.x by putting it in bootloader mode first and typing fastboot boot <name of twrp custom recovery>.img at the command prompt to reboot it into TWRP custom recovery mode without if actually flashing the TWRP recovery on the device. Back then, this temporarily recovery mode allowed me to flash the supersu update zip file I needed to. Since 4.3, this command reboots the phone, but the screen is now blank, and I can't flash the zip file. I can reboot the phone normally into stock recovery mode using the volume keys and power button, but this does not allow me to flash the zip file to root it. Can I still use fastboot boot method like before, and how? The reason I want t stay on stock recovery for now is to keep future OTA updates from throwing an error message.
Click to expand...
Click to collapse
Sorry for asking about your reason, but if you install the TWRP (or some other) custom recovery then can't you simply manually flash the OTA yourself? That's how I upgraded to 4.3.

ajay_zalavadia said:
Can you please write a Step by Step guide to root without flashing custom recovery,
I am familiar with basic commands of adb and fastboot. But a step wise guide will hep me get my N4 rooted
Click to expand...
Click to collapse
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
adb reboot-bootloader
Click to expand...
Click to collapse
Then, once you're booted into Bootloader, type
fastboot -c "lge.kcal=0|0|0|x" boot customrecoveryname.img
Click to expand...
Click to collapse
Flash SuperSU 1.51 zip and then reboot your device.

rajendra82 said:
You are absolutely wrong. I just booted into TWRP without flashing it and rooted my Nexus 4, which is otherwise stock 4.3. I still have the stock recovery on the device and can access it using the volume keys. Booting into TWRP was a temporary state achieved using the command line syntax:
fastboot -c "<your_default_command_line> lge.kcal=0|0|0|x" boot <name of custom recovery>.img
The 4.2.x version of this command was simpler, as it did not require the -c "<your_default_command_line> lge.kcal=0|0|0|x" part, but you do need it on 4.3, or the device just temporarily boots into a blank screen, instead of the custom recovery. So the long answer is you do need to boot into a custom recovery, but it does not have to be flashed to the boot partition. With a Nexus 4, you are never out of luck.
Click to expand...
Click to collapse
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.

Mercado_Negro said:
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
Then, once you're booted into Bootloader, type
Flash SuperSU 1.51 zip and then reboot your device.
Click to expand...
Click to collapse
thank you, will try when I get chance :good:

kzoodroid said:
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Click to expand...
Click to collapse
I just prefer the command line booting instead of having to flash a recovery twice. I already knew that I could flash the custom recovery to get it done, although I didn't clearly state that in the original post.

Mercado_Negro said:
Copy your custom recovery to where fastboot.exe is.
Open a CMD window and type
Then, once you're booted into Bootloader, type
Flash SuperSU 1.51 zip and then reboot your device.
Click to expand...
Click to collapse
Thanks for you guide, but for use it, do I nerd unlocke the bootloader ?
Inviato dal mio Nexus 4 con Tapatalk 2

futuro82 said:
Thanks for you guide, but for use it, do I nerd unlocke the bootloader ?
Inviato dal mio Nexus 4 con Tapatalk 2
Click to expand...
Click to collapse
Yes

Thanks
Inviato dal mio Nexus 4 con Tapatalk 2

kzoodroid said:
In your original post you said you tried using the boot into recovery method and it didn't work so how am I wrong in saying that your only other option was to flash the custom recovery, install su, then flash the stock recovery all without rebooting? It was just another way of accomplishing the same thing. I posted at the same time as the other guy did who knew the new fastboot command, which I was unaware of and obviously you were too.
Click to expand...
Click to collapse
LOL.. You were still wrong though bro. Don't get upset about it. He didn't seem to be...
Sent from my Nexus 4 using xda app-developers app

[Q] cant flash custom recoveries

Hello I have recently bought a nexus 4 and updated to 4.3 via ota. I tried to flash custom roms but I am not able to open recoveries
I have successfully unlocked the bootloader but for some reason after flashing a custom recovery temporarily, it doesnt boot the recovery at all! its just a blank screen :/ help?

eeshlikhith said:
Hello I have recently bought a nexus 4 and updated to 4.3 via ota. I tried to flash custom roms but I am not able to open recoveries
I have successfully unlocked the bootloader but for some reason after flashing a custom recovery temporarily, it doesnt boot the recovery at all! its just a blank screen :/ help?
Click to expand...
Click to collapse
by "temporarily", do you mean you used the command "fastboot boot recovery.img" instead of "fastboot flash recovery recovery.img"?
Can you tell what are the output after you input the command?
If you wish to boot/flash the recovery via fastboot, the extension of the recovery file should be in .img instead of .zip. If you downloaded a zip file, you need to extract the recovery.img from the zip file.

eeshlikhith said:
Hello I have recently bought a nexus 4 and updated to 4.3 via ota. I tried to flash custom roms but I am not able to open recoveries
I have successfully unlocked the bootloader but for some reason after flashing a custom recovery temporarily, it doesnt boot the recovery at all! its just a blank screen :/ help?
Click to expand...
Click to collapse
With 4.3 the command for booting into custom recovery has changed.
With the help of hwti and el_charlie from this post you are able to boot into recovery.
Basically:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
The command for flashing another recovery remained the same.

I just used the ncry tool kit in which when i clicked the recovery menu i could choose to temporarily boot into a custom recovery (wither TWRP OR CWM) But the thing is then it doesnt show up

[Q] Recovery Issues.

Hi,
I just unlocked and rooted my Nex 10 today, installed a custom recovery and everything done by the book.
I did it a couple of times, even three cause every time I installed the recovery CWM or TWRP it worked right after I installed it.
Then I rebooted the tablet, tried to get back into the recovery, and always dead droid
Can someone please tell me what am I doing wrong???
Also can I install the latest SuperSU version??
Thanks

When you say by the book where your steps
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
And then you choose recovery it works, you flashed a ROM, then booted to ROM but when you boot back to recovery it has been replaced with stock?
It sounds like you may have ran the wrong command like
fastboot boot nameofrecovery.img
In this case you would not overwrite existing recovery with custom
Sent from my Nexus 7 using XDA Premium 4 mobile app

Can't boot into recovery no matter how many times it is installed

Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?

carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app

Same thing, successful install and it won't open. Just shows the dead android when going to recovery.

carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app

Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought

tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app

tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.

If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.

Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!

[Help][A2017G] SoftBrick only bootloader and stock recovery

Hi,
I have an A2017G which after trying linageos had the stock rom from here https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 TWRP and an unlocked bootloader. That worked ok, and I wanted to upgrade to the stock ROM 7.1. I installed this using TWRP https://forum.xda-developers.com/showpost.php?p=71664539&postcount=29. But now when it boot's after the bootloader it's stuck showing a linux logo, and it won't boot Android.
In the bootloader (http://i.imgur.com/Os4vkwT.jpg) I can try to go to fastboot, but selecting that only reboots the phone. I can however select recovery and go to the stock recovery (http://i.imgur.com/PBj6y6X.jpg). From there I have tried to sideload (selecting Apply update from ADB and adb sideload rom.zip) the stock rom (http://www.ztedevice.com/support/detail?id=1170789A90BA42E18B3364B80C7F5A26), the previous rom I tried to install (https://forum.xda-developers.com/showpost.php?p=71664539&postcount=29) and another TWRP stock rom (https://forum.xda-developers.com/axon-7/development/rom-kernel-stock-7-1-1-b02-based-a2017g-t3592470) but all fail at the very beginning saying "(adbd status 1) Installation aborted" (http://i.imgur.com/RzNSBtu.jpg).
I also tried to install linageos back using sideload but it fails ("failed to verify whole-file signature"). I believe that is because it's not the official rom and the stock recovery only accepts that.
ADB only works in sideload mode and fastboot doesn't (it loads the bootloader again).
Do you know how I should proceed? How could I install the stock rom, or TWRP again?
Thanks in advance.

Try it with this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-reinstall-twrp-root-update-to-t3578552
If you can't flash recovery with axon7toolkit try it with the last step "Get Fastboot" first. ZTE removed the fastboot mode in Nougat, so you have to flash another fastboot image.
If you can boot into fastboot again you can flash TWRP and from TWRP a rom.
Good luck!

Hi Darkem,
Thanks a lot, that actually worked. I was under the impression I wouldn't be able to install TWRP because I was only able to use the command "adb sideload update.zip" but other commands like "adb reboot edl" didn't work. But as it's said in the other post, pushing the three buttons of the phone set the phone into EDL mode. From there I was able to install TWRP.
Thanks a lot again

(A2017G) Hello. I no longer have access to fastboot because I flash a stock rom (Nougat) with the recovery stock and it has removed my modified bootloader, I managed to install twrp in edl mode but I still have no access to bootloader. What should I do please? Flash a stock rom (Marshmallow) here (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547) to gain access to fastboot again (bootloader )? Thank you. Sorry translation from French to English with Google Translate

GAO161 said:
Hello. I no longer have access to fastboot because I flash a stock rom (Nougat) with the recovery stock and it has removed my modified bootloader, I managed to install twrp in edl mode but I still have no access to bootloader. What should I do please? Flash a stock rom (Marshmallow) here (https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547) to gain access to fastboot again (bootloader )? Thank you. Sorry translation from French to English with Google Translate
Click to expand...
Click to collapse
Granted I have the A2017U, but in stock recovery I can still access the phone memory with my pc. Why not download the stock rom from ZTE, put it on the phone memory, and flash it in the stock recovery?

tabletalker7 said:
Granted I have the A2017U, but in stock recovery I can still access the phone memory with my pc. Why not download the stock rom from ZTE, put it on the phone memory, and flash it in the stock recovery?
Click to expand...
Click to collapse
So I flash a recovery stock with twrp and then I update to an official version Marshmallow with the recovery stock? I will recover my bootloader? Thank you

GAO161 said:
So I flash a recovery stock with twrp and then I update to an official version Marshmallow with the recovery stock? I will recover my bootloader? Thank you
Click to expand...
Click to collapse
Sorry, why do you want fastboot? If you're planning to relock the bootloader you'll need to be fully stock, which wouldn't be the case if you just installed a fastboot zip. Relocking the bootloader is probably the only thing that fastboot is mandatory for

Choose an username... said:
Sorry, why do you want fastboot? If you're planning to relock the bootloader you'll need to be fully stock, which wouldn't be the case if you just installed a fastboot zip. Relocking the bootloader is probably the only thing that fastboot is mandatory for
Click to expand...
Click to collapse
I want fastboot to be able to order with adb. Before I had it and when I flash a rom stock nougat it has deleted me

GAO161 said:
I want fastboot to be able to order with adb. Before I had it and when I flash a rom stock nougat it has deleted me
Click to expand...
Click to collapse
on fastboot mode you have fastboot lol
you have adb on FTM mode (vol down + power) or recovery

Choose an username... said:
on fastboot mode you have fastboot lol
you have adb on FTM mode (vol down + power) or recovery
Click to expand...
Click to collapse
I want to go back to ROM stock and bootloader locked but when I do not have access to the bootloader anymore I can not do the command "adb lock oem"