Here's a free How-To on how i successfully Carrier/Sim unlocked my Samsung Galaxy S21 Ultra 5G running the NEWEST Android update on bootloader 5 (USQU5BULJ)released in January of 2022 that was carrier locked to Verizon and now fully Unlocked.
DISCLAIMER:
*This does NOT trip Knox or Void your warranty and does NOT require a root or a paid service. **This is the process I took, you may find some of these steps are not needed but for the purpose or recreating my results, I'll be posting my exact process.***This has ONLY BEEN TESTED ON SNAPDRAGON BASED SAMSUNG GALAXY S21 ULTRA 5G SM-G998 U & U1, if you try it on a different model or phone you may (and likely will) receive different results!!!!
You can read more on how this method works to force a carrier update to your device, here, on the Official Android dev site.
Here's what you'll need:
•ANY (activated or not) Sim from the carrier you wish to switch too.(or a way to replicate the carriers cert from one)
•A computer
•Patched Odin
•BOTH the NEWEST U & U1 ROMs/Firmware - theres a full post on these and how to flash them here, Stock Firmware and ODIN Flashing Guide (XDA) or visit SamFW.com, it has both Odin and the ROM/Firmware files you will need.
•(Optional?) Android ADB platform tools (You can find them on the official Android Developers page here or use any ADB software of your choice, fastboot is not required or used in this process. Link: Android Dev Platform Tools (Official)
Step 1:
So let's presume you have a Verizon or T-Mobile carrier locked phone, if you look at your baseband, which you can find in Settings > About > Software Info, you should see this "SM-G998Uxxxxxxx"
NOTE:
It Is CRITICAL that we flash the U1 rom BEFORE putting in the desired carriers SIM, then reboot, let phone fully boot, ONLY THEN should we insert the desired carriers SIM.
Step 1b:
Head over to your preferred site to get stock Samsung Roms (Refer to link above if you don't know where to find) and download the U1 XAA rom and the U rom of the CARRIER YOU WISH TO USE.
IMPORTANT! MAKE SURE YOU DOWNLOAD BOTH THE "U" ROM FOR THE CARRIER YOU WISH TO SWITCH TO AND THE U1 UNLOCKED (XAA) ROM/Firmware.
IF YOU ALREADY HAVE U1 FIRMWARE
I.e "SM-G998U1xxxxxxx" - you can skip to step 2, but I would recommend reading through the next part.
Put you device in download mode (Hold Vol up and Vol down and plug in the USB, which should be connected to your PC and now your phone at this point.)
Flash the U1 XAA Rom, place appropriate files in appropriate places in Odin, when you get to CSC, DO NOT use the "HOME_CSC" use the other.
Leave the rest of Odin settings alone and hit Start, wait for it to finish and reboot.
Step 2:
Once the phone boots, return to Settings>About>Software and confirm the device is now showing the "U1_XAA" in the Service Provider Software Version - it should say something like "SM-G998U1_XAA blah blah blah" - you just want to see the "U1" bit.
Now put in the Sim from the carrier you desire. A pop-up should appear prompting you to restart your device.
! CRITICALLY IMPORTANT STEP !
We will now initiate a reboot, but BEFORE the device fully restarts, we need to force it into RECOVERY MODE, I was able to achieve this by holding the power and Vol Down buttons at the same time, starting to hold them directly after the "Samsung" Logo fades away upon initial restart. If you have trouble getting into recovery, please comment below.
Once in recovery, use the volume keys to navigate to "Clear Cache" select and execute. Now go to Factory Data Reset/Wipe, select and execute. It should be the option directly above "Clear cache".
Once done, go up to "Reboot to Bootloader", Select & Execute.
AGAIN, Very Important step! We MUST interrupt the boot process again and force the phone BACK into download mode this time, so once the phone attempts to reboot, we need to hold the Vol Down and Vol Up buttons at the same time and the USB MUST be already plugged in, essentially it should remain plugged in throughout this process.
We should now be back in download mode and be on "U1" as we have verified in the steps above.
STEP 3:
Now it's time to flash the ROM/Firmware from the carrier you wish to use. Make SURE you have the SIM from the same carrier inserted during this process as mentioned at the beginning. It doesn't need to be a working or activated SIM, just simply one from the carrier you wish to have this S21 work on.
Flash all items from the "U" ROM/Firmware as you did earlier, ensuring to use the "U" ROM/Firmware for your desired carrier as described above. Same deal with CSC here, DO NOT use the "Home_CSC", use the other.
BE SURE that you use the USERDATA file that comes with the "U" ROM/Firmware. Its Critical in order to get the phone working properly on the new carrier.
Start the Odin flashing process & wait.
Phone will Auto-Reboot.....
Done!
You should now be on the carrier you wish to use.
This can be (in theory, test at own risk) replicated for ANY carrier supported by Samsung.
Please comment your experiences/ issues etc below. Don't be afraid to ask for clarity of something.
PoC, results after doing above process pictured in this screenshot.
Good luck.
-k0mrade
Send me Crypto if I helped?
Before process, this message would appear shortly after inserting a new SIM in testing devices:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After preforming above procedures I now find pictured below by running this activity:
com.samsung.ssu.unlock.MainActivity
And verify twice by checking my work in Settings>About>Software Information> Service Provider Software Version & Carrier Configuration Version.
For anyone whos still having trouble, try following the directions on this thread. Maybe they explain it a bit better or their process omits/includes parts ive missed.
Alternative Guide To Carrier Unlocking S21
Good Luck.
-
Have you attempted this on lower bootloader revisions?
iBowToAndroid said:
Have you attempted this on lower bootloader revisions?
Click to expand...
Click to collapse
I have not. But am very interested to see how it goes if you or anyone decides to give it a shot, it SHOULD work on any BL considering the method of attack. But I can't verify it does.
Hello. I did everything as in the guide. I downloaded U1 firmware for XAA, but for some reason CCT remains on the phone. Also in the step where to insert the Sim, my phone does not ask me to reboot the device.
xDpakaX said:
Hello. I did everything as in the guide. I downloaded U1 firmware for XAA, but for some reason XAS remains on the phone. Also in the step where to insert the Sim, my phone does not ask me to reboot the device.
Click to expand...
Click to collapse
Have you tried doing a normal reboot and forcing into recovery first, wipe cache, factory reset, reboot to Bootloader, then before full boot force into download mode with your SIM from the carrier you want to go to already inserted and downloading the "U" Firmware for the carrier you want and flashing it? What does Odin and/or your Baseband in settings say after doing above e process?
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Proverbs2 said:
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Click to expand...
Click to collapse
What's the Baseband Version?
iBowToAndroid said:
What's the Baseband Version?
Click to expand...
Click to collapse
@Proverbs2 it can be done with a computer, but not with the method listed above. It would have to be done by a professional business that offers SIM unlocking, so it wouldn't be free. If you want to have it done, don't do any more software updates until after it's unlocked
iBowToAndroid said:
@Proverbs2 it can be done with a computer, but not with the method listed above. It would have to be done by a professional business that offers SIM unlocking, so it wouldn't be free. If you want to have it done, don't do any more software updates until after it's unlocked
Click to expand...
Click to collapse
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Proverbs2 said:
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Click to expand...
Click to collapse
Yep then you're screwed. It can't done if Knox is tripped
Proverbs2 said:
Thanks for the guide! Is there any chance this process might also work on other phones? I have a Samsung Galaxy XCover Pro that I've been trying to unlock for months. I've called Verizon many times, and they claim they already unlocked it, but when I put another sim in I still get the message "Sorry, your device can't be activated on another carrier's network right now. For help, contact Verizon at (800) 922-0204 or (888) 294-6804 (prepaid plans)."
Click to expand...
Click to collapse
Hmm I have not tried it, but, in all reality, I used this exact same method YEARS ago on my S7 Edge and it worked then. I have not tried it on another Samsung but I'd imagine anything other then the newest flagship would probably be quite simple to fix as there should already plenty of resources available via Github and such. If you take it on let me know, I'll do what I can to help.
If you want to test it out on your device, i see no reason why it shouldnt work if done correctly, but you may have to play with the order in which you interrupt the bootloader and force the update. Even if you have tripped Knox, there is indeed a way to completely disable Knox all together and not get locked out of the device. I did it on the S21 that I unlocked when I was mucking about on the phone. But that's an entire different tutorial and I'd need people to test it on other Samsung devices. But I'd be happy to share that too if you'd like.
Proverbs2 said:
Thanks! I tried paying a service to unlock it already, but they were unable to unlock it and refunded my money. I unlocked the bootloader and rooted the phone before getting the sim unlocked, unfortunately, so none of the usual methods seem to work.
Click to expand...
Click to collapse
Is it still unlocked and rooted? That would make life another easier. We can repair the IMEI, baseband etc. It's worth a go if the phones just a paper weight right now imo. But ultimately up to you.
K0mraid3 said:
Hmm I have not tried it, but, in all reality, I used this exact same method YEARS ago on my S7 Edge and it worked then. I have not tried it on another Samsung but I'd imagine anything other then the newest flagship would probably be quite simple to fix as there should already plenty of resources available via Github and such. If you take it on let me know, I'll do what I can to help.
If you want to test it out on your device, i see no reason why it shouldnt work if done correctly, but you may have to play with the order in which you interrupt the bootloader and force the update. Even if you have tripped Knox, there is indeed a way to completely disable Knox all together and not get locked out of the device. I did it on the S21 that I unlocked when I was mucking about on the phone. But that's an entire different tutorial and I'd need people to test it on other Samsung devices. But I'd be happy to share that too if you'd like.
Click to expand...
Click to collapse
Thank you! I'll give it a try and report how it goes.
Good luck! Worst case, look up a program called "Samsung TFT Module", just be sure to scan it for viruses and bad code if you have the ability.unless you are able to find the 2022 update of it, you'll have to settle for whatever version is available. It'll likely be old, clunky and out-of-date, half the program defunct, but a few key parts still work, and quite well. Don't forget ADB drivers. Let us know how it goes!
Proverbs2 said:
Thank you! I'll give it a try and report how it goes.
Click to expand...
Click to collapse
Ok, I tried to follow each step carefully, but I had to make one minor change to the procedure: after flashing the U1_XAA firmware, I had to power off the phone in order to insert the SIM card. (In the XCover Pro, the SIM card slot is obstructed by the battery, so there is no way to insert the card without powering off the phone and removing the battery.) After inserting the card, I booted directly into recovery and followed the other steps from there.
Unfortunately, it didn't work for me: the phone is still locked, showing the same message: "Sorry, your device can't be activated on another carrier's network..." Perhaps that's because I wasn't able to perform that one critical step, inserting the sim card while the phone is turned on. Any suggestions for a workaround?
K0mraid3 said:
Have you tried doing a normal reboot and forcing into recovery first, wipe cache, factory reset, reboot to Bootloader, then before full boot force into download mode with your SIM from the carrier you want to go to already inserted and downloading the "U" Firmware for the carrier you want and flashing it? What does Odin and/or your Baseband in settings say after doing above e process?
Click to expand...
Click to collapse
Yes, I followed the guide. The problem is that when I'm on U1 my phone doesn't ask me to reboot.
Hello. I did all on VZW SQU3AUDB phone. Did all steps.
I have question. But in first start after step 3 (i flash G998U VZW) i see: Sorry, your devic.... verizon message
STEP3: Now it's time to flash the ROM/Firmware from the carrier you wish to use
It min - i need to flash not VZW ROM? some other? I need to use Ukrainia operator sim. Or i need flash G998W or else?
can someone help me?
Does my bootloader need to be unlocked
Related
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
One thing I wanna ask everyone here: Amazon also sells the 6GB int'l version (H9493) of the XZ3 for cheaper than the U.S. one, and this site seems to confirm that it not only has all the exact same bands one would need for T-Mobile (2, 4, and 12) and prob AT&T too, but also VoLTE. It's also a Dual SIM version too, though I would only ever use one SIM card.
But if the bands are all the same ones we use in the U.S., would we need to flash it with the U.S. software??
RockStar2005 said:
One thing I wanna ask everyone here: Amazon also sells the 6GB int'l version (H9493) of the XZ3 for cheaper than the U.S. one, and this site seems to confirm that it not only has all the exact same bands one would need for T-Mobile (2, 4, and 12) and prob AT&T too, but also VoLTE. It's also a Dual SIM version too, though I would only ever use one SIM card.
But if the bands are all the same ones we use in the U.S., would we need to flash it with the U.S. software??
Click to expand...
Click to collapse
If US software is not needed, that's is perfect. Anyone can confirm please?
tiunilohmu said:
If US software is not needed, that's is perfect. Anyone can confirm please?
Click to expand...
Click to collapse
I'm not saying I know for sure, but it APPEARS that all the models, or at least the single SIM H8416 and the dual SIM H9493 (both are sold on U.S. Amazon) have the same radio bands. The H8416 that I got off Amazon was supposed to be the "U.S. version" (with warranty), but when I got it, despite the LTE reception status being int'l and not U.S. in terms of looks (4G shows as LTE, 4G LTE shows as LTE+), VoLTE still works, and I definitely am getting all the T-Mobile bands at least (2, 4, and 12). So that is why I'm asking this? It APPEARS that all the models of the XZ3 have the same radio bands again, so yeah.
RockStar2005 said:
I'm not saying I know for sure, but it APPEARS that all the models, or at least the single SIM H8416 and the dual SIM H9493 (both are sold on U.S. Amazon) have the same radio bands. The H8416 that I got off Amazon was supposed to be the "U.S. version" (with warranty), but when I got it, despite the LTE reception status being int'l and not U.S. in terms of looks (4G shows as LTE, 4G LTE shows as LTE+), VoLTE still works, and I definitely am getting all the T-Mobile bands at least (2, 4, and 12). So that is why I'm asking this? It APPEARS that all the models of the XZ3 have the same radio bands again, so yeah.
Click to expand...
Click to collapse
Thanks for your info. Have you tried yours with at&t?
YW!
I haven't, but I started this thread which discusses both AT&T and T-Mobile and the XZ3. I suggest you check it out! Though it mainly looks at the single SIM H8416 version.
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
I have this model on AT&T but haven't flashed the US firmware. VoLTE is not available on the Taiwan firmware.
tiunilohmu said:
I'm planning to get H9493, 6gb ram model. I'm wondering can i flash the US firmware on it? (for At&t VoLTE)
Click to expand...
Click to collapse
I don't think you can flash it. The H9493 is a dual sim model (please correct if I'm wrong), and on Xperifirm there is no Customized US version for it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And since it's a dual sim model, and you try flashing a single sim one, you won't be able to obviously use your 2nd sim. If that's not an issue for you, then I guess you can try it.
iArvee said:
I don't think you can flash it. The H9493 is a dual sim model (please correct if I'm wrong), and on Xperifirm there is no Customized US version for it.
And since it's a dual sim model, and you try flashing a single sim one, you won't be able to obviously use your 2nd sim. If that's not an issue for you, then I guess you can try it.
Click to expand...
Click to collapse
Very interesting!!
Yeah that's the thing, I could care less about using a 2nd SIM. I only need 1 and of course MicroSD card.
So you think it would work then, even though it's a Dual SIM phone?
RockStar2005 said:
Very interesting!!
Yeah that's the thing, I could care less about using a 2nd SIM. I only need 1 and of course MicroSD card.
So you think it would work then, even though it's a Dual SIM phone?
Click to expand...
Click to collapse
I read threads on the XZP forum about people flashing the single sim firmware on their dual sim phone. What I've gained from that is the phone will still work, minus the functionality for the 2nd sim, since the modem configs are different. I haven't tried it myself, don't see any harm in trying it anyway.
iArvee said:
I read threads on the XZP forum about people flashing the single sim firmware on their dual sim phone. What I've gained from that is the phone will still work, minus the functionality for the 2nd sim, since the modem configs are different. I haven't tried it myself, don't see any harm in trying it anyway.
Click to expand...
Click to collapse
Ok great! You da MAN iArvee! LOL :good:
Can you explain the process of flashing? How difficult is it? Does it involve rooting or unlocking bootloaders?? God I hope not. lol
I don't have an issue with Sony Companion as I've used it before though. But I'll admit I'm intimidated by anything complicated. I once unlocked the bootloader, rooted, and S-OFF'd my old HTC One M8. It wasn't fun. LOL
RockStar2005 said:
Ok great! You da MAN iArvee! LOL :good:
Can you explain the process of flashing? How difficult is it? Does it involve rooting or unlocking bootloaders?? God I hope not. lol
I don't have an issue with Sony Companion as I've used it before though. But I'll admit I'm intimidated by anything complicated. I once unlocked the bootloader, rooted, and S-OFF'd my old HTC One M8. It wasn't fun. LOL
Click to expand...
Click to collapse
It's fairly simple compared to other OEMs. You don't need to unlock the bootloader nor need root. It's as easy as downloading the firmware, repacking it, then flashing it. The easiest way to flash is using Flashtool, however I don't think that flashtool has been updated yet to support the XZ3.
There is another way using newflasher, no need to repack the firmware. Just place the .exe file in the folder of the downloaded firmware and flash. While it's the same as Flashtool, I prefer flashtool because there are settings you can change (if you want).
iArvee said:
It's fairly simple compared to other OEMs. You don't need to unlock the bootloader nor need root. It's as easy as downloading the firmware, repacking it, then flashing it. The easiest way to flash is using Flashtool, however I don't think that flashtool has been updated yet to support the XZ3.
There is another way using newflasher, no need to repack the firmware. Just place the .exe file in the folder of the downloaded firmware and flash. While it's the same as Flashtool, I prefer flashtool because there are settings you can change (if you want).
Click to expand...
Click to collapse
Ok. That doesn't sound too bad then. And AWESOME on no bootloader or root stuff! lol
But how did you do it then if Flashtool (which I HAVE heard of) doesn't support the XZ3 then?
Ok let's just say I use newflasher. That sounds MUCH easier! lol I'm assuming it's good then for the XZ3 right? Also, what's the link for the U.S. firmware please?
So I connect my phone to my PC.........put the downloaded firmware "folder" into say the root directory of my Xperia, then put in newsflasher.exe into that folder, and double-click on it (exe)? This is what the instructions here on XDA say to do. But it also (Step 2) says something about putting my phone into "flash mode"? WTF is that? lol Do I have to do that? If so, how??
Well, what settings does Flashtool allow you to change? I just wanna see if it's worth it to deal with it if I don't have to. lol
Thanks!!!!!!!
RockStar2005 said:
Ok. That doesn't sound too bad then. And AWESOME on no bootloader or root stuff! lol
But how did you do it then if Flashtool (which I HAVE heard of) doesn't support the XZ3 then?
Ok let's just say I use newflasher. That sounds MUCH easier! lol I'm assuming it's good then for the XZ3 right? Also, what's the link for the U.S. firmware please?
So I connect my phone to my PC.........put the downloaded firmware "folder" into say the root directory of my Xperia, then put in newsflasher.exe into that folder, and double-click on it (exe)? This is what the instructions here on XDA say to do. But it also (Step 2) says something about putting my phone into "flash mode"? WTF is that? lol Do I have to do that? If so, how??
Well, what settings does Flashtool allow you to change? I just wanna see if it's worth it to deal with it if I don't have to. lol
Thanks!!!!!!!
Click to expand...
Click to collapse
I used newflasher.
That's the wrong link for flashtool. Here's the correct one: https://forum.xda-developers.com/showthread.php?t=920746
You can download the firmware using a software called Xperifirm. The settings that Flashtool allows you to change is keep userdata, basically just flash the firmware but leave your installed apps, documents, whatever is on the internal storage intact (and more settings, but that's basically the gist of the settings). You can do that also using newflasher, however since there's no settings menu, you have to just not include a few files.
Flash mode is done by turning your phone off, then holding volume down while plugging your phone in to the PC. Once the notification LED turns green, that means it's in flash mode.
iArvee said:
I used newflasher.
That's the wrong link for flashtool. Here's the correct one: https://forum.xda-developers.com/showthread.php?t=920746
You can download the firmware using a software called Xperifirm. The settings that Flashtool allows you to change is keep userdata, basically just flash the firmware but leave your installed apps, documents, whatever is on the internal storage intact (and more settings, but that's basically the gist of the settings). You can do that also using newflasher, however since there's no settings menu, you have to just not include a few files.
Flash mode is done by turning your phone off, then holding volume down while plugging your phone in to the PC. Once the notification LED turns green, that means it's in flash mode.
Click to expand...
Click to collapse
Oh ok. Then I will use Newsflasher too! No repacking?? I'm IN!! LOL
Yeah I just had a random site for Flashtool bookmarked from a while ago. I'll remove it.
Ahh I see. Well I'd rather just do a clean flash. Less chance of issues. lol
Ok so using PC I download U.S. H9493 firmware folder (please confirm that is best site), and yes I know to find H9493 firmware now, and Newsflasher. Put Newsflasher.exe file INTO the firmware folder, then connect phone (turned off) to my PC via USB WHILE pressing the volume DOWN button until the green notification LED light on my XZ3 turns on. Then let it flash by double-clicking newsflasher.exe, and then after it's done, check log file for any errors, then unplug phone and start it up! And then finally put it through Sony Companion ("Software Repair") ftw for extra assurance. Sounds right??
Will Sony Companion know or detect the U.S. firmware? If I do a software repair, will it vary how it does that by model, or is the process the same for all models? I know you did it but you did it on the U.S. H8416 version. Do I have anything to worry about there? I'm guessing no since all the radio bands & VoLTE option are in all 3 models. But let me know if you think I should skip this or just do it.
RockStar2005 said:
Oh ok. Then I will use Newsflasher too! No repacking?? I'm IN!! LOL
Yeah I just had a random site for Flashtool bookmarked from a while ago. I'll remove it.
Ahh I see. Well I'd rather just do a clean flash. Less chance of issues. lol
Ok so using PC I download U.S. H9493 firmware folder (please confirm that is best site), and yes I know to find H9493 firmware now, and Newsflasher. Put Newsflasher.exe file INTO the firmware folder, then connect phone (turned off) to my PC via USB WHILE pressing the volume DOWN button until the green notification LED light on my XZ3 turns on. Then let it flash by double-clicking newsflasher.exe, and then after it's done, check log file for any errors, then unplug phone and start it up! And then finally put it through Sony Companion ("Software Repair") ftw for extra assurance. Sounds right??
Will Sony Companion know or detect the U.S. firmware? If I do a software repair, will it vary how it does that by model, or is the process the same for all models? I know you did it but you did it on the U.S. H8416 version. Do I have anything to worry about there? I'm guessing no since all the radio bands & VoLTE option are in all 3 models. But let me know if you think I should skip this or just do it.
Click to expand...
Click to collapse
Basically just leave everything in if you'll do a clean flash.
Download the one from XDA: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Sounds right! Just make sure you install the XZ3 drivers. Google Xperia XZ3 drivers. Should be a sony developer link. Yes, Xperia Companion will know what firmware you are on. When you do a software repair, it will just redownload and reflash whatever firmware is on your phone. However, if you flash the single sim version, I'm not sure if that will work on Xperia Companion. Again, you can try!
I'd just do it. It's really hard to brick Xperia phones. If you do something wrong, you can always just reflash again. But don't take my word for it. I've been rooting, flashing, created some mods, and have a lot of experience with Xperia phones since 2014. I'm just speaking from experience.
iArvee said:
Basically just leave everything in if you'll do a clean flash.
Download the one from XDA: https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Sounds right! Just make sure you install the XZ3 drivers. Google Xperia XZ3 drivers. Should be a sony developer link. Yes, Xperia Companion will know what firmware you are on. When you do a software repair, it will just redownload and reflash whatever firmware is on your phone. However, if you flash the single sim version, I'm not sure if that will work on Xperia Companion. Again, you can try!
I'd just do it. It's really hard to brick Xperia phones. If you do something wrong, you can always just reflash again. But don't take my word for it. I've been rooting, flashing, created some mods, and have a lot of experience with Xperia phones since 2014. I'm just speaking from experience.
Click to expand...
Click to collapse
Ok I'll use your link. It looks exactly the same as what I got but no big deal. lol
Ok I found this for the drivers. Approve? But wait, when do I install them? lol That was never mentioned. So it's an additional step?
Ok. Well I'd be flashing the Dual H9493 version, not single, so it should be fine, right?
Yes I'll just reflash if not working right after completing the flashing process.
Thanks for all that!
RockStar2005 said:
Ok I'll use your link. It looks exactly the same as what I got but no big deal. lol
Ok I found this for the drivers. Approve? But wait, when do I install them? lol That was never mentioned. So it's an additional step?
Ok. Well I'd be flashing the Dual H9493 version, not single, so it should be fine, right?
Yes I'll just reflash if not working right after completing the flashing process.
Thanks for all that!
Click to expand...
Click to collapse
The drivers aren't automatically installed (well the right ones anyway) so it's best to install them yourself. Download the ZIP (yes thats the correct link), extract the zip, right click on the INF file, then click install.
Yep, should be fine.
iArvee said:
The drivers aren't automatically installed (well the right ones anyway) so it's best to install them yourself. Download the ZIP (yes thats the correct link), extract the zip, right click on the INF file, then click install.
Yep, should be fine.
Click to expand...
Click to collapse
So I would do that AFTER completing the flashing process and Companion part too?
Ok thanks!
RockStar2005 said:
So I would do that AFTER completing the flashing process and Companion part too?
Ok thanks!
Click to expand...
Click to collapse
Are you flashing the H9493?
Please let us know how it goes. If possible test out at&t too.
I recently bought what was supposed to be a "NEW Unlocked" Note 8 from seller on Ebay and when it arrived, I noticed that it was a few updates behind so I connected it to my WiFi and attempted to update it, but I received this error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I contacted the seller, but they were not helpful at all, so I installed the Phone INFO ★SAM★ app by vndnguyen to research the issue myself. The information the app provided was really confusing to say the least. First of all, the phones settings menu shows that the phones model number is SM-950U (US Market).
The model number provided by app however is SM-9500 (Chinese / Hong Kong Market)
Adding to that confusion, the phone seems to have both US and Chinese firmware components installed on it as shown by the following screenshot:
The CSC codes all seem to point to the phone originally being created for the Hong Kong market as shown in this screenshot:
However, when I checked the phones IMEI number, it comes back that it was originally a T-Mobile phone. Maybe that was just the last carrier that the IMEI was registered to I am not 100% certain about this, but there is definitely something very odd about this phone and so my questions are:
1.) Is there anyway (without tearing the phone apart) to tell exactly what model this phone is (950U or 9500) ?
2.) Why would anyone alter the phone like this / what advantages are there to doing this ?
3.) Is there anyway to actually update this device ?
mtcellph said:
3.) Is there anyway to actually update this device ?
Click to expand...
Click to collapse
You could update it with odin. It looks like the update center downloaded the wrong update.
SnowFuhrer said:
You could update it with odin. It looks like the update center downloaded the wrong update.
Click to expand...
Click to collapse
Thanks for the reply, but I do not think this was done by a bad OTA update or anything like that. I think this was done intentionally because I bought a different Note 8 about a month ago from a different seller and it had this same issue so I think this is done on purpose. What that purpose is I am not sure about yet, but I hope someone can help answer that question. As far as using ODIN to update is concerned I first have to figure out what the real model of the phone is so I can flash the right firmware, but thanks again for the reply.
mtcellph said:
Thanks for the reply, but I do not think this was done by a bad OTA update or anything like that. I think this was done intentionally because I bought a different Note 8 about a month ago from a different seller and it had this same issue so I think this is done on purpose. What that purpose is I am not sure about yet, but I hope someone can help answer that question. As far as using ODIN to update is concerned I first have to figure out what the real model of the phone is so I can flash the right firmware, but thanks again for the reply.
Click to expand...
Click to collapse
I'm more worried about that phone being a knock-off fake! If it really was N950U it would absolutely not be able to have that firmware on it that's currently on it. Also if you try to install the real firmware it's more than likely going to brick it especially if it's fake because that firmware is just not right. I would immediately send it back and get your money back!!
MrMike2182 said:
I'm more worried about that phone being a knock-off fake! If it really was N950U it would absolutely not be able to have that firmware on it that's currently on it. Also if you try to install the real firmware it's more than likely going to brick it especially if it's fake because that firmware is just not right. I would immediately send it back and get your money back!!
Click to expand...
Click to collapse
I doubt it's fake, just had some alterations on it. @mtcellph to see the model of the phone, boot into download mode. It should say.
--
@MrMike2182
I already got a refund from Ebay and they told me to keep the phone too so I am not worried about bricking it or anything like that.
@SnowFuhrer
This is the information from my Download Mode screen:
It shows the Carrier as TMB (T-Mobile) which would in theory be a SM-N950U model device, but I hoping more for an actual model number so I could be sure. Any other way to get a more definite answer would be welcome.
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
UnBeATaBLe~PrO said:
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
Click to expand...
Click to collapse
You might be right, but I would still like to update it if possible because everything else works on the phone.
Again if anyone has any sort of advice on figuring this mystery out, I would love to hear it.
UnBeATaBLe~PrO said:
What probably happened is, They took a broken phone from 1 region and used the parts from another region to fix. Probably board stuff. That might explain why it has mix match info
Click to expand...
Click to collapse
I seen devices sold like this with the exact same setup. Usually done by third party refurbishers.
iceepyon said:
I seen devices sold like this with the exact same setup. Usually done by third party refurbishers.
Click to expand...
Click to collapse
So what is the use of it?
SnowFuhrer said:
So what is the use of it?
Click to expand...
Click to collapse
Most 3rd party device repair specialist would use working parts from similar devices to make a new device and sell it on for a profit.
The Phone INFO app did say it was a refurb which is the reason why Ebay let me keep it, but the mystery still remains. Is it a N9500 with N950U parts in it or vise versa?
Is there any sort of app / software that will work on a 9500 that will not work on a 950U? I did see the thread about unlocking using an app named 835crom.apk that will unlock the BL of a N9500 model, but apparently will just crash when ran on a N950U model, but it's from like 2017 and I am not trying to root or anything like that.
I simply want to update to the latest security patch available for the phone, but I first need to find out what firmware I need to flash to do that. Again any help in this are would be really appreciated.
From what I know the majority of the components used in the Note 8 are interchanged able with the exception of the SOC, motherboards and modems. While both the N9500 and the N950U run on the same SOC, they do not utilize the same modems. Which maybe what is causing your issue.
mtcellph said:
The Phone INFO app did say it was a refurb which is the reason why Ebay let me keep it, but the mystery still remains. Is it a N9500 with N950U parts in it or vise versa?
Is there any sort of app / software that will work on a 9500 that will not work on a 950U? I did see the thread about unlocking using an app named 835crom.apk that will unlock the BL of a N9500 model, but apparently will just crash when ran on a N950U model, but it's from like 2017 and I am not trying to root or anything like that.
I simply want to update to the latest security patch available for the phone, but I first need to find out what firmware I need to flash to do that. Again any help in this are would be really appreciated.
Click to expand...
Click to collapse
I really wouldn't flash anything to it period! Simply because you can't flash one hardware piece with the N9500 and then try to flash the N950U hardware piece because it doesn't work like that! If anything is going to work it would most likely be the unlocked N950U1 firmware but I would tread cautiously because if your modem needs N9500 and your board/CPU needs N950U it's just going to mess it up!
Edit: Also about wanting to update just for the security patch, it's highly unlikely that you'll EVER be the target of such security breaches.. Ask around, if you're not rooted it's seriously HIGHLY UNLIKELY!
If you knew what you were doing, you could flash the modem from one firmware and flash the rest from the motherboard model.
SnowFuhrer said:
If you knew what you were doing, you could flash the modem from one firmware and flash the rest from the motherboard model.
Click to expand...
Click to collapse
Yeah. But you would have to be extremely skilled in doing so.
Thanks for the replies and I don't really understand why this would be that complicated. It's obviously possible to mix & match the firmware on the phone and it still work (minus the non-updating issue) because that is how it is now, but from what everyone is saying it's a lot more difficult then just flashing the right firmware in ODIN, but I do not understand why and would appreciate some clarification on this.
If the hardware on both models is basically exactly the same thing with the exception of the modem and the current modem that is installed is from the US version, would I not just be able to flash the full US firmware using ODIN and call it a day? If not, why?
Right now the Baseband (modem) and Bootloader are both from the US model. The CSC (which could easily be changed later if I wanted / needed to do that) & PDA (which is basically just the android OS stuff) are from the Chinese model. I am far from an expert in this area but it seems that the PDA is the only thing that I would need to change or am I missing something ?
Finally, I should have included that the reason I NEED to get the security patch updated on the phone is because the firmware (CSC & PDA) that is installed on the phone now does not have VOLTE enabled/working on it and in a later security patch it does have it enabled/working & since I would be using the phone on the Verizon network I kind of have to have VOLTE or the phone will not work once they turn off 2G/3G in the near future.
mtcellph said:
Thanks for the replies and I don't really understand why this would be that complicated. It's obviously possible to mix & match the firmware on the phone and it still work (minus the non-updating issue) because that is how it is now, but from what everyone is saying it's a lot more difficult then just flashing the right firmware in ODIN, but I do not understand why and would appreciate some clarification on this.
If the hardware on both models is basically exactly the same thing with the exception of the modem and the current modem that is installed is from the US version, would I not just be able to flash the full US firmware using ODIN and call it a day? If not, why?
Right now the Baseband (modem) and Bootloader are both from the US model. The CSC (which could easily be changed later if I wanted / needed to do that) & PDA (which is basically just the android OS stuff) are from the Chinese model. I am far from an expert in this area but it seems that the PDA is the only thing that I would need to change or am I missing something ?
Finally, I should have included that the reason I NEED to get the security patch updated on the phone is because the firmware (CSC & PDA) that is installed on the phone now does not have VOLTE enabled/working on it and in a later security patch it does have it enabled/working & since I would be using the phone on the Verizon network I kind of have to have VOLTE or the phone will not work once they turn off 2G/3G in the near future.
Click to expand...
Click to collapse
I think it would work with an AP partition(pda) flash. It only flashes system, recovery and boot partitions.
SnowFuhrer said:
I think it would work with an AP partition(pda) flash. It only flashes system, recovery and boot partitions.
Click to expand...
Click to collapse
Thanks for the reply & I think so as well because I am just updating the version that is already flashed on the phone and the PDA is what contains the Android security updates I need if I not mistaken.
This seems like it would be a fairly trivial process, but other users have stated it's more difficult than it seems so I'm curious why they have come to that conclusion.
I think I'll give it a few more days to see if anyone else responds before moving forward just to be on the safe side.
Today I got up real pissed with Samsung for being so restrictive around ROM flashing, rooting, flashing custom firmware or even stock firmware, so wanted to create this post to help anybody considering to get a Samsung phone to stay away from it.
This post is not intended to recommend any specific brand or model of android phone, but to recommend the exact opposite, which brand and model NOT TO EVEN THINK of purchasing.
This post relates to Samsung Galaxy S9 G9600 model which is Snapdragon architecture, but since Samsung is coming up with a bunch of "security features" I tend to think this may be the case for other models as well. I browsed all around XDA and other sources for guides on how to root and install custom roms, and it turns out Samsung manages to have limitations for EVERY step of the way.
Getting a few facts straight
Reference post: https://forum.xda-developers.com/ga.../rom-lineageos-17-1-s9-s9-snapdragon-t4093301
Ok, so there is a solid thread about a custom firmware and looks like several users got hands on it, but they might have been able to get passed though all Samsung security crap before it came out or before it got so tightened up. I'll list below every limitation I found:
OEM Unlock
There is a step where we need to tick OEM Unlock from the phone developer settings, it turns out Samsung has put a 7-day timer for this option to even appear listed to enable. If you do factory reset of the phone, the 7-day timer restarts. There are a few posts around on how to get passed this timer, but to me they were all crap, none of them worked. STRIKE ONE!
Bootloader unlock
After 7-days, we get the OEM Unlock option to appear, at this point you may think: Hurray!! .... WRONG! Now next step is to unlock the bootloader using an utility called CROM Services... And as you may have already guessed, did not work! I'm able to install the apk, but on launch it complains about wrong android version. (Tried with Android 8 and 10) STRIKE TWO!
There are some posts and guides claiming to be able to unlock bootloader by using fastboot utility, I can't reach to understand how, since fastboot commands rely on the bootloader to be previously unlocked (?). I least that is my understanding, correct me if wrong. Needless to say fastboot did not work for me. ADB lists my device but fastboot doesn't. There are a few troubleshoot guides around to try selecting proper USB driver from windows device manager, tried all that, tried a couple of ADB installations, fastboot didn't work.
Knox and RMM state
After some lookup in the web, Samsung incorporates some security features trying to prevent device theft and such things. For us power users this is in reality just a whole load of crap preventing us to get all the juice out of our phones.
Reference: https://www.goandroid.co.in/unlock-bootloader-of-galaxy-s9-plus-snapdragon/84688/
TWRP Recovery
Next step would be to flash a custom recovery such as TWRP with Odin or adb/fastboot, but since we are not able to unlock the bootloader in previous step, this is not doable at all. STRIKE THREE! OUT!
Fastboot utility doesn't recognize the device in download mode, so we can't send any commands to the phone.
Odin complains it is only able to flash signed stock roms, so since TWRP is not, we cannot flash it.
Rooting
Needless to say that if we don't have TWRP, we cannot flash the corresponding packages to root. Although this step may not be needed to install custom firmware, rooting has not been possible.
Stock ROM Flashing
Ok, so let's stay out of custom firmware - let's play around with stock firmwares. At this point, since flashing stock firmwares is kind of allowed by Samsung I was able to try out a couple from android 8 to 10 with Odin
Stock ROM Source: https://www.sammobile.com/samsung/galaxy-s9/firmware/#SM-G9600
But watch out! Once you get to install a specific build version, you cannot go back or downgrade to ROMS with previous Android build version. So now that I got Android 10 cannot go back to 8 or 9, this is probably because locked bootloader and unable to unlock. Here, Odin complains with FAIL! (AUTH) message.
STRIKE FOUR! EVEN OUTTER!
SIM Unlock
Ok, let's stay out of Samsung S9 G9600 model, let's crash it to the wall and throw it away to the garbage! Ok no, let's have it carrier unlocked and sell. Unlockbase is a well known and trusted sim unlock provider, I purchased a license to unlock by USB cable, but... GUESS WHAT! G9600 is not supported for unlocking operator network with this software... what a surprise!! I was able to apply for a refund and got my money back, so no worries here.
Note that flashing carrier free ROM does not unlock sim to use with any network operator.
I'll be trying to unlocking by code soon, as this is based on IMEI number, I may think this is independent to the phone model and edition, so I hope I have more luck with this option.
Conclusion
G9600 is a really crappy phone to mess around with. I may have ran low on luck with this specific Samsung Galaxy model since I got it as a gift, which is the latinamerican crappy edition. I wonder if other S9 editions and other Samsung models run with better luck than mine on this scenery... But as a lesson to myself, I will stay away of any Samsung smartphone in the foreseeable future.
OEM Unlock
The 7-day lock prevents stolen phones from being factory reset, leaving the thief with a phone permanently protected by your account. While a minor inconvenience, it's actually effective and not the worst compared to other manufacturers.
Bootloader Unlock
After OEM Unlocking, flashing TWRP through ODIN is effectively unlocking the bootloader. This is possible on both exynos and snap.
Knox and RMM
While this is an inconvenience, from Samsung's point of view, it's worth it. It makes the phone look more secure in the eyes of potential customers. If you really wish for NFC payments, I'm still able to use GPay with Magisk on a custom ROM.
TWRP Recovery
TWRP is flashed through ODIN, not fastboot. Look up an actual guide before complaining.
Root
Yes you can
Stock ROM Flashing
The one thing I could agree on with you is Samsung disabling OTA updates when OEM unlocking. I don't see the point really, but you're free to flash whatever you want through ODIN. Downgrading shouldn't be an issue. Not sure what's up with that.
Before buying a phone, how about you do some research before crying on forums. As a power user coming from the Oneplus One, I don't regret going for Samsung in the least.
Thanks for your reply, I had dropped all hope after several attempts over last few weeks. Found this option and I was able to get past my blocking issue with TWRP and moved on.
https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751
I have G960F and have to admit I totally disagree with your original post. I've been using custom ROMs on nearly every phone I ever had and don't think S9 (G960F) is bad in terms of unlocking. Just did an OEM unlock, waited a week, flashed TWRP through Odin, booted straight to TWRP and immediately flashed a custom ROM from it (because a boot to the stock ROM would replace TWRP back with the stock recovery IIRC). In the end I got sick of all the problems with Magisk and non-working google pay that I went back to the stock ROM - making S9 the first phone I use with a stock ROM even though it can be flashed. I think it's a great phone for power users.
And as far as SIM unlock goes - Samsung is not to blame, the carrier the phone was made for (and purchased from) is. Phones that Samsung itself sells are unlocked. I wonder why there's still some countries where SIM locking remains legal.
This thread is a prime example of how people end up with bricked devices. So much misinformation in one page LOL
I had the 9650 and most of what I'm doing here is user error. This was one of the best devices I've ever owned. I mention of fast boot and such you obviously just do not know samsung devices. You can't blame samsung on your own ignorance
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru LG developers site. Then I tried to get TWRP working and it might be the problem (more on that later). So, in order to get TWRP one of the steps was to fastboot boot TWRP-judypn-boot.img. I did that but didn't know that to do next (cause when I did it the phone booted normally and I didn't fully understood what now), so I abandoned the idea and just loaded the backup from LG Mobile Switch. But, then I realized that with having unlocked bootloader I won't be able to use google pay, so after some reading I found out that Magisk might be the answer (it wasn't) so I managed to get Magisk root on my device. When I found out that it didn't help with google pay i tried to do what others on forum warned me not to - RElock the bootloader using 'fastboot oem lock'. And now it has locked bootloader. But also now of course the phone is rather bricked in a way that: I can enter both fastboot mode and download mode but: trying fastboot something I get the info that it is not possible in Lock State, and when trying to just flash kdz of that stock android 10 that I started with, the LGUP says error 'error 0x6004 crossDL' and below that it mentions 'judypn_lao_eea>@judypn_lao_co' so probably that first fastbooted img now prevents it from beign flashed. So now I cannot fastboot or flash anything, and trying to boot the phone gives me error "Your device has failed a routine safety check and will not boot." and also sometimes, below 'All slots are unbootable'.
I know that I screw up multiple times, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
AnDevil said:
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru L<brevity>imes, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
Click to expand...
Click to collapse
Sounds kind of messy. Two things to know; 1) u most certainly can have google pay working on v40 w/10. I just added it on my (orig at&t) korean 10 30e / rooted / magisk / twrp. And 2) u should never ever try to relock the bootloader unless you just flashed a stock kdz to the device (completely unmodified, don't even choose language when it boots).
So the prob is what to do now. I'd first try to use fastboot to switch slots and see if the other side boots? And if that doesn't work / achieve what you want, then use lgup with dll version 1.14 to do the 'cross flash' (the 1.16 version doesn't work for that). Be sure to do a part DL (if u do the crossflash), then do a refurbish with the same kdz just after the part DL (of course you let the part DL complete, just shut it off after it boots all the way), then do refurb.
Ideally, what are u trying to accomplish?
cheers
Well, for now I would want to have bootloader locked, stock Android 10 on there. I'm probably going to leave the modding cause of the mess I've made - especially that I don't have much free time to tinker with phone when things go bad (and also as You can see I don't have enough experience to do so).
Right, so back to the point. How do you switch slots in fastboot? If by 'fastboot set_active a' (or b), then the result is 'not possible in lock state'. And for the other part (with LGUP and crossflashing), can You provide some kind of idiot-proof tutorial for that? Which files should I download and try to flash on the phone?
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
AnDevil said:
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
Click to expand...
Click to collapse
Okay, just so that it's clear, you do want to use 1.14 when going from 8 or 9 to 10. 1.16 won't recognize the older OS.
But, if you'd have done 1.16 Part DL from the beginning, it would have worked, as you've discovered. When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them).
Because you want to flash ebw 30b, there shouldn't be any reason to select all partitions. But I'd suggest (again), after doing the part DL, let the phone reboot of course, to complete. Then just shut it off and go back to LGUP and do a refurbish this time of the exact same kdz.
good luck
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
AnDevil said:
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
Click to expand...
Click to collapse
Sorry yes, that should have been 'there shouldn't be any reason NOT to select all partitions' (I think that's what the 'context' of the whole comment implied').
Yes, those steps are correct.
I think the confusion about lgup is around this; 1.14 is used if u need to 'cross flash' (going to diff OS). If you're not cross flashing then 1.16 will work. I think most people are cross flashing due to desire to get rid of bloatware and / or wanting to move to A10 when their OS doesn't have it or the kdz is unavailable.
you are in a somewhat unusual circumstance, having the only version of v40 that lg actually allows legit unlocking. So you never cross flashed (had to re read to realize that, it's that uncommon).
good luck
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
AnDevil said:
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
View attachment 5190441
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
Click to expand...
Click to collapse
So here's what I'd suggest, because you have an ebw version, which I believe has dual sim, and many many have had issues with those and losing the dual sim capability (very frustrating and difficult to get back).
Go to the v40 rom forum and Markus (los developer), put in the first post of his lineage rom an invite to the lgv40 tele gram group. Use that and join tele group and there are a lot of international users there, they can guide you with this problem (they have and use that specific device, among others).
If you want to do more reading on this, follow this link. It's the lg firmware dl page and do a search from the top for 'judy'. You'll see others have had the same error you're getting, and used lgup 1.15 command line to get around it.
I don't think it's because of what u flashed with fastboot (twrp), judypn is the name of the device, not specific to twrp.
So join the tele group and also (here on xda) look in the thread about 'unlocking all devices - except t-mo'. Not to unlock it, but to learn to use qfil. You will probably need that.
cheers
Ok, definitely will do that. Thank You very much for Your help
USE UPDATED POST, HERE!
THIS POST IS NOW ONLY REFERENCE ONLY - WILL BE DELETED SOON.
Well I figured I'd make a quick How-To on how I successfully Carrier/Sim unlocked my Samsung Galaxy S21 Ultra 5G running the NEWEST Android update on bootloader 5 (USQU5BULJ)released in January of 2022.
***This does NOT trip Know and does NOT require a root or a paid service. ***
****Also Note - This is the process I took, you may find some of these steps are not needed but for the purpose or recreating my results, I'll be posting my exact process.
****This has ONLY BEEN TESTED ON SNAPDRAGON BASED SAMSUNG GALAXY S21 ULTRA 5G SM-G998 U & U1, if you try it on a different model or phone you may (and likely will) receive different results!!!!
Here's what you'll need:
•ANY (activated or not) Sim from the carrier you wish to switch too.(or a way to replicate the carriers cert from one)
•A computer
•Patched Odin
•BOTH the NEWEST U & U1 ROMs/Firmware - theres a full post on these and how to flash them here on XDA (Reminder for myself or mod to link it) or visit SamFW.com, it has both Odin and the ROM/Firmware files you will need.
•Android ADB platform tools (You can find them on the official Android Developers page here or use any ADB software of your choice, fastboot is not required or used in this process.(Google "Android Developer Platform Tools" to get them from the official Android devs page. )
STEP 1:
So let's presume you have a Verizon or T-Mobile carrier locked phone, if you look at your baseband, which you can find in Settings > About > Software Info, you should see this "SM-G998Uxxxxxxx"
*****IF YOU SEE "SM-G998U1xxxxxxx" STOP - Skip to step 2******
Head over to your preferred site to get stock Samsung Roms (Refer to link above if you don't know where to find) and download the U1 XAA rom and the U rom of the CARRIER YOU WISH TO USE. IMPORTANT! MAKE SURE YOU DOWNLOAD THE "U" ROM FOR BOTH THE CARRIER YOU WISH TO SWITCH TO AND THE U1 UNLOCKED ROM.
Put you device in download mode (Hold Vol up and Vol down and plug in the USB, which should be connected to your PC and now your phone at this point.)
Flash the U1 XAA Rom, place appropriate files in appropriate places in Odin, when you get to CSC, DO NOT use the "HOME_CSC" use the other.
Leave the rest of Odin settings alone and hit Start, wait for it to finish and reboot.
Step 2:
Once the phone boots, return to Settings>About>Software and confirm you are using the XAA rom by looking at Service Provider Software Version and it should say something like "SM-G998U1_XAA blah blah blah" you just want to see the U1 and XAA.
Now put in the Sim from the carrier you desire. A pop-up should appear prompting you to restart your device. Follow the prompt.
!MOST IMPORTANT STEP!
BEFORE the device fully restarts, force it into RECOVERY MODE, I was able to achieve this by holding the power and Vol Down buttons at the same time, starting to hold the directly after the "Samsung" Logo fades away upon initial restart. If you have trouble getting into recovery please comment below.
Once in recovery, use the volume keys to navigate to "Clear Cache" select and execute. Now go to Factory Data Reset/Wipe, select and execute. It should be the option directly above "Clear cache".
Once done, go up to "Reboot to Bootloader", Select, Execute.
AGAIN, Very Important step,you MUST interrupt the boot process again and force the phone BACK into download mode this time, so once the phone attempts to reboot, you need to hold the Vol Down and Vol Up buttons at the same time and the USB MUST be already plugged in.
We should now be back in download mode and be on the U1 rom. We have verified all of this in the steps above.
STEP 3:
Now it's time to flash the ROM from the carrier you wish to use. Make SURE you have a Sim from that carrier inserted during this process. It doesn't need to be a working or activated Sim, just simply one from the carrier you wish to have your S21 work on.
Flash all items as you did earlier, but using the "U" ROM for your desired carrier as described above. Same deal with CSC, DO NOT use the "Home_CSC"
BE SURE that you use the USERDATA file if there is one for your carrier. Very important to have the phone working properly.
Start the Odin flashing process.
Phone will Auto-Reboot.
Done!
You should now be on the carrier you wish to use. This can be (in theory, test at own risk) replicated for ANY carrier supported by Samsung, and, I should soon find out if it will lead to what my original goal was, a bootloader unlock on the QualComm SnapDragon variant of the S21 and future Galaxy devices.
If you have any issues please comment below.
PoC, results after doing above process.
Good luck.
-k0mrade
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There are some parts of my tutorial that are not well expressed and may be misleading. Please don't hesitate to post in comments if you need clarity.
IMPORTANT!!! I LEFT OUT ONE MAJOR STEP! ************ ----- BETWEEN STEP ONE AND STEP 2 - After you do the factory data reset/Wipe cache -> reboot to Bootloader -> force into download, you need to flash the U1 rom BEFORE putting in your desirced carriers SIM, then reboot, let phone fully boot, THEN insert your desired carriers SIM -> restart phone-> interrupt boot by forcing into recovery and repeat factory data wipe and cache wipe and reboot bootloader -> interrupt Boot Process again, but into Download Mode -> Flash your desired "U" carrier Firmware (must be same carrier as the SIM you put in as described above). -> Done.
And when/where does one need to use the required ADB-Tools?
tested and work only on S21 ULTRA 5G SM-G998 U & U1
thank you
OnnoJ said:
And when/where does one need to use the required ADB-Tools?
Click to expand...
Click to collapse
Lol this is likely one of those steps thats unneeded. i cant remeber off the top of my head why exactly i added that in. But it wont hurt to have the drivers, thats for sure.
Ive made a (Slightly) more clear post, hopefully better detailing this, Here. Mods may close this thread as they feel free but i will leave it up as a resource for the time being.
How many different devices have you tested this on?
iBowToAndroid said:
How many different devices have you tested this on?
Click to expand...
Click to collapse
ive just finished doing it on my 6th one device, 4 were Verizon 1 was Tmobile and 1 was ATT. I seem to be able to replicate this process over and over again so far with no issues so far, but i am making sure to update each device manually via odin 1st to latest u1 Firmware first as described above.
K0mraid3 said:
ive just finished doing it on my 6th one device, 4 were Verizon 1 was Tmobile and 1 was ATT. I seem to be able to replicate this process over and over again so far with no issues so far, but i am making sure to update each device manually via odin 1st to latest u1 Firmware first as described above.
Click to expand...
Click to collapse
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
thats essentially the point of going from u to u1 then back to u after you booted atleast once into u1 with the desired carriers sim, somewhere along in the process of interrupting the bootloader and flashing the carriers U Firmware its overwriting the system policy. Theres a hole in here somewhere im positive. still trying to pin point exactly where this weakness lies.
iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
End Game is to find a BL exploit to force enable OEM Unlocking on these qcomm s21s.
K0mraid3 said:
End Game is to find a BL exploit to force enable OEM Unlocking on these qcomm s21s.
Click to expand...
Click to collapse
You're definitely not going to find that, as that's not related to SIM unlocking whatsoever
iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
And sorry to answer your initial question, yes, verfied carrier lock, getting errors like this, see attached.
iBowToAndroid said:
You're definitely not going to find that, as that's not related to SIM unlocking whatsoever
Click to expand...
Click to collapse
I like a challenge
This "temporary" thread is now closed. Main thread is here.