Database Users

All senior members please help !!!

Hi All,
Hope all are doing well. I'm posting this message on behalf of those people who are facing the most irritating problem currently(those who wants to root their devices on latest CM 12S lollipop 5.0) is:
Custom recovery image not updating, it shows recovery is updated message but when boot into recovery, the phone shows original recovery only, also it gives error of signature verification while applying root package (started pc with signature mode off) and its not rooted.
The following process are done by maximum users.
1. Installing the adb drivers correctly. Even we also used the manual methods to install adb drivers and it went well.
2. Also checked in the device manager. The Android ADB interface is there.
3. Tried Yureka All in one tool box and also manual method. 0% success.
4. Tried CWM and TWRP recovery. 0% success.
Pleas note that, rooting process went well in Kitkat (CM 11S) but not in Lollipop (CM 12S).
You will find lots of posts claiming can't replace custom recovery after bootloader unlock. But we didn't find a single or multiple way to fix this. So, What to do now? There is always a way to make this right. Please help.

das.palash89 said:
Hi All,
Hope all are doing well. I'm posting this message on behalf of those people who are facing the most irritating problem currently(those who wants to root their devices on latest CM 12S lollipop 5.0) is:
Custom recovery image not updating, it shows recovery is updated message but when boot into recovery, the phone shows original recovery only, also it gives error of signature verification while applying root package (started pc with signature mode off) and its not rooted.
The following process are done by maximum users.
1. Installing the adb drivers correctly. Even we also used the manual methods to install adb drivers and it went well.
2. Also checked in the device manager. The Android ADB interface is there.
3. Tried Yureka All in one tool box and also manual method. 0% success.
4. Tried CWM and TWRP recovery. 0% success.
Pleas note that, rooting process went well in Kitkat (CM 11S) but not in Lollipop (CM 12S).
You will find lots of posts claiming can't replace custom recovery after bootloader unlock. But we didn't find a single or multiple way to fix this. So, What to do now? There is always a way to make this right. Please help.
Click to expand...
Click to collapse
**********************************************************************************************************************
now go to this thread download software from this thread only. there are two thread for this tool but i prefer you to go to this one.
GUIDE
using above tool unlock bootloader.
and go for step 4(which flash twrp recovery)(this will create folder in your mobile)
now
download and copy this recovery file in your adb folder LINK
now go to adb folder
now press and hold shift button and right click on empty space there you will see open cmd , click on it cmd will open
now copy below code (this is for CM12 only)
Code:
fastboot -i 0x1ebf flash recovery recovery_twrp.img
anow right click in cmd and click on paste.
hit enter and after a while you will se 'Okay ' message at the end.
bingo you have flasher recovery :highfive: :good:

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

**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. This is a systemless root. Yet you need to unlook Lollipop before upgrading to Marshmallow.
3. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Unlock your device in Lollipop, then upgrade to Android 6.0
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. This TWRP is recommended.
HTML:
adb reboot-bootloader
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Unroot:
Just flash back stock boot.img
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade to Lollipop:
In case you need to downgrade to Lollipop, follow the instructions with care. Do it at your risk.
Refer to Asus Zentalk Forum and grab the required files from there.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Now you are back in Lollipop. You can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!

It worked!Thank you master!I bow now....

I just need root on 6.0.1. Is this going to achieve that?

MikeyLee said:
I just need root on 6.0.1. Is this going to achieve that?
Click to expand...
Click to collapse
According to op it will
Sent from my ASUS_Z00AD using Tapatalk

It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.

pokey006 said:
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
Click to expand...
Click to collapse
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?

samcjtsai said:
1. All credits go to @shakalaca and I just try to recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum but, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Works like a charm !! Thanks !!

kamyk70 said:
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
Click to expand...
Click to collapse
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users

when update to 6.0. bootloader unlocked again ! how can i flash twrp ?

pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.

Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
No it does not

Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thank You for explaining that to me, appreciated!

To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.

euthic said:
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
Click to expand...
Click to collapse
You need to adb sideload all LP .184 images first then use Asus FlashTool to flash RAW Firmware.
Sent from my ASUS_Z00AD using XDA-Developers mobile app

root works perfect along with systemless xposed, but i still cant pass safenet check..(super su disabled, and also xposed) so no AP.. is that normal ?

pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well

ponhei9502 said:
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
Click to expand...
Click to collapse
Guess your ZF2 is not unlocked in LP first, so that you can't see twrp booting. Since you are in Android 6.0 now, try to downgrade to LP, Unlock it, upgrade to 6.0 and then root.

