Database Info

Trouble installing new recovery

Im trying to get my new XOOM from unlock to root and having a nightmare!
I have read and followed guides from the forum but still can't get the new recovery on?
I have done fastboot oem unlock and followed the instructions on the tab and at the end it says complete. Next once it reboots enabled usb debugging and rebooted into bootloader, all ok so far but when I try to run the command "fastboot flash recovery recovery-tiamat-r4c-100611-1150-cwm.img" it comes up with "cannot load"? I have tried with and without the. img at the end and also renamed the file "recovery" and "recovery.img" and still the same thing.
Has anyone had this same problem and can get me back on track please.
Sent from my MZ604 using xda premium

(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img

Ok, will give it a try when I get to my computer and will report back.
Thank you
Sent from my Desire HD using xda premium

Our Indian cricket team is in your country desperately need a win

rohit3192 said:
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
nope that didnt work, same thing error: cannot load 'recovery.img

ok now im getting someware
still not working but when i do adb devices it says list of devices attached but nothing?

Just a note usb debbuging is on
Sent from my MZ604 using xda premium

rohit3192 said:
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, it really doesn't matter if all your files that you need are in Tools or Platform tools, as long as they are all in there and your command window is operating out of that folder.
Second, you are making a good point re: the img file extension...in Windows, it sometimes is set to hide file extensions, so it is possible that someone could already have the img file extension there and not see it and add it again, making recovery.img.img which of course wouldn't work.
I don't think this is the OP's problem, but you never know.

I'm lost installing CMW

OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?

polish_pat said:
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
Click to expand...
Click to collapse
change directory to the folder the recover/fastboot is in, using the CMD on windows. So:
"cd C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools"
make sure the recovery is called "recovery.img" and that its in the "platform-tools" folder alongside the fastboot.exe, then run the commands:
"fastboot -i 0x0B05 flash recovery recovery.img"
and
"fastboot reboot"

polish_pat said:
OMG yes i know im a newb but there is a first time for everybody for anything.
So i'm trying to unlock, root, install cwm and install custom roms but ive looked at all the instruction from many thread and a lot of them had missing steps
Anyways, i've downgraded from JB to 4.0.3, rooted, unlocked and now i'm trying to install CWM. So i installed android SDK and all tools, i've put recovery image in same folder as fastboot.exe, i've booted the tablet and selectied USB icon but wtf do i do now??
I'm basically here:
** FastBoot Method **
1) Install Android SDK
2) Download CWM Recovery image from the original thread and check the MD5 sum (don't skip MD5 check,is there to make sure the file is not corrupted)
3) Copy the downloaded file in the same directory as your fastboot.exe (unless you have /platform-tools in PATH then you can flash from anywhere)
4) Turn off your device and boot into fastboot mode (power on while holding volume down, then select the usb icon and hit volume up to confirm)
5) Plug the device into your computer
6) Run the following command via the command line:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Where do i get this command line?? is it command line from windows such as CMD?? cause if it is, i've tried it and nothing. Do i have to point to where is the recovery image?? Its in C:\Users\Patrick\AppData\Local\Android\android-sdk\platform-tools but i'm lost from that point, i'm not sure what command line i have to use, and how to set it up so i can tell it where to look.
Can anybody help me please?
Click to expand...
Click to collapse
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------
buhohitr said:
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
Click to expand...
Click to collapse
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.

buhohitr said:
Yes, command line is in your PC. The location of the fastboot.exe located in c:\android-sdk\platformtools (if you install from sdk).
On your PC, open CMD and navigate to the above directory where fastboot.exe is. Make sure your recovery.img in also copied to this same folder. Now you can execute the fastboot comand:
fastboot -i 0x0B05 flash recovery recovery.img
fastboot reboot
---------- Post added at 05:52 PM ---------- Previous post was at 05:48 PM ----------
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
Click to expand...
Click to collapse
Thanks but I've already downgraded. I'll try what the guy above said thank you for the help
Sent from my SGH-I747M using Tapatalk 2

when you are in the fastboot folder, you have to press control & right click inside the folder, and you will see the option to open a terminal.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Pat,
If it makes you feel any better I had a heck of a time with this myself.
Once I realized I had platform tools in a folder on my PC desktop with the command prompt
in it I was able to flash.
Gotta say it wasn't easy to figure out in bits and pieces.
Sent from the inside out...

