Any chance someone with an H931 can use LGUP to do a firmware dump? I'm specifically interested in the modem and system partitions (for unlocking band 30 and maybe enabling AT&T WiFi calling), but it might also be possible to do a full flash to the H931 from a bootloader unlocked US998 (depending on firmware signatures).
I'm still on Nougat, but Oreo will probably also work (and I'll eventually want Oreo anyways), so either would be awesome.
To dump the firmware, use the LGUP from this thread (https://forum.xda-developers.com/showthread.php?t=3738917), and use the patched DLL and EXE from this thread (https://forum.xda-developers.com/showpost.php?p=75272845&postcount=23 and use LGUP+V30DLL_PATCHED.zip), and just use the DUMP function. Definitely skip userdata though (I don't want your data, and it's encrypted anyways).
Thanks!
Anybody have an AT&T H931 and can help me out?
Cross flashing the modem to get band 30 seems like a definite possibility, so I'd really appreciate it. ?️
gwillmer said:
Any chance someone with an H931 can use LGUP to do a firmware dump? I'm specifically interested in the modem and system partitions (for unlocking band 30 and maybe enabling AT&T WiFi calling), but it might also be possible to do a full flash to the H931 from a bootloader unlocked US998 (depending on firmware signatures).
I'm still on Nougat, but Oreo will probably also work (and I'll eventually want Oreo anyways), so either would be awesome.
To dump the firmware, use the LGUP from this thread (https://forum.xda-developers.com/showthread.php?t=3738917), and use the patched DLL and EXE from this thread (https://forum.xda-developers.com/showpost.php?p=75272845&postcount=23 and use LGUP+V30DLL_PATCHED.zip), and just use the DUMP function. Definitely skip userdata though (I don't want your data, and it's encrypted anyways).
Thanks!
Click to expand...
Click to collapse
I have a H931, do you still need the dump?
banziitox24 said:
I have a H931, do you still need the dump?
Click to expand...
Click to collapse
Yes! Oreo would be awesome if you have it.
gwillmer said:
Yes! Oreo would be awesome if you have it.
Click to expand...
Click to collapse
don't have Oreo, only have 7.1.2, do you think you can help me make these files flashable, either DZ or KDZ. Can't seem to find anything to do that
Nougat is definitely still useful for me, so I'd really appreciate you uploading that. Using the modem might be questionable across versions, but the wifi calling config in /system would be great.
I'm pretty sure only the bootloader-unlocked models (US998/H930) would have any way to flash this kind of partition dump (using dd from recovery), because they aren't the kdz or dz format that LGUP seems expect. I haven't really looked into how to write those file formats either, but I'm not optimistic about my skills there.
However, I was just thinking about one possible upgrade path to Oreo for the H931s that aren't on AT&T's network: if we get the FOTA upgrade file. Looking at my /fota dump, I think it'd be on the cache partition after downloading/before upgrading, and I bet it'd be in the format LGUP wants for the "FOTA UPGRADE" option, meaning it could be used with a stock H931. Are you on AT&T?
gwillmer said:
Nougat is definitely still useful for me, so I'd really appreciate you uploading that. Using the modem might be questionable across versions, but the wifi calling config in /system would be great.
I'm pretty sure only the bootloader-unlocked models (US998/H930) would have any way to flash this kind of partition dump (using dd from recovery), because they aren't the kdz or dz format that LGUP seems expect. I haven't really looked into how to write those file formats either, but I'm not optimistic about my skills there.
However, I was just thinking about one possible upgrade path to Oreo for the H931s that aren't on AT&T's network: if we get the FOTA upgrade file. Looking at my /fota dump, I think it'd be on the cache partition after downloading/before upgrading, and I bet it'd be in the format LGUP wants for the "FOTA UPGRADE" option, meaning it could be used with a stock H931. Are you on AT&T?
Click to expand...
Click to collapse
No I'm not with AT&T I just need these files converted in a way that I could use them to flash into another phone, I'm uploading files now I'll send you a PM when i have them uploaded, also how you plan to flash modem or the files that you need from this dump because that might help me a little
banziitox24 said:
No I'm not with AT&T I just need these files converted in a way that I could use them to flash into another phone, I'm uploading files now I'll send you a PM when i have them uploaded, also how you plan to flash modem or the files that you need from this dump because that might help me a little
Click to expand...
Click to collapse
With the disclaimer that I haven't tested this yet, here's my plan. Before flashing anything, I'm going to open up the modem in a hex editor to check if the secure boot RSA certificate matches the one from mine (it seems the US998, AS998, VS996, and LS998 have the same one, while the H932 does not). If it doesn't, then I can't flash the modem, because then it won't boot.
I should be able to flash /system though, because I have an unlocked bootloader (which disables the signature check). I don't actually want most of AT&T's bloatware though, so I'm going to open the system image in 7zip, and extract what I need.
As far as how I would actually flash, I'm going to use the dd command after booting TWRP (using either adb shell, or TWRP's built in terminal). dd is a tool for doing low level disk and file copying, and it can be really dangerous (I've seen it called "disk destroyer" lol). The command will be something like:
Code:
dd if=/external_sd/modem.img of=/dev/block/platform/soc/1DA4000.UFSHC/by-name/modem
Unfortunately, this has to be done from a custom recovery, because the stock recovery doesn't have a terminal or the dd command, and you won't be able access anything under /dev/block when booted without root. Trying to write an image to a live file system is not a good idea, and even if you could, it would check the signature on boot and have problems.
This PDF explains secure boot, though I think it's a little different for the file system images (like /system).
https://www.qualcomm.com/media/docu...d-image-authentication-technical-overview.pdf
This post by @runningnak3d explains which images are signed (for both regular and bootloader unlocked). https://forum.xda-developers.com/showpost.php?p=76319892&postcount=34
Thanks again!
gwillmer said:
With the disclaimer that I haven't tested this yet, here's my plan. Before flashing anything, I'm going to open up the modem in a hex editor to check if the secure boot RSA certificate matches the one from mine (it seems the US998, AS998, VS996, and LS998 have the same one, while the H932 does not). If it doesn't, then I can't flash the modem, because then it won't boot.
I should be able to flash /system though, because I have an unlocked bootloader (which disables the signature check). I don't actually want most of AT&T's bloatware though, so I'm going to open the system image in 7zip, and extract what I need.
As far as how I would actually flash, I'm going to use the dd command after booting TWRP (using either adb shell, or TWRP's built in terminal). dd is a tool for doing low level disk and file copying, and it can be really dangerous (I've seen it called "disk destroyer" lol). The command will be something like:
Code:
dd if=/external_sd/modem.img of=/dev/block/platform/soc/1DA4000.UFSHC/by-name/modem
Unfortunately, this has to be done from a custom recovery, because the stock recovery doesn't have a terminal or the dd command, and you won't be able access anything under /dev/block when booted without root. Trying to write an image to a live file system is not a good idea, and even if you could, it would check the signature on boot and have problems.
This PDF explains secure boot, though I think it's a little different for the file system images (like /system).
https://www.qualcomm.com/media/docu...d-image-authentication-technical-overview.pdf
This post by @runningnak3d explains which images are signed (for both regular and bootloader unlocked). https://forum.xda-developers.com/showpost.php?p=76319892&postcount=34
Thanks again!
Click to expand...
Click to collapse
Yeah I figured you where either going to zip it and flash it via TWRP or even via Fastboot, here's a link for the dumped ROM.
https://www.mediafire.com/download/zp558y5y5qms3i7
Please don't make mirrors or redistribute my link without my consent.
Thank you
Sent from my SM-N950U using Tapatalk
It will be interesting to see if you can get any of this to work. I'd like to get WiFi calling and band 30 support on my unlocked US998 on AT&T. I recently just updated mine to Oreo. So if anyone can dump Oreo I can try that.
I have Oreo and the H931.
Do you still need this done and if so, will I be taking any risks by doing this?
I meant to report back what happened with Nougat, but life got a little crazy. Using the Nougat modem didn't seem to unlock band 30, but I didn't get to test much further because it also made my fingerprint reader not work (flashing back to my US998 modem fixed it). No issues booting though!
Sulgor84 said:
I have Oreo and the H931.
Do you still need this done and if so, will I be taking any risks by doing this?
Click to expand...
Click to collapse
Yes please! I think the Oreo modem won't cause the same problem with the fingerprint reader, and I'm much more optimistic about getting wifi calling to work using the Oreo system dump. And no, it won't harm your phone (you aren't writing anything to the phone, only reading). Thank you so much!
Sulgor84 said:
I have Oreo and the H931.
Do you still need this done and if so, will I be taking any risks by doing this?
Click to expand...
Click to collapse
Any chance you were able to do this, it would be very useful to have this around given the cross flashing/bootloader unlock. Unfortunately there are no KDZ/TOT's for the ATT variant like there are for other models.
Thanks
Anybody with the H931 and Oreo able to help us out? It'd be very much appreciated!
gwillmer said:
Anybody with the H931 and Oreo able to help us out? It'd be very much appreciated!
Click to expand...
Click to collapse
I have two V30's that I can access, both H931 Oreo. One is still stock entirely, bootloader still locked and running the ATT OTA oreo update. The other is mine, converted to a US998 running a custom rom rooted. Would you like me to dump the stock phone? I'd be very interested in seeing band 30 support on a custom rom possibly, and wifi calling would be a bonus.
Phoked said:
I have two V30's that I can access, both H931 Oreo. One is still stock entirely, bootloader still locked and running the ATT OTA oreo update. The other is mine, converted to a US998 running a custom rom rooted. Would you like me to dump the stock phone? I'd be very interested in seeing band 30 support on a custom rom possibly, and wifi calling would be a bonus.
Click to expand...
Click to collapse
Yeah, that would be awesome. Backup boot and modem also if you can. At&t has no kdz like sprint. It would be nice for at&t users to have a stock flashable zip also.
Phoked said:
I have two V30's that I can access, both H931 Oreo. One is still stock entirely, bootloader still locked and running the ATT OTA oreo update. The other is mine, converted to a US998 running a custom rom rooted. Would you like me to dump the stock phone? I'd be very interested in seeing band 30 support on a custom rom possibly, and wifi calling would be a bonus.
Click to expand...
Click to collapse
Yes! Not only is there potentially band 30 and wifi calling, but as of right now, there's no way to bring an H931 back to stock Oreo after doing any crossflashing. Modem and system definitely are most important, but it might not be a bad idea to dump everything except userdata (so that a crossflashed H931 can be completely returned to stock in case of warranty issues, etc).
Thanks!
gwillmer said:
Yes! Not only is there potentially band 30 and wifi calling, but as of right now, there's no way to bring an H931 back to stock Oreo after doing any crossflashing. Modem and system definitely are most important, but it might not be a bad idea to dump everything except userdata (so that a crossflashed H931 can be completely returned to stock in case of warranty issues, etc).
Thanks!
Click to expand...
Click to collapse
I'll be glad to help development in any kind of way.
Didn't know there was so many partitions haha. Dumping all partitions except userdata with patched LGUP as I type this. Is there any uploading site you would prefer me to use? I haven't uploaded large files for public use before.
---------- Post added at 09:16 AM ---------- Previous post was at 09:05 AM ----------
Hmm, I unfortunately ran into an error towards the end of the dump
{
"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"
}
Is this dump still valid or should I try something else? All the files I got from it are sitting at 8.42gb so far.
Edit: Just tried again. Watched the progress from 0-100% this time and it his the error once at 100%. Produced the same error and dump files are the same size as before. 74 files in total. There are 3 modem files, the first one at 110mb, the rest at 2mb. The system file is at 6.58gb. Let me know if these files are still of use despite the error and I will upload to the site of your choice.
Phoked said:
I'll be glad to help development in any kind of way.
Didn't know there was so many partitions haha. Dumping all partitions except userdata with patched LGUP as I type this. Is there any uploading site you would prefer me to use? I haven't uploaded large files for public use before.
---------- Post added at 09:16 AM ---------- Previous post was at 09:05 AM ----------
Hmm, I unfortunately ran into an error towards the end of the dump
Is this dump still valid or should I try something else? All the files I got from it are sitting at 8.42gb so far.
Edit: Just tried again. Watched the progress from 0-100% this time and it his the error once at 100%. Produced the same error and dump files are the same size as before. 74 files in total. There are 3 modem files, the first one at 110mb, the rest at 2mb. The system file is at 6.58gb. Let me know if these files are still of use despite the error and I will upload to the site of your choice.
Click to expand...
Click to collapse
The size sounds about right. The last file it dumped might be corrupted, but it's odd that it did the same thing twice. It does say timeout, so maybe the phone just stops sending data when it's done? Either way, all the other files should be fine.
banziitox24 used mediafire and that worked pretty well. Also, putting them all in an zip or rar would cut down on the file size and save you some time.
Thanks again!
Glad to help, uploading compressed rar (2.54gb) to mediafire right now. If there's a way to fix the error I was seeing and you at some point need the file that perhaps got corrupted, let me know and I will be happy to try again. Also, I noticed a file popped up after LGUP finished the dump, titled "LG_358164080144563_20180619092912.xml", is this of any use too?
---------- Post added at 10:46 AM ---------- Previous post was at 10:05 AM ----------
http://www.mediafire.com/file/jy11ghyhh5iddz3/H93120d.rar/file
Hope this helps. Would be exciting to see these carrier limited functions come back for those rooted, especially if my V30 dump contributed to so haha. Feel free to ask me if there's anything else I can help with.
Related
**WARNING** I TAKE NO RESPONSIBILITY FOR ANYTHING THAT HAPPENS TO YOU, YOUR MOM, YOUR DEVICE, OR ANYTHING ELSE THAT HAPPENS IN YOUR LIFE AS A RESULT OF FOLLOWING ANY INFORMATION/INSTRUCTIONS I OR ANYONE ELSE POSTS IN THIS THREAD. EVERYTHING YOU DO IN YOUR LIFE IS AT YOUR OWN RISK AND THIS IS NO DIFFERENT. DO NOT CONTINUE IF YOU'RE GOING TO BLAME ME FOR ANYTHING AT ALL.
This is mostly going to pertain to the oem.prop file located in /oem on your device because that's where my work ended up taking me.
So in my research and impatience I've discovered a few things about the Amazon variant of the Moto G4:
The 32GB model of the Amazon variant *can* be bootloader unlocked, just follow the normal instructions.
The athene_amz descriptor in ro.product.name in oem.prop prevents Amazon variant users from installing stock ROMs not specifically meant for the Amazon variant.
ro.product.name in oem.prop can be modified.
Some things I'm working on:
Trying to find a copy of the non-Amazon oem.prop.
Seeing if there's anything else that needs to be done to the Amazon version to show completely as the default USA model.
Some questions:
Is anyone willing to send me a copy of their oem.prop from their standard Moto G4 USA/NA oem.prop?
I'm having some radio/SIM issues with AOSP/Lineage-based Nougat ROMs, I'm on a Sprint-based MVNO. Is anyone else having these issues?
After modifying oem.prop which stock ROMs work with the Amazon variant?
Does anyone have a more efficient way of mounting /oem? My method will be described below.
That's it for the lists, I just thought since some of this stuff was new or not well organized that I'd make it easy to understand my key points.
The reason you would want to modify oem.prop, which contains the basic information about your device no matter what ROM you have installed, is because when you try to install stock ROMs they check for at least these 2 things: They check your phone's model and your currently installed firmware. I believe the soak test release looks for the latest available version of Marshmallow (64/65), which should be the same as the Amazon variant... but even with an unlocked bootloader it will still refuse to install because instead of showing up as just "athene" in oem.prop it shows up as "athene_amz" and refuses to install. For the Indian release it looks for an *older* revision of Marshmallow (63/64) and refuses to install for that reason and because of the ro.product.name descriptor in oem.prop. If you're looking to install a stock ROM besides the Amazon versions it's imperative to make these changes. There are a few other reasons as well. I've seen people talk about successfully relocking their devices, I haven't done any research on this but if you're looking to sell or gift your device you may possibly be able to fully convert it to a standard Moto G4 using the non-Amazon ROMs and update line through these means.
So here's what I did to modify my oem.prop:
Find and download a stock ROM for a Moto G4/Plus variant you know to be incompatible with your device (I used the soak test).
Plug phone into computer via USB.
Push the zip file to your phone/SD card.
Reboot to custom recovery (I'm using the latest TWRP).
Attempt to flash ROM.
Go to your PC and open up ADB shell.
Enter the command
Code:
mount -o rw,remount,rw /oem
Via ADB shell navigate to /oem and pull oem.prop
Create a back up of oem.prop on your PC for posterity. I highly recommend that you do not skip this step.
Open oem.prop on your PC and change all instances of "athene_amz" to "athene" (without any quotes).
Rename the oem.prop on your device to oem.prop2.
Push your modified oem.prop to /oem
Enter the command
Code:
mount -o ro,remount,ro /oem
Enjoy your new ability to flash non-Amazon stock ROMs!
A few notes:
The reason I had to make an invalid flash attempt is because I couldn't figure out how to get /oem to mount otherwise. Normally the folder appears completely empty and I don't know where the files are nested in the filesystem. Even using the mount command I was unable to do so.
I have yet to install a stock ROM on my device because after unlocking my bootloader I immediately flashed Lineage thinking I'd have no issues with it. I did have issues and I had read something that lead me to the impression that I had to flash a modem file to my phone to get it to work properly. After being unable find it I went in search of a stock Nougat ROM thinking the update from that might flash the necessary firmware. The error from that attempt is what lead me to figuring what I've posted about oem.prop... but sadly in order to install ANY stock ROM I'll need to go through the lengthy downgrade process... which I will as I experiment but since this G4 is my primary device it'll be some time before I get too deep into it. Lineage works fine enough for now. Hopefully there's a fix soon. But it's worth stating that the reason I was refused the stock ROMs is because of the installed ROM version rather than the variant as it was before.
Whoa, thanks for this information!
But can we change it in the rom we want to install?
{
"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"
}
lerg96 said:
But can we change it in the rom we want to install?
Click to expand...
Click to collapse
I'm wondering if changing that file will allow us to get on the correct upgrade path
---------- Post added at 02:31 PM ---------- Previous post was at 02:23 PM ----------
Because I'm rooted and unlocked I can edit the file... here is the contents of the file
# # OEM_BUILD_PROPERTIES #
ro.build.id=MPJ24.139-64
ro.build.version.incremental=65
ro.product.name=athene_amz
ro.mot.build.oem.product=athene_amz
ro.mot.build.customerid=amz
ro.carrier.oem=amz
so question... What does the CustomerID and Carrier.OEM need to be?
bigunwhistle said:
I'm wondering if changing that file will allow us to get on the correct upgrade path
---------- Post added at 02:31 PM ---------- Previous post was at 02:23 PM ----------
Because I'm rooted and unlocked I can edit the file... here is the contents of the file
# # OEM_BUILD_PROPERTIES #
ro.build.id=MPJ24.139-64
ro.build.version.incremental=65
ro.product.name=athene_amz
ro.mot.build.oem.product=athene_amz
ro.mot.build.customerid=amz
ro.carrier.oem=amz
so question... What does the CustomerID and Carrier.OEM need to be?
Click to expand...
Click to collapse
That's the main reason why I want copies of non-Amazon oem.prop files. I'd also like a few from different (primarily earlier) versions of stock ROMs.
I'm also interested in how you got the file to show up at all. I'm rooted and unlocked as well but I can't even see the contents of /oem without following the steps I posted.
MoseIlla said:
That's the main reason why I want copies of non-Amazon oem.prop files. I'd also like a few from different (primarily earlier) versions of stock ROMs.
I'm also interested in how you got the file to show up at all. I'm rooted and unlocked as well but I can't even see the contents of /oem without following the steps I posted.
Click to expand...
Click to collapse
I used solid explorer.
https://play.google.com/store/apps/details?id=pl.solidexplorer2&hl=en
#
# OEM_BUILD_PROPERTIES
#
ro.build.id=MPJ24.139-63
ro.build.version.incremental=64
ro.product.name=athene
ro.mot.build.oem.product=athene
ro.mot.build.customerid=retail
This is from a UK G4 xt1622, I ran CM and Lineage before downgrading to marshmallow. The last couple of Lineage made my WiFi unstable. I hope this helps.
Guys I have a problem I edited my oem.prop and now my phone will not make it past boot. It goes into TWRP and I can't get to that file again. Any suggestions? I can't follow the above directions because it will not allow me to mount OEM
bigunwhistle said:
Guys I have a problem I edited my oem.prop and now my phone will not make it past boot. It goes into TWRP and I can't get to that file again. Any suggestions? I can't follow the above directions because it will not allow me to mount OEM
Click to expand...
Click to collapse
Have you tried doing a factory reset and reflashing your ROM? Where exactly in the instructions I've provided are you getting stuck?
mikemelbrooks said:
#
# OEM_BUILD_PROPERTIES
#
ro.build.id=MPJ24.139-63
ro.build.version.incremental=64
ro.product.name=athene
ro.mot.build.oem.product=athene
ro.mot.build.customerid=retail
This is from a UK G4 xt1622, I ran CM and Lineage before downgrading to marshmallow. The last couple of Lineage made my WiFi unstable. I hope this helps.
Click to expand...
Click to collapse
Interesting, yours doesn't have "ro.carrier.oem" carrier property?
MoseIlla said:
Have you tried doing a factory reset and reflashing your ROM? Where exactly in the instructions I've provided are you getting stuck?
Click to expand...
Click to collapse
I have not done a factory reset yet or rom, does the rom overwrite the OEM folder? I have tried to restore my backup with TWRP and it is still not working. Also when I try do
ADB Devices the device is listed
when I goto ADB Shell and try to SU it says it isn't found (but it was rooted) and when I try to mount /OEM it says it can't find it in /proc/mounts
bigunwhistle said:
I have not done a factory reset yet or rom, does the rom overwrite the OEM folder? I have tried to restore my backup with TWRP and it is still not working. Also when I try do
ADB Devices the device is listed
when I goto ADB Shell and try to SU it says it isn't found (but it was rooted) and when I try to mount /OEM it says it can't find it in /proc/mounts
Click to expand...
Click to collapse
Follow the directions I've provided. If you skip even one of the steps you won't be able to make any changes.
As far as what happened to your install my GUESS is that your ROM is bugging out because that information is different from the original install. Are you using stock or something else?
MoseIlla said:
Follow the directions I've provided. If you skip even one of the steps you won't be able to make any changes.
As far as what happened to your install my GUESS is that your ROM is bugging out because that information is different from the original install. Are you using stock or something else?
Click to expand...
Click to collapse
I've got a 32gb amazon variant
the bootload it unlocked, system rooted TWRP installed and the ads disabled. Am I missing something. I'm running windows and I followed what commands you had listed but I still can't get it to connect.
MoseIlla said:
Interesting, yours doesn't have "ro.carrier.oem" carrier property?
Click to expand...
Click to collapse
Probably because the phone was bought unlocked, I E no carrier. In the UK you can buy most phones unlocked,and put in the sim of your choice, otherwise why have a dual sim phone?
bigunwhistle said:
I've got a 32gb amazon variant
the bootload it unlocked, system rooted TWRP installed and the ads disabled. Am I missing something. I'm running windows and I followed what commands you had listed but I still can't get it to connect.
Click to expand...
Click to collapse
I went back to pushed the soak test which allowed me to finally see the files in TWRP filemanager on the phone, renamed the backup I made of the OEM.PROP file to the correct name and rebooted, it worked!!! I have my phone back.... I had changed the last two lines from AMZ to retail it did not help.
mikemelbrooks said:
Probably because the phone was bought unlocked, I E no carrier. In the UK you can buy most phones unlocked,and put in the sim of your choice, otherwise why have a dual sim phone?
Click to expand...
Click to collapse
The Moto G4 is sold almost exclusively SIM unlocked to the best of my knowledge. Amazon being listed as the carrier must have to do with the way they deliver updates. Perhaps removing that line completely is what will set an Amazon device to retail on the update channel.
bigunwhistle said:
I went back to pushed the soak test which allowed me to finally see the files in TWRP filemanager on the phone, renamed the backup I made of the OEM.PROP file to the correct name and rebooted, it worked!!! I have my phone back.... I had changed the last two lines from AMZ to retail it did not help.
Click to expand...
Click to collapse
It's good to know that can happen. I'll play with it more soon. When I have the patience I'm going to downgrade and switch to some form of stock ROM.
MoseIlla said:
The Moto G4 is sold almost exclusively SIM unlocked to the best of my knowledge. Amazon being listed as the carrier must have to do with the way they deliver updates. Perhaps removing that line completely is what will set an Amazon device to retail on the update channel.
It's good to know that can happen. I'll play with it more soon. When I have the patience I'm going to downgrade and switch to some form of stock ROM.
Click to expand...
Click to collapse
I had to reroot the phone, I want to see that retail OEM.prop file really bad now... Do you think we need to make changes anywhere else?
bigunwhistle said:
I had to reroot the phone, I want to see that retail OEM.prop file really bad now... Do you think we need to make changes anywhere else?
Click to expand...
Click to collapse
If you look at the one mikemelbrooks posted it shows that there's no ro.carrier.oem property at all. Otherwise it's exactly what you did. My guess is just that the inconsistency is what was causing you issues, but I couldn't say otherwise. My oem.prop is modified and works fine under Lineage. You shouldn't modify your oem.prop unless you're planning on installing a ROM that's not compatible with the Amazon variant, so don't mess with it until you're going to attempt a flash which would necessarily involve a factory reset of your device.
MoseIlla said:
If you look at the one mikemelbrooks posted it shows that there's no ro.carrier.oem property at all. Otherwise it's exactly what you did. My guess is just that the inconsistency is what was causing you issues, but I couldn't say otherwise. My oem.prop is modified and works fine under Lineage. You shouldn't modify your oem.prop unless you're planning on installing a ROM that's not compatible with the Amazon variant, so don't mess with it until you're going to attempt a flash which would necessarily involve a factory reset of your device.
Click to expand...
Click to collapse
Yeah but his is a xt1622 I've been thinking about lineage is it the bees knees?
bigunwhistle said:
Yeah but his is a xt1622 I've been thinking about lineage is it the bees knees?
Click to expand...
Click to collapse
Cyanogenmod has always been a great ROM. I'm having some trouble with getting 4G(I only get 3G) but I don't think my problem is typical. I'm on a Sprint-based MVNO so that may have something to do with it. I would recommend backing up your current install and giving it a try.
Hi everyone, I've followed the WTF thread to unlock the bootloader on a V30 H933 (the Canadian version), but even after unlocking there's no fastboot support on the phone, only the US998 version seems to have it. Trouble is that Rogers, my local operator, only supports VoLTE and VoWiFi on their recognized devices - I tried having US998 running on my phone, calling their support and possibly getting some actual configuration I could put on the phone, but their response was "your phone is defective and needs to be replaced".
All that said, my goal here is to somehow install TWRP on this phone and root under the original ROM, so I can have the features I need from the network. So far, I've been pretty unsuccessful in this, so my plead would be: could anyone chime in to help me either
flash the minimal necessary over US998 to get H933 functionality/network information back as to reenable VoLTE and VoWiFi on my operator
come up with an update.zip or some other file I could use to flash a Magisk-patched boot.img
pack a full flashable ZIP image of the Canadian ROM (my last attempt at this left the phone in bootloop)
an alternative idea I haven't thought about that could help?
Ideally, at the end of the process, I'd like to have TWRP and Magisk installed on the phone, but I could settle for simply Magisk.
Once again, any help or pointers are more than welcome and appreciated.
I think you can extract a h933 kdz and flash individual partitions that do not have to do with recovery or the bootloader. You can probably use the dd command for it. I think the partitions you dont flash are anything with boot in it, abl and recovery. There may be a few more however.
The Elite said:
I think you can extract a h933 kdz and flash individual partitions that do not have to do with recovery or the bootloader. You can probably use the dd command for it. I think the partitions you dont flash are anything with boot in it, abl and recovery. There may be a few more however.
Click to expand...
Click to collapse
I tried something similar, extracted a KDZ and put the necessary BIN files on a flashable ZIP I found around. All I achieved was bootlooping the device...
I have an H933 on Freedom Mobile, and running the stock FM firmware. The loss of VOWIFI (and VoLTE) are exactly what i thought would happen if I proceed with flashing to US998.
I think #1 is right; that you may be able to restore access to network specific functionality but it would depend on being able to isolate the specific required "patch".
With this in mind, take a look at this post from the WTF! Thread:
https://forum.xda-developers.com/showthread.php?p=76613814
That user flashed some files (modem binaries from the original device firmware I think) and was able to restore VOWIFI and VoLTE functionality on the Verizon network.
Sent from my LG-H933 using Tapatalk
My h933 converted to us998 says that my volte is enabled
cre4per said:
My h933 converted to us998 says that my volte is enabled
Click to expand...
Click to collapse
What menu is that from @cre4per? Have you had the opportunity to confirm staying on LTE while receiving a call?
That would be good news to hear VoLTE working on a Canadian network using a generic phone model (instead of proprietary stuff).
Sent from my LG-US998 using Tapatalk
Mad Medik said:
What menu is that from @cre4per? Have you had the opportunity to confirm staying on LTE while receiving a call?
That would be good news to hear VoLTE working on a Canadian network using a generic phone model (instead of proprietary stuff).
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
*#*#4636#*#*,
and to be honest i never really noticed, will do some checks today to see if i stay on lte, will let you know
cre4per said:
*#*#4636#*#*,
and to be honest i never really noticed, will do some checks today to see if i stay on lte, will let you know
Click to expand...
Click to collapse
Looking at this this morning. I don't think that is an indication that you are connected to a VoLTE service; just that your device is ready to accept it if the right service becomes available. I have that switch turned on and the service menu even says the voice network is LTE too (see image below) but Freedom Mobile doesn't even offer VoLTE service so it isn't possible that I actually have VoLTE operational.
I would interpret the LTE provision switch as turning on or off the functionality in your device, not a connection authorization from the network. Sort of like turning on the HD calling option on your device; it allows the possibility but won't do anything unless the service provider has the capability and authorizes it on your connection.
If someone has VoLTE working, could you check the menu cited by @cre4per, then hit the options (3 dots) and in there, select IMS service status? It lools like this is where you *should* see if the network has connected you to their VoLTE service (see image below).
I don't know how to interpret the, "Voice Network: LTE" on the main menu screen.
Just check and switches to 3g on calls also when going into that ims menu says unavailable
GryphonBR said:
I tried something similar, extracted a KDZ and put the necessary BIN files on a flashable ZIP I found around. All I achieved was bootlooping the device...
Click to expand...
Click to collapse
Out of all the partitions which ones did you flash and which ones did you not flash? Also was the h933 kdz also for oreo?
-deleted-
cre4per said:
My h933 converted to us998 says that my volte is enabled
Click to expand...
Click to collapse
As @Mad Medik mentioned, so far I don't know of any Canadian operators enabling VoLTE (or VoWiFi for that matter) to generic phones. I have a Rogers P10 Plus that's registered under my account as my main phone and which I reflashed to have these features available, but it just won't work. I've had extended arguments with Rogers representatives about it, and the 1+3T I'm presently using even have the same config your phone is showing: VoLTE Provisioned, but IMS shows as Not Registered so nothing else works. I'm waiting on an LS998 I bought to arrive, I'll try flashing H933 on it to see if it actually allows me to register on IMS.
The Elite said:
Out of all the partitions which ones did you flash and which ones did you not flash? Also was the h933 kdz also for oreo?
Click to expand...
Click to collapse
KDZ was for Oreo, indeed. It was the one I used to bring the phone to the latest (at the moment) update available.
As for which partitions I flashed, I was gonna give you a list, but to make it short the only partition not flashed was recovery.
GryphonBR said:
As @Mad Medik
KDZ was for Oreo, indeed. It was the one I used to bring the phone to the latest (at the moment) update available.
As for which partitions I flashed, I was gonna give you a list, but to make it short the only partition not flashed was recovery.
Click to expand...
Click to collapse
As far as I know there are some boot partitions that should not be flashed, which may have caused the soft brick. I know autoprime used to make these zips for the G3 and runningnak3d made one for the V10, you might want to cross reference the partitions they used and what they didnt. Probably the V10 first because the G3 is relatively ancient. I think in essence you should just be able to flash boot, system and modem and rpm though, but you would need 2 combine the split up system images after the extract.
The Elite said:
As far as I know there are some boot partitions that should not be flashed, which may have caused the soft brick. I know autoprime used to make these zips for the G3 and runningnak3d made one for the V10, you might want to cross reference the partitions they used and what they didnt. Probably the V10 first because the G3 is relatively ancient. I think in essence you should just be able to flash boot, system and modem and rpm though, but you would need 2 combine the split up system images after the extract.
Click to expand...
Click to collapse
The reason why I was flashing everything is because I used this thread to recover from a previous soft brick I stumbled upon. Upon speaking to the thread creator, he mentioned I should be able to follow a similar process to achieve an H933 flashable file. Did that and, well, managed to soft brick the phone... I might try your idea, though.
So, from my knowledge of attempting to get VoLTE working on an HTC 10, I suspect you won't get VoLTE working on anything other than Rogers H933 firmware. For whatever reason, the programming required for VoLTE isn't on the USIM card in your phone, but rather programmed into the phone by the provider. This means, unless your phone model is sold and supported for VoLTE on the provider you wish to use it on, you're screwed like I was, trying to get VoLTE working on my HTC 10 on Rogers.
This being said, the good news is we are back to CDMA tech here, where the only thing preventing you from using your third party phone with your provider is knowing what code to enter, and what parameters to program in. Since my H933 is on Telus, my programming won't do you much good.
What you're looking for is the IMS settings or IP Multimedia Subsystem settings, as this is what carries the VoIP packets that consist of VoLTE. If someone were to post the settings from their Rogers H933, you may be able to get VoLTE working on US998 firmware.
Why not just flash system and boot? After unlocked and rooted of course.. Lg up partition DL will let you flash individual partitions. I would have done it that way for my carrier but there is no kdz available..
JWnSC said:
Why not just flash system and boot? After unlocked and rooted of course.. Lg up partition DL will let you flash individual partitions. I would have done it that way for my carrier but there is no kdz available..
Click to expand...
Click to collapse
I tried that last night just bootloops
cre4per said:
I tried that last night just bootloops
Click to expand...
Click to collapse
Did you wipe data?
JWnSC said:
Did you wipe data?
Click to expand...
Click to collapse
Yea. Then went to restore and the restore wouldn't even work anymore. Was saying there was no partitions backed up but I had use that restore numerous of times trying to get los to boot very strange had to start back from scratch
Anyone with H933 from freedom mobile convert to US988? I'm just wondering how the service is after the change. I'm reading mixed reports but once modems extracted and compared there was a difference.
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.
Hello,
I currently have an H932 with a corrupt LAF on pie. I am unable to root or downgrade because of this. My phone is laggy and unresponsive at times and hope to upgrade soon. If anyone could help to get the .up file for my h912. The link below is instructions on how to get this URL or .up file.
https://www.the***********.com/how-to-capture-ota-update-url-android/
Thanks,
zapzapdew
Same here,. hopefully someone that has not yet updated, or has just started the h932 root process can capture the ota before continuing the steps
Repairing LAF Partition with LG Bridge
zapzapdew said:
Hello,
I am unable to root or downgrade because of this. My phone is laggy and unresponsive at times and hope to upgrade soon.
Click to expand...
Click to collapse
I face similar issue when I reset my phone (also h932) and then TWRP deleted and replaced by stock recovery. I tried to install twrp again via lafsploit method no luck. my phone not detected on my PC. so I decide to download LG Bridge and perform an update (I assume that your phone can boot android). If your phone is already running 30d pie then click update error recovery (see image below). If you still on older version you can update to recent version without update error recovery
{
"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"
}
proceed and wait till complete. laf partitiom will be restored and download mode works as usual
download LG Bridge
(select software update >> software update tool)
immns said:
proceed and wait till complete. laf partitiom will be restored and download mode works as usual
download LG Bridge
(select software update >> software update tool)
Click to expand...
Click to collapse
May I ask did your phone bootloader unlocked when update using LG bridge. Actually I try before using update error recovery but no luck. After download firmware when install update on stock recovery, it hang on 5% then restart. My phone is bootloader unlocked when I try. Is it necessary has to be on locked bootloader. Thank you.
hendavi said:
May I ask did your phone bootloader unlocked ..... Thank you.
Click to expand...
Click to collapse
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
immns said:
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
Click to expand...
Click to collapse
Thank you for reply, I have try manual enter to download mode but not successful. The phone restart when it boot into download mode.
I try flash twrp using fwul, thanks for the info.
hendavi said:
Thank you for reply, I have try manual enter to download mode but not successful. The phone restart when it boot into download mode.
I try flash twrp using fwul, thanks for the info.
Click to expand...
Click to collapse
Do you know what version of LAF you are running? It was pointed out in the root thread that after you get TWRP, you need to flash the correct version of LAF or put TWRP on LAF.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Do you know what version of LAF you are running? It was pointed out in the root thread that after you get TWRP, you need to flash the correct version of LAF or put TWRP on LAF.
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I don't know what laf do I have now, probably is stock laf because after flash pie stock rom I forget to flash RCTD Remover and Disable DM-Verity zip.
Unable to flash TWRP because my phone cannot go to download mode. Thanks anyway.
immns said:
yes, i did it with unlocked bootloader. in my case, i could enter download mode but my pc couldn't detect any device. have you tried to enter download mode manually? what's look like? mine says "unknown 0/0/0"
if you never try to flash laf partition with another things (e.g stock laf or twrp), it might be still using h933 laf, and that means you can try to flash twrp using fwul
Click to expand...
Click to collapse
could you solve your problem ???? The same happens to me, if you could answer thank you very much.
lost download mode and twrp, also root.
I would like to know if there is any way}, thanks
Reposting this here for visibility:
Hello all. So I am having a similar issue. I was already running a stock rom and I flashed the stock laf from the stock H932 thread. However, I noticed that the latest laf version from that thread doesn't match the latest firmware. I'm not sure if that was the cause but I lost my download mode abilities and twrp recovery (booting into recovery shows "no command". My bootloader is still unlocked and the device will boot into the stock system but download mode freezes whenever accessed meaning I can't use either oreo or pie LGUP to repair it. It shows Unknown B79 and says Unknown / E / L / RO at the bottom. Does anyone have an idea on if there is anything I can do to restore download mode? I noticed I have Would it cause problems to relock the bootloader at this point, as I would like to relock it with the coming changes to safetynet. Thank you for any help.
I don't have any suggestions other than what was already posted in the H932 root thread.
1) If you're NOT already on Pie, you should be offered an OTA update, which will repair Download mode (at least previous OTA updates did that).
2) If you're already on Pie, you need that Pie OTA file which everybody is looking for. Force flashing that with LGUP in FOTA mode (inside the OS) should also repair Download mode (at least previous OTA updates did that).
Do NOT relock the bootloader unless the phone is completely, 100% stock. Otherwise you'll get a brick on next boot, when signature checks are performed on all partitions. As I understand, this will blow a Qfuse, which is irreversible.
TheDannemand said:
I don't have any suggestions other than what was already posted in the H932 root thread.
1) If you're NOT already on Pie you, should be offered an OTA update, which will repair Download mode (at least previous OTA updates did that).
2) If you're already on Pie, you need that Pie OTA file which everybody is looking for. Force flashing that with LGUP in FOTA mode (inside the OS) should also repair Download mode (at least previous OTA updates did that).
Do NOT relock the bootloader unless the phone is completely, 100% stock. Otherwise you'll get a brick on next boot, when signature checks are performed on all partitions. As I understand, this will blow a Qfuse, which is irreversible.
Click to expand...
Click to collapse
Thanks for the info. I'm already on pie. It seems the .up file is nowhere to be found. I can use the phone as is but with the bootloader unlocked I'm hoping that I won't be affected by the supposed upcoming safetynet changes. Is there no other way to repair the laf partition besides getting a hold of a file it seems no one has? Thanks for your help.
tbxn said:
Thanks for the info. I'm already on pie. It seems the .up file is nowhere to be found. I can use the phone as is but with the bootloader unlocked I'm hoping that I won't be affected by the supposed upcoming safetynet changes. Is there no other way to repair the laf partition besides getting a hold of a file it seems no one has? Thanks for your help.
Click to expand...
Click to collapse
I do understand. But remember that Qualcomm, LG and T-Mobile all went out of their way to make sure that this phone was locked down and un-rootable. They stripped flash and boot commands from fastboot. And they choose RSA signatures different from all the other V30 models, so that it would be like a prison island in the middle of the ocean.
The only reason we can still root it at all, is because of a massive effort by a brilliant and knowledgeable Dev, who reverse engineered the boot and laf code. And he found this narrow path to let us root it.
But that doesn't mean the H932 just rolls over and starts to cooperate with us: It's still designed to make it as difficult as possible for us to do what we're trying to do. And it is very unforgiving of any mistakes.
So once both TWRP and Download mode and root (in the OS) are gone, there's not much left to fix the situation. The only thing left is LGUP FOTA. But it requires an OTA file. Several were posted for Oreo, but none so far for Pie.
Anybody with an H932 and enough time on their hands can capture it, if they're willing to roll back to Oreo (losing their data) then update again using OTA.
TheDannemand said:
I do understand. But remember that Qualcomm, LG and T-Mobile all went out of their way to make sure that this phone was locked down and un-rootable. They stripped flash and boot commands from fastboot. And they choose RSA signatures different from all the other V30 models, so that it would be like a prison island in the middle of the ocean.
The only reason we can still root it at all, is because of a massive effort by a brilliant and knowledgeable Dev, who reverse engineered the boot and laf code. And he found this narrow path to let us root it.
But that doesn't mean the H932 just rolls over and starts to cooperate with us: It's still designed to make it as difficult as possible for us to do what we're trying to do. And it is very unforgiving of any mistakes.
So once both TWRP and Download mode and root (in the OS) are gone, there's not much left to fix the situation. The only thing left is LGUP FOTA. But it requires an OTA file. Several were posted for Oreo, but none so far for Pie.
Anybody with an H932 and enough time on their hands can capture it, if they're willing to roll back to Oreo (losing their data) then update again using OTA.
Click to expand...
Click to collapse
I understand, and I am also very grateful for the work put in by that dev and the many others here on xda who help other users out. Perhaps some generous person will be able to do like you mentioned and be able to capture the OTA link. Just out of curiousity, what would that process look like? Roll back to oreo via lgup? And then what would be the best way to capture the link? Could it be done without root? Thanks again for your input.
tbxn said:
I understand, and I am also very grateful for the work put in by that dev and the many others here on xda who help other users out. Perhaps some generous person will be able to do like you mentioned and be able to capture the OTA link. Just out of curiousity, what would that process look like? Roll back to oreo via lgup? And then what would be the best way to capture the link? Could it be done without root? Thanks again for your input.
Click to expand...
Click to collapse
Yes, roll back to Oreo with LGUP. The best way to do that is via Nougat in Partition DL mode, in order to rewrite the partition table. Then to Oreo from there, Upgrade mode should work.
Then trigger the OTA (if it doesn't come right away) by changing the date forward a few days at a time.
Once the OTA is offered, there is a process to capture the link. I've never done it myself. The OP posted a link in post #1, but XDA scrambled it for the benefit of... well, someone, we'd hope. Google should be able to find it.
One thing I forgot: You can also try LG Bridge Recovery mode, if you haven't already. Some reported it fixed their Download mode, others say it requires Download mode. Worth a try. See post #2.
Edit: Capturing the OTA does NOT require root, that much I remember. I seem to recall you just search through logcat file immediately after starting the OTA download. But again, I haven't done it myself.
TheDannemand said:
Yes, roll back to Oreo with LGUP. The best way to do that is via Nougat in Partition DL mode, in order to rewrite the partition table. Then to Oreo from there.
Then trigger the OTA (if it doesn't come right away) by changing the date forward a few days at a time.
Once the OTA is offered, there is a process to capture the link. I've never done it myself. The OP posted a link in post #1, but XDA scrambled it for the benefit of... well, someone, we'd hope. Google should be able to find it.
One thing I forgot: You can also try LG Bridge repair mode, if you haven't already. Some reported it fixed their Download mode, others say it requires Download mode. Worth a try. See post #2.
Click to expand...
Click to collapse
Yea, I tried LG Bridge but I ran into the same problem as LGUP. When the phone reboots to enter download mode it freezes in download mode. It does the same thing when I manually enter download mode. I tried different ports, cords, pcs etc. all the same outcome.
However, I may be able to get ahold of another H932 so that I can possibly try my hand at capturing the ota link. I have to be more careful with this one, haha. It was never rooted or bootloader unlocked and I have no intention of doing that. Does it still need to be rolled back to nougat to rewrite the partitions if it was always stock? If so, then I would flash Nougat_h93210c_00_1017.kdz in Partition DL mode selecting all partitions, then flash Oreo_h93220h_00_0416.kdz (in Partition DL mode selecting all partitions again?) and then capture the update url when I get it via adb, correct?
The H932 handset that lost twrp and download mode was last flashed with one of the latest twrp flashable roms based on the kdz and not the actual stock kdz so I hope it still has a chance of working, but at the very least hopefully I can capture the ota url for some other's benefit.
That's a good plan, including the bit about being extra careful
I would first perform a Factory Reset (from Settings menu) while still in Pie. This will save you from FRP and possibly other issues. Then LGUP Partition DL back to Nougat 10d, using the latest Dev Patched LGUP from one of ChazzMatt's threads. Then reboot. If any problems Master Reset (Button Dance). Then LGUP Upgrade to latest Oreo 20s. Reboot.
Make sure you know what to do when you get the OTA offer BEFORE you get it.
I think there's a good chance you'll be able to salvage your other H932. It doesn't have to be completely stock for LGUP FOTA to restore Download mode. At least that's what others reported.
And posting that Pie OTA will be a great help for many people!
Edit: Of course there IS a risk to the unlocked phone. People have had issues going back and forth to Pie. Just saying...
TheDannemand said:
That's a good plan, including the bit about being extra careful
I would first perform a Factory Reset (from Settings menu) while still in Pie. This will save you from FRP and possibly other issues. Then LGUP Partition DL back to Nougat 10d, using the latest Dev Patched LGUP from one of ChazzMatt's threads. Then reboot. If any problems Master Reset (Button Dance). Then LGUP Upgrade to latest Oreo 20s. Reboot.
Make sure you know what to do when you get the OTA offer BEFORE you get it.
I think there's a good chance you'll be able to salvage your other H932. It doesn't have to be completely stock for LGUP FOTA to restore Download mode. At least that's what others reported.
And posting that Pie OTA will be a great help for many people!
Edit: Of course there IS a risk to the unlocked phone. People have had issues going back and forth to Pie. Just saying...
Click to expand...
Click to collapse
Yes, I have taken a look at the steps to capture the link and they seem simple enoughto just use adb logcat while the ota downloads. But I just want to clarify beforehand... When I use LGUP to partition dl back to nougat I think I should be selecting all partitions, but when I go from nougat to oreo should I be using partition dl again and selecting all partitions once again? Just want to verify, thanks.
tbxn said:
Yes, I have taken a look at the steps to capture the link and they seem simple enoughto just use adb logcat while the ota downloads. But I just want to clarify beforehand... When I use LGUP to partition dl back to nougat I think I should be selecting all partitions, but when I go from nougat to oreo should I be using partition dl again and selecting all partitions once again? Just want to verify, thanks.
Click to expand...
Click to collapse
I had suggested the Upgrade mode for going from Nougat to Oreo, but you can do Partition DL too. In fact, that may be best since you're going straight from 10d to 20s. Yes, all partitions.
@ChazzMatt: You sometimes warn about going straight up to the latest Oreo. Any thoughts here? Particularly coming from Pie in the first place?
TheDannemand said:
I had suggested the Upgrade mode for going from Nougat to Oreo, but you can do Partition DL too. In fact, that may be best since you're going straight from 10d to 20s. Yes, all partitions.
@ChazzMatt: You sometimes warn about going straight up to the latest Oreo. Any thoughts here? Particularly coming from Pie in the first place?
Click to expand...
Click to collapse
OK, so I flashed the stock phone and got to the point of running logcat. Nothing showed up in the logcat so I used the Take Bug Report method. I found two different ota file urls in the log. One of them was repeated more often so I think that is the correct one. However, I am unsure as to how I should proceed now. Do I need an .up file in order to use fota on the phone with no download mode? Did I perhaps grab the wrong zips? The zips appear to contain all the ota partition files. Trying to use the zip results in a "Windows cannot find WPDAPI.exe" error and an MTP is not running error. Granted this is the LGUP version that i just used to flash the stock phone successfully.
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!