[GUIDE] How to get the official OneUI open beta snapdragon on a locked s8/s8+ - Samsung Galaxy S8 Guides, News, & Discussion

1.Download modded odin HERE.
If you don't know how to use Odin there are tons of tutorials. Just never use the userdata section unless you plan on starting fresh from the setup screen.
2.Download latest firmware for SM-G950u1 Or G955u1 for + models. Shouldn't be carrier specific though I used my carriers when doing so.
I got my firmware from https://updato.com
3.Flash the firmware using Odin.
4.Power on the phone and go to Google play
5.Download samsung+ and scroll down to join Samsung+ beta
6. After you update the Samsung+ app to the beta you should have a banner invite in the Samsung+ app to opt into the oneui beta,
7. After you opt in to OneUI go to software update and it should be ready for download
Side note, you can also flash the update file directly from an sd card for the latest pie beta if you want to skip the Samsung+ part. Just make sure you rename the latest beta firmware to update.zip and place it in the root folder of your sd card.
You need to be on U1 firmware as that's unlocked device firmware otherwise it will not work.

someone has the link with the beta update to load it with the sd?

Thanks for this update man, wish I could known this before I flashed the ZSAB firmware. Its working fine with me with the ZSAB firmware as Netflix is now working. I had to flash the sm-g950u1 firmware first.
---------- Post added at 06:34 PM ---------- Previous post was at 06:19 PM ----------
racuna95 said:
someone has the link with the beta update to load it with the sd?
Click to expand...
Click to collapse
This is where I got the firmware after flashing the CLR2 sm-g950u1 on my Verizon unlocked s8 on t mobille. https://downloadmirror.co/2CXh/SS-G...=LdUniblIAWIL+sfjZK7ot6v3B16RNMoXDzapUtOlNo4=

Thank you! I'm testing it and it's pretty stable at the moment

racuna95 said:
Thank you! I'm testing it and it's pretty stable at the moment
Click to expand...
Click to collapse
Only issue I have run across is that bluetooth headphones will get disconnected from time to time and no super slow motion setting to change to multiple shots or manual

Is this guide for U.S. carrier locked S8+'s? Can I do this with my locked sprint s8+?
edit: now i'm getting some kind of "package expects build fingerprints of" so on and so on. I'm on CRL2 trying to install by Sd.

I'd the ZSAB to ZSAI update for snapdragon s8+ available yet?

This isn't working for me. Odin'ed CRL2 on my Sprint locked S8+ successfully, but i'm not able to flash the ZSAB firmware after that, through recovery or sideload. Getting a bunch of errors in recovery and in the end, ends up aborted. Welp

Is there an OTA update to go from SA4 to a One UI firmware? I have access to a Mac only, and Jdoin3 isn't able to get the PIT file from my G950U

Related

Galaxy S9+ Pie Beta

I had a bit of trouble installing Pie on my device. Since I have AT&T and AT&T devices do not get beta updates (the betas are internally tested by AT&T staff), I had to flash an unlocked U1 firmware to get the update. When I flashed the newest firmware for U1 using the modded Odin by Raymond, my phone legitimately bootlooped on the Samsung start-up screen. I, then, wiped the cache, /data and mounted the /system directory, and rebooted the phone. Voila! I was on Android 8.0.0 for U1, and then I signed up for the beta program through Samsung+ (I had to sideload the newest beta version of Samsung+). Within 20 mins, I manually checked the software updates and Pie was ready. And everything went smoothly after that.
Some steps to flash U1 Firmware
- Use Modded Odin
- Get correct firmware with the same or newer bootloader for your device
- Try updating the firmware using an OTA.zip file from SD Card or through adb sideload
Best of luck to all AT&T customers rearing to get Pie.
Hey there, also on an AT&T S9+ locked device. Currently on BRJ5. Am I correct in reading that we have no choice but to wipe data to update?
JewishMatt said:
Hey there, also on an AT&T S9+ locked device. Currently on BRJ5. Am I correct in reading that we have no choice but to wipe data to update?
Click to expand...
Click to collapse
Yes. You have 2 options.
1. Flash to U1. That requires a wipe. Sign up for beta.
2. Side load the builds. You'll need to be on ARIB. You can Odin to ARIB or in my case, I Odin to ARI6, and sideload to ARIB, then sideload to K9 build.
ATT causes a wipe every time you side load. So if you stay on the U firmware, every time a new beta is out, you get wiped. If you swap to the U firmware, the Beta will do an Ota, which does NOT wipe.
If you don't care about video calling, wifi calling or Volte (not 100% on that one), go to the U1 firmware and hope the beta isn't full.
We need an AT&T employee to drop the files up in here...
Perfect on my ATT s9+

