[GUIDE] Flashing XQ-AT51 Firmware on XQ-AT52 Device - Sony Xperia 1 II Guides, News, & Discussion

Disclaimer: I am not responsible for any bricks/ issues you may encounter following this guide. Although, I will do my best to try to help you if something were to go wrong.
MAKE SURE OEM UNLOCK IS ENABLED UNDER DEV SETTINGS BEFORE YOU DO ANYTHING BELOW
Update 2: 3/11/2021 : I see maybe deleting the .ta files may help avoid soft bricking, feel free to try it I have not personally tested yet to see if it works.
Update#3 3/13/2021 : If you are following this guide recently make sure you update to Android 11 first! Do not do any updates after the first one to Android 11! Then the flashing should work just fine. Tested and verified this on Taiwan XQ-AT52 to 51 firmware
Hello, I've managed to successfully flash AT51 firmware on my AT52 without issue using Newflasher.
Step 1 download = the US firmware/ whatever region is needed for you and new flasher/ the sony xperia drivers needed to flash the firmware to your device. Extract it to your desktop. Install the Xperia driver from newflasher if you need to/ haven't yet. Newflasher needs to be extracted into the same folder where the firmware files are that you downloaded from Xperifirm. This step is crucial!
Step 2 : Power off your Xperia and put it in flash mode by pressing down on the volume and connecting it to your PC via usb. (Do not use the USB C cable that came with the phone use a different one if you have one) You'll know it is in flashmode if the notification LED turned green and the screen remains off.
Step 3 : Open newflasher.exe
Step 4: type n then press enter
Step 5: type n again and press enter
Step 6 : This is when you should get to the flashing stage. Press Y and enter to everything you are prompted to. type y for yes to. This for me resulted in a successful conversion over to AT51.
Step 7: Once everything is done and it says you are safe to disconnect your phone please do so and then press and hold your power button until the phone boots up.
At this point you should have a fully working AT51 firmware!
Bare with me as I"m working on getting developer access for androidfilehost and will upload the files asap. In the meantime you can download newflasher and the firmware files yourself using Xperifirm if you don't wanna wait for me to upload.
Xperifirm: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Newflasher: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426

Can you please help? I followed and i got a corrupted message and power off in 5 second.
I tried xperia companion, failed.
I tried to reflash newflasher with original firmware again, failed.
Please help.

tiunilohmu said:
Can you please help? I followed and i got a corrupted message and power off in 5 second.
I tried xperia companion, failed.
I tried to reflash newflasher with original firmware again, failed.
Please help.
Click to expand...
Click to collapse
Can you tell me the model of your xperia phone? If you can still get it into flash mode when the notification LED turns green you may still be able to recover it.

Hi, I finally managed to restore it. I have to remove all the ta files to flash it, then it booted up.
Thanks for your respond.

my device is corrupted please help

blegs said:
my device is corrupted please help
Click to expand...
Click to collapse
what did you do to corrupt it?

Lennyuk said:
what did you do to corrupt it?
Click to expand...
Click to collapse
I have using newflasher
After using 3 time xperia companion it work normal again

Hi, I didn't find this thread until after I made an attempt at flashing the device. I followed the instructions from the link below and ended up with the device saying it's corrupted.
https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
I tried redownloading newflasher as well as redownloading the firmware I wanted as well as a new cable and that did not help. I reflashed it with this procedure listed above and it did not help.
Xperia companion won't let me do anything because it says the device is locked even though the device was not locked and there doesn't appear to be a way to unlock it. edited to add that I did get xperia companion to repair it successfully
edit again to advise I succeeded only after doing n and enter a third time then hitting y and enter for the final flashing step and that was successful in getting it updated correctly

