Develop Bugs

Was on oreo and did flash all to 7.1 by mistake.

So I was on Oreo and accidentally flashed back to 7.1.
Didn't brick it but now it doesn't recognize my sim even after flashing back to Oreo.
I tried to fastboot the tmo baseband but no luck there.
Anyone run across this or have any suggestions?

That was one of the 1st thing I ran across in the Oreo update thread. With development just really getting fired up I'll be surprised if you find a fix. If. I was you I would flash the mod that hides the unlocked bootloader warning and take it to TMobile. It's only a 5 dollor charge for defective devices. I've returned a total brick before.

So I am on the same board. The problem is I'm in UK and I cant claim warranty repair. Also my warranty was void in December soon when I generated bootloader unlock key.
SO what have I tried so far?
Hard brick bootloader to state when it is Qualcomm loader- only blank flash and Oreo Flash All is able to bring it back to live.
Ive also tried boot from B slot in twrp but it looks like my B partition is messed up. Fastboot will show red warning about no flashable A/B slot and only oreo flash can get it back to boot because it will oem lock itself.
When I get back fully on unlocked bootloader to 7.1.1 I cant update via adb sideload or update menu in settings. Both will fail.
Sim looks like it is detected on start but when taken out and slided back in it wont show up.
I have QCN area backed up with nv data but it wont help me.
Please note when boot is bricked oreo flash all will flash it on locked bootloader and will not show warning screen at all about botloader. However I was unable to boot to recovery from that point so I had to unlock it and flash 7.1.1 then oreo again.
So if someone could do nandroid backup of clear not set up rom it would be great. I can try restore it. I dont even know if twrp is able to do backup on A/B device.
Also if someone could read NV data from phone and share it ( from phone with working radio of course) would be really appreciated.

Can someone PM me NV backup? I need urgently qcn file. I think my hw partition is messed up. Please don't share it in this post as it can contain IMEI.

this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!

byt3b0mb said:
this is what i did, and why there is a giant post in caps in the thread that says not to do this. You essentially end up with a bootloader mismatch which hoses the radio. the only solution is a replacement.
and DONT DOWNGRADE !!!
Click to expand...
Click to collapse
Sorry but warning isn't clear. I did not enjoy Oreo and was looking for unlock method.
Also bootloader match to my current Oreo rom and radio but still no sim detected so I think it is hw partition messed up. When I flash retail Oreo on it bootloader just change itself to retail Oreo version. Still no sim.
Device is useable as paperweight with WiFi

I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0

Everything about the phone works 100% except the Sim slot. It's like it can't read the Sim. It knows there is a sim in, but it can't access it.
On Oreo oem retail version.

donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.

robdevil said:
I'm happy to stay on 8 but need my sim get back to life. All works fine except SIM card is not detected.
My phone boot as normal. When downgraded it won't accept ota's. It won't install it via sideload too. SIM card remain undetected no matter what rom and what version( T-Mobile, retail, etc) when I try to boot from slot B via twrp it won't boot. It will show bootloader screen with unbootable a/B partition.
Click to expand...
Click to collapse
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts

Kaesberg said:
i got a script that was able to get my tmobile variant back up and running on any version i installed please give this a try and let me know.
just copy all this to the platform tools drectory ans double click the oem flash.bat the oem lock.bat will re-lock your boot-loader if you want that as well.
pm me for a link to my drive since im still under 10 posts
Click to expand...
Click to collapse
pm sent. i could use this

Please let us know if it works

Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/

breakerfall said:
Not OP, or guy with a link, but I did a similar bad thing and ended up on the retail Oreo without working SIM. What I did was take the modem file (the one that you fastboot flash to modem) from the tmo oreo zip and replaced the modem file in the retail oreo zip with the tmo one -- just change the name of the tmo modem file to the one that comes in the retail oreo zip and then run the retail flashall.
Still no way to get the latest tmo update that fixes some volte issues, though. Since I purchased within 14 days, I just added insurance and will probably end up drowning the phone to replace it... unless someone has a better idea. :/
Click to expand...
Click to collapse
Where did you get this modem?

mattlowry said:
Where did you get this modem?
Click to expand...
Click to collapse
from the tmo oreo zip here (bottom of the OP):
https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932
it's the NON-HLOS file
this is the retail oreo:
https://forum.xda-developers.com/showpost.php?p=75250794&postcount=82
I swapped the NONHLOS file from the tmo oreo into the retail oreo and I currently have working tmo service/SIM on the retail (tmo-less) oreo

donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
My Moto Z Play is bricked, after downgrade of oreo to nougat, my imei not work. so i decided go to oreo again, when i reboot my phone bricked. help me please!!!

Try this. Updated my Sprint only thread to be a little more universal.
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783

bricked moto z2 force tmobile
donjuro said:
I think I've found a way to unbrick your phones guys!
If someone still has their bricked phone could they tell me what state they're in? I managed to successfully unbrick mines but had to stay on 8.0
Click to expand...
Click to collapse
guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...

How to flash a AT&T Galaxy S9 SM-G960U with a T-Mobile Stock Rom?

Hello,
I've been trying to find my answers on how to flash a AT&T GS9 SM-G960U with a T-Mobile S9 Stock Firmware\ROM.
I found this thread and although it's fairly close to what I am trying to do, I didn't want to post this there because they are talking about flashing U1 to U and I'm not sure if that is what I need to do exactly. https://forum.xda-developers.com/galaxy-s9/how-to/how-to-flash-u1-firmware-to-device-t3765200 from this thread, I've followed the initial steps and although Odin (Moded Odin v3.13.1 Raymonf ) tells me that the flash passed, upon reboot, the phone does not have the TMO firmware, it's still the original AT&T firmware. The only thing that it did do was add the TMO Visual VM icon\app.
I was informed of being able to download the TMO firmware from here: https://www.droiddosh.com/2018/04/samsung-galaxy-s9-sm-g960u-firmware-tmobile-usa-G960USQU1ARBG.html
Am I doing something wrong here? It seems that maybe these US models do not offer the OEM Bootloader unlocker option in developer settings unless you purchase the U1 version direct from Samsung that does not have a locked boot loader? I got this phone at no cost so that is also why I did not purchased from Samsung directly.
Any guidance and help would be appreciated.
Thank you

US carrier models have locked bootloaders, no way to root or install custom roms.
We should be able to flash between carrier versions/CSCs like we could with the S8, but the process is different and I've only read of a few people finding success in trying. The voicemail app you're seeing is due to flashing the T-Mobile userdata partition. This is the bloat partition - doesn't actually change device features, etc.

Any chance anybody has success doing this? It seems like a "Must Have" feature to switch carrier roms on the G960U between carriers, including Boot Screen/Logo, Firmware, Bloatware, etc.
All the goodies.
Any help?
Thank you,