Thanks guys, you've been REALLY helpful! I completely forgot about the shortcut to open cmd in a folder, and i'm not sure if you were wrong or its because im on windows 8 but its ctrl + shift + right click
EDIT: now i get a problem, it do all this and i get "waiting for device"
i tried different USB ports, same deal...any ideas?
EDIT: EDIT: tried all USB port but one, the last one i used did the trick, thanks for all!

I'm having this exact same problem but changing USB ports is not working for me and I tried everything else. Would it help if I tried a different computer?
Sent from my Galaxy Nexus using xda app-developers app

mnk0ota said:
I'm having this exact same problem but changing USB ports is not working for me and I tried everything else. Would it help if I tried a different computer?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
try to open CMD as Administrator.

buhohitr said:
...
I think it's easier for you to download Voodoo OTA root keeper to preserve root, then upgrade to JB, then use OTA root keeper to restore root. After this you can install TWRP recover by download goomanager from the play store and install it, once you have twrp, you're home free.
Currently you are on ICS, becareful if you use a wrong version of cwm you could brick your device. Many ppl installed ICS cwm version then upgrade to JB without the right version and they bricked.
Click to expand...
Click to collapse
I don't mean to threadjack, but this portion of your post caught my attention.
I just swapped a prime for an infinity. I rooted, installed rootkeeper, preserved root, upgraded to JB and restored root.
Are you saying I can install goomanager and update recovery without unlocking via the Asus tool?
If so, sweet!
Sent from my MB855 using Tapatalk 2

John Kotches said:
I don't mean to threadjack, but this portion of your post caught my attention.
I just swapped a prime for an infinity. I rooted, installed rootkeeper, preserved root, upgraded to JB and restored root.
Are you saying I can install goomanager and update recovery without unlocking via the Asus tool?
If so, sweet!
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
No. You will still have to unlock the bootloader to install a custom recovery, unfortunately.

Firebrazer said:
No. You will still have to unlock the bootloader to install a custom recovery, unfortunately.
Click to expand...
Click to collapse
Thanks... if it seems too good to be true it probably is.
Sent from my MB855 using Tapatalk 2

Acer Predator 8 TWRP 3.0.2

TWRP 3.0.2 for Acer Predator 8 ported by Ruben. - If you like my work please donate here, it will also give me a boost to make more things for this device : https://www.paypal.me/RubenCraveiro
----------- -----------
IMPORTANT NOTE ABOUT ROOTING AND UNLOCKING BOOTLOADER:
After flashing TWRP 3.0.2, use the SuperSU 2.46 flashable zip, do NOT use latest version or will result in a bootloop. Good Luck and have fun with rooting. Unlocking bootloader will delete all your data, so please make a backup first. Thank you.
----------- -----------
CREDITS
And also, before anything i would like to say thanks to @arjaylzo for telling me the name of a device with TWRP which helped making this update possible.
REQUIREMENTS
1- Fastboot/ADB Drivers and ADB folder
For drivers: http://adbdriver.com - Download ADB Driver Installer (universal) from the website, extract it, connect device it should detect device(if not, enable USB Debugging and reconnect), and press install, it should install drivers.
For ADB Folder: download this and extract to your main drive(C:/): https://goo.gl/ZTrfBb
2- Unlocked Bootloader (you need requirement 1 to do this)
Instructions for Unlocking bootloader: Go on settings, about device, press build version several times till it says your a developer, go back to settings, press Developer Options, and enable OEM Unlocking. Power off, then press at same time Power and Vol+ button, then connect to pc and open a cmd and write cd c:\\adb and write fastboot oem unlock, then accept the prompt it will give on tablet, and follow the rest of the steps.
----------- -----------
New TWRP bugfix update! Now you can flash stock rom on TWRP without bricking! Download Page updated!
----------- -----------
BUGS:
1- adb shell command needs to be sent before system partition is mounted or it will give an error, after doing adb shell you can mount system and do all the modifications you need.
2- You cant flash any img on twrp it gives an error, im trying to fix.
3- Backups do work, but everytime twrp restarts, the device name seems to change (which means that on /TWRP/BACKUPS/devicename/backupsinside/ changes every reboot so you have to go get the backup inside the old devicename folder and put on the new devicename folder).
----------- ADITIONAL NOTES -----------
Im leaving an unsecured boot image because system seems not want to boot android if anything seems changed. So please if system does not boot after flashing twrp/rooting, flash the unsecured boot img on fastboot
----------- -----------
Steps TO INSTALL TWRP AND ROOT
1. Download and extract the files: https://drive.google.com/file/d/0BxzG5iupOOSKNTdlRC1Wd0VmTlk/view?usp=drivesdk
2. Power off the tablet.
3. Enter fastboot mode by pressing the power button while holding down Vol -
4. Open up command prompt and navigate to the directory where fastboot.exe is located.
5. Pass the following commands:
fastboot flash boot unsecuredboot.img
fastboot flash recovery TWRP.img
6. Reboot into recovery (TWRP) and install SuperSU v2.46.zip
----------- -----------
Acer Predator 8 Support website(sourcecode, manuals, drivers, stockrom):