SM-G930U root for v9 Bootloader "G930UUEU9CSA3"

i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
kpwnApps said:
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
Click to expand...
Click to collapse
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
cooltt said:
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
Click to expand...
Click to collapse
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
snaksalot said:
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
Click to expand...
Click to collapse
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
cooltt said:
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
Click to expand...
Click to collapse
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
snaksalot said:
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
Click to expand...
Click to collapse
Hmmm so it may be that loophole is now closed, what you need to think about is if you deffo need root? Or is it just nice to have. I'm sure a dev will get round it soon.
snaksalot said:
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
Click to expand...
Click to collapse
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
kpwnApps said:
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
Click to expand...
Click to collapse
Okay I was completely unaware of TWRP being an option or the possibility of Magisk with a locked bootloader, now to clarify I'm running the latest unbranded US Region firmware for the US T-Mobile version of the Qualcomm Galaxy S7 "(TMB) G930UUEU9CSA3" that being said I have a few questions about how to specifically to proceed if you don't mind helping me?
First is the version of Odin available from the post provided above inst the modified version I've been required to use for all my previous flashing "Odin3_v3.13.1_3B_PatcheD" should I use this one or the version provided in the post above "Odin3_v3.13.1"?
My next question is that all the different versions and variants of TWRP available for my device the Galaxy S7 and the S7 Edge are either for Exynos Canada/International or Korea or the Chinese Qualcomm variant of each. Should I download and use the TWRP for the Chinese Qualcomm S7?
The sammobile link in the original post for "Android 8.0 Oreo Stock Rom" provides me with a list of the latest and up to date international versions of firmware for the Galaxy S7 Edge "SM-G935FD" I'm assuming I should just use the stock firmware image for my device "SM-G930U" instead?
The link for the no-verity-opt-encrypt-6.0 is dead but I don't think its needed because of something someone said in the original post about this method failing after latest security update "the one I'm on" https://forum.xda-developers.com/showpost.php?p=78115895&postcount=18 he said he solved it easily with information and another flash able zip from this post https://forum.xda-developers.com/showpost.php?p=77000849&postcount=47 and the zip from here https://forum.xda-developers.com/showpost.php?p=76564735&postcount=37
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
snaksalot said:
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
Click to expand...
Click to collapse
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
I'd be interested to know how this turned out if the device with V9 bootloader could be rooted with temp TWRP method.
Can i actually flash magisk on my 930u?
Is there any way to root my g930t ?
I'm on v9 bootloader, and i don't care about knox tripping.
Did developpers really failed to break the security of this little old device ? Or no one worked it ?
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Toolmighty said:
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Click to expand...
Click to collapse
Yes same hardware
cooltt said:
Yes same hardware
Click to expand...
Click to collapse
Can't get twrp to flash. Tried w rom as is, tried factory reset tried reinstall w/o auto reboot. All get same error
what about jruze root?
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
nm it uses flashfire
Toolmighty said:
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
Click to expand...
Click to collapse
Yes by using 1st and #1623 post number it can be rooted easily. I already have done that on both G930P and G930U.

Sos help - nothing pass by odin