I've done it!
dovid said:
Any chance anybody has success doing this? It seems like a "Must Have" feature to switch carrier roms on the G960U between carriers, including Boot Screen/Logo, Firmware, Bloatware, etc.
All the goodies.
Any help?
Thank you,
Click to expand...
Click to collapse
I've completed this task tonight thanks to some great help from a user that stepped me through it on a TMO Forum.
First an FYI, I first was able to flash my AT&T S9 version from SM-960U to a Stock SM-960U1. It worked great. After that, I was able to flash the TMO Rom and it's also working perfect. I'm not sure if it's required or not to flash the phone to a U1 first or if the TMO Rom can just be flashed. After I flashed the TMO firmware, I had no issues downloading and installing the latest TMO update. (My device is unlocked as well)
It's best to use Samsung switch first to backup your texts, pics, etc. first if you want to restore them to the device after completing the flash. The below instructions will start the phone up as if it was new out if the box.
Here is what I was provided with and the steps I followed.
To Flash the SM-G960U to a SM-G960U1
1. Allow\Enable USB Debugging in Developers settings.
2. Download the U1 Firmware here: https://androidfilehost.com/?w=files&flid=257063
(this is the U1 from Samsung, it's compressed but once extracted it will be around 4GB's of data.)
3. Download the ADB tools: https://devfiles.co/download/PDYvOWBg/platform-tools-latest-windows.zip. Create a folder on your desktop and name it ADB (for easy reference)
4. Download Odin: https://drive.google.com/file/d/10dSyPTuccP8Km9MnDrvbRdS-CAcgFZB3/view
5. From windows, run command prompt, in the command prompt type the following: cd C:\Users\XXX\Desktop\ADB
(XXX is your username)
6. Connect your phone to a USB port on your computer, your phone should prompt you to allow the connection to\from your computer. Allow the connection. Might be best to choose to "Always Allow"
7. Return to the command prompt and type in: adb devices You should see your device listed.
8. In the same command window, type in: adb reboot bootloader This will auto reboot your device into the "Download" mode.
9. Open and run Odin, add the corresponding tar files to the respective area's, in the "options tab" in Odin, make sure that only "Auto Reboot" and "F. Reset Time" is checked.
Click "Start" and the process will take a few minutes to complete.
Allow the device a few minutes to auto reboot and start up.
After you get through all the post boot setup screens, open a phone dial pad and type in, *#2263#. then make sure that all LTE bands are enabled.
Here you can find the SM-G960U T-Mobile Files: https://www.droiddosh.com/2018/04/samsung-galaxy-s9-sm-g960u-firmware-tmobile-usa-G960USQU1ARBG.html

Switching from U -> U1 -> U
B"H
Ok, thank you.
1. So stock G960U (Original Carrier) -> Flash to U1 -
2. Then, Go from G960U1 -> Stock G960U (Any Carrier)
Few questions:
1. Which CSC file are you using to flash -- CSC_HOME?
2. In moving from U1 -> U, do you need the final carrier SIM inside the phone?
I've tried this with a Verizon phone I'd like to convert to XFinity (CCT). I flashed the G960U VZW to G960U1 XXA. That worked fine. Then I flashed the G960U CCT rom, and the phone just boots up Verizon. When I check the CSC, it says "VZW/VZW/VZW", even though I flashed the CCT rom.
I don't have an XFinity sim card, so perhap that is the problem.
Any help would be great.

dovid said:
B"H
Ok, thank you.
1. So stock G960U (Original Carrier) -> Flash to U1 -
2. Then, Go from G960U1 -> Stock G960U (Any Carrier)
Few questions:
1. Which CSC file are you using to flash -- CSC_HOME?
2. In moving from U1 -> U, do you need the final carrier SIM inside the phone?
I've tried this with a Verizon phone I'd like to convert to XFinity (CCT). I flashed the G960U VZW to G960U1 XXA. That worked fine. Then I flashed the G960U CCT rom, and the phone just boots up Verizon. When I check the CSC, it says "VZW/VZW/VZW", even though I flashed the CCT rom.
I don't have an XFinity sim card, so perhap that is the problem.
Any help would be great.
Click to expand...
Click to collapse
You most likely will need a Xfinity Sim Card. I was able to convert my Xfinity Mobile S9 to AT&T by going to U1 firmware then inserting my AT&T sim card then flashing the AT&T U firmware.

ajairola said:
You most likely will need a Xfinity Sim Card. I was able to convert my Xfinity Mobile S9 to AT&T by going to U1 firmware then inserting my AT&T sim card then flashing the AT&T U firmware.
Click to expand...
Click to collapse
Where is the at&t u firmware? Currently on the unlocked firmware. Thanks

Savebig said:
Where is the at&t u firmware? Currently on the unlocked firmware. Thanks
Click to expand...
Click to collapse
Go to this thread (thanks @iBowToAndroid) and then look in the RB7 folder on Android File host.

Question
Does anyone know if you have to have the phone unlocked before changing over carriers? for example if i had a Galaxy S9 from Sprint and wanted to change the firmware to T-Mobile would it work or would it still be locked to Sprint? Thanks for your Help!

B AdamsHxC said:
Does anyone know if you have to have the phone unlocked before changing over carriers? for example if i had a Galaxy S9 from Sprint and wanted to change the firmware to T-Mobile would it work or would it still be locked to Sprint? Thanks for your Help!
Click to expand...
Click to collapse
Have the same question, but on my Verizon Note 8...

PieceofSlice said:
Have the same question, but on my Verizon Note 8...
Click to expand...
Click to collapse
I would check if your phone is already unlocked, Most Verizon phones come unlocked (unless you bought them from a Verizon Tent at Cosco or stores like that) Just put in another carriers sim card and check, if it is unlocked then you shouldnt have to flash anything, once you put in a different carrier sim it will tell you to restart your phone and once you do it will come up with the new carriers splash logo and apps

PieceofSlice said:
Have the same question, but on my Verizon Note 8...
Click to expand...
Click to collapse
In my experience all the carrier S9s are locked. You will need an unlock code from your carrier or an unlocking service.

Noob here: I’ve read that all US S9 models are the same in terms of hardware, is that true? Would that mean if I change the firmware from verizon to T-Mobile, it’ll be fully compatible?

Xamuyees said:
Noob here: I’ve read that all US S9 models are the same in terms of hardware, is that true? Would that mean if I change the firmware from verizon to T-Mobile, it’ll be fully compatible?
Click to expand...
Click to collapse
Yes! All 965U's, 965U1's, and 965W's are the exact same hardware, just different firmware.

For those of you that use TMO or U1 firmware on an unlocked ATT phone on TMO network, do you get a <Subject: NoSubject> before other people's texts in group texts? I've tried flashing U and U1 firmware several times as well as factory reset without being able to get rid of the subject line. Anyone have any insight or suggestions?

