The may firmware update is now available for the S8+ (assuming it's also out for the S8 and S8U) on samfw, and I downloaded it, but I noticed the security bit level is now 2 instead of 1. I remember this when rooting and updating my Tab S7+ and was wondering if I should update to security bit 2 (having a U2 bootloader) at the cost of not being able to downgrade to a security bit 1 firmware (a U1 bootloader). I'm not sure if there will eventually be an incentive of having a lower security bit level or not, but I just wanted to ask before I make a decision I can't undo (unless it's different for the tab s8 series, which I doubt).
Pardon my ignorance, but is this "Security Bit Level" represented in the "U2" portion of X900XXU2AVD6, for example? I don't have any knowledge to help answer your question - I was just wondering if that is where you get that information, or if it's somewhere else, where is it?
Thanks!
OLD - disregard:
Where can I find this "Security Bit Level" displayed? I checked in all the Android Settings / About menu and didn't find anything listed similar to that. When I Googled for samsung security bit level, everything I see has to do with Knox. This makes sense since this is the security chip, but the Knox bit is permanently flipped when we unlock our Samsung bootloaders. Is this Security Bit Level you're referencing something different?
roirraW edor ehT said:
Pardon my ignorance, but is this "Security Bit Level" represented in the "U2" portion of X900XXU2AVD6, for example? I don't have any knowledge to help answer your question - I was just wondering if that is where you get that information, or if it's somewhere else, where is it?
Thanks!
OLD - disregard:
Where can I find this "Security Bit Level" displayed? I checked in all the Android Settings / About menu and didn't find anything listed similar to that. When I Googled for samsung security bit level, everything I see has to do with Knox. This makes sense since this is the security chip, but the Knox bit is permanently flipped when we unlock our Samsung bootloaders. Is this Security Bit Level you're referencing something different?
Click to expand...
Click to collapse
That's exactly right. The U2 in the firmware info signifies U2 bootloader and a security bit level of 2. I was a little confused with the terminology at first, but I got my info from here.
SavXL said:
That's exactly right. The U2 in the firmware info signifies U2 bootloader and a security bit level of 2. I was a little confused with the terminology at first, but I got my info from here.
Click to expand...
Click to collapse
Thanks! Argh. I now see that the three previous months' XAR firmware for my Tab S8 Ultra were U1 but the one I flashed for May is U2. I wonder why they would do that.
roirraW edor ehT said:
Thanks! Argh. I now see that the three previous months' XAR firmware for my Tab S8 Ultra were U1 but the one I flashed for May is U2. I wonder why they would do that.
Click to expand...
Click to collapse
I guess it may be to patch out some sort of vulnerability with the previous bootloader type. Perhaps making flashing unauthorized code harder for the hard-working software developers? I'm not sure. All I know is that once I flash the latest firmware, I can't go back. So, I'm not quite sure if it's the best decision at the moment. I mean, TWRP was made for the Tab S7+, and that works for both U1 and U2 bootloaders. I don't fully know why Samsung does firmware updates like this sometimes.
roirraW edor ehT said:
Thanks! Argh. I now see that the three previous months' XAR firmware for my Tab S8 Ultra were U1 but the one I flashed for May is U2. I wonder why they would do that.
Click to expand...
Click to collapse
How do you check what bootloader it is? Since I want to check it myself if mine also has changed from U1 to U2.
Jake.S said:
How do you check what bootloader it is? Since I want to check it myself if mine also has changed from U1 to U2.
Click to expand...
Click to collapse
If your firmware version has U1 in the name, it's a U1 bootloader. If it has U2, it's a U2 bootloader. I'm not quite sure what the difference between the two is apart from one being more secure than the other. Having a higher security bit level will do that for ya.
SavXL said:
If your firmware version has U1 in the name, it's a U1 bootloader. If it has U2, it's a U2 bootloader. I'm not quite sure what the difference between the two is apart from one being more secure than the other. Having a higher security bit level will do that for ya.
Click to expand...
Click to collapse
Okay I checked and saw that in April update it shows U1 and May update it shows U2. So yeah my s8 ultra has changed from U1 to U2
Related
Now running on Android 6, but i want downgrade to Andoid 5. Through One does not turn out, error during setting of recovery.
https://justforprogrammers.blogspot.be/2015/12/downgrade-from-marshmallow-to-lollipop.html
You need to wipe your data partition and flash the stock firmware
As I know, you can't downgrade your Tab S2...If this isn't right, please correct me.
PS: Hope my english is not to bad...
LordHelmchen89 said:
As I know, you can't downgrade your Tab S2...If this isn't right, please correct me.
PS: Hope my english is not to bad...
Click to expand...
Click to collapse
Who says?
ashyx said:
Who says?
Click to expand...
Click to collapse
I don't know who exactly said this, but I remember that it was impossible for me and many others to downgrade from 5.1.1 to 5.0. Why should it be different this time?
LordHelmchen89 said:
I don't know who exactly said this, but I remember that it was impossible for me and many others to downgrade from 5.1.1 to 5.0. Why should it be different this time?
Click to expand...
Click to collapse
It's not impossible. It depends on the firmware. If the firmware has had a revision update then there are occasions where the bootloader will not allow the downgrade.
However usually Samsung will inform the user of this before the OTA is applied.
A firmware revision will usually have U2 in the build number.
ashyx said:
It's not impossible. It depends on the firmware. If the firmware has had a revision update then there are occasions where the bootloader will not allow the downgrade.
However usually Samsung will inform the user of this before the OTA is applied.
A firmware revision will usually have U2 in the build number.
Click to expand...
Click to collapse
Did you mean, a firmware with an U2 in the build number can't be downgraded? All the firmwares I used in the past and for now have U2 in the build number...
My English is really not as good, so I didn't understand everything you wrote.
I'm sorry if I told something wrong.
Indeed, when it contains U1 in its firmware-name, you better not flash those if you're already on U2.
In the list that you can find here:
http://www.sammobile.com/firmwares/database/SM-T810/
the oldest 9 firmwares (bottom of the list) are all U1 firmwares, you better not use those.
All the other (more recent) firmwares are U2 versions, so you can flash all those if you want (doesn't matter if it's 5.0.2, 5.1.1 or 6.0.1.) if you have the SM-T810 model of the tab S2 of course.
As per the title, bought an unlocked G970U instead of U1 by mistake. Should I expect a Verizon splash screen greeting me in the bootloader? I don't wanna see any branding anywhere in my phone. Can I get rid of any of that flashing U1 firmware?
redsmith said:
As per the title, bought an unlocked G970U instead of U1 by mistake. Should I expect a Verizon splash screen greeting me in the bootloader? I don't wanna see any branding anywhere in my phone. Can I get rid of any of that flashing U1 firmware?
Click to expand...
Click to collapse
Which G970U phone you have bought. If it was a Verizon branded, then their logo should greet you If you bought T-Mobile variant, then its logo will be present while booting the phone. Flashing is possible and it depends which carrier you have. Also don't you have the phone in hand yet?
Charkatak said:
Which G970U phone you have bought. If it was a Verizon branded, then their logo should greet you If you bought T-Mobile variant, then its logo will be present while booting the phone. Flashing is possible and it depends which carrier you have. Also don't you have the phone in hand yet?
Click to expand...
Click to collapse
Yeah, the phone hasn't arrived yet. In the pictures I can see the box has no carrier logo, but I'm guessing it's Verizon because I haven't seen a Verizon branded box yet. Also, the box definitely says G970U.
I've been a Nexus/Pixel user all my flashing life, so I'm well versed in the fastboot/adb dark arts. How does this compare to Odin? There are so many new terms that I'm still trying to understand: CSC, HOME CSC, USERDATA, etc. Is there any guide I can follow to flash my incoming phone to U1 firmware?
redsmith said:
Yeah, the phone hasn't arrived yet. In the pictures I can see the box has no carrier logo, but I'm guessing it's Verizon because I haven't seen a Verizon branded box yet. Also, the box definitely says G970U.
I've been a Nexus/Pixel user all my flashing life, so I'm well versed in the fastboot/adb dark arts. How does this compare to Odin? There are so many new terms that I'm still trying to understand: CSC, HOME CSC, USERDATA, etc. Is there any guide I can follow to flash my incoming phone to U1 firmware?
Click to expand...
Click to collapse
The T-Mobile version is also G970U, so it can be pretty much any carrier. USERDATA file is present in carrier firmware, if you flash unlocked firmware you won't need/have this file.
Link below is for S8, but works for S10 as well. Of course you would need to use firmware files for your phone. I would also use instructions under "Flashing standard firmware" first using Standard Odin. If you get an error when staring to flash, then use (Patched) Prince Comsy's Odin.
https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Charkatak said:
The T-Mobile version is also G970U, so it can be pretty much any carrier. USERDATA file is present in carrier firmware, if you flash unlocked firmware you won't need/have this file.
Link below is for S8, but works for S10 as well. Of course you would need to use firmware files for your phone. I would also use instructions under "Flashing standard firmware" first using Standard Odin. If you get an error when staring to flash, then use (Patched) Prince Comsy's Odin.
https://forum.xda-developers.com/gal...rrier-t3625817
Click to expand...
Click to collapse
Thanks a lot. One last question. I'm based in Mexico (we only get Exynos here), so I got a U version to get the Snapdragon CPU. Obviously I don't want any US carrier branding/blotware in the phone since I couldn't benefit whatsoever from it. What about OTA's, though? Will I get them whenever Samsung releases an update for U1? Or will that depend on my carrier? Should I update monthly using Odin? Do I have to factory reset? So many questions :silly:
The link you provided doesn't work, btw. But I've since found some other Odin guides. Thanks!
redsmith said:
Thanks a lot. One last question. I'm based in Mexico (we only get Exynos here), so I got a U version to get the Snapdragon CPU. Obviously I don't want any US carrier branding/blotware in the phone since I couldn't benefit whatsoever from it. What about OTA's, though? Will I get them whenever Samsung releases an update for U1? Or will that depend on my carrier? Should I update monthly using Odin? Do I have to factory reset? So many questions :silly:
The link you provided doesn't work, btw. But I've since found some other Odin guides. Thanks!
Click to expand...
Click to collapse
I corrected the link in case you need it.
To answer OTA question: I had unlocked U1 model of S8 and when I flashed it with T-Mobile firmware then my phone got OTA from T-Mobile when they release it. I assume if you have carrier branded phone and flash it with U1(XAA) firmware then most likely your phone will get updates when Samsung releases them. You won't have to use Odin every time there is an update if you flash properly. Also, it would be advisable to flash using CSC file instead of HOME CSC, so your phone would be wiped. It is because you change firmware and want your software to be fully compatible. After flashing and you check your phone's software update and see that is shows "not compatible or something similar", then I would just suggest you to do "reset"(factory reset) from setting and after you setup your phone, that message will disappear. Also don't do any software update before flashing as you phone may get a fresher firmware than the one you might be trying to flash.
1) Check your current phone firmware
2) Download firmware you want, but if you can, get the firmware that is a previous one than the current one, so you will check to see how your phone gets OTAs
3) Flash using Odin
4) After that disconnect and let the phone do its thing
5) Set it up and check to see if software update section in settings don't give you any messages such as the one I outlined above, if it does, just factory reset the phone
Hi all, I'm new to modding in general so there's many things I don't quite understand, hoping somebody can help.
I bought an S10 from a site which was supposed to just send me a refurbed (italian) S10, instead they sent me the US version, (G973U) and I believe it is carrier locked since it's stuck with Android 9 and doesn't find any update.
I have tried searching to no avail what I should flash to simply unbrand it, and allow it to receive OTA updates without tripping Knox.
The build version is the following: PPR1.180610.011.G973USQU2ASGC and the CRC is XAA/XAA/ATT
Thanks in advance.
You shall call them.
Who and what for? I'm past the point of dealing with those sellers, I just want to flash the phone.
CSC (not CRC).
XAA is a multi-region USA ROM, so I don't think it will change over properly for you in Italy. There are threads here for how you reflash a different ROM. The one I used for my S10+ was this one: https://forum.xda-developers.com/t/...e-links-and-flashing-discussion-here.3905897/ but I am sure there is one like that for your S10 non-plus... find it, follow the instructions, and you should be all set.
Thanks! I'm a newbie, what does it mean it wouldn't change properly? No OTAs? Tripping KNOX?
I have found this which seems to be the equivalent of the link you posted.
So, I should flash the U1 version right? However I see only a file "SAU - 1 - ....", and my build number doesn't end in that, furthermore I don't know which bootloader version I'm at.
lrzfc said:
Who and what for? I'm past the point of dealing with those sellers, I just want to flash the phone.
Click to expand...
Click to collapse
Oh ok. I couldn't understand first.
For that, You'll flash in EDL mode. But the problem is if your device is powered by a snapdragon chip, it'll not working seamlessly.
FardinIslam said:
Oh ok. I couldn't understand first.
For that, You'll flash in EDL mode. But the problem is if your device is powered by a snapdragon chip, it'll not working seamlessly.
Click to expand...
Click to collapse
No problem. I'm aware of the mode I have to enter to flash, as above I'm trying to figure out which stock rom I should flash to avoid tripping knox, and to receive OTAs. What won't work seamlessly?
Well, mods can close the thread, found the way to do it. Leaving it in case somebody ever needs it.
First, found & checked the bootloader version (5th number from the right in the build version) since you can only flash older bootloader versions apparently.
Then downloaded through Frija the rom for the unlocked phone variant (SM-G973U1) and the unbranded CSC (XAA)
Then using odin 3.13.3b flashed the rom
Watch this video
lrzfc said:
Well, mods can close the thread, found the way to do it. Leaving it in case somebody ever needs it.
First, found & checked the bootloader version (5th number from the right in the build version) since you can only flash older bootloader versions apparently.
Then downloaded through Frija the rom for the unlocked phone variant (SM-G973U1) and the unbranded CSC (XAA)
Then using odin 3.13.3b flashed the rom
Click to expand...
Click to collapse
Hello, I'm in more or less same situation. When you flashed, which files did you use? All of them or just the AP_*** file?
Never mind. Flashed it anyway, now I don't see the AT&T startup screen anymore which is promising. Firmware version is now Android 11 (SM-G973U1 and not SM-G973U) on XAA CSC. Will see if I get any firmware updates later.
Hello guys, I've decided to downgrade my s10 from Android 11 to Android 10, I've tried downloading a version of one UI 2.5 from Sam mobile but gave an error saying the binary code wasn't the same. So I wanted to ask if someone can link the correct version to downgrade to. I'll attach a screenshot of my software info.
Binary code difference means that your BL (bootloader) is newer than the one in your flash file. Samsung doesn't allow you to downgrade the BL version, hence the error.
In most cases, OneUI updates come with new BLs, so you may be stuck at your OneUI version. Generally, the BL version is the 5th character from the right... "C" in your case. At least that's how it works for Snapdragon devices... yours seems to be Exynos so it may be different... but I'm guessing it's not.
What are you trying to flash? Check the 5th character from the right, it's probably "B" or older, I'm guessing?
T
schwinn8 said:
Binary code difference means that your BL (bootloader) is newer than the one in your flash file. Samsung doesn't allow you to downgrade the BL version, hence the error.
In most cases, OneUI updates come with new BLs, so you may be stuck at your OneUI version. Generally, the BL version is the 5th character from the right... "C" in your case. At least that's how it works for Snapdragon devices... yours seems to be Exynos so it may be different... but I'm guessing it's not.
What are you trying to flash? Check the 5th character from the right, it's probably "B" or older, I'm guessing?
Click to expand...
Click to collapse
Thanks for the reply, yeah now that you mention it the one that I'm trying to flash has 9 as the 5th character, so i assume i'm stuck with c(12 in hexadecimal i assume). And yes it's an exynos.
So there's no way to downgrade? That would very sad, since now i have a phone that fully charged lasts only 8 hours(with power saving mode).
I don't know Exynos well enough, but this is my understanding. However, being Exynos, you may have the ability that Snapdragon doesn't - Exynos can be rooted, and if you can do that, you may be able to go back. On Snapdragon, this is not possible (for the most part). So, check out the Exynos threads and see what they mention for flashing other ROMs, and if the BL issue applies there, too... again, it may not.
So root my phone and install TWRP and flash the rom from there? My only issue is that some banking apps will stop working with a rooted device, it's happened in the past, but I'll do some research and see if I find anything
Same, I want to downdrade from android 11 to android 10 but no success, if found any solution please post here.
Anyone seen or have the new U1 Firmware G998U1UEU5BULH?
None of the baseband 5 firmware's have been posted yet. I'm still waiting for something to come up cause mine is stuck in a boot loop from when I tried to downgrade to 4AUIP cause I didn't know my phone updated in the background to the new baseband.
I now have a brick until a 5xxxx firmware is posted. However, 5CVAx is rumored for February 9th, but I've still been checking Frija every morning haha
The OTA's have been around for about a week now, my AT&T S21 Ultra have received it from BULE -> BULH. However, I haven't seen a standalone anywhere.
I was thinking it was probably only available via OTA right now. I am wanting to flash my VZW to U1 firmware, but I have already been bumped to the #5 BL. I will wait patiently until it appears.
I have BULH on my u1 s21 ultra with a t-mobile sim card in it. I got it about a week ago, I really haven't noticed much of a difference.
I'm with VZW and on BULJ
I'm on BULJ as well, but I like the U1 Firmware better to be honest. Just waiting on it to be posted somewhere so I can flash the U1 on my Ultra.
FYI...it's out today!