the phone was initially on android Nougat 7.1.1, I updated it officially to android Oreo
after that, I flashed new STOCK ROM Oreo too, by Odin for the first time for this phone after unpacking and updating it from Nougat to Oreo
now I cannot flash anything by Odin TWRP, ROOT, STOCK ROM, COMBINATION FILE .... nothing pass
I can't even flash any other stock ROM beside the one i flashed before, either it's the same android version or not
odin always fail
I Waited 190 hours (more than 7 days) of continuous up time without restarting to have access and Remove FRP Lock but no luck at all, still the same
SEE ATTACHMENTS For Photos
SM-A530F/DS
Odin3 v3.13.1
Android 8.0.0 Oreo
Country / Region : Morocco (MWD)
PDA : A530FXXS4BSB1
Product Code : MWD
CSC : A530FOJM4BSB1
Phone : A530FXXU4BRL8
COMBINATION_OXM_FA71_A530FXXU4ASB1_BoxWares.tar
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
emovere said:
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
Click to expand...
Click to collapse
It looks like your trying to down grade to a version 3 and you can't do that.
Sorry wrong person.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
Pro Cal said:
the phone was initially on android Nougat 7.1.1, I updated it officially to android Oreo
after that, I flashed new STOCK ROM Oreo too, by Odin for the first time for this phone after unpacking and updating it from Nougat to Oreo
now I cannot flash anything by Odin TWRP, ROOT, STOCK ROM, COMBINATION FILE .... nothing pass
I can't even flash any other stock ROM beside the one i flashed before, either it's the same android version or not
odin always fail
I Waited 190 hours (more than 7 days) of continuous up time without restarting to have access and Remove FRP Lock but no luck at all, still the same
SEE ATTACHMENTS For Photos
SM-A530F/DS
Odin3 v3.13.1
Android 8.0.0 Oreo
Country / Region : Morocco (MWD)
PDA : A530FXXS4BSB1
Product Code : MWD
CSC : A530FOJM4BSB1
Phone : A530FXXU4BRL8
COMBINATION_OXM_FA71_A530FXXU4ASB1_BoxWares.tar
Click to expand...
Click to collapse
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Dantar0 said:
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Click to expand...
Click to collapse
You can from Pie to Oreo some country received Oreo now so they come with BL 4
emovere said:
Which file are you trying to flash?
If I'm not wrong you could flash any firmware with version 4 or upper. For example you could not flash A530FXXU3BSA3 (Version 3) but it should be fine with A530FXXS4BSB1 (Version 4).
Click to expand...
Click to collapse
thanks a lot for the feedback, appreciated
if I understood it correctly the version number is the tow characters that comes after XX like U3 or S4 right ?
how to know the version number you mentioned exactly ?
and what about TWRP then, why even TWRP won't pass
mchlbenner said:
It looks like your trying to down grade to a version 3 and you can't do that.
Sorry wrong person.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Click to expand...
Click to collapse
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock rom for 7.1.1 but even with same current version "Oreo" nothing pass
how can I know the version you mentioned please ?
Dantar0 said:
Samsung updated the binary from Nougat to oreo. Its impossible to downgrade. Its thr same with pie, you can downgrade to oreo for now as it still has the same binary on the latest security patch.
Click to expand...
Click to collapse
how to know please the exact binary version or locate ot on the PDA File for example PDA : A530FXXS4BSB1
Pro Cal said:
how to know please the exact binary version or locate ot on the PDA File for example PDA : A530FXXS4BSB1
Click to expand...
Click to collapse
For that, the binary is 4 (after the FXXS)
https://www.sammobile.com/firmwares/galaxy-a8/SM-A530F/MWD/
As you can see, Samsung updated the binary on the latest security update for your region. Its impossible to downgrade to a previous OS due to having different binaries. You'll also find that even though it's oreo, the binary updated from the January security patch to February's. Probably to make way for android 9 One UI.
The only option is to flash oreo but with the February security patch
Dantar0 said:
For that, the binary is 4 (after the FXXS)
https://www.sammobile.com/firmwares/galaxy-a8/SM-A530F/MWD/
As you can see, Samsung updated the binary on the latest security update for your region. Its impossible to downgrade to a previous OS due to having different binaries. You'll also find that even though it's oreo, the binary updated from the January security patch to February's. Probably to make way for android 9 One UI.
The only option is to flash oreo but with the February security patch
Click to expand...
Click to collapse
many thanks for the feedback and effort
so basically it means nougat is out of the question
and tell me please why country si important, I can flash any other firmware for another country as longer it the same binary version, right ?
and what about root for this binary version or TWRP why it won't pass either ?
Pro Cal said:
many thanks for the feedback and effort
so basically it means nougat is out of the question
and tell me please why country si important, I can flash any other firmware for another country as longer it the same binary version, right ?
and what about root for this binary version or TWRP why it won't pass either ?
Click to expand...
Click to collapse
You can flash a different regions firmware as long as you download the right variation. (SM-A530F)
Sorry but I don't know much about rooting this phone though
Pro Cal said:
thanks a lot for the feedback, appreciated
if I understood it correctly the version number is the tow characters that comes after XX like U3 or S4 right ?
how to know the version number you mentioned exactly ?
and what about TWRP then, why even TWRP won't pass
Click to expand...
Click to collapse
Read post if you had read before you jump this would not have happened.
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
mchlbenner said:
Read post if you had read before you jump this would not have happened.
You can't flash twrp because your in prenormal state you have to wait 168 hour no reboots.
Are you trying to down grade to 7.1?
Click to expand...
Click to collapse
I did read it and did answer you but it's you who didn't read mine otherwise you wouldnt repeat the same thing
*********************
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock ROM for 7.1.1 but even with same current version "Oreo" nothing pass
Pro Cal said:
I did read it and did answer you but it's you who didn't read mine otherwise you wouldnt repeat the same thing
*********************
actually I already did waited 190 of continuous up time, then after directly tried to flash TWRP and still no pass in Odin fail
I did tried to flash stock ROM for 7.1.1 but even with same current version "Oreo" nothing pass
Click to expand...
Click to collapse
Is your phone branded.
Post this info screenshot example .
I will see if I can figure this out.
mchlbenner said:
Is your phone branded.
Post this info screenshot example .
I will see if I can figure this out.
Click to expand...
Click to collapse
Nop i dnt think so
Pro Cal said:
Nop i dnt think so
Click to expand...
Click to collapse
That as far that you can down grade to.

