Develop Bugs

LGUP - NEW!!! - INSTALL KDZ - MM or LP - FACTORY RESET/UPGRADE

NEW software!!!!!...... LGUP WILL FLASH YOUR KDZ files
Download LGUP from here http://www.filedropper.com/g4 or here https://www.dropbox.com/s/d2dw48uqh4hku8m/G4.rar?dl=0 or here http://oceanhost.eu/eps4h4pmwphu/LGUP.zip.htm thank you hyelton for this link :good:
Install LGUP_8994_DLL_Ver_0_0_3_23 first and then LGUP_Install_Ver_1_14_3
Make sure you have downloaded the required KDZ file MM or LP
Start LGUP prog on your computer "make sure your phone is plugged in"
ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it.
THANK YOU FOR THIS Killerdog:good: <~~~To Modify This File You Must Have Root!!
For me it's show in LGUP as unknow device.
reboot my phone, remove battery and anything else don't work.
I install LG Bridge to test, and nothing seem to work.
After make some test and search, i find some info modified by S3V3N into his rom (cust partition) that he have modify into this file:
/cust/OPEN_COM/cust_OPEN_EU.prop
Code:
ro.lge.swversion=[COLOR="Red"]some info[/COLOR]
ro.lge.swversion_short=[COLOR="Red"]some info[/COLOR]
change to
Code:
ro.lge.swversion=[COLOR="Red"]H81510c[/COLOR]
ro.lge.swversion_short=[COLOR="Red"]V10c[/COLOR]
restart my phone and woow it show correctly in LGUP and i can refurbish my phone.
TO UPGRADE TO MM from LP - make sure BIN file is ticked and in the File Path point it towards the MM KDZ you have downloaded. MAKE SURE YOU HAVE CLICKED UPGRADE! This will update you from LP to MM with out wiping any of your info. Press Start. Make cup of tea and be patient
TO DO A FULL WIPE AND INSTALL MM - Open the LGUP on your computer. FILE PATH point it towards the MM KDZ.
IMPORTANT!!!!!!! shut down LGUP!
Now open LGUP again - you will notice that the MM KDZ will still be showing in the FILE PATH section. Select REFURBISH and make sure BIN file is ticked. Press Start. Make cup of tea and be patient
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a full wipe, tick BIN file. Press Start. Make cup of tea and be patient
If you are worried about losing your data after a full wipe, why not use the LG Bridge software to backup and restore.... it works fine!
YOU WILL LOSE ROOT!
There is no need to enter download mode! LGUP will do it for you.
Original thread by schafi03 http://www.android-hilfe.de/thema/a...er-zurueck-auf-android-5.733674/#post-9342963
Thank You schafi03
INSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install then select images then select recovery NOT BOOT then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery.
How to root LG G4 H815 on Android Marshmallow
http://www.ibtimes.co.uk/how-root-lg-g4-h815-android-marshmallow-1526102
OTHER GREAT THREADS TO HELP YOU
http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282 by autoprime "Great Job"
http://storagecow.eu/index.php?dir=Xda/LG+G4/ an extensive list of KDZ files
Have fun people! :good:

don't know if it makes a difference, but i read somewhere to install LGUP dll first, then the other one.

reg66 said:
don't know if it makes a difference, but i read somewhere to install LGUP dll first, then the other one.
Click to expand...
Click to collapse
Not sure but I'll put that in the op cheers.

Do you need root so use this method to upgrade to marshmallow ?

H81520A_00.Kdz flashed (by upgrade option) succesfully. It takes 10-15 mins(longest part is "android upgrading" screen.), and i lost root access. By the way root access is not necessary for upgrade.

So since it wasn't clarified, I'll be the one to ask...
Will this work on a unit without root (which is yes according to the OP), and without a bootloader unlock, ie the Taiwan (TWN) variant of the H815.
I completely understand it's a complete wipe and root will not be retained.

I would also like to know about this..... will it work on a unit with a locked bootloader... TWN variant?

downloaded from a different mirror re flashed no problems

Hello downgrande wokrs?

munkypoo7 said:
So since it wasn't clarified, I'll be the one to ask...
Will this work on a unit without root (which is yes according to the OP), and without a bootloader unlock, ie the Taiwan (TWN) variant of the H815.
I completely understand it's a complete wipe and root will not be retained.
Click to expand...
Click to collapse
its working on all last night i did downgrade to 5.1 and so far all working great
no root or unlocked bootloader is needed
madshabz said:
I would also like to know about this..... will it work on a unit with a locked bootloader... TWN variant?
Click to expand...
Click to collapse
yes it will work with locked bootloader
ktomika said:
Hello downgrande wokrs?
Click to expand...
Click to collapse
great i did it and now using 7Rom 6.3 3d Rom
best of luck guys

