Database Users

How to Root without flashing custom recovery

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.

[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required

[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required
Simplified procedures with LMY47M / LYZ28E now available as a factory image.
Hopefully this isn't blatantly obvious to everyone, it is a little different than the normal sideload procedure. Thought it might be useful to some who want to load 5.1.1 (and get Wifi calling with T-Mobile!) and not be forced to encrypt.
Requirements:
1. I'm assuming you have adb/fastboot working on your computer / connecting to your device and you understand a little bit about using adb / fastboot with an android phone.
2. Your phone cannot be encrypted, if you're encrypted already - this will not un-encrypt your data - you need to turn off forced encryption and format the "userdata" partition to disable the encryption.
3. You need to have an unlocked bootloader for this to work of course.
How to follow this procedure:
1. If you're on LMY47M (T-Mobile) and unencrypted, you can follow option 2, starting with Step 3 - only a small ~150MB download required.
2. If you're on anything other than LMY47M, you should use option 1 unless you have a desire to flash LMY47M and sideload LYZ28E.
I didn't do much here - except spent a bunch of time writing the procedure.
All Credit for tools / ideas goes to:
- efrant for his explanation of how to get OTA updates to work with TWRP ( http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919/page4 )
- hlxanthus for the NO FORCE ENCRYPT mod ( http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788 )
- Q9Nap and mhous33 for the LMY47M factory image ( http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 )
- bbedward and others for the original disable forced encryption boot.img ( http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715 )
- TeamWin - the TWRP Developer ( https://twrp.me/ )
——————————————————————————————————
OPTION 1 - Easy Method - Flash the LYZ28E factory image directly:
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Download LYZ28E for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lyz28e-factory-b542b88a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img (OPTIONAL - If you have TWRP or another alternative recovery you can skip this step)
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Restart the Bootloader, and flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the Bootloader again and then go to Recovery (TWRP). Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!
———————————————————————————————————————————————————
OPTION 2 - SIDELOAD Method (Makes sense if you’re already on LMY47M):
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Follow the normal procedure, if you're already on LMY47M you can skip to step 3. Download LMY47M for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lmy47m-factory-5228e84a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Now flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the bootloader, and enter recovery mode (TWRP). Once in TWRP, go to Advanced -> ADB Sideload. You may need to unplug/plug in the USB cable to your computer again.
Download my version of LYZ28E from here: https://www.androidfilehost.com/?fid=23991606952609905
Note: I modified this version to work with TWRP, it will not work with the stock recovery (because I modified it, the signature on the file is now invalid). The only thing I changed was I edited the updater-script to remove the release keys check which seems to fail on the stock recovery and doesn't work right with TWRP).
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
5. After it finishes, do not reboot yet. Go back and I recommend rebooting to recovery again. Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!

why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.

simms22 said:
why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.
Click to expand...
Click to collapse
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.

liqice said:
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.
Click to expand...
Click to collapse
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.

simms22 said:
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.
Click to expand...
Click to collapse
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?

Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.

cam30era said:
Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.
Click to expand...
Click to collapse
Thanks, updated the original post.

liqice said:
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?
Click to expand...
Click to collapse
easier/harder isnt an option here, since any way takes seconds. im just saying there are several options for this, thats all

liqice said:
Code:
fastboot flash f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
Click to expand...
Click to collapse
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?

So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?

Chahk said:
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?
Click to expand...
Click to collapse
Oops, you're right. Thanks!

Gage_Hero said:
So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?
Click to expand...
Click to collapse
This is where I was, LMY47E, rooted, unencrypted and with TWRP. I followed the entire procedure - went back to LRX22C using fastboot, then sideloaded LMY47M (T-Mobile version) - then flashed the no force encrypt boot.img - booted, after it finished booting, rebooted to the bootloader and so on ...
When you go to LRX22C you flash back to the stock recovery. So you need to boot into the stock recovery, pick "apply update from adb" and then run the adb sideload command from the PC.

Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?

With the factory images being posted, I just did the following:
Flashed the factory images
While still in bootloader, flashed TWRP
Rebooted into TWRP
Pushed SuperSU and the No_Force_encrypt to the /sdcard/ partition
Installed via TWRP
Profit.

lamenting said:
Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?
Click to expand...
Click to collapse
For LMY47D you need to get to LMY47M first, so you would follow the entire procedure, downgrade to LRX22C and then sideload LMY47M and so on.

Heavily updated the procedure since LMY47M and LYZ28E factory images are now available directly from Google.
Should be a lot easier and more straight forward now!

I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?

Boot loader and radio only...
So if I understand the instructions correctly, if you are still encrypted but rooted, from any Lollipop installation, fast boot flash the factory images... then flash TWRP ... root and done right? Then I have another question... the kernel I am running EX 1.07 along with Flar's app is running perfect for me.... any dangers in just flashing the boot loader and radio? I would like to wait on the system part until the kernel has been updated.....
Also, if I needed to do a restore, if I only flash the boot loader and radio have I pooched being able to go backwards to a nand backup?

FYI, step 3 in option one should read:
fastboot flash recovery twrp-2.8.6.0-shamu.img
vs
fastboot flash twrp-2.8.6.0-shamu.img

frater said:
I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?
Click to expand...
Click to collapse
Starting with Android Lollipop (5.0) and newer - at least on the Nexus 6 - encryption is turned on by default for the userdata partition.
You would - if you wanted to - backup all of the data on your userdata partition (e.g. Any pictures you've taken with the phone, etc - all of the data basically that shows up when you plug your phone into your computer).
Then you need to be running an OS that doesn't force encryption (for example if you follow my instructions) - this would also get you running 5.1.1.
After that you need to format your userdata - it wouldn't be encrypted at that point, and then copy your data back if you want to.
If you don't care about encryption, you can simply flash the factory 5.1.1 image following my instructions and skip the TWRP parts.

How do you keep up with the updates after rooting your P8?

Afaik you loose the OTA updates after rooting (because of twrp) so how do you keep your system up to date? or is this somthing that you risk in order to root your phone

You can try to flash the stock recovery back and install the firmware manually or using the updater, or you find the firmware in flashible zip format and flash it through twrp. I personally rooted without keeping Twrp so i can still update.

Thanks for answering! And yeah the problemas is that I cant find the firmware updates anywhere, so how do I root without a custom recovery? Can you tell me some hints to find the solution or a link? Thanks again
EDIT: Oh, just found a way, and in case someone is also wondering heres how its done: You have to boot to twrp through adb, and then you can flash super su without flashing the custom recovery . This is the generic way to do it, have not tested im my P8 yet, will report later.

fede011 said:
Thanks for answering! And yeah the problemas is that I cant find the firmware updates anywhere, so how do I root without a custom recovery? Can you tell me some hints to find the solution or a link? Thanks again
EDIT: Oh, just found a way, and in case someone is also wondering heres how its done: You have to boot to twrp through adb, and then you can flash super su without flashing the custom recovery . This is the generic way to do it, have not tested im my P8 yet, will report later.
Click to expand...
Click to collapse
*No need to go through all the hassle there is an automated script which i used it myself if you are still on stock recovery, it installs Twrp to flash superSu and then restores the original recovery.
http://forum.xda-developers.com/p8l...otloader-root-p8-p8lite-t3164956#post62851688
*If you are on Twrp, you can download "Huawei update extractor" http://forum.xda-developers.com/showthread.php?t=2433454 use it to extract your firmware (update.app) and take from it the 'recovery.img'. Then go to platform-tools where you open the CMD from, place the recovery.img in it you can rename it to "stockrecovery.img"
then "shift+right click" open the command line.
type: adb reboot bootloader
type: adb devices ----->to see your device
type: fastboot flash recovery 'type hear the name of recovery'
example: flastboot flash recovery stockrecovery.img
type: fastboot reboot ----->reboot device
some tutorial i found on youtube:
https://www.youtube.com/watch?v=YfWYKREeQeQ
By the way the method for Twrp i haven't tested but that's the theory, so please do it on your own risk and do the required research. Goodluck:good:
Edit: Another method in theory if you have Twrp could be to use 'flashify' app https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en to flash the stock 'recovery.img' which you extracted from the stock firmware. No need to use adb.

Rashad83 said:
*No need to go through all the hassle there is an automated script which i used it myself if you are still on stock recovery, it installs Twrp to flash superSu and then restores the original recovery.
http://forum.xda-developers.com/p8l...otloader-root-p8-p8lite-t3164956#post62851688
*If you are on Twrp, you can download "Huawei update extractor" http://forum.xda-developers.com/showthread.php?t=2433454 use it to extract your firmware (update.app) and take from it the 'recovery.img'. Then go to platform-tools where you open the CMD from, place the recovery.img in it you can rename it to "stockrecovery.img"
then "shift+right click" open the command line.
type: adb reboot bootloader
type: adb devices ----->to see your device
type: fastboot flash recovery 'type hear the name of recovery'
example: flastboot flash recovery stockrecovery.img
type: fastboot reboot ----->reboot device
some tutorial i found on youtube:
https://www.youtube.com/watch?v=YfWYKREeQeQ
By the way the method for Twrp i haven't tested but that's the theory, so please do it on your own risk and do the required research. Goodluck:good:
Edit: Another method in theory if you have Twrp could be to use 'flashify' app https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en to flash the stock 'recovery.img' which you extracted from the stock firmware. No need to use adb.
Click to expand...
Click to collapse
I still haven't changed the bootloader so it will be easier, I was waiting for the email from huawei but never received, but with the link you provided I was able to get the code instantly (since my model GRA-UL10 isn't on the list) its late here so will try it tomorrow. But I have a final question, will be possible to flash SuperSU without flashing twrp? There is a command that lets you boot twrp without flashing I just don't want to reflash my bootloader unnecessarily, thanks in advance. After this I will probably post a guide since it is not easy to find everything in one place.

fede011 said:
I still haven't changed the bootloader so it will be easier, I was waiting for the email from huawei but never received, but with the link you provided I was able to get the code instantly (since my model GRA-UL10 isn't on the list) its late here so will try it tomorrow. But I have a final question, will be possible to flash SuperSU without flashing twrp? There is a command that lets you boot twrp without flashing I just don't want to reflash my bootloader unnecessarily, thanks in advance. After this I will probably post a guide since it is not easy to find everything in one place.
Click to expand...
Click to collapse
In order to root your device you need a custom recovery which gives you the ability to push files which is not possible with the stock recovery that's how i understand it. The script in the link i gave u automates the steps you have to do manually, if you are going to root the device using the command line you will need a su.zip to flash using twrp, and a twrp recovery image through which you will access the file system, and finally knowing the command lines to do it all which is all in all is a hassle. So booting into or flashing twrp isn't really a big deal (at least for me) as long as you have the stock recovery by the end of it all.

[GUIDE] Root H815 v20e without installing TWRP

I've been trying for the last couple of days to root my MM G4 H815 v20e but all the guides I've tried to follow have either wanted TWRP installed before rooting, or root being required before installing TWRP. No matter which TWRP I tried, none would install. Yeah, the install would succeed ok, but when I tried rebooting into recovery all I got was the dead robot. Then I came across a method for running TWRP as a boot img and installing root from there. And it worked 100%, first time. So I'm putting this method on here so anyone else having the same problems as I had, can root their phone.
This is non-destructive but, as usual, I take no responsibility for you wandering from the path and breaking something. You will need an unlocked bootloader, instructions here, and your warranty will most definitely be invalidated after this. The original instructions were in Turkish, so many thanks to the original poster, and to Google Translate for at least making it understandable.
So I take it we're all sure what we're doing with adb, fastboot etc? This is serious stuff so if you don't think you're up to it, don't try it until you are. I'm just posting the method for rooting, the other stuff can be easily found. Plus it helps you understand the system of searching.
So when you're ready, connect your phone to your pc by USB cable, ensure USB Debugging is enabled, and off we go:
Step 1 - Visit https://dl.twrp.me/h815/ and download twrp-3.0.2-0-h815.img to your sdk/platform-tools folder. Rename it to "twrp.img". Copy this file to either the root of your internal memory or external sd card.
Step 2 - download SU zip from here https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip and rename it to "su.zip". Copy it to either the root of your phone's internal memory or sd card
Step 3 - switch to your sdk/platform-tools folder, shift and right-click on a white space and select "Open command window here"
Step 4 - type "adb reboot bootloader" [ENTER] then type "fastboot boot twrp.img" [ENTER]
TWRP will now run in memory
Step 5 - As TWRP isn't actually installed, you'll need to swipe the switch at the bottom to allow it to modify your phone
Step 6 - Tap Install and select su.zip. Select "Zip signature verification".
Step 7 - Swipe the switch at the bottom to flash the zip.
Step 8 - It would be a good idea at this point to also flash the TWRP. go back to the install screen. As it is an img file and not a zip you want to flash, tap the "Install Image" button at the bottom right, choose the twrp.img file you copied to the phone, and swipe to flash.
When complete, tap the Reboot button, choose Recovery and your phone should now boot into TWRP. Now choose to reboot to System and allow your phone to restart (it may take a while longer than normal and may reboot , mine did once).
And that's your phone rooted. Install Root Checker from the Play Store and run it to confirm your phone has been rooted.

Unlocked bootloader, I guess, yes?

cesedy said:
Unlocked bootloader, I guess, yes?
Click to expand...
Click to collapse
Without unlocking the bootloader he wouldn't be even able to boot the twrp img, since its unsigned by LG!

This is common sense
If I unlock the bootloader I´ll also fire up the twrp (not boot but simply flash twrp)
Root is just optional there

U rock man!!!
100% working!!!! i've been looking for this for so long and all tutorials were complicated and hard to follow and you came with this simple tutotial xD i have the same lg g4 h815 20e. You are the real MVP!!!:highfive:

But why? Why wouldn't you just install TWRP seeing as you've unlocked the bootloader, might as well make your life easier in the long run...
adb reboot bootloader
fastboot boot twrp.img
copy twrp.img to internal storage
in twrp -> install -> images -> twrp.img -> select recovery and swipe to install
Can't install TWRP via fastboot (fastboot flash recovery twrp.img doesn't work properly, have to flash the twrp.img inside TWRP itself).

dontpannic said:
But why? Why wouldn't you just install TWRP seeing as you've unlocked the bootloader, might as well make your life easier in the long run...
adb reboot bootloader
fastboot boot twrp.img
copy twrp.img to internal storage
in twrp -> install -> images -> twrp.img -> select recovery and swipe to install
Can't install TWRP via fastboot (fastboot flash recovery twrp.img doesn't work properly, have to flash the twrp.img inside TWRP itself).
Click to expand...
Click to collapse
Exactly, makes no sense
Sent from my LG-H815 using Tapatalk