samcjtsai said:
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca and I just recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Where are these files again? They aren't in the zip

thanks, works great, was able to downgrade to lollipop with no problem what so ever. Install twrp, gain root again, and rockin custom roms...

[Root] Using Tethered TWRP to root Android 6.0.1 ZE551ML with locked bootloader

**** This is a modified post with detailed explanation and different files. The original post was made by @samcjtasi at here. *****
If you installed Android 6 from locked Lollipop Bootloader or forgot to unlock the bootloader before the installation and all you need is to root the device, this is a guide for you.
I did unlocked my Bootloader when I was on 168 with Asus unlock app. I flashed 194 raw file via Asus Flash tool which locked my bootloader. I installed MM via adb sideload and I had MM with Locked bootloader. I used this method to root my phone.
I am sure you'd already known that rooting the phone (acquiring the administrative rights for your own phone) will void the phone warranty.
With this method,
1. You do not need to downgrade your MM bootloader to Lollipop, unlock it, install twrp and root the phone, and then upgrade back to MM.
2. You do not need to install the TWRP. You will be running the TWRP from the tethered mode so your stock recovery will be intact.
3. SuperSu initial installation will modify some files in your boot partition in order to re-direct the system request to the SuperSu, as such In case you want to 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.
4. Make sure your phone has battery 80% or more.
Requirements:
1. USB drivers for Asus have to be installed in the computer and your computer should recognize and can do the file transfers between the computer and your phone. You can get the drivers here. You will need to allow the file transfer from your phone when prompt.
2. Android debug bridge (ADB) has to be installed in your computer. I used ADB version 1.0.32. Some knowledge in using DOS and ADB is a plus.
3. Your phone should have the developer option enable and usb debugging should be checked in the developer option tab.
4. You need to know how to use the TWRP. There are a couple videos on youtube explaining about using TWRP.
The Files you need for the root.
1. TWRP - you can download the latest twrp file from here. The latest is ver 3.0.20. You could use older 2.8 versions if you want it.
2. SuperSu installer - I did try with latest SuperSu without success as such use the SuperSu patched by @shakalaca . Get the BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0.zip file here.
Steps:
1. Copy the downloaded TWRP to the directory that you install the ADB. (If you do not want to type long file name in adb, rename it to twrp.img. )
2. Connect your phone to the computer and copy the SuperSu installer to the phone internal memory or the external SD card.
3. Open the command prompt windows with administrative rights. (Without admin right ADB will not work properly).
4. Go to the ADB directory using the cd command. (e.g. cd\, cd adb, etc...)
5. Start the ADB environment by typing "adb start-server" . (without the quotation marks of course). You should see ****the demon started successfully*** message.
6. If you want to check your phone connection in adb, you can type "adb devices" to see your phone is recognized in ADB environment. You should see your phone serial no. and status .
7. Boot the phone to bootloader by typing "adb reboot-bootloader". The phone should vibrate and go into the fastboot mode. Wait till your phone get in the fastboot mode before you proceed.
8. Give the command to boot the phone to the twrp by typing "fastboot boot twrp.img". (If you did not change the name of the image file you need to type or copy and paste the whole file name).
You will see the message saying like-
"downloading 'boot.img' .....
OKAY [0.668s]
booting.....
OKAY [0.450s]
finished. total time: 1.120s "
The phone will vibrate twice and the Asus Logo with black splash screen will appear. The phone is start booting with TWRP image.
9. Unplug the phone from the computer. (If within 30 sec your phone should not start booting to TWRP. you can press and release the power button to go to the normal boot mode or press and release the volume-up key to go to the recovery mode. The TWRP should start by then.)
10. In TWRP install the SuperSu file by tapping install option. (I am sure you remember where you put the SuperSU installer zip file)
11. When the SuperSu installation is completed you will see the message saying like " You will see the your phone has failed verification message and reboot a couple times". Please remember that.
12. Clear the Dalvik cache and then reboot the phone. (You can reboot the phone without clearing the dalvik cache if you want).
Your phone will reboot and you will see the triangle saying like "your phone has failed verification" message and then automatically reboot the phone, showing up the message again. It would happen two to three times and you phone will be booted to the system. (You will not see that error message anymore in the upcoming boots).
Now your phone is rooted. You can check it by installing and running the app like root-chekcer.
Good luck.

