Can I install the H850 firmware on H831 (Canadian version)?
The H831 is missing a lot of options, like the WiFi (SIP) calling,the radio app, etc.
genasoft said:
Can I install the H850 firmware on H831 (Canadian version)?
The H831 is missing a lot of options, like the WiFi (SIP) calling,the radio app, etc.
Click to expand...
Click to collapse
NO
Just as I thought. Thanks
genasoft said:
Just as I thought. Thanks
Click to expand...
Click to collapse
No problem
On an another though, can I install firmware that is for the same device (H831) but from different carrier:
eg. AVC (H83110d_00_007_11.kdz), RGS (H83110d_00_05_04.kdz), TLS (H83110e_00_07_20.kdz).
genasoft said:
On an another though, can I install firmware that is for the same device (H831) but from different carrier:
eg. AVC (H83110d_00_007_11.kdz), RGS (H83110d_00_05_04.kdz), TLS (H83110e_00_07_20.kdz).
Click to expand...
Click to collapse
Yes
nash211 said:
Yes
Click to expand...
Click to collapse
Thanks
OK guys so here is some additional info. Since I am a rookie when it comes to Android, this info might help somebody get things further.
I spoke with LG Canada tech support and they confirmed that theoretically the H850 firmware would work on H831 so long it is properly done. There is a chance thought that the device might get bricked, but since the hardware is identical it should work.
Your thouths on this are much appreciated.
genasoft said:
OK guys so here is some additional info. Since I am a rookie when it comes to Android, this info might help somebody get things further.
I spoke with LG Canada tech support and they confirmed that theoretically the H850 firmware would work on H831 so long it is properly done. There is a chance thought that the device might get bricked, but since the hardware is identical it should work.
Your thouths on this are much appreciated.
Click to expand...
Click to collapse
@autoprime has already stated...and rather obviously! H850 ROMs are NOT compatible to flash on different G5 variants! There are many changes that will inevitably lead to bricking your handset.
DO NOT FLASH DIFFERENT VARIANT ROMS.
I dont want this to come off as me not agreeing with Anarchist77's comments above or anything like that. I 100% agree with his advice. BUT... just to lay all the facts out there (and some of my opinions) I will say the following...
it would only be a definite brick if the H831 was had the anti-rollback fuse set to version 01... since the H850 is still at version 00.
technically if both the H831 and H850 were fuse version 00.. you could flash the H850 kdz onto the H831 and it wouldnt be an instant brick.. but who knows how much would be broken or crashing... and then you may or may not get stuck on the H850 software unable to flash back to H831 if you wanted to. It's hard to say exactly what would happen but I see nothing positive coming from it.. other than the possible confirmation that it IS possible to flash without brick.
the H830 (tmobile usa) kdz/tot is the model you DO NOT want to flash to any other variant no matter what fuse version each device is at... it would be a 100% brick.
I believe my initial comments about not "cross-flashing" versions was with the H830 and H831... as many H831 users assumed since the numbers were close they could be shared. The H830 has a completely different bootloader than every single other G5 and is 100% incompatible with any other G5.
All the other G5's (att, vzw, sprint, us cellular, canada, intl, korea, etc) all share some common info that would not lead to a instant brick. But without having root access and twrp and the ability to boot into recovery and fix some things that broke.. I dont think anyone should be flashing a different models kdz/tot to their phone.The only exception being the EUR H850 and some other regions H850... Or flashing a H850K device with H850 EUR KDZ... that would be ok (but you still may lose settings like lte calling etc based on carrier).
If you want to "yolo" and try flashing H850 to H831... don't let me stop you. There's a chance you flash the H850 kdz and all is ok. But I think the chance is slim and you should probably stick to just trying other canadian KDZs instead like mentioned in post #5 of this thread.
tl;dr
the only absolutes are..
1. you cannot flash H830 KDZ to any other model as it will 100% be a brick... and the opposite is also true.. you cannot flash a non-H830 KDZ to a H830 phone.. insta-brick.
2. you cannot flash another models KDZ if the KDZ's fuse version is lower than your phones fuse version (KDZ fuse version 0 + phone fuse version 1 = brick)
everything else is uncharted territory but due to region/carrier/radio differences not all things may work... if at all.
Wow, nicely laid out. Very good info.
All I want is to enable the SIP(internet calling) menu and configure a VoIP account.
I guess I M out of luck.
Thanks for the amazing explanation again. Much appreciated.
Just tried to flash a bunch of h860 and h850 roms and, unfortunately, it looks like lg added a variant checker in lgup and thus, unless we find a way to desactivate the check or trick it, we can't flash any rom thats wasn't made for our variant.
So it is possible to flash h850 aboot on h831 device variant without bricking it? The chain of trust will not break?
cloud1250000 said:
So it is possible to flash h850 aboot on h831 device variant without bricking it? The chain of trust will not break?
Click to expand...
Click to collapse
Dunno what you mean by "chain of trust" but I will guess that the kdz fuse count. Anyway, I wrote (and afaik that still true) just before your comment that if you try to flash any firmware that wasn't built for your particular g5 variant (such as the h850 firmware on the h831) lgup will simply throw an error and won't flash so you won't even pass the fuse count check part of the flashing process.
EDIT: Just read @Honestly Annoying post and I guess that's what your referring to. It looks like he found a way to disable the variant check in lg up or simply use another tool for flashing a specific partition. With that said, unless he's using a method specific to the sprint g5 firmware to disable that check (which I doubt ) I don't see why we couldn't do the same.
Well not exactly from lgup, when you get root access, you can flash w/e you want right? Pretty sure this is how he did. But this should brick the device...
cloud1250000 said:
Well not exactly from lgup, when you get root access, you can flash w/e you want right? Pretty sure this is how he did. But this should brick the device...
Click to expand...
Click to collapse
You could be interested in this
---------- Post added at 01:52 AM ---------- Previous post was at 01:49 AM ----------
Also @autoprime I just tried to downgrade to android 6.0 using upercut and I get this error. Do you have any idea of what it could be ? Just checked and the rollback number is still 00..
autoprime said:
Or flashing a H850K device with H850 EUR KDZ... that would be ok (but you still may lose settings like lte calling etc based on carrier)
Click to expand...
Click to collapse
you reckon this will work? i got H850K, i can't live without xposed.
Binh Vo said:
you reckon this will work? i got H850K, i can't live without xposed.
Click to expand...
Click to collapse
flashing H850 kdz to H850K device won't help you unlock the bootloader... LG's bootloader unlock program goes by device IMEI and serial number... not what model number you flash it to. Otherwise people could just flash a different model's KDZ and unlock.
It will work as in not brick your phone.. and allow you to use the H850 software vs the H850K but that's about it.
Just want to add my 2 cent. I'm a technician in a repair shop and use different tools to unlock/repair phones. Most of these tools can (I believe) access and modify partitions through the serial port when in "Download mode". They can erase the /persist partition that is responsible for FRP lock (or directly edit the /data partition to make it seem like the initial setup has been completed), unlock the phone, and also change the IMEI to anything. These three procedures require access to important commands and partitions of the phone. I am looking into how these tools can obtain what seems to me like an unrestricted R/W access to the filesystem. I would guess that since important partitions like /persist, /efs , /data etc. can be freely modified in DL mode to achieve this, the /system partition can probably be modified too. Don't know too much about secure boot, SE Linux and the anti-rollback e-fuse, but these procedures seem to be unaffected by any of those security measures.
What can be done to a H831 today to enable VoLTE?
Related
Question for those of you with experience on the V10. I just upgraded to the V20 (love it btw). My V10 is probably the first phone I never rooted, or loaded a ROM on. I've had many devices with custom roms in the past, however they were always carried branded (not unlocked) phones. Here is my question:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Thanks in advance..
X
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
xarius76 said:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Click to expand...
Click to collapse
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
beavis5706 said:
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
Click to expand...
Click to collapse
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
emdroidle said:
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
Click to expand...
Click to collapse
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
X
xarius76 said:
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
Click to expand...
Click to collapse
This is a substantial annoyance to many people, though there are some hopes of working around this...
xarius76 said:
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
Click to expand...
Click to collapse
I won't swear to it, but I was under the impression the updates come from LG, at which point it should still nominally update if brought to the EU. Failing that, LG Bridge should be able to get updates.
xarius76 said:
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
Click to expand...
Click to collapse
Remember, this is risky though hopeful.
Hi,
Originally I had opened this thread in LG 5 AT&T forum. But, after a request from @Nitro1max1, I understood that he is right and it should be reached for more useres.
Please find the link for requesting LG to open our bootloader - https://www.change.org/p/lg-electro...utm_source=share_petition&utm_medium=copylink
Hopefully, we could make a change together.
last thing, this is the origina thread - https://forum.xda-developers.com/at...se-kdz-tot-t3587926/post71887733#post71887733
I will switch updating here since it will be more convinent to update in one single place.
Cheers,
Mor
stop
What happens when we reach 100 people?
Hopefully, LG will pay attention to our request. This device is no longer a valuable asset for LG (the newly LG G6 is out), therefore I guess we will have a fair odds with getting an unlocking method.
H840 now officially can unlock bootloader
I signed even though I know they will give a sh...t
The real question is who is the one who holds the responsibility for locking the bootloader,LG or AT&T?
I've included both of then in the petition, but, it will be easier to know who have the upper hand here.
About the H840, they are so lucky
Well, I got some idea that might work - but, maybe someone will prove me wrong.
While searching around for methods to unlock the boot-loader for AT&T varient, I came across lots of information about bricked phones. A method that had been proposed there, is to use some device that have JTAG protocol in order to revive the phone.
Digging around the JTAG subject, I found out that it's basicly an interface that have the ability to write new bootloader and pushing new .kdz images.
So, with using some common sense, it might be, that AT&Ts owners could use this method in order to flash the european bootloader into their system and bypassing this whole signed bootloader issue. after that, flashing a new european .kdz file will support this new bootloader that will transform the phone to EU modle.
Only thing is the IMEI and other modem related drivers needs to be taken in consideration.
What do you think about it?
P.S - I'm trying to get in touch with some JTAG box that might give a clearer picture about this subject.
ForMartha said:
Well, I got some idea that might work - but, maybe someone will prove me wrong.
While searching around for methods to unlock the boot-loader for AT&T varient, I came across lots of information about bricked phones. A method that had been proposed there, is to use some device that have JTAG protocol in order to revive the phone.
Digging around the JTAG subject, I found out that it's basicly an interface that have the ability to write new bootloader and pushing new .kdz images.
So, with using some common sense, it might be, that AT&Ts owners could use this method in order to flash the european bootloader into their system and bypassing this whole signed bootloader issue. after that, flashing a new european .kdz file will support this new bootloader that will transform the phone to EU modle.
Only thing is the IMEI and other modem related drivers needs to be taken in consideration.
What do you think about it?
P.S - I'm trying to get in touch with some JTAG box that might give a clearer picture about this subject.
Click to expand...
Click to collapse
No... nononononono. JTAG will not work, look around the threads. I'll say it one more time:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Honestly Annoying said:
No... nononononono. JTAG will not work, look around the threads. I'll say it one more time:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Click to expand...
Click to collapse
Well - you made your point with saying it.
I had looked in the threads but I didn't understand what lockes us with flashing new boot partition using JTAG method (it's like mounting the entire emmc to a point where it can be written with new bootloader etc.)
Please let me know what I'm missing here..
ForMartha said:
Well - you made your point with saying it.
I had looked in the threads but I didn't understand what lockes us with flashing new boot partition using JTAG method (it's like mounting the entire emmc to a point where it can be written with new bootloader etc.)
Please let me know what I'm missing here..
Click to expand...
Click to collapse
You can find the full explanation if you dig around, but basically for the G5 (and most devices) the bootloader unlock is not located in aboot, it is an actual change in the whole bootchain. You can modify aboot to disable a sig check, but that is not the same as unlocking the bootloader and doing so will break the signature of the aboot.img and hard brick your device.
Question is, what is the real differance between H850 to H820. they are sharing the same physical parts, but the bootloader is diffarent. so, by using external tool that will flash the new bootloader, it could be done, right?
Signed.
Honestly Annoying said:
THE ONLY WAY, ONLY. WAY. THIS PHONE WILL GET A BOOTLOADER UNLOCK OR PERSISTANT ROOT IS BY CREATING A NEW EXPLOIT. DONE. THAT'S IT. LITERALLY NOTHING ELSE WILL WORK.
Click to expand...
Click to collapse
few days ago LG G5 SE (H840 - Euro) was added to list of unlockable devices (probably it's a coincidence and not related to this petition, but also give a hope to owner of other G5 devices)
ayaromenok said:
few days ago LG G5 SE (H840 - Euro) was added to list of unlockable devices (probably it's a coincidence and not related to this petition, but also give a hope to owner of other G5 devices)
Click to expand...
Click to collapse
Yep, I agree. I tend to belive that it's LG's move. let's hope that they will do the same for the H820.
Meanwhile, I've spend sime time speaking with @autoprime (thanks for your time!) and the way he sees it is the following :
1. Finding some exploit in the H820 bootloader that will pretty much will effect all the other devices. Question is, if one will find it - will he share it on XDA or sell it to Qualcomm or LG. Time will tell.
2. Finding some leaked debug bootloader (one which the development team is using or the tech system) - That way we will be able to flash custom boot.img (AKA some open recovery).
Meanwhile, I'm doing some digging around for finding exploits.
Now, let's have our finger crossed for one to happen.
ForMartha said:
The real question is who is the one who holds the responsibility for locking the bootloader,LG or AT&T?
I've included both of then in the petition, but, it will be easier to know who have the upper hand
Click to expand...
Click to collapse
You have to take into account that for carrier-specific models, the CARRIER is actually the customer of LG, not the end user.
Only if you buy an unlocked device you are LG's customer.
So I'd guess that LG cannot provide a bootloader unlock for carrier-specific devices, this goes against the contract. Of course things change when the carrier agrees to the unlocking. But do you really think your carrier will allow this?
T-Mobile USA doesn't seem to care, but Verizon and AT&T?
Here in Europe carriers sell the regular H850, they "just" add additional bloat, so you can flash stock KDZs and unlock the bootloader. But the American carriers seem to stick to a different approach. Customers need to vote with their wallets to change this, but I think most people just don't care.
Well said BabelHuber,
Still, I have wish that it will be released eventually.
LG needs to do this or it will be my last LG phone.
Signed
Signed
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.
Hi guys!
At this kind of bad time, I got my hands on a weird Japan variant of V30+, meaning that it came with some weird Japanese baseband, IMEIs, modems or whatever. As already seen in xda threads, someone has succeeded in breaking their LGV35... And I surely just in no way want that also happens to me.
So would someone who has successfully flashed any custom ROMs on their LGV35 be kind enough to help me out? Many thanks for any helping hand! I'm willing to install Lineage OS while maintaining the normal SIM functions.
If I ever find any working solutions I would share it here so as to help anyone that comes after me.
For failures that already happened or anyone confused by the weirdo names plz take a look at this thread: https://forum.xda-developers.com/lg-v30/help/lg-v35-isai-japanese-lg-v30-modem-t3966962
Guessing from my former experiences fighting with these Japan variant of Samsung phones, we need to at least back up the original, that meaning, the working EFS partition in TWRP. But as for LG phones, that might just be impossible: You need to flash US998 firmware, or don't I?
Possible solutions found! Guys, I ain't no Fermat who leaves others' a** kicked. I found it on some Chinese forum and I just need to test it out--don't want to misguide anyone else.
blazkowicz255 said:
For failures that already happened or anyone confused by the weirdo names plz take a look at this thread: https://forum.xda-developers.com/lg-v30/help/lg-v35-isai-japanese-lg-v30-modem-t3966962
Guessing from my former experiences fighting with these Japan variant of Samsung phones, we need to at least back up the original, that meaning, the working EFS partition in TWRP. But as for LG phones, that might just be impossible: You need to flash US998 firmware, or don't I?
Click to expand...
Click to collapse
Problem with US998 firmware is it doesn't have this Japanese variant modem. They even use Wi-Max bands!
ChazzMatt said:
Problem with US998 firmware is it doesn't have this Japanese variant modem. They even use Wi-Max bands!
Click to expand...
Click to collapse
Yay, that is what exactly causing problems around... Japan kinda falls behind maybe could I say so, or it is just they are really different.
blazkowicz255 said:
Yay, that is what exactly causing problems around... Japan kinda falls behind maybe could I say so, or it is just they are really different.
Click to expand...
Click to collapse
The last person who had one of these got a 2nd one which still had unrooted stock. He was going to try to extract the modem partitions so he could re-flash on his bootloader unlocked rooted one. Never heard the results.
ChazzMatt said:
The last person who had one of these got a 2nd one which still had unrooted stock. He was going to try to extract the modem partitions so he could re-flash on his bootloader unlocked rooted one. Never heard the results.
Click to expand...
Click to collapse
Finally, I had time to get my hands on the phone. I'm not as $$y as him tho. I've been trying the method you provided to convert LGV35 to US998, only after which could I proceed. However, I am aware that "master reset" was unable to stop the repeating bootup-reboot procedure. After flashing US998 10D, in LGUP, the phone is still recognized as LGV35 instead of US998. As a result, "upgrading" to US99820a says the wrong device. I had to use DL partitions again. Well, it still loops under that circumstance. Still working on it now.
Updates: Conversion seems successful, LGUP recognize it as "US99820a" now. Dunno if I could ever stop that boot loop or not. If impossible, maybe I had to attempt skipping it then.
There really isn't anything I might do due to that constantly rebooting. In that master resetting, the erasing image does appear, but it doe not help with the boot looping. It is okay for me. The all but one thing that I learned in my long-struggling with android devices, from as early as 2012 to 2020, that it is super normal if things went wrong. You just need to give it more shots, till you finally succeed or simply dump it somewhere.
Finally, I found the way to stabilize OS on the LG LGV35 isai variant. Read accompanied by this song over here if you are a jazz fan just like me: https://www.youtube.com/watch?v=HsM_VmN6ytk
The method is simple:
1, Partition Download US998 10d
2, Partition Download US998 20a
3, PD H930 20j
4, PD US998 10d
5, Refurbish US998 10d
6, Upgrade to US998 20a
ChazzMatt said:
The last person who had one of these got a 2nd one which still had unrooted stock. He was going to try to extract the modem partitions so he could re-flash on his bootloader unlocked rooted one. Never heard the results.
Click to expand...
Click to collapse
Sending 'unlock' (1 KB) FAILED (Write to device failed (Invalid argument))
Don't know if someone else also having this problem? Any fixes?
blazkowicz255 said:
Finally, I found the way to stabilize OS on the LG LGV35 isai variant. Read accompanied by this song over here if you are a jazz fan just like me:
The method is simple:
1, Partition Download US998 10d
2, Partition Download US998 20a
3, PD H930 20j
4, PD US998 10d
5, Refurbish US998 10d
6, Upgrade to US998 20a
Click to expand...
Click to collapse
i have tried but the sim has no signal
Can someone using this variant backup me the partition ftm and modem? help me
phamtuan1699 said:
Can someone using this variant backup me the partition ftm and modem? help me
Click to expand...
Click to collapse
I do understand your frustration. But it is better if you only post about it in ONE thread. You've resurrected 4-5 different threads here asking for help with the same problem.
I replied in one of the other threads too, although unfortunately I don't have a modem image for you.
Good luck. I hope you find it
TheDannemand said:
I do understand your frustration. But it is better if you only post about it in ONE thread. You've resurrected 4-5 different threads here asking for help with the same problem.
I replied in one of the other threads too, although unfortunately I don't have a modem image for you.
Good luck. I hope you find it
Click to expand...
Click to collapse
thanks. I will note the following times
My V30 doesn't seem to enjoy being flashed with Android 10, as it bootloops no matter what ROM I decide to use (Lineage, Havoc, Pixel Experience), and now I'm thoroughly stumped on what to do, as I can't find a fix for this issue. My phones bootloader is unlocked via Frankenstein, and I've used the method of flashing over 10d with 30b and having no luck. I've recently come across a post that said to attempt trying 20b to 30b, which I'll try as a last effort to get this working, but I'd still appreciate advice on what to do. Whether it be this last method, a modification of it, or just something else entirely, I'd be forever grateful for the help.
If you need more information, feel free to ask and I'll provide to the best of my ability.
AkajiWins said:
My V30 doesn't seem to enjoy being flashed with Android 10, as it bootloops no matter what ROM I decide to use (Lineage, Havoc, Pixel Experience), and now I'm thoroughly stumped on what to do, as I can't find a fix for this issue. My phones bootloader is unlocked via Frankenstein.
Click to expand...
Click to collapse
So you Frankensteined to US998, then unlocked the bootloader via WTF exploit. What variant did you start with?
AkajiWins said:
I've used the method of flashing over 10d (Nougat/Android 7) with 30b (Pie/Android 9) and having no luck. I've recently come across a post that said to attempt trying 20b (early Oreo) to 30b, which I'll try as a last effort to get this working, but I'd still appreciate advice on what to do. Whether it be this last method, a modification of it, or just something else entirely, I'd be forever grateful for the help.
If you need more information, feel free to ask and I'll provide to the best of my ability.
Click to expand...
Click to collapse
1) You need stock Android 9 (Pie) as a base before flashing any LOS-17 (Android 10) ROMs. But you seem to know that.
There are several methods to update to to Pie US998. See US998 Pie KDZ thread, post #2 and FOUR MORE WORKAROUND in post #6.
2) What variant did you start with? If you have former AT&T H931 or Canada H933, you'll need to do additional prep steps before installing any LOS custom ROMs.
Of course, you've read the V30 custom ROMs FAQ -- before you even unlocked your bootloader -- right? It tells all this and conveys other important information. This FAQ is prominently linked in the WTF instructions, with suggestion to read first, then come come back to finish unlocking bootloader...
V30 CUSTOM ROMS FAQ
https://forum.xda-developers.com/showpost.php?p=79459374&postcount=2
ChazzMatt said:
So you Frankensteined to US998, then unlocked the bootloader via WTF exploit. What variant did you start with?
1) You need stock Android 9 (Pie) as a base before flashing any LOS-17 (Android 10) ROMs. But you seem to know that.
There are several methods to update to to Pie US998. See US998 Pie KDZ thread, post #2 and FOUR MORE WORKAROUND in post #6.
2) What variant did you start with? If you have former AT&T H931 or Canada H933, you'll need to do additional prep steps before installing any LOS custom ROMs.
Of course, you've read the V30 custom ROMs FAQ -- before you even unlocked your bootloader -- right? It tells all this and conveys other important information. This FAQ is prominently linked in the WTF instructions, with suggestion to read first, then come come back to finish unlocking bootloader...
V30 CUSTOM ROMS FAQ
https://forum.xda-developers.com/showpost.php?p=79459374&postcount=2
Click to expand...
Click to collapse
Yes, I did read through the FAQ before and after unlocking. My variant is the US998U/V30+, which is why I'm a bit confused. The US998 and US998U are identical, aside from storage capacity, right?
I was following one of the guides you posted that stated:
ChazzMatt said:
So for installing the KDZ, I suggest FIRST downgrading to US998 Nougat 10d via Partition DL mode, Master Reset, then Refurbish to US998 Pie KDZ. Here are the steps...
If you have problems flashing this US998 Pie 30b KDZ, see post #6 for FOUR more workaround methods proven to work for some people.
You should probably use this method (DOWNGRADE to NOUGAT first) even if you have TWRP installed. Then reinstall TWRP again after successfully updating to Pie.
KDZ INSTALLATION INSTRUCTIONS
0) Turn off phone, manually go into Download mode before opening Dev Patched LGUP.
1) Using Dev Patched LGUP from THIS thread, flash US998 10d Nougat KDZ via Dev Patched LGUP using Partition DL mode. Select ALL partitions.
2) Master Reset. This is NOT Factory Reset.
3) Boot up to Welcome screen. Turn off phone, manually go back into Download mode.
4) Flash US998 30b Pie KDZ via Dev Patched LGUP using Refurbish mode.
5) Master Reset. This is NOT Factory Reset.
If you did not unlock your bootloader before doing this, then you bootloader is still locked -- because that's what you want. Finished. Set up your phone.
If you had unlocked bootloader before doing all this, you will still have it. Boot to ADB, and PLEASE follow these instructions for re-install TWRP and root!!
Click to expand...
Click to collapse
So that's what I had done a few days ago, but that's also when my problems arose. I was on the TWRP flashable kdz of 30b for a month or two now after Frankensteining it, but wanted to try out some 10 ROMS, but attempting to flash those ROMs was when I started having issues. Flashing the stock US998 kdzs didn't cause issues, the 30b zip I had been running daily wasn't weird, and the md5s for all the files downloaded matched what was provided as correct. That's why I'm a bit stumped, since I believe I followed all the guides I've looked at to make things work correctly, but this one part is giving me a hard time.
I will try those other four methods, since I don't believe to have seen them yet. I will provide an edit to this post after trying them, thank you.
AkajiWins said:
Yes, I did read through the FAQ before and after unlocking. My variant is the US998U/V30+, which is why I'm a bit confused. The US998 and US998U are identical, aside from storage capacity, right?
I was following one of the guides you posted that stated:
So that's what I had done a few days ago, but that's also when my problems arose. I was on the TWRP flashable kdz of 30b for a month or two now after Frankensteining it, but wanted to try out some 10 ROMS, but attempting to flash those ROMs was when I started having issues. Flashing the stock US998 kdzs didn't cause issues, the 30b zip I had been running daily wasn't weird, and the md5s for all the files downloaded matched what was provided as correct. That's why I'm a bit stumped, since I believe I followed all the guides I've looked at to make things work correctly, but this one part is giving me a hard time.
I will try those other four methods, since I don't believe to have seen them yet. I will provide an edit to this post after trying them, thank you.
Click to expand...
Click to collapse
If you Frankenstein'ed, I'm asking what your original variant is. Frankenstein is to convert North American variant to another, also called cross flashing.
Whereas " WTF" is bootloader unlock and installing TWRP. Some North American variants have to Frankenstein to US998 for fastboot flash commands. Then they can use WTF INSTRUCTIONS. But Frankenstein itself is not bootloader unlock, TWRP and root. It's just fully converting one variant to another. It ONLY works with the North American variants, except for T-Mobile H932.
_____
OK, so you were on LG US998 30b stock Pie successfully.
Put your IMEI into this database and tell me what it says? Don't post your IMEI here, publicly. Just curious what variant it says you have.
https://www.imeipro.info/
If you have V30+ US998 , then it's either native US998U or was formerly LS998U and converted to US998 by you or previous owner if you bought it used.
Neither AT&T H931 not Canada H933 have a native V30+, but I've seen H933 V30+ which were Frankenstein'ed.
ChazzMatt said:
If you Frankenstein'ed, I'm asking what your original variant is. Frankenstein is to convert North American variant to another, also called cross flashing.
Whereas " WTF" is bootloader unlock and installing TWRP. Some North American variants have to Frankenstein to US998 for fastboot flash commands. Then they can use WTF INSTRUCTIONS. But Frankenstein itself is not bootloader unlock, TWRP and root. It's just fully converting one variant to another. It ONLY works with the North American variants, except for T-Mobile H932.
_____
OK, so you were on LG US998 30b stock Pie successfully.
Put your IMEI into this database and tell me what it says? Don't post your IMEI here, publicly. Just curious what variant it says you have.
https://www.imeipro.info/
If you have V30+ US998 , then it's either native US998U or was formerly LS998U and converted to US998 by you or previous owner if you bought it used.
Neither AT&T H931 not Canada H933 have a native V30+, but I've seen H933 V30+ which were Frankenstein'ed.
Click to expand...
Click to collapse
Ahh, alrighty, I understand the difference now. So I had Frankenstein'ed to unlock my bootloader, then unlocked it with "WTF".
Also, the IMEI checker reported my device as a US998U V30+, which was what I bought it as used.
AkajiWins said:
Ahh, alrighty, I understand the difference now. So I had Frankenstein'ed to unlock my bootloader, then unlocked it with "WTF".
Also, the IMEI checker reported my device as a US998U V30+, which was what I bought it as used.
Click to expand...
Click to collapse
Merely downgrading to earlier firmware is not Frankenstein. Frankenstein is fully converting one variant to another. It takes on those different LTE bands, etc. Cross flashing AT&T H931 to US998 gives it CDMA bands the H931 doesn't have, different LTE bands, fastboot flash commands. Same with Frankenstein'ed H933. See screenshot.
If you already had US998 firmware and your IMEI check says it's a native US998U (V30+), then you didn't Frankenstein to US998. You already had US998 with fastboot flash commands. You just used LGUP to downgrade to early US998 Oreo for WTF bootloader unlock, TWRP installation and root and/or maybe you went to US998 Nougat at one point. But you were already US998. You weren't on LS998, AS998, H933, H931, VS996 firmware, at any point in time.
Why you are bootlooping on LOS-17 Android 10 ROMs, I don't know. You don't have former H931 or H933, and you said you were on US998 30b (Pie) when you tried to flash those ROMs.
ChazzMatt said:
Merely downgrading to earlier firmware is not Frankenstein. Frankenstein is fully converting one variant to another. It takes on those different LTE bands, etc. Cross flashing AT&T H931 to US998 gives it CDMA bands the H931 doesn't have, different LTE bands, fastboot flash commands. Same with Frankenstein'ed H933. See screenshot.
If you already had US998 firmware and your IMEI check says it's a native US998U (V30+), then you didn't Frankenstein. You already had US998 with fastboot flash commands. You just used LGUP to downgrade to early Oreo for WTF bootloader unlock, TWRP installation and root.
Why you are bootlooping on LOS-17 Android 10 ROMs, I don't know. You don't have former H931 or H933, and you said you were on US998 30b (Pie) when you tried to flash those ROMs.
Click to expand...
Click to collapse
Should I attempt to Frankenstein to a different variant then come back? I was going to try to use the fourth method that you linked to before to try to put myself on an actual US998.
AkajiWins said:
Should I attempt to Frankenstein to a different variant then come back? I was going to try to use the fourth method that you linked to before to try to put myself on an actual US998.
Click to expand...
Click to collapse
The problem with Method #4 is you are willingly converting to Canada H933. While that might get you back to US998 30b, it will then give you more difficulty in flashing LOS ROMs. You have to go through the tedious extra steps of former H931/H933.
ChazzMatt said:
The problem with Method #4 is you are willingly converting to Canada H933. While that might get you back to US998 30b, it will then give you more difficulty in flashing LOS ROMs. You have to go through the tedious extra steps of former H931/H933.
Click to expand...
Click to collapse
As someone who doesn't necessarily mind the extra preparation, would you recommend it for someone in my predicament? And is there any log file I can provide to hopefully help give more insight?
AkajiWins said:
As someone who doesn't necessarily mind the extra preparation, would you recommend it for someone in my predicament?
Click to expand...
Click to collapse
That's your decision. It should get you back to 30b. After that, for flashing ROMs, you'll have to follow the other instructions for H933 (since you will have converted to that, then converted back).
ChazzMatt said:
That's your decision. It should get you back to 30b. After that, for flashing ROMs, you'll have to follow the other instructions for H933 (since you will have converted to that, then converted back).
Click to expand...
Click to collapse
Though if I am to do that, would I still keep the bands I have at the moment or would I lose them when converting? Would I have to refflash my modem partition(s)?
AkajiWins said:
Though if I am to do that, would I still keep the bands I have at the moment or would I lose them when converting? Would I have to refflash my modem partition(s)?
Click to expand...
Click to collapse
The method is flash to H933 Nougat I believe, then flash back to US998. You don't stay on H933. You flash everything via LGUP Partition DL mode.
ChazzMatt said:
The method is flash to H933 Nougat I believe, then flash back to US998. You don't stay on H933.
Click to expand...
Click to collapse
Ah alright, I'll try that. So just to clarify, I'd flash over to an H933, then come back to a US998, and then install the 30b kdz, and that should hopefully fix my issues?
AkajiWins said:
Ah alright, I'll try that. So just to clarify, I'd flash over to an H933, then come back to a US998, and then install the 30b kdz, and that should hopefully fix my issues?
Click to expand...
Click to collapse
Yes. But read Method 4 carefully. Involves timing and buttons.
ChazzMatt said:
Yes. But read Method 4 carefully. Involves timing and buttons.
Click to expand...
Click to collapse
LGUP doesn't seem to recognize my phone as a H933 after flashing and rebooting back to download mode, but the phone seems to know it's one when I flash and it says what build it's on and what's being flashed.
EDIT 1: Reinstalling LGUP fixed that particular issue, so I'll have to restart the procedure just so it's as unobstructed as possible.
EDIT 2: Never mind, still the same strange occurrence that happened before. I'll try to move on and see if it'll still work.
Okay so, after a lot of trouble, everything seems to work. I ran Jett's Wifi Backup fix to fix the broken wifi on Havoc, along with the Haumea kernel, and now everything seems stable.
Thank you for your help!!
I guess I just had to keep doing the procedure until it stuck
Hi guys, I'm a bit lost too.
My phone is a V300S that is Frankensteined to US998 with V300S modem, bootloader unlocked and installed TWRP.
However i also faced the problem of installing Android 10 based roms causing bootloops, I've seen on the Custom ROMs page that i needed the lastest stock Pie blobs, which is what i have currently (30b)
Is this variant using a different way for custom ROMs? Or did i do something entirely wrong on Frankensteining?
Edit: silly me recently saw that i need to convert my V300S to H930, not US998... I guess I'll try that first
Update: well everything went south, now i can't go back to US99830b anymore, stuck at V300s Oreo. I guess I'll start everything over again, but if there are things or procedures i needed to know, please, any help will do