I purchased a pre-owned Galaxy S10+ from Best Buy. It has One UI 3.1 with the September 1st, 2021 security patch on it. I can't get it to update to One UI 4. Every time I check for updates on the phone it says the software is up to date when it isn't. Is this normal? Will I get the One UI 4.0 update eventually? I am on Google Fi if it matters. The phone appears to have previously been on Sprint.
Is it rooted or modified Ina my other way? Is the phoen supposed to get oneui 4?
Arealhooman said:
Is it rooted or modified Ina my other way? Is the phoen supposed to get oneui 4?
Click to expand...
Click to collapse
Not that I know of. It does not appear to be rooted. I have not modified it in any way myself. Since it is a pre-owned device I don't know the history of it. I have read in numerous places that the S10 series is supposed to get One UI 4 and it started rolling out around the end of 2021.
Do you get a unlocked bootloader warning when unlocking device?
Arealhooman said:
Do you get a unlocked bootloader warning when unlocking device?
Click to expand...
Click to collapse
No, I don't.
sega dude said:
No, I don't.
Click to expand...
Click to collapse
reboot into the download mode by turning off the phone, waiting 5 secs, then pressing bixby + volume down button for 6 secs and then connecting the usb cable phone x pc.
after that, check for Know warranty or Warranty Bit or Knox Bit or Knox Trip or anything related. If it says 0, your device has never been rooted and knox isn't tripped. but if it says 1 or 0x003 it is tripped
I es gonna say that, but it’s to complicated for most people, and if BL locked that means they are stock, so ota shoudl work. @sega dude if ur tech savvy, unlock BL, flash latest firmware thru Odin then relock BL (or keep unlocked).
Related
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
I'm no expert at all but I ran motoapocolyps and if didn't do anything. It will either fail and your phone will be fine or, depending on what update you last took, unlock it. My phone is past due for unlocking the bootloader unless there is a way to downgrade it.
Hi
aviwdoowks said:
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
Click to expand...
Click to collapse
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
aviwdoowks said:
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
Click to expand...
Click to collapse
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
RikRong said:
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
Click to expand...
Click to collapse
"You can't cover up a BL unlock." <- THANK YOU! That is what I was trying to confirm....
I was thinking that since you can do this to cover up the unlocked bl warning: http://forum.xda-developers.com/showthread.php?t=1901444
that you can also do something to cover up the AP screen as well.
Since I'm rooted, and this phone is supposed to get 4.4, I'm not too upset that I can't unlock (Though with 4.4 I'll probably lose root ).. The stock rom is pretty nice on these, and root gives me pretty much anything I want for customization.
Thanks!
dreamersipaq said:
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
Click to expand...
Click to collapse
I am the one confused! I need to learn my codes.
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
McXred said:
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
Click to expand...
Click to collapse
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Lawlrus said:
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Click to expand...
Click to collapse
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
McXred said:
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
Click to expand...
Click to collapse
Right, it shows that message when the BL is unlocked, once you relock your BL that *should* go away, never tried it because I don't plan on even being back on stock with no root.
If you do any modifications to the device even root, or using a stock custom ROM like we have, it is suggested to NOT relock your BL, while on it. Keep that in mind.
You want to go back to full stock to lock it, then reflash the factory image
Pretty much what the title says. I've been trying to unlock the bootloader on my sprint v20 to install lineage 16, but I can't seem to get it to fastboot. I tried both using adb commands as well as holding volume down + plugging the cable in, but both ways simply boot the phone without doing anything. Can someone help?
i95swervin said:
Power off the phone, press & hold volume up
( if I'm not mistaken )
and plug in the power cord connected to a PC.
Good luck
Click to expand...
Click to collapse
Hey. Doing this sent my phone to a "download" screen with two icons for a few seconds, and then a firmware update screen. Is this what fastboot looks like? Because I hear people describing it as a menu with options.
Thanks.
Anwiday said:
Hey. Doing this sent my phone to a "download" screen with two icons for a few seconds, and then a firmware update screen. Is this what fastboot looks like? Because I hear people describing it as a menu with options.
Thanks.
Click to expand...
Click to collapse
Wrong volume key.
But you've got an ls997 mate. If you've taken an ota in about the last 18 months Sprint helpfully eliminated any chance of you unlocking the bootloader and rooting.
The last software version it was possible to revert futher back to an actually rootable version was ZV7, way back in the early-mid nougat versions.
Once updated past ZV7 Sprint helpfully physically burned fuses embedded in the CPU to keep you from going back and rooting. Hail overlord Sprint.
Phoenix591 said:
Wrong volume key.
But you've got an ls997 mate. If you've taken an ota in about the last 18 months Sprint helpfully eliminated any chance of you unlocking the bootloader and rooting.
The last software version it was possible to revert futher back to an actually rootable version was ZV7, way back in the early-mid nougat versions.
Once updated past ZV7 Sprint helpfully physically burned fuses embedded in the CPU to keep you from going back and rooting. Hail overlord Sprint.
Click to expand...
Click to collapse
Damn. So there's no way to install a custom ROM then?
Anwiday said:
Damn. So there's no way to install a custom ROM then?
Click to expand...
Click to collapse
Nope. Once it's past ZV7 it's never going back and you need to go back to root and install custom roms.
Please dd and pm me your frp, ftm, and if you are willing to, factory reset and then enable oem unlock, and send your userdata partition, all with the oem unlock allowed.
Thanks!
bump?
What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.
wgrant said:
What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.
Click to expand...
Click to collapse
The request is probably for this thread. People are trying to use the recently rediscovered exploit to finally be able to bootloader unlock Verizon Pixel 2 XL phones.
wgrant said:
What is this needed for? I've upgraded to the 4XL but still have my 2XL for right now.
Click to expand...
Click to collapse
On the LG V40 if the frp partition from a phone with the OEM lock flag triggered is dd'd to another device, the bootloader will allow unlocking, additionally, the ftm partition on the v40 seems to carry the imei so I assume the same is true for the Pixel, I'd understand if you didnt want to share that partition but I think if the phones imei registers as a Google store one, that could help trick it into working.
Is there any way an exchange can be done here for the Verizon software that enables WiFi calling, volte, voicemail, and video calling? Is that Verizon software out there somewhere? If you guys are trying to root and unlock vzw phones you'll be wiping and starting with a fresh phone anyway. Is that a good time to extract these files and provide them?
I have a Verizon Pixel 2 XL on Android 9 [last security patch]. Bootloader unlocked :good:
IcyAgitator said:
I have a Verizon Pixel 2 XL on Android 9 [last security patch]. Bootloader unlocked :good:
Click to expand...
Click to collapse
Could you follow this guide: https://forum.xda-developers.com/showthread.php?t=2450045 to get frp and ftm partitions? Then PM them to @Whoareyou
Thanks again!
Unfortunately I already was able to get these from someone with a Google Store unlocked one, the dd'd partitions didnt stick through a reboot, and it wasnt able to oem unlock, ive been messing with the oemlock-bridge-client, so far chaning the device_lock status from 1 to 0 does nothing :/
shwise said:
Could you follow this guide: https://forum.xda-developers.com/showthread.php?t=2450045 to get frp and ftm partitions? Then PM them to @Whoareyou
Thanks again!
Click to expand...
Click to collapse
I updated to Android 10 Security Patch October 6 2019. But I will do what I can.
Whoareyou said:
Unfortunately I already was able to get these from someone with a Google Store unlocked one, the dd'd partitions didnt stick through a reboot, and it wasnt able to oem unlock, ive been messing with the oemlock-bridge-client, so far chaning the device_lock status from 1 to 0 does nothing :/
Click to expand...
Click to collapse
Could you try flashing those from temp root, hard powering off (holding button) and then booting to BL?
shwise said:
Could you try flashing those from temp root, hard powering off (holding button) and then booting to BL?
Click to expand...
Click to collapse
I'll try when I get home, but I don't know if it'll be any different than using the "reboot bootloader" command.
No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.
krolla03 said:
No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.
Click to expand...
Click to collapse
I expect to get two more years out of this phone.... It'd be nice to have root options.
krolla03 said:
No offence but,why are people still trying to unlock/root the "unlockable/unrootable" variants of this phone? Its like what 3-4 years old? Like i get trying to root/unlock them when they 1st come out even though like come on you should've known by now. But now there are way better phones. Everyone is offering good deals for trade in's. I think its time to give up.
I would not have even rooted android 10 if Google music had a dark mode. (literally the only thing i use root for now) Oh and to fix the things google ****ed up like the lock and unlock sound and battery sound.
Click to expand...
Click to collapse
It's 2 years old
Hi all,
I tried searching for it here and in other sources but couldn't find anything that would help since this is an unlocked version.
I am not getting any updates or the Android 10 update and its already end of February, is this normal?
FYI the phone was purchased unlocked in the US but I'm living in Jordan.
Give it a check whether your device does actually get any updates using Frija here:
https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594/
Just need to find the correct CSC.
If there is a new firmware it means your device some how couldnt get OTA to work properly. you may wanna check whether your device's knox is void.
All how-to mentioned above can be found in xda.
alex.do said:
Give it a check whether your device does actually get any updates using Frija here:
https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594/
Just need to find the correct CSC.
If there is a new firmware it means your device some how couldnt get OTA to work properly. you may wanna check whether your device's knox is void.
All how-to mentioned above can be found in xda.
Click to expand...
Click to collapse
Thanks!
So I checked it on Frija as you said and it turns out there is a software update (Android 10) for my phone. The problem is that I got some updates after purchasing but now it is stuck on November security update. Do you recommend I wait for an OTA or maybe flash it manually?
Of123 said:
Thanks!
So I checked it on Frija as you said and it turns out there is a software update (Android 10) for my phone. The problem is that I got some updates after purchasing but now it is stuck on November security update. Do you recommend I wait for an OTA or maybe flash it manually?
Click to expand...
Click to collapse
Lets go with some more checks to make sure your phone is still OTA-able
1. Manually check for update: go to Settings -> Software Update -> Download and install see if you can get any updates. If you are on a VPN or proxy, try without it just in case the update server somehow gets blocked (doubt that. but... lets give it a try)
2. Go to download mode: Vol down + Bixby + Power combination and check the Knox status. if your knox is intact you should see something like Warranty void 0x0. If its 0x1 then your Knox is void and this is permanent Samsung makes sure of that. Unless you get a mainboard replaced, i dont think you are able to get OTA working again.
3. Use Samsung SmartSwitch on PC (with your phone connected) see if it can update your phone, the "official" way.
3b. Or try flashing a latest stock firmware, again, stock firmware, with Odin. you must use the HOME_CSC... not CSC... to keep existing apps and data. Then wait for the next update see if OTA works.
Flashing a stock firmware should not void your Knox nor cause any problems. Just be careful of the risk of losing exising data.
alex.do said:
Lets go with some more checks to make sure your phone is still OTA-able
1. Manually check for update: go to Settings -> Software Update -> Download and install see if you can get any updates. If you are on a VPN or proxy, try without it just in case the update server somehow gets blocked (doubt that. but... lets give it a try)
2. Go to download mode: Vol down + Bixby + Power combination and check the Knox status. if your knox is intact you should see something like Warranty void 0x0. If its 0x1 then your Knox is void and this is permanent Samsung makes sure of that. Unless you get a mainboard replaced, i dont think you are able to get OTA working again.
3. Use Samsung SmartSwitch on PC (with your phone connected) see if it can update your phone, the "official" way.
3b. Or try flashing a latest stock firmware, again, stock firmware, with Odin. you must use the HOME_CSC... not CSC... to keep existing apps and data. Then wait for the next update see if OTA works.
Flashing a stock firmware should not void your Knox nor cause any problems. Just be careful of the risk of losing exising data.
Click to expand...
Click to collapse
So
1. Phone says it's up to date
2. Download mode shows that warranty is intact "0 and 0x000
3. Smartswitch didnt show any updates
3b. I still did not try this, its been a long time since i flashed any software on a samsung phone (since the S2), i guess i might give it a try??
Of123 said:
So
1. Phone says it's up to date
2. Download mode shows that warranty is intact "0 and 0x000
3. Smartswitch didnt show any updates
3b. I still did not try this, its been a long time since i flashed any software on a samsung phone (since the S2), i guess i might give it a try??
Click to expand...
Click to collapse
Hmmm then maybe i was guessing wrong the whole time. maybe theres nothing wrong with your phone. its your unlocked (unbrand) us. normally carriers (brand ones) would be pushing updates faster. maybe you will need to wait for samsung to push the updates for unbrand phones, which could be usually slower. am not sure.
maybe you might wanna go with the flashing option. you using stock firmware so there shouldnt be any risks and would be pretty easy do to just follow the steps.
sorry i wasnt helpful enough mate
Edit: just wanna share 1 more thing i been suffering with latest update. if you upgrade to 10 and one ui 2.0, android (and/or samsung) has completely blocked using custom fonts. gxfonts wings or other theming apps no longer works with changing fonts. so if you re using custom fonts it will survive the update just make sure you dont change it or you will lose it. am almost abt to give up knox to go root now.
alex.do said:
Hmmm then maybe i was guessing wrong the whole time. maybe theres nothing wrong with your phone. its your unlocked (unbrand) us. normally carriers (brand ones) would be pushing updates faster. maybe you will need to wait for samsung to push the updates for unbrand phones, which could be usually slower. am not sure.
maybe you might wanna go with the flashing option. you using stock firmware so there shouldnt be any risks and would be pretty easy do to just follow the steps.
sorry i wasnt helpful enough mate
Edit: just wanna share 1 more thing i been suffering with latest update. if you upgrade to 10 and one ui 2.0, android (and/or samsung) has completely blocked using custom fonts. gxfonts wings or other theming apps no longer works with changing fonts. so if you re using custom fonts it will survive the update just make sure you dont change it or you will lose it. am almost abt to give up knox to go root now.
Click to expand...
Click to collapse
Thanks a lot mate, you've helped by showing me that there's nothing wrong.
As with any update there are always problems, so considering to just keep waiting for the OTA for now, it's not like there are new features in it, Samsung already have everything you could ever think of.
alex.do said:
Hmmm then maybe i was guessing wrong the whole time. maybe theres nothing wrong with your phone. its your unlocked (unbrand) us. normally carriers (brand ones) would be pushing updates faster. maybe you will need to wait for samsung to push the updates for unbrand phones, which could be usually slower. am not sure.
maybe you might wanna go with the flashing option. you using stock firmware so there shouldnt be any risks and would be pretty easy do to just follow the steps.
sorry i wasnt helpful enough mate
Edit: just wanna share 1 more thing i been suffering with latest update. if you upgrade to 10 and one ui 2.0, android (and/or samsung) has completely blocked using custom fonts. gxfonts wings or other theming apps no longer works with changing fonts. so if you re using custom fonts it will survive the update just make sure you dont change it or you will lose it. am almost abt to give up knox to go root now.
Click to expand...
Click to collapse
I'm checking Sammobile and Frija for the firmware for my specific csc and couldn't find it anywhere. Is it ok to flash another country's firmware?