I was able to go from U1 to the att firmware. My question is why does samsung pass not work? I can see that the knox is not tripped and google play store is certified. Device status says official. Device is not rooted but Samsung pass thinks it is rooted. Why would this happen when all I did was install the carrier bundle?

(Newbie) doing what jrockz3000 did would allow root to be possible?

MFmvrdoc said:
(Newbie) doing what jrockz3000 did would allow root to be possible?
Click to expand...
Click to collapse
Unfortunately not. All North American S9s are not able to be rooted at this point.

ajairola said:
Unfortunately not. All North American S9s are not able to be rooted at this point.
Click to expand...
Click to collapse
Thank you man~

Odin link down
jrockz3000 said:
I've completed this task tonight thanks to some great help from a user that stepped me through it on a TMO Forum.
First an FYI, I first was able to flash my AT&T S9 version from SM-960U to a Stock SM-960U1. It worked great. After that, I was able to flash the TMO Rom and it's also working perfect. I'm not sure if it's required or not to flash the phone to a U1 first or if the TMO Rom can just be flashed. After I flashed the TMO firmware, I had no issues downloading and installing the latest TMO update. (My device is unlocked as well)
It's best to use Samsung switch first to backup your texts, pics, etc. first if you want to restore them to the device after completing the flash. The below instructions will start the phone up as if it was new out if the box.
Here is what I was provided with and the steps I followed.
To Flash the SM-G960U to a SM-G960U1
1. Allow\Enable USB Debugging in Developers settings.
2. Download the U1 Firmware here:
(this is the U1 from Samsung, it's compressed but once extracted it will be around 4GB's of data.)
3. Download the ADB tools: . Create a folder on your desktop and name it ADB (for easy reference)
4. Download Odin:
5. From windows, run command prompt, in the command prompt type the following: cd C:\Users\XXX\Desktop\ADB
(XXX is your username)
6. Connect your phone to a USB port on your computer, your phone should prompt you to allow the connection to\from your computer. Allow the connection. Might be best to choose to "Always Allow"
7. Return to the command prompt and type in: adb devices You should see your device listed.
8. In the same command window, type in: adb reboot bootloader This will auto reboot your device into the "Download" mode.
9. Open and run Odin, add the corresponding tar files to the respective area's, in the "options tab" in Odin, make sure that only "Auto Reboot" and "F. Reset Time" is checked.
Click "Start" and the process will take a few minutes to complete.
Allow the device a few minutes to auto reboot and start up.
After you get through all the post boot setup screens, open a phone dial pad and type in, *#2263#. then make sure that all LTE bands are enabled.
Here you can find the SM-G960U T-Mobile Files:]
Click to expand...
Click to collapse
Odin link down.

Need Android Pie firmware details for Unlocked T-Mobile Samsung S9

Hi All,
I have Samsung S9 Unlocked T-mobile from US and currently in India. Currently i have Oreo Version.
As all know, it doesnt have VOLTE option enabled which is needed for my sim network for voice calls to go through.
Somewhere i read Pie update will have VOLTE option and hence i am trying to update to Pie update.
I downloaded G960USQS6CSGB firmware for T-mobile, but before upating firmware using Odin, i got doubt if it will stick to T Mobile after update. This will make my phone not usable in India.
I tried to check online, but couldnt get direct answer and hence posting in new thread.
Can someone help clarify if it will lock the mobile to T-Mobile or will the phone be still in unlocked state?
Also i see two CSC files in the firmware folder. CSC and HOME_CSC. Which one to use?
If I should update with some other firmware for being unlocked and yet to get PIE update, please point to required firmware name or links.
Also will updating to PIE update will have VOLTE option ? Kindly confirm.
Thanks in Advance.

abalanag said:
Hi All,
I have Samsung S9 Unlocked T-mobile from US and currently in India. Currently i have Oreo Version.
As all know, it doesnt have VOLTE option enabled which is needed for my sim network for voice calls to go through.
Somewhere i read Pie update will have VOLTE option and hence i am trying to update to Pie update.
I downloaded G960USQS6CSGB firmware for T-mobile, but before upating firmware using Odin, i got doubt if it will stick to T Mobile after update. This will make my phone not usable in India.
I tried to check online, but couldnt get direct answer and hence posting in new thread.
Can someone help clarify if it will lock the mobile to T-Mobile or will the phone be still in unlocked state?
Also i see two CSC files in the firmware folder. CSC and HOME_CSC. Which one to use?
If I should update with some other firmware for being unlocked and yet to get PIE update, please point to required firmware name or links.
Also will updating to PIE update will have VOLTE option ? Kindly confirm.
Thanks in Advance.
Click to expand...
Click to collapse
csc will factory reset your phone, home_csc wont
volte wasnt removed from pie, so that shouldnt be an issue
the firmware version you posted has the 6th bootloader revision, im betting here is a 7th available for your phone, but the 6th version should be fine as well
as far as the unlocked state of the phone goes, it shouldnt re-lock, but im paranoid lol. Have you looked into the U1 versions of the phones firmware? Theyre inherently unlocked firmwares and dont have any of that irritating bloatware **** in them

youdoofus said:
csc will factory reset your phone, home_csc wont
volte wasnt removed from pie, so that shouldnt be an issue
the firmware version you posted has the 6th bootloader revision, im betting here is a 7th available for your phone, but the 6th version should be fine as well
as far as the unlocked state of the phone goes, it shouldnt re-lock, but im paranoid lol. Have you looked into the U1 versions of the phones firmware? Theyre inherently unlocked firmwares and dont have any of that irritating bloatware **** in them
Click to expand...
Click to collapse
Thanks youdoofus the inputs. Say by chance if it gets locked, is there a way to unlock the phone again from here?
may be then i will try to load U1 versions otherwise. Thanks alot.

abalanag said:
Thanks youdoofus the inputs. Say by chance if it gets locked, is there a way to unlock the phone again from here?
may be then i will try to load U1 versions otherwise. Thanks alot.
Click to expand...
Click to collapse
if it has no financial obligation to any carrier and the phone locks to that carrier, then the carrier it locked to would be required to release it. I cant imagine how it would lock to t-mob tho

Factory unlocked phones stay unlocked, no matter what firmware you flash.
Carrier locked phones that were properly unlocked by the carrier (they provide the code to SIM unlock the phone) will stay unlocked, again, no matter what firmware you flash to it - as long as it's compatible. Flashing the wrong firmware may just brick the phone. But, at least it's still SIM unlocked.
Phones that had some kind of software hack installed to trick the phone into thinking it's unlocked will lose the unlock status when you flash a firmware that also wipes the phone. Then it will come back as carrier locked again, because the hack is gone.
That last case is the only case I know of that will "re-lock" a phone. I've never heard of a carrier unlocked phone spontaneously re-locking under any circumstance.