Rikoman17 said:
Do you need root so use this method to upgrade to marshmallow ?
Click to expand...
Click to collapse
no you do not need root....this method will take you back to stock ROM

do I have to unlock bootloader?

microcens said:
do I have to unlock bootloader?
Click to expand...
Click to collapse
no you do not

Kdz only? Does it work with tot file?

bobimbap said:
Kdz only? Does it work with tot file?
Click to expand...
Click to collapse
I'm presuming yes but I havn't tried this, maybe someone could enlighten us

madshabz said:
I would also like to know about this..... will it work on a unit with a locked bootloader... TWN variant?
Click to expand...
Click to collapse
work for all . root and unroot . locked or unlocked . doesnt care . its a special software
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
bobimbap said:
Kdz only? Does it work with tot file?
Click to expand...
Click to collapse
that work fine with TOT file too my friend tested on corean version of g4

Worked a treat no issues so far
Sent from my LG-H815 using Tapatalk

kevtrysmoddin said:
Worked a treat no issues so far
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Great... Did you upgrade to MM or factory reset MM or LP?

shakeyabooti said:
Great... Did you upgrade to MM or factory reset MM or LP?
Click to expand...
Click to collapse
Upgraded
Sent from my LG-H815 using Tapatalk

info
i tried with this tutorial , but the program search my lg g4 with unknown model and i can't use this procedure..
why?
at moment i have a unlocked bootloader and a 10 ve rooted rom twrp

I can't Lock Bootloader (Mediapad M2 10 A01W)

Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.

ma2crmam said:
Hi.
I rooted my M2 10 Wifi (A01W) with Kingroot and apparently now it's unroot (Magisk Manager said that). Even I made a factory reset.
I have the _B007 version and when I try to upgrade via OTA to _B008, it always fail and show "Failed to check the update files. Please download the package again".
I've working with ADB, Fastboot... and I could see that it's unroot, but the Bootloader is Unlock and I can't Relock it. Maybe it's the reason because the OTA doesn't work.
So I got a fastboot code with DC-UNLOCKER and tried to relock (fastboot oem relock CODE) and the answer was:
FAILED (Remote: root type is risk)
If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: RISK
change_time: xxxxxxxxx
Apparently, the Recovery is stock, with EMUI logo showing 3 options:
Reboot, Wipedata/factory reset and Wipe chache partition
I made the factory reset that way.
Any idea? Thanks.
Click to expand...
Click to collapse
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!