Would it work to unlock my phone
Thanks for the guide!
Can I ask few questions please?
First is do I need to have my bootloader unlocked? I enabled OEM unlock setting in developer settings but that is only one thing I did.
And the second one is could this flash unlock my phone?
I am in this situation where my AT51 won't work with other sims except for Vodafone. UK.
I stayed with them for 30 days, (required time frame to get your phone unlocked) requested unlock code and it has been more than 10 working days but still have not received the code.
So today I did some searching online and found the service code to check if my phone is locked to a network and to my surprise it says it's not. So I am guessing that they have limited my phone to using only their sim through some other means andnot buy locking my modem. But this is ofc just a guess.
I kept chatting with the customer support and he keeps saying wait for the code which I do not believe is going to come, they have to unlock it on their end. But I am not sure about that. I don't think they are sure either..
Basically I'll wait fem more days maybe they will unlock it but if they won't when I am thinking maybe my modem is not locked and I could unlock it by flashing different ROM?
Or do you think this won't work?
Sorry for a rambling post. Looking forward to your reply. Thanks!

Mazvydelis said:
Thanks for the guide!
Can I ask few questions please?
First is do I need to have my bootloader unlocked? I enabled OEM unlock setting in developer settings but that is only one thing I did.
And the second one is could this flash unlock my phone?
I am in this situation where my AT51 won't work with other sims except for Vodafone. UK.
I stayed with them for 30 days, (required time frame to get your phone unlocked) requested unlock code and it has been more than 10 working days but still have not received the code.
So today I did some searching online and found the service code to check if my phone is locked to a network and to my surprise it says it's not. So I am guessing that they have limited my phone to using only their sim through some other means andnot buy locking my modem. But this is ofc just a guess.
I kept chatting with the customer support and he keeps saying wait for the code which I do not believe is going to come, they have to unlock it on their end. But I am not sure about that. I don't think they are sure either..
Basically I'll wait fem more days maybe they will unlock it but if they won't when I am thinking maybe my modem is not locked and I could unlock it by flashing different ROM?
Or do you think this won't work?
Sorry for a rambling post. Looking forward to your reply. Thanks!
Click to expand...
Click to collapse
You do not need the bootloader unlocked as you are flashing official firmware.

Anyone know if you can flash a XQ-AT52 to a XQ-AT51 and then back to the XQ-AT52 firmware?
Sent from my XQ-AT52 using Tapatalk

I know this thread is a few months old at this point but I'm really struggling to flash to XQ-AT51. I've successfully flashed from XQ-AT52 Hong Kong (my original firmware) to the Taiwan version which is slightly better because of the messaging compatibility but I really want to get the US version. I have tried at least 20 times over the course of a full day and I have not been able to flash the US firmware without getting an error saying "Your device is corrupt It can't be trusted and will not boot" every time. I have repaired it back to the Hong Kong firmware (back when that was the one I had) and to the Taiwan version once I had that installed. But I have never gotten the US firmware to take without the "Device is corrupt" error.
My phone is the Sony xperia 1 mark 2 running the then default XQ-AT52 Hong Kong, and now running the default XQ-AT52 Taiwan. I've been trying to flash to XQ-AT51 US. I've been using newflasher v39 and the US firmware downloaded for xperifirm v 5.5.0.

So I was able to flash from the hong kong version to the Taiwan version and back with no issues at all. But I'm still unable to flash to the US version without the "Your device is corrupt It can't be trusted and will not boot" error that seems to happen every single time I try to install the US firmware.

Can someone make me a favor and can upload the latest ftf of Android 10 for the Xperia 1ii Single SIM?

ProjectBlitz said:
So I was able to flash from the hong kong version to the Taiwan version and back with no issues at all. But I'm still unable to flash to the US version without the "Your device is corrupt It can't be trusted and will not boot" error that seems to happen every single time I try to install the US firmware.
Click to expand...
Click to collapse
The 1 II has downgrade protection, so as long as the firmware version of the US version isn't the same or newer than the highest version you've ever used you're gonna get the corruption error.
What you could try is flashing the newer EU version and then flashing only the older US customisation image. That's what I did for a while since US firmware was older than EU firmware, and it worked. Not sure if it'll work with Android 11.

