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
Related
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
Here is your unofficial TWRP
Please report all issues on my github so I can track them
Download the update!
Merged in TWRP 3.0.0.0
Fixed the time issue Bug in LG's kernel (however daylight savings time does not work when set on/off in recovery)
3.0.0.0
https://www.androidfilehost.com/?fid=24407100847293244
md5: f7c84c5328fb073a1a57fb75dc70191a
2.8.7.1
https://www.androidfilehost.com/?fid=24269982086988199
md5: 736456843ecaa2b65fbbb749008e1ff3
2.8.7.0
https://www.androidfilehost.com/?fid=24052804347853160
md5: f6d38b88b51d8cc39635534b559f719f
This requires you to have an unlocked bootloader which will wipe data if you have not unlocked already.
Recovery does take some time to boot It has taken up to 45 seconds for the TWRP curtain to show for me
To get to bootloader without adb:
Turn device off
Hold Vol Down
Insert USB plug while plugged into your PC
Hold Vol Down until fastboot pops up
Instructions:
If you have issues with adb or fastboot follow this post: HERE
If bootloader is unlocked:
reboot into bootloader
Code:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img
If your bootloader is locked:
enabled developer options
in developer options "Enable OEM unlock"
reboot into bootloader
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img
Known issues:
You get to see that it's not truly 2 displays
Time is not saved from Android to Recovery
Display does not turn off when it times out
TheJesus said:
I've messaged @KAsp3rd to include it in his OP.
ONLY PERFORM IF YOU HAVE ALREADY FLASHED TWRP AND CREATED AN EXTERNAL BACKUP!!!
1. Hold Volume Down
2. Hold Power button until you see LG screen
3. Release Power button and then rehold Power button
4. Follow on-screen prompts to perform a Factory Reset (If you have TWRP, this should not actually factory reset, but there has been one case of it doing it, that's why I suggest keeping a copy of your backup on your computer), may take a minute to boot into TWRP
5. Enjoy TWRP without fastboot
EDIT: On hold until verified on latest TWRP/more devices.
Click to expand...
Click to collapse
Device tree is here https://github.com/KAsp3rd/android_device_lge_h901
Compiled using omnirom 5.1 with 6.0 bootable/recovery
Get superSU from chainfire http://download.chainfire.eu/supersu
Thanks to @TheJesus @shabbypenguin @Dees_Troy @_that @bigbiff @helicopter88 @savoca @autoprime and anyone I've forgotten.
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
geeserver said:
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
Click to expand...
Click to collapse
I get the same thing
geeserver said:
I'm getting the android with his guts (triangle exclamation) open when I do a
{adb reboot recovery}
Am I doing something wrong or have done something wrong?
My bootloader is UNLOCKED.
Click to expand...
Click to collapse
Did you reboot to bootloader and fastboot flash recovery "img"?
re-read the op
adb reboot bootloader
then do the fastboot commands
KAsp3rd said:
Did you reboot to bootloader and fastboot flash recovery "img"?
Click to expand...
Click to collapse
Here are the commands
-In OS, Android with ADB Debugger on with UNLOCKED bootloader checked
{adb reboot bootloader}
-Welcome to Fastboot Mode:
{fastboot flash recovery twrp-2.8.7.0-h901.img}
{fastboot reboot}
-Phone back in Android
{adb reboot recovery}
NO TWRP
Right now I'm using stock.img files to restore everything and retrying.
I'm currently using Minimal ADB and Fastboot [8-28-15] to push commands.
geeserver said:
Here are the commands
-In OS, Android with ADB Debugger on with UNLOCKED bootloader checked
{adb reboot bootloader}
-Welcome to Fastboot Mode:
{fastboot flash recovery twrp-2.8.7.0-h901.img}
{fastboot reboot}
-Phone back in Android
{adb reboot recovery}
NO TWRP
Right now I'm using stock.img files to restore everything and retrying.
Click to expand...
Click to collapse
Flashing stock.img myself to make sure
same issues here also
Mine worked first try... I personally change the recovery img file's name to recovery.img, but other than that I use the same commands.
yeah, mine has the android open door with "no command" under it
KAsp3rd said:
Flashing stock.img myself to make sure
Click to expand...
Click to collapse
I can't push stock.img from fastboot. Reading from mickeyinid post in that thread, "Make sure you have the newest fastboot binary or it won't flash the system.img" It has a cap at 53MB but the filesize for system.img is 4.2GB.
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Didn't catch that one shabby thanks for pointing it out. I'll update op
this worked. Thanks!!
and thank you so much @KAsp3rd for this recovery
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Once I put in the fastboot boot twrp-2.8.7.0-h901.img command, I heard the computer disconnect and it took more like a minute or a minute in a half but it worked. Then I flashed SuperSU and now I'm ROOTED!!! Thanks!!!!
All rooted. Thank you @KAsp3rd!!
Sent from my LG-H901 using Xparent Skyblue Tapatalk 2
that worked. TWRP installed and rooted. FYI it does take a little time to boot into TWRP with the fastboot command and normal also.
Thanks for the help all
shabbypenguin said:
android has a file /system/etc/install-recovery.sh when you boot up it overwrites teh recovery with stock, chances are its doing that.
boot into fastboot, flash it, then use
fastboot boot twrp-2.8.7.0-h901.img
that will drop you into recovery (it takes like 30 seconds) form there you can do a syou wish, then click on reboot system and it will remove that file so youll have twrp always.
Click to expand...
Click to collapse
Xposed
Can you flash xposed in this recovery?
huynh727 said:
Can you flash xposed in this recovery?
Click to expand...
Click to collapse
Yes. I have it. Use the arm64 for Lollipop version. It does however break the second screen occasionally (it FC's when I get/make a phone call, but that's it). BUT it has RootCloak which lets me use Android Pay while rooted
Success! The whole process was very easy and worked the first time! Thanks for posting this!
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?
**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...
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
forgot something
looks like i skipped this part . Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.Is there anything i can do?
videodave1 said:
I've had my Essential two weeks i was on 8.1 beta.Today i unlocked the boot loader.Then installed twrp while in twrp i side loaded magisk.I went back to fastboot then hit start .The phone just went into a bootloop.I Was able to go back to twrp 2 times but now i can't get back to any type of recovery.I Can get back to fastboot mode ishow all the info and secure boot says yes and device state unlocked.My pc see essential phone fastboot in the device manager but i can't get adb to see it .Can anyone help me ?
Click to expand...
Click to collapse
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
WOW thank you so much'
Arju said:
adb only works while phone is booted into system so nothing wrong there. If you're in the bootloader menu where you see that the status of your device is unlocked then you're already in fastboot mode. Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too. Go into install and press flash image file and find the stock boot image and then go into install again and change to flash .zip and flash magisk. After that, reboot into system.
Click to expand...
Click to collapse
I was able to flash twrp i'll try the rest when i get home from work
sideloading stock img
videodave1 said:
I was able to flash twrp i'll try the rest when i get home from work
Click to expand...
Click to collapse
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
zip file
videodave1 said:
Do i need it to be zipped I've tried it as image that i downloaded from xda and I've tried a zip i got from Essential neither are working?
Click to expand...
Click to collapse
When i try i get invalid file format. This is using a zip i got from Essential.
Stuck twrp says no os installed . But i did learn how to push files.
just trying to get back to stock now
videodave1 said:
just trying to get back to stock now
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
thanks been there tried the Oreo beta that is what i was on when i started and tried the 1st build before the betas i get an error on both i'll try to download them on another pc my phone does show up when i type fastboot devices now just need an os now .
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
thanks everyone.
videodave1 said:
Okay got back to 8.1 bootloader still unlocked twrp not install and i don't have root.I may just wait until P comes out.I'll try and learn more about adb. Thanks for your help Arju.
Click to expand...
Click to collapse
No problem. Thank you very much for the donation, that was really kind of you. Hey I'm sure you'll get the hang of it before android P drops. you did figure out what went wrong all by yourself so get a hold of the right boot.img and the rest is exactly as how you did it in the first place but flash the boot.img before magisk. Let me know if you want to give it a dive again.
I'm on 8.1 boot loader unlocked and ready to try to root again .Thanks for the help
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
avocom said:
This is the closest thread i could find to what is happening to my PH-1.
Like videodave1 I 'was' running the latest stock 8.1 and have my bootloader unlocked. In trying to root the phone I did this:
flash boot flash boot twrp.img
adb shell twrp sideload
adb sideload magisk.zip
All installations went well, but when trying to reboot from twrp it forced me to install the app. After that the phone went into boot loop.
* Note how I didn't sideloaded the Oreo 8.1 image before magisk.
By pressing all 3 buttons I can get the phone to reboot and releasing the volume up I can get to Fastboot. Just volume down and power doesn't work.
The problem now is that adb and fastboot no longer recognise the phone. adb devices just gives an empty list and fastboot only shows < waiting for device >
Trying to go into Recovery mode doesn't work either. Power off doesn't work and Restart bootloader, well, restarts the bootloader.
It might be relevant to mention that I'm running adb and fastboot from Terminal in a Mac and that this is my very first and frustrated attempt to root any phone.
For reference this is what the FastBoot Mode brings:
PRODUCT_NAME - Mata
VARIANT - OPENUS
BOOTLOADER VERSION - mata-aad8ac4
BASEBAND VERSION - 2.0.C4-M1.3.1
SECURE BOOT - yes
DEVICE STATE - unlocked
I might have to just resign myself to the ordinary land of unlocked full stock phones
Thanks very much
Click to expand...
Click to collapse
Even though your phone does not show up its there wipe everything.Fallow what Arju said in his post.I got back to stock then took the 8.1 update i'm not rooted but my bootloader is still unlocked.Oh make sure you unlock critical
videodave1 said:
Fallow what Arju said in his post.
Click to expand...
Click to collapse
Thanks for coming back to me. I really appreciate it.
Arju said:
Just flash twrp again and the sideload stock 8.1 beta boot image (you can probably find it on xda), sideload magisk too.
Click to expand...
Click to collapse
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
avocom said:
Thanks for coming back to me. I really appreciate it.
I might be missing something hopefully obvious here. How can I flash twrp again if I my computer can't see the phone. With the USB phone plugged in and in the FastBoot screen I enter into Terminal:
fastboot flash boot twrp.img
and I get:
< waiting for any device >
How do I flash it from the FastBoot screen? BTW, going to Recovery mode just hangs at the Essential logo.
Thanks
Click to expand...
Click to collapse
are you able to get to the bootloader menu? where it says start on the top.
Arju said:
are you able to get to the bootloader menu? where it says start on the top.
Click to expand...
Click to collapse
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
avocom said:
Thanks Arju. If you are referring to the FastBoot menu where you can use the up and down volume keys to select Start, Restart Bootloader, Recovery mode and Power off Yes, but not much else unfortunately.
If I select Recovery mode I don't go to the screen with the blue buttons from twrp.
Thanks
Click to expand...
Click to collapse
What you need to understand is that twrp will not stick after you flash it. This device does not have a recovery partition and that's why you replace the boot partition with twrp and while you're in twrp you need to flash the boot.img back and whatever mods on top of that such as kernel etc.. If you flash a rom then it will replace the twrp with the boot.img found in the rom zip.
So now we need the computer to recognize you device. Could you unplug the cable and change the usb port on you computer. connect your phone while you're in the bootloader menu where it says start on the top.
The use use fastboot command: fastboot devices
See if the computer recognizes you device.