Hi,
Thanks for the details. I tried to flash G960U1UES6CSG4_G960U1OYM6CSG4_XAA firmware. But while loading AP file in ODIN, it gave some error. Couldnt understand what is the error as its in chinese.
Then i loaded G960USQS6CSGB_G960UOYN6CSGB_TMB firmware which i downloaded previously. This got loaded in ODIN without any issues. And i am able to flash to phone. On rebooting, saw that phone moved to Pie version.
But i couldnt find VOLTE option (Enhanced calling) option. Does anyone know which version will enable that option?
Or anyother way to enable that please.
Thanks in advance.

joeldf said:
Factory unlocked phones stay unlocked, no matter what firmware you flash.
Carrier locked phones that were properly unlocked by the carrier (they provide the code to SIM unlock the phone) will stay unlocked, again, no matter what firmware you flash to it - as long as it's compatible. Flashing the wrong firmware may just brick the phone. But, at least it's still SIM unlocked.
Phones that had some kind of software hack installed to trick the phone into thinking it's unlocked will lose the unlock status when you flash a firmware that also wipes the phone. Then it will come back as carrier locked again, because the hack is gone.
That last case is the only case I know of that will "re-lock" a phone. I've never heard of a carrier unlocked phone spontaneously re-locking under any circumstance.
Click to expand...
Click to collapse
another user just posted up in another thread that they had a factory cricket phone that got unlocked, he put an at&t sim in it and it installed at&t apps and locked the phone to at&t FWIW
---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------
abalanag said:
Hi,
Thanks for the details. I tried to flash G960U1UES6CSG4_G960U1OYM6CSG4_XAA firmware. But while loading AP file in ODIN, it gave some error. Couldnt understand what is the error as its in chinese.
Then i loaded G960USQS6CSGB_G960UOYN6CSGB_TMB firmware which i downloaded previously. This got loaded in ODIN without any issues. And i am able to flash to phone. On rebooting, saw that phone moved to Pie version.
But i couldnt find VOLTE option (Enhanced calling) option. Does anyone know which version will enable that option?
Or anyother way to enable that please.
Thanks in advance.
Click to expand...
Click to collapse
if your Odin error messages are in Chinese, youve obtained a modified version. Itll probably work, but youll get that Chinese stuff whenever it needs to tell you anything. I dont know which versions have volte tbh. Sorry man.

youdoofus said:
another user just posted up in another thread that they had a factory cricket phone that got unlocked, he put an at&t sim in it and it installed at&t apps and locked the phone to at&t FWIW
---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------
if your Odin error messages are in Chinese, youve obtained a modified version. Itll probably work, but youll get that Chinese stuff whenever it needs to tell you anything. I dont know which versions have volte tbh. Sorry man.
Click to expand...
Click to collapse
Thanks youdoofus for trying to help. For me atleast it didnt get locked when i moved to Pie. I will try other methods.
I will try to root the phone for enabling volte, but the methods that i tried didnt work.

youdoofus said:
another user just posted up in another thread that they had a factory cricket phone that got unlocked, he put an at&t sim in it and it installed at&t apps and locked the phone to at&t FWIW
Click to expand...
Click to collapse
That's just weird.

joeldf said:
That's just weird.
Click to expand...
Click to collapse
yeah, sort of. The CSC's on these things are weird. Im starting to believe that these new versions of android are just like windows ISOs where they have all the versions compressed into one file and it uses a directory file to tell the firmware which version to install. Im sure a code writing dev can confirm or deny this thought, but at this point its merely a weak theory

