Title says it. I'm requesting a stock LGUP partition dump from an LG V30. Please provide one from version 20o or 20k. Preferrably unrooted, stock, minimum alterations, and NO 'FRANKENSTEIN' cross-flashed H932 devices! I'm going to test to see if a system dump from a T-Mobile H932 can allow me to unlock LTE band 71 on all LG V30 (JOAN) variants. I discovered I could unlock LTE band 12 on my Verizon VS996 -> USA OPEN US998 Frankenstein phone. Though I cross-flashed, I couldn't get LTE band 12. I fixed it by creating a flashable H931 (AT&T) zip from partitions I found online. Most importantly, flashing modem, modemst1, and modemst2 alone seems to have fixed my issue. I do realize doing this could brick my device, as the H932 has a different RSA key than all the other variants.
The issue: The 3 hidden LTE band selection menus (LG LTE Band Selection, TMO Only, and iot band selection) don't really enable all LTE bands that the V30 (JOAN) supports. Band 71 is for sure sabotaged on all devices but the H932, and the hidden menu doesn't seem to enable it. Similarly for me, no hidden menu could enable band 12 for me, maybe because I was coming from a Verizon VS996 (though this is a special case, no one else has reported this).
The fix: Flash working modem, modemst1, and modemst2 partitions from a working T-Mobile H932. OR flash working H932 modemst1 and modemst2 partitions only. OR flash working H932 system, boot, modem, modemst1 and modemst2 partitions.
*I've flashed an H932 modem before onto my Frankenstein phone without issue, and no bootloop. So maybe it is not RSA-locked...
Anyways, kindly upload your T-Mobile H932 dump (zipped). It can be around 8GB unzipped, and then 3.2GB zipped.
LGUP Install Procedure:
1. Download and install LG USB drivers (under USB Driver) here
2. Download and install LG UP 1.14.3 from here
3. Download .dll file for LG V30 here
4. Navigate to C:\Program Files (x86)\LG Electronics\LGUP\model
5. Create folder called "common" and unzip the .dll file inside of it.
LGUP Patch Procedure:
1. Extract (confirm replace, yes) LGUP+V30DLL_PATCHED.zip to C:\Program Files (x86)\LG Electronics\LGUP
2. Extract LGUP_common.dll in LGUP_common_DLL_V30_ALLVARIANTS.zip to C:\Program Files (x86)\LG Electronics\LGUP\model\common
3. Reboot computer
LGUP Dump Procedure:
1. Update software to latest H932 20o (check for system updates)
2. Turn off phone
3. Connect micro usb cable to computer
3. Hold volume up button and connect the usb cable
4. Open LGUP
5. Select DUMP
6. DON'T select partitions: userdata or data, and cache.
7. Click OK
8. Create a ZIP from all the partition dumps (should be around 30 files)
9. Upload ZIP to Google Drive or MEGA.
patato21 said:
Title says it. I'm requesting a stock LGUP partition dump from an LG V30. Please provide one from version 20o or 20k. Preferrably unrooted, stock, minimum alterations, and NO 'FRANKENSTEIN' cross-flashed H932 devices!
Click to expand...
Click to collapse
If you knew about the topic, you would know there's no such thing as Frankenstein H932. This is why they can't use WTF.
This is also why I doubt your statements in the other thread about LTE bands 12 and 13.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
If you knew about the topic, you would know there's no such thing as Frankenstein H932. This is why they can't use WTF. This is why I doubt your statements in the other thread about LTE bands 12 and 13.
Click to expand...
Click to collapse
It is possible to have a H932 -> US998 Frankenstein by merely flashing system and boot. Which definitely don't have an RSA key. Why would I have a reason to lie about my situation? It is not impossible for these two scenarios to happen.
patato21 said:
It is possible to have a H932 -> US998 Frankenstein by merely flashing system and boot. Which definitely don't have an RSA key. Why would I have a reason to lie about my situation? It is not impossible for these two scenarios to happen.
Click to expand...
Click to collapse
I wrote the instructions for Frankenstein and there's very little you can cross flash between the other North American variants and T-Mobile H932. Not enough to call it Frankenstein.
@runningnak3d is the expert on this, and I deferring him. (This below is quote from @runningnak3d, but some apps don't show the quote reference. So view in web browser.)
__________
https://forum.xda-developers.com/showpost.php?p=76319892&postcount=34
runningnak3d said:
Here is the list of all files that are flashed in a KDZ that are signed with the RSA cert. If just ONE of these doesn't match the key in your CPU, you will probably have a 9008 brick. Some just won't load, and your phone won't work until you flash the proper KDZ (for example modem), but the fact of the matter is -- it is NOT possible to crossflash ANY of these files IF the RSA key in your CPU doesn't match the signature on these files:
Code:
ablbak.image
abl.image
apdp.image
cmnlib64bak.image
cmnlib64.image
cmnlibbak.image
cmnlib.image
devcfgbak.image
devcfg.image
hypbak.image
hyp.image
keymasterbak.image
keymaster.image
modem.image
msadp.image
pmicbak.image
pmic.image
rpmbak.image
rpm.image
storsecbak.image
storsec.image
tzbak.image
tz.image
xbl2.image
xbl.image
If you have an unlocked bootloader, this is the list of files that you can flash without worrying about the RSA key:
Code:
boot.image
recoverybak.image
recovery.image
lafbak.image
laf.image
system.image
userdata.image
If you do not have an unlocked bootloader, and you flash one of the above files WITHOUT flashing the corresponding abl, you will bootloop and never be able to fix your phone. So, if you have a locked bootloader, then you must flash ALL of the partitions listed as being checked by the RSA key, and ALL of the partitions listed here. If you don't -- you will not have a working phone.
And finally, this is the list of files that you can cross flash that aren't checked by the RSA key in the CPU nor dm-verity:
Code:
cache.image
carrier.image
drm.image
eksst.image
encrypt.image
eri.image
factory.image
ftm.image
grow.image
keystore.image
logfs.image
misc.image
mpt.image
operatorlogging.image
persist.image
pstore.image
qni.image
raw_resourcesbak.image
raw_resources.image
rct.image
sec.image
sns.image
srtc.image
ssd.image
Click to expand...
Click to collapse
_____________
1) the whole point of Frankenstein is to carrier unlock the phone and/or get fastboot flash commands to unlock the bootloader. Frankenstein is done BEFORE bootloader unlock. The two partitions you mention require bootloader unlock. Even if theoretically possible, no one is going to flash those from H932 onto their carrier unlocked, bootloader unlocked phone for any reason whatsoever. Why would they? They already have what they need , and it would only potentially mess up their phone in many different ways.
2) There's tons of Frankensteined North America variants on T-mobile (AS998, VS996, H931, H933 converted to US998) - - including Wi-Fi calling, which I'm pretty sure requires LTE band 12 - - and no one else except you has said they can't get it? I am glad you fixed your problem, but as you mentioned in your post, only you have reported it.
I say if you DL partition with dev patched LGUP, it will overwrite the partitions, including modem partitions. I can't see how your modem partitions stayed as VS996.
patato21 said:
Band 71 is for sure sabotaged on all devices but the H932, and the hidden menu doesn't seem to enable it.
Click to expand...
Click to collapse
If you can bring LTE band 71 to other V30 models, then more power to you.
We aren't disagreeing about that. I hope you succeed.
ChazzMatt said:
I wrote the instructions for Frankenstein and there's very little you can cross flash. Not enough to call it Frankenstein.
@runningnak3d is the expert on this.
All I know is there's tons of Frankensteined North America variants on T-mobile - - including Wi-Fi calling which I'm pretty sure requires LTE band 12 - - and no one else except you has said they can't get it.
I am glad you fixed your problem, but as you mentioned in your post, only you have reported it.
I say it you DL partition with dev patched LGUP, if will overwrite the partitions, including modem partitions. I can't see how the modem partitions are exceptions.
Click to expand...
Click to collapse
Ironically I appear to be stuck on band 2 >.> LS998 > US998
me2151 said:
Ironically I appear to be stuck on band 2 >.> LS998 > US998
Click to expand...
Click to collapse
Did you use the hidden menu to choose LTE bands? I made that mistake, it sticks on the last one you choose. I started a thread about it and there's a solution.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Did you use the hidden menu to choose LTE bands? I made that mistake, it sticks on the last one you choose. I started a thread about it and there's a solution.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Not to hijack the thread, can you try this file?
I get Dolby in the LG music app, but not the actual icon.
I'm guessing that the same reasons the different v20 got real Dolby applies to the v30 as well.
Sent from my LG-H932 using XDA Labs
Edit, not my work
https://forum.xda-developers.com/v20/themes/mod-stock-lg-music-app-dolby-sound-fx-t3812459
ChazzMatt said:
snip
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
As you can see, this is how the stock file looks.
Sent from my LG-H932 using XDA Labs
ChazzMatt said:
Did you use the hidden menu to choose LTE bands? I made that mistake, it sticks on the last one you choose. I started a thread about it and there's a solution.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Nope never used the hidden menu
@potato21 If you want the H932 modem just download one of the H932 TWRP flashable zips and extract it. It is most definitely RSA signed, however, the hole in the US998 abl that allows the WTF unlock method to work may also break the boot chain of trust. In other words .. yes, you may be able to flash the H932 modem. That is what sucks about the fact that abl is encrypted .. can't decompile to check.
As for getting a dump of modemst1 and 2 .. someone will have to dump them with LG UP, or if they are rooted, just boot to TWRP and use dd.
To anyone willing to do it .. you IMEI is contained in fsg, so you are safe sending st1 and st2.
-- Brian
runningnak3d said:
@potato21 If you want the H932 modem just download one of the H932 TWRP flashable zips and extract it. It is most definitely RSA signed, however, the hole in the US998 abl that allows the WTF unlock method to work may also break the boot chain of trust. In other words .. yes, you may be able to flash the H932 modem. That is what sucks about the fact that abl is encrypted .. can't decompile to check.
As for getting a dump of modemst1 and 2 .. someone will have to dump them with LG UP, or if they are rooted, just boot to TWRP and use dd.
To anyone willing to do it .. you IMEI is contained in fsg, so you are safe sending st1 and st2.
-- Brian
Click to expand...
Click to collapse
Modem is installable. no rsa on it(that works properly) however it fails hardware checks. so it wont start. It might be possible to hex some changes in to allow it to start on the other models though.
me2151 said:
Modem is installable. no rsa on it(that works properly) however it fails hardware checks. so it wont start. It might be possible to hex some changes in to allow it to start on the other models though.
Click to expand...
Click to collapse
The modem firmware is most certainly RSA signed, and *usually* verified by abl in the boot chain of trust. If you can flash the H932 modem on a WTF rooted phone, that means that whatever eff-up that LG did with that abl broke the boot chain of trust:
Code:
binwalk -e modem.img --dd="x509"
openssl asn1parse -inform DER -in 1D2A8.crt
0:d=0 hl=4 l=1164 cons: SEQUENCE
4:d=1 hl=4 l= 884 cons: SEQUENCE
8:d=2 hl=2 l= 3 cons: cont [ 0 ]
10:d=3 hl=2 l= 1 prim: INTEGER :02
13:d=2 hl=2 l= 3 prim: INTEGER :0E1CA0
18:d=2 hl=2 l= 13 cons: SEQUENCE
20:d=3 hl=2 l= 9 prim: OBJECT :sha256WithRSAEncryption
<snip>
499:d=5 hl=2 l= 3 prim: OBJECT :organizationalUnitName
504:d=5 hl=2 l= 25 prim: UTF8STRING :01 0000000000000004 SW_ID
So, that opens up a world of possibilities if LG screwed up and broke the chain of trust and you are able to flash H932 firmware onto other devices. You wouldn't be able to flash xbl or abl (obviously), but other than that you could convert a phone to an H932.
Remember the PBL verifies XBL, and XBL verifies ABL. If the chain of trust stops there ... the LG V30 may be the most awesome phone currently in production.
-- Brian
do you still need the files?
DSTNMZ said:
do you still need the files?
Click to expand...
Click to collapse
You do NOT want to send someone that complete dump. Sending modemst1 and modemst2 is OK, but there are a lot of files from a full dump that contain info that is specific to your phone -- for example (from your dump) fsg_COM5 contains your IMEI, serial number, and other info. misc_COM5 contains your serial number, and (while not very important) your bt and wifi MAC addresses.
-- Brian
DSTNMZ said:
do you still need the files?
Click to expand...
Click to collapse
I would like modem,modemst1 and modemst2 please
runningnak3d said:
You do NOT want to send someone that complete dump. Sending modemst1 and modemst2 is OK, but there are a lot of files from a full dump that contain info that is specific to your phone -- for example (from your dump) fsg_COM5 contains your IMEI, serial number, and other info. misc_COM5 contains your serial number, and (while not very important) your bt and wifi MAC addresses.
-- Brian
Click to expand...
Click to collapse
I would not send everything, I put that image as a sample to see what I had obtained, I would only send the parts that are required, and thanks to you now I know that I should not send those files that you mention (fsg_COM5 and misc_COM5) , I am sorry the English language is not my language native in case it does not make sense what I say
---------- Post added at 03:31 PM ---------- Previous post was at 03:23 PM ----------
me2151 said:
I would like modem,modemst1 and modemst2 please
Click to expand...
Click to collapse
there you have it
https://drive.google.com/file/d/1MxbCBGbujzWWnOg35ePk35KVh5sabJ4h/view?usp=sharing
DSTNMZ said:
I would not send everything, I put that image as a sample to see what I had obtained, I would only send the parts that are required, and thanks to you now I know that I should not send those files that you mention (fsg_COM5 and misc_COM5) , I am sorry the English language is not my language native in case it does not make sense what I say
---------- Post added at 03:31 PM ---------- Previous post was at 03:23 PM ----------
there you have it
https://drive.google.com/file/d/1MxbCBGbujzWWnOg35ePk35KVh5sabJ4h/view?usp=sharing
Click to expand...
Click to collapse
Thanks
EDIT: Tmobile modemst1 and st2 work just fine on frankenstein
me2151 said:
Thanks
EDIT: Tmobile modemst1 and st2 work just fine on frankenstein
Click to expand...
Click to collapse
So you have working band 71 now?
-- Brian
runningnak3d said:
So you have working band 71 now?
-- Brian
Click to expand...
Click to collapse
No idea. I dont have band 71 in my area nor am i on stock to try to force it
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 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.
I've been getting the Android update notice the past few days. Regardless of what gets frozen in TiBu it doesn't seem to do the trick.
I've had some serious issues trying to update my phone via using LGUP to flash a updated US998 KDZ, and then editing apn's to allow service thru Sprint, who is my carrier. I am of course, frankensteined to a US998, then back to a LS998 using @JWnSC's Sprint 20a zip file.
Can I flash the US998 KDZ via LGUP, and not flash the modem files, or recovery partition? Then flash magisk, no_verity, rctd in TWRP? Will this allow me to keep my phone up to date while staying on Sprint?
can someone idiot check my procedure that I'm going to attempt, if the previous question didn't pan out, please?
Need to back up my modem/modemst1/modemst2 from my currently known good setup. Place those on SD card.
Flash US998 KDZ, skipping recovery partition.
Boot to TWRP.
flash all 3 modem files (modem, modemst1, modemst2) as an image file via TWRP.
Boot phone. Setup via wifi.
Edit apn's that I copied down earlier.
Reboot.
Disco?
I'm apparently a bit of a Luddite when it comes to doing things other than via 0din.
elijah420 said:
Need to back up my modem/modemst1/modemst2 from my currently known good setup. Place those on SD card.
Flash US998 KDZ, skipping recovery partition.
Boot to TWRP.
flash all 3 modem files (modem, modemst1, modemst2) as an image file via TWRP.
Boot phone. Setup via wifi.
Edit apn's that I copied down earlier.
Reboot.
Disco?
I'm apparently a bit of a Luddite when it comes to doing things other than via 0din.
Click to expand...
Click to collapse
The steps you listed so far would work to keep TWRP, but you would need re-flash the three files you flashed when you first rooted, since you are going back to stock (except keeping TWRP): the no encryption file, the no root check file and Magisk.
OR
You can also flash the 20D US998 TWRP-flashable zip file that @westwood24 created for us.
After that, you still need to flash Magisk -- but he already has the no encryption file and no root check file built into the image.
[ROM][US998][Stock][OREO] LG-US998 20D ROM
You would then do the other stuff you mention about Sprint to get those LTE bands back...
Dont have a clue.
CAN ANYONE POINT ME IN THE RIGHT DIRECTION TO GET A LG V30 THINQ VERIZON FLASHED TO BOOST MOBILE and not loose 4glte and most of the features?
Used the Frankenstein method to root my ls998 as well. Flashed back to the ls998 rom. I keep getting update notifications as well, is there a way to flash it in twrp? I tried the us998 rom, but didn't have luck getting my service/lte working.
Justwinbaby43 said:
CAN ANYONE POINT ME IN THE RIGHT DIRECTION TO GET A LG V30 THINQ VERIZON FLASHED TO BOOST MOBILE and not loose 4glte and most of the features?
Click to expand...
Click to collapse
Boost is Sprint minor leagues, right? Problem is does Boost accept Bring Your Own Phone? Because Sprint won't accept any V30 not ID'ed as their own LS998, and won't even let Sprint MNVOs accept US998 V30. So, people have to first activate their LS998 on Sprint, then flash to US998 (Frankenstein) for bootloader unlock, then change back parts to get all the Sprint LTE bands. It's been done by many on Sprint -- but you are throwing in a new wrinkle with Boost. Also, you are starting out with Verizon VS996.
Would be better to start with LS998 (mint on eBay for $315 last time I checked) or choose another provider.
Only phones on a list sent to Boost Mobile from Sprint are acceptable Sprint branded phones that can be reskewed for Boost Mobile. Other then that you would need to buy a Boost Mobile branded phone.
Could you post a snapshot of all your apn settings for Sprint? I've updated my phone from the LS998 to the US998 and I just cant seem to get my apn settings right.
As of right now, I finally got 4g lte (albeit slow, which could just be the crappy sprint towers near me). But my text messages are acting really weird.
As of right now I'm only receiving text messages when I receive phone calls, and I am not receiving voice mails.
I can send out text messages just fine though. This apn part is kicking my butt.
@Klenon
Bottom of op or you can flash Sprint system
https://forum.xda-developers.com/lg-v30/how-to/us998-to-ls998-sprint-lte-root-t3802310
Okay, thanks for the heads up. I'll try to follow that tomorrow and let you know how it goes.
error post
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