LG V30 US998-30b ROMHi!
This Rom is 99% Stock. 3.2.3-7 TWRP should first be installed. Then you can install this Rom and have Pie with working TWRP.
WARNINGS!!!!!
Only for North American variants -- EXCEPT T-mobile H932. NOT for H930, H930G, H930D, H930DS!
This zip is created from the original KDZ. It contains almost the complete 30b firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM is booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop (only 2 extra lines added for DTS, full weather lockscreen)
Unrooted
System image modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
LATEST ZIP
john-fawkes.com US99830b.zip [Click to Download]
OLDER ZIPS
AFH ZIPS [Download]
John-fawkes.com [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 30b firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occur, maybe you need to do a factory reset to start fresh*
Flash the 30b zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 9.0 Pie
Android security patch level: 2019-09-1
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
reserved
reserved
@ChazzMatt
Thank you very much for sharing. Currently downloading
Sent from my LG-H930 using Tapatalk
Wow, that was quick. Thank you very much for all your efforts!
Thank you so much for your flashable zip to stock pie! Before i installed Android 10 and lost my sensors, camera and download mode, but because of your ROM i installed it through TWRP and everything started to work fine. Thank you again, you saved my phone!
I am on a VS996 running stock VS96620k Oreo. I have unlocked bootloader, twrp and root.
Can I switch directly over to US998 Pie via this flashable zip in TWRP or do I need to LGUP Partition DL the kdz?
TIA
idk what the hell is going on when i flash kdz it stucks at v30 logo
when i flash twrp zip it also stucks at v30 logo dont know what to do
Ali1228 said:
idk what the hell is going on when i flash kdz it stucks at v30 logo
when i flash twrp zip it also stucks at v30 logo dont know what to do
Click to expand...
Click to collapse
Downgrade to us998-10d nougat via dual mode lgup, boot up, then kdz 30b
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
taspankya said:
I am on a VS996 running stock VS96620k Oreo. I have unlocked bootloader, twrp and root.
Can I switch directly over to US998 Pie via this flashable zip in TWRP or do I need to LGUP Partition DL the kdz?
TIA
Click to expand...
Click to collapse
Clean flash
HueyT said:
Downgrade to us998-10d nougat via dual mode lgup, boot up, then kdz 30b
Already done didnt work still stuck at v30 logo
not sure why its happening
i am following all everything the kdz thread includes but still not working
oreo and nougat works fine
only stucks at pie
both for kdz and flashable zip
Click to expand...
Click to collapse
Ali1228 said:
HueyT said:
Downgrade to us998-10d nougat via dual mode lgup, boot up, then kdz 30b
Already done didnt work still stuck at v30 logo
not sure why its happening
i am following all everything the kdz thread includes but still not working
oreo and nougat works fine
only stucks at pie
both for kdz and flashable zip
Click to expand...
Click to collapse
i have the same issue
Click to expand...
Click to collapse
Did u guys cross flash to h930-30b before? May need to downgrade to h933-10d instead of us998-10d, then 30b
HueyT said:
Did u guys cross flash to h930-30b before?
Click to expand...
Click to collapse
no i purchased h931 which was rooted converted to us998
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
also i was able to bootloader unlock h931 it was at 20a already and installed twrp to flash us99820h twrp zip
Ali1228 said:
no i purchased h931 which was rooted converted to us998
Click to expand...
Click to collapse
Canadian 10d fixes AOSP looping too. Try partition dl, dual mode lgup, choose all partitions of h93310d, boot up, then us99830b kdz
HueyT said:
Clean flash
Click to expand...
Click to collapse
Sorry, can you define?
taspankya said:
Sorry, can you define?
Click to expand...
Click to collapse
The first part of "How to install" in the OP describes a clean flash. It's wiping the phone clean.
Sent from my LG-US998 using Tapatalk
Do I need the beta "Pie" TWRP to flash this?
Jimmy_Z said:
Do I need the beta "Pie" TWRP to flash this?
Click to expand...
Click to collapse
No. 3.2.3.7.
ChazzMatt said:
No. 3.2.3.7.
Click to expand...
Click to collapse
Has anyone done a dirty flash with the flash zip?
Related
KDZ File:
D85130e_00_0711.zip (KDZ is zipped)
TWRP Flashable Files:
LG-D85130E-Flashable.COMPLETE.zip - all stock with recovery removed (to preserve twrp)
LG-D85130E-Flashable.Boot.zip - stock boot.img
LG-D85130E-Modem.zip - stock modem.img
LG-D85130E-Bootloader - stock bootloader
LG-D85130E-Boot-REPACK - stock boot.img repackaged so SU can be used on stock rom
TWRP / FlashFire installable SuperSU 2.79 ZIP :
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Latest TWRP:
https://dl.twrp.me/d851/twrp-3.0.2-0-d851.img.htmlTWRP 3.0.2 d851 image
all zips and scripst were takes from @autoprime's 30D thread (I was too lazy to make my own)
PLEASE BACK EVERYTHING UP AND FLASH AT YOUR OWN RISK!
Install Directions (coming from rooted and twrped 30d):
1) Copy LG-D85130E-Flashable.COMPLETE.zip + LG-D85130E-Boot-REPACK + SuperSU + Latest TWRP to sdcard or internal memory
2) Reboot into TWRP
3) Flash 1)files in the same order you copied. DO NOT REBOOT IN BETWEEN FLASHING. FLASH ALL 4 FILES AT THE SAME TIME.
4) Reboot wipe/cache and davlvik
Install Directions (coming from 30E no root and no twrp)
1) You can't get into twrp and you lost root. No problem.
2) Use LGUP to flash back to 30d (search xda forums)
3) Start up MM 30d
4) Copy kingroot to /sdcard or internal memory
5) Run kingroot and you'll have t...velopers.com/member.php?u=3771760"]aclegg2011
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-10-11
Last Updated 2017-02-23
screenshots
Some ScreenShots!
Even works on cm14!
Bootloader + modem seems to work just fine on cm14.
Nice. I had flashed Resurrection Remix ROM a few days ago, but it wasn't stable. Rebooted several times when I tried to manually input a phone number in dialer. Also, it took far too long to boot. About twice as long as Stock. So now I am back to Stock, still rooted on 30D & I just got hit with an OTA update notification.
How is CM 14 doing for you in regards to heat issues, Bluetooth connectivity and camera quality?
eeo1122 said:
Nice. I had flashed Resurrection Remix ROM a few days ago, but it wasn't stable. Rebooted several times when I tried to manually input a phone number in dialer. Also, it took far too long to boot. About twice as long as Stock. So now I am back to Stock, still rooted on 30D & I just got hit witave h an OTA update notification.
How is CM 14 doing for you in regards to heat issues, Bluetooth connectivity and camera quality?
Click to expand...
Click to collapse
I don't use my g3 for daily use so I can't tell you about what issues. The Bluetooth seems to work, but I haven't tested it totally yet. I need to update the g3 vendor and configs to 30e and make sure nothing is broken.
From where do I download the SU.zip file?
Working so far! Thank You!
aclegg2011 said:
KDZ File:
D85130e_00_0711.zip (KDZ is zipped)
TWRP Flashable Files:
LG-D85130E-Flashable.COMPLETE.zip - all stock with recovery removed (to preserve twrp)
LG-D85130E-Flashable.Boot.zip - stock boot.img
LG-D85130E-Modem.zip - stock modem.img
LG-D85130E-Bootloader - stock bootloader
LG-D85130E-Boot-REPACK - stock boot.img repackaged so SU can be used on stock rom
all zips and scripst were takes from @autoprime's 30D thread (I was too lazy to make my own)
PLEASE BACK EVERYTHING UP AND FLASH AT YOUR OWN RISK!
XDA:DevDB Information
[STOCK] D851 30E KDZ + Flashable ZIPs (MM), ROM for the T-Mobile LG G3
Contributors
aclegg2011
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-10-11
Last Updated 2016-10-11
Click to expand...
Click to collapse
Working so far, Thank You!!
Hi and thanks for the uploads! My questions is, if I'm already on stock 30D what files do I need to flash in order to only update. Or do I need to flash the complete 1.1GB package? Thanks in advance!
FMSL said:
Hi and thanks for the uploads! My questions is, if I'm already on stock 30D what files do I need to flash in order to only update. Or do I need to flash the complete 1.1GB package? Thanks in advance!
Click to expand...
Click to collapse
bootloader and modem
aclegg2011 said:
bootloader and modem
Click to expand...
Click to collapse
Thanks. Just flashed it. In the Software Version it still displays D85130d. Is it something I missed?
Used TWRP to dirty flash Complete, Boot Repack, and latest SU from the link in post 1 of the 30d thread, in that order, on a phone with 30d rooted, and everything seems to be working correctly. Still rooted, showing 30e in software version.
FMSL said:
Thanks. Just flashed it. In the Software Version it still displays D85130d. Is it something I missed?
Click to expand...
Click to collapse
tha's because you didn't want to flash the whole rom. You're bootloader and modem are on 30E, but you're still using the 30D rom.
aclegg2011 said:
tha's because you didn't want to flash the whole rom. You're bootloader and modem are on 30E, but you're still using the 30D rom.
Click to expand...
Click to collapse
Ok, I understand what I did and thank you for the explanation. I'm kinda of a noob when it comes to ROMs and for a moment I thought this was the OTA from D to E but breakdown into separate files. Guess I have to flash the ROM compelety. Again, thanks for all the work to do!
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
danam said:
Used TWRP to dirty flash Complete, Boot Repack, and latest SU from the link in post 1 of the 30d thread, in that order, on a phone with 30d rooted, and everything seems to be working correctly. Still rooted, showing 30e in software version.
Click to expand...
Click to collapse
Did it boot up normally, or did you have to go through the process of setting up a new phone? (enter email, restore apps, etc) Thanks.
So this only changes the software version. I'm on
D85130D, is there anything different in this ROM.??
Another question. If I only want to run the stock without root what do I flash.
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
[/COLOR]
Did it boot up normally, or did you have to go through the process of setting up a new phone? (enter email, restore apps, etc) Thanks.[/QUOTE]
Yes. Dirty flash (just cleared cache and dalvik, but not data or full wipe) preserved all settings. Took a couple of minute to boot and update apps, but everything was preserved. Only dirty flash if you are coming from stock or rooted stock, not from any other rom.
danam said:
---------- Post added at 10:01 PM ---------- Previous post was at 09:56 PM ----------
Yes. Dirty flash (just cleared cache and dalvik, but not data or full wipe) preserved all settings. Took a couple of minute to boot and update apps, but everything was preserved. Only dirty flash if you are coming from stock or rooted stock, not from any other rom.
Click to expand...
Click to collapse
Dirty Flashed using TWRP 3.0 over 30D (Rooted+Stock) by clearing Dalvik and Cache.
* First boot took a while.. roughly 20-25 minutes for Optimizing App (as I have around 250 Apps)
* Took 23% of my battery (flashing to first boot -- Surprised!)
* Ubuntu 16 no longer detecting phone (no charging or MTP) was working fine before update
* Lost Root Access -- SuperSU no longer works.. says SU Binary not installed (was working before)
* Tried KingRoot 4.8.2 for temp root , NO LUCK! (root is gone)
* Rebooted - Ubuntu is detecting the phone now
* Bloatware are back
googled .. couldn't find any root method for this update.
Anyone has info.. how to root 30E?
---------- Post added at 06:37 AM ---------- Previous post was at 06:31 AM ----------
UPDATE
=======
Battery's dropping FAST!!! (from 77% to 66% in few minutes of standby)
UPDATE 2
========
Flashed Boot Repack, and latest SU .. ROOT is back!
Battery Draining FAST!
This one is a working method 30E+ROOT+TWRP.
Thanks
Working fine so far. Thanks a lot!
Worked for me too. Thanks.
BTW, I did the dirty flash option. and followed danam's post.
http://forum.xda-developers.com/showpost.php?p=69116733&postcount=11
So for clarity, I just want to make sure I'm doing this right if someone can chime in. I currently have a D851 with Lollipop 5.0 CloudyG3 2.5 rom unrooted with TWRP recovery. If i wanted to upgrade to 30E KDZ, i have to do the following:
1. upgrade to 30e kdz firmware using LG Flash Tool
2. use twrp to flash the complete flashable zip
thats all I have to do?
forevergone said:
So for clarity, I just want to make sure I'm doing this right if someone can chime in. I currently have a D851 with Lollipop 5.0 CloudyG3 2.5 rom unrooted with TWRP recovery. If i wanted to upgrade to 30E KDZ, i have to do the following:
1. upgrade to 30e kdz firmware using LG Flash Tool
2. use twrp to flash the complete flashable zip
thats all I have to do?
Click to expand...
Click to collapse
If you flash the KDZ, it'll erase TWRP and you won't be able to get root.
I flashed a modified bootloader to use magisk with oos as it forced seslinux to premissive
now i need to go back to stock bootloader
can anyone provide me zip for the stock bootloader so i can flash it throught twrp
the modified bootloader thread
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
the mordified bootloader zip file is in the download links ->magisk 14.3 zip-> oneplus_bootloader.zip
this might also help
https://www.xda-developers.com/onep...ng-of-selinux-to-permissive-mode-in-fastboot/
file also attached mordified bootloader
indroider said:
I flashed a modified bootloader to use magisk with oos as it forced seslinux to premissive
now i need to go back to stock bootloader
can anyone provide me zip for the stock bootloader so i can flash it throught twrp
the modified bootloader thread
https://forum.xda-developers.com/oneplus-3t/how-to/magisk-oxygen-os-8-0-op3-3t-t3689901
the mordified bootloader zip file is in the download links ->magisk 14.3 zip-> oneplus_bootloader.zip
this might also help
https://www.xda-developers.com/onep...ng-of-selinux-to-permissive-mode-in-fastboot/
file also attached mordified bootloader
Click to expand...
Click to collapse
Simply dirty flash the ROM.
tnsmani said:
Simply dirty flash the ROM.
Click to expand...
Click to collapse
Its not wot m looking for.. Bootloader will not go enforced by its own . so.. Looking for bootloader stock zip
Hoping it's not too late: have you looked there?
Simone98RC said:
Hoping it's not too late: have you looked there?
Click to expand...
Click to collapse
No boot loader there
Just firmwares n boot logos
Still thanks for trying
indroider said:
No boot loader there
Just firmwares n boot logos
Still thanks for trying
Click to expand...
Click to collapse
Sure? You're wrong: the mentioned link include only bootloader+modem that are coming with every OOS release.
There's no system partition, because that packages are built for custom rom users.
I used them for a long time, until I went back to modded stock.
Ps also full firmware include bootloader+modem partitions, otherwise you would get in hard brick especially with major updates.
Are you referring to a particular partition? What you mean for firmware?
Simone98RC said:
Sure? You're wrong: the mentioned link include only bootloader+modem that are coming with every OOS release.
There's no system partition, because that packages are built for custom rom users.
I used them for a long time, until I went back to modded stock.
Ps also full firmware include bootloader+modem partitions, otherwise you would get in hard brick especially with major updates.
Are you referring to a particular partition? What you mean for firmware?
Click to expand...
Click to collapse
Yes they do include that bootloader img i have tried flashing multiple boot images but i used a bootloader zip from. A dev that changed the setting of my selinux of bootloader from enforced to permissive in order to use magisk 14.2 with oos as magisk earlier didnt support enforced state.... That is only poossible to replace when you have a bootloader zip that include instructions to do so .. So the default bootloader zip will have that instruction as default values
Did you find any solution?
theo.j22 said:
Did you find any solution?
Click to expand...
Click to collapse
Yes just flash community beta of pie n bootloader will be updated to stock settings
For bootloader unlock purposes, use the US998 KDZ versions with pre-July 2018 security patch: I recommend 20a or 20b.
Look at the names for dates in the title. You can always update to newer firmware later, AFTER bootloader is unlocked. Flashing a newer KDZ will not relock your bootloader. See bottom of post for instructions on how to downgrade to earlier firmware.
____________
US99820h_00_0318.kdz
2.8GB
DOWNLOAD LINKS:
* Android File Hosts MIRROR
* LG Bridge server MIRROR
(Thanks to @Redline!)
* LG-Firmwares MIRROR
md5: 9915d400f3f815afe457188179973dfa
TWRP FLASHABLE VERSION:
(thanks to @JohnFawkes!)
https://androidfilehost.com/?fid=1395089523397938154
AFH MIRROR: https://www.androidfilehost.com/?fid=1395089523397941723
AFH MIRROR: https://www.androidfilehost.com/?fid=1395089523397942132
MEGA MIRROR: https://mega.nz/#F!oqZXmaYL!-kIP78wxilXLbg5SLeFwOw
(Thanks @cityneversleepz!)
md5: 6d74ab2618b5065bcb1c9d90b3f7e6b0
ONLY USE MAGISK 18.X ON OREO TWRP-FLASHABLE ZIPS!
If you are installing/updating latest US998 firmware for the first time after bootloader unlock/root, you should flash 20e zip (below), then 20f zip, 20g zip, 20h zip back-to-back in TWRP, then flash Magisk. If you go straight to 20h via TWRP-flashable zip from very early Oreo, you will most likely have problems. There were massive changes starting with US998 20f and you need the prior 20e as foundation before going on to 20h. You should also do this if coming from a custom ROM.
JohnFawkes said:
Also flashing magisk in between each and rebooting in between each is not needed. You can add all (zips) to the queue and flash at once then flash magisk and then reboot. Tested this method with the us998 zips and works just fine
Click to expand...
Click to collapse
Flash the "ROM" with latest TWRP, after wiping caches. Reflash Magisk 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. Go to this thread and thank him.
Screenshots below are for previous firmware and only demonstrate how to upgrade full KDZ using LGUP.
__________
PREVIOUS FIRMWARE
US99820g_01_0110.kdz
2.8GB
DOWNLOAD LINKS:
* Android File Hosts MIRROR * MIRROR
* LG Bridge server MIRROR
* LG-Firmwares MIRROR
md5: 8FF267DECE84CB3ABC690AC57D3F5F7B
TWRP FLASHABLE VERSION:
(thanks to @JohnFawkes!)
https://androidfilehost.com/?fid=11410963190603907012
MEGA MIRROR: https://mega.nz/#F!oqZXmaYL!-kIP78wxilXLbg5SLeFwOw
(Thanks @cityneversleepz!)
AFH MIRROR: https://www.androidfilehost.com/?fid=6006931924117905842
md5: 04bc62b70a6c06a3f3f072307b63d9ea
ONLY USE MAGISK 18.X ON OREO TWRP-FLASHABLE ZIPS!
Flash the "ROM" with latest TWRP, after wiping caches. Reflash Magisk 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.
Screenshots below are for previous firmware and only demonstrate how to upgrade full KDZ using LGUP.
__________
PREVIOUS FIRMWARE
US99820f_00_1121.kdz
2.8GB
DOWNLOAD LINKS:
* Android File Hosts MIRROR
* LG-Firmwares MIRROR
md5: 902477d9c5bcb92797f7018b1b8a2bd3
TWRP FLASHABLE VERSION:
(thanks to @JohnFawkes!)
https://androidfilehost.com/?fid=11410963190603889519
MEGA MIRROR: https://mega.nz/#F!oqZXmaYL!-kIP78wxilXLbg5SLeFwOw
(Thanks @cityneversleepz!)
AFH MIRROR: https://www.androidfilehost.com/?fid=6006931924117905841
md5: fc2ae3a3a9fe3d274ee8305f1f9da21c
ONLY USE MAGISK 18.X ON OREO TWRP-FLASHABLE ZIPS!
Flash the "ROM" with latest TWRP, after wiping caches. Reflash Magisk 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.
Screenshots below are for previous firmware and only demonstrate how to upgrade full KDZ using LGUP.
__________
PREVIOUS FIRMWARE
US99820e_02_0910.kdz
2.8GB
DOWNLOAD LINKS:
* Android File Hosts MIRROR
* Mega MIRROR
md5: 1356de6f4856b5e4ac9c5d719426ee15
TWRP FLASHABLE VERSION:
(thanks to @JohnFawkes!)
https://androidfilehost.com/?fid=11410963190603889520
AFH MIRROR: https://www.androidfilehost.com/?fid=6006931924117905843
MEGA MIRROR: https://mega.nz/#F!oqZXmaYL!-kIP78wxilXLbg5SLeFwOw
(Thanks @cityneversleepz!)
md5: 3fb2d258b37dbfc5195ebd207bbb9765
ONLY USE MAGISK 18.X ON OREO TWRP-FLASHABLE ZIPS!
Flash the "ROM" with latest TWRP, after wiping caches. Reflash Magisk 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.
Screenshots below are for previous firmware and only demonstrate how to upgrade full KDZ using LGUP.
__________
PREVIOUS FIRMWARE
US99820d_01_0710.kdz
2.76GB
DOWNLOAD LINKS:
* Android File Hosts MIRROR
AFH Mirror: https://www.androidfilehost.com/?fid=6006931924117906091
md5: A85265F221E082D699680B3117D0F20D
TWRP FLASHABLE VERSION:
(Thanks to @westwood24!)
https://forum.xda-developers.com/lg-v30/development/rom-lg-us998-20d-rom-t3830318
md5: c09d4cd31171cc2a5a325ae41b7aa79f
ONLY USE MAGISK 18.X ON OREO TWRP-FLASHABLE ZIPS!
Flash the "ROM" with latest TWRP, after wiping caches. Reflash Magisk 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.
Screenshots below are for previous firmware and only demonstrate how to upgrade full KDZ using LGUP.
__________
PREVIOUS FIRMWARE
US99820c_03_0615.kdz
2.8GB
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5: c5590e7a6b5baa2e14f7d4cc6f34925e
__________
PREVIOUS FIRMWARE
US99820b_03_0524.kdz
2.76GB
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5: 66b32b2d332a876889b6a74ba8d8be7c
TWRP FLASHABLE VERSION:
(Thanks to @westwood24)
https://forum.xda-developers.com/lg-v30/development/rom-lg-us998-20b-rom-t3813923
md5: 056f3e7e5fa6dd1c5c8d92bd8ba731ff
ONLY USE MAGISK 18.X ON OREO TWRP-FLASHABLE ZIPS!
Flash the "ROM" with latest TWRP. Reflash Magisk 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.
Screenshots below are for previous firmware and only demonstrate how to upgrade full KDZ using LGUP.
__________
PREVIOUS FIRMWARE
US99820a_04_0330.kdz
3GB
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5: 5654DD3238DB691C1E6E633FE16092C4
* CODEFIRE (Thanks to XDA dev @autoprime.)
______________
NOTE: This is for all V30/V30+/V30S US998 -- open market US998 V30/V30+/V30S, as well as U.S Cellular US998 V30/V30+.
Here's my own US998 V30+ updating:
{
"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"
}
__________
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. You can update to more current firmware AFTER unlocking bootloader on early Oreo.
(If you just don't like Pie, then choose the most recent Oreo KDZ, 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
0. Uninstall any prior LGUP you have. Uninstall anything like Uppercut, which no longer works and causes conflicts with this 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, NOT the Install folder shortcut.
Choose Process : PARTITION DL (all partitions) or REFURBISH
----------------------------
3) DOWNGRADING/UPGRADING ANY LG V30/V30+/V30S TO 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
_________________________
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
Yesss! Finally. Thanks. I hope this will lead to new weta rom.
ChazzMatt said:
DOWNLOADING NOW. Be patient.
Thanks to @autoprime.
use this download link until I get and Android Hosts file link.
http://downloads.codefi.re/autoprime/LG/LG_V30/US988/US99820a_04_0330.kdz
Click to expand...
Click to collapse
Sent from my LG-US998 using Tapatalk
agamemnonn said:
Yesss! Finally. Thanks. I hope this will lead to new weta rom.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
We now have two working download links -- Android File Hosts and Codefire. I'll add the LG Bridge server link when it becomes available. Now I have to actually flash it myself!
DONE. See screenshots.
Thanks for this. So what all do we need to do in order to root again after upgrading? I assume this wipes everything, correct? So do we need to re-flash the new TWRP after we upgrade, then format data and flash the no verity script again, then install magisk? Or is the format data and flash no verity not needed if we've already done that on Nougat? I'm pretty new to using KDZs.
jeston said:
Thanks for this. So what all do we need to do in order to root again after upgrading? I assume this wipes everything, correct? So do we need to re-flash the new TWRP after we upgrade, then format data and flash the no verity script again, then install magisk? Or is the format data and flash no verity not needed if we've already done that on Nougat? I'm pretty new to using KDZs.
Click to expand...
Click to collapse
EDIT: changing this answer based on people's experiences.
Yes, you will lose root and custom TWRP recovery. You'll have flash/reinstall those. Be sure to use the Oreo compatible TWRP 3.2.1:
https://forum.xda-developers.com/lg-v30/development/unofficial-twrp-3-2-1-t3779171/page8
ChazzMatt said:
EDIT: changing this answer based on people's experiences.
Yes, you will lose root and custom TWRP recovery. You'll have flash/reinstall those. Be sure to use the Oreo compatible TWRP 3.2.1:
https://forum.xda-developers.com/lg-...t3779171/page8
Click to expand...
Click to collapse
Thanks, will work on this tomorrow when I have more time!
jeston said:
Thanks, will work on this tomorrow when I have more time!
Click to expand...
Click to collapse
Yes, I updated my still-bootloader locked US998 V30+ immediately. I'll do my bootloader unlocked, rooted US998 V30 later...
I just relock bootloader before flashing. But now i have warning "your device has failed a routine safety check and will not boot" and does not even get into bootloader mode. Do you have any idea?
agamemnonn said:
I just relock bootloader before flashing. But now i have warning "your device has failed a routine safety check and will not boot" and does not even get into bootloader mode. Do you have any idea?
Click to expand...
Click to collapse
See this thread for the V20 but you need KDZ for the V30.
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
You should still be able to use Oreo KDZ and LGUP, I would think.
_______
EDIT:
After further discussion, I've removed instructions to re-lock the bootloader as people have successfully upgraded without doing that.
ChazzMatt said:
See this thread for the V20 but you need KDZ for the V30.
https://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903
You should still be able to use Oreo KDZ and LGUP, I would think.
I just know if you don't relock the bootloader you have problems then relocking it after flashing the update.
Click to expand...
Click to collapse
I dont know how but i could enter bootloader finally. I just unlocked again. I guess problem was that i was on custom rom with TWRP. now first, flashing 10d kdz, and then relock and then i will flash oreo.
Deleting this post as information has changed. Do NOT re-lock the bootloader.
ChazzMatt said:
Very important question! Make sure you relock the bootloader first before flashing this KDZ update. Then, you will need your unlock.bin file again, which LG sent you. You will unlock the bootloader again, after you install the Oreo KDZ.
Then root and install TWRP like you did before.
If you flash this KDZ upgrade without relocking the bootloader, you will be stuck in a no-man's land where you will be told you need to unlock the bootloader but another place (Developer Options) will tell you it's already unlocked.
How to re-lock bootloader for open market LG G6, but should be the same for LG V30:
https://www.androidexplained.com/lg-g6-lock-bootloader/
Click to expand...
Click to collapse
i didn't relock the bootloader and haven't had any issues
Updated my US Cellular V30 with no issues! Thank you for the guide Chazz!
Sent from my LG-US998 using Tapatalk
Shadicbypass said:
i didn't relock the bootloader and haven't had any issues
Click to expand...
Click to collapse
Really? I was just going by what happened in another thread.Fantastic if we don't have to, for those who have unlocked BOOTLOADER. I'll change instructions when I get home.
You just had unlocked bootloader and root, no custom ROM?
I'm updating my other phone with unlocked bootloader tomorrow.
Hey here we go let's toss a coin heads we relock the bootloader tails we don't and see what happens LOL
All I know is I updated a couple times with the kdz so far and never relocked, but that was just nougat to nougat. Wasn't sure if it was different for nougat to Oreo.
jeston said:
All I know is I updated a couple times with the kdz so far and never relocked, but that was just nougat to nougat. Wasn't sure if it was different for nougat to Oreo.
Click to expand...
Click to collapse
Tomorrow I'll test with my bootloader unlocked V30.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Tomorrow I'll test with my bootloader unlocked V30.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I just did and it worked for me
foamerman said:
I just did and it worked for me
Click to expand...
Click to collapse
Thank you. I removed it from the op. Now I need to edit post #5.
ChazzMatt said:
Really? I was just going by what happened in another thread. Maybe he was running a custom ROM. I'll change instructions when I get home.
You just had unlocked bootloader and root, no custom ROM?
Click to expand...
Click to collapse
yeah stock nougat to stock oreo, i was actually using weta rom but still based on stock so...
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.
Hello,
Boot.img for Rog Phone II patched with Magisk 7.5.1:
update WW-17.0240.2007.27
Patched
Stock boot.img
update WW-17.0230.2004.60
Patched
Stock boot.img
update WW-17.0210.2001.60.
Patched Mirror 1
Patched Mirror 2
Stock boot.img
If you need other version boot.img patched with Magisk just comment or msg me.
Very very thanks
I need it
thank you!
Stuck on bootloop while updating to Android 10
How did you update your phone while keeping magisk? I tried updating via OTA, did not restart and then flashed Magisk 7.5.3 on inactive slot and then rebooted my phone. Now it is stuck on bootloop.
Even the TWRP is gone but the stock recovery shows that the update is installed.
Do you know any way as to how I can fix this?
I have unlocked bootloader so im not using OTA, just downloading updates from Asus site, after update and phone restart you lose magisk, you have to install magisk manager APK, then via fast_boot install patched boot.img.
That's why i uploaded patched boot.img for 17...., u always have to repeat it after updating.
Right now just flash stock ROM
Ushrael said:
I have unlocked bootloader so im not using OTA, just downloading updates from Asus site, after update and phone restart you lose magisk, you have to install magisk manager APK, then via fast_boot install patched boot.img.
That's why i uploaded patched boot.img for 17...., u always have to repeat it after updating.
Right now just flash stock ROM
Click to expand...
Click to collapse
I also have rooted my device. I downloaded the update zip, kept it on internal storage. rebooted my device and when the update notification showed i updated and did not reboot.
Then i went to magisk and installed the magisk to inactive slot and then went onto reboot my device but now i am stuck on a bootloop.
Today only i updated to A10. Can some tell me how to root and install magisk? I will really appreciate your support.
Spawn_Ishan said:
did not reboot.
Click to expand...
Click to collapse
IDK why did u done it, but maybe installing stock boot.img will help u, install stock same as your rom version.
husen4u said:
Today only i updated to A10. Can some tell me how to root and install magisk? I will really appreciate your support.
Click to expand...
Click to collapse
I can't post links, but just type in google Rog phone 2 magisk, even on XDA u have some instructions, just take my patched boot.img if u have version WW-17.0210.2001.60 instead
Ushrael said:
IDK why did u done it, but maybe installing stock boot.img will help u, install stock same as your rom version.
I can't post links, but just type in google Rog phone 2 magisk, even on XDA u have some instructions, just take my patched boot.img if u have version WW-17.0210.2001.60 instead
Click to expand...
Click to collapse
Installing the stock boot image helped me boot my device, but installing magisk causes a bootloop everytime and even if i try to flash twrp, the phone boots only into twrp and not the system.
Also tried using your patched boot image and tried patching a boot image myself from the magisk manager app but still causes bootloop.
---------- Post added at 10:34 PM ---------- Previous post was at 10:13 PM ----------
Ushrael said:
Hello,
If some1 need boot.img for Rog Phone II update WW-17.0210.2001.60.
Patched with Magisk 7.5.1:
Mirror 1
Mirror 2
Stock boot.img
If you need other version boot.img patched with Magisk just comment or msg me.
Click to expand...
Click to collapse
Can i have a boot.img flashed from magisk manager 7.5.3?
Click to expand...
Click to collapse
where did u found 7.5.3? newest is 7.5.1
Do u have WW or CN ROM
Ushrael said:
where did u found 7.5.3? newest is 7.5.1
Do u have WW or CN ROM
Click to expand...
Click to collapse
I have 7.5.1, i confused the manager version.
I have WW Rom.
Stock image booting works just fine, i can even boot twrp but when i flash magisk the system goes in a bootloop.
Spawn_Ishan said:
I have 7.5.1, i confused the manager version.
I have WW Rom.
Stock image booting works just fine, i can even boot twrp but when i flash magisk the system goes in a bootloop.
Click to expand...
Click to collapse
If u are using TWRP just download magisk 20.3.zip file and flash it with twrp. Don't use patched boot.img.
Ushrael said:
If u are using TWRP just download magisk 20.3.zip file and flash it with twrp. Don't use patched boot.img.
Click to expand...
Click to collapse
Tried that first but it causes bootloop, thats when i resorted to patched boot. Dont know why but flashing magsik anyhow causes a bootloop.
Was able to install magisk after i reset my phone.
can i use your bootstock for relock my android 10? is it possible flash by minimal adb and fastboot?
Fresh boot.img for version WW-17.0230.2004.60
I followed this guide: https://forum.xda-developers.com/ro...-check-change-fingerprint-cn-to-t4002279/amp/
And then i did the update to WW-17.0230.2004.60 and lost root.
How I can root again?
Thank you for share!
Spawn_Ishan said:
Installing the stock boot image helped me boot my device, but installing magisk causes a bootloop everytime and even if i try to flash twrp, the phone boots only into twrp and not the system.
Also tried using your patched boot image and tried patching a boot image myself from the magisk manager app but still causes bootloop.
---------- Post added at 10:34 PM ---------- Previous post was at 10:13 PM ----------
Click to expand...
Click to collapse
did you ever find a solution? I want to update from Android 9 but don't want to end up in your situation.
boot.img for update WW-17.0240.2007.27
Thank you ?????
hi friends, can you tell me please, i have WW installed with twrp, what steps have to do if i want update from another zip update? to avoid problems with encryption for example, or problems with boot img because i have root with magisk, thank you