Will it work on LG G4 H815 V10d ? anyone tried it ? I hate it not having root, thats the first phone i have so many problems rooting it...
already unlocked my bootloader...
thanks...

snail22 said:
Will it work on LG G4 H815 V10d ? anyone tried it ? I hate it not having root, thats the first phone i have so many problems rooting it...
already unlocked my bootloader...
thanks...
Click to expand...
Click to collapse
Since you have unlocked bootloader anything will work
you can simply boot the twrp (like the op shows) and flash supersu
or rather -> copy twrp img to the internal, boot twrp (look op) and flash the twrp img (tap first the zip/img checkbox) --it will ask where to flash -> select recovery, don´t tap boot...
Then you might also flash the supersu
and now you have twrp and root

bender_007 said:
or rather -> copy twrp img to the internal, boot twrp (look op) and flash the twrp img (tap first the zip/img checkbox) --it will ask where to flash -> select recovery, don´t tap boot...
Then you might also flash the supersu
and now you have twrp and root
Click to expand...
Click to collapse
Great, This looks like what I want, will try in the evening, if this work, I will be able to use TASKER AGAIN !! hooray :laugh:

The problem with the boot loop is only in the devices that are bootloader unlocked ? My H815 (506) is locked...and i was thinking at unlock the bootloader, but, i am "afraid" of the boot loop.

