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
Related
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
HOW TO ROOT YOUR DEVICE WITHOUT FLASHING RECOVERY
This can be done with two methods.
ADB or FASTBOOT.
I have tested both methods and they worked for me.
I tested this on JSS15J. I am not sure about any other versions but I guess it should work.
SOME BASIC INFORMATION
Usually when you want to root your device, you must have UNLOCKED BOOTLOADER.
A CUSTOM RECOVERY is usually used to flash SuperSU to gain root access.
CUSTOM RECOVERIES ARE USUALLY FLASHED (they permanently replace your stock recovery)
In this guide, You BOOT into custom recovery by going into BOOTLOADER and then using fastboot/adb tools to flash SuperSU .
Booting is temporary and thus once you restart from recovery, the custom recovery will be gone
Make sure, you have USB debugging mode enabled. To go into bootloader you can either use adb commands ( Type [adb reboot bootloader] in cmd in platform tools directory with your device connected) or do it manually by turning it off and then holding power and volume down.
You must also have platform tools of SDK (Fastboot and ADB) for this to work. MAKE SURE YOU OPEN CMD into the folder where platform tools are present.
Try it on OWN risk. I will not be responsible for bricked devices or any damage.
ADB METHOD
Connect to your PC and make sure USB debugging is on.
COMMANDS IN BRACKETS. DON'T WRITE THEM. COMMAND WOULD BE LIKE : fastboot boot recovery.img
MAKE SURE YOUR DEVICE HAS UNLOCKED BOOTLOADER
(fastboot boot [recovery.img])--------------------- Name of recovery to be here
Mount /system and push the necessary files once the recovery has started:
(adb push su /system/xbin)
(adb push Superuser.apk /system/app)
Set correct permissions:
(adb shell)------------------------------ You have got into your device's shell
(chmod 06755 /system/xbin/su)
(chmod 0644 /system/app/SuperSU.apk)
(exit)
Reboot:
(adb reboot)
FASTBOOT METHOD
This is relatively easier as you will boot into custom recovery temporarily and then flash ZIP of SuperSU. Afterwards I recommend to clear davik cache and restart.
UNLOCKED BOOTLOADER REQUIRED
Boot into bootloader.
Type these commands to boot into custom recovery. This will not flash recovery and you will have stock recovery once you restart.
fastboot boot recovery recovery.img where recovery.img will be the file name of recovery
(After 4.4, use this command "fastboot boot recovery.img" instead of above mentioned)
After booting into reccovery, flash SuperSU and you are done.
I recommend clearing dalvik cache before leaving and restart.
And you are done.
YOU CAN ALSO USE A PREROOTED KERNEL WHICH YOU CAN FLASH VIA FASTBOOT. I AM NOT SURE IF THERE IS ANY
For information on how to retain root after OTA, please refer to this :
Update Super SU is also taken from this guide.
http://forum.xda-developers.com/showthread.php?t=2415497
For Recovery/SuperSU/TWRP
http://forum.xda-developers.com/showthread.php?t=2382051
CWM
http://forum.xda-developers.com/showthread.php?t=2381544
PLATFORM TOOLS:
http://www.androidfilehost.com/?fid=9390355257214632011
If you are stuck in a bootloop, make sure you have cleared dalvik cache in custom recovery.
I got bootloop when i tried with fastboot method as I was new to twrp, I explored it a bit and tried to remove system and tried overwriting data to see how it is different from CWM and check its strength. I got an error clearing cache so I rebooted into custom recovery to clear dalvik and my nexus booted fine (DON'T TRY THIS, JUST CLEAR CACHE AND WIPE DATA and restart)
REMEMBER, UNLOCKING BOOTLOADER WILL DELETE ALL YOUR DATA AND DOING WIPES WILL ALSO DELETE ALL YOUR DATA.
DALVIK WON'T DELETE YOUR DATA BUT
MAKE SURE YOU HAVE MADE A BACKUP using BACKUP PRO (non rooted) or Helium (non rooted) and Titanium Backup Pro (Daah, you are not rooted so this won't work)
GOOD LUCK
Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.
sfhub said:
Booting into custom recovery to install root works fine.
As you mentioned unlocking bootloader is still a prerequisite.
You may want to just use the SuperSU install zip though. Though I haven't tried Superuser on this tablet, it is my understanding it hasn't been modified to work with 4.3 security. That may have changed since I last looked so if you find differently please post. SuperSU added a daemon mode to deal with 4.3 security changes.
Click to expand...
Click to collapse
I got bootloop but then realised it might due to trying to wipe system in twrp. Clearing dalvik worked fine .SuperSU used
So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)
Muikkuman said:
So you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
You will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
[UPDATE]
http://forum.xda-developers.com/showthread.php?t=2415497
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone
Hnk1 said:
The trick here is to BOOT into custom recovery BUT not FLASH recovery permanently. Once you restart, the CUSTOM recovery will be gone.
You can use simple commands if using Fastboot
fastboot boot recovery [recovery name.img]
This way you will install SuperSU using recovery which is relatively easier than ADB commands.
This way you will only go into recovery temporarily.
I also read a forum where you can preserver root even after OTA/ Updates.
Do check that out as well.
I tried this with Twrp and superSU.
I got bootloop as I have been always CWM person so I accidently tried to delete system too with dalvik cache and hard reset and I got an error
However, I boot again into recovery and cleared wipes and the bootloop was gone
Click to expand...
Click to collapse
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)
Muikkuman said:
Thanks for your reply I'll make sure to check everything out.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Anytime mate
How do we clear dalvik without a custom recovery?
Master619 said:
How do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
You restart your device. Boot into bootloader and use fastboot to Boot into custom recovery(command given in post above).Once Into recovery, you can easily clear dalvik cache.
And remember, it might not require clearing cache because I was exploring twrp n overwriting data n tried To delete system to see how powerful the recovery is. I will update guide now
muikkuman said:
so you don't replace stock recovery if you boot into a custom recovery using fastboot?
Sent from my nexus 7 (2013)
Click to expand...
Click to collapse
master619 said:
how do we clear dalvik without a custom recovery?
Click to expand...
Click to collapse
guide updated. Check it.
Platform tools are being attached
The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.
gunner49 said:
The "fastboot boot recovery recovery.img" command is not working anymore. The command prompt returns with a "cannot load recovery" error. At least that's what it does on my Nexus 7 running Android 4.4.2.
This seems to affect Android 4.3 and upwards according to this Nexus 4 thread: http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
There's a workaround with a different fastboot command line as mentioned in the thread. I wonder if there's also a fix for the Nexus 7. Any replies would be greatly appreciated.
Click to expand...
Click to collapse
Did you try: fastboot boot recovery.img ?
mdamaged said:
Did you try: fastboot boot recovery.img ?
Click to expand...
Click to collapse
That worked a treat! Thanks a lot mate!
Those who finding difficulty in rooting Nexus 7 (2013) can use Wugfresh Nexus Root Toolkit. It is so powerful that you would find every function you would like to do on your Nexus 7, from the comfort of your PC. Also watch qbking77 's video on using the Toolkit for further information.
I am looking for a way to root my Nexus 4 (and 7 later on should be able to figure that out through this) without flashing CWM or TWRP. Essentially, I just want to root and keep OTA updates. At the current time, 4.3 has been just fine for me, however I would like root for certain applications. I have heard you can use TWRP and still get OTA updates, but it seems every thread I've checked has lots of people saying yes and no to that, so I am not sure.
Is there anyway to flash the zip without installing a custom recovery? I have been searching for a couple days and have gotten no definite answer. Of course I could just not be using the right search words as always.
Yes you can use the fastboot boot command to temporarily go into twrp (instead of permanently flashing it) and flash the root zip. After you reboot twrp will be gone, and it will go back to stock recovery. Search up 'oode' on YouTube. He's got a video that shows you how to do this (on the n7, but the steps are essentially the same as for the n4...just different recovery file)
Sent using xda-developers app
I tried doing this, but anything I load with "fastboot boot blablabla.img" doesnt boot correctly. The custom recovery is actually running, as i can connect with adb shell and I get a root shell, but it is completely black screen. I tried with both CWM images, twrp, and even the stock recovery.img. they all load to blackscreen when I use "fastboot boot" but they work fine when I do "fastboot flash recovery blablabla.img".
So, if you dont mind navigating the recovery blind, then sure, you can load up a custom CWM, then find your way somehow to the "install zip-> install from sideload" option. Then grab the installer zip for kouch's superuser and run "adb sideload superuser.zip". wait about 30 seconds, and then "adb shell", and finally "reboot".
gianptune said:
I tried doing this, but anything I load with "fastboot boot blablabla.img" doesnt boot correctly. The custom recovery is actually running, as i can connect with adb shell and I get a root shell, but it is completely black screen. I tried with both CWM images, twrp, and even the stock recovery.img. they all load to blackscreen when I use "fastboot boot" but they work fine when I do "fastboot flash recovery blablabla.img".
So, if you dont mind navigating the recovery blind, then sure, you can load up a custom CWM, then find your way somehow to the "install zip-> install from sideload" option. Then grab the installer zip for kouch's superuser and run "adb sideload superuser.zip". wait about 30 seconds, and then "adb shell", and finally "reboot".
Click to expand...
Click to collapse
Instead of using "fastboot boot" try this command instead:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot blablabla.img
Chromium_ said:
Instead of using "fastboot boot" try this command instead:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot blablabla.img
Click to expand...
Click to collapse
Holy hell. That worked. Is this documented anywhere? I've had similar issues where I cannot even fastboot the stock kernel on my Galaxy s4 Google Edition. Maybe it needs a similar fix?
Chromium_ said:
Yes you can use the fastboot boot command to temporarily go into twrp (instead of permanently flashing it) and flash the root zip. After you reboot twrp will be gone, and it will go back to stock recovery. Search up 'oode' on YouTube. He's got a video that shows you how to do this (on the n7, but the steps are essentially the same as for the n4...just different recovery file)
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks for this, I knew there would be some how to do this. Will try it here in a bit and see how it goes.
I just use CF Auto Root by Chainfire a few minutes ago to root. Pretty simple and fast.
Wow, this was so straight forward that I slapped myself afterwards.
It is literally just "fastboot boot twrp.img"
then you just flash the zip that you have on your nexus 4 and you win, worked very fast and easy.
Thank you very much, I will remember this when I go to do my Nexus 7.
Here is your unofficial TWRP
Please report all issues on my github so I can track them
Download the update!
Merged in TWRP 3.0.0.0
Fixed the time issue Bug in LG's kernel (however daylight savings time does not work when set on/off in recovery)
3.0.0.0
https://www.androidfilehost.com/?fid=24407100847293244
md5: f7c84c5328fb073a1a57fb75dc70191a
2.8.7.1
https://www.androidfilehost.com/?fid=24269982086988199
md5: 736456843ecaa2b65fbbb749008e1ff3
2.8.7.0
https://www.androidfilehost.com/?fid=24052804347853160
md5: f6d38b88b51d8cc39635534b559f719f
This requires you to have an unlocked bootloader which will wipe data if you have not unlocked already.
Recovery does take some time to boot It has taken up to 45 seconds for the TWRP curtain to show for me
To get to bootloader without adb:
Turn device off
Hold Vol Down
Insert USB plug while plugged into your PC
Hold Vol Down until fastboot pops up
Instructions:
If you have issues with adb or fastboot follow this post: HERE
If bootloader is unlocked:
reboot into bootloader
Code:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img
If your bootloader is locked:
enabled developer options
in developer options "Enable OEM unlock"
reboot into bootloader
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img
Known issues:
You get to see that it's not truly 2 displays
Time is not saved from Android to Recovery
Display does not turn off when it times out
TheJesus said:
I've messaged @KAsp3rd to include it in his OP.
ONLY PERFORM IF YOU HAVE ALREADY FLASHED TWRP AND CREATED AN EXTERNAL BACKUP!!!
1. Hold Volume Down
2. Hold Power button until you see LG screen
3. Release Power button and then rehold Power button
4. Follow on-screen prompts to perform a Factory Reset (If you have TWRP, this should not actually factory reset, but there has been one case of it doing it, that's why I suggest keeping a copy of your backup on your computer), may take a minute to boot into TWRP
5. Enjoy TWRP without fastboot
EDIT: On hold until verified on latest TWRP/more devices.
Click to expand...
Click to collapse
Device tree is here https://github.com/KAsp3rd/android_device_lge_h901
Compiled using omnirom 5.1 with 6.0 bootable/recovery
Get superSU from chainfire http://download.chainfire.eu/supersu
Thanks to @TheJesus @shabbypenguin @Dees_Troy @_that @bigbiff @helicopter88 @savoca @autoprime and anyone I've forgotten.
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
geeserver said:
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
Click to expand...
Click to collapse
I get the same thing
geeserver said:
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
Click to expand...
Click to collapse
Did you reboot to bootloader and fastboot flash recovery "img"?
re-read the op
adb reboot bootloader
then do the fastboot commands
KAsp3rd said:
Did you reboot to bootloader and fastboot flash recovery "img"?
Click to expand...
Click to collapse
Here are the commands
-In OS, Android with ADB Debugger on with UNLOCKED bootloader checked
{adb reboot bootloader}
-Welcome to Fastboot Mode:
{fastboot flash recovery twrp-2.8.7.0-h901.img}
{fastboot reboot}
-Phone back in Android
{adb reboot recovery}
NO TWRP
Right now I'm using stock.img files to restore everything and retrying.
I'm currently using Minimal ADB and Fastboot [8-28-15] to push commands.
geeserver said:
Here are the commands
-In OS, Android with ADB Debugger on with UNLOCKED bootloader checked
{adb reboot bootloader}
-Welcome to Fastboot Mode:
{fastboot flash recovery twrp-2.8.7.0-h901.img}
{fastboot reboot}
-Phone back in Android
{adb reboot recovery}
NO TWRP
Right now I'm using stock.img files to restore everything and retrying.
Click to expand...
Click to collapse
Flashing stock.img myself to make sure
same issues here also
Mine worked first try... I personally change the recovery img file's name to recovery.img, but other than that I use the same commands.
yeah, mine has the android open door with "no command" under it
KAsp3rd said:
Flashing stock.img myself to make sure
Click to expand...
Click to collapse
I can't push stock.img from fastboot. Reading from mickeyinid post in that thread, "Make sure you have the newest fastboot binary or it won't flash the system.img" It has a cap at 53MB but the filesize for system.img is 4.2GB.
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Didn't catch that one shabby thanks for pointing it out. I'll update op
this worked. Thanks!!
and thank you so much @KAsp3rd for this recovery
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Once I put in the fastboot boot twrp-2.8.7.0-h901.img command, I heard the computer disconnect and it took more like a minute or a minute in a half but it worked. Then I flashed SuperSU and now I'm ROOTED!!! Thanks!!!!
All rooted. Thank you @KAsp3rd!!
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
that worked. TWRP installed and rooted. FYI it does take a little time to boot into TWRP with the fastboot command and normal also.
Thanks for the help all
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Xposed
Can you flash xposed in this recovery?
huynh727 said:
Can you flash xposed in this recovery?
Click to expand...
Click to collapse
Yes. I have it. Use the arm64 for Lollipop version. It does however break the second screen occasionally (it FC's when I get/make a phone call, but that's it). BUT it has RootCloak which lets me use Android Pay while rooted
Success! The whole process was very easy and worked the first time! Thanks for posting this!
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!