Weird t-mobile OTA / factory reset issue - Samsung Galaxy Note 20 Ultra Questions & Answers

Hello just a few minutes ago I manually searched for updates from the system setting (have auto update off) and realized I had an update so I took it. I've taken updates OTA before with no issues however this time it basically completely factory data reset my phone and also what's more bizarre is it removed my bootloader unlock that I had gotten way back when the phone was first released. I have never installed custom firmware or even rooted the device but I did get my bootloader unlocked using a paid service that I found about here. I have a snapdragon model note 20 ultra 5g. I am so confused why this time around the OTA affected these things. I have included a screenshot of the OTA I took. Can anyone tell me what happened to my bootloader unlock I've had for like 6 months ?

Do you have a U or a UI device? If so I think Samsung changed the bootloader from version 1 to version 2 and that might be why you lost it. Checkout the last 2 pages of this thread here where you might be able to get more clarification.

Whenever you lock or unlock your bootloader, you device will factory reset.
When you took the update, it updated the bootloader to version 2.
Since your unlock was not an official one, it relocked your bootloader in the process.
This is what caused the wipe.

Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.

coilbio said:
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
Click to expand...
Click to collapse
Is there such a thing as an official bootloader unlock?

shpotik said:
Is there such a thing as an official bootloader unlock?
Click to expand...
Click to collapse
Nope. Not for US versions.

Why did you unlock the bootloader if you haven't ever rooted or flashed custom?

*Detection* said:
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
Click to expand...
Click to collapse
It sounded like a good idea at the time.

Related

Can I still do non-OTA updates after unlocking the bootloader?

Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
...can no longer receive ASUS software updates...
Click to expand...
Click to collapse
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Also, does unlocking the bootloader also run a factory reset and wipe the device?
nothsa said:
Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Also, does unlocking the bootloader also run a factory reset and wipe the device?
Click to expand...
Click to collapse
You'll be flashing ROMs, not getting ASUS's updates. A rom for the latest firmware usually takes less than a week to get on the dev section of the forum.
nothsa said:
Hi!
I'm wanting to unlock the bootloader on my new TF700, but I read this in the bootloader unlocker disclaimer:
Does this mean that I can't use ANY official ASUS updates, even if I want to run the update manually? Or does this just refer to OTA updates? I really want to put Jellybean on here when they release it, so I probably won't unlock the bootloader if I can't update to it manually.
Click to expand...
Click to collapse
Only refers to OTA, as far as we currently know -- the bootloader unlock hasn't been available long enough to prove otherwise.
Also, does unlocking the bootloader also run a factory reset and wipe the device?
Click to expand...
Click to collapse
Nope, it only reboots. It will leave your user data intact when performed correctly. Obviously, when the crap goes into the ventilator, global nuclear war might ensue or your cat may just die (if you don't have one, you will receive one from a local asylum a few days before, that's enough emotional attachment to make it hurt).
<Oh, sometimes I'm vile. Sorry! >

How to restore status code to 0 from status code 2

Plzzz help!!!!!!!!!!!!!!!!!!!!!!
you can't
K.V.K said:
Plzzz help!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
bromoxitos said:
well my friend sry but you can't restore this code
most of devices like samsung,motorola etc they have.... lets say a key for the bootloader(is the door) and this key if you root your device
breaks and the half key stays inside the door hole to reminds you that the key is broken(the devicesis root/unlockbootloader).
so if you root any motorola device the code state goes
automatically 2 and stays like this,you can flash again the stock rom and relock the bootloader sure
but the code stays 2 for ever.
i hope to help you
moto g XT1541 stock rom 6.0.1 lockbootloader
Click to expand...
Click to collapse
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
yeap
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
bromoxitos said:
YEAAA we say the same think,but i use an othey way to say it.
i say in the end you can relock the bootloader (more or less) when i say this i mean that you put some partitions back in boot loader
so when you flash the stock rom you can take any ota update,but the main bootloader is unlock always.
i know that form my old moto g2gen, moto x2013!!!
Click to expand...
Click to collapse
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
ohh!!
acejavelin said:
You could relock the bootloader on older Motos, but not anymore... Actually, it can be relocked but it will never report as locked or relocked, it will always be reported as unlocked. I don't how to be more plain in describing this.
And yes, you can take an OTA when unlocked, as long as you have a stock ROM and recovery and your bootloader is the correct version for your ROM. If your bootload and ROM are out of sync (ie. you have a Marshmallow bootloader and a Lollipop ROM), if your bootloader and ROM are out of sync, you could potentially get into a hard bricked situation.
Click to expand...
Click to collapse
not any more? damn....yea we say the same think,sry for my english,yea i khow what you talking about i brick my moto x like this!!! any way.
ty for the new info about bootloader.
you was 100%
were you a clear,thanks a lot,and i hope to help him
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
yagyaxt1068 said:
Once I sent my hard bricked phone to Motorola. I had unlocked the bootloader and done the stupid mistake of sideloading an older version and upgrading to a newer, but still older version. When it came back, it said it was Status Code 0.
Wonder how they did it.
Click to expand...
Click to collapse
They flash the eMMC chip (internal storage chip) directly... If you could get the right image you could possibly do it yourself with a few hundred to thousand dollar investment in a proper JTAG flashing unit.
Key would be getting the right Image, this would be far more than just a normal stock fastboot image, and is probably generated on the fly per device due to differences in serial number, IMEI, etc. These types of images don't get leaked out.
acejavelin said:
I'm not exactly sure what you are saying, but I think the jist of it is how do you relock the bootloader... the answer is you cannot, once it is unlocked it will always report as unlocked, even if you reflash stock and find a way to relock the device.
When you unlocked your device, it was plainly stated in the disclosure on the website that once the bootloader is unlocked, it is irreversible.
Click to expand...
Click to collapse
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
wiytboi said:
ok so what if you have never root unlocked, did nothing but use as intended to be.. never trying to do anything to it. wtf would i have a code 2 status then? care to sum that up for me.. cause 100% my situation.
Click to expand...
Click to collapse
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
acejavelin said:
You unlocked the bootloader... It doesn't matter if you actually changed anything else or not. Once it's been done, this status code can never go back to 0. If the status code is 2 and you didn't unlock the bootloader, then someone else did.
Click to expand...
Click to collapse
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
wiytboi said:
No I didn't.. I don't even know how to.. I just found out about recovery mode.. Wait wait before i say that.. How do you unlock boot loader? Turning developer mode on? Going to recovery menu? I've never hard reset it.. Just soft or doing new device. You said it could work fine for a while then shirt out? Like guy I bought from did and then I bought used for couple years and then went tits up?
Click to expand...
Click to collapse
You unlock the bootloader with a series of steps that includes submitting a code to Motorola and getting an unlock code back... Performing it forces a factory reset as well. It's not something you can do by accident.
The issue with Status Code 2 was that an official update could have detected that and refused to update properly or done something worse... That never happened.
If everything is working fine, the status being 2 isn't important, it just means the previous owners had unlocked the bootloader and likely rooted or otherwise modified the phone.

