hello so i got a refurbished us998 on android 7.1 i couldnt get it to update vie ota so i flashed oreo firmware with lgup after that i unlocked bootloader and installed twrp all good but after that i wanted to update to pie so i can install android 10 custom roms i flashed the pie kdz and i got stuck at lg logo couldn't boot then i tried with flashable zip same i tried flashing back 7.1 then to pie that didnt work then i flashed all the oreo zip from build 820e to 820h as mentioned in a thread and then pie
that didnt work as well so i tried to flash lineage os 16 or and other pie roms same thing they all dont boot up and got stuck on logo so is there any other ways to try that would be appreciated
stifbaker7 said:
hello so i got a refurbished us998 on android 7.1 i couldnt get it to update vie ota so i flashed oreo firmware with lgup after that i unlocked bootloader and installed twrp all good but after that i wanted to update to pie so i can install android 10 custom roms i flashed the pie kdz and i got stuck at lg logo couldn't boot then i tried with flashable zip same i tried flashing back 7.1 then to pie that didnt work then i flashed all the oreo zip from build 820e to 820h as mentioned in a thread and then pie
that didnt work as well so i tried to flash lineage os 16 or and other pie roms same thing they all dont boot up and got stuck on logo so is there any other ways to try that would be appreciated
Click to expand...
Click to collapse
In the US998 Pie KDZ thread, there's several methods to get to Pie. Look at post #2 and post #6. It sounds like you tried some of those, but read again carefully. Method #4 in post #6 seems to work for almost everyone.
You can't flash LOS-16 immediately after failing to update to Pie. Enough Pie infected the partitions that it will not work. So, if you want LOS-16 you have to flash back to Oreo first. LOS-16 needs Oreo blobs (drivers).
ChazzMatt said:
In the US998 Pie KDZ thread, there's several methods to get to Pie. Look at post #2 and post #6. It sounds like you tried some of those, but read again carefully. Method #4 in post #6 seems to work for almost everyone.
You can't flash LOS-16 immediately after failing to update to Pie. Enough Pie infected the partitions that it will not work. So, if you want LOS-16 you have to flash back to Oreo first. LOS-16 needs Oreo blobs (drivers).
Click to expand...
Click to collapse
thanks i will try method 4 but i already flashed back to oreo and los 16 still cant boot and when i boot back to twrp i find it that nth is installed and everything is wiped out 0mb its like not detecting internal storage or smth maybe partition issue like u said
edit: so i tried method 4 and it worked thanks a lot hopefully i can install adnroid 10 custom roms now
Related
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
I think since the stock rom is 8.0 it might brick your device... Not sure though.
snsone said:
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Vcek said:
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Click to expand...
Click to collapse
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
snsone said:
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
Click to expand...
Click to collapse
I would recommend OTA through the device but it's not reversible (once you flash it you can't downgrade because of bootloader upgrade)
Flashing reteu over retus should be fine as long as you are doing it manually and are aware which partitions you are flashing and which you are omitting. I don't recommend this because sometimes it can break certain things like wifi or data signal (especially if you are on stock rom) and doing OTA later through the device can cause errors
Tldr;
If you want to stay on stock rom, flash back to stock then update everything through rom
If you need root or play around with custom ROMs then don't flash anything just reinstall a stock-like custom ROM
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-install-official-oreo-t3768712 this is the guide i've used to update to oreo (which is RETUS and my device is RETEU), then installed RRO. My guess is I have to install all oreo partitions again (I installed all as stated in that guide) and let it do its OTAs. I had no problems with IMEI and signal on RRO.
Hi, with the recently great news convert models to unlock bootloaders I convert my at&t h931 to us998 and unlock bootloader and twrp, flash the boombox v30 rom because the title say compatible with all rooted v30 and run perfect and great rom, then I flash the WETA rom but only ended with bootloops and flash back to boombox rom so I decide to see more deep the situation, the boombox in the settings say model h930 and I look in the thread and saw the rom its for the h930 but works with other models like mine thats its us998 converted its ok, but in the WETA title say us998 rom and dont work soo I little confused about that.
so I decide to make this trhead for people like me
for my part the boombox rom works and the WETA wont work.
bootloop as in stuck in bootanimation forever?
or it reboots and reboots and reboots all the time?
If the later, then its probably because youre on Oreo firmware, which denies to boot any nougat kernel. (thats the reason i made the updated recovery)
SGCMarkus said:
bootloop as in stuck in bootanimation forever?
or it reboots and reboots and reboots all the time?
If the later, then its probably because youre on Oreo firmware, which denies to boot any nougat kernel. (thats the reason i made the updated recovery)
Click to expand...
Click to collapse
so.... for that reason wont boot and the 10c means nougat, oh! interesting. thanks.
so I can flash all the roms here except the nougat roms? lineage os to?
ALUCARD4DEAD said:
so.... for that reason wont boot and the 10c means nougat, oh! interesting. thanks.
so I can flash all the roms here except the nougat roms? lineage os to?
Click to expand...
Click to collapse
H931 and H933 (i think those 2 it was, models are confusing) are the 2 models that bootloop (actually on the animation) on AOSP based roms like lineage... still have to figure out why
Oreo based stock roms should work fine though
Hi, I'm using a converted us998 with stock 20h, bl unlocked, rooted and twrp 3.2.7 installed. I wanna install aosp-based pie ROMs, but after trying many them, like los 16, havoc 2.9, crdroid 5.4, all of them stuck at their specific boot animations. I'm sure the process of flashing these ROMs are all correct that data, cache, dalvik cache and even system are all wiped before flashing the new ROMs. I also tried los 17 with or without permissive patcher, but it behaves the same.
Before requesting help here, I tried to flash in twrp 20e to see if anything would change, but not at all. So I wonder if I need any kdz work, as currently I have some difficulty to get access to computers.
By the way, this phone I got from a former user, and he told he had used havoc and maybe tried stock pie, but I'm not sure what he had done with this phone. Since I got the phone, I had done no system-level change but daily use. The stock 20h running now has one issue since I got it: after any accident reboot, it may reboot itself every 1-2 minutes, and triggers of wifi, bluetooth cannot work during the process. Only forced reboot while its automatic rebooting can break the misbehavior.
If kdz work is indeed needed, could I convert it to h930 from nougat? I see h930 gets more frequent update.
I was facing similar problem.
But I am able to boot LOS17.1 now. I use this method #3 mentioned in Stock US998 Pie thread on post #4.
basically you need to Partition DL to H933 10h first, just give it a read. This is the only working method for me.
you did flashed Stock Pie firmware, didn't you? It's mentioned here that flashing Stock Pie will gives you irreversible changes to your device that cause problem when you flashed Stock Oreo and AOSP 9.0, they say it'll mess up sensors and camera, but for me I can even boot AOSP 9.0, and haven't go back to Stock Oreo ever since, so idk.
it looks like your only option is AOSP 10.
zacox123 said:
Hi, I'm using a converted us998 with stock 20h, bl unlocked, rooted and twrp 3.2.7 installed. I wanna install aosp-based pie ROMs, but after trying many them, like los 16, havoc 2.9, crdroid 5.4, all of them stuck at their specific boot animations. I'm sure the process of flashing these ROMs are all correct that data, cache, dalvik cache and even system are all wiped before flashing the new ROMs. I also tried los 17 with or without permissive patcher, but it behaves the same.
Click to expand...
Click to collapse
IF you have a former H931 or H933 converted to US998 you need to follow the AOSP prep stages here for any AOSP ROM to boot:
* Running any AOSP ROM on an US998 converted H931
* [GUIDE] Canadian H933 compatibility with AOSP ROMs
This is mentioned in the WTF Instructions with link to
ADVICE ON CUSTOM ROMS
See post #2, point #2 of that "ROOT YOUR V30!" Sticky Guide.
You don't say WHAT your former variant is, but I assume it's one of those if you are having this much trouble...
zacox123 said:
Hi, I'm using a converted us998 with stock 20h, bl unlocked, rooted and twrp 3.2.7 installed.
I also tried los 17 with or without permissive patcher, but it behaves the same.
Click to expand...
Click to collapse
To run LOS-17 ROMs you additionally need to first flash LG stock Pie as a base. The LOS-17 (Android 10) ROMs need the LG stock Pie blobs (drivers). Whereas, LOS-16 ROMS use the LG stock Oreo blobs.
_____
YES, all this information should be posted in EVERY ROM thread, but it's not. However, I wrote "ROOT YOUR V30!" Sticky Guide so people would still have that information. Same reason @tech_infinity maintains an ASOP bugs thread, which is something else that should be posted in every ROM thread!
* BUGS ON LOS-17 (Android 10) ROMS
* BUGS ON LOS-16 ROMS (those 7 will probably never be fixed)
Uh, sadly I made a mistake and almost bricked my phone. See Help! bootloop per 5 sec, cannot enter rec, download or fastboot
ChazzMatt said:
IF you have a former H931 or H933 converted to US998 you need to follow the AOSP prep stages here for any AOSP ROM to boot:
* Running any AOSP ROM on an US998 converted H931
* [GUIDE] Canadian H933 compatibility with AOSP ROMs
This is mentioned in the WTF Instructions with link to
ADVICE ON CUSTOM ROMS
See post #2, point #2 of that "ROOT YOUR V30!" Sticky Guide.
You don't say WHAT your former variant is, but I assume it's one of those if you are having this much trouble...
Click to expand...
Click to collapse
I'm back from the 9008 recovery. I think the original variant of my phone is ls998 as the former owner told me. I have been tired doing anything with North America variants, so if it's feasible to move to stock h930 base as I don't care about baseband, @ChazzMatt?
zacox123 said:
I'm back from the 9008 recovery. I think the original variant of my phone is ls998 as the former owner told me. I have been tired doing anything with North America variants, so if it's feasible to move to stock h930 base as I don't care about baseband, @ChazzMatt?
Click to expand...
Click to collapse
1) It's strange if you have former LS998 that you can't boot any AOSP custom ROMs. No one else has that issue. Whereas H931/H933 are documented with needing additional prep. Is your phone V30+ (128GB) or just V30 (64GB)? That would definitely tell you what the original variant is. H931/H933 are only 64GB, whereas all the LS998 I've seen are V30+ (128GB).
2) I'm never going to advise anyone to flash anh H930 variant KDZ over North American phones. However, some people have done it, as long as they EXCLUDE certain partitions when flashing H930 KDZ with Dev Patched LGUP in Partition DL mode.
https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-convert-us998-20h-to-h930-t3956182
Mrxyzl said:
Select all partition except the following 3: modem, xbl, xbl 2, click Ok and accept partition changes
Click to expand...
Click to collapse
That guide above was made when people were too impatient to wait for US998 to get Pie, so they partially converted to EU H930, just to get LG stock Pie. It's not like Frankenstein where you fully convert all partitions, and even change LTE bands.
Also some people have done it to get East European languages not present in the North American firmware.
From what I understand once you flash the H930 stock firmware, it's hard to flash back -- but that may have been the stock "Pie" effect, with sensors messed up, etc -- as people were flashing back to US998 stock Oreo once they tried EU H930 stock Pie. We've managed to overcome that "Pie" effect for the most part, by flashing Nougat then going to Oreo.
(For others reading this do NOT try it with T-mobile H932!)
My apologies in advance if this has been discussed before. My searching has only lead me to threads stating not to flash to pie without upgrading. I had some trouble connecting to the phone but after finally working through it and getting the bootloader unlocked and TWRP on the phone, it was late and I flashed LOS 16 before properly upgrading through each iteration of Oreo(20a -> LOS 16). The phone seems to be working fine. My question is, do I need to flash back to Nougat then oreo as discussed in some of the stock pie threads or can I just flash back to oreo 20e up to 20h?
Thanks.
Phone is US998 flashed to LOS 16 from Oreo 20a
weasellystoat said:
My apologies in advance if this has been discussed before. My searching has only lead me to threads stating not to flash to pie without upgrading. I had some trouble connecting to the phone but after finally working through it and getting the bootloader unlocked and TWRP on the phone, it was late and I flashed LOS 16 before properly upgrading through each iteration of Oreo(20a -> LOS 16). The phone seems to be working fine. My question is, do I need to flash back to Nougat then oreo as discussed in some of the stock pie threads or can I just flash back to oreo 20e up to 20h?
Thanks.
Phone is US998 flashed to LOS 16 from Oreo 20a
Click to expand...
Click to collapse
Yes, you can flash US998 20e, f, g, h, then flash back to LOS 16.
LOS-16 doesn't have to persistent changes LOS-17/Android 10 has. So, no need to go back to Nougat to scrub it clean.
Hi, I unlocked bootloader, installed twrp, flashed a Android 10 custom rom (Havoc), flashed gapps and magisk on my US998. Flashed a different modem to get wifi working etc but after trying it for a while, there's just too much that doesn't work properly, specifically the camera and LMT. Anyway, I'm wanting to go back to stock Oreo, then maybe after that another custom Oreo or pie rom. What's the procedure for doing this, I searched around but couldn't figure it out. Thanks!
Best to temporarily downgrade to Nougat, then go back to last Oreo which is very stable.
Your bootloader will remain unlocked but you will have to reinstall TWRP (go through Section 6 of WTF Instructions again). Unless you can find the Nougat TWRP flashable zip someone on Telegram built, which keeps TWRP.