Question Q: What to do with ATT Snapdragon SM-S908 stuck on OneUI 5.0 beta 1? (Re-enable OTA)

Essentially I'm in a pickle and I'm currently running OneUI 5.0 beta 1 on my Samsung Galaxy S22 Ultra ATT locked device (SM-S908U) and I sideloaded the .bin for the official SMS908U beta build and it flashed and wiped everything and works fine. Except ONEUI 5 stable is coming out soon and I have tried Odin flashing several builds of Android 12 OneUI 4.1, I have tried Samsung Smart Switch emergency initialization (which doesn't show my device after failing to post the update), I went to Samsung Members but it says something about changed country info or not being in the Beta, but once I go to the open card to actually enroll for the beta, it says I'm already on it because it thinks since I have it at all its legit but it doesn't talk to the same exact framework of the app to find out if I need to officially enroll still. Either way I cannot opt out via Members either, I am fairly stuck. Any advice ?
*I do not have any backups from Android 12 stable.
You tried flashing official firmware for U device right? You were using CSC file or HOME_CSC to preserve data?
Going back from beta to stable means wiping data, phone will factory reset when you flash back the stable firmware and you should use the CSC file (not HOME_CSC)
Yeah... I know how to operate Odin3... It literally says right there I tried flashing multiple stable builds and each time it fails with AUTH error. Tried HOME and regular CSC....
I have the same phone. I have not gone back to stock U firmware from beta. But I have gone from beta to stock U1 firmware. I believe once you go back to stock U1 Android 12. You can flash back with Odin not patched to U firmware.
zlib1 said:
Essentially I'm in a pickle and I'm currently running OneUI 5.0 beta 1 on my Samsung Galaxy S22 Ultra ATT locked device (SM-S908U) and I sideloaded the .bin for the official SMS908U beta build and it flashed and wiped everything and works fine. Except ONEUI 5 stable is coming out soon and I have tried Odin flashing several builds of Android 12 OneUI 4.1, I have tried Samsung Smart Switch emergency initialization (which doesn't show my device after failing to post the update), I went to Samsung Members but it says something about changed country info or not being in the Beta, but once I go to the open card to actually enroll for the beta, it says I'm already on it because it thinks since I have it at all its legit but it doesn't talk to the same exact framework of the app to find out if I need to officially enroll still. Either way I cannot opt out via Members either, I am fairly stuck. Any advice ?
Click to expand...
Click to collapse
Any chance you still have the flashing zip file for beta 1 s908?
The link for beta 1 in this post isn't working
If you do can you send it to me please?
Thanks

Question Android 13

Z flip 4 is supposed to get OneUI 5.0 with A13 in November, but it just received the November security patch without A13. Do you think that A13 will get delayed for our phone?
I read here that beta 2 was released recently. Usually they will issue beta 3 before it will be final. So yes, I can see the A13 can be delayed till December.
But that's no biggie really. Not that much changed from A12 to A13 anyway.
Beta 4 ZVK3 is under testing at the moment
I am still stuck in beta 1 ZVK9. I manually load this one, after that, keep looking for beta 2, 3 and 4 now. No luck. For those if you are still in A12, maybe be patient. Google Pay won't work in beta software, I don't see other issues.
johnny8910 said:
Beta 4 ZVK3 is under testing at the moment
Click to expand...
Click to collapse
Oh, good to know.
I guess my part regarding delay is irrelevant then.
What about performance? Any significant variances against A12? How's the battery life?
starche_old said:
What about performance? Any significant variances against A12? How's the battery life?
Click to expand...
Click to collapse
No massive changes, but does seem snappier. Ram Memory management is improved over A11 in my opinion.
Battery life for me is exactly the same.
Has anyone managed to get the firmware file or the fetch the ota update file, for the US model, for the stable release yet?
I too, curiously any one (service/model) combination in US get official A13 update?
I have F721U1 directly purchased from samsung.com. I am with US mobile service (VZW MVNO). I manually apply A13 beta 1. Phone runs fine and does not hit any issues as I am aware in my usage pattern.
However, Gpay won't work with beta SW. Keep googling without any luck for official download Link. Tired for read all different web site post update screen and news announcement. None of them has download link.
Missed previous Pixel phones, Google post Full and OTA as soon as they announce update news. I can always download and apply myself.
Maybe a couple days more.....
https://www.sammobile.com/news/galaxy-z-flip-4-fold-4-android-13-update-stable-released/
krusir said:
Missed previous Pixel phones, Google post Full and OTA as soon as they announce update news. I can always download and apply myself.
Click to expand...
Click to collapse
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Thank you. I will try it when I find download link.
SandFromUndertal said:
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Click to expand...
Click to collapse
SM-F721B A13 CSC SLK is official
Download from Samfirm
SandFromUndertal said:
The Z Flip 4 and fold 4 got the update a few hours ago in Korea, so hopefully it should be coming for the US models very soon.
You may have to end up flashing the SM-F721U firmware instead of the SM-F721U1 firmware, as the U firmware typically becomes available before the U1 firmware, if I remember correctly. In order to flash the U firmware over the U1 firmware, you need to use a patched version of Odin, here's the link for that - https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/ and make sure to download the file named "Odin3 v3.14.1_3B. The process of flashing is identical to normal Odin, and if you want to keep your data make sure to flash the HOME_CSC and not the standard CSC file
Click to expand...
Click to collapse
I knew that u1 is the Google Fi version. But what exactly is the software different between the two? You can use non fi sim card on an u1.
Flashed One UI 5 yesterday. From the SM-F721B EUX to SM-F721B SRI, dirty flash.
Worked fine, it feels a little more smooth but I was expecting more changes tbh.
EUX upgrade live today for me.
One day later for me. Also EUX.
acytoo said:
I knew that u1 is the Google Fi version. But what exactly is the software different between the two? You can use non fi sim card on an u1.
Click to expand...
Click to collapse
The only difference between the two is the carrier (U) firmware has carrier specific features, not apps, that aren't in the unlocked (U1) firmware. For example, people who have AT&T as their carrier, such as myself, can get AT&T's 5G+ an I have no idea what AT&T's 5G+ even is. Also the U1 version isn't the Google Fi version, I'm guessing when you buy a Google Fi Z flip they use the unlocked variant and just put a sim card inside of it.
krusir said:
Thank you. I will try it when I find download link.
Click to expand...
Click to collapse
In case you haven't found it yet, and one UI 5 is out, you can use samloader, which is a terminal/command line tool that allow you to download firmware straight from Samsung's servers. On Linux it is as simple as running pip install git+https://github.com/samloader/samloader.git and on windows I don't know what to do as I don't primarily use it. The only Idea I have is to download python for windows, clone the repository and copy the files to the same directory of python.exe.
The command to download the firmware using samloader - samloader -m SM-F721U -r TMB -v F721USQU1BVK3/F721UOYN1BVK3/F721USQU1BVK3/F721USQU1BVK3 -o <name of file, e.g. flip4-oneui5.zip or SM-F721U-OneUI5.zip>

Categories

Resources