[GUIDE] Root H815 v20e without installing TWRP - G4 General

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?

Related

Help rerooting after 4.3

My wife has a rooted nexus 7 2012 wifi and she unintentionally accepted the ota Android 4.3 update. So of course it unrooted her.
I originally had a hell of a time rooting this tablet using wugfresh nexus toolkit. Took me several days to succeed and the same thing is happening again. My Windows 7 laptop keeps installing the wrong drivers even though I selected the option to disable the auto driver configuration. Also USBDeview never shows the installed Samsung adb drivers yet when I try to install them I am warned they are already installed. It's already been hours and who knows how many retries and reboots!
So even though I'm a newbie I decided to go the Android sdk route.
1. Where do I download the files I need to just root the darn tablet?
2. What do I do next?
Please keep it simple........
Anyone want to walk me through it on the phone?
Thanks
If you are new to using SDK, check this out for a well laid out tut on how to get set up and rooted.
I now have android sdk set up.
What are the commands I should issue to root?
Thanks
now you need to flash a custom recovery then flash a root zip file via windows command prompt...Have you figured out how to interface with your device and the windows command prompt? eg;
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
-then you would issue "adb reboot bootloader"
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
-then while in bootloader toggle with the volume keys to "recovery" option and press power
-now you will be in your new recovery you just flashed and you can push the zipped root file you chose to the sdcard, "adb push rootyouchose.zip /sdcard/"
-once its been pushed you can flash it in recovery and reboot, and you are now rooted
-this is the latest cwm recovery that you could flash in fastboot as described above
-this would be the root file you want to push then flash in recovery
-this may be of some help, scroll down halfway
Thank you so much for helping. You can't know how much it is appreciated.
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
Got that. It works!!
-then you would issue "adb reboot bootloader"
Worked! Got the Android on his back.
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
Is recovery image on my pc or the tablet?
Why do I have to indicate the img name here if I will later select it
When I write
Fastboot flash......... Img
I get
Unknown partition 'the image file name'
"error : cannot determine image filename for. '.......'
You need to have downloaded a recovery image, that is what you flash I linked to one on my last post, that file is called "recovery-clockwork-touch-6.0.4.3-grouper.img" so you would issue,
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
"fastboot flash recovery" is telling it to flash a recovery file and "recovery-clockwork-touch-6.0.4.3-grouper.img" is the recovery file in this case to be flashed so, combined its, "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img"
I do not use Windows, I use a terminal instead of windows command prompt so I can't be specific as I am not too familiar with windows command prompt. With terminal it is much easier in my opinion but you need to be running nix or Mac OS to have a terminal
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Anderson2 said:
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Click to expand...
Click to collapse
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
GedBlake said:
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
Click to expand...
Click to collapse
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Anderson2 said:
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Click to expand...
Click to collapse
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it.
...but I assume your Nexus 7's bootloader is already unlocked, given it's been rooted once before.
And so swiftly skipping forward to step 2...
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
GedBlake said:
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it. I assume your bootloader is already unlocked.
So swiftly skipping forward to step 2....
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Anderson2 said:
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Click to expand...
Click to collapse
Hello again, Anderson2...
Well, you sort of are already doing something in return.... you're asking questions.
Questions that require answers. Those answers, whoever posts them, may be of assistance to somebody else. Somebody else looking for a solution to a similar problem.
I always look upon these forums as a means of sharing. Not everybody can know everything. God knows, I don't know everything.... and I've been messing around with Android for three years now. So don't worry so much about it being a quid pro quo sort of arrangement.
I know what I know primarily as a result of my own experiences and what I've learned here from the many (in most cases, more knowledgeable) posters here on XDA. What you learn today, you can pass on to others, tomorrow (metaphorically speaking). We, all of us, stand on the shoulders of each other.
With regard to the second generation Nexus 7 (2013)... I'm afraid I really don't know much about it... but I'd be surprised if rooting it deviated significantly from rooting the first generation Nexus 7....
Namely...
1). Unlock the bootloader.
2). Flash a Custom Recovery.
3). Using that Custom Recovery, flash some SU root package... probably from Chainfire.
Anyway, I've found this tutorial here...
http://forum.xda-developers.com/showthread.php?t=2382051
...and it appears to follow a very similar template.
The Nexus 7 (2013) forum itself, which is also worth visiting, is located here....
http://forum.xda-developers.com/nexus-7-2013
Rgrds,
Ged.