Verizon Pixel OTA 7.1.1 - BL relock?

So I picked up my Pixel from big red today and successfully used depixel8 to unlock the bootloader. I know depixel8 does not work on 7.1.1, but am I able to safely accept the update or will it relock my bootloader and leave me with no options for unlocking it again for the time being? TIA for your help guys.
You can take the update, it will not re lock the bootloader.
AndroiderM said:
You can take the update, it will not re lock the bootloader.
Click to expand...
Click to collapse
Beautiful, thanks.
You *should* be fine taking the OTA (and keep your bootloader unlocked) if you unlocked it before taking the OTA.
Edit: I'm too slow.

Buying Verizon Pixel, have some questions

Hello guys.
I'm going to buy used and bootloader unlocked Verizon Pixel tomorrow and I'm interested in couple of things:
1. Can I flash all the ROMs that are available for Pixel on Verizon version too?
2. Can I properly install TWRP, root using Magisk, etc?
3. Can I properly flash (and downgrade if needed) official system images (and are they ever available for Verizon models?)
4. Can I take part in Android Beta program?
5. Is there anything I should be afraid of?
Thanks in advance.
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that are bootloader unlocked. You need that to do the items on you list.
TonikJDK said:
Make sure it is bootloader unlocked, and not just SIM unlocked. There are not many VZ ones around that area bootloader unlocked. You need that to do the items on you list.
Click to expand...
Click to collapse
As I already stated, bootloader is already unlocked.
No one has an answer?
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
I got a replacement about a month ago on my small Pixel and that one was unlocked. However, the one I got from Verizon in store did not have an unlocked bootloader. I'm not sure what the deal is, but maybe getting a replacement from an "accidental" break might do the trick. just to clarify, my first Pixels' usb port got completely fried and started to smell bad whenever it charged, and the phone would get really hot. I am now on 8.1 with an unlocked bootloader but have yet to actually root the phone
KittyRgnarok said:
If it's bootloader u locked then yeah u can do all those things. Just do not ever for any reason ever relock the bootloader. Also I believe there have been a few cases where ppl have had semibricks or other issues which required locked stock to fix or somehow resulted in locked stock
Click to expand...
Click to collapse
Thank you!
gb_14 said:
Thank you!
Click to expand...
Click to collapse
Np

How to restore bootloader?

As my device was rooted a month ago but couple of days ago I lost the L1 cirtification, today I updated to latest firmware by downloading full size by oxygen updater and updated it with in-device local update method. But even after the update my device's L1 cirtification is still not back and it's showing L3.
I rooted my device by flashing patched image with adb. Now I'm afraid locking bootloader might cause issues... Any suggestions how should I lock my bootloader. Somewhere I saw that lock option for bootloader in developer option cause bootloop/brick.
Btw my own lock is greyed.
Relocking the bootloader will definitely cause issues, maybe this thread can help?
XDHx86 said:
Relocking the bootloader will definitely cause issues, maybe this thread can help?
Click to expand...
Click to collapse
Yes I tried that already.

Categories

Resources