Even with the command to boot into twrp from fast boot mine still boots into stock recovery
Sent from my ASUS_Z00AD using Tapatalk

sci05 said:
Even with the command to boot into twrp from fast boot mine still boots into stock recovery
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
It should not be go to stock recovery. The command is to boot with twrp.img.
Did you see message "booting ok finsihed" in the adb window?
Once you see that message, you can unplug the phone from the computer and twrp should be boot within 30 sec.

I finally found the time to update, everything went smooth but I'm having problems booting the twrp
I've tried several twrp from the guides but none worked
In cmd it says
Downloading boot.img
Okay
Booting...
Okay
Finished
C:\
The phone reboots but it goes to the dead droid screen.
I'm using adb and fastboot from adb-setup-1.4.3
IntelAndroidDriver1.10.0 and I've selected this version for the device in device manager.
The so is win 10 prof, I'm starting cmd as administrator.
I tried unplugging the phone and leaving it connected.
Also I'm using the 550 version, I've tried twrps from several threads for 550 and 551 (even tho twrp has merged both phones)
Am I missing something?
A little ot :
I need root 'couse adaway but I thought I would just use the twrp file manager to swap the default hosts file with the one I had in L.
It should work, right?
Sent from my ASUS_Z008D

sway8966 said:
It should not be go to stock recovery. The command is to boot with twrp.img.
Did you see message "booting ok finsihed" in the adb window?
Once you see that message, you can unplug the phone from the computer and twrp should be boot within 30 sec.
Click to expand...
Click to collapse
Yup says boot ok bit it boots into the dead android which is the load screen of the stock recovery. Press vol up and power and stock recovery menu appears.
Sent from my ASUS_Z00AD using Tapatalk

Acca85 said:
I finally found the time to update, everything went smooth but I'm having problems booting the twrp
I've tried several twrp from the guides but none worked
In cmd it says
Downloading boot.img
Okay
Booting...
Okay
Finished
C:\
The phone reboots but it goes to the dead droid screen.
I'm using adb and fastboot from adb-setup-1.4.3
IntelAndroidDriver1.10.0 and I've selected this version for the device in device manager.
The so is win 10 prof, I'm starting cmd as administrator.
I tried unplugging the phone and leaving it connected.
Also I'm using the 550 version, I've tried twrps from several threads for 550 and 551 (even tho twrp has merged both phones)
Am I missing something?
A little ot :
I need root 'couse adaway but I thought I would just use the twrp file manager to swap the default hosts file with the one I had in L.
It should work, right?
Sent from my ASUS_Z008D
Click to expand...
Click to collapse
The guide was written from the experience working with 551ML but it should work for the 550ML I think.
I am also using the Win10 Prof and my adb has a date of 3/30/2015.
I downloaded the latest twrp from the teamwin site. I did not use the twrp mentioned in this forum because they did not work for me. (The purpose of this guide is to use TWRP as temporary and not to install on the phone as such we do not need the signed TWRP ).
In the original thread some mentioned about going to the stock recovery (dead droid with red triangle) as such I put the instruction to press the power button or press the volumn-up button to go to the recovery mode. Actually, they are not required. If everything works, your phone should start booting with the twrp image.

sci05 said:
Yup says boot ok bit it boots into the dead android which is the load screen of the stock recovery. Press vol up and power and stock recovery menu appears.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you saw the message booting .... and ok your phone should be start booting to TWRP not the recovery. The command was to boot the phone with TWRP image. Try to download the TWRP image again from the teamwin site.

If someone just need root for Adaway, just don't, it is not required anymore since you can use other adblocker without root. Just install Block this and you're on: https://block-this.com
Sent from my Asus Zenfone 2 using XDA Labs
---------- Post added at 02:05 AM ---------- Previous post was at 02:03 AM ----------
Will this root method unlock definitely the boot loader as the other methods around here for MM?
Sent from my Asus Zenfone 2 using XDA Labs

sway8966 said:
If you saw the message booting .... and ok your phone should be start booting to TWRP not the recovery. The command was to boot the phone with TWRP image. Try to download the TWRP image again from the teamwin site.
Click to expand...
Click to collapse
I used the latest twrp. Should I use a different one?
Sent from my ASUS_Z00AD using Tapatalk

sci05 said:
I used the latest twrp. Should I use a different one?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you are using latest twrp directly downloaded from the teamwin site and if you are following the steps that I mentioned you should be OK. The only thing different could be the ADB version. Try different adb version or try this on the different computer.