No, it's random
Sent from my LG-H815 using Tapatalk

Its because of a hardware problem, isnt?
Sent from my LG-H815 using XDA-Developers mobile app

Exactly, we have a poll about it but I see sone 505, 506 users wanted to re-vote because their phones died. :/
Sent from my LG-H815 using Tapatalk

Did work h815 TWN ? I need to root or unlock bootloader. Help me pl0x

Hey,
I have H815 6.0 with locked bootloader v20e
will this work for me? or i have to unlock the bootloader first? i just want root

can i use this method for v20d? thx.

After typing "adb reboot bootloader" phone restarts to bootloader. And thats it. Typing "fastboot boot twrp.img" does nothing but writes <...> is not recognized as and internal or external command, operable program or batch file. Whats going on? Also if i type adb devices there is empty list of devices attached

xyster13 said:
After typing "adb reboot bootloader" phone restarts to bootloader. And thats it. Typing "fastboot boot twrp.img" does nothing but writes <...> is not recognized as and internal or external command, operable program or batch file. Whats going on? Also if i type adb devices there is empty list of devices attached
Click to expand...
Click to collapse
You don't have fastboot installed, or you're typing the command wrong.
c:> adb reboot bootloader
c:> fastboot boot twrp.img

What happens if I want to go back to stock, will the device remain as it was before rooting and will receive OTAs and allow device encryption and all?