2019-10-08_21:17:56 Device Info:
MAC : 44:91:60:6F8:11
MACs : 44:91:60:6F8:11 46:91:60:6F8:11
Root : false
VirtualMachine : false
build.characteristics : nosdcard
build.display.id : PPR1.180610.011.G960USQS6CSGB
build.fingerprint : samsung/starqltesq/starqltesq:9/PPR1.180610.011/G960USQS6CSGB:user/release-keys
build.host : SWDH7918
build.id : PPR1.180610.011
build.incremental : G960USQS6CSGB
build.release : 9
build.sdk : 28
build.tags : release-keys
build.time : 1563280950
build.type : user
build.user : dpi
clientidbase : android-samsung-ss android-tmus-us-revc
cpu.abi : arm64-v8a
cpu.abilist : arm64-v8a,armeabi-v7a,armeabi
cpu.abilist32 : armeabi-v7a,armeabi
cpu.abilist64 : arm64-v8a
hardware : qcom
iso-country : us
maps :
/data/app/air.com.vudu.air.DownloaderTablet-t5mbVjvM1FFl0QEUPwzQyw==/base.apk
/data/app/app.greyshirts.firewall-d39DVNDNC1T-3kBvPh9atA==/base.apk
/data/app/cn.trinea.android.developertools-i-YQ40tKZG_8h1XUaPXnNw==/base.apk
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/base.apk
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/lib/arm64/libdeviceid.so
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/oat/arm64/base.art
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/oat/arm64/base.odex
/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/oat/arm64/base.vdex
/data/app/com.bluedf.secretcodes-HV9rnYLpul4wQolux9pzwA==/base.apk
/data/app/com.bluedf.secretcodesroot-hGA1tSj9Tvim8s_10D9gsQ==/base.apk
/data/app/com.cleanerapp.supermanager-WePEX1NMFy_p1AuwuQ-8rw==/base.apk
/data/app/com.cleanerapp.supermanager-WePEX1NMFy_p1AuwuQ-8rw==/split_config.arm64_v8a.apk
/data/app/com.cleanerapp.supermanager-WePEX1NMFy_p1AuwuQ-8rw==/split_config.en.apk
/data/app/com.cleanerapp.supermanager-WePEX1NMFy_p1AuwuQ-8rw==/split_config.xxhdpi.apk
/data/app/com.contextis.android.BLEScanner-_JPbA8nJK6dFNifXOStWBw==/base.apk
/data/app/com.cpu82.roottoolcase-LS9phULHU4si2JZypZu18g==/base.apk
/data/app/com.cradlepoint.netcloud.manager-QNZJb2X6rbWHPj0nzT26SQ==/base.apk
/data/app/com.cradlepoint.netcloud.manager-QNZJb2X6rbWHPj0nzT26SQ==/split_config.en.apk
/data/app/com.cradlepoint.netcloud.manager-QNZJb2X6rbWHPj0nzT26SQ==/split_config.xxhdpi.apk
/data/app/com.derevenetz.oleg.magicphotos-dORDc6h1twxKI0IxBcyHAw==/base.apk
/data/app/com.diamond.apps.filemanager-Zt29zbvNjupsE3yzke4RHA==/base.apk
/data/app/com.enflick.android.TextNow-2ZsLoogNdPWqIwmaQGJb2g==/base.apk
/data/app/com.eypcnn.wifipasswordshow-2cIzlBAsm7GP4BuTC9feYw==/base.apk
/data/app/com.facebook.katana-WloRDUS_s087OTw-SlM3kg==/base.apk
/data/app/com.facebook.katana-WloRDUS_s087OTw-SlM3kg==/split_arservicesoptional.apk
/data/app/com.facebook.katana-WloRDUS_s087OTw-SlM3kg==/split_rtc.apk
/data/app/com.facebook.katana-WloRDUS_s087OTw-SlM3kg==/split_streamingsdk.apk
/data/app/com.facebook.orca-tsPK3nLBiCqKSuZzFyTgeg==/base.apk
/data/app/com.facebook.orca-tsPK3nLBiCqKSuZzFyTgeg==/split_cardio.apk
/data/app/com.freeit.java-znqdl0s04I9N-fbGWtOW_A==/base.apk
/data/app/com.freeit.java-znqdl0s04I9N-fbGWtOW_A==/split_config.arm64_v8a.apk
/data/app/com.freeit.java-znqdl0s04I9N-fbGWtOW_A==/split_config.xxhdpi.apk
/data/app/com.google.android.apps.access.wifi.consumer-eQa-41SblsmvYiy0lVSy7Q==/base.apk
/data/app/com.google.android.apps.books-jjrUo5E6vP0zhGP19Fch2A==/base.apk
/data/app/com.google.android.apps.docs-Up5ehHhl3wsTfpiLF95Z4A==/base.apk
/data/app/com.google.android.apps.photos--0tzlNaW_wuwWUDJMigTww==/base.apk
/data/app/com.google.android.apps.photos--0tzlNaW_wuwWUDJMigTww==/split_config.en.apk
/data/app/com.google.android.apps.photos--0tzlNaW_wuwWUDJMigTww==/split_config.xxhdpi.apk
/data/app/com.google.android.apps.translate-nkvNQXFkcbpp1zglp84UUw==/base.apk
/data/app/com.google.android.music-a7QiK-jqDGc_rE9Fw5XOzw==/base.apk
/data/app/com.google.earth-5XZzMY1I3fKcWGaJhJ1iyg==/base.apk
/data/app/com.indeed.android.jobsearch-5ciyVRNfrci-EXuXkANUcw==/base.apk
/data/app/com.inspiredandroid.linuxcommandbibliotheca-bb3ZTfwlOfOPylFFNy0fGQ==/base.apk
/data/app/com.inspiredandroid.linuxcommandbibliotheca-bb3ZTfwlOfOPylFFNy0fGQ==/split_config.arm64_v8a.apk
/data/app/com.inspiredandroid.linuxcommandbibliotheca-bb3ZTfwlOfOPylFFNy0fGQ==/split_config.xxhdpi.apk
/data/app/com.inspiredandroid.linuxcontrolcenter-Kqp5BsR5cSkjdffSe6TuEA==/base.apk
/data/app/com.instagram.android-y85BBsblTUYo1is0WluBZA==/base.apk
/data/app/com.jao.wifi.map.hotspot.connection.wifianalyzer.password.anywhere.wifimanager-lTiKRkBr35XPsQ-_RiB_oQ==/base.apk
/data/app/com.jumobile.manager.systemapp-16NybbvDbjY_D5agiVtsGw==/base.apk
/data/app/com.kasitskyi.hiddensettings-a-osLmMm5ePEz1y3VJ7RuA==/base.apk
/data/app/com.kpstv.youtube-5fN6D5m5G0FISRCSFBWMeg==/base.apk
/data/app/com.lonelycatgames.Xplore-h8Vemfk9AJcGgO6TlEcEog==/base.apk
/data/app/com.lookout.net-PEfkrK56N9hOzHDBXAW9KA==/base.apk
/data/app/com.magdalm.usbsettings-KCF_d3UQ4pXNZJekMlYO8Q==/base.apk
/data/app/com.magdalm.usbsettings-KCF_d3UQ4pXNZJekMlYO8Q==/split_config.en.apk
/data/app/com.magdalm.usbsettings-KCF_d3UQ4pXNZJekMlYO8Q==/split_config.xxhdpi.apk
/data/app/com.mobile.antivirus.security.virus.cleaner-torftuRqVy9ycIJqODc-Lw==/base.apk
/data/app/com.movietube.fullest.inwebsite-EEkAQ5GNuzQJvizkFk2Diw==/base.apk
/data/app/com.pandora.android-lQA_FIeHZhK1xUFFO2Svyw==/base.apk
/data/app/com.paprbit.dcoder-xDi_9MfJVQAwHkehs4caTg==/base.apk
/data/app/com.propel.ebenefits--ftv6kBm2X8SHhJRyzj-IQ==/base.apk
/data/app/com.samsung.android.app.notes-XcN2lg0cZZ0I-ZK86oSPlg==/base.apk
/data/app/com.samsung.android.videolist-VwfMDYlOcOgRJj7CTx4fxQ==/base.apk
/data/app/com.sec.android.app.ocrservice-Vx7pGxQhVb9Ct_EkebxUzg==/base.apk
/data/app/com.sec.android.app.popupcalculator-uHV2SpAqv4fNWhv_wlBCTA==/base.apk
/data/app/com.sec.android.app.voicenote-mJUISc5gQ2yx9gYhJC49Tg==/base.apk
/data/app/com.sharpened.androidfileviewer-s9Z0CE2pWNr-XyeCUfIrfQ==/base.apk
/data/app/com.sharpened.androidfileviewer-s9Z0CE2pWNr-XyeCUfIrfQ==/split_config.arm64_v8a.apk
/data/app/com.sharpened.androidfileviewer-s9Z0CE2pWNr-XyeCUfIrfQ==/split_config.en.apk
/data/app/com.sharpened.androidfileviewer-s9Z0CE2pWNr-XyeCUfIrfQ==/split_config.xxhdpi.apk
/data/app/com.snapchat.android-cqgv7rBP2rPoPNuiNtwTGg==/base.apk
/data/app/com.snapchat.android-cqgv7rBP2rPoPNuiNtwTGg==/split_config.arm64_v8a.apk
/data/app/com.snapchat.android-cqgv7rBP2rPoPNuiNtwTGg==/split_config.en.apk
/data/app/com.snapchat.android-cqgv7rBP2rPoPNuiNtwTGg==/split_config.xxhdpi.apk
/data/app/com.soomapps.screenmirroring-u0awU7-A205YfaTfw3t8bw==/base.apk
/data/app/com.spatialnetworks.fulcrum-tTNdrKTK5n5g8HapjAcvXA==/base.apk
/data/app/com.spatialnetworks.fulcrum-tTNdrKTK5n5g8HapjAcvXA==/split_config.arm64_v8a.apk
/data/app/com.spatialnetworks.fulcrum-tTNdrKTK5n5g8HapjAcvXA==/split_config.en.apk
/data/app/com.spatialnetworks.fulcrum-tTNdrKTK5n5g8HapjAcvXA==/split_config.xxhdpi.apk
/data/app/com.thirtydegreesray.openhub-m-X5STyX1NiOqdIWsjHHKw==/base.apk
/data/app/com.twitter.android-CCrLl-3tWEVBih_z7Vjo7A==/base.apk
/data/app/com.twitter.android-CCrLl-3tWEVBih_z7Vjo7A==/split_config.arm64_v8a.apk
/data/app/com.twitter.android-CCrLl-3tWEVBih_z7Vjo7A==/split_config.en.apk
/data/app/com.twitter.android-CCrLl-3tWEVBih_z7Vjo7A==/split_config.xxhdpi.apk
/data/app/com.ubnt.unifihome-dWJY-qLGK6YuYRn8GBV1BQ==/base.apk
/data/app/com.xda.labs-mj8AI7PMA4ykJLKmGx6F1A==/base.apk
/data/app/duy.com.text_converter-i71QdR_GutTm06Qk_IhnxA==/base.apk
/data/app/eu.faircode.netguard-xjF0xDra31VKBHL8Nnk0OA==/base.apk
/data/app/info.valky.decryptor-QNpaSsdyNK0O06DvqskOrA==/base.apk
/data/app/mtk.engineering.mode.app.apk-cj5K8glcKnDDeaKlfy1wSw==/base.apk
/data/app/net.techet.netanalyzerlite.an-A1UGqlffdlQSxA2FMePInw==/base.apk
/data/app/options.developer.com.developeroptions-0zTXrjNvoYe-hKYjU1gouQ==/base.apk
/data/app/org.malwarebytes.antimalware-0u7tRaOtS69f-f-uAr6vnQ==/base.apk
/data/app/org.mozilla.fennec_aurora-n1jo0bDX8Jh7pYm3koDuLQ==/base.apk
/data/app/org.mozilla.firefox--wE0cOpC-5dw9t0zdv-Cyw==/base.apk
/data/app/org.pocketworkstation.pckeyboard-1y0BnUC9lJpmMo24g65nzA==/base.apk
/data/app/ru.gavrikov.mocklocations-1KKeGOBK6SYV1zwIgMaQvg==/base.apk
/data/app/scd.atools-ugyYuEQfYtLTOV4NY433Ow==/base.apk
/data/app/screenmirroring.abdelm.com.screenmirroring-DSxowgttK15MH2GEt6-lrg==/base.apk
/data/misc/zoneinfo/current/icu/icu_tzdata.dat
/dev/ashmem/dalvik-/data/app/com.bigsing.changer-vw1KB9QxofVWzkNA5AIQqg==/oat/arm64/base.art_14890_14890 (deleted)
/mnt/asec/com.effinitytech.networkexplorer-1/base.apk
product.board : sdm845
product.brand : samsung
product.device : starqltesq
product.manufacturer : samsung
product.model : SM-G960U
product.name : starqltesq
Time Used: 2.00 s