Thanks. I got systemless root by this method.

fred_gaou said:
If someone just need root for Adaway, just don't, it is not required anymore since you can use other adblocker without root. Just install Block this and you're on: https://block-this.com
Sent from my Asus Zenfone 2 using XDA Labs
---------- Post added at 02:05 AM ---------- Previous post was at 02:03 AM ----------
Will this root method unlock definitely the boot loader as the other methods around here for MM?
Sent from my Asus Zenfone 2 using XDA Labs
Click to expand...
Click to collapse
Thanks for the reminder, I'm using this until I get twrp to boot.
I tried adb 1.0.36 that should be the latest but it didn't work. I'll try on win7 or something.
If someone that succeeded could do
Adb version
Fastboot --version
And report here I'd be grateful.
Edit:
I've tried win 7 too but without luck.
Sent from my ASUS_Z008D

I confirm - it doesn't work. I have too "dead droid" and "No command" below.
Windows 10 Pro, ADB 1.4.3. Asus Zenfone 2 ZE551ML 4GB/32GB/Z3580 stock firmware 4.21.40.134.

ok, so how to install xposed framework?

Hi,
Does it reset the phone (apps, documents, accounts,...) ?
Tks !

This will probably not work. In other for it to work and be able to boot into twrp, I had to unlock the bootloader first, because the "fastboot boot twrp.zip" command wouldn't work unless I did so

CBT38 said:
Hi,
Does it reset the phone (apps, documents, accounts,...) ?
Tks !
Click to expand...
Click to collapse
No it does not. The procedure is to boot with twrp image temporarily.

jman0 said:
This will probably not work. In other for it to work and be able to boot into twrp, I had to unlock the bootloader first, because the "fastboot boot twrp.zip" command wouldn't work unless I did so
Click to expand...
Click to collapse
It work for me though. If you unlocked your bootloader you do not need this method. You can simply install the twrp to your recovery partition.

I can confirm it does not work with a locked bootloader, it boots into the dead droid screen.

Can i install Xposed with threded recovery

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?

Problems with rooting, loading ROM then recovery & download images -some solutions

Problems with rooting, loading ROM then recovery & download images -some solutions
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810p rom (H91810p_00_0717.kdz) downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload
Download Magisk-v16.0.zip and copy to adb directory.
On Windows PC connect Cell with USB and in CMD window type (copy/paste):
adb start-server
adb sideload "Magisk-v16.0.zip"​And never update migisk after installing from above or will lose root. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
4. No need to download UPPERCUT (that is hard to download), because LGUP works fine without UPPERCUT.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin

shahinman said:
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810P that needs to be reloaded was missing in original links - I think I downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload
Download Magisk-v16.0.zip and copy to adb directory.
On Windows PC connect Cell with USB and in CMD window type (copy/paste):
adb start-server
adb sideload "Magisk-v16.0.zip"
And never update migisk after installing. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
Click to expand...
Click to collapse
You can restore download mode by flashing the zip in the original lafexploit thread, but make sure you have twrp on the recovery partition. Make sure you are on the latest version of twrp, when you flashed twrp, you were supposed to format the data partition before flashing the rom.
Sent from my LG-H910 using XDA Labs

For access to Data in TWRP: In the original thread there is nothing about formatting, but in step by step guide there is and I followed - however it does not specify what partition to format. I also ran ./step2.sh script per instructions.
Anyhow as I mentioned above I rebuilt and reformatted the Data partition and that did not give me access. I am on the TWRP 3.2.1-3. What partitions do I need to reformat anyhow?
To flash recovery: I used TWRP and flashify to flash recovery-twrp-h918-2018-10-18.img and it flashes but does not work - I get to fastboot with Vol- & USB.

shahinman said:
Problems with rooting, loading ROM then recovery & download images -some solutions
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810p rom (H91810p_00_0717.kdz) downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload​Download Magisk-v16.0.zip and copy to adb directory.​On Windows PC connect Cell with USB and in CMD window type (copy/paste):​adb start-server​adb sideload "Magisk-v16.0.zip"​
And never update migisk after installing from above or will lose root. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
4. No need to download UPPERCUT (that is hard to download), because LGUP works fine without UPPERCUT.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
Click to expand...
Click to collapse
I had this same situation and ended up bricking the phone, can't get into recovery, stuck in boot loop. This was months ago, just got another v20 and ready to try again. Previously I'd successfully done 3 v20's.