Database Develop

[GUIDE] Flash SBF to Motorola Atrix 4G

WARNING
DO NOT FLASH ON BELL ATRIX
​If you appreciate this guide, please visit my website (maybe check out my sponsors!), subscribe on Twitter, press the thanks button below, or donate to Fixter, DesignGears, Fenny and other great helpers/devs for the Atrix 4G.
Download
1.2.6
http://bandbinnovations.com/Atrix.7z
Password: atrixbl
1.5.2
HTTP (Rename from .rar to .gz)
HTTP (Rename from .rar to .gz)
MultiUpload
Hotfile.com
DepositFiles
UPDATE: Linux SBF guide here --> http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html --> Thank you "relaxed"
Flash Guide (Instructions)
Prerequisites
Download RSDLite 5.0 (MediaFire mirror)
Install the program
Download SBF file from above links
Bricked phone or test device
Fully charged device
Drivers installed (if you rooted your phone, your computer has the necessary drivers)
32-bit
64-bit
Problems
Some users experiencing WiFi connectivity weirdness
SIM-unlocked devices may still have WiFi problems
Market might not show all applications (easy fix on the way)
Do not flash this file unless absolutely necessary. It will help those who’ve bricked their device to recover, but this is not for flashing just for fun. BriefMobile cannot be held responsible for device damage due to this guide.
Make sure your phone is turned off
Take out your microSD card and SIM card for the flashing process
While turning the phone on, hold the Volume Up button until it acknowledges RSD
Your device will say “Starting RSD protocol support”
Run “RSD Lite” on your computer
Press the “. . .” button next to the box labeled “Filename”
Load up the SBF file
The SBF file is located inside of the .gz file, you must extract it out before loading it into RSD Lite
Use WinRAR or 7-Zip to extract the .gz file on your computer
Plug your device into your computer
Use the USB ports on the back side of your computer for safety
RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
Press the “Start” button
Be patient while the phone reboots. It will take a long time.
Congratulations!

Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.

designgears said:
Thanks, I was about to write one up myself because of the Adeo bricks
Alternatively you can just enable usb debugging. Clicking start will reboot into rsd mode.
Click to expand...
Click to collapse
Good tip! Didn't know that!

Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?

tianqi said:
Sorry but why shouldn't it be used with sim unlocked devices?
Is it cause it can cause wifi issue?
Click to expand...
Click to collapse
Yes. This isn't a confirmed issue, but others have experienced WiFi problems with this SBF flash over their SIM unlocked devices.

Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.

cellzealot said:
Are you sure it says "NS Flash Olympus" and not "S Flash Olympus"?
NS stands for Non Secured and is how a development phone with unlocked bootloader is designated.
A secured stock phone should be seen as S Flash in RSD Lite.
Click to expand...
Click to collapse
That's very odd. Mine most definitely shows as "NS Flash Olympus."

im a noob sorry, but what does this actually do?

fRenZy-_- said:
im a noob sorry, but what does this actually do?
Click to expand...
Click to collapse
If you mess around with your device and break it, this can save your life by unbreaking it!

I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.

kennethpenn said:
That's very odd. Mine most definitely shows as "NS Flash Olympus."
Click to expand...
Click to collapse
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.

cellzealot said:
I would suggest a large warning to always charge the battery completely before any flash attempt.
The phone cannot charge in bootloader and if you get stuck or need to reflash several times you can run the risk of a dead battery if the phone will not boot normally to recharge it.
Another important note is it is a very common misconception that flashing and SBF file completely restores the phone to a stock factory state. This is not true. Most SBF files and in particular official release builds do not write to cache or user data partitions by default and you must factory reset/wipe either in recovery or from the phone menu after flashing if you want a truly clean configuration.
Click to expand...
Click to collapse
Thanks for the info! Duly noted... editing the post.

jimmydafish said:
Are you sure you purchased your device retail? As cell stated if you do indeed have a NS device you have hit the jackpot.
Click to expand...
Click to collapse
100% positive I purchased my device retail. I'll screenshot the RSD Lite for you in a moment when I recover from my soft brick (screwed up framework-res).