How to Covert LG V30 V300L to global( Pie)

Remember you're doing this at your own risk. I won't be hold responsible for any damage.
Read and follow steps carefully.
First follow the tutorial to unlock your bootloader, install twrp and root.( https://forum.xda-developers.com/lg-v30/how-to/korean-variant-bootloader-unlock-root-t3804505), after unlooking the bootloader,
flash twrp flashable v300l android 8 rom( 2019 prefered) and boot android first.
Go to developer options and enable usb debugging and OEM unlocking if is unticked.
Now download v300l pie rom and flash with LGUP( Use the dualmode version to get all options), but this time choose refurbish.
After it successfully boot, go back to enable developer options and enable usb debugging.
Now Download H930 pie rom you like and flash with lgup but this time choose partition dl then click start.
Now this is the important part, when the partition selection menu pops up, select all partitions except xbl, xbl 2 and modem, these three partitions must be unselected or unmarked then hit ok to flash.( if you dont unselect them, it will flash H930 Modem and you wont get network since the korea variants and Global variants dont have the same modem. unselect those 3 options to retain the korea modem)
After it finishes, hold the volume down and power button to got to recovery and do factory reset.
Wait for it to finish booting and configure to get your lg v30 korea variant as a global version.
Notes:
Any time there is an update, please use the LGUP to flash kdz and select partition dl, and leave xbl xbl2 and modem unselected or else you will not get network or service signal.
Never use a flashable zip or else you will get softbrick( you can use a back up global rom to restore as update but make sure you dont select modem anytime youre doing update)
sometime registering network seems to take longer time, be patient.
You can also root by using the recovery installion method and root using twrp.
I dont know if this will work on the other korea versions but you can try.
You can now flash any aosp rom made for H930 you want without any problem because your device is now global version.
Please Fm radio will never work because the Korea Variants don't have Fm hardware. LG replaced the Fm hardware with DMB hardware for Korea market.
Saying thank you will be appreciated

@Amosika
Please just to verify, you mean all custom roms available to H930 can now be installed on V300L?

fi5z.x9 said:
@Amosika
Please just to verify, you mean all custom roms available to H930 can now be installed on V300L?
Click to expand...
Click to collapse
yes. every rom for H930 works on v300l with a single problem unless that rom is buggy.

fi5z.x9 said:
@Amosika
Please just to verify, you mean all custom roms available to H930 can now be installed on V300L?
Click to expand...
Click to collapse
But just covert from v300l to H930 first or else you wont get network signal. follow the tutorials and you will see the magic

just finish converting mine. V300S
from v21e
1.i flashed v300s 30h
2.next flashed H93030q_00_OPEN_EU_OP_0902.kdz (unchecked xbl,xbl2,modem)
3.flash TWRP-3.2.3-7-DataIMG.img
4.from twrp: flash magisk v19.4, dm_verity, ak3_rctd remover.
reboot successfully with signal and data. buy one thing i notice, there is no 3g/lte indicator under signal icon. but then again, i have data connection.
Now, my concern is:
1. if I backup my current stock rom (h93030q) via twrp, then i restore it via twrp. will I get softbrick?
2. what twrp version must prefer to install custom rom?
3. what are the working custom rom do i use?
4. whats the proper step in twrp to have a clean install for custom rom?
5. lastly, when im in custom rom, can i go back to stock h93030q via RESTORE on TWRP?

Earlier i flashed v300l rom step by step but i got no signal so i revert back to us998 20h oreo. But still i lost signal. (When i search it shows "error while searching networks) and (i check ims status in *#*#4636#*#* the n phone info and tap three dots and ims status. Ims status : not registered) my original device is h931 converted to us998.
I done everything flash rom in DL/Refurbished but no success till date. So if you guys have any fix please help me. And yes i don't loose imei number , i have it but no network. And wifi not able to search Wi-Fi's every time i need to restart to connect wifi. Sometimes it connect. Till restarting for wifi connection.

hi guys. this method works well, but network searching is too long, because firmware is searching for a second sim. At Oreo roms it was possible to fix it by changing (removing) persist.radio.multisim.config property in build.prop or OP folder. is there any way to fix it at Pie?
---
ok guys, i found a solution if you have root
edit file /vendor/bin/init.class_main.sh
about string ~120-130 find
multisim=`getprop persist.radio.multisim.config`
Click to expand...
Click to collapse
and change it with
multisim=tsts
Click to expand...
Click to collapse
looks like workaround, but works well

viktor.s said:
hi guys. this method works well, but network searching is too long, because firmware is searching for a second sim. At Oreo roms it was possible to fix it by changing (removing) persist.radio.multisim.config property in build.prop or OP folder. is there any way to fix it at Pie?
---
ok guys, i found a solution if you have root
edit file /vendor/bin/init.class_main.sh
about string ~120-130 find
and change it with
looks like workaround, but works well
Click to expand...
Click to collapse
i tried that, after reboot i have no signal anymore even i backed the default.
fortunately i have backup from twrp.
---------- Post added at 01:13 PM ---------- Previous post was at 12:44 PM ----------
coming from v300s pie and flashed h930 30q. my only problem is lte/4g icon on statusbar, how can I fix it?

no Vietnamese language

Hi bro. Can it be used with volte?

The guide look promising and I would like to try it on my V300L that I bought to replace my H930 with a smashed screen (unfortunately a screen assembly would have cost more).
But I got two questions before trying it out:
1. The Bootloader unlock and root guide is based on Oreo, but I got my V300L on Pie, unfortunately (V300L30h). According to the hidden menu, ARB is 0 for APPSBL, SBL1, TZ and RPM, so it should work, right?
2. My goal is to convert the firmware to the EU variant, but I don't necessarily need a bootloader unlock or root myself. In the bootloader unlock guide you are supposed to flash the H930 firmware as a whole, including XBL, XBL2 and modem. So it seems like the V300L and H930 firmware is signed using the same key. As bootloader unlocking requires to reflash the firmware multiple times, which is not optimal for the EMMC chip, and bootloader unlocking could introduce some hassle with some apps, I wondered if it was possible to flash the firmware directly without peforming the bootloader unlock first, of course without flashing XBL, XBL2 and modem. Unfortunately, I don't really know how Qualcomm's chain of trust works, but I can imagine that having bootloader stages from different device firmwares might trip up the validation and I really don't want to mess up the bootloader chain.
Thanks in advance

what h930 rom that have not dual sim. i need a single sim version of h930 firmware

dchinacay said:
what h930 rom that have not dual sim. i need a single sim version of h930 firmware
Click to expand...
Click to collapse
Android Oreo or pie?

dchinacay said:
what h930 rom that have not dual sim. i need a single sim version of h930 firmware
Click to expand...
Click to collapse
??? I think you are confused about something.
All actual H930 firmware is single SIM. LG H930 and (even LG H930G) are single SIM phones.
There are only two "V30" dual SIM variants -- H930DS and H930D. So don't flash H930DS or H930D KDZ.
But actual H930 is single SIM. So, any LG stock KDZ for H930 is single SIM. The hard part is finding dual SIM KDZ not avoiding them.
________
I'm a little confused by "ROM". Are you talking about LOS custom ROMs? Or stock firmware TWRP flashable zips built like ROMs? Or are you merely using the word ROM to describe LG stock KDZ? In the OP, they use the word "ROM" to mean LG stock KDZ, so I will assume that's what you mean.

sorry that's for stock kdz. as i have v300s and converting to h930. this is the file i fl(H93030q_00_OPEN_EU_OP_0902.kdz) but it has a dual simcard option in settings.
i

dchinacay said:
sorry that's for stock kdz. as i have v300s and converting to h930. this is the file i fl(H93030q_00_OPEN_EU_OP_0902.kdz) but it has a dual simcard option in settings.
Click to expand...
Click to collapse
That's a single SIM phone. It is compatible with dual SIM H930 variants (DS and D), but H930 is a single SIM phone.
If it has dual SIM card option, just ignore it.
Early Oreo H930 KDZ didn't have that option and H930DS people who flashed that couldn't use their dual SIMs.

ChazzMatt said:
That's a single SIM phone. It is compatible with dual SIM H930 variants (DS and D), but H930 is a single SIM phone.
If it has dual SIM card option, just ignore it.
Early Oreo H930 KDZ didn't have that option and H930DS people who flashed that couldn't use their dual SIMs.
Click to expand...
Click to collapse
i can confirm what @dchinacay has said above with regard to stock H930 30q firmware having Dual SIM option in Korean V300 Frankenstein; is that option visible by default in non DS version of H930 too?
i have just converted a V300S to H930 Pie using method by @darkidz555 and @Amosika and flashed the stock H930 30q KDZ firmware from your mega upload last to achieve that.
many thanks to everybody that has contributed to this marvel!
while signal searching was instantaneous when the phone was still in its V300 state, it has slowed down noticeably as a H930 now.
is the slow down due to the Dual SIM option or because the phone is now searching for networks in bands not supported by the V300?
hope some gurus can shed some light and maybe we can solve the problem with a simple config file edit.
(i did not try the suggestion (https://forum.xda-developers.com/showpost.php?p=80558959&postcount=7) by @viktor.s as @dchinacay has encountered problem with it.)
@dchinacay, I do have 4G on top of the signal bars when mobile data is in use (wifi off or when not connected to wifi).

Dual SIM and slow signal search issue resolved!
I accidentally stumbled upon the solution for slow signal search after conversion to H930.
As I did not uncheck the box beside recovery and recoverybak for Partition DL when flashing H930 30q KDZ firmware, I had to reflash TWRP after 30q.
As known, Format Data is required during the first boot in TWRP recovery for TWRP to work.
After formatting data and rebooting back into TWRP recovery, I went ahead to flash Magisk 20.1, Disable DM Verity and RCTD Remover.
To my surprise, after the phone has booted into android PIE, there is no more Dual SIM option and the 4G cellular signal caught on almost instantaneously, like how it was when the phone is still a V300!
 @dchinacay, the 4G signal icon display went back to that of V300's too!
Hope the above works a treat for all those facing the same issues!

potatohead said:
I accidentally stumbled upon the solution for slow signal search after conversion to H930.
As I did not uncheck the box beside recovery and recoverybak for Partition DL when flashing H930 30q KDZ firmware, I had to reflash TWRP after 30q.
As known, Format Data is required during the first boot in TWRP recovery for TWRP to work.
After formatting data and rebooting back into TWRP recovery, I went ahead to flash Magisk 20.1, Disable DM Verity and RCTD Remover.
To my surprise, after the phone has booted into android PIE, there is no more Dual SIM option and the 4G cellular signal caught on almost instantaneously, like how it was when the phone is still a V300!
@dchinacay, the 4G signal icon display went back to that of V300's too!
Hope the above works a treat for all those facing the same issues!
Click to expand...
Click to collapse
finally someone explained properly about this situation, as I'm not good in english.
so what step i will do? go back to v300s kdz - flash h930 30q - uncheck xbl, xbl2, modem, recovery, recoverybak - start?

potatohead said:
I accidentally stumbled upon the solution for slow signal search after conversion to H930.
As I did not uncheck the box beside recovery and recoverybak for Partition DL when flashing H930 30q KDZ firmware, I had to reflash TWRP after 30q.
As known, Format Data is required during the first boot in TWRP recovery for TWRP to work.
After formatting data and rebooting back into TWRP recovery, I went ahead to flash Magisk 20.1, Disable DM Verity and RCTD Remover.
To my surprise, after the phone has booted into android PIE, there is no more Dual SIM option and the 4G cellular signal caught on almost instantaneously, like how it was when the phone is still a V300!
@dchinacay, the 4G signal icon display went back to that of V300's too!
Hope the above works a treat for all those facing the same issues!
Click to expand...
Click to collapse
Glad you got it worked out.
dchinacay said:
finally someone explained properly about this situation, as I'm not good in english.
so what step i will do? go back to v300s kdz - flash h930 30q - uncheck xbl, xbl2, modem, recovery, recoverybak - start?
Click to expand...
Click to collapse
He did NOT uncheck the recovery and recovery_bak, so he wiped out TWRP... Which actually solved his problem. He then re-installed TWRP, reformatted his data (necessary), flashed Magisk 20.1, Disable DM Verity and RCTD Remover.
He basically followed these steps:
INSTALL or REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
https://forum.xda-developers.com/showpost.php?p=79972584&postcount=3285

[Moto Z2 | XT1789-x] Paritionning, modem and A/B general questions

Hi everyone,
I’m used to ROM flashing, programming and hacking some stuff using linux and other, but I currently stuck on a serious issue:
I am totally unable to fix modem issue on the Moto Z2 Force - “Nash” - XT-1789-06 FR/intenational.
I have another brand new stock XT-1789-04 “retail” on label but ATT software ready to be flashed !
I hope this post will help to anderstand both modem firmware and seemless A/B devices.
------------------
Here is my story as an example:
- I get a XT1789-06, factory reset it. All worked perfectly.
- I unlocked the bootloader with the motorola well know method. No trouble.
- I boot Lineage-recovery.img then install Lineage 16.0 from zip with adb-sideload
- It boot and works perfectly, I can call, use wifi etc... but when I restart, it goes into Bootloop…
- After few attempt to re reflash, may be I miss something, so i decided to return into stock-rom until I’ll find a way to fix this bootloop issue.
- As I don’t have any back-up, I start to find the stockrom zip.
- I find the great rom reprository for ‘nash’ :
- I’m questionning about de difference bettween RETAIL and RET.EU and other ? So I finaly flash the XT1789-06-RETAIL-OPSX
- The phone boot well but no sim Card detected and no wifi, no baseband, no IMEI, strange MAC wifi adress.
-This looks like a classical issue so I tried ALL the classic methode to fix it:
--- Fastboot erase modemst1/st2 erease carrier ..
--- Root it using Magisk (no problem) and tried the chmod something way.
Still same issue...
So I started to flash several different NON-HLOS.bin and FSG.bin (this two file only), and I find the XT1789-05 T-mobile file is working on my XT1789-06! (strange because my is XT1789-06 and the carrier is not TMO) Wifi is working, Sim card detected asking for PIN ok IMEI OK ….
But no network (Gsm,LTE,2G,3G,4G…) at all. The Baseband is shown as ‘xxxTMO”
It is the only NON-HLOS.bin wich detect my SIM card and turn on wifi.
All the other give me baseband not found, no IMEI, no wifi.
Could it be an issue with android 8.0 and 9.0 ? (I may have flash 8.0/9.0)
Now, I’m no more able to boot into lineage recovery, only TWRP is possible.
When I triy to install lineage Zip using TWRP it tell me “ERROR:X” (7 ?)
So here is some general question to clarify all modem question:
- What the file NON-HLOS.bin stand for ? What does it mean, from which source it come from and for what purpose ?
- What the file fsg.bin stand for ? What does it mean, from which source it come from and for what purpose ?
- Is is possible to flash only NON-HLOS and/or fsg.bin ? Does it need to be according to gpt.bin for partitionning ?
- Do yo know the exact file is needed for the XT1789-06 French/Europ
- How to know if a baseband is “locked” for a specific carrier ? Is the RETAIL sotck ROM totaly unlocked ?
- Do you think I can use T-Mobile baseband to access the French ‘orange’ networks ? The TMO modem dont ask me any “SIM-LOCK code” so it not appear to be locked, but no still no networks.
- Is it possible to change the networks/frequency/zone/technology by software methode ? (like by dialing *#*#4636#*#* we could select GSM only CMDA LTE ….. ) could someone to explain exactly for wich country is it applicable ?)
- What OPXS / OPX / PPX exactly mean ?
- Could Some one Clarify the “slot a / slot b” reason, usage, method of flashing boot … I suspect the underliying reason of the issue is about the two slots.
- When we flash NON-HLOS to modem partion, why we usaly erase modemst1/2 after that ? When we choose ‘modem” partition, is it slot_a, slot_b or both ?
- What is the carrier and OEM partition ?
- Is it possible to make a backup of a fully working machine, then applying only the “modem” or “persist” partition to another same exact model phone ? (I’m about to buy a brand new one to dump the exact modem file)
- Is there a way to get the full (even unofficial) source code for hardware part of the motorola nash ?
- What about a blank flash ? Do you think it could be a way to recover the modem ?
- Could the Qualcom serial debug be a way of un-bricking it ? Then, how to boot EDL ?
- Please clarify the what we exactly have to flash on A/B slot to avoid boot loop ?
I am very commited to deleted all the Google bloat stuff from motorola mobile so I bought a brand new 17896-04 and I will try a new round :fingers-crossed:
I hope this post will defenitely clarify the handeling of modem issue be cause lot of us seems to have serious trouble.
Thank in advance,
Best regards,
R-A-F

The problem are the updates, screw the modem data, and we are so much people who have this issue, we trying to solve this, pls stay tune