Related
Well i seem to have nuked my LS998 when trying to LG UP Cross flash via Frankenstein (LG UP gave me an error) after flashing AIS and loosing Modem......i can still boot TWRP from boot loader if i use "fastboot boot TWRP.img" , but if i try to install it it gives me "C:\Users\juanj\Desktop\platform-tools>fastboot flash TWRP.img
unknown partition 'TWRP.img'
fastboot: error: cannot determine image filename for 'TWRP.img'" and if i try to go into download mode again in order to try LG UP again, but before connecting it will bootloop so it seems i have removed not just recovery partition but also download mode partition and system partition .-.
6th_Hokage said:
i can still boot TWRP from boot loader if i use "fastboot boot TWRP.img".
Click to expand...
Click to collapse
Of course, this means you are booting to TWRP from copy on your PC -- a.k.a "temp" TWRP.
6th_Hokage said:
if i try to go into download mode again in order to try LG UP again, but before connecting it will bootloop so it seems i have removed not just recovery partition but also download mode partition and system partition .-.
Click to expand...
Click to collapse
Wow.
1) What happens if you Master Reset, then try to go into Download mode?
2) What happens if from temp TWRP you flash this US998 TWRP file?
https://forum.xda-developers.com/lg-v30/development/v300s-stock-flashable-zip-us998-t3795995
Someone really messed up their system one time and only recovered by flashing that. Yes, it was made by/for the Korea guy to flash on their Korea carrier variants, but someone with Sprint LS998 was able to use it. No guarantees from me, just a suggestion.
3) What happens if you flash this other TWRP flashable US998 TWRP file with temp TWRP?
https://forum.xda-developers.com/lg-v30/development/rom-lg-us998-20b-rom-t3813923
4) What happens if you flash this WETA beta ROM with temp TWRP?
https://forum.xda-developers.com/showpost.php?p=76981435&postcount=136
ChazzMatt said:
Of course, this means you are booting to TWRP from copy on your PC -- a.k.a "temp" TWRP.
Wow.
1) What happens if you Master Reset, then try to go into Download mode?
2) What happens if from temp TWRP you flash this US998 TWRP file?
https://forum.xda-developers.com/lg-v30/development/v300s-stock-flashable-zip-us998-t3795995
Someone really messed up their system one time and only recovered by flashing that. Yes, it was made by/for the Korea guy to flash on their Korea carrier variants, but someone with Sprint LS998 was able to use it. No guarantees from me, just a suggestion.
3) What happens if you flash this other TWRP flashable US998 TWRP file with temp TWRP?
https://forum.xda-developers.com/lg-v30/development/rom-lg-us998-20b-rom-t3813923
4) What happens if you flash this WETA beta ROM with temp TWRP?
https://forum.xda-developers.com/showpost.php?p=76981435&postcount=136
Click to expand...
Click to collapse
I first tried restoring stock ls998 back up from temp root and it went through, but still bootloop. If I try doing the master reset it acts like it wants to go to recovery but then bootloops. Same trying to go to DL Mode after master reset...I will try your suggestions and report back
Ypu have to download lgup hacked and flash kdz on partition dl
---------- Post added at 02:46 AM ---------- Previous post was at 02:45 AM ----------
dami00976 said:
Ypu have to download lgup hacked and flash kdz on partition dl
Click to expand...
Click to collapse
That rom is a no go for me no matter if its fix our not simply to dangerous.
Some how flashing 20b gave me back download mode .-. will try LG UP again
And it gave me the error again :/
And if I try the upgrade instead
If I partition dl everything except for the system then it 100% completes ._.
And after that 100% now it's showing up as the correct model....
And I think there was an error when I downloaded the KDZ's so I'm re downloading them both
Okay so i successfully LG UP'd to Nougat but upon reboot it went straight to bootloader and not system, so i went ahead and flashed Oreo and same thing again...but this time i was able to flash TWRP....but i can install a rom but it will instead boot into bootloader....
6th_Hokage said:
Okay so i successfully LG UP'd to Nougat but upon reboot it went straight to bootloader and not system, so i went ahead and flashed Oreo and same thing again...but this time i was able to flash TWRP....but i can install a rom but it will instead boot into bootloader....
Click to expand...
Click to collapse
After going to US998 Nougat, usually you have to do a Master Reset to stabilize.
Normally then you can just "upgrade" to US998 Oreo, but I would suggest DL PARTITION method (with all partitions).
I just ordered an LS998U and plan to convert it to a US998U. I need to use it on MetroPCS, so the conversion is necessary before I can even use the device.
Interested to see how you get along with resolving the issues you are seeing. Just an observation, obviously having no experience with the V30 but I'd check your USB configuration (drivers, other devices etc.) and try another cable. It seems you are getting some odd /unexpected errors during flash in LGUP. When I had my G3, I had some odd errors with the LG Flash Tool (which is legacy I assume?) and needed to use specific USB cables to flash KDZ files.
ChazzMatt said:
After going to US998 Nougat, usually you have to do a Master Reset to stabilize.
Normally then you can just "upgrade" to US998 Oreo, but I would suggest DL PARTITION method (with all partitions).
Click to expand...
Click to collapse
I went ahead and did the master reset on both Nougat and Oreo and it actually does the erase but then boots straight into bootloader...
One thing i have noticed when using LGUP is that even if i Partition DL completely it goes pretty fast but the moment i flash TWRP and then do LGUP again it takes like an hour longer to complete...
6th_Hokage said:
I went ahead and did the master reset on both Nougat and Oreo and it actually does the erase but then boots straight into bootloader...
Click to expand...
Click to collapse
So you have flashed Oreo KDZ in LGUP using Upgrade/Partition DL (20a or 20b since the unlock flaw is patched in 20d) and upon reboot your device is going straight into bootloader?
6th_Hokage said:
One thing i have noticed when using LGUP is that even if i Partition DL completely it goes pretty fast but the moment i flash TWRP and then do LGUP again it takes like an hour longer to complete...
Click to expand...
Click to collapse
I am confused, if you completed the Frankenstein conversion you should have an unlocked US998 (stock, not rooted). The phone technically could be used as is correct? If you are attempting installing TWRP, you have already gone through the bootloader unlock successfully? I think you need to get a stable device running 20a or 20b of US998 Oreo before attempting to move to the bootloader unlock/TWRP/encryption/root in the WTF thread.
I am going to be doing this in a few days so I'd like to understand where you're at and what the next steps would be...
jdgesmlls said:
So you have flashed Oreo KDZ in LGUP using Upgrade/Partition DL (20a or 20b since the unlock flaw is patched in 20d) and upon reboot your device is going straight into bootloader?
I am confused, if you completed the Frankenstein conversion you should have an unlocked US998 (stock, not rooted). The phone technically could be used as is correct? If you are attempting installing TWRP, you have already gone through the bootloader unlock successfully? I think you need to get a stable device running 20a or 20b of US998 Oreo before attempting to move to the bootloader unlock/TWRP/encryption/root in the WTF thread.
I am going to be doing this in a few days so I'd like to understand where you're at and what the next steps would be...
Click to expand...
Click to collapse
I already have the bootloader unlocked i completed both Frankenstein and WTF like a month or so ago but in theory you could still install twrp after either Nougat or Oreo flash...and be on your marry way but the only thing that isn't going correctly is the flashing of the system...cause it's booting straight into bootloader....
jdgesmlls said:
I am confused, if you completed the Frankenstein conversion you should have an unlocked US998 (stock, not rooted). The phone technically could be used as is correct? If you are attempting installing TWRP, you have already gone through the bootloader unlock successfully?
I think you need to get a stable device running 20a or 20b of US998 Oreo before attempting to move to the bootloader unlock/TWRP/encryption/root in the WTF thread.
I am going to be doing this in a few days so I'd like to understand where you're at and what the next steps would be...
Click to expand...
Click to collapse
He installed something he said messed the phone partitions up. So, he's been trying to recover from that, and get back to what he had before which was bootloader unlocked and rooted US998.
The Frankenstein method works on normal V30 variant, but somehow his download and recovery partitions were deleted due to what he did prior to starting this thread.
However, DL PARTITION method should have restored them. So, I'm a little confused also.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
ChazzMatt said:
Of course, this means you are booting to TWRP from copy on your PC -- a.k.a "temp" TWRP.
Wow.
1) What happens if you Master Reset, then try to go into Download mode?
2) What happens if from temp TWRP you flash this US998 TWRP file?
https://forum.xda-developers.com/lg-v30/development/v300s-stock-flashable-zip-us998-t3795995
Someone really messed up their system one time and only recovered by flashing that. Yes, it was made by/for the Korea guy to flash on their Korea carrier variants, but someone with Sprint LS998 was able to use it. No guarantees from me, just a suggestion.
3) What happens if you flash this other TWRP flashable US998 TWRP file with temp TWRP?
https://forum.xda-developers.com/lg-v30/development/rom-lg-us998-20b-rom-t3813923
4) What happens if you flash this WETA beta ROM with temp TWRP?
https://forum.xda-developers.com/showpost.php?p=76981435&postcount=136
Click to expand...
Click to collapse
Did you try #2 yet?
ChazzMatt said:
He installed something he said messed the phone partitions up. So, he's been trying to recover from that, and get back to what he had before which was bootloader unlocked and rooted US998.
The Frankenstein method works on normal V30 variant, but somehow his download and recovery partitions were deleted due to what he did prior to starting this thread.
However, DL PARTITION method should have restored them. So, I'm a little confused also.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
Did you try #2 yet?
Click to expand...
Click to collapse
Well i got DL mode back and recovery mode seems to have come back, which is reinforced by the fact that the Master Reset goes through with the Erase. but The System doesn't want to come back even though it flashes 100% in LGUP, right now i'm trying 10C and 20B to see if that does anything to the phone....
And i have not tried the 2nd method.
hello guys sorry for my english...i recently unlocked the booloader of my v30 h930, but when i try to enter twrp recovery after flashing the image via fastboot comands,i found this frustrating message "factory data reset is disabled by kill switch"...is there any thing to do ?? thanks again
Odd. Did you flash the twrp image, and then boot the image? as per the WTF instructions?
What command, specifically, are you entering, and then getting this message?
Sounds like twrp didn't install. Make sure you go through all the steps from WTF correctly
Sent from my LG-US998 using Tapatalk
yahya2110 said:
hello guys sorry for my english...i recently unlocked the booloader of my v30 h930, but when i try to enter twrp recovery after flashing the image via fastboot comands,i found this frustrating message "factory data reset is disabled by kill switch"...is there any thing to do ?? thanks again
Click to expand...
Click to collapse
Normally we only see that on U.S. T-Mobile H932 which has crappy McAfee installed. Has to be uninstalled before factory reset or you get that error message. Do you have something like that installed?
yahya2110 said:
hello guys sorry for my english...i recently unlocked the booloader of my v30 h930, but when i try to enter twrp recovery after flashing the image via fastboot comands,i found this frustrating message "factory data reset is disabled by kill switch"...is there any thing to do ?? thanks again
Click to expand...
Click to collapse
ChazzMatt said:
Normally we only see that on U.S. T-Mobile H932 which has crappy McAfee installed. Has to be uninstalled before factory reset or you get that error message. Do you have something like that installed?
Click to expand...
Click to collapse
Personally I have never seen that McAfee stuff on my H932, but maybe it's something you have to deliberately install first.
But we have had others report about this error. As I have posted before, I think it is just "something" (McAfee or whatever) trying to save you from wiping the phone in a way that would trigger Android Factory Reset Protection: The entire point of FRP is to render the phone useless to anyone but the legitimate owner, in case it is wiped from outside the OS while an account is active in the OS. That is a sensible protection. I always wondered why LGs Master Reset (using the buttons) doesn't warn about this before proceeding with its wipe.
But if indeed the error reported by OP is caused by such "protection against unintended triggering of FRP" then the solution should be to remove the Google account in the OS before performing any actions that would wipe the phone outside the OS (LGUP, Master Reset, TWRP etc). Alternatively, perform a Factory Reset from inside the OS first, which also will remove the account in a way that doesn't trigger FRP.
Arguably, this should be mentioned in the various root/WTF/Frankenstein guides, since FRP can have unintended consequences, say in case a user flashes the phone back to stock before selling it or sending it in for repair, and doesn't remove his/her account first. In that case the phone will (or should) demand that the same account be entered on first boot -- and the new owner or repair center would be stuck.
But maybe LGUP Refurbish mode clears FRP, and that's why we don't get more complaints about it...
I apologize if this turns out to be completely unrelated to the error reported by OP
Don't worry I've been through this problem and solution ia simple.
-Boot the phone in normal.
-Plug in the usb cable in your phone and connect to the computer.
-Then type "adb reboot bootloader". When u boot into fastbooot then type "fasboot boot recovery or whatever u named the file.
-Then u will boot into twrp.
I was sold a refurbished v30 off Amazon that had this kill switch enabled also when trying to go into TWRP. I had to return it because it might have been stolen.
Sent from my iPad using Tapatalk
I bought a V30 on ebay, is a LS998 Frankenstein, the problem is that the installed ROM is the AS998 and not the US998, it has the kill switch problem. Some way to solve it? I can not access fastboot and I can not install the ROM US998 from LGUP. I tried installing the KDZ US998 from LG UP with Partition UP option but it does not boot. Some way to return to the LS998 ROM?
jorgeaoc said:
I bought a V30 on ebay, is a LS998 Frankenstein, the problem is that the installed ROM is the AS998 and not the US998, it has the kill switch problem. Some way to solve it? I can not access fastboot and I can not install the ROM US998 from LGUP. I tried installing the KDZ US998 from LG UP with Partition UP option but it does not boot. Some way to return to the LS998 ROM?
Click to expand...
Click to collapse
There are no public LS998 KDZ available.
Which US998 KDZ did you try? If you read the Frankenstein instructions you need to start with US998 Nougat first.
Yes, of the North America V30 variants, only US998 has full fastboot flash commands.
ChazzMatt said:
There are no public LS998 KDZ available.
Which US998 KDZ did you try? If you read the Frankenstein instructions you need to start with US998 Nougat first.
Click to expand...
Click to collapse
The phone came with the ROM AS99820b (Oreo) :crying:, try to install US99810d and US99820b KDZ. Only the Partition DL option works in the LGUP application, but the phone not boot. The other options show Error: 0x4, Not support cross model download AS998 to US998 . Do you know any way to jump to the US ROM?
ChazzMatt said:
Yes, of the North America V30 variants, only US998 has full fastboot flash commands.
Click to expand...
Click to collapse
Do you know if the previous ways to root the LG G works on the V30?
jorgeaoc said:
The other options show Error: 0x4, Not support cross model download AS998 to US998 ?
Click to expand...
Click to collapse
Are you using the Dev Patched LGUP?
ChazzMatt said:
Are you using the Dev Patched LGUP?
Click to expand...
Click to collapse
Yes, the LGUP patch in the [Frankenstein Phone] Using LGUP for crossflashing Post #168
jorgeaoc said:
Yes, the LGUP patch in the [Frankenstein Phone] Using LGUP for crossflashing Post #168
Click to expand...
Click to collapse
And do you get the cross flashing error when trying to install US998 10D Nougat?
ChazzMatt said:
And do you get the cross flashing error when trying to install US998 10D Nougat?
Click to expand...
Click to collapse
Yes, when I try to install the two US KDZ ROMs Nougat and Oreo
jorgeaoc said:
Yes, when I try to install the two US KDZ ROMs Nougat and Oreo
Click to expand...
Click to collapse
I ran across this before where some dealer probably used Octopus box to convert LS998 to AS998 and the new owner couldn't then convert to anything else...
All I can suggest is you try Board DL or Refurbish mode.
Is wiping the system partition the same thing as factory data reset? Will that trigger ye' old kill switch?
I ask, because I've run into the cross-flash warning once before while trying to flash US998 while on VZ996. To get rid of that message, I simply wiped my system partition in TWRP and was then able to use LGUP with the US998 KDZ.
So if you can wipe your system partition, then maybe it will get you to a spot where you can kdz?
I got it!
After many attempts, use a LGUP that I found in the LG G7 forum, the difference is that it was from CLI, restore the KDZ Nougat, when restarting appeared a screen with the android doll and the text without command. The next step was not clear, I pressed all the buttons with different convincing. The phone restarted several times and remained in the same window, in one of those attempts I went to the LG logo and to the initial configuration, the phone was blocked by google. Surely this is the reason why the seller installed the ROM AS998.
Turn off the phone and from LGUP update to the Oreo version. Again the error of blocking by google. On YouTube I found a tutorial to bypass this step. Now I am in the US99820b version. I followed the steps to unlock the bootloader, I had a problem with the USB cable, I must use a good quality cable. The problem of the message "factory data reset is disabled by kill switch" continues, but I can enter TWRP from fastboot.
I will try to install a ROM from TWRP and see if the message disappears.
jorgeaoc said:
I got it!
After many attempts, use a LGUP that I found in the LG G7 forum, the difference is that it was from CLI, restore the KDZ Nougat, when restarting appeared a screen with the android doll and the text without command. The next step was not clear, I pressed all the buttons with different convincing. The phone restarted several times and remained in the same window, in one of those attempts I went to the LG logo and to the initial configuration, the phone was blocked by google. Surely this is the reason why the seller installed the ROM AS998.
Turn off the phone and from LGUP update to the Oreo version. Again the error of blocking by google. On YouTube I found a tutorial to bypass this step. Now I am in the US99820b version. I followed the steps to unlock the bootloader, I had a problem with the USB cable, I must use a good quality cable. The problem of the message "factory data reset is disabled by kill switch" continues, but I can enter TWRP from fastboot.
I will try to install a ROM from TWRP and see if the message disappears.
Click to expand...
Click to collapse
You can also enter TWRP using the Recovery Reboot app I recommend in the WTF instructions.
US998 20B is old (but necessary for bootloader unlock). You should update to US998 20H. Download 20E, 20F, 20G, 20H and dirty flash back-to-back, using TWRP auto queue function -- with flashing Magisk last.
ChazzMatt said:
You can also enter TWRP using the Recovery Reboot app I recommend in the WTF instructions.
US998 20B is old (but necessary for bootloader unlock). You should update to US998 20H. Download 20E, 20F, 20G, 20H and dirty flash back-to-back, using TWRP auto queue function -- with flashing Magisk last.
Click to expand...
Click to collapse
Excellent, I'm going to try LineageOS first, where do I find the 20E, 20F, 20G, 20H zip updates?
jorgeaoc said:
Excellent, I'm going to try LineageOS first, where do I find the 20E, 20F, 20G, 20H zip updates?
Click to expand...
Click to collapse
NO. You need to be on newest firmware before flashing any AOSP/Lineage ROMs due to recent changes. That's where people mess up. They try to go from old Oreo or even Nougat (H932) firmware to custom ROMs. You need foundation of newest firmware. Read post #2 of this sticky:
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
A whole lot of recent posts in Lineage are about people not updating their stock firmware first.
Here's the US998 KDZ/TWRP-flashable thread:
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
US998 original, TWRP 3.2.3-7-DataImg, bootloader unlocked
Have tried installing both Lineage and LiquidRemix, with no success. Upon reboot, phone bootloops. Easily put it in download mode and start all over again, using factory image (data seems to be getting corrupted).
When in recovery: factory reset, then wipe data, dalvik, cache, and system. Only installing ROM at this time, trying to weed out potential problems.
Tried flashing just no-verity earlier and phone was stuck on splash screen, then.
Any suggestions on this would be appreciated. Not sure where to pull a logcat, even if available, as I am not 100% sure where the problem is originating from.
mpicasso said:
snip.
Click to expand...
Click to collapse
Did you ever update stock firmware to newest update before trying to flash a custom ROM?
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Did you ever update stock firmware to newest update before trying to flash a custom ROM?
Click to expand...
Click to collapse
Was rooted, with Magisk, on US99820H, when i did it the 1st time.
Thought there was a chance maybe i had not removed encryption but it seems to be something causing data corruption.
mpicasso said:
Was rooted, with Magisk, on US99820H, when i did it the 1st time.
Thought there was a chance maybe i had not removed encryption but it seems to be something causing data corruption.
Click to expand...
Click to collapse
I've no idea if this will or won't help, but have an ls998 converted to us998 which has successfully booted numerous of the custom roms, even from us99820H.
I always remove any accounts on phone, any finger prints unlock, pins, everything. Then do a factory reset. It should be bone stock at that point (for 20H), except of course bl unlocked and twrp installed.
Then, install the rom as you have been. If it doesn't boot, in the various after market rom threads people have discussed fixes they've found. But from what I've read it seems a pretty common problem is the device itself. You say it was an original us998? Was that US Cellular us998? I had one of those, it wouldn't boot an aftermarket rom either.
good luck, Cheers
Did you try flashing the TWRP ready firmware for your phone?
This is what ChazzMatt said: "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."
So, I am guessing you can flash a custom ROM by just flashing 20e first then the custom ROM after. Instead of flashing a custom ROM from 20h, which is known to cause issues.
AsItLies said:
You say it was an original us998? Was that US Cellular us998? I had one of those, it wouldn't boot an aftermarket rom either.
Click to expand...
Click to collapse
Thought US998U was US Cellular but went on to their website to verify IMEI...device not compatible with their network.
mpicasso said:
Thought US998U was US Cellular but went on to their website to verify IMEI...device not compatible with their network.
Click to expand...
Click to collapse
IF it's been converted from LS998 you'll get a false result like that. You're sure you have original US998?
US998U just means US998 V30+. U.S. CELLULAR sold them as well as B&H Photo, Best Buy, Amazon...
I know nothing about U.S. Cellular. It's possible they only allow phones they sold, whose IMEI are on their database. I don't know.
skittles-1999 said:
This is what ChazzMatt said: "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. Instead of flashing a custom ROM from 20h, which is known to cause issues.
Click to expand...
Click to collapse
TWRP: TWRP-3.2.3-7-default.img
Haha - had just noticed this comment before coming on here to respond! Yes, I went from B to H, without the tweeners. Honestly thought I had read everything...
Did not see the note where flashing from 20H causes problems. Do you have a link for that?
Will go back and install E and F, at minimum, as he said massive changes happened with 20F. Really want this phone to work with AOSP rom's, especially since I paid around $250 for it, but willing to still use it stock and rooted. Phone before this was a Nexus 6, which I hung on to for as long as I could (over 3 years...) but after this, going to OnePlus or Pixel.
Thanks for your help!
mpicasso said:
Thought US998U was US Cellular but went on to their website to verify IMEI...device not compatible with their network.
Click to expand...
Click to collapse
Did LG developers website give u the unlock bin for this device? That would be the definitive indication of what device it is as there is only that one and the 930 you can get unlock codes for.
*If* that's the case, that LG identifies it for unlock purposes, then I can only say be sure to have done what's mentioned above in removing accounts etc. After doing that, and an aftermarket rom won't boot? I'd be at a loss. It really wouldn't make any sense at all.
Cheers
mpicasso said:
Thought US998U was US Cellular but went on to their website to verify IMEI...device not compatible with their network.
Click to expand...
Click to collapse
AsItLies said:
Did LG developers website give u the unlock bin for this device? That would be the definitive indication of what device it is as there is only that one and the 930 you can get unlock codes for.
*If* that's the case, that LG identifies it for unlock purposes, then I can only say be sure to have done what's mentioned above in removing accounts etc. After doing that, and an aftermarket rom won't boot? I'd be at a loss. It really wouldn't make any sense at all.
Cheers
Click to expand...
Click to collapse
LG NEVER gave bootloader unlock code for any US998U aka US998 V30+ (128GB). I have Open Market US998U (V30+) bought from B&H Photo and had to use WTF bootloader unlock.
Only my US998 V30 (64GB) bought from B&H Photo was eligible for LG bootloader unlock code, and even then you have to hack the LG Developer drop down menu to get a code. No US998 is listed on the LG Developer website.. LG never officially put the US998 on the approved list. Yes, for original B&H Photo 64GB US998, you can still get LG bootloader unlock code -- but you have to know how to do it. However, we have no need with WTF exploit.
ChazzMatt said:
Only my US998 V30 bought from B&H Photo was eligible for bootloader unlock code, and even then you have to hack the LG Developer drop down menu to get a code.
Click to expand...
Click to collapse
^ this...
Bought new SD card today and doing as ChazzMatt originally suggested, which is start at B, then do E and up. Stopping at G, and trying from there.
Thank you...but no thanks to the drama.
I appreciate the help but sadly, skittles-1999 offered the best response, which I must have overlooked when reading everything I did.
Phone was bought off of Swappa and assured by seller it was a US998U. Box stated as such, model number shows as LG-US998. KDZ downloaded/installed, from LG, was a US998. Cannot think of any other way to verify that it truly is a US998, original.
Things I have changed - new microSD card, 1, and 2, have gone from B, to E, F, to G.
Have to step out but will try installing lineage later.
Tried installing Lineage, Magisk, and Gapps all together. Will try to go back and reinstall just Lineage, to see if that fixes the problem.
Thanks for everything.
Erm calm down?
Thread cleaned. No flaming please. Read Rules.
{
"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"
}
-XDA Staff
Giving up...almost
Have tried flashing this:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Running US99820H, Magisk 19.3 with root. Even tried installing Lineage 15.0 (8.1) but again with no success.
System wipe
Advanced wipe: Data, Internal Storage, System, Cache, and Dalvik Cache
Format data
Reboot recovery
Install ROM
Install DM-verity
Install Magisk
Reboot
Can flash 20H zip, along with any other Magisk module, with no problem. Guessing it has something to do with boot.img?
mpicasso said:
Have tried flashing this:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Running US99820H, Magisk 19.3 with root. Even tried installing Lineage 15.0 (8.1) but again with no success...
Click to expand...
Click to collapse
I thought 19.3 was not working properly for us.
Try 18.1 which definitely does work
gazzacbr said:
I thought 19.3 was not working properly for us.
Try 18.1 which definitely does work
Click to expand...
Click to collapse
Sorry, I install 18.1, them updates. Suggesting to not update before installing?
mpicasso said:
Sorry, I install 18.1, them updates. Suggesting to not update before installing?
Click to expand...
Click to collapse
Yes.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Yes.
Click to expand...
Click to collapse
Have downgraded to US998E. Is there a possibility partitions on the US998U have the same problem as others, such as the H931/H933? Would I brick my phone if I partitioned, using an H933 rom?
Tried installing bootlegger, with permissive kernel, but bootlooping as we speak. Have been at this, off and on, for days, with no success installing an AOSP rom but will try the suggestion offered. At the point I am ready to keep this as a backup and buy either an H930 or a US998, no plus.
mpicasso said:
Have downgraded to US998E. Is there a possibility partitions on the US998U have the same problem as others, such as the H931/H933? Would I brick my phone if I partitioned, using an H933 rom?
Click to expand...
Click to collapse
No, plenty of US998U (V30+) are running AOSP/Lineage custom ROMs. US998, US998U, US998R are all identical internally -- except for storage amount or RAM.
If you wish to try H933 workaround, no you won't brick the phone.
Ok I just got my ATT V30 , works great but wanted to switch to US998 as ATT hotspot dont work, I try to flash us99820g and LGUP and selecting all the partitions, after click start LGUP told me some partitions will change and I click yes (my bad) and after all the process completed the phone is in a boot loop and all I can see is the Android green robot with an red exclamation and the reboots, is there any way to fix it or I sent $130 to the trash can.
If I keep vol - and power it reboots and I can see LG V30 thinkq logo but then the loop starts again.
PonchosoftX said:
Ok I just got my ATT V30 , works great but wanted to switch to US998 as ATT hotspot dont work, I try to flash us99820g and LGUP and selecting all the partitions, after click start LGUP told me some partitions will change and I click yes (my bad) and after all the process completed the phone is in a boot loop and all I can see is the Android green robot with an red exclamation and the reboots, is there any way to fix it or I sent $130 to the trash can.
If I keep vol - and power it reboots and I can see LG V30 thinkq logo but then the loop starts again.
Click to expand...
Click to collapse
No it's not bricked.
But you need to read the Frankenstein instructions. You can't just flash other KDZ willy nilly.
For North America variants (except for T-Mobile H932), you have to use Dev Patched LGUP and flash US998 Nougat, then Master Reset, then US998 Oreo.
https://forum.xda-developers.com/showpost.php?p=76510671&postcount=168
Sent via open market LG US998 V30/V30+
ChazzMatt said:
No it's not bricked.
But you need to read the Frankenstein instructions. You can't just flash other KDZ willy nilly.
For North America variants (except for T-Mobile H932), you have to use Dev Patched LGUP and flash US998 Nougat, then Master Reset, then US998 Oreo.
https://forum.xda-developers.com/showpost.php?p=76510671&postcount=168
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Thank you, I miss the part where I have to flash Nougat then Oreo, I was on ATT oreo and then flash US998 Oreo, now I was able to enter download mode and do a factory reset but phone keeps reset after I try to enter the wifi setup, let me try flash Nougat and the oreo and see If works
Thank you.
Phone is now fully working, thanks so much for your help. Please close this thread if possible.
What do the different options in the partition DL mode of LGUP mean? Some are self explanatory (modem, boot), some can be identified with searching (xbl), but some are unclear (tz, hyp).
Information on which ones have changed between oreo and pie would be helpful. My immediate goal is to complete an upgrade to pie (H930DS SEA / SG region flashed to 22J global / com but any pie update hangs at v30 / LG boot screens). But really I'm hoping to better understand what each portion of the kdz refers to. Cheers.
EsotericScreenName said:
What do the different options in the partition DL mode of LGUP mean? Some are self explanatory (modem, boot), some can be identified with searching (xbl), but some are unclear (tz, hyp).
Information on which ones have changed between oreo and pie would be helpful. My immediate goal is to complete an upgrade to pie (H930DS SEA / SG region flashed to 22J global / com but any pie update hangs at v30 / LG boot screens). But really I'm hoping to better understand what each portion of the kdz refers to. Cheers.
Click to expand...
Click to collapse
Just double-checking... You have an H930DS phone?
Which Dev Patched LGUP are you using? You need to use the ones in the Pie KDZ threads.
Most people with H930DS have flashed any of H930DS Pie KDZ or EU H93O Pie 30q with no problems. In fact, the only people having problems are North American variants trying to flash the wonky US998 30b Pie KDZ.
ChazzMatt said:
Just double-checking... You have an H930DS phone?
.
Click to expand...
Click to collapse
Yes, H930+ ThinQ DS from Singapore, verified model by LG bridge and IMEI lookup. It has been bootloader unlocked by WTF method, but I'm having difficulty upgrading past 22j. Software info shows android 8.0, 22j-global-com. When I flash pie KDZs (regardless of refurbish, partition DL, upgrade, etc) LGUP continues to show the version as 22j despite the fact that TWRP flashed zips (flashable versions of KDZ, verity decrypt, RCTD remover, etc) show android version 9. LGUP flashing to any oreo or nougat version works fine.
ChazzMatt said:
Which Dev Patched LGUP are you using? .
Click to expand...
Click to collapse
LGUP dual mode 1.14 from the PIE 3030Q thread. I have also tried 1.16 from lg-firmwares and the older 1.14 from oreo threads, with no difference.
ChazzMatt said:
Most people with H930DS have flashed any of H930DS Pie KDZ or EU H93O Pie 30q with no problems. In fact, the only people having problems are North American variants trying to flash the wonky US998 30b Pie KDZ.
Click to expand...
Click to collapse
Yes I see most people upgrade without any issues. However it also seems that some 300VL Korean users and 930DS users have issues upgrading which sound very similar to mine:
https://forum.xda-developers.com/showpost.php?p=76510671&postcount=168
https://forum.xda-developers.com/lg-v30/help/v30-update-android9-0-boot-logo-freeze-t3963369/page2
I realize these threads are old.
Thanks for your assistance and helpful guides.
EsotericScreenName said:
Yes, H930+ ThinQ DS from Singapore, verified model by LG bridge and IMEI lookup. It has been bootloader unlocked by WTF method, but I'm having difficulty upgrading past 22j. Software info shows android 8.0, 22j-global-com. When I flash pie KDZs (regardless of refurbish, partition DL, upgrade, etc) LGUP continues to show the version as 22j despite the fact that TWRP flashed zips (flashable versions of KDZ, verity decrypt, RCTD remover, etc) show android version 9. LGUP flashing to any oreo or nougat version works fine.
LGUP dual mode 1.14 from the PIE 3030Q thread. I have also tried 1.16 from lg-firmwares and the older 1.14 from oreo threads, with no difference.
Yes I see most people upgrade without any issues. However it also seems that some 300VL Korean users and 930DS users have issues upgrading which sound very similar to mine:
https://forum.xda-developers.com/showpost.php?p=76510671&postcount=168
https://forum.xda-developers.com/lg-v30/help/v30-update-android9-0-boot-logo-freeze-t3963369/page2
I realize these threads are old.
Thanks for your assistance and helpful guides.
Click to expand...
Click to collapse
Going to sound counterintuitive, but try downgrading to H930DS Nougat via Partition DL, Master Reset. Then from Nougat try Refurbish to Oreo.
You'll still have unlock Bootloader. After you get past Pie, then you can reinstall TWRP and root again.
ChazzMatt said:
Going to sound counterintuitive, but try downgrading to Nougat via Partition DL, Master Reset. Then from Nougat try Refurbish to Oreo.
You'll still have unlock Bootloader. After you get past Pie, then you can reinstall TWRP and root again.
Click to expand...
Click to collapse
Thanks but I have tried this, by adapting instructions from the 998 and v300l threads. The result is the same, still can't get past the boot screens (hangs for 30+ minutes at v30 or lg splash screens). Generally, I did:
- Refurbish to version 20 (usually f or d, tried 930ds sg 20f, 930 EU 20d, 930d's two 20d)
- Partition dl and select all to v10 (10d from several different regions)
- partition dl, refurbish or upgrade to pie (30b EU, 30q EU, 30a Aus, 30c Aus and sg)
I have tried with and without master reset, format data, and/or boot to welcome screen after each step. Still cannot successfully boot to pie. 22j EU and hk both work fine but that's the latest I can boot. I have even tried converting to us998 20a and upgrading from there (risky I realize) but still no good.
I have tried dirty flashing 22j to 30b (both original and v3) or 30q via twrp and it still just hangs at lg splash screen. Related to op I have been experimenting with omitting various partitions in partition dl mode (e.g. boot or recovery) during upgrade but still no success.
Is there some specific kdz version I should try (as with us998 20h > 10d > pie) beyond just downgrade to nougat?
EsotericScreenName said:
Thanks but I have tried this, by adapting instructions from the 998 and v300l threads. The result is the same, still can't get past the boot screens (hangs for 30+ minutes at v30 or lg splash screens). Generally, I did:
- Refurbish to version 20 (usually f or d, tried 930ds sg 20f, 930 EU 20d, 930d's two 20d)
- Partition dl and select all to v10 (10d from several different regions)
- partition dl, refurbish or upgrade to pie (30b EU, 30q EU, 30a Aus, 30c Aus and sg)
I have tried with and without master reset, format data, and/or boot to welcome screen after each step. Still cannot successfully boot to pie. 22j EU and hk both work fine but that's the latest I can boot. I have even tried converting to us998 20a and upgrading from there (risky I realize) but still no good.
I have tried dirty flashing 22j to 30b (both original and v3) or 30q via twrp and it still just hangs at lg splash screen. Related to op I have been experimenting with omitting various partitions in partition dl mode (e.g. boot or recovery) during upgrade but still no success.
Is there some specific kdz version I should try (as with us998 20h > 10d > pie) beyond just downgrade to nougat?
Click to expand...
Click to collapse
If you have H930DS, you should only flash H930 variant firmware, not any North American variant firmware like USS98.
Very strange you can't update to any of the H930/H930DS firmware, either via KDZ or TWRP-flashable zips.
____
As for the US998 to 10d, that's just chosen because that was the last Nougat before Oreo. 10c would be just as good.
ChazzMatt said:
If you have H930DS, you should only flash H930 variant firmware, not any North American variant firmware like USS98.
Very strange you can't update to any of the H930/H930DS firmware, either via KDZ or TWRP-flashable zips.
____
As for the US998 to 10d, that's just chosen because that was the last Nougat before Oreo. 10c would be just as good.
Click to expand...
Click to collapse
Yeah it's really stumped me. Hence the question about the partitions. I'm thinking something is mismatched somehow, as lgup keeps claiming the phone is still on Oreo while twrp confirms pie. Probably I should just pay for octo session but I was hoping to learn about how this works
Finally got it to load, by
- boot into system while connected to pc with mtp and usb debugging enabled. it stays connected the whole time
- pc has installed: lgup + dlls from the 3030q kdz thread, latest official lg bridge, latest official lg driver
- dirty flashing the 3030q twrp zip with no wipes or formats of any kind
- wipe cache + dalvik after dirty flash
- reboot phone to system, phone hangs on lg splash screen as usual
- reboot pc. somehow the lg software detected the dirty flash and identified it could be fixed... by rebooting the pc for some reason. I got a windows notification about this
- after rebooting pc, phone auto reboots and finally loads pie correctly
I have no idea what went wrong here but it seems fine now
EsotericScreenName said:
Finally got it to load, by
- boot into system while connected to pc with mtp and usb debugging enabled. it stays connected the whole time
- pc has installed: lgup + dlls from the 3030q kdz thread, latest official lg bridge, latest official lg driver
- dirty flashing the 3030q twrp zip with no wipes or formats of any kind
- wipe cache + dalvik after dirty flash
- reboot phone to system, phone hangs on lg splash screen as usual
- reboot pc. somehow the lg software detected the dirty flash and identified it could be fixed... by rebooting the pc for some reason. I got a windows notification about this
- after rebooting pc, phone auto reboots and finally loads pie correctly
I have no idea what went wrong here but it seems fine now
Click to expand...
Click to collapse
Glad you got it working!
When was the last time you rebooted the PC before this?
One of the dozen WTF Trouble Shooting Tips is to reboot the PC. It helps to register drivers and newly installed software.
ChazzMatt said:
Glad you got it working!
When was the last time you rebooted the PC before this?
One of the dozen WTF Trouble Shooting Tips is to reboot the PC. It helps to register drivers and newly installed software.
Click to expand...
Click to collapse
I rebooted it yesterday. I'd tried rebooting several times during various upgrade attempts but never had this notification or any apparent differences. Still have expected weirdness from a dirty flash (magisk issues, etc) but LGUP now recognizes the device as 30q so hopefully I can clean flash the kdz successfully now. Thanks for your advice!