RSD Lite reports "NS Flash" for me too
{
"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"
}
purchased through Amazon

kmiller8 said:
RSD Lite reports "NS Flash" for me too
purchased through Amazon
Click to expand...
Click to collapse
Perhaps "NS Flash" does not mean developer phone on the Atrix?

kennethpenn said:
Perhaps "NS Flash" does not mean developer phone on the Atrix?
Click to expand...
Click to collapse
Or maybe we both got incredibly lucky is there any way to further verify if RSD Lite is reporting incorrectly?
Also off topic, why is the "Start" grayed out for me?

mine also says NS, purchased directly from AT&T
start is greyed out if there is no file/an incorrect file to flash, notice that the file properties pane is blank, it has not actually loaded the file in the select box in that screenshot

Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device

tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
Mainly just recovers you from a soft-bricked or improperly hacked device. It flashes you back to stock (or as close to stock as we have right now.)
No new features. No bug fixes. Nothing different from stock except a few new possible issues.

tianqi said:
Does this leaked update (leaked sbf/ whatever you want to call it :] )
do anything useful?
E.g. make any important/useful updates? If it does I am willing to try despite having a sim unlocked device
Click to expand...
Click to collapse
It changes some stuff, but I can hardly see anything different at face value.

Help needed, 'Your device has failed a routine safety check and will not boot.' after relocking BL

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

General Journal: A brand new OPPO Find X3 Pro (UK/EE) - From new to clean de-bloated android (hopefully)

To start this journal I will begin by stating, I am not actually sure if it will be possible to finish this journal; from what I have read there can be quite a number of obstacles with international versions of the OPPO, some of which can be quite troublesome, but I thought it would be an interesting and hopefully helpful (for my self and anyone else wanting to do the same) way of going through the process with such a modern device.
The device arrives tomorrow, I wanted to get the initial post in without knowing precise details about the device.
I will update this primary post with the journal entries and post into the main thread when I update it going forwards
-- Entry 1 29/01/2022 00:21 (Dellivery today at some point!)
So far I have found out that cpw means car phone warehouse, which used(still is?) a store in the uk, 'EE' a network provider in the UK releases of the Oppo x3 find pro are apparently identical to releases from this store.
I have asked the user who informed me of this if they could possible put any information they are aware of within this thread.
Also, I will be doing the unboxing and initial looking at what it is via youtube I hope this is ok? I could not see a way to embed video onto this platform!
-- Entry 2 29/01/2022 10:53 (Delivery)
This is just a few images of the arrived device, simply unboxed and put on charge nothing has been set on the device what so ever.
{
"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"
}
Also note that this image showing the build number is by @alvydas it is not from my device yet! just some more information to add to the journal, this is believed to be the same as mine should show later on when I decide to video/start the phone up
Also for note the CPH (Possible related to CarPhoneWarehouse) prefix in the build number)
-- Entry 3 29/01/2022 13:11 (Turning on, Bootloader unlock, USB Debugging enabled)
Youtube video:
- May still be processing the HD version in google HQ!
-- Entry 4 30/01/2022 10:53 (Getting sorted)
Ok so we can't root it and we can't change the boot laoder .... however we can get novo launcher to start by default! The pro version at least!
Not exactly an amazing feat but hey its progress, I also removed the gmail mail application as I preffer outlook (mainly because I have 3 email accounts):
And boy .... you can really remove everything including:
130|OP4F57L1:/ $ pm uninstall --user 0 com.oppo.launcher
The coloros launcher its self X_X, so it seems you cannot get root, but there is no protected package, you can remove ANYTHING.
so this bodes the question .... other than wanting lineage OS of course, how thin can we get it ....
-- Entry 3 10/02/2022 10:53 (Hackery and cleaning)
.... So there is no fastboot on the international model, it is simply not there I even got EE them self to confirm this.
However, I have made some progress in discovering a way to get to the qualcomm flashable download mode, that is it will show up as a:
One of those (if you have the Qualcomm drivers installed), some information I put in the forum about this mode was this:
1) Turn the phone off (shutdown)
2) Hold the power button and the Vol up/down (I Forget which) down all the way through the phone starting, you will feel a little Bzzzzz
3) you will be presented with a menu probably in chinese, this is because you held down the power button and it auto selected the first language (its not a biggie), just press the back touch screen button in the top left <--
4) Select english (or chinese if you preffer!)
5) you will be presented with a menu that has 3 options, Format, Reboot, .... something else ...
6) Select none of the options! look to the bottom of the screen you will see a version mine was v12 o3 v1.2 - double tap this
7) you will get a warning you are entering 'customer service mode', and wallah .... you will get the device show up in device manager.
I was going to shoot a video of this, I still might! but its rather redundant at this point as I am now at a brick wall, I need to figure out how to deal with this mode, can I flash something to it .... how?
I am scrubbing the phone of all the bloatware I can and to be honest I have it pretty damn clean .... but still the fastmode is elusive and what else could be loaded onto this lovely phone.

