As mention. I need to crossflash from att to T-mobile to use ota feature.
I followed instruction but always fail at LGUP step.
So someone can DM support me and more.
Thanks !
You can't use ota features when you cross flash because every phone has its special, serial number and IMEI. Once the software status is detected as modified and the model number is different from the software version, you cannot connect to LG or carrier server for update.
Amosika said:
You can't use ota features when you cross flash because every phone has its special, serial number and IMEI. Once the software status is detected as modified and the model number is different from the software version, you cannot connect to LG or carrier server for update.
Click to expand...
Click to collapse
i try change PC, change kdz, still cannot lg up flash
{
"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"
}
Did you boot into edl mode to wipe FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.? Boot into edl mode and back up FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B and erase them one by one after backing up. Please rename each back up you make and save them some where safe just in case something goes wrong. After backup and erase, boot up into download mode immediately by holding power and volume down button at the same time then immediately release them and hold volume up button only when the edl exit sound is heard (don't boot into system or else it will brick). This is the method I used to cross flash my Verizon and all Att devices successfully used it too.
Amosika said:
Did you boot into edl mode to wipe FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B.? Boot into edl mode and back up FTM, OP_A OP_B, MODEM_A MODEM_B, SID_A SID_B and erase them one by one after backing up. Please rename each back up you make and save them some where safe just in case something goes wrong. After backup and erase, boot up into download mode immediately by holding power and volume down button at the same time then immediately release them and hold volume up button only when the edl exit sound is heard (don't boot into system or else it will brick). This is the method I used to cross flash my Verizon and all Att devices successfully used it too.
Click to expand...
Click to collapse
Could you get carrier updates after doing the cross flash?
stormeye25 said:
Could you get carrier updates after doing the cross flash?
Click to expand...
Click to collapse
No. If you want ota update, then stay on your carrier firmware
Amosika said:
No. If you want ota update, then stay on your carrier firmware
Click to expand...
Click to collapse
My amazon refurbished v60 AT&T unlocked is on the way. I will use mint which is t-mobile. Do you have any idea if I will get a12?
stormeye25 said:
My amazon refurbished v60 AT&T unlocked is on the way. I will use mint which is t-mobile. Do you have any idea if I will get a12?
Click to expand...
Click to collapse
With Att there is no kdz and ota update if you're outside USA, so you will need to cross flash and TMobile works but I don't think TMobile android 12 kdz is out yet but global A12 kdz is already out there
Amosika said:
With Att there is no kdz and ota update if you're outside USA, so you will need to cross flash and TMobile works but I don't think TMobile android 12 kdz is out yet but global A12 kdz is already out there
Click to expand...
Click to collapse
I'm sorry I don't understand. What's the difference between att, t mobile and global kdz? I'm in North America currently
stormeye25 said:
I'm sorry I don't understand. What's the difference between att, t mobile and global kdz? I'm in North America currently
Click to expand...
Click to collapse
If you're in North America then you will need Att sim and data plan before you get updates. That's Att policy. They don't release firmware or updates to non Att user on LG smart phones
Amosika said:
If you're in North America then you will need Att sim and data plan before you get updates. That's Att policy. They don't release firmware or updates to non Att user on LG smart phones
Click to expand...
Click to collapse
I understand. Is there any way around this? Reflash, unlock bootloader, anything?
stormeye25 said:
I understand. Is there any way around this? Reflash, unlock bootloader, anything?
Click to expand...
Click to collapse
The only option you have is to make a full backup of all your partition dumps using qfil in edl mode. Check how to do that. If you don't and something happens, you're doomed. Before cross flash, make sure to backup all your dumps first and keep them safe before you try anything just in case something happens or you want to go back to original Att firmware then you restore them
Amosika said:
The only option you have is to make a full backup of all your partition dumps using qfil in edl mode. Check how to do that. If you don't and something happens, you're doomed. Before cross flash, make sure to backup all your dumps first and keep them safe before you try anything just in case something happens or you want to go back to original Att firmware then you restore them
Click to expand...
Click to collapse
I get the idea. Is it okay if I pm you when I do that I'm case I have some questions?
stormeye25 said:
I get the idea. Is it okay if I pm you when I do that I'm case I have some questions?
Click to expand...
Click to collapse
You can join the v60 telegram group. There are a lot of guys there to support and also notes there to guide you
Amosika said:
The only option you have is to make a full backup of all your partition dumps using qfil in edl mode. Check how to do that. If you don't and something happens, you're doomed. Before cross flash, make sure to backup all your dumps first and keep them safe before you try anything just in case something happens or you want to go back to original Att firmware then you restore them
Click to expand...
Click to collapse
If you make a backup copy of the AT&T firmware,I would advise doing it as a LUNS backup with Fh_loader.This will ensure you get a valid,and known working copy.
stormeye25 said:
My amazon refurbished v60 AT&T unlocked is on the way. I will use mint which is t-mobile. Do you have any idea if I will get a12?
Click to expand...
Click to collapse
Don't be surprised if it's a U.S. Cellular V60 coming from Amazon.I have ordered 2 of them that state they're AT&T models unlocked,but they're old stock from that carrier.If they are,you won't even have to crossflash it.Leave it as it is,and it will OTA update with any sim card in it.
Surgemanxx said:
Don't be surprised if it's a U.S. Cellular V60 coming from Amazon.I have ordered 2 of them that state they're AT&T models unlocked,but they're old stock from that carrier.If they are,you won't even have to crossflash it.Leave it as it is,and it will OTA update with any sim card in it.
Click to expand...
Click to collapse
I just got it 1 hour ago and it is exactly as you described. V600tm U.S. Cellular. Thank you!
stormeye25 said:
I just got it 1 hour ago and it is exactly as you described. V600tm U.S. Cellular. Thank you!
Click to expand...
Click to collapse
It's probably one I have returned to them because it wasn't from AT&T originally..lol..I have the same one,but have it crossflashed with AT&T firmware...lol
Surgemanxx said:
It's probably one I have returned to them because it wasn't from AT&T originally..lol..I have the same one,but have it crossflashed with AT&T firmware...lol
Click to expand...
Click to collapse
Haha. How can we check if it's one you've returned? Also, why did you want to crossflash with AT&T?
stormeye25 said:
Haha. How can we check if it's one you've returned? Also, why did you want to crossflash with AT&T?
Click to expand...
Click to collapse
I didn't save the IMEI's from them or we would have known for sure..lol..I do know the plastic that goes around them was already off,and someone just wrapped it back around it with the 2 I got from them.I have AT&T service,and without the original firmware it won't provision properly for VoLTE.Data,and text works no problem.With that in mind,keep it on T-Mobile or Mint.Even being unlocked,it will never have voice on AT&T.
Related
Stock Partitions + KDZ for the T-Mobile G6. Anti-rollback v00.
The boot.img should allow you to get TWRP working now.
And I believe this is the first proper G6 system dump (not a system pull from an unrooted device that has files missing) so it should help get LineageOS etc going as well.
I don't have a G6 so I won't be making stock roms or contributing to actual G6 development.
Enjoy.
DOWNLOAD @ CODEFIRE LG G6 H872 10E DIRECTORY
You are the Man! Thanks for zipping the System! Downloading right now...
EDIT: Compared the System with the G5 System. The G6 is a bad Joke (Software and Hardware) no real upgrade to the G5 besides the Display. Compare by Yourself and You will see... Most of the new Features are Framework and UI related. But even there are no big Changes at all compared to the G5 or the V20. I'm done with LG. Sony, Xiaomi, OnePlus, ZTE. There are so many nice Flagships coming, including the latest Snapdragon 835. I can wait for them using My G5 and knowing that it is still as good as the G6...
Thanks again autoprime for sharing all the Images with us. The LG Forums would be nothing without You!
@autoprime thank you so much. I'd like to start testing. Do you know how to flash these ? Just fasboot or do I need a special lg tool?
matteosaeed said:
@autoprime thank you so much. I'd like to start testing. Do you know how to flash these ? Just fasboot or do I need a special lg tool?
Click to expand...
Click to collapse
not sure how fastboot will handle it.. I dont have the phone and there are lots of possible variables. For example some partitions may be allowed to use fastboot flash.. while others may not.
LGUP should hopefully work. Not sure if UPPERCUT works with the G6 as is.. haven't received any feedback from G6 users. So someone will need to test that.
autoprime said:
not sure how fastboot will handle it.. I dont have the phone and there are lots of possible variables. For example some partitions may be allowed to use fastboot flash.. while others may not.
LGUP should hopefully work. Not sure if UPPERCUT works with the G6 as is.. haven't received any feedback from G6 users. So someone will need to test that.
Click to expand...
Click to collapse
I can give testing a shot except i am a potato head over here.
autoprime said:
not sure how fastboot will handle it.. I dont have the phone and there are lots of possible variables. For example some partitions may be allowed to use fastboot flash.. while others may not.
LGUP should hopefully work. Not sure if UPPERCUT works with the G6 as is.. haven't received any feedback from G6 users. So someone will need to test that.
Click to expand...
Click to collapse
I will test this method out tonight. LGUP may be a huge step forward if we can send unsigned recovery images through it. There are no useful fastboot commands other than oem unlock. fastboot flash/boot both give an error about an unknown command, and the aboot file confirms this.
Hopefully I can come back with good news tonight. No work tomorrow so I shall be picking up multiple energy drinks and going at it.
Flippy125 said:
I will test this method out tonight. LGUP may be a huge step forward if we can send unsigned recovery images through it. There are no useful fastboot commands other than oem unlock. fastboot flash/boot both give an error about an unknown command, and the aboot file confirms this.
Hopefully I can come back with good news tonight. No work tomorrow so I shall be picking up multiple energy drinks and going at it.
Click to expand...
Click to collapse
any luck?
matteosaeed said:
any luck?
Click to expand...
Click to collapse
Literally just got home and on my computer. Downloading everything now. Will keep you guys updated
Flippy125 said:
Literally just got home and on my computer. Downloading everything now. Will keep you guys updated
Click to expand...
Click to collapse
Alright, hopefully we can get this to work, going to pick up a g6 soon
I am able to get the G6 detected in LGUP using the dll extracted from the kdz file. It oddly only pops up when sitting at the secure bootup passcode prompt. The phone does not show up as a COM port in the bootloader. I have not tried to flash anything yet
EDIT: loljk just needed to power off > hold vol+ > attach usb cable to enter download mode wooooo
I shall be updating with progress HERE as to not hijack this thread
{
"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"
}
Autoprime,
Nice to see you here! By any chance are you able to get the KDZ for the Korean model? I have the G600S. Or of there is anyway I can help.
Thanks!
Sent from my ONEPLUS A3000 using Tapatalk
hope to get a kdz for at&t as well.
Any chance of the us cellular version becoming rootable?
autoprime said:
....
I don't have a G6 so I won't be making stock roms or contributing to actual G6 development.
Enjoy.
DOWNLOAD @ CODEFIRE LG G6 H872 10E DIRECTORY
Click to expand...
Click to collapse
What would it take for you to develop for the device? Do we need to crowdsource you the funds to purchase the device???? ??
reignlight said:
What would it take for you to develop for the device? Do we need to crowdsource you the funds to purchase the device???? ?
Click to expand...
Click to collapse
I put a stock rom thread together for the new tmo g6 10h update: https://forum.xda-developers.com/tmobile-g6/development/stock-h720-10h-rom-imgs-kdz-t3607236
TWRP is still needed before the zips are useful.. but it's there all ready to use.
Won't be doing them for every release but we'll see how it goes.
Would love a G6 but not looking for donations or anything. But I am looking for people that might have access to..
extra G6 boards...
or broken G6..
or bad esn/imei G6..
or bricked G6.. etc?
Something that might be a bit cheaper than getting a brand new g6 since it wont ever leave my desk.. it'd be a dedicated developing/testing device.
autoprime said:
I put a stock rom thread together for the new tmo g6 10h update: https://forum.xda-developers.com/tmobile-g6/development/stock-h720-10h-rom-imgs-kdz-t3607236
TWRP is still needed before the zips are useful.. but it's there all ready to use.
Won't be doing them for every release but we'll see how it goes.
Would love a G6 but not looking for donations or anything. But I am looking for people that might have access to..
extra G6 boards...
or broken G6..
or bad esn/imei G6..
or bricked G6.. etc?
Something that might be a bit cheaper than getting a brand new g6 since it wont ever leave my desk.. it'd be a dedicated developing/testing device.
Click to expand...
Click to collapse
Thank you thank you !! Prices are dropping really quickly , wait till someone puts it on facebook market , I wouldn't trust swappa
autoprime said:
Stock Partitions + KDZ for the T-Mobile G6. Anti-rollback v00.
The boot.img should allow you to get TWRP working now.
And I believe this is the first proper G6 system dump (not a system pull from an unrooted device that has files missing) so it should help get LineageOS etc going as well.
I don't have a G6 so I won't be making stock roms or contributing to actual G6 development.
Enjoy.
DOWNLOAD @ CODEFIRE LG G6 H872 10E DIRECTORY
Click to expand...
Click to collapse
Damn I had hope that I will find the cust partition in this dump but no luck:crying:
It will be nice if someone can actually share that partition for a huge project.
(For those who don't know, G973U is the model number of all of the US carrier versions of the Galaxy S10. The G973U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among any of those models.)
The large files will be your 4 part firmware and then grab your desired USERDATA as well. I'll continue to add more versions and more USERDATAs over time.
Happy flashing!
U firmware: https://www.androidfilehost.com/?w=files&flid=290645
U1 firmware: https://www.androidfilehost.com/?w=files&flid=290646
Notes:
- I compress extra small for space and bandwith savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- I remove the .md5 from each file solely for faster flashing (Odin won't check the file integrity without it). Rest assured, the files are perfectly fine and safe - Odin has a million safechecks built in.
- My naming method for Android File Host folders is: build - bootloader - Android version.
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Any zips with "wipe" in the title do not have a HOME CSC included.
- SamFirm still works, if you want to download them yourself. I pay for a subscription to a site that gets beta builds and also gets the official releases before they hit SamFirm, so that's where my files come from
- I have identical threads for the S10e and S10+ as well
- Post #173 has the correct procedure for changing from one U firmware to a different U firmware, with proper bloat and carrier features, etc.
- You can get USERDATAs from SamFirm for everything but AT&T and Cricket- those files will never be on SamFirm. So in addition to the 5 piece firmware, I'll try to always upload one USERDATA per bootloader increment for those carriers.
- For USERDATAS (all the others are self explanatory):
AIO = Cricket
CCT = Xfinity Mobile (Comcast)
CHA - Spectrum Mobile (Charter)
TMK = Metro PCS
The SM-G973U is the model number for the Samsung Galaxy S10. SM-G970U is the model number for the Galaxy S10e.
Drakoid said:
The SM-G973U is the model number for the Samsung Galaxy S10. SM-G970U is the model number for the Galaxy S10e.
Click to expand...
Click to collapse
Ughhh stupid new nomenclature. Thanks for catching that - gonna take some brain re-training to keep these all straight now haha
Build SBA added.
SPR is the only USERDATA for this build so far - not sure if it will stay a Sprint-exclusive release, or be more widely pushed out. But like with any other build, it can be flashed to any S10, regardless of which carrier it originally came from.
EDIT: Xfinity and Verizon USERDATAs added
G973U and G973U1 firmware is now live and downloadable in SamFirm. Getting U1 (at least for now) requires manual entry - Auto will not work. U firmware is up for these carriers:
Xfinity Mobile
Spectrum Mobile
Sprint
T-Mobile
US Cellular
Verizon (have to use Manual entry - Auto will not work)
So going forward, I'll only be adding full builds if I can get them before they hit SamFirm, and only if there isn't build for that month already (eg. I won't add any more February builds since SBA is already up.). I will try to stay up to date on USERDATAs for AT&T and Cricket, since AT&T won't let their firmware be put on SamFirm.
Will this work to remove the Verizon branding from my s10? I ask that as I purchased outright from Samsung and am running G973USQU1ASBA.
It appears when my phone activated with the Verizon SIM, it added their profile and I would prefer it to be unlocked as purchased so I can get features like smart call back. Thanks in advance.
iOSNick said:
Will this work to remove the Verizon branding from my s10?
Click to expand...
Click to collapse
Yep!
iBowToAndroid said:
Yep!
Click to expand...
Click to collapse
Awesome, thanks for the verification. As for the 5th file to flash 'userdata', would I opt to not do this for Verizon and just flash the first four files to go back to unlocked status?
iOSNick said:
Awesome, thanks for the verification. As for the 5th file to flash 'userdata', would I opt to not do this for Verizon and just flash the first four files to go back to unlocked status?
Click to expand...
Click to collapse
There is no USERDATA in U1 firmware
Ok, that clears it up, userdata is just for the U firmware. Is there something I should do to avoid Verizon from installing their profile? I am currently running the U1 firmware, but somehow have Verizon's branding attached to the phone, presumably from the SIM setup.
Or is there any way to just remove the Verizon branding while retaining the U1 firmware I'm on currently?
iOSNick said:
Ok, that clears it up, userdata is just for the U firmware. Is there something I should do to avoid Verizon from installing their profile? I am currently running the U1 firmware, but somehow have Verizon's branding attached to the phone, presumably from the SIM setup.
Or is there any way to just remove the Verizon branding while retaining the U1 firmware I'm on currently?
Click to expand...
Click to collapse
I define "branding" by a startup/shutdown logo, plus carrier apps installed. U1 firmware doesn't have any of that
iBowToAndroid said:
I define "branding" by a startup/shutdown logo, plus carrier apps installed. U1 firmware doesn't have any of that
Click to expand...
Click to collapse
Agreed, same thing I am referring to. My phone has the Verizon splash page on boot up/shut down and the My Verizon folder with their specific apps in the app drawer. Weird thing is, I am actually running the U1 software straight from my Samsung.com order.
I'm currently downloading the U1from this thread to flash to the phone in an effort to remove the Verizon bloatware, was just was curious if there was another way to remove Verizon without re-flashing U1. Appreciate your help with this and setting up these download links as well!
{
"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"
}
Sent from my SM-G973U using Tapatalk
iOSNick said:
Agreed, same thing I am referring to. My phone has the Verizon splash page on boot up/shut down and the My Verizon folder with their specific apps in the app drawer. Weird thing is, I am actually running the U1 software straight from my Samsung.com order.
I'm currently downloading the U1from this thread to flash to the phone in an effort to remove the Verizon bloatware, was just was curious if there was another way to remove Verizon without re-flashing U1. Appreciate your help with this and setting up these download links as well! View attachment 4721638
Sent from my SM-G973U using Tapatalk
Click to expand...
Click to collapse
It's impossible to have carrier bloat if you're running U1, and it's impossible to be running U1 if you have carrier bloat. You're not running U1. You're running U. Look at the picture you posted. You didn't order a Samsung unlocked model, you ordered a Verizon variant.
Flashing U1 is the only way to remove bloat.
Built-in Visual Voicemail 973U T-Mobile Not Working
Thanks for the links!
I flashed my U1 S10 over to U with TMo Userdata. I have the TMo pink splash screen and bloat installed, as well as the better reception gained from adding their firmware, but the Visual Voicemail that could be accessed by tapping the 3 dot menu in dialer, then selecting Visual Voicemail, is gone. The only option that shows is the regular voicemail. It worked perfectly on my Note 9 with the Pie Beta firmware, and I had switched it from U1 to U as well.
Does anyone have any idea what I might be doing wrong, or how to get stock VVM back? I've read that it's carrier dependent and all of that, but the conditions on my S10 are the same they were on my Note 9 from everything I can see, yet I don't have stock VVM. I am wondering if this might be something where TMo is just behind in adding support for the S10 to work with the stock VVM, but I have no clue how all that stuff works on the carrier side of things.
Any help with this would be greatly appreciated, so I can remove the vomit-spewed (just in appearance IMO) app that is TMo's Visual Voicemail app. I tend to obsess over things like this and it's driving me crazy. Lol, I know, it's nitpicky, but I shelled out almost $2K for mine and my wife's phones, so I just want it to work.
I have the Verizon 'u' software. If I flash the attached G973U1_SAU_1 firmware, will my phone be unlocked of carrier bloatware? Verizon blocks SMART callerID unless someone knows an alternative.
That's the only reason I would move because I use Package Disabler to hide the bloat.
brian5259 said:
I have the Verizon 'u' software. If I flash the attached G973U1_SAU_1 firmware, will my phone be unlocked of carrier bloatware?
Click to expand...
Click to collapse
The answer is found in the 2nd sentence of the OP
brian5259 said:
I have the Verizon 'u' software. If I flash the attached G973U1_SAU_1 firmware, will my phone be unlocked of carrier bloatware? Verizon blocks SMART callerID unless someone knows an alternative.
That's the only reason I would move because I use Package Disabler to hide the bloat.
Click to expand...
Click to collapse
Technically, yes. The smart caller id function will be available after flashing the unlocked firmware, however it appears there is still some control, as the setting will keep toggling itself off. Since flashing, my caller id will stay enabled for about 48 hours max, then be automatically toggled off. Others are reporting the same thing, so something is still preventing it from staying enabled all the time. Quite annoying, as there is no way to tell when it is toggled off, aside from seeing a call without it or constantly checking settings.
Sent from my SM-G973U1 using Tapatalk
So I have the G973U1 phone, and want to flash the Verizon software for video calling, etc.
A few questions...
Am I correct that I down/flash the G973U firmware.
Do I really need the USERDATA package? What happens if I skip it?
When all is done will my phone show VZW/VZW/VZW or will it show VZW/VZW/XAA?
What is the impact if it stays XAA as opposed to VZW, or... do I want it to show VZW/VZW/VZW?
how do I change it to VZW/VZW/VZW (there was a thread I followed for my GS8, but starting with the GS9/Note9 it appears its either not needed, or not done the same way? or I just can't find the instructions)
Thanks!
Same Here! Anybody know?
KidJoe said:
So I have the G973U1 phone, and want to flash the Verizon software for video calling, etc.
A few questions...
Am I correct that I down/flash the G973U firmware.
Do I really need the USERDATA package? What happens if I skip it?
When all is done will my phone show VZW/VZW/VZW or will it show VZW/VZW/XAA?
What is the impact if it stays XAA as opposed to VZW, or... do I want it to show VZW/VZW/VZW?
how do I change it to VZW/VZW/VZW (there was a thread I followed for my GS8, but starting with the GS9/Note9 it appears its either not needed, or not done the same way? or I just can't find the instructions)
Thanks!
Click to expand...
Click to collapse
Same here!
i have chinese model G9730ZCU1ABA do you think firmware on this thread first link is compatible? just in case
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 using Lgup put my foot in it with complete wipe and flashing a kdz and now lost the imei number and whatnot can someone help.......please
You didn't lose your IMEI just by flashing a KDZ using the recommended Upgrade, Partition DL or Refurbish methods. You must have flashed using some mode NOT recommended in any of the Instructions. We specifically say to NOT mess with any modes not mentioned.
In all my Dev Patched LGUP instructions, I include this:
ChazzMatt said:
{
"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"
}
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
Click to expand...
Click to collapse
ChazzMatt said:
You didn't lose your IMEI just by flashing a KDZ using the recommended Upgrade, Partition DL or Refurbish methods. You must have flashed using some mode NOT recommended in any of the Instructions. We specifically say to NOT mess with any modes not mentioned.
In all my Dev Patched LGUP instructions, I include this:
Click to expand...
Click to collapse
If I didn't do it the way I did wouldn't get update......
stinka318 said:
If I didn't do it the way I did wouldn't get update......
Click to expand...
Click to collapse
Why do you claim that?
You simply flash KDZ via Refurbish or Partition DL with Dev Patched LGUP and your phone is updated.
Most times you can even flash KDZ via Upgrade mode and keep data.
In ALL the KDZ threads we have, where users update their phones all the time, we only use Upgrade, Refurbish, or Partition DL modes.
What variant do you have?
ChazzMatt said:
Why do you claim that?
You simply flash KDZ via Refurbish or Partition DL with Dev Patched LGUP and your phone is updated.
Most times you can even flash KDZ via Upgrade mode and keep data.
In ALL the KDZ threads we have, where users update their phones all the time, we only use Upgrade, Refurbish, or Partition DL modes.
What variant do you have?
Click to expand...
Click to collapse
The fact the update is out there and tried LG bridge and tried a few other ways to push the update to no success........it is a v30 us998 being used in Australia is probably the reason.
I'm using the device right now so it is only a cosmetic thing at the moment.
stinka318 said:
The fact the update is out there and tried LG bridge and tried a few other ways to push the update to no success........it is a v30 us998 being used in Australia is probably the reason.
Click to expand...
Click to collapse
Follow the instructions in the US998 KDZ thread. We post all the KDZ images there, with several mirrors for each KDZ release.
You simply download the KDZ, flash via Upgrade mode with the Dev Patched LGUP -- which is also provided in the first post. At the most use Refurbish mode.
There's plenty of Instructions in the KDZ thread and how to use Dev Patched LGUP.
See Post#1.
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
ChazzMatt said:
Follow the instructions in the US998 KDZ thread. We post all the KDZ images there, with several mirrors for each KDZ release.
You simply download the KDZ, flash via Upgrade mode with the Dev Patched LGUP -- which is also provided in the first post. At the most use Refurbish mode.
There's plenty of Instructions in the KDZ thread and how to use Dev Patched LGUP.
See Post#1.
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99820a040330-kdz-t3786337
Click to expand...
Click to collapse
Download was not the problem it was the fact that it didn't want to update with refurbish or upgrade parts
Despite it being recognized by LGup.........
stinka318 said:
Download was not the problem it was the fact that it didn't want to update with refurbish or upgrade parts
Despite it being recognized by LGup.........
Click to expand...
Click to collapse
What LGUP were you using?
ChazzMatt said:
What LGUP were you using?
Click to expand...
Click to collapse
Tried a few different ones until i tried store version 1.14 it was a China man that i got it off so it may have been unlocked by a third-party in china.....
stinka318 said:
Tried a few different ones until i tried store version 1.14 it was a China man that i got it off so it may have been unlocked by a third-party in china.....
Click to expand...
Click to collapse
The Dev Patched LGUP in that US998 KDZ thread works for everyone around the world -- unless the seller did something to that USS98 with Octoplus box which Matt may prevent that Dev Patched LGUP from working right.
I saw that one time before with AS998, where Dev Patched LGUP couldn't do anything because dealer had messed it up with Octopus/Octoplus box when converting it from LS998.
ChazzMatt said:
The Dev Patched LGUP in that US998 KDZ thread works for everyone around the world -- unless the seller did something to that USS98 with Octoplus box which Matt may prevent that Dev Patched LGUP from working right.
I saw that one time before with AS998, where Dev Patched LGUP couldn't do anything because dealer had messed it up with Octopus/Octoplus box when converting it from LS998.
Click to expand...
Click to collapse
I have the box with the imei number on it......it is i reckon it is because someone didn't want to pay to get it unlocked by us cellular so they paid a third party to do it it has happened b4 to me......
Using dual mode LG UP in OP of US998 kdz thread and directions from post #6 on "how to get past stuck v30 logo", go back to freshly kdz 20h, H933 Nougat to get imei and partitions back, then 20e, then 20h, and lastly pie 30b
stinka318 said:
I have the box with the imei number on it......it is i reckon it is because someone didn't want to pay to get it unlocked by us cellular so they paid a third party to do it it has happened b4 to me......
Click to expand...
Click to collapse
All US998 are already carrier unlocked. Even U.S. Cellular.
If you're trying to update to Pie it's a different KDZ thread. I assumed you were trying to update to latest US998 Oreo since to you said it wouldn't update...
[US998][STOCK][PIE]LG V30 US998 US99830b_00_0902.KDZ
https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
ChazzMatt said:
All US998 are already carrier unlocked. Even U.S. Cellular.
Click to expand...
Click to collapse
Well that thows out that theory out the window.....
I just want to know if there is a fix for this problem.
ChazzMatt said:
All US998 are already carrier unlocked. Even U.S. Cellular.
If you're trying to update to Pie it's a different KDZ thread. I assumed you were trying to update to latest US998 Oreo since to you said it wouldn't update...
Click to expand...
Click to collapse
It was running oreo when i got the phone i was trying to get pie that was a success but it cost the imei number and being somewhat dyslexic and parsuly color blind didn't see the warning about the fact I'd lose imei number if i knew I'd probably stick with oreo.
stinka318 said:
It was running oreo when i got the phone i was trying to get pie that was a success but it cost the imei number and being somewhat dyslexic and parsuly color blind didn't see the warning about the fact I'd lose imei number if i knew I'd probably stick with oreo.
Click to expand...
Click to collapse
Luckily you still have box with IMEI, etc.
You'll have to Google for tools to repair your IMEI. You know what it is, you will just need to type it in.
It's a touchy subject on XDA we can't really discuss in depth because some people for nefarious reason want to CHANGE their IMEI and XDA frowns on that.
ChazzMatt said:
Luckily you still have box with IMEI, etc.
You'll have to Google for tools to repair your IMEI. You know what it is, you will just need to type it in.
It's a touchy subject on XDA we can't really discuss in depth because some people for nefarious reason want to CHANGE their IMEI and XDA frowns on that.
Click to expand...
Click to collapse
Yep so i think I'll will leave it alone got what i need now hopefully i can figure it out......thanks anyway.
ChazzMatt said:
Luckily you still have box with IMEI, etc.
You'll have to Google for tools to repair your IMEI. You know what it is, you will just need to type it in.
It's a touchy subject on XDA we can't really discuss in depth because some people for nefarious reason want to CHANGE their IMEI and XDA frowns on that.
Click to expand...
Click to collapse
Just got it fixed now have it back fully it has something to do with hidden menu.......lol
Hi all,
First some details:
LG930DS
secure startup enabled
H930DS30s_00_OPEN_HK_DS_OP_0902.kdz installed via LG Bridge. It changed me from AU to HKG for reasons unknown to me.
rooted with TWRP and Magisk 20.1 installed
I'm having issues with VoLTE not working (actually no longer in settings of the hidden menu) since installing Pie and I want to rule out the HKG variant as the cause. To do this I will install H930DS30c_00_OPEN_AU_DS_OP_0902.kdz instead. I have downloaded this kdz but now I'm not sure if I can install it without having to wipe and re-do all the Magisk and TWRP (and setting up all my files and apps again). After reading the guides none seem to answer this question quite right as they are mostly aimed and either US, EU, or India with their TWRP flashable roms like this one https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
Can someone with a better idea of how this works let me know the best option for me to switch over to the AU variant.
Wibble Wobble said:
Hi all,
First some details:
LG930DS
secure startup enabled
H930DS30s_00_OPEN_HK_DS_OP_0902.kdz installed via LG Bridge.
It changed me from AU to HKG for reasons unknown to me.
Click to expand...
Click to collapse
LG Bridge will look for the KDZ intended for your IMEI, not the firmware you have on the phone right now. Was your phone imported from Hong Kong (China)? Or did you buy from Australian carrier or Australia LG authorized retailer? Did you buy the phone new or used? Have you updated it before using LG Bridge?
Any H930DS can be flashed to run any other H930DS firmware. Best guess is somehow the phone was originally Hong Kong variant and someone flashed it to Australian firmware. When you went to look for update via LG Bridge, then it updated to that region Pie meant for that IMEI.
Unless you have used LG Bridge successfully before and you are sure it is Australian IMEI H930DS?
Wibble Wobble said:
rooted with TWRP and Magisk 20.1 installed
I'm having issues with VoLTE not working (actually no longer in settings of the hidden menu) since installing Pie and I want to rule out the HKG variant as the cause. To do this I will install H930DS30c_00_OPEN_AU_DS_OP_0902.kdz instead. I have downloaded this kdz but now I'm not sure if I can install it without having to wipe and re-do all the Magisk and TWRP (and setting up all my files and apps again). After reading the guides none seem to answer this question quite right as they are mostly aimed and either US, EU, or India with their TWRP flashable roms like this one https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
Can someone with a better idea of how this works let me know the best option for me to switch over to the AU variant.
Click to expand...
Click to collapse
We haven't always had TWRP-flashable zips. Only thanks to generous, talented devs do we have the collection of TWRP flashable zips for US998, H931, H933, VS996, LS998, T-mobile H932, H930, India H930DS. That's only 8 of at least 20 variants and I'm not even counting all the different regional variants of H930DS...
So you will have to do what we all did before TWRP-flashable zips, and what we will have to do again when some of our TWRP flashable zip devs move onto other phones.
Method #1 -- Works some of the time on Oreo, not yet tried on Pie
This worked for many people in Oreo -- but some still had to reinstall TWRP, reformat data, reinstall the root files. Never could figure out the difference between success and not. Then we got TWRP-flashable zips and the issue became moot.
1) Make backup in TWRP AND make backup of all apps in Titanium Backup.
2) Flash new KDZ via Pie-compatible Dev Patched LGUP in Partition DL mode, but omit the Recovery partitions. Do NOT select "all partitions". This will let you keep TWRP.
3) Boot into TWRP via fastboot commands from your computer, just like when you first installed TWRP using the WTF instructions. (Best not to use the stupid hardware button dance.) Once in TWRP, then choose Reboot to Recovery (from within TWRP) to get the actual internal phone TWRP, instead of the PC TWRP.
4) Flash the Pie-compatible three root files (Magisk, encryption disabler, root check disabler, Magisk again). See attachments on this post to download those files.
5) Restore all Data from within TWRP. Do not choose any other categories.
6) Wipe all Caches.
7) Reboot
Restoring all TWRP data may or may not overcome the fact that you have re-flashed encrypted stock Pie on your phone. IF it does work, then after rebooting the phone if anything is still wonky, use Titanium Backup to restore all apps and data (this is in addition to the TWRP data restore you did).
Good luck.
Method #2 -- Works all the time, but yeah you have set up your phone again
1) Flash new KDZ via Pie-compatible Dev Patched LGUP in REFURBISH mode.
2) Your phone is now on the region KDZ you desire and you still have unlocked bootloader. You will need to reinstall TWRP, and then flash the three root files (Magisk, encryption disabler, root check disabler, Magisk again). This includes the step where you reformat all data with a "YES".
See instructions here:
REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
THAT POST ASSUMES YOU HAVE PREVIOUSLY UNLOCKED BOOTLOADER, AND THAT YOU HAVE NOW UPGRADED TO STOCK PIE KDZ. YOU HAVE UNLOCKED BOOTLOADER and are STILL on firmware which has FASTBOOT FLASH COMMANDS.
___________
Dev Patched LGUP
Dev Patched LGUP vs regular LGUP is necessary when cross flashing across regions or other variants. You will need this for either of the two methods above.
Here's how to flash with LGUP:
UPGRADING LG V30/V30+/V30S TO PIE KDZ FIRMWARE WITH LGUP
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open Dev Patched LGUP and flash PIE KDZ either via PARTITION DL MODE (but omit Recovery Partitions for your purpose in this thread) for Method #1 or via REFURBISH for Method #2.
Use the attached patched LGUP in this post. If you get a ".dll error" you either didn't install correctly or are using the wrong version of Dev Patched LGUP. Read the installation instructions carefully. Some people have used OTHER versions of LGUP before and ignore the installation instructions -- they think they know how to install and they do NOT --- then complain about .dll error, which is their fault.
* NOTE: YOU CAN NOT USE LGUP "UPGRADE" MODE IF YOU HAVE TWRP CUSTOM RECOVERY. LGUP "Upgrade" is like a manual OTA and is only for pure stock (but you can have unlocked bootloader).
3) IF your bootloader is unlocked, it will remain unlocked after flashing KDZ.
_________________
HOW TO INSTALL DEV PATCHED LGUP
0. UNINSTALL any prior LGUP version. Seriously. Go to Programs folder and delete the LGUP folder if you must.
1. DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. < READ THAT AGAIN.
5. Launch LGUP using the desktop shortcut. NOT from folder icon!
{
"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"
}
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
I don't care what anyone else tells you. If you listen to them, let them help you recover from messing up your phone.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
ChazzMatt said:
LG Bridge will look for the KDZ intended for your IMEI, not the firmware you have on the phone right now. Was your phone imported from Hong Kong (China)? Or did you buy from Australian carrier or Australia LG authorized retailer? Did you buy the phone new or used? Have you updated it before using LG Bridge?
Any H930DS can be flashed to run any other H930DS firmware. Best guess is somehow the phone was originally Hong Kong variant and someone flashed it to Australian firmware. When you went to look for update via LG Bridge, then it updated to that region Pie meant for that IMEI.
Unless you have used LG Bridge successfully before and you are sure it is Australian IMEI H930DS?
Click to expand...
Click to collapse
Ahh thank you for explaining this. I imported mine from Hong Kong. As far as I know it was never sold new in AU.
I'm about to rush off to work for the day so I will have to try this when I get home tonight and let you know how it goes. Thank you so much for the detailed and fast response! This is much more than I was hoping for!
One last question. Do I need to disable secure startup or does the encryption work with the method #1?
Wibble Wobble said:
One last question. Do I need to disable secure startup or does the encryption work with the method #1?
Click to expand...
Click to collapse
Yes, I would do that.
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Wibble Wobble said:
As far as I know it was never sold new in AU.
Click to expand...
Click to collapse
I don't know the Australian market, but we have an Australian XDA moderator who has or had Australia H930DS. Since there is Australia H930DS firmware, I assume it was sold new back in 2017/2018 by some carrier or by LG authorized retailer.
He has Vodafone in his profile. @Redline.
ChazzMatt said:
I don't know the Australian market, but we have an Australian XDA moderator who has or had Australia H930DS. Since there is Australia H930DS firmware, I assume it was sold new back in 2017/2018 by some carrier or by LG authorized retailer.
He has Vodafone in his profile. @Redline.
Click to expand...
Click to collapse
This is correct. I bought one BNIB from an eBay seller, a H930DS and it was only a couple weeks old from the factory. Came pre-loaded with AU firmware and I updated it to the latest. Before going the LineageOS route.
Redline said:
This is correct. I bought one BNIB from an eBay seller, a H930DS and it was only a couple weeks old from the factory. Came pre-loaded with AU firmware and I updated it to the latest. Before going the LineageOS route.
Click to expand...
Click to collapse
Interesting to know. I bought mine back in 2017 but I couldn't find it in AU and read somewhere that imports were going to be the only option. To bad for me.
I know little of what IMEI's do. Is there any issues related to regional OS versions and the IMEI of a device? Is the hardware otherwise the same?
Wibble Wobble said:
Interesting to know. I bought mine back in 2017 but I couldn't find it in AU and read somewhere that imports were going to be the only option. To bad for me.
I know little of what IMEI's do. Is there any issues related to regional OS versions and the IMEI of a device? Is the hardware otherwise the same?
Click to expand...
Click to collapse
I could kind of answer is the question of if the hardware is otherwise the same, the rest might be a question for ChazzMatt.
AFAIK the modem on my H930DS was the same as other similar models, similar to the V20 you can flash a KDZ from another region if you wanted to (to for example, get less bloat or better coverage on a band you rely on for service). I remember on my V20 the region that had Claro-carrier firmware came with the least bloat out of the box vs other regions, but we also had KDZ Writer with the V20 that allowed us to flash specific parts of the KDZ *in* TWRP on the device itself, so you could have, say, Claro firmware with the AU modem.
As for what IMEIs do, they're similar to the MAC address on a piece of networking gear; it's a globally-unique identifier specific to your device, you can put it into IMEI lookup websites to get information about manufacture date, model etc.
If you have a carrier-model phone, they can also block your IMEI on their network if it is stolen and then attempted to be re-used.
I've had to opt with #2 as the encryption was a problem as you suspected. I'm puzzled though... while I was setting up for USB debugging I noticed that I had VoLTE in the drop down menu, however, calls still reverted back to 3G. I didn't pay much attention to it as I had to do a format in the steps to follow. Now that I'm back up and running I no longer have VoLTE in the drop down menu? It's the only icon missing. Calls still revert to 3G again. I'm on the boost network which uses Telstra and this phone is listed as compatible for VoLTE with them. I know that it worked in Oreo too.
Wibble Wobble said:
I've had to opt with #2 as the encryption was a problem as you suspected. I'm puzzled though... while I was setting up for USB debugging I noticed that I had VoLTE in the drop down menu, however, calls still reverted back to 3G. I didn't pay much attention to it as I had to do a format in the steps to follow. Now that I'm back up and running I no longer have VoLTE in the drop down menu? It's the only icon missing. Calls still revert to 3G again. I'm on the boost network which uses Telstra and this phone is listed as compatible for VoLTE with them. I know that it worked in Oreo too.
Click to expand...
Click to collapse
Hmmm.... Sorry, I don't know. But you are back on Australian firmware.
If you wish, you can use the same procedure to downgrade back to Australian Oreo to see if you can get VoLTE back.
H930DS20f_00_OPEN_AU_DS_OP_0408.kdz
https://lg-firmwares.com/downloads-file/19586/H930DS20f_00_OPEN_AU_DS_OP_0408
ChazzMatt said:
Hmmm.... Sorry, I don't know. But you are back on Australian firmware.
If you wish, you can use the same procedure to downgrade back to Australian Oreo to see if you can get VoLTE back.
H930DS20f_00_OPEN_AU_DS_OP_0408.kdz
https://lg-firmwares.com/downloads-file/19586/H930DS20f_00_OPEN_AU_DS_OP_0408
Click to expand...
Click to collapse
Out of frustration I started doing random things just to test there effect, much of it being in the hidden menu where I discovered VoLTE settings. Nothing was working until... I force stopped the carrier service and made a phone call. Presto! VoLTE now appears (though not listed under any setting in mobile networks, or in the drop down menu) and my calls say HD call. Finally to confirm 4G remains active and still works during a call!