Right now I am on AT&T firmware CTA2 which is the v2 bootloader. I know if I take the OTA (I have it frozen so it doesn't auto update) to the March security patch it will update my bootloader to v3 and block my ability to revert back to Android 9. I am asking is anyone else in the same boat here and if so what did you? Keep v2 or jump to v3?
Anyone? Guess I am alone here on this one.
I upgraded to 10 before rooting mine, luckily the Binary code was still v3 aka build number G975FXXS"3"ASJG, so reverted to pie and rooted it.
Reason,as samsung are making it harder to root and i wasn't risking upgrading it.
Also no reason too, as custom roms will be made which will be 10, so best of both worlds
Wingchundub said:
I upgraded to 10 before rooting mine, luckily the Binary code was still v3 aka build number G975FXXS"3"ASJG, so reverted to pie and rooted it.
Reason,as samsung are making it harder to root and i wasn't risking upgrading it.
Also no reason too, as custom roms will be made which will be 10, so best of both worlds
Click to expand...
Click to collapse
So what I am getting here is that you were on v3 bootloader and went back to Pie?
Yes, Look at the binary code, you will see number 3 in my build number.
there is a few more updates in pie, and also i think the first two in 10 that have binary code 3 in build number.
As i did update to 10 BUT only to the last update which contained the number 3 as i show in build number.
Thererfore i was able to revert back.
If i went further to binary code 4, then i'd be screwed
the last v3 you can use which is on android 10 and you can revert back if you wish is:-
2020-01-06 10 G975FXXS3BSL4 G975FOXM3BSKO
the next android 10 update v4 is:- 2020-02-12 10 G975FXXU4BTA8 G975FOXM4BTB1 (Do not update this, if you want to revert back to pie)
these are updates for my BTU G975f
Wingchundub said:
Yes, Look at the binary code, you will see number 3 in my build number.
there is a few more updates in pie, and also i think the first two in 10 that have binary code 3 in build number.
As i did update to 10 BUT only to the last update which contained the number 3 as i show in build number.
Thererfore i was able to revert back.
If i went further to binary code 4, then i'd be screwed
the last v3 you can use which is on android 10 and you can revert back if you wish is:-
2020-01-06 10 G975FXXS3BSL4 G975FOXM3BSKO
the next android 10 update v4 is:- 2020-02-12 10 G975FXXU4BTA8 G975FOXM4BTB1 (Do not update this, if you want to revert back to pie)
these are updates for my BTU G975f
Click to expand...
Click to collapse
Hey sorry for the real late reply, I just now dug up this thread. I noticed you have G975F phone. Is it rooted? I have a G975U phone. Does this matter? If I update to bootloader v3 (which is the bootloader my carrier is on), I can go back to Pie as long as I don't update to bootloader v4?
Reports in the forum here are saying once you've updated to a newer bootloader version you can't go back for the G975U version of the phone.
StoneyJSG said:
Hey sorry for the real late reply, I just now dug up this thread. I noticed you have G975F phone. Is it rooted? I have a G975U phone. Does this matter? If I update to bootloader v3 (which is the bootloader my carrier is on), I can go back to Pie as long as I don't update to bootloader v4?
Reports in the forum here are saying once you've updated to a newer bootloader version you can't go back for the G975U version of the phone.
Click to expand...
Click to collapse
I did have the G975f which i did root successfully, sold it on and replaced it with the A71. which is much cheaper, a cracking phone, and has snapdragon chip which are much faster than exynos.
Midrange phones are now coming up to the main flagship phones, and cameras are excellent on it, and its also rooted.
Anyhow.........
Anyway if your s10 has the Exynos chip, you can root, if it has Snapdragon, as far as i know its not possible, you'd need to search.
As i mentioned in post, if the binary code aka 3 remains and it does in the early 10 release, then you can of course go back to pie, as i did.
If you upgrade to binary code 4 aka BL 4, you can not downgrade back to v3.
I'm not sure if it is still rootable at v4, you'd have to check, as like i say, i don't have mine anymore and never got to that stage to investigate.
Hope that helps you bud
Wingchundub said:
I did have the G975f which i did root successfully, sold it on and replaced it with the A71. which is much cheaper, a cracking phone, and has snapdragon chip which are much faster than exynos.
Midrange phones are now coming up to the main flagship phones, and cameras are excellent on it, and its also rooted.
Anyhow.........
Anyway if your s10 has the Exynos chip, you can root, if it has Snapdragon, as far as i know its not possible, you'd need to search.
As i mentioned in post, if the binary code aka 3 remains and it does in the early 10 release, then you can of course go back to pie, as i did.
If you upgrade to binary code 4 aka BL 4, you can not downgrade back to v3.
I'm not sure if it is still rootable at v4, you'd have to check, as like i say, i don't have mine anymore and never got to that stage to investigate.
Hope that helps you bud
Click to expand...
Click to collapse
So v3 can go back to v2 bootloader? I have a snapdragon G975U phone running AT&T firmware so I can't root it. I just don't wanna brick my phone if I unfreeze the update and update to v3 then wanna go back to v2 bootloader later.
Related
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
CKR83 said:
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
Click to expand...
Click to collapse
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Rooting Help?
fgth90 said:
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Click to expand...
Click to collapse
I see that there are tutes here, and am wading through the 50+ pages of forum posts to find what I need. However, my worry is that none of this stuff will work because of the new firmware. Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Thanks all the pertinent info, I think.
Because the update was so new, I don't think there's a way to root this anymore. People keep telling me to use ODIN and to download an earlier ROM (and I now have ODIN and an earlier ROM -- hopefully from a good source, but I have no idea if it is), but my impression is that this latest AT&T "security" update keeps you from reflashing the ROM because of the bootloader lockout.
Any further help would be appreciated.
Thanks
CKR83 said:
...
Any further help would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
As I told you, the only method working for me (because of towelroot non working) is cf auto root.
Check periodicaly here http://autoroot.chainfire.eu/ to see if your model is listed.
I had just a look and it's not listed yet.
If it is, flash by odin and look if root works.
If not, you've got to flash by odin the same rom again (keep your original file on pc), you'll loose nothing, and report this fails on chainfire to test other solution.
Good luck
Franky
CKR83 said:
Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Not only build number and kernel version, you need to check your Bootloader version with Phone INFO ★Samsung★ app (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
vndnguyen said:
Not only build number and kernel version, you need to check your Bootloader version with (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
Click to expand...
Click to collapse
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Does that help any? People keep telling me I need to use ODIN and flash this, that or the other thing. Those comments would probably be more helpful if I knew more about this stuff, but my reading has lead me to believe that ODIN won't work with certain version of the bootloader. Or is that wrong?
CKR83 said:
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Did you every get your post July 2014 AT&T GS5 rooted?
If so, please drop me an email.
Thanks
TPG
Click to expand...
Click to collapse
No unfortunately not....
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Will I have to wait for a developer to build an oreo room and get the bugs ironed out? (No, I cannot build it myself) or is there any chance that there will be an easy way to upgrade to oreo and keep root access intact?
It will take a Dev to port it. Taking the upgrade, if available, will erase root and custom recovery.
That said, a Dev can take the system.img and other partitions and and edit them to port it to this phone.
When I had a note 4 there were ports to the note 5, S6, S7 and note 7, Lollipop, Marshmallow, Nougat . There may even be one now for the S8.
Don't hold your breath.
Bottom line: You need to be rooted and someone needs to build a custom rom based on Oreo.
V20 is expected to get Oreo in the first quarter of 2018:
https://www.reddit.com/r/lgv20/comments/7gckad/the_g5_is_apparently_getting_oreo_before_the_v20/
Hopefully some devs will be around to root it, or provide a path from rooted machines to update without losing root.
phr00t said:
V20 is expected to get Oreo in the first quarter of 2018:
https://www.reddit.com/r/lgv20/comments/7gckad/the_g5_is_apparently_getting_oreo_before_the_v20/
Hopefully some devs will be around to root it, or provide a path from rooted machines to update without losing root.
Click to expand...
Click to collapse
YES!! (Hopefully) I have an unlocked AT&T version (not on AT&T) and I haven't got ANY updates, I ordered a AT&T GoPhone SIM, hopefully when I pop it in, I will get the updates
I would like to downgrade my galaxy s8 (G950U) sprint version from Oreo 8.0 back to Nougat 7.0 but I’ve been having a hard time figuring out if it’s possible.
Looking around I’ve seen people saying that’s it’s not possible due to the bootloader which doesn’t allow you to go down from v2 back to v1.
It’s also my understanding that the fifth number from the right is the bootloader version, in this case I have version two (G950USQU2CRC5). Now, looking at the Nougat releases for the phone, the last three that were released before Oreo show that they have the version two bootloader (G950USQS2BRB1, G950USQS2BQL1, G950USQU2BQK5).
So, would it be possible to downgrade if I used one of these three versions or are there other things preventing this that don’t involve the bootloader?
Thanks.
Yes. As long as the bootloader version of the package and the bootloader version on your phone are the same, you're fine.
Also, don't flash a bootloader 3 package unless you want to completely ditch Nougat or don't want root for a long time.
Potatey said:
I would like to downgrade my galaxy s8 (G950U) sprint version from Oreo 8.0 back to Nougat 7.0 but I’ve been having a hard time figuring out if it’s possible.
Looking around I’ve seen people saying that’s it’s not possible due to the bootloader which doesn’t allow you to go down from v2 back to v1.
It’s also my understanding that the fifth number from the right is the bootloader version, in this case I have version two (G950USQU2CRC5). Now, looking at the Nougat releases for the phone, the last three that were released before Oreo show that they have the version two bootloader (G950USQS2BRB1, G950USQS2BQL1, G950USQU2BQK5).
So, would it be possible to downgrade if I used one of these three versions or are there other things preventing this that don’t involve the bootloader?
Thanks.
Click to expand...
Click to collapse
did you ever get the chance to downgrade? could you please let me know how you did it? please include links to the files that work for you. thanks!
Deleted
Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?
that was the Sprint answer
SprintBama said:
Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?
Click to expand...
Click to collapse
If anything, they would change it to v7. Maybe they are waiting for a merger, which could happen next week
I checked for update today and got 1627.64mb g930pvpu6cre7 Samsung experience 9.0 with oreo.
I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.
Just received oreo on my s7 for boost. So far I'm not impressed. I was really hoping for Dolby on this but guess not. The build number is SMG930PVPU6CRE7
kalala said:
I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.
Click to expand...
Click to collapse
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.
i manfully updated @ 4:15. they sent it @ 1627.64 mb. still downloading. when I got my att update I tried all the batch root methods for my 935a. saving magisk for last bc I didn't have the boot.img for the cre4 update.
I I only had the "att beta" update from March. long story short it won't boot with the nougat eng.boot. I gave it an hour. I cleared the cache, factory reset, tried to add flash all of the earlier img files I had for oreo, nothing worked. had to flash it back to nougat bra1. I immediately requested the update again. they approved. the next day I attempted to flash magisk 16.4. w/ the modified odin 3.1.3 version. it wouldn't flash. with the cre4 boot.tar in hand, I tried every method on gods green earth to gain some sort of r/w access. it was late, I was tired, I flashed the eng boot. once again it was stuck at the Samsung boot logo. it wouldn't allow me into recovery to push the cre4 update zip. once again I'm back to bra1 nougat. I booted into recovery & updated it from the sd card. when it booted I noticed it wasn't anywhere as clean & polished as the ota I had twice. I've flashed back to brd1 ten times, & requested the ota. after smart switch, I used all the avail windows software I could acquire & kept trying, they won't send it. but they did provide me with a new picture for my samsung account. I'll post it later. gotta check out this 930p oreo.
razor001_ said:
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.
Click to expand...
Click to collapse
I don't think Heimdall works on High Sierra or even Sierra anymore.
I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?
schmism said:
I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?
Click to expand...
Click to collapse
almost zero... asuming that Oreo for "U" Variants step up with BL on this month maybe next one, is something pausible but stepping up two versions in any short time is questionable... but who knows. The best you can do is wait this or the next month for BL update on U variants.
To be clear I'm still on version 5. I will continue to put off the upgrade to 6.
I have my reasons for wanting a device that runs Android 7, but can that subsequently be upgraded to Android 8 (and above), and I am thinking that a second hand Galaxy S8 might do the job.
However, since I am looking at second hand phones, there is no guarantee that it would actually be on Android 7 (unless the online shop is willing to check for me), and I am just wondering if, in the instance where the phone comes with Android 8 or above, would I be able to flash it back to Android 7, or would it be dependent on bootloader version. And if it is bootloader version dependant, which version would allow me to downgrade back to Android 7?
Thanks.
xAxB said:
I have my reasons for wanting a device that runs Android 7, but can that subsequently be upgraded to Android 8 (and above), and I am thinking that a second hand Galaxy S8 might do the job.
However, since I am looking at second hand phones, there is no guarantee that it would actually be on Android 7 (unless the online shop is willing to check for me), and I am just wondering if, in the instance where the phone comes with Android 8 or above, would I be able to flash it back to Android 7, or would it be dependent on bootloader version. And if it is bootloader version dependant, which version would allow me to downgrade back to Android 7?
Thanks.
Click to expand...
Click to collapse
On the S8 android version 7 has a binary ( bootloader ) version 1. Early version of Oreo has a binary ( bootloader ) 1 as well ie: beta and next few upgrades. I can't remember exactly when the version 2 binary ( bootloader ) was introduced, might have been 3 or 4 version of Oreo before being stable.
If looking for a 2nd phone that can by downgraded to android 7 you will need bl version 1. Anything with bl version 2 and higher can not be downgraded to android version 7.
You can check in settings - about phone - software information - Baseband version. Binary ( bootloader ) number will be the 5th number/letter from the right, you can also check build number as well.
spawnlives said:
On the S8 android version 7 has a binary ( bootloader ) version 1. Early version of Oreo has a binary ( bootloader ) 1 as well ie: beta and next few upgrades. I can't remember exactly when the version 2 binary ( bootloader ) was introduced, might have been 3 or 4 version of Oreo before being stable.
If looking for a 2nd phone that can by downgraded to android 7 you will need bl version 1. Anything with bl version 2 and higher can not be downgraded to android version 7.
You can check in settings - about phone - software information - Baseband version. Binary ( bootloader ) number will be the 5th number/letter from the right, you can also check build number as well.
Click to expand...
Click to collapse
Thanks a lot. Do you know if custom ROMs, for instance Lineage also update the baseband as you go up versions?
The second hand shop I was looking at update everything they sell with the latest available update and I suspect that is common practice. So I am thinking that the best option for me would be to sacrifice the e-fuse on my Samsung S7 with Android 7.0, and start playing with various Android versions / ROMs. However, I may want to go back to Android 7.0 on that phone eventually, so it is important that I don't accidentally mess that up.
xAxB said:
Thanks a lot. Do you know if custom ROMs, for instance Lineage also update the baseband as you go up versions?
The second hand shop I was looking at update everything they sell with the latest available update and I suspect that is common practice. So I am thinking that the best option for me would be to sacrifice the e-fuse on my Samsung S7 with Android 7.0, and start playing with various Android versions / ROMs. However, I may want to go back to Android 7.0 on that phone eventually, so it is important that I don't accidentally mess that up.
Click to expand...
Click to collapse
I normally use stock rom's as some of my apps don't work well with custom roms. Usually the only time that i've installed a custom roms is if someone else is having trouble with the installation process then i revert back to stock.
The Baseband ( in about phone ) will always show the current version of the OS whether it's stock or custom that you are on ( including updates ).
As far as i know custom roms do not increase you bootloader version number. So you should be able to revert back to the current stock rom that your on. You can always check bootloader version in Download ( odin ) Mode.
If you have any questions you should ask in the custom roms section for more information.