RECOVERY TIPS if you get stuck on logo while updating to this wonky US998 Pie. < Please stop asking in Telegram thread or creating new XDA threads when it's right here. We will just direct you back here. OK?
____________
* Do NOT update to Pie yet if you wish to unlock bootloader in order to root.
For bootloader unlock purposes, use the US998 Oreo KDZ versions with no later than July 2018 security patch: 20a or 20b.
Look at the names for dates in the title in that thread link. AFTER you unlock bootloader, then you can update to newer firmware (like this Pie). Flashing a newer KDZ (like to Pie) will not re-lock your bootloader.
With unlocked bootloader, then on Pie KDZ you can install TWRP and root.
Stable TWRP 3.3.1 is recommended by our TWRP dev for Pie.
To install TWRP (or re-install TWRP on bootloader unlocked Pie) and root, PLEASE follow these instructions for success!
* If you've already updated to Pie with locked bootloader, see post #3 for instructions on how to downgrade to earlier Oreo firmware to first unlock bootloader. Or downgrade back to most recent Oreo because you decided you don't like Pie.
* If you have no desire to unlock bootloader or your bootloader is already unlocked, see full image KDZ and KDZ-based TWRP-flashable zips below.
* ALSO do NOT update to LG stock Pie yet if you wish to run LOS-16 "Pie" custom ROMs -- at least for now. See REASON HERE. Stock Pie update conflicts with LOS-16 Pie, even if you downgrade back to stock Oreo. After stock Pie update, your phone has been permanently changed/degraded when going back to Oreo for custom ROMs. Using Permissive kernel can overcome some of those issues, but you have been warned.
Whereas you do need to update to stock Pie first as a foundation before trying to install "Android 10" LOS-17 custom ROMs. However, those ROMs are still unfinished work in progress -- so if you don't like them and want to go back to the older stable LOS-16 "Pie" custom ROMs, then you've totally ignored the warning above. Again, stock Pie makes permanent changes.
NOTE: After installing Pie, if you get weird lag,
* try this fix. Just make a backup in LG Bridge. Nothing else. Somehow CREATING the backup (but not actually using it to restore anything) re-sets some stuff in Pie, so it acts like it should? I know it sounds strange but it works. Thanks to @thefpspower for the tip!
* OR If that doesn't work or you don't have access to PC, try this: go to Settings> Restart & Reset> Reset App Preferences. Thanks to @HoussiLAM for that tip. Both may do the exact same thing, I've not experimented to see.
I've been reading reports from other LG models (like LG G6), where LG has LG Bridge downgrade the phone back to Nougat first before then updating to Pie. LG Bridge uses full image KDZ, temporarily downloaded to PC.
So for installing the KDZ, I suggest FIRST downgrading to US998 Nougat 10d via Partition DL mode, Master Reset, then Refurbish to US998 Pie KDZ. Here are the steps...
If you have problems flashing this US998 Pie 30b KDZ, see post #6 for FOUR more workaround methods proven to work for some people.
You should probably use this method (DOWNGRADE to NOUGAT first) even if you have TWRP installed. Then reinstall TWRP again after successfully updating to Pie.
KDZ INSTALLATION INSTRUCTIONS
0) Turn off phone, manually go into Download mode before opening Dev Patched LGUP.
1) Using Dev Patched LGUP from THIS thread, flash US998 10d Nougat KDZ via Dev Patched LGUP using Partition DL mode. Select ALL partitions.
2) Master Reset. This is NOT Factory Reset.
3) Boot up to Welcome screen. Turn off phone, manually go back into Download mode.
4) Flash US998 30b Pie KDZ via Dev Patched LGUP using Refurbish mode.
5) Master Reset. This is NOT Factory Reset.
If you did not unlock your bootloader before doing this, then you bootloader is still locked -- because that's what you want. Finished. Set up your phone.
If you had unlocked bootloader before doing all this, you will still have it. Boot to ADB, and PLEASE follow these instructions for re-install TWRP and root!!
[US998][STOCK][PIE]LG V30 US998 US99830b_00_0902.KDZ
3.1GB
Only for North American variants -- EXCEPT T-mobile H932. NOT for H930, H930G, H930D, H930DS!
DOWNLOAD LINKS:
* LG Bridge MIRROR
* Android File Hosts MIRROR
* LG-Firmwares MIRROR
* Mega MIRROR
(Thanks to @HueyT!)
* Google Drive MIRROR
(Thanks to @HueyT!)
md5: 1abe04d95cf000eca9a78e0ea1df4301
TWRP FLASHABLE VERSION (ROM):
(thanks to @JohnFawkes!)
Only for North American variants -- EXCEPT T-mobile H932. NOT for H930, H930G, H930D, H930DS!
See Installation instructions for KDZ. That is your best chance of success. Then re-install TWRP after successfully updating to Pie KDZ. Your bootloader will still be unlocked.
* MAIN DOWNLOAD THREAD (see post #1)
* Android File Hosts MIRROR
md5: 836d739379eb6bfdf7e6f04aa481711e
See Installation instructions for KDZ. That is your best chance of success. Then re-install TWRP after successfully updating to Pie KDZ. Your bootloader will still be unlocked. These instructions below are if you are stubborn and don't want to do that...
Flash the "ROM" with latest TWRP. Flash Magisk + @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler) immediately afterwards before rebooting to system. It's just stock KDZ but in TWRP-flashable version. Not debloated nor meant to be updated in the future. It's just a very convenient mechanism to have newer stock firmware instead of using dev patched LGUP to flash partitions, etc.
This TWRP flashable zip has the new Pie encryption disabled. No encryption enforced, but you can encrypt in TWRP if you want afterwards.
The dev recommends formatting data before installing this TWRP-flashable zip: "format data before flashing, not wipe but format". That's your decision. Others have not.
* Stable TWRP 3.3.1 is recommended by our TWRP dev for Pie.
TWRP-FLASHABLE NOTES:
If those instructions above do not work for you for some reason, then go through these full blown steps (adapted from Section 6 of WTF Instructions):
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the TWRP-flashable zip
d. Install the latest stable Magisk zip.
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Pie, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, please make another TWRP backup.
___________
Screenshot thanks to @fatboysh:
Here's how to flash with LGUP:
----------------------------
UPGRADING LG V30/V30+/V30S TO PIE KDZ FIRMWARE WITH LGUP
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash PIE KDZ either via UPGRADE (to keep your data, but see Note about TWRP) or via REFURBISH or PARTITION DL. If the latter, then in the pop up box "Select All". Use the attached patched LGUP in this post.
* NOTE: YOU CAN NOT USE LGUP "UPGRADE" IF YOU HAVE TWRP CUSTOM RECOVERY. LGUP "Upgrade" is like a manual OTA and is only for pure stock (but you can have unlocked bootloader). If you have TWRP custom recovery and want to use LGUP, then use PARTITION DL OR REFURBISH which will NOT keep your data and will wipe out TWRP. Or use the TWRP-flashable zip (ROM) instead of LGUP, which will keep your data and will keep TWRP.
3) IF your bootloader is unlocked, it will remain unlocked. If it's not unlocked, then you will just be updating to Pie -- but will have to temporarily downgrade to early Oreo if you ever want to unlock bootloader for root.
_________________
HOW TO INSTALL DEV PATCHED LGUP
0. UNINSTALL any prior LGUP version. Seriously. Go to Programs folder and delete the LGUP folder if you must.
1. DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. READ THAT AGAIN.
5. Launch LGUP using the desktop shortcut. NOT from folder icon!
As mentioned before, use UPGRADE, REFURBISH or PARTITION DL modes. REFURBISH and Partition DL are probably best.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
I don't care what anyone else tells you. If you listen to them, let them help you recover from messing up your phone.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
HOW TO (temporarily) DOWNGRADE BACK TO OREO FOR BOOTLOADER UNLOCK
(or DOWNGRADE BECAUSE YOU DON'T LIKE PIE)
1) DOWNLOAD FIRMWARE AND DEV PATCHED LGUP
* Download Oreo KDZ you wish to install -- for bootloader unlock would be US998 20a or 20b.
(If you just don't like Pie, then choose the most recent Oreo KDZ in that thread, which is US998 20h at the top.)
* DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
_________________
2) INSTALL DEV PATCHED LGUP
1. Extract LGUP_DualMode.zip to a folder on your PC.
2. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
3. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
4. Launch LGUP using the desktop shortcut.
Choose Process : PARTITION DL or REFURBISH
----------------------------
3) DOWNGRADING ANY LG V30/V30+/V30S TO EARLIER OREO KDZ FIRMWARE
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash OREO KDZ to DL PARTITION mode. In the pop up box "Select All". Use the attached patched LGUP in this post.
You can also use REFURBISH mode, if you wish.
3) Master Reset (post 101 of Frankenstein thread)
5) DONE.
It's fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again, making sure the files are placed where they need to go (LG Electronics folder, etc).
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
_________________
4) IF YOU NEED TO UNLOCK BOOTLOADER (with early Oreo), GO READ WTF INSTRUCTIONS
ROOT Your LG V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Sticky everyone should read.
____________
EXTRAS
If you root with stock Pie KDZ (after unlocking bootloader in early Oreo), then you will need to flash Magisk modules or manually edit build prop to get root-enabled DTS, Equalizer, and lockscreen weather animations. Dual Speaker mode gives you audio directed at your face, besides the main downward facing speaker. High Impedance Mode give you more volume.
(NOTE: The TWRP flashable zips already have this, thanks to the devs who make them.)
* Fully enable LG DTS 3D stereo (root needed) + Equalizer
* LG V30 Lockscreen EXTRA Weather Animations Enabler
* DUAL SPEAKER MODE + HIM (High Impedance Mode)
SETTINGS
I know everyone has their own settings, but for new owners who want a reference point for all the various submenus and customization, I'll share screenshots of my settings. You can always change to what you like.
https://photos.app.goo.gl/NCm643Y7prJhDLaS2
NOTE:
Four workarounds. Two require unlocked bootloader. If none work for you,
1) make sure you are on the correct Dev Patched LGUP from this thread. (See post #2 for Dev Patched LGUP and follow the installation instructions. Uninstall any prior version of LGUP.)
2) Look over these steps again, make sure you followed them all. Do NOT skip steps!
If it STILL doesn't work, there are no more answers after this. Just flash back to US998 Oreo 20h wait for the next US998 Pie KDZ.
RECOVERY TIPS if you get stuck on logo while updating to this wonky US998 Pie. < Please stop asking in Telegram thread or creating new XDA threads when it's right here. We will just direct you back here. OK?
___________
4 WORKAROUND METHODS TO SUCCESSFULLY UPDATE TO US998 PIE FOR THOSE PEOPLE GETTING STUCK ON ThinQ/ LG LOGO
_____________
METHOD #1 -- WITH OR WITHOUT UNLOCKED BOOTLOADER
I've been reading reports from other LG models (like LG G6), where LG has LG Bridge downgrade the phone back to Nougat first before then updating to Pie. LG Bridge uses full image KDZ, temporarily downloaded to PC.
So I suggest trying to Partition DL back to Nougat KDZ, Master Reset, then Partition DL to Pie KDZ. Here are the steps...
0) Using Dev Patched LGUP from this thread, REFURBISH back to US998 20h. Turn off phone, go into Download mode.
1) Flash US998 10d Nougat KDZ via Dev Patched LGUP using Partition DL mode. Select ALL partitions.
2) Master Reset. This is NOT Factory Reset.
3) Boot up to Welcome screen. Turn off phone, go into Download mode.
4) Flash US998 30b Pie KDZ via Dev Patched LGUP using Partition DL mode. Select ALL partitions.
5) Master Reset. This is NOT Factory Reset.
If you did not unlock your bootloader before doing this, then you bootloader is still locked -- because that's what you want. Finished. Set up your phone.
If you had unlocked bootloader before doing all this, you will still have it. Boot to ADB, and PLEASE follow these instructions for re-install TWRP and root!!
jreed3786 said:
The newest method you just added worked when all others failed! THANK YOU! Donation coming!
Click to expand...
Click to collapse
_____________
This next method by @EstebanxZ uses parts of #1 & #3 (oldest method which works). I'll will rewrite when I get time, but right now just quoting verbatim what worked for him:
METHOD #2 -- NEEDS UNLOCKED BOOTLOADER
EstebanxZ said:
*You need to be on US99820H with unlocked bootloader*
A- First i started with refurbished US99820h
B- Then i proceeded to partition DL US99810d
C- MASTER RESET
D- Booted into OS, let the phone restart and get to the welcome screen, power off then get in bootloader mode
E- Flashed TWRP (fastboot flash recovery twrp.img) then boot to TWRP (fastboot boot twrp.img)
F- In TWRP i did this (in steps): swipe to allow modifications->factory reset->format data and type YES->reboot to recovery->factory reset->wipe system->install US99830b zip->install magisk 20.0->install latest disable verity-dm force-encrypt->install AK3 RTCD remover->reboot to system
and here i am in US99830b with magisk (WHICH is what i really wanted, to have both magisk and android 9)
this is the only way i could get my originally H931 to boot to pie with magisk, i could get to pie with H933 kdz but no magisk, because of no fastboot commands.
Click to expand...
Click to collapse
_______
This third below is our oldest method which works, but is most complicated.
METHOD #3 -- WITH TWRP
We have a working method for people with TWRP who are having trouble getting across the line for Pie. Most people have no problems updating. I didn't. However, for those who are having issues, there's a workaround, but you need TWRP installed and make sure you're using the Dev Patched LGUP from THIS thread. (See post #2 for Dev Patched LGUP and follow the installation instructions. Uninstall any prior version of LGUP.)
For users with TWRP who get stuck on ThinQ/LG logo:
0) Using Dev Patched LGUP from this thread, REFURBISH back to US998 20h. Flash TWRP recovery via fastboot. Turn off phone, go into Download mode.
1) Flash Canada H933 10h Nougat via Dev Patched LGUP using Partition DL mode -- EXCEPT for Recovery partitions, to keep TWRP. Do NOT choose "all" partitions! Omit/UNcheck the Recovery partitions.
Reboot. You will probably have lost download mode, but you've prepped your phone, corrected any partitions -- and you still have TWRP.
____
NOTE: For the next step, you will need to use the much-hated "hardware button dance" to boot to TWRP custom recovery, since H933 firmware doesn't have fastboot flash commands to boot to TWRP from PC. You also no longer have root at this stage, so you can't use the excellent Reboot Recovery app or NOXX Advanced Power Menu app...
You will need to IMMEDIATELY start the "hardware button dance" just time phone reboots. This is the ONLY time I will ever tell you to use the "hardware button dance". Any other time, it's stupid and ridiculous and there are better ways to boot to TWRP custom recovery.
____
2) Flash US99820e TWRP-flashable zip to get back Download mode. (Remember you KEPT TWRP recovery partition!) IF it doesn't boot, make sure you are on Magisk 18.1. Oreo TWRP-flashable zips normally require Magisk 18.x.
3) Then REFURBISH to US998 20h KDZ.
This will temporarily wipe out TWRP, but give you a completely fresh install. You will still have unlocked bootloader and fastboot flash commands.
4) Now flash TWRP recovery again via fastboot flash commands and then flash the US99830b Pie TWRP-flashable zip. See Section 6 of the WTF instructions if you need to remember all the steps to install TWRP, etc.
"Phone booted immediately on pie and everything is working great." - TESTER
You are now on US998 30b Pie!
After all that you can flash to other compatible TWRP-flashable zip if you wish.
_____________
METHOD #4 -- WITH OR WITHOUT UNLOCKED BOOTLOADER
Thanks to @SaiLas:
https://forum.xda-developers.com/showpost.php?p=81499481&postcount=593
ChazzMatt said:
US99830b_00_0902.kdz LG Bridge server link live. Enjoy!
Click to expand...
Click to collapse
Hi,
I have a LS998 converted to US998, will I be able to update from the device or LG Bridge or I need to reflash with LGUP ?
caquito07 said:
Hi,
I have a LS998 converted to US998, will I be able to update from the device or LG Bridge or I need to reflash with LGUP ?
Click to expand...
Click to collapse
You'll need to flash the KDZ with newer Dev Patched LGUP found in this thread, but you can use Upgrade mode which will keep your data.
If you have TWRP and root, you need to wait for @JohnFawkes to create TWRP flashable zip. Unless you want to Refurbish to full KDZ, reinstall TWRP and three root files again.
ChazzMatt said:
You'll need to flash the KDZ with Dev Patched LGUP, but you can use Upgrade mode which will keep your data.
If you have TWRP and root, you need to wait for @JohnFawkes to create TWRP flashable zip. Unless you want to Refurbish to full KDZ, reinstall TWRP and three root files again.
Click to expand...
Click to collapse
I have stock rom, so I will get the KDZ and flash it with Upgrade mode. Thx.
no full kdz yet?
martin_yo said:
no full kdz yet?
Click to expand...
Click to collapse
This is the KDZ thread, so of course there's full KDZ.
Please don't post nonsense anymore.
Giddy up! Thanks for setting this thread up!!
P.S. was hoping for something after 30b, but I'll take it.
ETA: I'm cool with the same version of LGUP I've been using for a while now, right?
jaysus145 said:
Giddy up! Thanks for setting this thread up!!
P.S. was hoping for something after 30b, but I'll take it.
Click to expand...
Click to collapse
Technically (and don't obsess over this whatsoever), this is the KDZ released for U.S. Cellular -- but in the past it made no difference and makes no difference now. We always just grabbed the first US998 KDZ available and has worked fine for almost two years.
I will be curious though when LG releases the "USA" KDZ variant, to see if for some reason it's slightly higher number like 30c (but may be same security patch date).
In the past all US998 firmware are really the same and have had same numbering. There was no difference U.S. Cellular and official Open Market in any way we could tell.
...nvm the question was already asked.
Finally! I've tried several of the AOSP Pie ROMs and always ended up going back to stock Oreo because of the same few issues present on all AOSP ROMs. Now I'm just waiting for the TWRP version of this.
Quick question, since I want to keep my data, should I first disable any and all Magisk modules aimed at Oreo (including Xposed)?
Is it safe to flash to h931 converted and rooted to us998?
Ali1228 said:
Is it safe to flash to h931 converted and rooted to us998?
Click to expand...
Click to collapse
You have two choices:
1) Wait for the TWRP-flashable zip if you want to do it the easy way. @JohnFawkes will create when he has time. Don't ask for ETA, please.
2) Otherwise, flash full Pie KDZ via Refurbish mode with Dev Patched LGUP. You'll still have unlocked bootloader. Then, follow the instruction in post #1 to reinstall TWRP and three root files:
ChazzMatt said:
With unlocked bootloader, then on Pie KDZ you can install TWRP and root.
Stable TWRP 3.2.3.7 is recommended by our TWRP dev -- yes, even on Pie.
To install TWRP and root, PLEASE follow these instructions for success!
Click to expand...
Click to collapse
ChazzMatt said:
You have two choices:
1) Wwait for the TWRP-flashable zip if you want to do it the easy way.
2) Otherwise, flash full KDZ via Refurbish mode with LGUP. You'll still have unlocked bootloader. Then, follow the instruction in post #1 to reinstall TWRP and three root files:
Click to expand...
Click to collapse
So i would choose 2nd option for flashing using refurb to get fresh install
But wanted to confirm if it will work cause there is guy with h930 whos stuck at v30 logo
I have h931 att
Ali1228 said:
So i would choose 2nd option for flashing using refurb to get fresh install
But wanted to confirm if it will work cause there is guy with h930 whos stuck at v30 logo
I have h931 att
Click to expand...
Click to collapse
There's a guy with H930 trying to flash this US998 KDZ who's stuck on V30 logo? This isn't for H930 and is clearly stated in the Download links.
You HAVE H931 right now, or you have already converted H931 to US998 firmware?
If you've ALREADY CONVERTED to any US998 firmware (via Frankenstein method), you can then update to US998 Pie like the instructions say on page 1.
If you are bootloader unlocked and rooted, and you are on AT&T H931 TWRP flashable zip (which you shouldn't be unless you are an AT&T customer) -- simply as a precaution, maybe flash US998 Oreo 20h TWRP flashable zip before flashing full PIE US998 KDZ.
Otherwise wait for US998 Pie TWRP-flashable zip.
jaysus145 said:
ETA: I'm cool with the same version of LGUP I've been using for a while now, right?
Click to expand...
Click to collapse
I have the newer versions of Dev Patched LGUP posted in all the Pie KDZ threads, as well as the WTF and Frankenstein thread. This can handle Pie. Please uninstall all previous versions and read the installation instructions carefully. Any people so far posting with issues didn't follow the installation instructions.
The older version of Dev Patched LGUP is still in the Oreo KDZ threads. It can't handle Pie, but there are uses for it so I'm keeping it there.
Related
Since i have my LG G3 Lollipop rooted by ABD method i want to install Xposed from HERE.
To do that i need have Custom recovery but how put custom recovery without downgrade to Kitkat?
My Lg D855 got lastes stock Lollipop and root.
rockman6 said:
Since i have my LG G3 Lollipop rooted by ABD method i want to install Xposed from HERE.
To do that i need have Custom recovery but how put custom recovery without downgrade to Kitkat?
My Lg D855 got lastes stock Lollipop and root.
Click to expand...
Click to collapse
To put it simply
You cant. If you want TWRP and custom rom you have to downgrade to Kitkat to install it
rockman6 said:
Since i have my LG G3 Lollipop rooted by ABD method i want to install Xposed from HERE.
To do that i need have Custom recovery but how put custom recovery without downgrade to Kitkat?
My Lg D855 got lastes stock Lollipop and root.
Click to expand...
Click to collapse
Try this :- http://forum.xda-developers.com/showthread.php?t=3048845 it's designed to add BUMP and TWRP(Custom Recovery) to Lollipop.....:good:
573v3 said:
Try this :- http://forum.xda-developers.com/showthread.php?t=3048845 it's designed to add BUMP and TWRP(Custom Recovery) to Lollipop.....:good:
Click to expand...
Click to collapse
Hi, first I own LG G3 D855 32gb with previously installed stock LL ANHD 8.3 rom with downgrading to KK rooting method. Today I decided to try fully root following guide from this threat given by @topet2k12001 and after clean installing LL 20H KDZ file I root it with no problem and then I decided to follow guide for installing bump¨d TWRP and aboot.img from KK witch I extracted from latest 10N KK version, only thing I did deferent is that for flashing TWRP and boot.img I used Flashify from playstore and for aboot.img I used Android terminal with commands in guide from this threat. After flashing all and turning off phone then turning it on to enter TWRP it work so I can state that TWRP is working fine, no more error, even I restore my backup (system and data) of rom ANHD 8.3 (LL) I used before this and all is working flawlessly with almost full lollipop rom except aboot.img (KK).
If you do bother to read clearly it requires you to flash the android bootloader which is a risky process since download mode function, bootloader and recovery all depend on it
If not done properly you will brick your phone. So please do not risk it and just downgrade it properly with LG Flash Tool, it will save you so much time.
itsbighead said:
Hi, first I own LG G3 D855 32gb with previously installed stock LL ANHD 8.3 rom with downgrading to KK rooting method. Today I decided to try fully root following guide from this threat given by @topet2k12001 and after clean installing LL 20H KDZ file I root it with no problem and then I decided to follow guide for installing bump¨d TWRP and aboot.img from KK witch I extracted from latest 10N KK version, only thing I did deferent is that for flashing TWRP and boot.img I used Flashify from playstore and for aboot.img I used Android terminal with commands in guide from this threat. After flashing all and turning off phone then turning it on to enter TWRP it work so I can state that TWRP is working fine, no more error, even I restore my backup (system and data) of rom ANHD 8.3 (LL) I used before this and all is working flawlessly with almost full lollipop rom except aboot.img (KK).
If you do bother to read clearly it requires you to flash the android bootloader which is a risky process since download mode function, bootloader and recovery all depend on it
If not done properly you will brick your phone. So please do not risk it and just downgrade it properly with LG Flash Tool, it will save you so much time.
Click to expand...
Click to collapse
Hi @itsbighead,
The "aboot.img" is the Bootloader (Android Bootloader).
The "sbl1.img" is the Secure Bootloader.
The "laf.img" is the Download Mode.
There are three (3) methods available in my thread:
1. "Kitkat Downgrade" method: this is the first method discovered/known to have custom recovery (TWRP) + root on LG G3 Android Lollipop
2. "No Downgrade" method: the reverse approach of the "Kitkat Downgrade" method
3. "Imageprep" method: it's nothing more than an automated script that combines the commands from the "No Downgrade" method. This is created to reduce the risk due to human error (typos, etc. when using the Terminal/Command Line)
The principle in the Kitkat Downgrade Method:
1. From a fully fresh/stock Kitkat, root the device
2. Install a "bump'd" (patched) custom recovery (TWRP)
3. Get a Lollipop Firmware and extract the following image files: system.img, modem.img, and boot.img
4. "Bump" (patch) the boot.img
5. Done
The principle in the No Downgrade Method:
1. From a fully fresh/stock Lollipop...
2. Get a Kitkat Firmware and extract the following image files: aboot.img, laf.img (some users nee to also download other image files like sbl1.img, rpm.img, tz.img, dbi.img, and persist.img)
3. Install a "bump'd" (patched) custom recovery (TWRP)
4. Get a Lollipop boot.img and "bump" (patch) it
5. Flash the "bump'd" boot.img, aboot.img, and laf.img
6. Done
The principle in the Imageprep Method:
1. Basically all the commands that need to be entered are automated in a script
2. Put the corresponding image files mentioned in the No Downgrade Method in the appropriate folders as per the instructions in Imageprep
3. Run the script
4. Done
So as you can see...either way, Kitkat Downgrade and No Downgrade have the same risks. The only difference is "which image files to flash", but essentially you are still flashing image files which, if done improperly, will definitely cause a "soft-brick". In any case, the problems are already anticipated and solutions already documented in the "Troubleshooting and Q&A" section of my thread.
EXTRA: as a matter of fact, it was one of your old posts that led me to understand all of these and therefore, led me to create a script. You are actually listed in the "Credits" section of my thread.
itsbighead said:
Hi, first I own LG G3 D855 32gb with previously installed stock LL ANHD 8.3 rom with downgrading to KK rooting method. Today I decided to try fully root following guide from this threat given by @topet2k12001 and after clean installing LL 20H KDZ file I root it with no problem and then I decided to follow guide for installing bump¨d TWRP and aboot.img from KK witch I extracted from latest 10N KK version, only thing I did deferent is that for flashing TWRP and boot.img I used Flashify from playstore and for aboot.img I used Android terminal with commands in guide from this threat. After flashing all and turning off phone then turning it on to enter TWRP it work so I can state that TWRP is working fine, no more error, even I restore my backup (system and data) of rom ANHD 8.3 (LL) I used before this and all is working flawlessly with almost full lollipop rom except aboot.img (KK).
If you do bother to read clearly it requires you to flash the android bootloader which is a risky process since download mode function, bootloader and recovery all depend on it
If not done properly you will brick your phone. So please do not risk it and just downgrade it properly with LG Flash Tool, it will save you so much time.
Click to expand...
Click to collapse
topet2k12001 said:
Hi @itsbighead,
The "aboot.img" is the Bootloader (Android Bootloader).
The "sbl1.img" is the Secure Bootloader.
The "laf.img" is the Download Mode.
There are three (3) methods available in my thread:
1. "Kitkat Downgrade" method: this is the first method discovered/known to have custom recovery (TWRP) + root on LG G3 Android Lollipop
2. "No Downgrade" method: the reverse approach of the "Kitkat Downgrade" method
3. "Imageprep" method: it's nothing more than an automated script that combines the commands from the "No Downgrade" method. This is created to reduce the risk due to human error (typos, etc. when using the Terminal/Command Line)
The principle in the Kitkat Downgrade Method:
1. From a fully fresh/stock Kitkat, root the device
2. Install a "bump'd" (patched) custom recovery (TWRP)
3. Get a Lollipop Firmware and extract the following image files: system.img, modem.img, and boot.img
4. "Bump" (patch) the boot.img
5. Done
The principle in the No Downgrade Method:
1. From a fully fresh/stock Lollipop...
2. Get a Kitkat Firmware and extract the following image files: aboot.img, laf.img (some users nee to also download other image files like sbl1.img, rpm.img, tz.img, dbi.img, and persist.img)
3. Install a "bump'd" (patched) custom recovery (TWRP)
4. Get a Lollipop boot.img and "bump" (patch) it
5. Flash the "bump'd" boot.img, aboot.img, and laf.img
6. Done
The principle in the Imageprep Method:
1. Basically all the commands that need to be entered are automated in a script
2. Put the corresponding image files mentioned in the No Downgrade Method in the appropriate folders as per the instructions in Imageprep
3. Run the script
4. Done
So as you can see...either way, Kitkat Downgrade and No Downgrade have the same risks. The only difference is "which image files to flash", but essentially you are still flashing image files which, if done improperly, will definitely cause a "soft-brick". In any case, the problems are already anticipated and solutions already documented in the "Troubleshooting and Q&A" section of my thread.
EXTRA: as a matter of fact, it was one of your old posts that led me to understand all of these and therefore, led me to create a script. You are actually listed in the "Credits" section of my thread.
Click to expand...
Click to collapse
Hi @itsbighead. Let me assure you I, "Do bother to read clearly"sic. I do believe that if you had bothered to read the Thread clearly, @topet2k12001 would not have had to post such a lengthy reply...
rockman6 said:
Since i have my LG G3 Lollipop rooted by ABD method i want to install Xposed from HERE.
To do that i need have Custom recovery but how put custom recovery without downgrade to Kitkat?
My Lg D855 got lastes stock Lollipop and root.
Click to expand...
Click to collapse
New Guide root+twrp for 5.0 by auto -scrpit:
http://forum.xda-developers.com/lg-g3/general/d855-one-click-root-twrp-recovery-t3072767
Hi I was wondering if it would be possible to unlock my bootloader and install twrp because my sprint lg g3 is already rooted successfully. Unfortunately I haven't been able to find a method aside from downgrading and I would like to feel safe in knowing that I have a backup. Installing a custom rom is in consideration also so you if you have any recommendations it'd be appreciated.
Thanks, Josh
Sent from my LGLS990 using XDA Free mobile app
u1988 said:
New Guide root+twrp for 5.0 by auto -scrpit:
http://forum.xda-developers.com/lg-g3/general/d855-one-click-root-twrp-recovery-t3072767
Click to expand...
Click to collapse
can confirm this method works. easiest tool available for the newbies.
Do you think that my ls990 already being rooted will affect the outcome?
Sent from my LGLS990 using XDA Free mobile app
kp_q said:
can confirm this method works. easiest tool available for the newbies.
Click to expand...
Click to collapse
I can't, other in the link are happy with the result ,just read it it very easy...
TheJQ54 said:
Do you think that my ls990 already being rooted will affect the outcome?
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/general/d855-one-click-root-twrp-recovery-t3072767
If you ask me,
This Precisely guide are for D855 Only, for ls990 you need the other guides the other told you here.
You need this gudie for other G3 non- D855
http://forum.xda-developers.com/showpost.php?p=59447661&postcount=153
in here I don't know about non-D855
http://forum.xda-developers.com/showpost.php?p=59287063&postcount=1
http://forum.xda-developers.com/showpost.php?p=59944418&postcount=473
573v3 said:
Hi @itsbighead. Let me assure you I, "Do bother to read clearly"sic. I do believe that if you had bothered to read the Thread clearly, @topet2k12001 would not have had to post such a lengthy reply...
Click to expand...
Click to collapse
Buddy go for it. I cant stop you
Dont say i didnt tell you when your phone chucks this error
ERROR : boot certification verify
[630]-----------------------------------------------
[630]
[630] Secure booting Error!
[630] Cause : boot certification verify
[630]
[630]-----------------------------------------------
Sorry to revive this thread. I was wondering that since I currently don't have the capability to unlock my bootloader, what steps would I need to take on my rooted ls990 to replace my stock messaging app with cm12's messaging app. Will it be compatible as I am running lollipop, and if there is a different build of the apk that doesn't need to be ran from the system and can be set as my default messing app please inform me.
Thanks in advance
u1988 said:
New Guide root+twrp for 5.0 by auto -scrpit:
http://forum.xda-developers.com/lg-g3/general/d855-one-click-root-twrp-recovery-t3072767
Click to expand...
Click to collapse
Will this method work for D850?
YoCrae said:
Will this method work for D850?
Click to expand...
Click to collapse
I'm not completely positive but I've been told by some developers that I should wait it out until a method comes that is specifically known to work on ls990. I appreciate the feedback though.
YoCrae said:
Will this method work for D850?
Click to expand...
Click to collapse
Like in the link said: only D855.
for other Non-D855 there is other guides (the links are in post #11 Link).
try Autorec d855 @ playstore...find it and just run it...that's it
Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?
I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.
droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.
charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.
How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx
sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs
Hello!
I'm making a zip which contains stock 2ba software untouched, extracted from the original kdz
Includes:
Stock untouched System
Stock Boot (compatible with Magisk)
Stock MM modem
Install instructions:
- Reboot to TWRP
- Wipe data, cache, system
- Install zip
- Reboot
- Enjoy!
Link:
https://drive.google.com/open?id=1GaPfb_WNUW_4-kd_jk_80OWosbjdCLAv
Link updated! Feel free to upload some mirrors if you want
P.D: Sorry for my bad english
Hello. Thank you very much for the file. Installed everything works. At first I could not understand why there was no root, but then installed Magisk and everything turned out.
I am on a completely stock OTA upgrade version of 2BA, I have NO root, my boot loader is still locked,<as I have still not got around to flashing the UsU method, There for I currently do NOT have a custom recovery installed; such as TWRP; which is listed as a requirement(?) in the first step of following process (to flash a rooted Rom.)
I am curious as to how I will be able to complete these steps, or am I missing something? Is this,supposed a way to gain root on 2BA if you are on a non root version like me, or is this suppose to be a update of your on a previous version which you already have rooted, or is this just a different way to root AFTER you have had the UsU boot loader unlocked?
robles4242 said:
I am on a completely stock OTA upgrade version of 2BA, I have NO root, my boot loader is still locked,<as I have still not got around to flashing the UsU method, There for I currently do NOT have a custom recovery installed; such as TWRP; which is listed as a requirement(?) in the first step of following process (to flash a rooted Rom.)
I am curious as to how I will be able to complete these steps, or am I missing something? Is this,supposed a way to gain root on 2BA if you are on a non root version like me, or is this suppose to be a update of your on a previous version which you already have rooted, or is this just a different way to root AFTER you have had the UsU bootloader unlocked?
Click to expand...
Click to collapse
the only way to root your phone on 2BA is with UsU.
so after you do UsU you can flash TWRP and from there you can flash magisk for root. you don't have to flash this rom for root
here's a side note. when you do the UsU unlock do not flash the baseband package. it gave me problems with my SIM not being detected
ANDROID2468 said:
the only way to root your phone on 2BA is with UsU.
so after you do UsU you can flash TWRP and from there you can flash magisk for root. you don't have to flash this rom for root
here's a side note. when you do the UsU unlock do not flash the baseband package. it gave me problems with my SIM not being detected
Click to expand...
Click to collapse
I tested downgrading from Lineage 15.1 and this ROM Works and TWRP works too! Thanks!
heres a collection of goodies on my Drive for the V35 like LG Radio app, TWRP and Magisk for 8.0 firmware patching. A prepatched image file of oreo or pie i cant remember however I am a bootloader unlocked, LG V35thinQ ATT varient (flashed to google FI and/orUnlocked Firmware) so flash at your own risk. Some of the Root and TWRP file must be patched into the firmware and then flashed via Patched LG UP or im told LGFLASHTOOL patched but i used LG UP. spend $20 and get GhaiPhapAndroid or any other reputable guy with an Octoplus box to unlock your bootloader first then just google LG firmware patching and enjoy!
https://drive.google.com/open?id=1-JgOX88wzIM-fk4vWbnRBUc1r8n3EG8g
-----P.S. TWRP & Magisk is for Oreo ONLY!!!!! the Magisk works fine on Pie however No TWRP. TWRP is a pain in the A$* on A/B devices anyway so just use Pie. If you bootloop just Fastboot flash your Boot.img file ONLY. should bring you back. Never flash Boot_a or any Laf.bin files leave them alone and youll keep fastboot, root and whatnot. Away you go! Bring me some yummy ROMS..... Yum... Yum.....
I want dem ROMS common feed me! nyum, nyum....
Vibrato86 said:
heres a collection of goodies on my Drive for the V35 like LG Radio app, TWRP and Magisk for 8.0 firmware patching. A prepatched image file of oreo or pie i cant remember however I am a bootloader unlocked, LG V35thinQ ATT varient (flashed to google FI and/orUnlocked Firmware) so flash at your own risk. Some of the Root and TWRP file must be patched into the firmware and then flashed via Patched LG UP or im told LGFLASHTOOL patched but i used LG UP. spend $20 and get GhaiPhapAndroid or any other reputable guy with an Octoplus box to unlock your bootloader first then just google LG firmware patching and enjoy!
https://drive.google.com/open?id=1-JgOX88wzIM-fk4vWbnRBUc1r8n3EG8g
-----P.S. TWRP & Magisk is for Oreo ONLY!!!!! the Magisk works fine on Pie however No TWRP. TWRP is a pain in the A$* on A/B devices anyway so just use Pie. If you bootloop just Fastboot flash your Boot.img file ONLY. should bring you back. Never flash Boot_a or any Laf.bin files leave them alone and youll keep fastboot, root and whatnot. Away you go! Bring me some yummy ROMS..... Yum... Yum.....
Click to expand...
Click to collapse
How did you get this to work? I'm on Oreo and I could not integrate this with boot.
Vibrato86 said:
heres a collection of goodies on my Drive for the V35 like LG Radio app, TWRP and Magisk for 8.0 firmware patching. A prepatched image file of oreo or pie i cant remember however I am a bootloader unlocked, LG V35thinQ ATT varient (flashed to google FI and/orUnlocked Firmware) so flash at your own risk. Some of the Root and TWRP file must be patched into the firmware and then flashed via Patched LG UP or im told LGFLASHTOOL patched but i used LG UP. spend $20 and get GhaiPhapAndroid or any other reputable guy with an Octoplus box to unlock your bootloader first then just google LG firmware patching and enjoy!
https://drive.google.com/open?id=1-JgOX88wzIM-fk4vWbnRBUc1r8n3EG8g
-----P.S. TWRP & Magisk is for Oreo ONLY!!!!! the Magisk works fine on Pie however No TWRP. TWRP is a pain in the A$* on A/B devices anyway so just use Pie. If you bootloop just Fastboot flash your Boot.img file ONLY. should bring you back. Never flash Boot_a or any Laf.bin files leave them alone and youll keep fastboot, root and whatnot. Away you go! Bring me some yummy ROMS..... Yum... Yum.....
Click to expand...
Click to collapse
The google drive link you gave is a restricted access link. Please set the link access to anyone so we can download some of these goodies.
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
jmaeshawn said:
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
Click to expand...
Click to collapse
Hi Bro.
Your ROG Phone was CN and did you flash the RAW WW firmware?.
Regards!.
jmaeshawn said:
I have been digging through these forums, but can't find an straight step-by-step guide explaining how you go about manually updating the firmware on this device when you have the bootloader unlocked, TWRP installed, and rooted with Magisk.
I know that having the bootloader unlocked means that the device can no longer get updates automatically and that the updates have to be manually downloaded installed from the ASUS website. But what I don't understand is how to install the firmware from the ASUS website and still keep TWRP recovery and Magisk root.
This is my first time updating the device after I first set it up in January, so I would very much appreciate it if some one knowledgeable could explain this process to me
(In case you need to know, I'm currently on WW-32.2810.2212.241 firmware, with TWRP 3.70_12-0 and Magisk 25.2 installed.)
Click to expand...
Click to collapse
I think twrp will not work properly with android 13 because twrp is made for android 12
Dumper UL full upgrade and you will get Boot.img and recovery.img (keep both files at safe place).
Use magisk manager to patch the boot file.
Keep recovery.img (original A13) and TWRP.img safe in ADB root folder (dont mix them up).
1. Update FOTA to Android 13 by copy UL full upgrade into root folder of your phone. If copy from PC/laptop with cable then unplug the cable, your phone will recognize the package, (if you already change COUNTRY CODE and currently use WW 241 rom that will be success update). Otherwise, reboot your device and pop up will appear. Wait the phone is fully reboot and set up everything.
2. Reboot your phone into download mode/fastboot mode (it's better that you should enable USB debug/Developer mode before doing anything). Using CMD command to flash patched boot from Magisk Manager. And reboot, now your phone could gain back root.
3. Check again if the recovery is gone or not. If it's gone, then use termux or any terminal emulator for the "dd command".
You will gain back the TWRP, if any failed, flash back original recovery.img that you have lately in ADB folder on your PC.
PS: backup everything, since going back from Android 13 to Android 12 need to full factory reset.
Br,
ChrisFeiveel84 said:
I think twrp will not work properly with android 13 because twrp is made for android 12
Click to expand...
Click to collapse
I'm on WW-33.0610.2810.81, and TWRP seems to be working OK so far