ma2crmam said:
Well, I've read that flashing a system.img extracted from the UPDATE.APP I would can restore the Stock ROM... but I don't find a complete Stock ROM for Mediapad M2 10 Wifi (A01W).
I found the OTA in Romfirmware or Fordroid (sorry, I'm new user and I can not post external links). With this I can flash BOOT.img and RECOVERY.img, but the problem persist.
Does someone has any idea... or where can I get the complete Stock ROM?
Thanks!!!
Click to expand...
Click to collapse
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs

5m4r7ph0n36uru said:
Stokk ROM maybe available through a paid service by easy firmware. Got my LTE Stock ROM frim there. For the Wi-Fi edition you could first take a look here.
Sent from my HTC U11 using XDA Labs
Click to expand...
Click to collapse
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?

ma2crmam said:
Thanks!!! I didn't know that page. It's fine and does not look very expensive.
Just one more doubt.
The firmaware I need (as read on the tablet) is M2-A01w...B008 for West Europe
The firmware that the page shows is M2-A01w...B008CUSTC100D001
Do you know what CUSTC100D001 mean? Could I used it without problems?
Click to expand...
Click to collapse
Glad it helped and yes it is not so expensive regarding the fact that there are all sorts of official firmware (mostly leaked ones) available for a lot of manufacturers.
The CUST reference at the end if the firmware version can be found in settings > about the tablet in the very last line. Mine is in German, So translated this line would state something like adapted/customized version. D001 is definitely Western Europe,this should be fine.
If not familiar how to install it google or search the forum for dload method. It will tell you what to do.
Sent from my HTC U11 using XDA Labs

I've done:
1. Get the correct firmware (version ...B007) and extract the RECOVERY.IMG and UPDATE.APP.
2. Flash the RECOVERY with Fastboot and install the UPDATE with the "dload" in the SD.
3. Reboot in RECOVERY MODE, wipe all and restore factory settings.
4. Then, the tablet was updated via OTA to the ...B008 version.
Then, positive:
1. The OTA works fine.
2. I was abble to install the Nextlix App and the HBO Spain App plays videos. Both didn't work before.
3. If I execute "fastboot oem check-rootinfo":
old_stat: RISK
now_stat: SAFE
Then, negative:
1. I can't relock the Bootloader yet. When I try to relock (fastboot oem relock CODE) and the answer was again: FAILED (Remote: root type is risk)
Well, for normal use that's enough, but... THE RELOCK is becoming personal!!!

[GUIDE] Unbrick your BLN-L24 and other variants after rollback to EMUI 4.1

The process here will work on all variants of 6X but you must use the Huawei Update Extractor Tool to get the necessary images from your devices initial firmware update.app. I have provided the images only for the BLN-L24 variant for which initial firmware is B110. Due to variants having different firmware the BXXX for the rollback might not be the same but the process is
When you attempt to rollback from Nougat/5.0 (B360) to MM/4.1 stock B110 firmware with successful updates using the dload method there is a good chance your phone will be bricked and fail to boot . The first update/downgrade from B360 firmware to B300 will boot the phone but when you do the second update from B300 to B110 firmware the phone will stay on the honor screen. This happened to me and after flashing firmware numerous times and using ADB to flash boot.img the phone was still not working but I was able to recover and get it working again thanks to the Huawei_Multi-Tool_by_Team_MT_v7.1.
Download Images and put them in the Unbrick folder of the Huawei Multi Tool.
System.img
Boot.img
Cust.img
Recovery.img
1. Put phone in fastboot by holding Vol - and connecting usb to computer
2. Unlock bootloader using command fastboot oem unlock xxxxxxxxxxxxxxx where x is your 16 digit unlock code
3. After automatic data reset put phone in fastboot again
4. Start Multi Tool and hit enter to get to main menu
5. Press U for unbrick and hit enter
6. Press 2 and hit enter to start the process
Downgrading from Nougat to MM will relock your bootloader so you must unlock it in order for the multitool to flash the files to unbrick your device. Once unbricked if you relock the bootloader your device will be factory fresh with initial firmware.
Credit to: Team MT for the multi tool and Update Extractor Tool
If this helped you give me a thanks!

No luck for me had to return my phone and get a replacement
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
McRoberts said:
No luck for me had to return my phone and get a replacement
Click to expand...
Click to collapse
At least your method is not just the dload method it does not always work. I know. Thank you. You did great on the method.

McRoberts said:
No luck for me had to return my phone and get a replacement
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
At least your method is not just the dload method it does not always work. I know. Thank you. You did great on the method.
Click to expand...
Click to collapse
Thank you. So you have another 6X now?

Yes I got today so I'm taking my time and reading a lil more. It's such a defeat taking that phone back it's my first real brick.

can i download the recovery img and then flash that using adb to remove twrp and then *try* to restore stock firmware? like.. will my BLN-L24 honor 6x accept that recovery img there?
i used the twrp app to back up my recovery and boot imgs but idk where they were backedup to and where ever they are, if i still have them.. i dont know how to restore them

xSpartacusx said:
can i download the recovery img and then flash that using adb to remove twrp and then *try* to restore stock firmware? like.. will my BLN-L24 honor 6x accept that recovery img there?
i used the twrp app to back up my recovery and boot imgs but idk where they were backedup to and where ever they are, if i still have them.. i dont know how to restore them
Click to expand...
Click to collapse
Look in a folder named TWRP (on your device's storage)

can you repost system.img, it doesn't seem to be available anymore. Thanks.

System. img link is error 404
Hi I wanted to take a shot and see if anyone is still on this thread that may have and is willing to help me out and relink the system.img for the initial release FW for the BLN-L24, any help would be great thanks in advance!

System.img
Boot.img
Cust.img
Recovery.img
Any chance someone has the System.img file and can reupload?
Thanks,
Greg

Looking for NPPS25.137-93-14 fastboot firmware

Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.

https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897

I have been looking for it during several weeks too, no success until now. I found 137-92-14, which is built for other software channels. It works well in my XT1685 (Dual sim 3GB/32GB reteu).
Still looking for 137-93-14... Regards.

Doesn't XT1685 equal G5 Plus?

Andrej_SK said:
Doesn't XT1685 equal G5 Plus?
Click to expand...
Click to collapse
Yes.
Enviado desde mi Moto G (5) Plus mediante Tapatalk

Andrej_SK said:
Could somebody provide full untouched fastboot firmware with build number NPPS25.137-93-14 for DualSIM Moto G5 (XT1676) with reteu software channel and 3GB RAM/16GB ROM, please? Thanks in advance.
Click to expand...
Click to collapse
How can I provide you with fastboot firmware as I am having same build version with untouched fastboot firmware.but I am having xt1677 with same specs.

I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...

Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?

Aaric leo's el drigo said:
Ok I will update recovery for you. Which varient it is if amzin one link will be uploaded at evening. Just let me know. Waiting for reply?
Click to expand...
Click to collapse
Mine is retail. Either *-12 or * -14 recovery.img will be ok.
Thanks.
Sent from my Moto G5 using XDA Labs

Ok I will upload it. As fast as possible
---------- Post added at 04:38 AM ---------- Previous post was at 03:42 AM ----------
Because I can't fine firmware online to download, or I don't have retail varient so I can't help you. But if you have laptop, pc. I can help let you know how you can download firmware. Let me know if you need guide as fast as possible.

leohussey said:
I'm also looking for NPPS25.137-93-14 (or NPPS25.137-93-12)... I only need the stock recovery.img file of either of the two...
Click to expand...
Click to collapse
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.

Andrej_SK said:
You can flash older recovery without bricking the phone. However, don't do that if you are running CustomROM. In my case, when I wanted to revert to fully updated stock, I flashed NPPS25.137-93-8 firmware without gpt, bootloader (that's what would brick the phone if flashed) and erase modem commands, updated it to NPPS25.137-93-12, then to NPPS25.137-93-14 using stock recovery and these files https://drive.google.com/drive/folders/1BkpfHvgQ477NViLYvzgv88Fgq3SSt5Py. No issues at all and my phone (XT1676, 3/16, DualSIM, reteu) is still working fine.
In the attachment, I'll put recovery.zip (with recovery.img inside of it) of the NPPS25.137-93-8. Use at your own risk, if you are interested.
Click to expand...
Click to collapse
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs

leohussey said:
Thanks.
But thing is: I'm currently on NPPS25.137-93-12 with TWRP and Magisk. As a proof of concept I want to go to *-14 via OTA to see if it is possible... And if so: to make the oreo jump when available for my channel (XT1671, 2 sim, retla). I want to avoid losing all my data or any long task that would keep me offline for a long time... Daily driver both work and personal...
Uninstalling Magisk reverts boot.img to stock.... but I still need the stock recovery.img to be in 100% stock state (but unlocked). That's the theory.
Tried yesterday using other recovery.img versions, but failed: /cache/recovery/last_log shows the Blur* OTA file updater-script explicitly checks recovery version to be either source or destination versions... So *-12 or *-14.
After that, updater-script checks boot, system and oem. Those are (will be, supposedly) stock since Magisk only patches boot.img and I'll uninstall it .... should work...
The longer path of flashing other version and do the OTAs is also possible... But I'd have to be on vacation or something...
Thanks again.
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.

Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). Once again, you are doing it at your own risk.
Click to expand...
Click to collapse
Thanks. I'll test tonight.
"Bad key" is no problem... Got it twice already by testing with other versions I was able to get.
As for it being from *-14, it should work if I believe the updater script checking for either *-12 recovery (source) or *-14 recovery (target)... We'll see.
Sent from my Moto G5 using XDA Labs
---------- Post added at 06:31 PM ---------- Previous post was at 06:28 PM ----------
Andrej_SK said:
Try one more time with file in the attachment of this reply. Although you will get "Image signed with key bad key" (because it's simply extracted from NPPS25.137-93-14), it should flash just fine. In my case, I've tried to flash it with fully updated phone to NPPS25.137-93-14, no issues at all. However, you should be more careful if you are running .12 firmware - this is stock and newer recovery (recovery of .14 firmware). .
Okay, so there are already 2 files in the attachment, first one contains recovery.img of .12 firmware, second one of the .14 firmware. You can recognize them by name of the file. With each of them, you will still get "Image signed with key bad key" message when flashing, but they flash just fine and everything seems to be working flawlessly on my phone with coresponding firmware version (means .12 recovery for .12 firmware, .14 recovery for .14 firmware). Once again, you are doing it at your own risk if you decide to.
Click to expand...
Click to collapse
Hm... By the time I quoted to answer, you updated. Cool.
Then I'll test directly on 12. Thanks.
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs

leohussey said:
Another question: are you extracting them from your own phone? If so, how? Untill now I only found possible by rooting, but rooting means changing recovery in first place... So... Hen and egg...
Sent from my Moto G5 using XDA Labs
Click to expand...
Click to collapse
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.

Andrej_SK said:
Yes, I rooted my phone by Magisk and used app called Flashify to backup recovery. However, to root, I didn't install TWRP permanently by "fastboot flash recovery twrp.img" command, I just booted into it by "fastboot boot twrp.img", so I was able to root my phone and keep stock recovery installed.
Click to expand...
Click to collapse
Thanks. I had been reading about it and some posts were misleading saying it was no longer possible and others said it was. Had not gotten down to test it yet. So now I know it works, I'll do it. Thanks again.
Sent from my Moto G5 using XDA Labs

Update: tested.
good: Recovery image -12 worked without issue and updater-script check passed.
bad: it failed while validating boot.img.
Apparently, Magisk uninstall did not restore the boot partition to stock. I also had a TWRP backup from when I had just unlocked. Restored boot. No luck. Maybe I took the backup *after* rooting.
well... I guess I will have to wait until I have some free time to do the long way: full flash
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
thanks!!

I am reading this tread form more then 2 days. I already told you I can help but it seems no one want know what I am saying. But it's now seem a serious tread so I will tell in anyway if someone is interested or not.
Guide to repair Moto Lenovo models.
Note: pc, laptop required.
1. Download latest driver for moto device.
2. Download Lenovo Moto smart assistant.
3. Enable usb debugging in developer options.
4. Click on Flash button on top of your tab bar.
5. Click on rescue.
6. Get into bootloader , fastboot.
7. Download your current varient latest firmware.
And all done.
Now you have your firmware with latest security patch.
You can relock bootloader and whatever you like.
Have fun enjoy.

Thanks a lot. This tool won't work if you have lost your IMEI, but it allows you to download the latest firmware (in my case 137-93-14). Using this full stock firmware I have been able to recover the IMEI following the steps explained in other topic in this forum.
Regards.

leohussey said:
EDIT: @Andrej_SK: would you by any chance have the boot.img of *-12 too?
Click to expand...
Click to collapse
I might give it a try, if you give me some time.

Root now posible on (bootloader-unlocked) pie!

Source:
https://www.reddit.com/r/LgV35/comm..._awm/?utm_medium=android_app&utm_source=share
Quote:
1. Extract boot IMG from 9.0 KDZ file
2. Use magisk on phone to patch it
3. Copy the patched boot.img to computer
4. Flash the phone to 8.0 kdz partition dl select boot a boot b
5. Automatically Phone goes into fastboot, use adb to flash the patched boot.img into boot.a boot.b
6. Reset or reflash 9.0 without selecting boot a b

Delete. Link answered question.

how to root withoit octoplus box?

Does this mean that if I was to flash Project Fi KDZ on an ATT V35, I could unlock the bootloader and follow this guide? Thanks in advance for answering my question.

Android# said:
Does this mean that if I was to flash Project Fi KDZ on an ATT V35, I could unlock the bootloader and follow this guide? Thanks in advance for answering my question.
Click to expand...
Click to collapse
Yes but you would want to flash the unlocked kdz. Not Fi as you can't use a crossflashed v35 with Fi because the IMEI won't work on Sprint.

bacon612 said:
Yes but you would want to flash the unlocked kdz. Not Fi as you can't use a crossflashed v35 with Fi because the IMEI won't work on Sprint.
Click to expand...
Click to collapse
Sorry, don't understand what Sprint has to do with rooting ATT sim-unlocked V35 as i am using a T-Mobile MVNO. Reading through the Reddit post it seems you still need bootloader unlocked to follow this guide and from what i am understanding crossflashing V35 will not unlock bootloader? (edit:
I have read through all posts here, no mention of how to unlock bootloader). Thanks.
Edit 2: Actually, please disregard my post as OP post mentions "bootloader unlocked Pie", i just misunderstood.