Entry 1 added - nothing really important

Entry 2 added, initial unboxing simply for charging, video to come soon: looking for details!

The CPW in the build number is more of a guess than anything else we all could be wrong

alvydasd2 said:
The CPW in the build number is more of a guess than anything else we all could be wrong
Click to expand...
Click to collapse
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.

PaulGWebster said:
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
Click to expand...
Click to collapse
Yh that's fine

Entry 3 uploaded, many thanks @alvydasd2 We do have slightly different builds it seems!

So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this

Also have to figure out if all the fancy camera things will work with a custom rom, such as the microscope mode and all the advanced functionalities
Maybe the best initial tangent is to simply root the phone and remove any bloatware as well as installing novolauncher, followed by re-rooting it
That way I will not lose the ability to use the special camera functions and in turn still receive updates, I believe I can actually freeze certain packages too so they are effectively immutable, so they show up but can never run or be changed ... hmmm

PaulGWebster said:
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Click to expand...
Click to collapse
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle

alvydasd2 said:
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
Click to expand...
Click to collapse
Check the youtube video, I appear to have lol ... though I did notice that going into the recovery menu is all in chinese ... so I assume its the chinese version:

The only problem being ... I have no idea idea what this menu says -_-

I guess that is tomorrows episode though, connecting it via ADB+TWRP

Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that

alvydasd2 said:
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
Click to expand...
Click to collapse
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options

PaulGWebster said:
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
Click to expand...
Click to collapse
Oppo has a weird bootloader cuz it can only be unlocked with an app that only works on Chinese version and to access fastboot u need a unlocked bootloader

just read this .... so there is no way to even fastboot the device https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/

I wonder if you could flash on the chinese version of the firmware

it seems that the device is really a 'realme gt 5g' .... trying to verify this

PaulGWebster said:
it seems that the device is really a 'realme gt 5g' .... trying to verify this
Click to expand...
Click to collapse
It's not -_-

How To Guide Carrier/SIM Unlock - Galaxy S21 Ultra 5G SM-G998U & U1 (QualComm SnapDragon) USA/CANADA! - NO ROOT- FREE

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

Question Cannot register a new fingerprint in OnePlus 10 PRO