[HOW TO] How to Root 5.1 with (unlocked bootloader)

I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link) UPDATE: There is an issue with TWRP 2.8.7.0 (SEE THIS POST Thanks @jodaboda ). Please use TWRP 2.8.6.0 for now!
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
EDIT: 9-17-2015 edited first TWRP link.
KidJoe said:
I've seen posts requesting "how to" and posts of problems attempting to root after installing the 5.1 OTA update. This post outlines the steps to root with an UNLOCKED BOOTLOADER.
NOTE: This will only work if your bootloader is already unlocked. It is based on -> http://forum.xda-developers.com/moto-x/moto-x-qa/instructions-unlocking-rooting-dev-ed-t2649738 but slightly updated.
Don't know if your bootloader can be unlocked? see -> HERE
Requirements...
the latest TWRP fastboot IMG file (Alternate Link)
the latest Installable ZIP of SuperSU (Alternate: http://download.chainfire.eu/supersu )
You must have already installed the Motorola Drivers, ADB, Android Platform Tools, and mFastboot
mFastboot (get from the previous link). NOTE: Stock fastboot that ships with the Android SDK/Platform tools will likely work, but Moto's fastboot is always suggested!
Your battery has an 80% or greater charge!!
MicroUSB Cable.
Know how to start your phone into the Fastboot AP/Bootloader mode...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in Fastboot AP menu on phone.
The steps...
NOTE: replace TWRP.IMG in the below steps, with the name of the file you downloaded!! Example: twrp-2.8.6.0-ghost.img
NOTE: failure to perform these steps EXACTLY as written can result in the apparence of the Android in distress (logo with Exclamation mark) with the caption "No Command" and the inability to enter recovery, OR it will enter STOCK recovery even though you have flashed TWRP!
Start the phone in Fastboot AP mode.
Connect your phone to PC via MicroUSB cable.
open a command prompt and change to the folder you downloaded your TWRP.IMG file.
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery TWRP.img
mfastboot reboot-bootloader
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device should enter TWRP.
If your device is not rooted, TWRP may prompt you to root now or install SuperSU. Do it.
Use the menu options to Reboot to system.
You will likely be prompted to UPDATE SuperSU. Please update it, and reboot.
IF TWRP doesn't prompt you to root/install SuperSU.... (more exact instructions coming later...)
With your phone booted normally, connect it via USB cable to your PC.
Drag/Drop the SuperSU.zip you downloaded onto the phone's internal storage
Reboot the phone into TWRP
Use the menu option to install zip, navigate to and select the SuperSU zip.
Boot to System.
Click to expand...
Click to collapse
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Do you know where I can find mfastboot for Mac OSX?
kidjoe, your a priceless resource!
i installed an older verison of twrp and had all the issues you speak off, installed 2.8.6 with success but would not root upon reboot, installed the super su zip in op via twrp, one last thing i had to enter the super su app and tap enable superuser and now all is good:good::good
Thanks, worked like a charm
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Vampirexox said:
I still haven't unlocked my Bootloader (being on 5.1). In the linked post it's been mentioned that "TWRP custom recovery for KitKat" - my question is, is there a TWRP Custom Recover for OTA 5.1 update? And I'm on XT1052, same procedure follows?
Click to expand...
Click to collapse
twrp-2.8.6.0-ghost.img works on Lollipop too. (just used it last night on my sister-in-law's GSM Dev Edition XT1053 that got the lollipop update)
jay_em said:
Do you know where I can find mfastboot for Mac OSX?
Click to expand...
Click to collapse
Here is a copy on my Box 'drive':
https://app.box.com/s/5nlgy2avccupw4box8z2be50ezt4qn7p
EDIT: I just got an e-mail saying it had been downloaded. :good:
---------- Post added at 08:54 AM ---------- Previous post was at 08:45 AM ----------
kyzn said:
Thanks.. It's been ages since I used I last used adb commands and flashed something. I couldn't figure out how to boot into recovery.
Click to expand...
Click to collapse
EDIT: [If you are still running the stock Recovery] You can also use:
Code:
adb reboot recovery
When you see the horizontal robot hold the Volume Up key for 3 seconds and then tap Power and the Recovery Menu will display.
Thanx for this how-to. Everyone has been getting confused in root process for 5.1 although it is nearly same as 4.4.4.
Sent from my XT1052
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
I had the same issue with my XT1053. Following your advice did the trick. Not being able to modify my dpi since upgrading has been killing me. Its the only thing i really want root for. Thanks for everything both you and op!
jodaboda said:
I had to use twrp-2.8.6.0-ghost.img
twrp 2.8.7 would not "see" the SD card, and I couldn't install the SuperSU.zip
Thanks for the post!
Click to expand...
Click to collapse
Ahh... 2.8.7 wasn't out when I tried.. 2.8.6 was the latest at that time. Maybe there is a bug in 2.8.7 that will get fixed in future versions?
Sunshine unlocked bootloader
Does anyone know if there are any issues resulting from a Sunshine unlocked bootloader? I saw one post that had a warning but it was a warning because there was no information at the time. Has this change?
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
md07 said:
i installed TWRP successful, but after normal reset, TWRP is gone, it's only stock recovery (Android down image). Please help me. My phone is running 5.1 update OTA, unlocked bootloader
Click to expand...
Click to collapse
When you say "installed TWRP successful"... do you mean that fastboot didn't error? or that fastboot completed the install, you did a mfastboot reboot-bootloader, and tried entering TWRP but it still gave you the "dead android" image?
Is there any unofficial way to unlock bootloader?
Sent from my Nexus 7 using Tapatalk
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
djibril13 said:
Is there any unofficial way to unlock bootloader?
Click to expand...
Click to collapse
Sunshine... IF you're phone has never been upgraded to 4.4.4.
BUT if you can get unlock code from Moto, while it can void your warranty (depending on your local laws), that is FREE, and the best way.
SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
help me understand your situation...
You are doing.. Mfastboot flash recovery -> mfastboot reboot-bootloader -> you get battery charging screen rather than fasboot/bootloader menu/screen?
or ??
SX86 said:
I can't get it to work on a friend's Moto X... I flash using mfastboot and upon rebooting, it goes into battery charging mode.
If I fully boot into Android, then reboot to recovery, I still get the "dead Android on his back" recovery. What's going on?!
Click to expand...
Click to collapse
after flashing did you but to recovery befour booting system? with my experience i had to boot to recovery first befour system

[Root] Zenfone 2 Official Android 6.0 Root + Xposed and Downgrade

**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. This is a systemless root. Yet you need to unlook Lollipop before upgrading to Marshmallow.
3. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Unlock your device in Lollipop, then upgrade to Android 6.0
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. This TWRP is recommended.
HTML:
adb reboot-bootloader
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Unroot:
Just flash back stock boot.img
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade to Lollipop:
In case you need to downgrade to Lollipop, follow the instructions with care. Do it at your risk.
Refer to Asus Zentalk Forum and grab the required files from there.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Now you are back in Lollipop. You can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!
It worked!Thank you master!I bow now....
I just need root on 6.0.1. Is this going to achieve that?
MikeyLee said:
I just need root on 6.0.1. Is this going to achieve that?
Click to expand...
Click to collapse
According to op it will
Sent from my ASUS_Z00AD using Tapatalk
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
pokey006 said:
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
Click to expand...
Click to collapse
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
samcjtsai said:
1. All credits go to @shakalaca and I just try to recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum but, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Works like a charm !! Thanks !!
kamyk70 said:
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
Click to expand...
Click to collapse
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
when update to 6.0. bootloader unlocked again ! how can i flash twrp ?
pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
No it does not
Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thank You for explaining that to me, appreciated!
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
euthic said:
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
Click to expand...
Click to collapse
You need to adb sideload all LP .184 images first then use Asus FlashTool to flash RAW Firmware.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
root works perfect along with systemless xposed, but i still cant pass safenet check..(super su disabled, and also xposed) so no AP.. is that normal ?
pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
ponhei9502 said:
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
Click to expand...
Click to collapse
Guess your ZF2 is not unlocked in LP first, so that you can't see twrp booting. Since you are in Android 6.0 now, try to downgrade to LP, Unlock it, upgrade to 6.0 and then root.
samcjtsai said:
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca and I just recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Where are these files again? They aren't in the zip
thanks, works great, was able to downgrade to lollipop with no problem what so ever. Install twrp, gain root again, and rockin custom roms...

How to flash TWRP and Root Moto X Style on Marshmallow

I am using moto x style and unlocked bootloader with 'Windroid Universal Android Toolkit' v2.5 but cannot flash TWRP and root this apl. Today I tried flash TWRP and then root but after showing 'Congratulation' pop up,my phone stucked on 'No command' page. I tried twice and same result. Later i check there is either no TWRP or root by SuperSU. And i see youtube video and and read many XDA forum and comments and most of the users says the phone stuck on M logo page when reboot after the root process. And all says its a issue with Marshmallow. And most of the xda posts and youtube video are made during 5.1.1 so there is no problem in that video during flash TWRP and root. So i need a seamless process to flash TWRP and root on Marshmallow so that it doesnot stuck on M logo. And I dont want to downgrade to L for root. And unluckily if it stuck M logo thwn what to do to go back to home screen?Thank you.
http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958
Look in my sig...
It's in my signature... There are multiple links to what your looking for and other threads, if you are on computer they should be immediately below the message, if you're in the XDA app you have to look in the user profile (don't think it's possible in Tapatalk though).
http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958
acejavelin said:
It's in my signature... There are multiple links to what your looking for and other threads, if you are on computer they should be immediately below the message, if you're in the XDA app you have to look in the user profile (don't think it's possible in Tapatalk though).
http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958
Click to expand...
Click to collapse
My build no is 24.49-18-4. So is this process suitable for this build no? And still i dont flash TWRP. I tried with "Windroid Universal Android Toolkit app" to flash TWRP. though it showed a 'Successful' pop up but it didn't. Can I go with any old process to flash TWRP or u have a new process?
Atanu Mukherjee said:
My build no is 24.49-18-4. So is this process suitable for this build no? And still i dont flash TWRP. I tried with "Windroid Universal Android Toolkit app" to flash TWRP. though it showed a 'Successful' pop up but it didn't. Can I go with any old process to flash TWRP or u have a new process?
Click to expand...
Click to collapse
Step 1 - Stop using toolkits! They rarely work right on modern Android devices. With the Moto the only safe, reliable way to root is manually.
I don't know what the 'old way' is to flash TWRP your referring to here... I recommend one time booting twrp with "fastboot boot twrp.img" command (replace twrp.img with your actual twrp image file) then perform a backup to the SD card or USB OTG device and put it away for safe keeping. Then flash twrp either with twrp you have booted, or manually with "fastboot flash recovery twrp.img"
The rooting method I linked before is valid for all Marshmallow builds, if you have Lollipop or Nougat you need to find a different method.
acejavelin said:
Step 1 - Stop using toolkits! They rarely work right on modern Android devices. With the Moto the only safe, reliable way to root is manually.
I don't know what the 'old way' is to flash TWRP your referring to here... I recommend one time booting twrp with "fastboot boot twrp.img" command (replace twrp.img with your actual twrp image file) then perform a backup to the SD card or USB OTG device and put it away for safe keeping. Then flash twrp either with twrp you have booted, or manually with "fastboot flash recovery twrp.img"
The rooting method I linked before is valid for all Marshmallow builds, if you have Lollipop or Nougat you need to find a different method.
Click to expand...
Click to collapse
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I am saying about this official method which is on twrp.me site. And after typing 'fastboot reboot' what I have to do to go home page? Sorry to ask u so many things. Actually I am totally new in this thing and very much worry after facing issues 2-3 times. And thank u very much for fast reply.
One more ques, I have unlocked bootloader with that "Windroid Universal Android Toolkit". Now in fastboot it shows 'bootloader unlocked,code 3' is that ok? As u say toolkit doesnot work on modern devices.
Atanu Mukherjee said:
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I am saying about this official method which is on twrp.me site. And after typing 'fastboot reboot' what I have to do to go home page? Sorry to ask u so many things. Actually I am totally new in this thing and very much worry after facing issues 2-3 times. And thank u very much for fast reply.
One more ques, I have unlocked bootloader with that "Windroid Universal Android Toolkit". Now in fastboot it shows 'bootloader unlocked,code 3' is that ok? As u say toolkit doesnot work on modern devices.
Click to expand...
Click to collapse
So Moto is a tad different... After you flash recovery, do not reboot with fastboot, instead use the Vol Dn key select Recovery and press Power to start it. When the splash screen comes up, allow changes to system, then I the TWRP main menu select Reboot - Recovery, the device will start TWRP again and it should be "locked" in. From there perform the rooting.
acejavelin said:
So Moto is a tad different... After you flash recovery, do not reboot with fastboot, instead use the Vol Dn key select Recovery and press Power to start it. When the splash screen comes up, allow changes to system, then I the TWRP main menu select Reboot - Recovery, the device will start TWRP again and it should be "locked" in. From there perform the rooting.
Click to expand...
Click to collapse
That mean after typing fastboot flash recovery twrp.img press enter and then i can plug off the usb keeping my device on fastboot then changes to recovery and do the rest?
Btw suppose if i dont want to root it at that time,then what i do? I mean just after flash recovery how to go to home screen without rooting?
And when i want to perform root process later,after installing SuperSU zip if I press power button and vol down then may I go to twrp recovery or ph stock recovery?
Atanu Mukherjee said:
That mean after typing fastboot flash recovery twrp.img press enter and then i can plug off the usb keeping my device on fastboot then changes to recovery and do the rest?
Btw suppose if i dont want to root it at that time,then what i do? I mean just after flash recovery how to go to home screen without rooting?
And when i want to perform root process later,after installing SuperSU zip if I press power button and vol down then may I go to twrp recovery or ph stock recovery?
Click to expand...
Click to collapse
OK... I'm confused, why are you unlocking and installing twrp if your not going root or flash a custom ROM?
acejavelin said:
OK... I'm confused, why are you unlocking and installing twrp if your not going root or flash a custom ROM?
Click to expand...
Click to collapse
I will definately do so. I also want to use CM14.1 but i want to do so step by step. Actually after facing issues 2-3 times i am little bit worry now. That is true. So hesitate to perform both at a single time.
Atanu Mukherjee said:
I will definately do so. I also want to use CM14.1 but i want to do so step by step. Actually after facing issues 2-3 times i am little bit worry now. That is true. So hesitate to perform both at a single time.
Click to expand...
Click to collapse
You don't need to root if your going CM, flash TWRP, backup, and flash CM. You don't need to over complicate it.
If you boot (not flash) TWRP and backup then get a copy to safe place there is little risk of anything going wrong.
acejavelin said:
You don't need to root if your going CM, flash TWRP, backup, and flash CM. You don't need to over complicate it.
If you boot (not flash) TWRP and backup then get a copy to safe place there is little risk of anything going wrong.
Click to expand...
Click to collapse
Ok. But is there any regular chance of going wrong during flash TWRP or flash CM? I backed up all internal important data to external sd card and when I perform these process I just remove that sd from phone.
You pls tell me how to go to home screen after flashing TWRP?
And if I need to root it later then also what to do then? I mean if then I press power and vol minus then will I get TWRP recovery to root it or it will be redirectred to phone custom recovery?
Atanu Mukherjee said:
Ok. But is there any regular chance of going wrong during flash TWRP or flash CM? I backed up all internal important data to external sd card and when I perform these process I just remove that sd from phone.
You pls tell me how to go to home screen after flashing TWRP?
And if I need to root it later then also what to do then? I mean if then I press power and vol minus then will I get TWRP recovery to root it or it will be redirectred to phone custom recovery?
Click to expand...
Click to collapse
There is always a chance of something going wrong, no one can guarantee everything will be fine. We have had people do everything perfectly but something happens and it's bricked... It's rare but does happen.
After you flash TWRP in the bootloader, press Vol Dn until it says Recovery and press power to start it, after several seconds you will get a screen that will ask if it can write to system, select yes, the next screen will be the TWRP home screen.
Once you flash TWRP, your stock recovery is gone, but you access it the same way... Power off, press and hold PWR+Vol Dn and in the bootloader menu select Recovery and press power.
acejavelin said:
There is always a chance of something going wrong, no one can guarantee everything will be fine. We have had people do everything perfectly but something happens and it's bricked... It's rare but does happen.
After you flash TWRP in the bootloader, press Vol Dn until it says Recovery and press power to start it, after several seconds you will get a screen that will ask if it can write to system, select yes, the next screen will be the TWRP home screen.
Once you flash TWRP, your stock recovery is gone, but you access it the same way... Power off, press and hold PWR+Vol Dn and in the bootloader menu select Recovery and press power.
Click to expand...
Click to collapse
Thank you very much for your kind guidance and quick reply. I will perform this may be tomorrow and then inform you. If it is bricked or stucked in any stage/page then is there any instant process to go back to safety?
acejavelin said:
There is always a chance of something going wrong, no one can guarantee everything will be fine. We have had people do everything perfectly but something happens and it's bricked... It's rare but does happen.
After you flash TWRP in the bootloader, press Vol Dn until it says Recovery and press power to start it, after several seconds you will get a screen that will ask if it can write to system, select yes, the next screen will be the TWRP home screen.
Once you flash TWRP, your stock recovery is gone, but you access it the same way... Power off, press and hold PWR+Vol Dn and in the bootloader menu select Recovery and press power.
Click to expand...
Click to collapse
I am listing here only the commands,u just tell me is this ok?
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot boot twrp.img
Will these commands directly take me to twrp page?
And here I put a pic of the twrp page. If I dont want to root it then what to do? Click reboot option or anything else to do?
Atanu Mukherjee said:
I am listing here only the commands,u just tell me is this ok?
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery twrp.img
fastboot boot twrp.img
Will these commands directly take me to twrp page?
And here I put a pic of the twrp page. If I dont want to root it then what to do? Click reboot option or anything else to do?
Click to expand...
Click to collapse
Your last two are redundant, either flash or boot, you don't have to do both, but each has a purpose... Flash is permanent, boot is transient and will disappear on a reboot.
Boot TWRP first, the first time it will not take you to the main page initially but show you a notification page asking if you want allow it to make changes to the system or keep it read-only, this time only do not allow changes... Then the main screen of TWRP will be displayed and you should do a full backup of all partitions to the SD card.
Flash will just write the recovery partition, it doesn't start anything, you select recovery from the fastboot menu to start it.
acejavelin said:
Your last two are redundant, either flash or boot, you don't have to do both, but each has a purpose... Flash is permanent, boot is transient and will disappear on a reboot.
Boot TWRP first, the first time it will not take you to the main page initially but show you a notification page asking if you want allow it to make changes to the system or keep it read-only, this time only do not allow changes... Then the main screen of TWRP will be displayed and you should do a full backup of all partitions to the SD card.
Flash will just write the recovery partition, it doesn't start anything, you select recovery from the fastboot menu to start it.
Click to expand...
Click to collapse
So after "fastboot boot twrp.img" i have to allow to make changes and have to do a nandroid backup. After that will I get option to "Reboot?"
And later when I went to recovery I will get twrp page instead of stock recovery? 1st I think I should flash cm13 then root then upgrade to 14.1 bcz still a feel little worry to root it on stock rom.
Atanu Mukherjee said:
So after "fastboot boot twrp.img" i have to allow to make changes and have to do a nandroid backup. After that will I get option to "Reboot?"
And later when I went to recovery I will get twrp page instead of stock recovery? 1st I think I should flash cm13 then root then upgrade to 14.1 bcz still a feel little worry to root it on stock rom.
Click to expand...
Click to collapse
No, almost every part of what your saying is wrong...
Boot twrp and do not allow changes first time and backup. This will give a clean backup to restore from if things go badly.
After this is complete, in TWRP go to Reboot menu and select Bootloader, flash TWRP, do not reboot but use the bootloader menu to start TWRP. This time allow it to make changes to system. At the main menu if twrp go to Reboot - Recovery the device will restart and TWRP will load automatically, this step will lock in twrp so the stock OS doesn't replace it.
You only need to root stock rom, you don't need to root CM roms as they are already rooted (there are a few roms that are not pre-rooted but they are rare and none of the ones your talking about). As far as CM 13 vs 14.1 I can't really help you but from I've read both are stable enough for a daily driver device.
acejavelin said:
No, almost every part of what your saying is wrong...
Boot twrp and do not allow changes first time and backup. This will give a clean backup to restore from if things go badly.
After this is complete, in TWRP go to Reboot menu and select Bootloader, flash TWRP, do not reboot but use the bootloader menu to start TWRP. This time allow it to make changes to system. At the main menu if twrp go to Reboot - Recovery the device will restart and TWRP will load automatically, this step will lock in twrp so the stock OS doesn't replace it.
You only need to root stock rom, you don't need to root CM roms as they are already rooted (there are a few roms that are not pre-rooted but they are rare and none of the ones your talking about). As far as CM 13 vs 14.1 I can't really help you but from I've read both are stable enough for a daily driver device.
Click to expand...
Click to collapse
After typing 'fastboot flash recovery twrp.img' i switch to recovery and select it. But it shows recovery failed,bla bla in red colour. I tried 3 times but same result. What to do? now again when I go to the recovery,i see still it is the stock recovery.

Unable to install TWRP

Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
gibawatts said:
Hey guys, I'm at a lost here. I don't think I'm that stupid but I am following all steps from the guides to install TWRP without luck. I already managed to unlock my bootloader with Axon7Toolkit. I already certified that QUSB_Bulk driver is installed, I did it with Zadig, but when in EDL mode, even after killing adb, the axon7tool can't find it. I tried installing a zip with the toolkit but when I choose the package, the toolkit simply closes. Is that me? My phone?
Thank you!
Click to expand...
Click to collapse
What software version are you on?
I was at latest nougat but I downgraded to B10
Doing it via fastboot never fails for me.
Get to fastboot put two img in adb folder (I rename it for ease of typing since I suck) rename to recovery.img
Type this cmd in adb
Fastboot flash recovery recovery.img
Reboot to recovery and root. Done deal
download 3.1.0.0 twrp into your download folder on your desktop enter fastboot into your phone open up your command prmt type fastboot devices, your phone should appear then type fastboot flash recovery then go to the twrp right click drag it into the command prmt air page and place it there. you should see the file then hit enter. It'll take like 5 seconds it's really fast then reboot t recovery. when in twrp it'll ask you to install it again say no and uncheck the to options. DONE.
After loads of stress and bangs on the table I managed to unlock, install TWRP, LOS and root. I removed every driver related to my cell phone, deleted everything I download from it and started from scratch. I installed TWRP via fastboot but wasn't able to enter recovery mode, than I mase the stupidity to lock the bootloader back and got stuck in that password screen. Then I gave another go with the toolkit, unlocked it again and, I don't know how or why, it finally booted TWRP. Now everything is OK. Glad to be back to "Nexus mode" after so many time.
Thank you!

Categories

Resources