I guess what I'm saying is that there is no advantage in using Fi with a cross flashed AWM as it will not switch to sprints network. This will throw an error from time to time and will result in the phone only using TMobile.
That said, why not flash the us unlocked kdz as it has no bloat and features that you can't use doe to IMEI limitations.
The only way to bootloader unlock is to use an octopus to flash a file to your phone. You can do this by a) buying an octopus and figuring it out
Or.
B) finding someone to do it for you remotely for a fee.
Pm me if you want details on someone I've used successfuly several times on v35s.
I also have a v350ulm that's mint, flashed to pie and already bootloader unlocked for sale if anyone is interested.
Sent from my GM1915 using Tapatalk

bacon612 said:
I guess what I'm saying is that there is no advantage in using Fi with a cross flashed AWM as it will not switch to sprints network. This will throw an error from time to time and will result in the phone only using TMobile.
That said, why not flash the us unlocked kdz as it has no bloat and features that you can't use doe to IMEI limitations.
Click to expand...
Click to collapse
Right. I don't understand people's obsession with cross flashing to Google Fi firmware when they can't really use Google Fi. They're better off flashing North American Open firmware, to remove bloat.
(Edited for clarification I meant cross flashing.)

Yes. Unless you actually have a ULM
Sent from my GM1915 using Tapatalk

