Related
I do contract work for a cellular dealer, and they've given me some demo units to set up as loaner units for client devices going out for service.
I've been able to disable and remove the Retail Mode application on most of the devices, but two of the devices (the v30 and the G7 Thinq) don't seem to allow it to be removed - it's effectively baked into the ROM (it can be stopped/disabled, but that doesn't allow for full access - each time the device is wiped it goes back into demo mode, something that's useless for a service loaner).
Can I just follow the WTF guide, unlock the bootloader, and install a stock ROM without the retail mode included? My knowledge in my time with devices leads me to understand that there's no way to remove an app that's baked in (although some Samsung devices have bloatware removal tools or ADB commands to help with this process, so I figured asking might be a long shot!)
Thanks in advance
There was an LG package disabler floating around, or you *might* be able to "uninstall" it for the base user using ADB and the package manager.
If you could attain root access, there's no reason at all that you couldn't use a file manager and outright delete the app, but...
At that point you may as well go the extra mile and flash a retail ROM, since there might be other differences in the ROM that prevent it from being usable on a day-to-day basis.
There shouldn't be any hardware difference between a "display" unit and a retail unit, so flash away.
I would get the correct carrier firmware for the phone and use refurbish mode in LGUP (from the WTF thread). This is assuming they were originally regular phones that were opened, put in demo mode, and put on display.
However, if the V30 is carrier specific and the store sells multiple carriers (like a Best Buy), I would in this instance go through with the WTF method and convert it to a retail US998 (much more convenient), but no root or TWRP since it's to be used as a loaner. I don't know if there is a way to do something similar to the G7.
sh0nuff said:
I do contract work for a cellular dealer, and they've given me some demo units to set up as loaner units for client devices going out for service.
I've been able to disable and remove the Retail Mode application on most of the devices, but two of the devices (the v30 and the G7 Thinq) don't seem to allow it to be removed - it's effectively baked into the ROM (it can be stopped/disabled, but that doesn't allow for full access - each time the device is wiped it goes back into demo mode, something that's useless for a service loaner).
Can I just follow the WTF guide, unlock the bootloader, and install a stock ROM without the retail mode included? My knowledge in my time with devices leads me to understand that there's no way to remove an app that's baked in (although some Samsung devices have bloatware removal tools or ADB commands to help with this process, so I figured asking might be a long shot!)
Thanks in advance
Click to expand...
Click to collapse
hitokage004 said:
I would get the correct carrier firmware for the phone and use refurbish mode in LGUP (from the WTF thread). This is assuming they were originally regular phones that were opened, put in demo mode, and put on display.
However, if the V30 is carrier specific and the store sells multiple carriers (like a Best Buy), I would in this instance go through with the WTF method and convert it to a retail US998 (much more convenient), but no root or TWRP since it's to be used as a loaner. I don't know if there is a way to do something similar to the G7.
Click to expand...
Click to collapse
The only thing I would add is that once you use refurbish to carrier unlocked US998 with dev patched LGUP and stock firmware, you may not even need to use WTF to unlock the bootloader and root.
Yes, root would give you ultimate control to remove system apps. But just for getting the phone out of demo mode, that may not be necessary.
What I'm curious about is exactly which variant of LG v30 we're talking about? I assume it's one of the North America models, but which one? Or is this a store that sells phones from several carriers? Just be aware T-mobile H932 cannot be used for Frankenstein and WTF, due to different RSA encryption. All the other North American variants can be flashed to US998 or use refurbish to keep that variant's firmware. However, Sprint and AT&T do not release KDZ so it's very hard to get firmware for those models. It's usually best just to convert them to US998.
If you're converting one North America LG v30 to carrier unlocked US998, it's safer to first install US998 Nougat, do a master reset, then install US998 Oreo. See the instructions in the Frankenstein thread.
I don't mention "refurbish" in those instructions, but that's a very powerful command to use.
CONVERTING ANY NORTH AMERICA V30/V30+ TO US998 OREO (except T-Mobile H932)
ChazzMatt said:
The only thing I would add is that once you use refurbish to carrier unlocked US998 with dev patched LGUP and stock firmware, you may not even need to use WTF to unlock the bootloader and root.
Yes, root would give you ultimate control to remove system apps. But just for getting the phone out of demo mode, that may not be necessary.
What I'm curious about is exactly which variant of LG v30 we're talking about? I assume it's one of the North America models, but which one? Or is this a store that sells phones from several carriers? Just be aware T-mobile H932 cannot be used for Frankenstein and WTF, due to different RSA encryption. All the other North American variants can be flashed to US998 or use refurbish to keep that variant's firmware. However, Sprint and AT&T do not release KDZ so it's very hard to get firmware for those models. It's usually best just to convert them to US998.
If you're converting one North America LG v30 to carrier unlocked US998, it's safer to first install US998 Nougat, do a master reset, then install US998 Oreo. See the instructions in the Frankenstein thread.
I don't mention "refurbish" in those instructions, but that's a very powerful command to use.
CONVERTING ANY NORTH AMERICA V30/V30+ TO US998 OREO (except T-Mobile H932)
Click to expand...
Click to collapse
Didn't see this reply until now (for some reason I do t have an auto notify for my posts.)
The carrier is Telus, a Canadian provider. In the past they've been identical in software to AT&T hardware and I've been able to use files made for those phones.
I'll have a dig and see what I can do. Thanks for your help and apologies in not seeing this until now!
sh0nuff said:
Didn't see this reply until now (for some reason I do t have an auto notify for my posts.)
The carrier is Telus, a Canadian provider. In the past they've been identical in software to AT&T hardware and I've been able to use files made for those phones.
I'll have a dig and see what I can do. Thanks for your help and apologies in not seeing this until now!
Click to expand...
Click to collapse
Hello man.
I want to know if you've been able to remove the retail mode ?
Title says it. I'm requesting a stock LGUP partition dump from an LG V30. Please provide one from version 20o or 20k. Preferrably unrooted, stock, minimum alterations, and NO 'FRANKENSTEIN' cross-flashed H932 devices! I'm going to test to see if a system dump from a T-Mobile H932 can allow me to unlock LTE band 71 on all LG V30 (JOAN) variants. I discovered I could unlock LTE band 12 on my Verizon VS996 -> USA OPEN US998 Frankenstein phone. Though I cross-flashed, I couldn't get LTE band 12. I fixed it by creating a flashable H931 (AT&T) zip from partitions I found online. Most importantly, flashing modem, modemst1, and modemst2 alone seems to have fixed my issue. I do realize doing this could brick my device, as the H932 has a different RSA key than all the other variants.
The issue: The 3 hidden LTE band selection menus (LG LTE Band Selection, TMO Only, and iot band selection) don't really enable all LTE bands that the V30 (JOAN) supports. Band 71 is for sure sabotaged on all devices but the H932, and the hidden menu doesn't seem to enable it. Similarly for me, no hidden menu could enable band 12 for me, maybe because I was coming from a Verizon VS996 (though this is a special case, no one else has reported this).
The fix: Flash working modem, modemst1, and modemst2 partitions from a working T-Mobile H932. OR flash working H932 modemst1 and modemst2 partitions only. OR flash working H932 system, boot, modem, modemst1 and modemst2 partitions.
*I've flashed an H932 modem before onto my Frankenstein phone without issue, and no bootloop. So maybe it is not RSA-locked...
Anyways, kindly upload your T-Mobile H932 dump (zipped). It can be around 8GB unzipped, and then 3.2GB zipped.
LGUP Install Procedure:
1. Download and install LG USB drivers (under USB Driver) here
2. Download and install LG UP 1.14.3 from here
3. Download .dll file for LG V30 here
4. Navigate to C:\Program Files (x86)\LG Electronics\LGUP\model
5. Create folder called "common" and unzip the .dll file inside of it.
LGUP Patch Procedure:
1. Extract (confirm replace, yes) LGUP+V30DLL_PATCHED.zip to C:\Program Files (x86)\LG Electronics\LGUP
2. Extract LGUP_common.dll in LGUP_common_DLL_V30_ALLVARIANTS.zip to C:\Program Files (x86)\LG Electronics\LGUP\model\common
3. Reboot computer
LGUP Dump Procedure:
1. Update software to latest H932 20o (check for system updates)
2. Turn off phone
3. Connect micro usb cable to computer
3. Hold volume up button and connect the usb cable
4. Open LGUP
5. Select DUMP
6. DON'T select partitions: userdata or data, and cache.
7. Click OK
8. Create a ZIP from all the partition dumps (should be around 30 files)
9. Upload ZIP to Google Drive or MEGA.
patato21 said:
Title says it. I'm requesting a stock LGUP partition dump from an LG V30. Please provide one from version 20o or 20k. Preferrably unrooted, stock, minimum alterations, and NO 'FRANKENSTEIN' cross-flashed H932 devices!
Click to expand...
Click to collapse
If you knew about the topic, you would know there's no such thing as Frankenstein H932. This is why they can't use WTF.
This is also why I doubt your statements in the other thread about LTE bands 12 and 13.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
If you knew about the topic, you would know there's no such thing as Frankenstein H932. This is why they can't use WTF. This is why I doubt your statements in the other thread about LTE bands 12 and 13.
Click to expand...
Click to collapse
It is possible to have a H932 -> US998 Frankenstein by merely flashing system and boot. Which definitely don't have an RSA key. Why would I have a reason to lie about my situation? It is not impossible for these two scenarios to happen.
patato21 said:
It is possible to have a H932 -> US998 Frankenstein by merely flashing system and boot. Which definitely don't have an RSA key. Why would I have a reason to lie about my situation? It is not impossible for these two scenarios to happen.
Click to expand...
Click to collapse
I wrote the instructions for Frankenstein and there's very little you can cross flash between the other North American variants and T-Mobile H932. Not enough to call it Frankenstein.
@runningnak3d is the expert on this, and I deferring him. (This below is quote from @runningnak3d, but some apps don't show the quote reference. So view in web browser.)
__________
https://forum.xda-developers.com/showpost.php?p=76319892&postcount=34
runningnak3d said:
Here is the list of all files that are flashed in a KDZ that are signed with the RSA cert. If just ONE of these doesn't match the key in your CPU, you will probably have a 9008 brick. Some just won't load, and your phone won't work until you flash the proper KDZ (for example modem), but the fact of the matter is -- it is NOT possible to crossflash ANY of these files IF the RSA key in your CPU doesn't match the signature on these files:
Code:
ablbak.image
abl.image
apdp.image
cmnlib64bak.image
cmnlib64.image
cmnlibbak.image
cmnlib.image
devcfgbak.image
devcfg.image
hypbak.image
hyp.image
keymasterbak.image
keymaster.image
modem.image
msadp.image
pmicbak.image
pmic.image
rpmbak.image
rpm.image
storsecbak.image
storsec.image
tzbak.image
tz.image
xbl2.image
xbl.image
If you have an unlocked bootloader, this is the list of files that you can flash without worrying about the RSA key:
Code:
boot.image
recoverybak.image
recovery.image
lafbak.image
laf.image
system.image
userdata.image
If you do not have an unlocked bootloader, and you flash one of the above files WITHOUT flashing the corresponding abl, you will bootloop and never be able to fix your phone. So, if you have a locked bootloader, then you must flash ALL of the partitions listed as being checked by the RSA key, and ALL of the partitions listed here. If you don't -- you will not have a working phone.
And finally, this is the list of files that you can cross flash that aren't checked by the RSA key in the CPU nor dm-verity:
Code:
cache.image
carrier.image
drm.image
eksst.image
encrypt.image
eri.image
factory.image
ftm.image
grow.image
keystore.image
logfs.image
misc.image
mpt.image
operatorlogging.image
persist.image
pstore.image
qni.image
raw_resourcesbak.image
raw_resources.image
rct.image
sec.image
sns.image
srtc.image
ssd.image
Click to expand...
Click to collapse
_____________
1) the whole point of Frankenstein is to carrier unlock the phone and/or get fastboot flash commands to unlock the bootloader. Frankenstein is done BEFORE bootloader unlock. The two partitions you mention require bootloader unlock. Even if theoretically possible, no one is going to flash those from H932 onto their carrier unlocked, bootloader unlocked phone for any reason whatsoever. Why would they? They already have what they need , and it would only potentially mess up their phone in many different ways.
2) There's tons of Frankensteined North America variants on T-mobile (AS998, VS996, H931, H933 converted to US998) - - including Wi-Fi calling, which I'm pretty sure requires LTE band 12 - - and no one else except you has said they can't get it? I am glad you fixed your problem, but as you mentioned in your post, only you have reported it.
I say if you DL partition with dev patched LGUP, it will overwrite the partitions, including modem partitions. I can't see how your modem partitions stayed as VS996.
patato21 said:
Band 71 is for sure sabotaged on all devices but the H932, and the hidden menu doesn't seem to enable it.
Click to expand...
Click to collapse
If you can bring LTE band 71 to other V30 models, then more power to you.
We aren't disagreeing about that. I hope you succeed.
ChazzMatt said:
I wrote the instructions for Frankenstein and there's very little you can cross flash. Not enough to call it Frankenstein.
@runningnak3d is the expert on this.
All I know is there's tons of Frankensteined North America variants on T-mobile - - including Wi-Fi calling which I'm pretty sure requires LTE band 12 - - and no one else except you has said they can't get it.
I am glad you fixed your problem, but as you mentioned in your post, only you have reported it.
I say it you DL partition with dev patched LGUP, if will overwrite the partitions, including modem partitions. I can't see how the modem partitions are exceptions.
Click to expand...
Click to collapse
Ironically I appear to be stuck on band 2 >.> LS998 > US998
me2151 said:
Ironically I appear to be stuck on band 2 >.> LS998 > US998
Click to expand...
Click to collapse
Did you use the hidden menu to choose LTE bands? I made that mistake, it sticks on the last one you choose. I started a thread about it and there's a solution.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Did you use the hidden menu to choose LTE bands? I made that mistake, it sticks on the last one you choose. I started a thread about it and there's a solution.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Not to hijack the thread, can you try this file?
I get Dolby in the LG music app, but not the actual icon.
I'm guessing that the same reasons the different v20 got real Dolby applies to the v30 as well.
Sent from my LG-H932 using XDA Labs
Edit, not my work
https://forum.xda-developers.com/v20/themes/mod-stock-lg-music-app-dolby-sound-fx-t3812459
ChazzMatt said:
snip
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
As you can see, this is how the stock file looks.
Sent from my LG-H932 using XDA Labs
ChazzMatt said:
Did you use the hidden menu to choose LTE bands? I made that mistake, it sticks on the last one you choose. I started a thread about it and there's a solution.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Nope never used the hidden menu
@potato21 If you want the H932 modem just download one of the H932 TWRP flashable zips and extract it. It is most definitely RSA signed, however, the hole in the US998 abl that allows the WTF unlock method to work may also break the boot chain of trust. In other words .. yes, you may be able to flash the H932 modem. That is what sucks about the fact that abl is encrypted .. can't decompile to check.
As for getting a dump of modemst1 and 2 .. someone will have to dump them with LG UP, or if they are rooted, just boot to TWRP and use dd.
To anyone willing to do it .. you IMEI is contained in fsg, so you are safe sending st1 and st2.
-- Brian
runningnak3d said:
@potato21 If you want the H932 modem just download one of the H932 TWRP flashable zips and extract it. It is most definitely RSA signed, however, the hole in the US998 abl that allows the WTF unlock method to work may also break the boot chain of trust. In other words .. yes, you may be able to flash the H932 modem. That is what sucks about the fact that abl is encrypted .. can't decompile to check.
As for getting a dump of modemst1 and 2 .. someone will have to dump them with LG UP, or if they are rooted, just boot to TWRP and use dd.
To anyone willing to do it .. you IMEI is contained in fsg, so you are safe sending st1 and st2.
-- Brian
Click to expand...
Click to collapse
Modem is installable. no rsa on it(that works properly) however it fails hardware checks. so it wont start. It might be possible to hex some changes in to allow it to start on the other models though.
me2151 said:
Modem is installable. no rsa on it(that works properly) however it fails hardware checks. so it wont start. It might be possible to hex some changes in to allow it to start on the other models though.
Click to expand...
Click to collapse
The modem firmware is most certainly RSA signed, and *usually* verified by abl in the boot chain of trust. If you can flash the H932 modem on a WTF rooted phone, that means that whatever eff-up that LG did with that abl broke the boot chain of trust:
Code:
binwalk -e modem.img --dd="x509"
openssl asn1parse -inform DER -in 1D2A8.crt
0:d=0 hl=4 l=1164 cons: SEQUENCE
4:d=1 hl=4 l= 884 cons: SEQUENCE
8:d=2 hl=2 l= 3 cons: cont [ 0 ]
10:d=3 hl=2 l= 1 prim: INTEGER :02
13:d=2 hl=2 l= 3 prim: INTEGER :0E1CA0
18:d=2 hl=2 l= 13 cons: SEQUENCE
20:d=3 hl=2 l= 9 prim: OBJECT :sha256WithRSAEncryption
<snip>
499:d=5 hl=2 l= 3 prim: OBJECT :organizationalUnitName
504:d=5 hl=2 l= 25 prim: UTF8STRING :01 0000000000000004 SW_ID
So, that opens up a world of possibilities if LG screwed up and broke the chain of trust and you are able to flash H932 firmware onto other devices. You wouldn't be able to flash xbl or abl (obviously), but other than that you could convert a phone to an H932.
Remember the PBL verifies XBL, and XBL verifies ABL. If the chain of trust stops there ... the LG V30 may be the most awesome phone currently in production.
-- Brian
do you still need the files?
DSTNMZ said:
do you still need the files?
Click to expand...
Click to collapse
You do NOT want to send someone that complete dump. Sending modemst1 and modemst2 is OK, but there are a lot of files from a full dump that contain info that is specific to your phone -- for example (from your dump) fsg_COM5 contains your IMEI, serial number, and other info. misc_COM5 contains your serial number, and (while not very important) your bt and wifi MAC addresses.
-- Brian
DSTNMZ said:
do you still need the files?
Click to expand...
Click to collapse
I would like modem,modemst1 and modemst2 please
runningnak3d said:
You do NOT want to send someone that complete dump. Sending modemst1 and modemst2 is OK, but there are a lot of files from a full dump that contain info that is specific to your phone -- for example (from your dump) fsg_COM5 contains your IMEI, serial number, and other info. misc_COM5 contains your serial number, and (while not very important) your bt and wifi MAC addresses.
-- Brian
Click to expand...
Click to collapse
I would not send everything, I put that image as a sample to see what I had obtained, I would only send the parts that are required, and thanks to you now I know that I should not send those files that you mention (fsg_COM5 and misc_COM5) , I am sorry the English language is not my language native in case it does not make sense what I say
---------- Post added at 03:31 PM ---------- Previous post was at 03:23 PM ----------
me2151 said:
I would like modem,modemst1 and modemst2 please
Click to expand...
Click to collapse
there you have it
https://drive.google.com/file/d/1MxbCBGbujzWWnOg35ePk35KVh5sabJ4h/view?usp=sharing
DSTNMZ said:
I would not send everything, I put that image as a sample to see what I had obtained, I would only send the parts that are required, and thanks to you now I know that I should not send those files that you mention (fsg_COM5 and misc_COM5) , I am sorry the English language is not my language native in case it does not make sense what I say
---------- Post added at 03:31 PM ---------- Previous post was at 03:23 PM ----------
there you have it
https://drive.google.com/file/d/1MxbCBGbujzWWnOg35ePk35KVh5sabJ4h/view?usp=sharing
Click to expand...
Click to collapse
Thanks
EDIT: Tmobile modemst1 and st2 work just fine on frankenstein
me2151 said:
Thanks
EDIT: Tmobile modemst1 and st2 work just fine on frankenstein
Click to expand...
Click to collapse
So you have working band 71 now?
-- Brian
runningnak3d said:
So you have working band 71 now?
-- Brian
Click to expand...
Click to collapse
No idea. I dont have band 71 in my area nor am i on stock to try to force it
Posting this PM conversation here as I prefer to answer in threads so others with same issue in the future can also be helped.
DDragons said:
Chazz,
I'm not sure what the difference is or what my options are at this point.
I picked up a LG V30+, which I thought was a US998 or at least that's what it says on my phone (Hardware Info). But when I ran the iemi # it comes back as an LS998.
Honestly don't know what the difference is and wouldn't care except for the fact that I can't send SMS text msgs. Seems like everything works even receiving SMS msg's just can't send. Oh and it turns out I can't see/view the SMSC #, which I guess is a big deal in regards to sending SMS msg's.
So I've been browsing through this site and you seem to be well versed and would like your opinion/advise if I may.
Q1) Will updating the firmware help?
> Says I'm @ Rev 1.0
Q2) Will updating the software help?
> says I'm at US99810d and Android Ver 7.1.2
Any suggestions/thoughts would be greatly appreciated.
Thanks,
Dirty D.
Click to expand...
Click to collapse
ChazzMatt said:
What carrier are you using?
I'll post your question in the forum and reply more there, so other people can be helped also.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
DDragons said:
I'm on Cricket.
Click to expand...
Click to collapse
GENERAL INFO
Yeah, most new and "mint" (like new) US998 V30+ on the market right now (eBay, even Wal-mart) are former LS998 which have been converted to US998 by 3rd party wholesalers trying to offload excess LS998 V30+ stock. Basically like our Frankenstein but probably done though Octopus box or some mass version of that.
{
"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"
}
I've noticed they often will convert to US998 but leave on Nougat for some reason. Maybe their Octopus box can't do Oreo for some reason? To me, that's a half-finished conversion! When I do it, I go all the way to Oreo!
Sometimes they will actually claim "US998" in the listing -- while other times they will say "unlocked V30+" but then list the US998 bands (which are different from the Sprint LS998 bands), so you assume it's a US998. Neither is technically incorrect, nor lying. It IS now a US998, and it does now have US998 bands... The BEST way I have seen is where they claim "UNLOCKED LS998" -- and when you get it, it's of course converted to US998, as that's the only way to unlock an LS998.
Caveats with former LS998 converted to US998:
If you use Verizon you would run into issues ACTIVATING a new SIM card with a former Sprint phone. You would need an already-activated Verizon SIM card. That's the only quibble I have with the converted LS998, where the origin is not fully disclosed. It doesn't bother me as I use Prepaid AT&T, but I have to warn others.
Sprint customers can't use it on Sprint, as it's no longer really an LS998. Sprint won't allow US998 (even former LS998) on their network. But advertising an "unlocked" LS998 might be attractive to a Sprint user who is thinking of switching to another carrier in the future or to buy a phone that can easily be re-sold. They should be told upfront it's a FORMER Sprint LS998.
None of the sellers are lying; it's just a hard situation to describe if you're not familiar with the V30.
Recently in December, I wanted a new (original) US998 V30+ with warranty as a backup, as I had given away all my converted LS998 V30+ > US998 V30+. My wife and I have original US998 V30/V30+, but I alway like having a new backup in a box in case of emergency. So, I specifically bought NEW US998 V30+ from online Wal-mart. Or thought I did! When I picked it up at local Wal-mart I found it's new V30+ all right -- but converted from LS998.... I kept it anyway, as I know it will work fine. But this time I was specifically wanting an "original" US998, even though I had bought converted ones before and had converted two myself.
Anyway, the point to all this is yes, you have a former LS998 converted to US998. So, do several of my friends and my wife used one for awhile. They all work fine on AT&T network. Cricket runs on AT&T network, as it's an AT&T-owned MNVO.
____
SOLUTION #1
What is possibly the issue is your Cricket APN. Go to your mobile settings and check your APN against this:
https://apn-settings.com/us/cricket-wireless-apn-settings/
You are still on Nougat, so you should be able to edit your APN settings. On Oreo that capability is locked out, but there are workarounds on Oreo and with root you can still edit APN on Oreo, I believe.
SOLUTION #2
Another option you can try is Master Reset. Sort of like a factory reset but more powerful.
With your device powered off, press and hold the Power button and Volume Down buttons simultaneously for a few seconds.
When the LG logo appears, quickly release and then re-hold the Power button while keep holding the Volume Down button.
Let go of the buttons when the onscreen menu appears.
When you see the option to Delete all user data (including LG and carrier apps) and reset all settings message prompt, press the Volume Down button to highlight Yes.
Then press the Power button to reset the device.
Wait until the reset is complete then reboot your device. If it’s able to boot up successfully, proceed with the initial setup.
SOLUTION #3
As far as the SMSC #, not sure why you can't view it, but the US998 (which you have now) has Hidden Menu which lets you delve deep into various settings. BE VERY CAREFUL in the Hidden Menu. You can mess up stuff, especially if you try to enable additional LTE bands. Don't do that. In the US998 that option doesn't really enable additional LTE bands, but instead locks you on ONE band (which may or may not work).
I've never had to view SMSC #. I stick in my SIM card and the phone works -- even former LS998 converted to US998. So, I'm not sure that's your issue. More likely the APN settings?
SOLUTION #4
Next, you are on very old version of Android. Nougat. At some point, you do need to update to Oreo as it brings lots of fixes and more features.
This thread below is where the stock KDZ are posted. You can use LGUP to update to newer firmware.
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
The other reason I am mentioning this is because instead of "upgrade", you can use an option called "refurbish". Refurbish re-builds EVERYTHING while also updating the firmware. It's possible whoever converted your LS998 to US998 botched something, which is why your SMS doesn't work. Using this refurbish option will lay the foundation again, totally rebuilding your firmware.
After you use that "refurbish" option, then in the future just choose "upgrade".
___________
Good luck!
Tonight I will edit the post above to clarify and organize better. I offered four different solutions, but it's not as coherent as it could be.
@ChazzMatt you are very helpful and I think we all greatful to have you in v30 community. You're the best bro! ??
ChazzMatt said:
Tonight I will edit the post above to clarify and organize better. I offered four different solutions, but it's not as coherent as it could be.
Click to expand...
Click to collapse
Done.
ChazzMatt said:
Done.
Click to expand...
Click to collapse
Okay so heres what/where im at.
1) I was able to view and edit the smsc # when the sim was in my old LG device. So i did so and then moved it to my new LG (V30+)
2) Checked & edited the APN
3) Changed the network node from Global to LTE/GSM/UMTS
4) Downloaded LGUP & upgraded
5) Nothing changed on the hardware side - still @ Rev 1.0 but on the software side i'm now at US99820b and Andriod Ver 8.0.0. Its to late to test tonight but tomorrow i'll attempt to send SMS & MMS messages.
ChazzMatt said:
Done.
Click to expand...
Click to collapse
Wow. On the XDA app Solution #1 and #2 don't even show. You have to read on web browser.
DDragons said:
Okay so heres what/where im at.
1) I was able to view and edit the smsc # when the sim was in my old LG device. So i did so and then moved it to my new LG (V30+)
2) Checked & edited the APN
3) Changed the network node from Global to LTE/GSM/UMTS
4) Downloaded LGUP & upgraded
5) Nothing changed on the hardware side - still @ Rev 1.0 but on the software side i'm now at US99820b and Andriod Ver 8.0.0. Its to late to test tonight but tomorrow i'll attempt to send SMS & MMS messages.
Click to expand...
Click to collapse
Good on APN and the LTE/GSM/UMTS choice.
You only updated to US998 20B (for now) because you intend to unlock the bootloader and root?
ChazzMatt said:
Good on APN and the LTE/GSM/UMTS choice.
You only updated to US998 20B (for now) because you intend to unlock the bootloader and root?
Click to expand...
Click to collapse
Well to be perfectly honest, im already out of my comfort zone. Didnt want to make/take to many changes/chances... Not having any experience in this realm to begin with. It was a leap of faith to begin with.
Do appreciate the knowledge share provided for such a novice like me.
ChazzMatt said:
Good on APN and the LTE/GSM/UMTS choice.
You only updated to US998 20B (for now) because you intend to unlock the bootloader and root?
Click to expand...
Click to collapse
So I'm not sure of the need or benefit of upgrading from US998 20B to whatever the latest is (appears to be 20G), but should I get the courage to do so, what would the process be?
Would it be as simple as plugging in the phone to the computer and then launch LGUP, selecting upgrade and the 20g kdz? If so I'd be more inclined to do so if their are substantial benefits for doing so.
DDragons said:
So I'm not sure of the need or benefit of upgrading from US998 20B to whatever the latest is (appears to be 20G), but should I get the courage to do so, what would the process be?
Would it be as simple as plugging in the phone to the computer and then launch LGUP, selecting upgrade and the 20g kdz? If so I'd be more inclined to do so if their are substantial benefits for doing so.
Click to expand...
Click to collapse
Yes, it's almost that easy. However, since there's such a large range of changes (especially to audio framework) form 20B to 20G, best to do it in stages. "upgrade" to 20E, reboot, let it settle a few minutes. "Upgrade" to 20F, reboot, let it settle, same with 20G, done.
I wasn't sure exactly what LGUP method you used to get to 20B from Nougat -- whether "upgrade", DL Partition or "refurbish". If the latter two you could have gone straight from Nougat to 20G. But now that you are on 20B, and you want to use "upgrade" (to keep your settings and data), do in those stages.
Since 20B, camera is improved, front and rear. DTS audio framework is introduced. While you still need root to fully enable it, hopefully that will be fixed by LG in upcoming update. Other fixes. Here's the changelog for US998 20F alone.
change log:
- DTS: X 3D stereo effect function has been added.
- New Always On Display options
- Selfie camera portrait mode
- Improved accessibility.
- Improved keyboard performance
- Improved the delay of keyboard input when installing multiple market apps at once.
- Photo display error in some apps since Google's latest security patch has been improved.
- Improved to keep app aspect ratio settings after app updates.
- Improved the phenomenon that fine lines are displayed on some screens when power saving mode is executed.
- Google Security Update has enhanced your phone's security.
Most of the list is found here in the link below -- plus the AOD and selfie camera portrait feature are from public reports. The AOD I verified myself, but the selfie thing seems to be subtle.
But there were other changes between 20B and 20F, and maybe more changes with 20G.
ChazzMatt said:
Good on APN and the LTE/GSM/UMTS choice.
You only updated to US998 20B (for now) because you intend to unlock the bootloader and root?
Click to expand...
Click to collapse
Alright talked me into it and now at 20g.
Bought unlocked US998 V30+, but it's former LS998 -- HOW TO UPDATE?
I'm adding onto this already-created post as it's still relevant. The person below also bought a US998 V30+ and found it's former LS998 V30+ converted to US998, but is still on older US998 Nougat firmware. The dealer/wholesaler probably did via Octopus box or something similar, while we use Frankenstein conversion via Dev Patched LGUP. But we always "finish" the process by then updating to Oreo. So, it's basically an "unfinished" Frankenstein conversion.
They don't have the SMS issue the first person had in this thread, but it's still same underlying issue. LS998 V30+, now on Nougat US998 and they want to update to current Oreo firmware...
Hi ChazzMatt,
I have a question. I am hoping you are willing to help me.
I have an LG V30+ unlocked mobile phone. It says US998 but I just found out that it is actually LS998 (I typed in the IMEI into this website to check what it truly was and it came back as LS998).
The vendor that sold it to me changed the firmware to US998 and I guess removed all the Sprint bloatware or whatever from the phone.
All is totally fine – the phone works great – no issues – I love it and for the low price I got it for it is fine…Except, because of the above, I do not receive any OTA updates.
See attached screenshots of my phone, it is out of date in terms of software and OS and from what I learned from online posts I will never receive any OTA updates.
Is this a problem? Should I update it manually? Can I?
Thank you for your help in advance.
Click to expand...
Click to collapse
chazzmatt said:
Yes, most US998 V30+ nowadays being sold are already-converted LS998 V30+. You can update to most recent US998 Oreo KDZ via our Dev Patched LGUP.
Later tonight I'll answer more fully.
Click to expand...
Click to collapse
Yes, the only way to carrier unlock a Sprint LS998 V30+ is to convert it to a North American V30/V30+ carrier unlocked version, using a process which we call Frankenstein. The US998 is the most popular firmware to convert LS998 to, as besides being carrier unlocked is also the only North American V30-series variant with fastboot flash commands (which are necessary if you ever want to unlock bootloader, install TWRP custom recovery and root). The remainder of this answer is on the assumption you do NOT wish to root at this time, but merely wish to update to most current US998 V30/V30+/V30S firmware.
SOLUTION
You can go to the US998 KDZ thread and use Dev Patched LGUP to update to US998 20G KDZ (most current US998 firmware at the moment). Dev Patch LGUP is attached to post #1 of that thread, and there are instructions on how to install LGUP, with screenshots on how to use it.
However, in this instance I would recommend using Dev Patched LGUP in "Refurbish" or "Partition DL" (choosing all partitions) mode -- which while it will wipe out your data, will probably present the least problems. There are a lot of audio framework changes with most recent US998 firmware (especially with 20F and 20G) and if you use "Update" mode (instead of "Refurbish" or "Partition DL") you would have to update in stages to 20E, then 20F, then 20G. Best to do it in one step, with "Refurbish" or "Partition DL".
In the future, with other KDZ you would merely use "Update" mode, which WILL keep all your data. It's like receiving OTA updates, but you would be flashing it manually.
MORE INFORMATION
Just for more information (if you are interested) you can also read this Frankenstein Instructions post, on how to convert from LS998 to US998 Oreo -- but several steps have already been done for you. You are already on US998 Nougat. The only step left is to update to US998 Oreo. In that post, you would be on Step #4. Ignore that it says to use "Update" mode. In this instance, I think you should use Refurbish or Partition DL mode. You can use "Update" in the future.
Hope this helps.
Thanks for the great advises Chazz. I was looking for a phone for my dad and your posts made me decided to get the LG V30 for him. I'm still waiting for the phone to come but I'm pretty sure that I got one of these converted ones. I've been reading your posts about converting, rooting, enable DTS. From what I understand, I will need to:
1/ Start at step #4 in the Frankenstein instruction (using REFURBISHED and 20b to obtain unlock bootloader) if my phone already has Nougat.
2/ Upgrade to the latest Oreo 20g
3/ Follow this post to root https://forum.xda-developers.com/lg-v30/help/unlocking-rooting-twrp-magisk-step-step-t3745006
4/ Follow this post to Enable DTS https://forum.xda-developers.com/lg-v30/how-to/enable-dts-3d-stereo-lg-v30-variants-t3887139
5/ Enjoy it.
Is it in the right order or did I mess up between step 2 and 3? Is there any root level adblock? Thanks. I'm using the s9+ but I'm really excited about the V30.
hytl said:
Thanks for the great advises Chazz. I was looking for a phone for my dad and your posts made me decided to get the LG V30 for him. I'm still waiting for the phone to come but I'm pretty sure that I got one of these converted ones. I've been reading your posts about converting, rooting, enable DTS. From what I understand, I will need to:
1/ Start at step #4 in the Frankenstein instruction (using REFURBISHED and 20b to obtain unlock bootloader) if my phone already has Nougat.
2/ Upgrade to the latest Oreo 20g
3/ Follow this post to root https://forum.xda-developers.com/lg-v30/help/unlocking-rooting-twrp-magisk-step-step-t3745006
4/ Follow this post to Enable DTS https://forum.xda-developers.com/lg-v30/how-to/enable-dts-3d-stereo-lg-v30-variants-t3887139
5/ Enjoy it.
Is it in the right order or did I mess up between step 2 and 3? Is there any root level adblock? Thanks. I'm using the s9+ but I'm really excited about the V30.
Click to expand...
Click to collapse
#3 is incorrect. Outdated instructions with old TWRP. Those Instructions were for official bootloader unlock code from LG, which we don't need. We no longer need LG permission to root our phones, plus only a few phones were even eligible under that program. A converted LS998 would not be, nor even most US998.
You want the WTF Instructions. You would use this to unlock bootloader, install TWRP custom recovery and root.
You would merely update from US998 Nougat to US998 20B, install TWRP, and follow the instructions to finish rooting.
After bootloader unlock, TWRP and root on 20B, I would then update to TWRP-flashable zip US998 20G in stages. 20E, 20F, then 20G due to the huge audio changes. (The alternative to this would be to refurbish to 20G, but then you would have to reinstall TWRP and re-root. Let's not do that.)
@JohnFawkes actually has DTS enabled on US998 20F and US998 20G TWRP-flashable zips, through build prop edits -- but you would still need to install the DTS Equalizer.
You have the right idea, just changing the order a bit.
ChazzMatt said:
#3 is incorrect. Outdated instructions with old TWRP. Those Instructions were for official bootloader unlock code from LG, which we don't need. We no longer need LG permission to root our phones, plus only a few phones were even eligible under that program. A converted LS998 would not be, nor even most US998.
You want the WTF Instructions. You would use this to unlock bootloader, install TWRP custom recovery and root.
You would merely update from US998 Nougat to US998 20B, install TWRP, and follow the instructions to finish rooting.
After bootloader unlock, TWRP and root on 20B, I would then update to TWRP-flashable zip US998 20G in stages. 20E, 20F, then 20G due to the huge audio changes. (The alternative to this would be to refurbish to 20G, but then you would have to reinstall TWRP and re-root. Let's not do that.)
@JohnFawkes actually has DTS enabled on US998 20F and US998 20G TWRP-flashable zips, through build prop edits -- but you would still need to install the DTS Equalizer.
You have the right idea, just changing the order a bit.
Click to expand...
Click to collapse
Thank you so much for the instruction. I'm going to spend this afternoon to go over all of the posts before I do anything.
hytl said:
Thank you so much for the instruction. I'm going to spend this afternoon to go over all of the posts before I do anything.
Click to expand...
Click to collapse
Be sure to read WTF INSTRUCTIONS on web browser, not on XDA app. XDA app truncates sections of very long posts like that.
Print out to read if you can.
Thank you
ChazzMatt said:
Bought unlocked US998 V30+, but it's former LS998 -- HOW TO UPDATE?
I'm adding onto this already-created post as it's still relevant. The person below also bought a US998 V30+ and found it's former LS998 V30+ converted to US998, but is still on older US998 Nougat firmware. The dealer/wholesaler probably did via Octopus box or something similar, while we use Frankenstein conversion via Dev Patched LGUP. But we always "finish" the process by then updating to Oreo. So, it's basically an "unfinished" Frankenstein conversion.
They don't have the SMS issue the first person had in this thread, but it's still same underlying issue. LS998 V30+, now on Nougat US998 and they want to update to current Oreo firmware...
Yes, the only way to carrier unlock a Sprint LS998 V30+ is to convert it to a North American V30/V30+ carrier unlocked version, using a process which we call Frankenstein. The US998 is the most popular firmware to convert LS998 to, as besides being carrier unlocked is also the only North American V30-series variant with fastboot flash commands (which are necessary if you ever want to unlock bootloader, install TWRP custom recovery and root). The remainder of this answer is on the assumption you do NOT wish to root at this time, but merely wish to update to most current US998 V30/V30+/V30S firmware.
SOLUTION
You can go to the US998 KDZ thread and use Dev Patched LGUP to update to US998 20G KDZ (most current US998 firmware at the moment). Dev Patch LGUP is attached to post #1 of that thread, and there are instructions on how to install LGUP, with screenshots on how to use it.
However, in this instance I would recommend using Dev Patched LGUP in "Refurbish" or "Partition DL" (choosing all partitions) mode -- which while it will wipe out your data, will probably present the least problems. There are a lot of audio framework changes with most recent US998 firmware (especially with 20F and 20G) and if you use "Update" mode (instead of "Refurbish" or "Partition DL") you would have to update in stages to 20E, then 20F, then 20G. Best to do it in one step, with "Refurbish" or "Partition DL".
In the future, with other KDZ you would merely use "Update" mode, which WILL keep all your data. It's like receiving OTA updates, but you would be flashing it manually.
MORE INFORMATION
Just for more information (if you are interested) you can also read this Frankenstein Instructions post, on how to convert from LS998 to US998 Oreo -- but several steps have already been done for you. You are already on US998 Nougat. The only step left is to update to US998 Oreo. In that post, you would be on Step #4. Ignore that it says to use "Update" mode. In this instance, I think you should use Refurbish or Partition DL mode. You can use "Update" in the future.
Hope this helps.
Click to expand...
Click to collapse
Thanks ChazzMatt. Thanks so much for the details! Oh boy - Seems doing this will erase all the data on my phone. I have had it for a few months now and not sure I want to wipe everything out. Not sure I feel confident to do the this. Is it worth it?
PaulaL19 said:
Thanks ChazzMatt. Thanks so much for the details! Oh boy - Seems doing this will erase all the data on my phone. I have had it for a few months now and not sure I want to wipe everything out. Not sure I feel confident to do the this. Is it worth it?
Click to expand...
Click to collapse
If you don't want to wipe your data, then try Upgrade mode in LGUP.
I was just giving you the answer that will definitely give you best results.
If you use Upgrade mode, you can try to go straight to US998 20G...
but if that gives you audio problems, then go to 20E, then 20F, then 20G in Update mode.
You would download and flash the various US998 Oreo KDZ from this thread with LGUP.
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
Sent via open market LG US998 V30/V30+
ChazzMatt said:
If you don't want to wipe your data, then try Update mode in LGUP.
I was just giving you the answer that will definitely give you best results.
If you use Update mode, you can try to go straight to US998 20G...
but if that gives you audio problems, then go to 20E, then 20F, then 20G in Update mode.
You would download and flash the various US998 Oreo KDZ from this thread with LGUP.
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
No worries. Thank you very much.
Your help is much appreciated!!
I have a ls998 that was flashed to us998 and the IMEI disappeared
Can someone she'd some light on how to fix this?
Thanks
I have a LGv30 VS996 that has been bootloader unlocked using WTF and is currently flashed and working great with a US998 stock firmware.
I would like to use VOLTE/VOWIFI but it is not showing up as an option for me.
My local region (I'm in Asia) uses the H903DS variant of LGv30 and they have a stock ROM for that device which I'm hoping will enable the VOLTE/VOWIFI options.
My question is, will that work? Are VS996/US998 similar enough to H903DS that I can cross flash?
skippybosco said:
I have a LGv30 VS996 that has been bootloader unlocked using WTF and is currently flashed and working great with a US998 stock firmware.
I would like to use VOLTE/VOWIFI but it is not showing up as an option for me.
My local region (I'm in Asia) uses the H903DS variant of LGv30 and they have a stock ROM for that device which I'm hoping will enable the VOLTE/VOWIFI options.
My question is, will that work? Are VS996/US998 similar enough to H903DS that I can cross flash?
Click to expand...
Click to collapse
Uhmmm... You can't fully CONVERT any North American phone to any H930* phone like Frankenstein can do to each other with most North American variants, but you can flash parts of the H930DS software to VS996 via Dev Patched LGUP in Partition DL mode. However, you have to OMIT certain partitions, like modems and XBL.
People have done this to flash EU H930 firmware over US998 to get East European languages, etc. Every time you flash an updated H930* KDZ, you would have to remember to omit those partitions. You would NOT be changing any bands like with Frankenstein.
See this guide, but change to H930DS KDZ instead of EU H930:
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
Let it complete and restart, if you stuck on LG logo, try reboot again, it will boot completely
Result: H930 30B on a US998 with working network and stuff working (testing on GSM network outside US only, cant confirm Vowifi, VoLTE or any other netwrok stuff.)
Click to expand...
Click to collapse
Read that last sentence.
Good luck.
My V30 doesn't seem to enjoy being flashed with Android 10, as it bootloops no matter what ROM I decide to use (Lineage, Havoc, Pixel Experience), and now I'm thoroughly stumped on what to do, as I can't find a fix for this issue. My phones bootloader is unlocked via Frankenstein, and I've used the method of flashing over 10d with 30b and having no luck. I've recently come across a post that said to attempt trying 20b to 30b, which I'll try as a last effort to get this working, but I'd still appreciate advice on what to do. Whether it be this last method, a modification of it, or just something else entirely, I'd be forever grateful for the help.
If you need more information, feel free to ask and I'll provide to the best of my ability.
AkajiWins said:
My V30 doesn't seem to enjoy being flashed with Android 10, as it bootloops no matter what ROM I decide to use (Lineage, Havoc, Pixel Experience), and now I'm thoroughly stumped on what to do, as I can't find a fix for this issue. My phones bootloader is unlocked via Frankenstein.
Click to expand...
Click to collapse
So you Frankensteined to US998, then unlocked the bootloader via WTF exploit. What variant did you start with?
AkajiWins said:
I've used the method of flashing over 10d (Nougat/Android 7) with 30b (Pie/Android 9) and having no luck. I've recently come across a post that said to attempt trying 20b (early Oreo) to 30b, which I'll try as a last effort to get this working, but I'd still appreciate advice on what to do. Whether it be this last method, a modification of it, or just something else entirely, I'd be forever grateful for the help.
If you need more information, feel free to ask and I'll provide to the best of my ability.
Click to expand...
Click to collapse
1) You need stock Android 9 (Pie) as a base before flashing any LOS-17 (Android 10) ROMs. But you seem to know that.
There are several methods to update to to Pie US998. See US998 Pie KDZ thread, post #2 and FOUR MORE WORKAROUND in post #6.
2) What variant did you start with? If you have former AT&T H931 or Canada H933, you'll need to do additional prep steps before installing any LOS custom ROMs.
Of course, you've read the V30 custom ROMs FAQ -- before you even unlocked your bootloader -- right? It tells all this and conveys other important information. This FAQ is prominently linked in the WTF instructions, with suggestion to read first, then come come back to finish unlocking bootloader...
V30 CUSTOM ROMS FAQ
https://forum.xda-developers.com/showpost.php?p=79459374&postcount=2
ChazzMatt said:
So you Frankensteined to US998, then unlocked the bootloader via WTF exploit. What variant did you start with?
1) You need stock Android 9 (Pie) as a base before flashing any LOS-17 (Android 10) ROMs. But you seem to know that.
There are several methods to update to to Pie US998. See US998 Pie KDZ thread, post #2 and FOUR MORE WORKAROUND in post #6.
2) What variant did you start with? If you have former AT&T H931 or Canada H933, you'll need to do additional prep steps before installing any LOS custom ROMs.
Of course, you've read the V30 custom ROMs FAQ -- before you even unlocked your bootloader -- right? It tells all this and conveys other important information. This FAQ is prominently linked in the WTF instructions, with suggestion to read first, then come come back to finish unlocking bootloader...
V30 CUSTOM ROMS FAQ
https://forum.xda-developers.com/showpost.php?p=79459374&postcount=2
Click to expand...
Click to collapse
Yes, I did read through the FAQ before and after unlocking. My variant is the US998U/V30+, which is why I'm a bit confused. The US998 and US998U are identical, aside from storage capacity, right?
I was following one of the guides you posted that stated:
ChazzMatt said:
So for installing the KDZ, I suggest FIRST downgrading to US998 Nougat 10d via Partition DL mode, Master Reset, then Refurbish to US998 Pie KDZ. Here are the steps...
If you have problems flashing this US998 Pie 30b KDZ, see post #6 for FOUR more workaround methods proven to work for some people.
You should probably use this method (DOWNGRADE to NOUGAT first) even if you have TWRP installed. Then reinstall TWRP again after successfully updating to Pie.
KDZ INSTALLATION INSTRUCTIONS
0) Turn off phone, manually go into Download mode before opening Dev Patched LGUP.
1) Using Dev Patched LGUP from THIS thread, flash US998 10d Nougat KDZ via Dev Patched LGUP using Partition DL mode. Select ALL partitions.
2) Master Reset. This is NOT Factory Reset.
3) Boot up to Welcome screen. Turn off phone, manually go back into Download mode.
4) Flash US998 30b Pie KDZ via Dev Patched LGUP using Refurbish mode.
5) Master Reset. This is NOT Factory Reset.
If you did not unlock your bootloader before doing this, then you bootloader is still locked -- because that's what you want. Finished. Set up your phone.
If you had unlocked bootloader before doing all this, you will still have it. Boot to ADB, and PLEASE follow these instructions for re-install TWRP and root!!
Click to expand...
Click to collapse
So that's what I had done a few days ago, but that's also when my problems arose. I was on the TWRP flashable kdz of 30b for a month or two now after Frankensteining it, but wanted to try out some 10 ROMS, but attempting to flash those ROMs was when I started having issues. Flashing the stock US998 kdzs didn't cause issues, the 30b zip I had been running daily wasn't weird, and the md5s for all the files downloaded matched what was provided as correct. That's why I'm a bit stumped, since I believe I followed all the guides I've looked at to make things work correctly, but this one part is giving me a hard time.
I will try those other four methods, since I don't believe to have seen them yet. I will provide an edit to this post after trying them, thank you.
AkajiWins said:
Yes, I did read through the FAQ before and after unlocking. My variant is the US998U/V30+, which is why I'm a bit confused. The US998 and US998U are identical, aside from storage capacity, right?
I was following one of the guides you posted that stated:
So that's what I had done a few days ago, but that's also when my problems arose. I was on the TWRP flashable kdz of 30b for a month or two now after Frankensteining it, but wanted to try out some 10 ROMS, but attempting to flash those ROMs was when I started having issues. Flashing the stock US998 kdzs didn't cause issues, the 30b zip I had been running daily wasn't weird, and the md5s for all the files downloaded matched what was provided as correct. That's why I'm a bit stumped, since I believe I followed all the guides I've looked at to make things work correctly, but this one part is giving me a hard time.
I will try those other four methods, since I don't believe to have seen them yet. I will provide an edit to this post after trying them, thank you.
Click to expand...
Click to collapse
If you Frankenstein'ed, I'm asking what your original variant is. Frankenstein is to convert North American variant to another, also called cross flashing.
Whereas " WTF" is bootloader unlock and installing TWRP. Some North American variants have to Frankenstein to US998 for fastboot flash commands. Then they can use WTF INSTRUCTIONS. But Frankenstein itself is not bootloader unlock, TWRP and root. It's just fully converting one variant to another. It ONLY works with the North American variants, except for T-Mobile H932.
_____
OK, so you were on LG US998 30b stock Pie successfully.
Put your IMEI into this database and tell me what it says? Don't post your IMEI here, publicly. Just curious what variant it says you have.
https://www.imeipro.info/
If you have V30+ US998 , then it's either native US998U or was formerly LS998U and converted to US998 by you or previous owner if you bought it used.
Neither AT&T H931 not Canada H933 have a native V30+, but I've seen H933 V30+ which were Frankenstein'ed.
ChazzMatt said:
If you Frankenstein'ed, I'm asking what your original variant is. Frankenstein is to convert North American variant to another, also called cross flashing.
Whereas " WTF" is bootloader unlock and installing TWRP. Some North American variants have to Frankenstein to US998 for fastboot flash commands. Then they can use WTF INSTRUCTIONS. But Frankenstein itself is not bootloader unlock, TWRP and root. It's just fully converting one variant to another. It ONLY works with the North American variants, except for T-Mobile H932.
_____
OK, so you were on LG US998 30b stock Pie successfully.
Put your IMEI into this database and tell me what it says? Don't post your IMEI here, publicly. Just curious what variant it says you have.
https://www.imeipro.info/
If you have V30+ US998 , then it's either native US998U or was formerly LS998U and converted to US998 by you or previous owner if you bought it used.
Neither AT&T H931 not Canada H933 have a native V30+, but I've seen H933 V30+ which were Frankenstein'ed.
Click to expand...
Click to collapse
Ahh, alrighty, I understand the difference now. So I had Frankenstein'ed to unlock my bootloader, then unlocked it with "WTF".
Also, the IMEI checker reported my device as a US998U V30+, which was what I bought it as used.
AkajiWins said:
Ahh, alrighty, I understand the difference now. So I had Frankenstein'ed to unlock my bootloader, then unlocked it with "WTF".
Also, the IMEI checker reported my device as a US998U V30+, which was what I bought it as used.
Click to expand...
Click to collapse
Merely downgrading to earlier firmware is not Frankenstein. Frankenstein is fully converting one variant to another. It takes on those different LTE bands, etc. Cross flashing AT&T H931 to US998 gives it CDMA bands the H931 doesn't have, different LTE bands, fastboot flash commands. Same with Frankenstein'ed H933. See screenshot.
If you already had US998 firmware and your IMEI check says it's a native US998U (V30+), then you didn't Frankenstein to US998. You already had US998 with fastboot flash commands. You just used LGUP to downgrade to early US998 Oreo for WTF bootloader unlock, TWRP installation and root and/or maybe you went to US998 Nougat at one point. But you were already US998. You weren't on LS998, AS998, H933, H931, VS996 firmware, at any point in time.
Why you are bootlooping on LOS-17 Android 10 ROMs, I don't know. You don't have former H931 or H933, and you said you were on US998 30b (Pie) when you tried to flash those ROMs.
ChazzMatt said:
Merely downgrading to earlier firmware is not Frankenstein. Frankenstein is fully converting one variant to another. It takes on those different LTE bands, etc. Cross flashing AT&T H931 to US998 gives it CDMA bands the H931 doesn't have, different LTE bands, fastboot flash commands. Same with Frankenstein'ed H933. See screenshot.
If you already had US998 firmware and your IMEI check says it's a native US998U (V30+), then you didn't Frankenstein. You already had US998 with fastboot flash commands. You just used LGUP to downgrade to early Oreo for WTF bootloader unlock, TWRP installation and root.
Why you are bootlooping on LOS-17 Android 10 ROMs, I don't know. You don't have former H931 or H933, and you said you were on US998 30b (Pie) when you tried to flash those ROMs.
Click to expand...
Click to collapse
Should I attempt to Frankenstein to a different variant then come back? I was going to try to use the fourth method that you linked to before to try to put myself on an actual US998.
AkajiWins said:
Should I attempt to Frankenstein to a different variant then come back? I was going to try to use the fourth method that you linked to before to try to put myself on an actual US998.
Click to expand...
Click to collapse
The problem with Method #4 is you are willingly converting to Canada H933. While that might get you back to US998 30b, it will then give you more difficulty in flashing LOS ROMs. You have to go through the tedious extra steps of former H931/H933.
ChazzMatt said:
The problem with Method #4 is you are willingly converting to Canada H933. While that might get you back to US998 30b, it will then give you more difficulty in flashing LOS ROMs. You have to go through the tedious extra steps of former H931/H933.
Click to expand...
Click to collapse
As someone who doesn't necessarily mind the extra preparation, would you recommend it for someone in my predicament? And is there any log file I can provide to hopefully help give more insight?
AkajiWins said:
As someone who doesn't necessarily mind the extra preparation, would you recommend it for someone in my predicament?
Click to expand...
Click to collapse
That's your decision. It should get you back to 30b. After that, for flashing ROMs, you'll have to follow the other instructions for H933 (since you will have converted to that, then converted back).
ChazzMatt said:
That's your decision. It should get you back to 30b. After that, for flashing ROMs, you'll have to follow the other instructions for H933 (since you will have converted to that, then converted back).
Click to expand...
Click to collapse
Though if I am to do that, would I still keep the bands I have at the moment or would I lose them when converting? Would I have to refflash my modem partition(s)?
AkajiWins said:
Though if I am to do that, would I still keep the bands I have at the moment or would I lose them when converting? Would I have to refflash my modem partition(s)?
Click to expand...
Click to collapse
The method is flash to H933 Nougat I believe, then flash back to US998. You don't stay on H933. You flash everything via LGUP Partition DL mode.
ChazzMatt said:
The method is flash to H933 Nougat I believe, then flash back to US998. You don't stay on H933.
Click to expand...
Click to collapse
Ah alright, I'll try that. So just to clarify, I'd flash over to an H933, then come back to a US998, and then install the 30b kdz, and that should hopefully fix my issues?
AkajiWins said:
Ah alright, I'll try that. So just to clarify, I'd flash over to an H933, then come back to a US998, and then install the 30b kdz, and that should hopefully fix my issues?
Click to expand...
Click to collapse
Yes. But read Method 4 carefully. Involves timing and buttons.
ChazzMatt said:
Yes. But read Method 4 carefully. Involves timing and buttons.
Click to expand...
Click to collapse
LGUP doesn't seem to recognize my phone as a H933 after flashing and rebooting back to download mode, but the phone seems to know it's one when I flash and it says what build it's on and what's being flashed.
EDIT 1: Reinstalling LGUP fixed that particular issue, so I'll have to restart the procedure just so it's as unobstructed as possible.
EDIT 2: Never mind, still the same strange occurrence that happened before. I'll try to move on and see if it'll still work.
Okay so, after a lot of trouble, everything seems to work. I ran Jett's Wifi Backup fix to fix the broken wifi on Havoc, along with the Haumea kernel, and now everything seems stable.
Thank you for your help!!
I guess I just had to keep doing the procedure until it stuck
Hi guys, I'm a bit lost too.
My phone is a V300S that is Frankensteined to US998 with V300S modem, bootloader unlocked and installed TWRP.
However i also faced the problem of installing Android 10 based roms causing bootloops, I've seen on the Custom ROMs page that i needed the lastest stock Pie blobs, which is what i have currently (30b)
Is this variant using a different way for custom ROMs? Or did i do something entirely wrong on Frankensteining?
Edit: silly me recently saw that i need to convert my V300S to H930, not US998... I guess I'll try that first
Update: well everything went south, now i can't go back to US99830b anymore, stuck at V300s Oreo. I guess I'll start everything over again, but if there are things or procedures i needed to know, please, any help will do