Related
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?
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!
I have a LGv30 VS996 that has been bootloader unlocked using WTF and is currently flashed and working great with a US998 stock firmware.
I would like to use VOLTE/VOWIFI but it is not showing up as an option for me.
My local region (I'm in Asia) uses the H903DS variant of LGv30 and they have a stock ROM for that device which I'm hoping will enable the VOLTE/VOWIFI options.
My question is, will that work? Are VS996/US998 similar enough to H903DS that I can cross flash?
skippybosco said:
I have a LGv30 VS996 that has been bootloader unlocked using WTF and is currently flashed and working great with a US998 stock firmware.
I would like to use VOLTE/VOWIFI but it is not showing up as an option for me.
My local region (I'm in Asia) uses the H903DS variant of LGv30 and they have a stock ROM for that device which I'm hoping will enable the VOLTE/VOWIFI options.
My question is, will that work? Are VS996/US998 similar enough to H903DS that I can cross flash?
Click to expand...
Click to collapse
Uhmmm... You can't fully CONVERT any North American phone to any H930* phone like Frankenstein can do to each other with most North American variants, but you can flash parts of the H930DS software to VS996 via Dev Patched LGUP in Partition DL mode. However, you have to OMIT certain partitions, like modems and XBL.
People have done this to flash EU H930 firmware over US998 to get East European languages, etc. Every time you flash an updated H930* KDZ, you would have to remember to omit those partitions. You would NOT be changing any bands like with Frankenstein.
See this guide, but change to H930DS KDZ instead of EU H930:
https://forum.xda-developers.com/lg-v30/how-to/guide-how-to-convert-us998-20h-to-h930-t3956182
Mrxyzl said:
Select all partition except the following 3: modem, xbl, xbl 2, click Ok and accept partition changes
Let it complete and restart, if you stuck on LG logo, try reboot again, it will boot completely
Result: H930 30B on a US998 with working network and stuff working (testing on GSM network outside US only, cant confirm Vowifi, VoLTE or any other netwrok stuff.)
Click to expand...
Click to collapse
Read that last sentence.
Good luck.
My V30 doesn't seem to enjoy being flashed with Android 10, as it bootloops no matter what ROM I decide to use (Lineage, Havoc, Pixel Experience), and now I'm thoroughly stumped on what to do, as I can't find a fix for this issue. My phones bootloader is unlocked via Frankenstein, and I've used the method of flashing over 10d with 30b and having no luck. I've recently come across a post that said to attempt trying 20b to 30b, which I'll try as a last effort to get this working, but I'd still appreciate advice on what to do. Whether it be this last method, a modification of it, or just something else entirely, I'd be forever grateful for the help.
If you need more information, feel free to ask and I'll provide to the best of my ability.
AkajiWins said:
My V30 doesn't seem to enjoy being flashed with Android 10, as it bootloops no matter what ROM I decide to use (Lineage, Havoc, Pixel Experience), and now I'm thoroughly stumped on what to do, as I can't find a fix for this issue. My phones bootloader is unlocked via Frankenstein.
Click to expand...
Click to collapse
So you Frankensteined to US998, then unlocked the bootloader via WTF exploit. What variant did you start with?
AkajiWins said:
I've used the method of flashing over 10d (Nougat/Android 7) with 30b (Pie/Android 9) and having no luck. I've recently come across a post that said to attempt trying 20b (early Oreo) to 30b, which I'll try as a last effort to get this working, but I'd still appreciate advice on what to do. Whether it be this last method, a modification of it, or just something else entirely, I'd be forever grateful for the help.
If you need more information, feel free to ask and I'll provide to the best of my ability.
Click to expand...
Click to collapse
1) You need stock Android 9 (Pie) as a base before flashing any LOS-17 (Android 10) ROMs. But you seem to know that.
There are several methods to update to to Pie US998. See US998 Pie KDZ thread, post #2 and FOUR MORE WORKAROUND in post #6.
2) What variant did you start with? If you have former AT&T H931 or Canada H933, you'll need to do additional prep steps before installing any LOS custom ROMs.
Of course, you've read the V30 custom ROMs FAQ -- before you even unlocked your bootloader -- right? It tells all this and conveys other important information. This FAQ is prominently linked in the WTF instructions, with suggestion to read first, then come come back to finish unlocking bootloader...
V30 CUSTOM ROMS FAQ
https://forum.xda-developers.com/showpost.php?p=79459374&postcount=2
ChazzMatt said:
So you Frankensteined to US998, then unlocked the bootloader via WTF exploit. What variant did you start with?
1) You need stock Android 9 (Pie) as a base before flashing any LOS-17 (Android 10) ROMs. But you seem to know that.
There are several methods to update to to Pie US998. See US998 Pie KDZ thread, post #2 and FOUR MORE WORKAROUND in post #6.
2) What variant did you start with? If you have former AT&T H931 or Canada H933, you'll need to do additional prep steps before installing any LOS custom ROMs.
Of course, you've read the V30 custom ROMs FAQ -- before you even unlocked your bootloader -- right? It tells all this and conveys other important information. This FAQ is prominently linked in the WTF instructions, with suggestion to read first, then come come back to finish unlocking bootloader...
V30 CUSTOM ROMS FAQ
https://forum.xda-developers.com/showpost.php?p=79459374&postcount=2
Click to expand...
Click to collapse
Yes, I did read through the FAQ before and after unlocking. My variant is the US998U/V30+, which is why I'm a bit confused. The US998 and US998U are identical, aside from storage capacity, right?
I was following one of the guides you posted that stated:
ChazzMatt said:
So for installing the KDZ, I suggest FIRST downgrading to US998 Nougat 10d via Partition DL mode, Master Reset, then Refurbish to US998 Pie KDZ. Here are the steps...
If you have problems flashing this US998 Pie 30b KDZ, see post #6 for FOUR more workaround methods proven to work for some people.
You should probably use this method (DOWNGRADE to NOUGAT first) even if you have TWRP installed. Then reinstall TWRP again after successfully updating to Pie.
KDZ INSTALLATION INSTRUCTIONS
0) Turn off phone, manually go into Download mode before opening Dev Patched LGUP.
1) Using Dev Patched LGUP from THIS thread, flash US998 10d Nougat KDZ via Dev Patched LGUP using Partition DL mode. Select ALL partitions.
2) Master Reset. This is NOT Factory Reset.
3) Boot up to Welcome screen. Turn off phone, manually go back into Download mode.
4) Flash US998 30b Pie KDZ via Dev Patched LGUP using Refurbish mode.
5) Master Reset. This is NOT Factory Reset.
If you did not unlock your bootloader before doing this, then you bootloader is still locked -- because that's what you want. Finished. Set up your phone.
If you had unlocked bootloader before doing all this, you will still have it. Boot to ADB, and PLEASE follow these instructions for re-install TWRP and root!!
Click to expand...
Click to collapse
So that's what I had done a few days ago, but that's also when my problems arose. I was on the TWRP flashable kdz of 30b for a month or two now after Frankensteining it, but wanted to try out some 10 ROMS, but attempting to flash those ROMs was when I started having issues. Flashing the stock US998 kdzs didn't cause issues, the 30b zip I had been running daily wasn't weird, and the md5s for all the files downloaded matched what was provided as correct. That's why I'm a bit stumped, since I believe I followed all the guides I've looked at to make things work correctly, but this one part is giving me a hard time.
I will try those other four methods, since I don't believe to have seen them yet. I will provide an edit to this post after trying them, thank you.
AkajiWins said:
Yes, I did read through the FAQ before and after unlocking. My variant is the US998U/V30+, which is why I'm a bit confused. The US998 and US998U are identical, aside from storage capacity, right?
I was following one of the guides you posted that stated:
So that's what I had done a few days ago, but that's also when my problems arose. I was on the TWRP flashable kdz of 30b for a month or two now after Frankensteining it, but wanted to try out some 10 ROMS, but attempting to flash those ROMs was when I started having issues. Flashing the stock US998 kdzs didn't cause issues, the 30b zip I had been running daily wasn't weird, and the md5s for all the files downloaded matched what was provided as correct. That's why I'm a bit stumped, since I believe I followed all the guides I've looked at to make things work correctly, but this one part is giving me a hard time.
I will try those other four methods, since I don't believe to have seen them yet. I will provide an edit to this post after trying them, thank you.
Click to expand...
Click to collapse
If you Frankenstein'ed, I'm asking what your original variant is. Frankenstein is to convert North American variant to another, also called cross flashing.
Whereas " WTF" is bootloader unlock and installing TWRP. Some North American variants have to Frankenstein to US998 for fastboot flash commands. Then they can use WTF INSTRUCTIONS. But Frankenstein itself is not bootloader unlock, TWRP and root. It's just fully converting one variant to another. It ONLY works with the North American variants, except for T-Mobile H932.
_____
OK, so you were on LG US998 30b stock Pie successfully.
Put your IMEI into this database and tell me what it says? Don't post your IMEI here, publicly. Just curious what variant it says you have.
https://www.imeipro.info/
If you have V30+ US998 , then it's either native US998U or was formerly LS998U and converted to US998 by you or previous owner if you bought it used.
Neither AT&T H931 not Canada H933 have a native V30+, but I've seen H933 V30+ which were Frankenstein'ed.
ChazzMatt said:
If you Frankenstein'ed, I'm asking what your original variant is. Frankenstein is to convert North American variant to another, also called cross flashing.
Whereas " WTF" is bootloader unlock and installing TWRP. Some North American variants have to Frankenstein to US998 for fastboot flash commands. Then they can use WTF INSTRUCTIONS. But Frankenstein itself is not bootloader unlock, TWRP and root. It's just fully converting one variant to another. It ONLY works with the North American variants, except for T-Mobile H932.
_____
OK, so you were on LG US998 30b stock Pie successfully.
Put your IMEI into this database and tell me what it says? Don't post your IMEI here, publicly. Just curious what variant it says you have.
https://www.imeipro.info/
If you have V30+ US998 , then it's either native US998U or was formerly LS998U and converted to US998 by you or previous owner if you bought it used.
Neither AT&T H931 not Canada H933 have a native V30+, but I've seen H933 V30+ which were Frankenstein'ed.
Click to expand...
Click to collapse
Ahh, alrighty, I understand the difference now. So I had Frankenstein'ed to unlock my bootloader, then unlocked it with "WTF".
Also, the IMEI checker reported my device as a US998U V30+, which was what I bought it as used.
AkajiWins said:
Ahh, alrighty, I understand the difference now. So I had Frankenstein'ed to unlock my bootloader, then unlocked it with "WTF".
Also, the IMEI checker reported my device as a US998U V30+, which was what I bought it as used.
Click to expand...
Click to collapse
Merely downgrading to earlier firmware is not Frankenstein. Frankenstein is fully converting one variant to another. It takes on those different LTE bands, etc. Cross flashing AT&T H931 to US998 gives it CDMA bands the H931 doesn't have, different LTE bands, fastboot flash commands. Same with Frankenstein'ed H933. See screenshot.
If you already had US998 firmware and your IMEI check says it's a native US998U (V30+), then you didn't Frankenstein to US998. You already had US998 with fastboot flash commands. You just used LGUP to downgrade to early US998 Oreo for WTF bootloader unlock, TWRP installation and root and/or maybe you went to US998 Nougat at one point. But you were already US998. You weren't on LS998, AS998, H933, H931, VS996 firmware, at any point in time.
Why you are bootlooping on LOS-17 Android 10 ROMs, I don't know. You don't have former H931 or H933, and you said you were on US998 30b (Pie) when you tried to flash those ROMs.
ChazzMatt said:
Merely downgrading to earlier firmware is not Frankenstein. Frankenstein is fully converting one variant to another. It takes on those different LTE bands, etc. Cross flashing AT&T H931 to US998 gives it CDMA bands the H931 doesn't have, different LTE bands, fastboot flash commands. Same with Frankenstein'ed H933. See screenshot.
If you already had US998 firmware and your IMEI check says it's a native US998U (V30+), then you didn't Frankenstein. You already had US998 with fastboot flash commands. You just used LGUP to downgrade to early Oreo for WTF bootloader unlock, TWRP installation and root.
Why you are bootlooping on LOS-17 Android 10 ROMs, I don't know. You don't have former H931 or H933, and you said you were on US998 30b (Pie) when you tried to flash those ROMs.
Click to expand...
Click to collapse
Should I attempt to Frankenstein to a different variant then come back? I was going to try to use the fourth method that you linked to before to try to put myself on an actual US998.
AkajiWins said:
Should I attempt to Frankenstein to a different variant then come back? I was going to try to use the fourth method that you linked to before to try to put myself on an actual US998.
Click to expand...
Click to collapse
The problem with Method #4 is you are willingly converting to Canada H933. While that might get you back to US998 30b, it will then give you more difficulty in flashing LOS ROMs. You have to go through the tedious extra steps of former H931/H933.
ChazzMatt said:
The problem with Method #4 is you are willingly converting to Canada H933. While that might get you back to US998 30b, it will then give you more difficulty in flashing LOS ROMs. You have to go through the tedious extra steps of former H931/H933.
Click to expand...
Click to collapse
As someone who doesn't necessarily mind the extra preparation, would you recommend it for someone in my predicament? And is there any log file I can provide to hopefully help give more insight?
AkajiWins said:
As someone who doesn't necessarily mind the extra preparation, would you recommend it for someone in my predicament?
Click to expand...
Click to collapse
That's your decision. It should get you back to 30b. After that, for flashing ROMs, you'll have to follow the other instructions for H933 (since you will have converted to that, then converted back).
ChazzMatt said:
That's your decision. It should get you back to 30b. After that, for flashing ROMs, you'll have to follow the other instructions for H933 (since you will have converted to that, then converted back).
Click to expand...
Click to collapse
Though if I am to do that, would I still keep the bands I have at the moment or would I lose them when converting? Would I have to refflash my modem partition(s)?
AkajiWins said:
Though if I am to do that, would I still keep the bands I have at the moment or would I lose them when converting? Would I have to refflash my modem partition(s)?
Click to expand...
Click to collapse
The method is flash to H933 Nougat I believe, then flash back to US998. You don't stay on H933. You flash everything via LGUP Partition DL mode.
ChazzMatt said:
The method is flash to H933 Nougat I believe, then flash back to US998. You don't stay on H933.
Click to expand...
Click to collapse
Ah alright, I'll try that. So just to clarify, I'd flash over to an H933, then come back to a US998, and then install the 30b kdz, and that should hopefully fix my issues?
AkajiWins said:
Ah alright, I'll try that. So just to clarify, I'd flash over to an H933, then come back to a US998, and then install the 30b kdz, and that should hopefully fix my issues?
Click to expand...
Click to collapse
Yes. But read Method 4 carefully. Involves timing and buttons.
ChazzMatt said:
Yes. But read Method 4 carefully. Involves timing and buttons.
Click to expand...
Click to collapse
LGUP doesn't seem to recognize my phone as a H933 after flashing and rebooting back to download mode, but the phone seems to know it's one when I flash and it says what build it's on and what's being flashed.
EDIT 1: Reinstalling LGUP fixed that particular issue, so I'll have to restart the procedure just so it's as unobstructed as possible.
EDIT 2: Never mind, still the same strange occurrence that happened before. I'll try to move on and see if it'll still work.
Okay so, after a lot of trouble, everything seems to work. I ran Jett's Wifi Backup fix to fix the broken wifi on Havoc, along with the Haumea kernel, and now everything seems stable.
Thank you for your help!!
I guess I just had to keep doing the procedure until it stuck
Hi guys, I'm a bit lost too.
My phone is a V300S that is Frankensteined to US998 with V300S modem, bootloader unlocked and installed TWRP.
However i also faced the problem of installing Android 10 based roms causing bootloops, I've seen on the Custom ROMs page that i needed the lastest stock Pie blobs, which is what i have currently (30b)
Is this variant using a different way for custom ROMs? Or did i do something entirely wrong on Frankensteining?
Edit: silly me recently saw that i need to convert my V300S to H930, not US998... I guess I'll try that first
Update: well everything went south, now i can't go back to US99830b anymore, stuck at V300s Oreo. I guess I'll start everything over again, but if there are things or procedures i needed to know, please, any help will do
Good day everyone, I'm new here so i hope i'm posting this right
This month i got an LG V30 V300S (korean variant), it was supposed to be H930 but they sent me this one instead, it didn't bother me much at first since the phone supports my country's frequency and XDA still supports the korean variant V30s, and I can't return the item too cuz of pandemic.
I came from the LG V20 so I'm quite familiar about cross flashing, but even before that i still did a little reading regarding on unlocking and rooting the phone on the V30 XDA thread (kind of easier than the V20 tbh).
The first thing i did was unlock and root the phone, installed TWRP and installed V300S firmware
(Based from here: https://forum.xda-developers.com/lg-v30/how-to/korean-variant-bootloader-unlock-root-t3804505)
It was ok at first, but now i decided to cross flash to US998 30b (Pie) via TWRP because V300 firmware is full of bloatware , and i stayed there for a few days.
Now i was wondering of installing Custom ROMs on the phone, it was a messy thing for me to understand, but as far as i knew since i want to install Android 10 based roms (Havoc OS), i needed Stock pie blobs.... Unfortunately it didn't work, i ended up in a bootloop, so i went back to US998 30b again.
After a while, i wondered that maybe the whole crossflashing is wrong? So i backed up the phone and flashed an H930 31a instead, but has no signal
Previously i can just easily bring back the modem using backed up V300S modem via LGUP or TWRP, but this time it didn't work, i also picked an older version (H930 30q) to match my phone's modem version, still no avail
And even disregarding the signal, i attempted to flash the custom rom again... Still bootloop
So I gave up at this point, and decided to go back to US998 30b, but this time i can't go back to US998 anymore, it also bootloops
I don't know what i did wrong now, i just followed the same instructions.
V300s > H930 > unlock > TWRP > US998 (TWRP)
Only difference on this one is i no longer flashed V300 kdz cuz i don't have one
So now I'm stuck at V300s_21e_Oreo cuz it's the only ROM that worked
I know I'm doing something wrong here, but due to a lot of procedures i have done I don't know where to start anymore, the phone is fully working with signal right now, but it lags on this ROM, US998 30b was way snappier
Sorry for the long post, I'm just desperate
Any help or suggestions will do.
Update: managed to go back to US998 Stock pie (30b) no idea how, 4G is painfully slow but i guess this will do for now