http://www.acer.com/ac/en/US/content/support-product/6400?b=1
----------- -----------
SCREENSHOTS:
http://imgur.com/s7CgJPR

I stuck at step 4.
is this the directory where fastboot.exe is located -> C:\adb... I have 4 files there and 1 of them is named fastboot.
Also the files i downloaded and extracted from step 1 , do i need to put them in my device or they need to stay on my pc.

goleoldark said:
I stuck at step 4.
is this the directory where fastboot.exe is located -> C:\adb... I have 4 files there and 1 of them is named fastboot.
Also the files i downloaded and extracted from step 1 , do i need to put them in my device or they need to stay on my pc.
Click to expand...
Click to collapse
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...

Ruben Craveiro said:
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...
Click to expand...
Click to collapse
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????

goleoldark said:
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????
Click to expand...
Click to collapse
make sure you didnt put a folder inside the adb folder instead of the actual file and make sure your writing the right name of the file..

goleoldark said:
Ok so in "C:\adb" i put all files i downloaded from step 1 then I opened cmd in that folder , then i typed "fastboot flash boot unsecboot.img" and it said that i cant load or open unsecboot.img
Any idea why or where is my mistake ????
Click to expand...
Click to collapse
also its not unsecboot, the name i added on this thread was just so it would be faster, the name is unsecuredboot.img and not unsecboot.img i guess ill have to edit that in order for people following the tutorial by line dont make these mistakes..

how do i flash the stock rom came from Acer Predator 8 Product Support Page.
can i just flash this Android 5.1 Lollipop Image via TWRP???
TIA

xdadevelopers13 said:
how do i flash the stock rom came from Acer Predator 8 Product Support Page.
can i just flash this Android 5.1 Lollipop Image via TWRP???
TIA
Click to expand...
Click to collapse
yes

thanks. will i have to flash the stockboot.img and P8AcerRecovery.img via fastboot?
tried flashing the stock rom via TWRP but to no avail.
still cant pass the boot logo

xdadevelopers13 said:
thanks. will i have to flash the stockboot.img and P8AcerRecovery.img via fastboot?
tried flashing the stock rom via TWRP but to no avail.
still cant pass the boot logo
Click to expand...
Click to collapse
If you flash stock rom, i think you have to reinstall stock recovery, the rom itself already brings stock boot.. after flashing stock recovery it should boot since no modifications have happend

Wow good job! Now i have a recovery where i can flash my custom rom for the Predator 8.

p8tgames said:
Wow good job! Now i have a recovery where i can flash my custom rom for the Predator 8.
Click to expand...
Click to collapse
no custom roms yet

How to enter the command ?
Hi i am not so sure how to execute those info in my head and act on it so can anyone teach me ? how to root my Predator 8 GT-810 Android 5.1
i saw the instruction i dk how do i Unlock Bootloader (Fastboot) i search all over google and i dont really got the solution to the question so anyone can teach me ? and "4. Open up command prompt and navigate to the directory where fastboot.exe is located." do i extract the whole file i downloaded into my Acer predator 8 or ?... im stupid sorry ...

ZaineJJ said:
Hi i am not so sure how to execute those info in my head and act on it so can anyone teach me ? how to root my Predator 8 GT-810 Android 5.1
i saw the instruction i dk how do i Unlock Bootloader (Fastboot) i search all over google and i dont really got the solution to the question so anyone can teach me ? and "4. Open up command prompt and navigate to the directory where fastboot.exe is located." do i extract the whole file i downloaded into my Acer predator 8 or ?... im stupid sorry ...
Click to expand...
Click to collapse
On step 4 You need the fastboot files, (adb & fastboot) just search how to install adb and fastboot drivers, choose the directory where to install them and place the needed files inside that folder and open a command prompt on that folder so you can flash the files.

