Database Users

[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

LG K20 plus, how to flash original rom

I have a LG K20 plus with t mobile as the carrier. I believe the model should be TP260. I mistakenly restored a twrp backup from a metro pcs phone that I got from this site coincidentally. Now my phone drops calls and data frequently and shows metro pcs on bootup vs tmobile. I have a kdz file but it won't flash because it now also thinks the model is MP260...not TP260 and says it's a mismatch. Any ideas on how I can get a restore for tmobile to try to reset the phone?

Just bumping

i could use a restore too. I installed super SU root and lost access to android pay. I wasnt to try that magisk root

I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay

colemanimal said:
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
Click to expand...
Click to collapse
You were able to install TWRP after this process with the TP26010k_00_0316.kdz?
I am on TP26010E and don't want to upgrade to TP26010k if TWRP cannot be flashed as it has been stated here.

Yeah, you have to perform OEM unlock again, but I have been able to flash TWRP after flashing the previously attached .kdz with the LGUP tool

colemanimal said:
I restored mine with the linked files.
install LG driver (uninstall any other drivers first)
install LGUP
remove battery from phone and replace
hold volume up key
insert USB while holding down volume up key
phone will boot to download mode
drivers will find phone
run UPPERCUT.exe
UPPERCUT.exe will launch LGUP with phone connected. if phone is not connected try again.
in LGUP lower window browse to TP26010k_00_0316.kdz
choose UPGRADE option in LGUP
click START in LGUP
factory ROM and Recovery will be installed, bootloader will still be unlocked
https://drive.google.com/open?id=0BygTApD1iNSSb3pCcU9RRlV1MVE
magisk can be installed using the same method as superSU. Mine is working along with AndroidPay
Click to expand...
Click to collapse
Can I install this kdz from twrp and install supersu?

no, you have to use LGUP tool. This is a LG image that will flash everything including your recovery partition, and not a flashable ROM image.

You flash root through TWRP, you use LGUP for kdz as the user above said rom flashing and kdz flashing are two different things

See this post which reflects the new kdz available https://forum.xda-developers.com/showpost.php?p=73690098&postcount=3
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
Click to expand...
Click to collapse

I flashed the modded ROM for MetroPCS, and couldn't flash kdz file because my phone was identified as MP260, instead of TP260.
I wiped the phone and re-locked the bootloader, and the phone would only boot into download mode, It gave a message about it being corrupted.
I took it back to TMO, and the sales people thought it was a virus, and replaced the device.
I've made a TWRP backup for anyone who runs into the same problem. This will fix your problem, so you can use the flash tools available for this device.
NOTE: I also provided Root tools and instructions for those Rooting for the first time.
1. Power off device, plug into computer, then hold volume up for download mode and let COM drivers install, you may need to change COM port to 41, through device manager.
2. In LGUP, choose upgrade or FOTA upgrade.
2. Once you flash firmware, you'll have to hit reset once or twice to get rid of the encryption failure notification.
3. Enjoy rooting your device again if you so choose.
ROOTING:
NOTE: Must have ADB & Fastboot setup already.
First you must unlock your bootloader.
1. In about phone settings, tap build number 6x to get developer settings, enable adb debugging and OEM unlock. Now plug into your computer.
2. Boot into Fastboot mode.
A. Open command prompt and type: adb reboot-bootloader.
B. Next type: fastboot oem unlock.
WARNING: You'll be prompted to factory reset device to protect your data. Your chance to turn back, if your brave then continue. Your device will factory reset, and you'll have to perform the first step again and you'll be ready to root.
1. To flash TWRP, plug into computer, then in command line navigate to where you have your recovery.img
A. adb reboot-bootloader
B. fastboot flash recovery recovery.img
2. Pull battery and manually boot into recovery,
A. volume+down as soon as you see LG, release then press again quickly and hold, follow the steps provided.
3. Hit cancel for the encryption notice, and swipe to modify system.
4. You must format device to get rid of encryption message, so choose format and it will ask you to type, yes.
5. Stay in recovery and flash the no-encryption.zip, and Magisk, if you choose to use it for your SU manager. Stay in recovery.
6. Reboot into recovery, and then set up your TWRP environment.
7. Enjoy Root:laugh:
NOTE: If you decide to root again, try using Magisk for SU management. Magisk's mods are excellent, and can run along side Xposed. If you choose Magisk, do not flash SuperUser.zip
TWRP STOCK BACKUP
https://mega.nz/#F!a59RBICD!kOisA-eOxviWK07Dn182FA
LG tools w/ Latest kdz
https://mega.nz/#F!b9sWDBwR!LjhrhZgYXB-BNHUWE11tJw
Sent from my K20 Plus using XDA Labs

Question I have a metropcs k20 version.Can I flash the t-mobile Rom with any problems.Thanks

Rican39 said:
Question I have a metropcs k20 version.Can I flash the t-mobile Rom with any problems.Thanks
Click to expand...
Click to collapse
You could probably flash the TWRP back up. After that your device would be Identified as TP260, by the flash tools and you'd end up with the same issue I had, when you decided to go back to stock, so make a TWRP backup on external memory. The KDZ file most likely won't flash because it performs a DLL check, to match device with firmware.

blas4me said:
You could probably flash the TWRP back up. After that your device would be Identified as TP260, by the flash tools and you'd end up with the same issue I had, when you decided to go back to stock, so make a TWRP backup on external memory. The KDZ file most likely won't flash because it performs a DLL check, to match device with firmware.
Click to expand...
Click to collapse
Thanks for reply.And info

does anyone have an mp 260 zip rom for twrp before boot?

5(/!p7 kiddie said:
does anyone have an mp 260 zip rom for twrp before boot?
Click to expand...
Click to collapse
I've got backup after unlock Bootloader and before root. Pretty sure it's got recovery on it. I always make a backup asap. It's the mp26010t (I had the November patch but some reason after root it says Oct).
Is that what you need?

Pm me if this is what you need and I'll send you a link

I have a Metro LG K20 Plus phone and want to change the firmware to T-Mobile. I have not been successful doing this as I always get invalid firmware, because LG UP recognizes the phone as a metro phone. Is there a way to succeed in getting the T-Mobile firmware on the phone?
thanks in advance.

lg k20 plus tmobil
lgup recognizes my model correctly as lg-tp260 on [com41] but it just sits there initializing for eternity. With my model highlighted I select it and I keep getting the error "LGUP cant load the model [C:\Program Files(x86)\LG Electronics\LGUP\model\com. I have installed lg air drive, lg bridge, lgup8994.dll, lgup for store. I desperately need to get this thing back to stock, I have the AICP rom installed but I dont like it. it was a mistake, if anyone can help I would appreciate it.

stovo06 said:
I've got backup after unlock Bootloader and before root. Pretty sure it's got recovery on it. I always make a backup asap. It's the mp26010t (I had the November patch but some reason after root it says Oct).
Is that what you need?
Click to expand...
Click to collapse
Could you PM me this link to the Metro PCS stock backup, if you still have it?

Hard/soft brick

I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum

jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/

That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.

https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed

jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.

wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc

Was finally able to get into recovery, so all is well. Thanks for the help yall

OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?

gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc

My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?

I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.

katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.

P9 lite brick? @transition Nougat-MM. PHONE locked, FRP unlock

Hi, second post on the forums, I'm in bigger trouble now.
I unlocked my bootloader and then rooted my VNS-L21 so I could edit my hosts file. I tried going back to official and unrooted firmware afterwards, but something went wrong along the way.
The stages:
-OFW VNS-L21C432B504, obtained bootloader code through DC-unlocker (developer options on, OEM unlock on, debug usb on)
-unlocked bootloader with SRKtool using this method get-instant-huawei-bootloader-unlock-code/
-rooted using Magisk and made a full backup through Revolution Recovery using this method https://ministryofsolutions.com/2018/05/huawei-p9-lite-root-for-nougat-new-method.html
- some tinkering here but don't remember exactly plus I guess it's not that relevant ; I think I got rid of root here
- downgraded from Nougat to MM using dload method according to this thread https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 (first flashing rollback package from C432B504 to C900B300, then flashing C432B160 - full)
- everything went fine, bootloader relocked; but I was unable to upgrade to Nougat/B504 - settings-update showed "no updates available", putting update.app in dload folder (obtained from firmware finder, TeamMT, full B504 file) didn't work, pressing three buttons resulted in error (the version not compatible or sth)
-tried dload with previous rollback file
...and now I'm here:
- phone constantly stuck at boot screen (red Huawei logo)
- dload not starting by pressing three buttons
- recovery not starting by pressing volume up
The only thing I can get is white fastboot screen when connected to PC. It says "phone locked" (bootloader) in green, "FRP unlocked" in red. As usb debugging/oem unlock were not enabled this time, platform-tools/adb with command "adb devices" says nothing is connected, similar goes for SRK
Is it hopeless and my phone is thrash or is there anything I can do? Please help!
PS. All I wanted to do with my root was to change hosts file and then unroot/relock phone, seems like it wasn't worth all this work ( https://forum.xda-developers.com/huawei-p9lite/help/retaining-modified-hosts-file-unrooting-t3868641 )
Update: "fastboot devices" in adb directory resulted in detecting my device, next I found and tried command "fastboot oem [PASSWORD]", now there's a change: "This device cannot be trusted" is showing again, in fastboot I see "PHONE Unlocked" in red now. So time to flash some firmware with a command? But which firmware and how exactly to do that?

You have again unlocked your Bootloader? I suggest you flash a Nougat Compatible TWRP and then from within TWRP make wipes. After that use Hurupdater to flash Nougat firmware. First flash TWRP. If it boots into TWRP then format data and then wipe Dalvik/Art Cache, Cache, Data, System and Internal. Next download Hurupdater and stock Nougat Firmware. You need to download three ZIP update.zip, update_data_full_public.zip and regional update file. Next rename them as suggested in Hurupdater thread. Finally place all four files in same folder in SD card and then install and select only Hurupdater.zip to flash. After it complete reboot to stock recovery and factory reset. If all goes well you will be on Nougat.

Thank you so much, HuRU update method was what finally got me from Marshmallow to Nougat

So. I take it your phone is working now? Glad to know and be of help. If you need help with anything then just ask

Yes, it is, I'm currently struggling with systemless hosts on my Magisk rooted Nougat but other than that - everything works fine. Turns out that most of the recoveries I found then were meant for Nougat, only one recovery file worked on Marshmallow (and I've tried quite a few of such files and they were hard to find).
________________
After flashing TWRP recovery, updating Magisk to 17.3 beta and installing newest (4.0.10) version of Adaway - the problem is gone. My guess is that the fault was on Magisk's side as after updating it the "systemless hosts" function in Adaway was no longer grayed out.

Phone doesn't get recognised in Download mode (bootloader)

Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me

Format data?

What your twrp version ? your twrp version must be version support 11.

You cant flash Magisk via TWRP. It doesn't work, Install the magisk App

Wrong place to ask this stuff