Hi
I bought a new OnePlus 10 PRO from Aliexpress. Its a CH version that the seller installed on it a global rom.
In the first setup of the phone, When I get to setting the fingerprint, I am unable to set it. I get the following:
{
"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 tried updating the phone, I tried factory reset... its always the same.
Any idea?
Thanks !

Are you sure that he installed the global rom? With model is yours NE2213 ? I bought from them also but I don't have this issue.
Anyway, you can try to use Oxygen Updater, to check if there is an update for your device or since your device is reseted, you can install ColorOS back

Hi,
I am on NE2215. Using Oxygen Updater I see that I have the most up to date version.
Not sure exactly how to install ColorOS.. I do want to have the regular OS that I would have as if I bought the global version (which i guess this is what the global rom mean..)

Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.

ok, and now for someone that have no idea how to do it?

If yours is NE2215 A13 you can download the ota file from this link: https://android.googleapis.com/packages/ota-api/package/7548d30abac02bde85a403bcc3a218df868e1910.zip
Then put it in your phone root and from your device Settings -> About the device -> Click on the option to check for the update -> 3 dots menu -> local installation and chose this package. It will start the installation.

Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
What am I missing?

I think it's obvious that something went wrong during the region change, this issue was prevalent on the 8 pro and was extremely difficult to fix.
Check out the 8 pro threads you'll be sure to see it. It's a partition iirc and if it's borked then it simply will not work..
I can't remember the name of it off hand but have a look and I'm sure you can get an idea of what may be wrong, specifically that partition.
Overall it's difficult to say as you've got a region changed phone, have you asked the seller what they did? If it is indeed as difficult as it was on the 8 pro to fix and seeing as you may be the only person experiencing this (far as I know) then I'd consider returning it.
You could re-flash the entire OS via fastboot enhance but that would also bring with it inherent problem's, if it's new then I guess the question you need to ask yourself is it worth it?
Did you save much money getting that converted variant?

dkaro said:
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
View attachment 5624305
What am I missing?
Click to expand...
Click to collapse
This page is from android play services. You need to click on the first banner

@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless

If that is the page showing I'm assuming you're on a gsi ROM and not oxygen os.
Now it's better to reinstall OxygenOS completely because it doesn't seem to be the ROM you're running.
Search here on xda to unlock your bootloader and then you need to find the zip with the full ROM for you device and install it from fastboot as mentioned.

OK, i'm trying to unlock my bootloader but as I mentioned:
dkaro said:
and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
Click to expand...
Click to collapse
Any idea what am I doing wrong?
I tried several tutorials online and so far I found no tutorial that will actually give me step by step that each step is actually working..

Maybe it's missing the drivers. Try this https://gsmusbdriver.com/oneplus-10-pro

dkaro said:
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
Click to expand...
Click to collapse
I feel you buddy.
You can use the app in my Magisk guide to do local installs.
Unlocking the bootloader you need to type fastboot flashing unlock
I haven't had to change region myself, but I did make a thread for someone else where the process was listed, think I called it changing Chinese firmware iirc.
If it's just a case of a re-flash of the firmware you're on, it's not that difficult.
Just use oxygen updater and grab the full firmware then do the local update using the app I mentioned above (listed in my Magisk/root guide)
I've never done this when not having the bootloader unlocked personally, but you can unlock and that'll wipe your phone with the recovery already on your device.
Only issue I have going down these routes is what else is missing? Do any of these processes stand up if we can't rely on the integrity of the OS that someone has put on and made a balls of it?
Sorry I know you may not agree but 30% is a small price to pay to avoid a brick and bring stability..
But that's me

zopostyle said:
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
Click to expand...
Click to collapse
That is a seriously good shout and would explain the fingerprint.

Hi guys, thank you again for helping me.
I tried installing again the uSB drivers, and ran again "fastboot flashing unlock" - it still telling me:
As far as I understand I have to unlock it for next step, right? (either for resetting back to colorOS or reinstalling oxygen)
I will try later tonight the other method (this magisk thing) - is this the link you're talking about?
Can you please also give me a link to download the full most up to date global Oxygen version and the CH Color one? i'll try both
Thanks !

For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585

zopostyle said:
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
Click to expand...
Click to collapse
Really is odd about them not being full... They're massive compared to conventional incremental updates. 4.05GB that's a hell of an incremental.
Haven't had to do it myself and it's sightly off topic but is the full version you'd use to recover a phone albeit without a functional MSM?
So fastboot flashing?
Cheers

Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?

dkaro said:
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
View attachment 5624521
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
Click to expand...
Click to collapse
As @zopostyle said earlier.. you'd need to use 12 mate. As that's the only full version available...13 won't cut it...you can extract the images using the button that says allow incremental, that's useful for extracting boot images for rooting.
But there's a reason why that's there, it's so you don't go ahead and flash it.... According to @zopostyle 12 is the only full version so that's what you would need.
Again I've not done this myself so perhaps wait for someone else to chime in what to do next.