Ruben Craveiro said:
On step 4 You need the fastboot files, (adb & fastboot) just search how to install adb and fastboot drivers, choose the directory where to install them and place the needed files inside that folder and open a command prompt on that folder so you can flash the files.
Click to expand...
Click to collapse
ir I tried finding how to install fastboot driver on Google all showed me downloads links must do survey or download or purchase item to unlock the download files ... So I don't trust it so I kept searching "how to unlock fastboot Acer predator 8"
So for ADB I can search on Google and install it on my tablet ?

ZaineJJ said:
ir I tried finding how to install fastboot driver on Google all showed me downloads links must do survey or download or purchase item to unlock the download files ... So I don't trust it so I kept searching "how to unlock fastboot Acer predator 8"
So for ADB I can search on Google and install it on my tablet ?
Click to expand...
Click to collapse
no, Search how to unlock bootloader, it should show the method that works for most devices and give necessary drivers..

Ruben Craveiro said:
no, Search how to unlock bootloader, it should show the method that works for most devices and give necessary drivers..
Click to expand...
Click to collapse
http://gsmusbdriver.com/acer-predator-8
Does this work ?
Or
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/

ZaineJJ said:
http://gsmusbdriver.com/acer-predator-8
Does this work ?
Or
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
Click to expand...
Click to collapse
Yes, and after you unlock the bootloader, you put the necessary files in adb folder and flash them according to the stepts

Ruben Craveiro said:
C:\adb is where my adb and fastboot commands are.. on the downloaded files from Step 1 only the SuperSU zip is needed on the tablet so that you can flash it later on with twrp, the rest you leave on pc and use fastboot to flash TWRP, unsecured boot image, etc...
Click to expand...
Click to collapse
Hi Ruben Craveiro is this the correct way ? i plugin usb cable into Predator 8 but it says its waiting for device is it the correct way ? after typing those Commands i go over to recovery mode to install SU from there then restart and its rooted ?

ZaineJJ said:
Hi Ruben Craveiro is this the correct way ? i plugin usb cable into Predator 8 but it says its waiting for device is it the correct way ? after typing those Commands i go over to recovery mode to install SU from there then restart and its rooted ?
Click to expand...
Click to collapse
That means adb drivers arent corrently installed, but i can see you have the folder with adb, all you have to now is download this(drivers): http://dl.adbdriver.com/upload/adbdriver.zip
Extract and open the software eith the tablet plugged in, it should tell of drivers is installer properly or not, and if not you can install, after installing it should work on the cmd the commands..

[HOWTO] ULM bootloader unlock and root 20e (Pie) from Oreo