bacon612 said:
Yes. Unless you actually have a ULM
Click to expand...
Click to collapse
Right. I should have specified "cross flashing". (That's what I was thinking.) I'll edit my post.

Can someone please elaborate on how to do steps 4 - 6? I do not know how exactly to do those steps.

@ThatOneGuyOverThere use this guide instead.

bacon612 said:
Yes. Unless you actually have a ULM
Sent from my GM1915 using Tapatalk
Click to expand...
Click to collapse
vlad48 said:
@ThatOneGuyOverThere use this guide instead.
Click to expand...
Click to collapse
What twrp do i use? do i use the stock abl attached to the post? when do i flash the magisk or the patched boot?

1.You need to be on latest ULM Oreo - V350ULM10i
2. Make sure you have checked slider in settings>>system>>developer options ENABLE OEM unlock
3. Enter 9008 and use the guide to flash the abl_a and abl_b only
4. Restart phone into fastboot by pressing Vol- and plugging it to USB cable and execute:
Code:
fastboot oem unlock
!!!beware that all of your data will be erased!!!
5. You can download already magisk patched boot for 10i from here
6. Flash it via fastboot.
Warning - unlocking bootloader ramps your Widevine check to L3 which means that you will not be able to watch Netflix HD content

vlad48 said:
1.You need to be on latest ULM Oreo - V350ULM10i
2. Make sure you have checked slider in settings>>system>>developer options ENABLE OEM unlock
3. Enter 9008 and use the guide to flash the abl_a and abl_b only
4. Restart phone into fastboot by pressing Vol- and plugging it to USB cable and execute:
Code:
fastboot oem unlock
!!!beware that all of your data will be erased!!!
5. You can download already magisk patched boot for 10i from here
6. Flash it via fastboot.
Warning - unlocking bootloader ramps your Widevine check to L3 which means that you will not be able to watch Netflix HD content
Click to expand...
Click to collapse
do i flash the engineering bootloader to both the abl_a and b or just a or b? will the 10i zip upgrade the device to android 9 or will i have to do another step?

Both slots is safer, but if you are sure and know which is your active slot (a or b) flash the abl only on it.

vlad48 said:
Both slots is safer, but if you are sure and know which is your active slot (a or b) flash the abl only on it.
Click to expand...
Click to collapse
will the 10i twrp zip upgrade the phone to android 9 or will i have to do other steps?

Of course not. You will have rooted and bootloader unlocked V35 on Oreo 10i.
For latest Pie 20E you will need to upgrade again via LGUP and perform additional tasks on enabling fastboot again and to flash patched with Magisk boot.img
Be also warned that all of the steps have a high risk of bricking your device, so if you have no idea what are you doing better do not start the process!

vlad48 said:
Of course not. You will have rooted and bootloader unlocked V35 on Oreo 10i.
For latest Pie 20E you will need to upgrade again via LGUP and perform additional tasks on enabling fastboot again and to flash patched with Magisk boot.img
Be also warned that all of the steps have a high risk of bricking your device, so if you have no idea what are you doing better do not start the process!
Click to expand...
Click to collapse
ok thank you sorry about asking all these questions just want to make sure that i do everything right and not screw it up

I still need some clarity with this. Can the at&t variant achieve the bootloader unlock with this method? I've seen that you can cross flash ulm pie onto it with no problem (which I have done myself) but of course the software version is still shown as v350AWM20d