Flashable Recovery?

Hello, I know our great device does not have a recovery partition, so we need to use fastboot to boot TWRP. But muy question is, is there no way to boot into TWRP without a computer? Maybe a terminal command from Android itself, or a little script that we can run when needed? This might be a noob question, but I'm sure many here could profit from a positive answer.
Thanks

Angelelz said:
Hello, I know our great device does not have a recovery partition, so we need to use fastboot to boot TWRP. But muy question is, is there no way to boot into TWRP without a computer? Maybe a terminal command from Android itself, or a little script that we can run when needed? This might be a noob question, but I'm sure many here could profit from a positive answer.
Thanks
Click to expand...
Click to collapse
Assuming youre rooted... Ive used the reboot app on my phone. I have a 1926-7 Moto G6 Plus. It will boot to fastboot, fast reboot, recovery, reboot system etc. Look around xda and see if someone has a good reboot app or else use GP. I actually had twrp flashed permanently to my phone but it would not back up so I have to redo it. Also the phones data was encrypted and I didnt know how to fix it. I hope that you are able to find something that works for you

You can boot into TWRP via terminal command without using a computer. Use the 'dd' command ( 'dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.backup.img' ) to take a backup of your boot.img. Than use 'dd' to overwrite boot with twrp and reboot to recovery (dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/boot)
Later to boot your phone as normal you only have to install your boot.img backup via TWRP.

now we can install a TWRP 3.3.0 ONLY ON DECRYPTED ROMS (the lastest Havoc, Resurrection Remix, AEX, Decendant, PixyOS are unencripted by default) for flashing magisk modules or mods but it will be overwrite when we flash/update our custom/stock rom:
https://drive.google.com/open?id=1CqzvBiEfk9xucXG8UemNZMhBxDCeSV0i
How to install it:
Put the donwloaded TWRP on your plataform tools folder and in your internal/sd storage.
Boot the same TWRP (fastboot boot TWRP.img)
Go to ADVANCED and select Install Ramdisk Recovery
Check backup boot box( in case something goes wrong just restore your boot partition)
Swipe and wait until finish.
Reboot
If every reboot finishes in twrp booting just flash magisk and youll be able to boot into system.