Here's a simple guide for those of you like me who bought a cheap ULM G7 that's actually cross flashed from something else (Sprint for my case).
I got mine with Oreo 11e on it. I'll just explain the steps to get to unlock with 20e (Pie) rooted. I'm not an expert, but I've been doing this stuff for a lot of years. I probably can't answer questions on why it's not working for your situation, so hopefully others can jump in when necessary.
These steps worked for me. Some may be unnecessary. Not sure.
DISCLAIMER: Don't blame me if something goes wrong. Again, this worked for me.
First of all, you'll want to flash to 11g, because we have a patched rooted boot image for it.
https://lg-firmwares.com/downloads-file/17341/G710ULM11g_01_NAO_US_OP_1112
Install the patched LGUP (GUI one, not command line).
Flash 11g by doing a Partition DL, select the kdz in the bottom half (click on the first empty line).
After it's done and it reboots into the system. Let it boot, do the initial setup to get into options and enable OEM unlock and USB debugging.
Then do the unlock guide here:
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
You can follow the steps in there exactly. There is nothing different that needs to be done for the G7. You're basically using QFIL to flash the v35 eng boot to get a hacked fastboot.
You're now bootloader unlocked.
Now, we want to get 20e rooted. Before we flash the 20e kdz, we need a patched boot image (Magisk). We have to create a patched boot image from the stock boot image. So, here are the steps for reference. If you want to skip this (trust me, you do), download my patched boot image here: https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
Skip until you see "Skip to here".
* I was informed after that it's easier to just flash the 20e kdz, then use QFIL to extract the boot image instead of fooling around with kdztools. Leaving this for reference. *
Dowload the 20e firmware: https://lg-firmwares.com/downloads-file/21135/G710ULM20e_00_NAO_US_OP_1010
Use kdztools to unkdz, then undz:
Download the DEVEL branch: https://github.com/steadfasterX/kdztools/tree/develop
Install python. I'm using 3.8 x64 for Windows 10.
In a command prompt, run "pip install zstandard" which you need to unkdz.
In your extracted kdztools folder, run:
Code:
python unkdz.py -f <path to 20e kdz> -x
This extracts a .dz file.
Now run:
Code:
python undz.py -f <path to extracted dz file> -s 42
This extracts the boot image (you can see it's 42 if you do a -l instead of -s).
Now you have your clean/stock 20e boot image.
Go back into fastboot (if you're not still there) and BOOT the rooted 11g boot image: https://androidfilehost.com/?fid=1899786940962574205
Code:
fastboot boot 710ULM11g_rootedboot.img
It'll boot into the system and magisk is installed temporarily. Copy the clean 20e boot image onto your phone. Install Magisk Manager, then in Magisk Manager, click the first Install (top of the 2) and it'll pop up a window. Click Install again, then it'll show a menu with 4 options (honestly, the patch should be moved to the main menu imo). Click "Select and Patch a File". Find your 20e boot image and choose it. Magisk will now patch it and create a magisk_patched.img. This is your rooted 20e boot.
Skip to here.
Now we flash 20e to get Pie. Same as above, use LGUP to partition_dl the 20e kdz (select all).
Once it's done, it'll reboot. Wait for it to get to the initial setup (I don't like force rebooting while system is doing possibly important stuff). Get back into 9008 mode. Use QFIL to flash the patched boot img to "boot_a". Once that's done, just vol down + power for 15 seconds to force a reboot.
You're now 20e + root + bootloader unlocked.
I won't be monitoring this thread a lot, so don't expect quick responses, but there's enough details here for most people who are familiar with rooting to get to where I am.

I successfully rooted my crossflashed spring LG G7 using the guide you linked, and this verizon guide.
I never updated to 11g image. I manually patched the boot_a and boot_b image within Magisk GUI app, within the phone itself.
First of all, you'll want to flash to 11g, because we have a patched rooted boot image for it.
Click to expand...
Click to collapse
Other guides mention disabling/erasing certain partitions: the laf_a/boot_b according to this Lineage16 guide or laf_a/laf_b/boot_a & boot_b according to the 9008 guide, but I could be wrong
Code:
adb root
[In magisk make sure ‘Shell’ is granted super user access AFTER executing the following]
adb shell su dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
adb shell su dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b
This will get rid of download mode feature on your phone, rendering LGUP un-useable, you can use QFIL to restore your backed up laf_a/_b files.
There's a KDZ GUI extract tool here.
It found the following in 20e kdz file: boot.img_65286, boot.img_163830; both 64MB. If anyone knows what the bolded parts represent it would be appreciated. I assume the lower number corresponds to A and the higher, is B.
I'll likely use the twrp_june.img for both boot_a/_b.
Any time you want to flash something via twrp you will have to flash twrp via fastboot again (hence the non persistance), do your stuff in twrp, and then reflash the boot img (it will not boot if you dont do this or use josh1x's boot file). Just like steps 5-6 for gapps.
Click to expand...
Click to collapse
According to this guide.
Now, we want to get 20e rooted. Before we flash the 20e kdz, we need a patched boot image (Magisk). We have to create a patched boot image from the stock boot image. So, here are the steps for reference. If you want to skip this (trust me, you do), download my patched boot image here:
Click to expand...
Click to collapse
Assuming you already rooted the phone, there's a way to prevent, the KDZ from overwriting patched boot_a and boot_b in LGUP, as seen 7:00 and 7:25 of the following video.
I appreciate the guide though.

Stuck in fastboot mode, I forgot something..

Aztec_native said:
Stuck in fastboot mode, I forgot something..
Click to expand...
Click to collapse
Do you have download mode? If yes, you can also flash a kdz to start over. With 9008/qfil, almost all situations should be recoverable.
And what were you doing just before getting stuck in fastboot? Did you have a working system before going into fastboot? If you had trouble with the unlock process, you will have to ask in the V40 thread.

paxar331 said:
I never updated to 11g image. I manually patched the boot_a and boot_b image within Magisk GUI app, within the phone itself.
Click to expand...
Click to collapse
Can you patch a boot image on a phone using magisk manager if it's not rooted? I assumed you needed to be rooted to be able to patch.
If you don't, then you can LGUP directly to 20e, pull the boot image using qfil, and patch with magisk manager right after. Saves a lot of steps and time if so.

strifej said:
Do you have download mode? If yes, you can also flash a kdz to start over. With 9008/qfil, almost all situations should be recoverable.
And what were you doing just before getting stuck in fastboot? Did you have a working system before going into fastboot? If you had trouble with the unlock process, you will have to ask in the V40 thread.
Click to expand...
Click to collapse
No download mode, I was trying to flash pie while on rooted Oreo.. it was fine before that. Half the fun, right?

strifej said:
Can you patch a boot image on a phone using magisk manager if it's not rooted? I assumed you needed to be rooted to be able to patch.
If you don't, then you can LGUP directly to 20e, pull the boot image using qfil, and patch with magisk manager right after. Saves a lot of steps and time if so.
Click to expand...
Click to collapse
No. I rooted with QFIL and V35eng.img → abl_a (after backing up abl_a). Then did fastboot oem unlock, re-inserted the backed up abl_a.img file, then did the magisk patch up to boot_a/_b.

Aztec_native said:
No download mode, I was trying to flash pie while on rooted Oreo.. it was fine before that. Half the fun, right?
Click to expand...
Click to collapse
Maybe try a different LGUP? At worst, you can use the command line only one that bypasses checks and can force flash any kdz. But you have to be very careful to not flash the wrong firmware.
I'm not sure if QFIL can flash kdz, but you could research into that if it helps.

strifej said:
Maybe try a different LGUP? At worst, you can use the command line only one that bypasses checks and can force flash any kdz. But you have to be very careful to not flash the wrong firmware.
I'm not sure if QFIL can flash kdz, but you could research into that if it helps.
Click to expand...
Click to collapse
I flashed a firmware that I previously had flashed, ULM20e.
The phone is only recognized in fastboot as Android Bootloader Interface... Can't get anything to work, haha. However, I did get the 11g IMG to get a different screen..
Edit: The update to pie stopped at 91% and then gave an error.

Aztec_native said:
I flashed a firmware that I previously had flashed, ULM20e.
The phone is only recognized in fastboot as Android Bootloader Interface... Can't get anything to work, haha. However, I did get the 11g IMG to get a different screen..
Edit: The update to pie stopped at 91% and then gave an error.
Click to expand...
Click to collapse
Same here:
According to multiple google searches LGUP is not properly patched.
I then made the mistake of using an older version of LGUP, that doesn't give you the option to disable boot_a/_b partitions from being over written; which was a foolish mistake.
I'd like to add that Pie LG stock boot images have NO FASTBOOT support, DO NOT delete laf_a & laf_b files, doing so does away with 'download mode'. If you do delete it, you'll need QFIL to flash abl_a to v35eng.img; this will give fastboot enablement on the phone, and allow to transfer backed up files to phone using 'fastboot'.
The following post helped, in allowing me to regain access to download mode.
QFIL does not allow overwriting of Pie files except abl_a, which is more than enough in this case.
I also patched Pie/20e boot_a/_b files with magisk, and the phone is stuck in a fastboot loop for me as well, this may explain why 11g is needed.
If using LGUP 1.15, you'll come across google link by sarang on how to implement the 'common dll' patch. Forum won't let me link to the website.
Installed 11g after changing to LGUP's program files (x86) directory:
Code:
lgup_cmd.exe com[your com port # in windows device manager] "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "E:\HIS Documents\Computer guides\LG G7\Softwares\G710ULM11g_01_NAO_US_OP_1112.kdz"
I'm finally able to boot into Android 8.x now, and make magisk fully root.

paxar331 said:
Same here:
According to multiple google searches LGUP is not properly patched.
I then made the mistake of using an older version of LGUP, that doesn't give you the option to disable boot_a/_b partitions from being over written; which was a foolish mistake.
I'd like to add that Pie LG stock boot images have NO FASTBOOT support, DO NOT delete laf_a & laf_b files, doing so does away with 'download mode'. If you do delete it, you'll need QFIL to flash abl_a to v35eng.img; this will give fastboot enablement on the phone, and allow to transfer backed up files to phone using 'fastboot'.
QFIL does not allow overwriting of Pie files except abl_a, which is more than enough in this case.
I also patched Pie/20e boot_a/_b files with magisk, and the phone is stuck in a fastboot loop for me as well, this may explain why 11g is needed.
Click to expand...
Click to collapse
Qfil allows backing up files as well as overwriting almost any file. I do it all the time.
Bricking my phone along the way trying different things. Unlocking and relocking bootloader.
Most of the time when you patch boot imgs people patch and load the magisk patched image to the wrong slot.
I have crossflashed the Korean pie and updated to Android 10 and achieved root with Android 10 as well.
All with qfil and using the command line LGUP to crossflash.
I don't mind helping users with issues as well.

Does anyone know the cmd syntax to execute the following? I.e. 'partition dl' is selected, and every partition but boot_a/_b is selected for installation. LGUP 1.15 GUI asks for a login making it un-usable for most on here.
Edit: This post may correspond with using the right version of LGUP.
I googled parts of this video: https://www.youtube.com/watch?v=ylBSZk7EqcA
I was able to reach 100%.
Unfortunately there's a boot loop, it seems 710ULM11g_rootedboot.img must be flashed before transferring file with LGUP.
I'm stuck and totally confused. Flashed 710ULM11g_rootedboot.img before transferring G710ULM20e_00_NAO_US_OP_1010.kdz. I then pressed power and Vol Down, then tapped the power button, click No on the white screen background, and again, I'm stuck on the fastboot loop.
The fastboot menu looks different than that of the video
https://www.youtube.com/watch?v=ylBSZk7EqcA
The one in the video looks like it's from v35eng.img used in 9008 QFIL guide.

Go back to ULM11g and crossflash using lgup command line to 20e then root it.
I believe there is a rooted 20e boot img that you can load with qfil or if adb fastboot works.
Crossflashing:
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Using qfil to load rooted 20e img.
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
The process in the second guide is the same when loading a rooted img to either boot a or b whatever slot your on.

I was able to solve it.
The magisk patched IMG file by this OP was flashed to both boot_a and boot_b, then executed 'fastboot reboot'; yeah boot_a and boot_b need to be flashed with an identical file.
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
The screen booted twice with the 'Red LG symbol" showing itself twice, before I could get in to the new user setup prompts.
The 20e patched file from the following thread was no good:
https://forum.xda-developers.com/lg-g7-thinq/development/magisk-18-0-boot-images-t3955096
The most important part of this upgrade is definitely making sure LGUP is setup properly, including not installing the stock 20e boot_a/_b partitions, as seen in my previous post, and don't delete the laf_a/_b partitions as a good precautionary measure.

paxar331 said:
I was able to solve it.
The magisk patched IMG file by this OP was flashed it to both boot_a and boot_b, then executed 'fastboot reboot'; yeah boot_a and boot_b need to be flashed with an identical file.
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
The screen booted twice with the 'Red LG symbol" showing itself twice, before I could get in to the new user setup prompts.
The 20e patched file from the following thread was no good.
https://forum.xda-developers.com/lg-g7-thinq/development/magisk-18-0-boot-images-t3955096
The most important part of this upgrade is definitely making sure LGUP is setup properly, including not installing the stock 20e boot_a/_b partitions, as seen in my previous post, and don't delete the laf_a/_b partitions as a good precautionary measure.
Click to expand...
Click to collapse
Yes the boot imgs are identical they are labled a and b because of the dual slots. If you knew what slot you were in prior to flashing any magisk rooted image you would just need to flash that specific boot img slot.
I relocked my bootloader just for kicks.
If you can get into fast boot there is no need to erase laf partitions only if you need fast boot.

I tried it but didn't work in EAW and I lost serial number mac address how get them back??? Need urgent help please

mine was already bootloader unlocked,
but tutorial worked fine here I flashed 20e using LG up and rooted.
What I did:
MAKE SURE YOU ARE BOOTLOADER UNLOCKED. I am not responsible for any damage, it is only what I did.
1)Dowload the 20e firmware: https://lg-firmwares.com/downloads-file/21135/G710ULM20e_00_NAO_US_OP_1010
2) Download this: LGUP new version - https://drive.google.com/file/d/1dJZxrj7nteDDUcQpiJLpX9Mjumm5mtKp/view
3) Install the file you downloaded above (LGUP).
4) Download this: LGUP common.dll https://drive.google.com/file/d/1V8IF2vJed3bQBsBCHLNBJdnW4gRj2uo0/view
5) Open the file downloaded and you will see the folder common. Copy the folder common and paste inside the folder model of the folder of the installation of the LGUP. For example: C:\Program Files (x86)\LG Electronics\LGUP\model
6) You are doing great! Congratulations. Let's proceed with 7.
7) Get phone in hands. Turn off it. Press and hold volume up and connect the phone into notebook. once appears download mode panel you unhold volume up softly.
7.1) When you connect the phone in download mode LG device must show in Windows Device Manager under "Ports" as a LG Serial COM port. Check it.
8) check if you completed the download of the kdz file. Did you complete the download of the big KDZ? Put the KDZ file in C:\ localization of your computer.
9) Let's open a command prompt as administrator. Now, in the command prompt input, type:
cd <path of LGUP folder>
Example:
cd C:\Program Files (x86)\LG Electronics\LGUP
10) Is your phone com5? check in Device Manager under Ports. It is written COM and a number after. If the answer is yes, you only have to type this code and run in the command prompt:
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "C:\G710ULM20e_00_NAO_US_OP_1010.kdz"
11) Are you unsure if your phone is com5? just modify com5 to comX replacing X with the properly number. For my EMW worked with com5.
lgup_cmd.exe comX "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "C:\G710ULM20e_00_NAO_US_OP_1010.kdz"
12) Wait 5 minutes, less or more.
13) it is completed! Remove the plug of the device.
14) It is like a new phone you have to conclude the phone configuration.
15) install magisk from magisk website but dont update it.
16) Get developer options enabled in your phone.
17) Open command prompt as administrator, type this code:
cd <path of minimal adb and fastboot folder>
Example
cd C:\Android-FastBoot-Adb
Don't have adb and fastboot minimal folder? Research in google and download. If you don't know what is the folder, it contains fastboot.exe inside.
18) Type this code now: adb reboot bootloader
19) confirm in phone allow usb depuration in this device or the command wont work
20) Download in your windows this pre rooted file made for this PIE OS by the author of the thread
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
21) put the file inside the fastboot folder. the file name is g7_20ulm_20e_boot_magisk_patched.img
22) in command prompt (already in cd path of minimal fastboot folder) type this:
fastboot boot g7_20ulm_20e_boot_magisk_patched.img
23) phone will reboot.
24) now phone started, open magisk and update it and click to install directly when it asks.
25) magisk will ask to reboot, click to reboot you are now rooted.
good luck