ProjectBlitz said:
I know this thread is a few months old at this point but I'm really struggling to flash to XQ-AT51. I've successfully flashed from XQ-AT52 Hong Kong (my original firmware) to the Taiwan version which is slightly better because of the messaging compatibility but I really want to get the US version. I have tried at least 20 times over the course of a full day and I have not been able to flash the US firmware without getting an error saying "Your device is corrupt It can't be trusted and will not boot" every time. I have repaired it back to the Hong Kong firmware (back when that was the one I had) and to the Taiwan version once I had that installed. But I have never gotten the US firmware to take without the "Device is corrupt" error.
My phone is the Sony xperia 1 mark 2 running the then default XQ-AT52 Hong Kong, and now running the default XQ-AT52 Taiwan. I've been trying to flash to XQ-AT51 US. I've been using newflasher v39 and the US firmware downloaded for xperifirm v 5.5.0.
Click to expand...
Click to collapse
im in the us and was looking to the 256gb version (i think its taiwan). is the hong kong or taiwan version missing anything? or is the only reason to flash to US to get better coverage with us carriers?

GreeleyXda said:
im in the us and was looking to the 256gb version (i think its taiwan). is the hong kong or taiwan version missing anything? or is the only reason to flash to US to get better coverage with us carriers?
Click to expand...
Click to collapse
It's for better coverage and for VoLTE and Wi-Fi calling support. Also if you get a HK one with Android 11 you will be unable to flash the US firmware, because it is still on Android 10; and the phone has anti-rollback protection.

it arrived on 10 still, but its bugging me to update.

THISISINSANE said:
It's for better coverage and for VoLTE and Wi-Fi calling support. Also if you get a HK one with Android 11 you will be unable to flash the US firmware, because it is still on Android 10; and the phone has anti-rollback protection.
Click to expand...
Click to collapse
This isn't the case now since the US models have Android 11 too now

Can anyone confirm that this process has to be done using USB 2.x? I've read in a separate post that newflasher isn't compatible with USB 3.x, which is currently what all my computer use. Also, should I be using the newest version newflasher?
EDIT: Tried on USB 2.0 and it worked perfectly.

Related

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...

Unlocking vs Unlocked Device

I purchased an att gs9+ directly from samsung, after that, I installed the unlocked firmware. Up to this point, I have used an att sim. When I tried to use a tmobile sim recently, I got a message saying "Invalid SIM card inserted - This SIM card is not supported. I was surprised as I thought it was unlocked since I installed the firmware. I then tried to install a version of the ATT firmare thinking I perhaps still needed to unlock it? At any rate, I tried but ODIN gave me the following error: FAIL!(auth).
So, first question is - If I installed unlocked firmware on my att gs9+, is it truly unlocked?
Second question, can I install the att version back again? Or perhaps the tmobile?
Finally - what does the ODIN error mean?
Thanks for taking the time to read,
Ben
benjiesell said:
I purchased an att gs9+ directly from samsung, after that, I installed the unlocked firmware. Up to this point, I have used an att sim. When I tried to use a tmobile sim recently, I got a message saying "Invalid SIM card inserted - This SIM card is not supported. I was surprised as I thought it was unlocked since I installed the firmware. I then tried to install a version of the ATT firmare thinking I perhaps still needed to unlock it? At any rate, I tried but ODIN gave me the following error: FAIL!(auth).
So, first question is - If I installed unlocked firmware on my att gs9+, is it truly unlocked?
Second question, can I install the att version back again? Or perhaps the tmobile?
Finally - what does the ODIN error mean?
Thanks for taking the time to read,
Ben
Click to expand...
Click to collapse
SIM unlock is a completely separate thing which you'd need to use an unlocking service for, nothing to do with the firmware
Check the bootloader version your phone is running now, vs the one you're trying to flash, you cannot downgrade the BL
Download mode will show BL:1 or BL:2)
Firmware shows it here
G960FXXU2BRGA
Flash an equal or higher BL
*Detection* said:
SIM unlock is a completely separate thing which you'd need to use an unlocking service for, nothing to do with the firmware
Check the bootloader version your phone is running now, vs the one you're trying to flash, you cannot downgrade the BL
Download mode will show BL:1 or BL:2)
Firmware shows it here
G960FXXU2BRGA
Flash an equal or higher BL
Click to expand...
Click to collapse
Ok, thanks for the response.
I can see that my bootloader version is 3. I dont see any ATT versions out there for 3 though. Am I correct in thinking that I would need an ATT firmware to even get the sim card unlock prompt? Thats really the issue for me.. I am unable to unlock the device despite trying to reinsert, and running those #XXX*# codes.
benjiesell said:
Ok, thanks for the response.
I can see that my bootloader version is 3. I dont see any ATT versions out there for 3 though. Am I correct in thinking that I would need an ATT firmware to even get the sim card unlock prompt? Thats really the issue for me.. I am unable to unlock the device despite trying to reinsert, and running those #XXX*# codes.
Click to expand...
Click to collapse
nvm...Im not sure if by dumb luck, or putting on several firmwares and clearing things out.. it finally prompted me. wtf...
Thanks for the advice. I learned a few things about the firmware.
benjiesell said:
nvm...Im not sure if by dumb luck, or putting on several firmwares and clearing things out.. it finally prompted me. wtf...
Thanks for the advice. I learned a few things about the firmware.
Click to expand...
Click to collapse
Good stuff :good:

S9 Message Your current software version isn't supported. Visit a service centre

Hi first post, please be gentle
I've got an s9 which is on EE UK, I flashed the phone with stock firmware, I did run into a couple of issues where when flashing the phone it got stuck on odm.img so I had to start again but using CSC and not home CSC so I lost everything
When the phone rebooted, it started up in German, so as I had my sim card in, it restarted in English
I'm using the following
G960FXXU2CSA2/G960FOXM2CSA2/G960FXXS2BRK3
Service provider SW SAOMC_SM-G960F_OXM_DBT_PP_0009
DBT/XEU/EVR
When I check for updates I get the following
Your current software version isn't supported. Visit a service centre
Can anyone help on how to put this right, I want to stay on stock firmware, not EE firmware
Thanks in advance
Good morning, I have a problem with my S9 model G9600 which came from the factory with the firmware of Hong Kong, however I tried to change the firmware for the one in Colombia because some voice services of the operators only work with the software of the country. But when trying to flash the part of CSC I mark the error and obviously the installation fails as in a kind of A brick because the logo of Galaxy S9 does not pass and is only solved by reinstalling the firmware with which it came from the factory; I have already made sure that the binary is the same, however I can not find a solution. I attach photos of the error.
dancevision said:
Hi first post, please be gentle
I've got an s9 which is on EE UK, I flashed the phone with stock firmware, I did run into a couple of issues where when flashing the phone it got stuck on odm.img so I had to start again but using CSC and not home CSC so I lost everything
When the phone rebooted, it started up in German, so as I had my sim card in, it restarted in English
I'm using the following
G960FXXU2CSA2/G960FOXM2CSA2/G960FXXS2BRK3
Service provider SW SAOMC_SM-G960F_OXM_DBT_PP_0009
DBT/XEU/EVR
When I check for updates I get the following
Your current software version isn't supported. Visit a service centre
Can anyone help on how to put this right, I want to stay on stock firmware, not EE firmware
Thanks in advance
Click to expand...
Click to collapse
You need to flash the XEU firmware, you have the German DBT firmware running right now
same issue, i have a hungarian telenor phone which suppoesed to be (PAN) , i flashed XEH which is hungarian, but it said software version not supported visit a support center , so i flashed the PAN 9.0 version and it still says this
Did you find any solution for this?
Bizzhub said:
Did you find any solution for this?
Click to expand...
Click to collapse
are you having an identical issue? i ask that because resolutions are very specific. Flashing firmware from www.sammobile.com/firmwares is very commonly the fix for a great many issues, but id hate to have you go thru the trouble of doing so if its not necessary
I tried flashing using odin but didnt work. btw, im using SM-965U and currently residing in Thailand. I dont know if this is the reason why I cant update at all.
S9 message
I am in the U.S. and am getting the message that software isn't supported also. Is there any resolution to this problem?
In case it helps, I was having this same issue with my unlocked Galaxy Note 10+. I found this thread after searching. I had gotten into this situation by flashing CP/AP/BL from TMO firmware without also flashing TMO's CSC or USERDATA. I avoided CSC/USERDATA (I was using the home CSC) because I wanted to avoid wiping the phone.
When I finally gave up and flashed CSC and USERDATA, everything was back to normal.
hueboy said:
I am in the U.S. and am getting the message that software isn't supported also. Is there any resolution to this problem?
Click to expand...
Click to collapse
have you tried flashing the stock firmware via Odin?
ThugEsquire said:
In case it helps, I was having this same issue with my unlocked Galaxy Note 10+. I found this thread after searching. I had gotten into this situation by flashing CP/AP/BL from TMO firmware without also flashing TMO's CSC or USERDATA. I avoided CSC/USERDATA (I was using the home CSC) because I wanted to avoid wiping the phone.
When I finally gave up and flashed CSC and USERDATA, everything was back to normal.
Click to expand...
Click to collapse
thats usually the fix. Glad you got it working
Bizzhub said:
I tried flashing using odin but didnt work. btw, im using SM-965U and currently residing in Thailand. I dont know if this is the reason why I cant update at all.
Click to expand...
Click to collapse
what is the issue after you flash in Odin?

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 should I move to an unbranded global ROM?