Hi Just a lost soul passing thru Lol
I'm looking to shed some light on my g710pm, its been a few days since I've been searching to get on AOSP.
I cross flashed to ULM 11g stock and had root and unlocked bootloader, then flashed 21d ULM and now Enable OEM unlock is grayed-out (bootloader is already unlocked ) sub message. SO... I back flashed to ULM 11g with same issue.
I've been reading the forums and have a rough idea how to fix, some how re-flashing laf_a ?
would really appreciate the help
Thanks
Found FIX
1. PS C:\Program Files\platform-tools> adb devices
List of devices attached
LMG710ULM******** device
2. PS C:\Program Files\platform-tools> adb reboot bootloader
3. PS C:\Program Files\platform-tools> fastboot oem lock
(bootloader) Erasing userdata and cache OKAY [ 0.492s]
Finished. Total time: 0.592s
4. PS C:\Program Files\platform-tools> fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031

I can't install TWRP on my Nubia Z20(android 11 v3.18

Hello there. I updated my Nubia Z20 global ROM to android 11. I lost Google services in the process.
So I install the necessary drivers on my PC and used minimal adb and fastboot to unlock bootloader on my phone. But my problem is that I can't install TWRP recovery on the phone itself.
I used the Twrp recovery for nubia z20.exe to get the phone into fastboot mode but I cannot proceed any further.
Once the phone enters into fastboot mode, the computer wont detect my phone anymore.
Please help

Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot flash recovery twrp.img

SMcC2 said:
Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot
Click to expand...
Click to collapse
Thanks so much. I will use 7zip to get the twrp.img file.
After that, what do I do next?
do I open minimal adb and fastboot then type the command "fastboot recovery twrp.img"?

Mr Sparks said:
Thanks so much. I will use 7zip to get the twrp.img file.
After that, what do I do next?
do I open minimal adb and fastboot then type the command "fastboot recovery twrp.img"?
Click to expand...
Click to collapse
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.

SMcC2 said:
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.
Click to expand...
Click to collapse
Been working a 12 hour shift all day. I will definitely do this when I close and then give you a feedback

SMcC2 said:
Are you able to extract the .exe with something like 7zip to get the twrp.img file?
Then you could fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Hello again. I tried to extract using 7zip but I couldn't get the .img file. It gave me an error message

Can you share the link you used to download TWRP and copy the error message you are getting?

SMcC2 said:
If you're able to extract it, yes. I tried searching for a copy of that file, but they all appear to be removed from the forums.
Click to expand...
Click to collapse
I found this image file. Is it the one?
https://forum.xda-developers.com/attachments/recovery-nubia-img.5368983/