I'm trying to root and update my friends T-Mobile 7T (HD1907) to the most recent generic ROM. She's leaving the country and has no need or desire to keep the T-Mobile branding, and getting on a generic ROM seems like it will allow for faster updates.
I've seen some threads that look like they might help, but having had issues in the past with other attempts on other phones, I know that one little oversight can cause HOURS of frustration.
So I figured I'd ask first and try to save the drama this time.
Where can I get the correct ROM to do what I want on this phone?
I have TWRP installed and have rooted with Magisk.
Current build # is 10.0.3 HD63CB
Carrier configuration version is 2.370001
I appreciate any help on this, thanks!
JustinChase said:
I'm trying to root and update my friends T-Mobile 7T (HD1907) to the most recent generic ROM. She's leaving the country and has no need or desire to keep the T-Mobile branding, and getting on a generic ROM seems like it will allow for faster updates.
I've seen some threads that look like they might help, but having had issues in the past with other attempts on other phones, I know that one little oversight can cause HOURS of frustration.
So I figured I'd ask first and try to save the drama this time.
Where can I get the correct ROM to do what I want on this phone?
I have TWRP installed and have rooted with Magisk.
Current build # is 10.0.3 HD63CB
Carrier configuration version is 2.370001
I appreciate any help on this, thanks!
Click to expand...
Click to collapse
[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!
Here is a patched MSM download tool for TMobile OP7T. It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the...
forum.xda-developers.com
The key is to force reboot into bootloader mode when u get stuck on pink T-Mobile bootscreen after first "flash-all" script so u can repeat this "flash-all" second try which will then work.
Thanks for that. I managed to unlock the bootloader and update to Oxygen OS 11.0.7.1.HD65AA, which I believe is the most recent global ROM.
The model of the phone still shows HD1907, which I thought should change from the T-Mobile model to the global model in this process, but perhaps this is normal.
Everything seems to be working fine, but I'm a bit concerned it won't update properly if its not entirely "converted" to the global model.
I did the same. All working fine though. It brought me unlocked bootloader to flash the dual sim firmware or global. All works. Only concern I have is ..The unlock bootloader ticker in dev options shows greyed out "Already Unlocked" but, the ticker is in the off position to the left which is odd. My friends was done by token but mine using patched boot msm. Any reason to be concerned ? Perhaps that's going to hinder the re lock and possible re unlock ?

Categories

Resources