For those who aren't already aware, N960U is the model number of all of the US carrier versions of the Note 9. The N960U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among these models: any U or U1 firmware version can be flashed to any U or U1 device at any time, assuming that you're not trying to downgrade the bootloader. A "U to U" or "U1 to U1" flash does not require a factory reset, but changing from one firmware to the other will require one. Also, U firmware is identical for the 4 base files (AP, BL, CP, CSC) for each individual build, no matter which carrier it comes from. So if you download 2 different carrier versions of the exact same build, the 4 base files will be identical. Where the firmware differs is in the USERDATA file - that's where the carrier bloatware and customizations reside.
Manual Odin flashing is designed for those who:
- want to manually update to a newer version of U firmware on their U device, either because they don't want to wait for their carrier's OTA or because OTAs aren't working on their device, or a different carrier got a new feature/patch before they did
- want to flash U1 firmware to their U device
- want to convert from U1 firmware to carrier U firmware
- want to convert from one carrier's U firmware (with all apps and bloatware) to a different carrier's U firmware (with all apps and bloatware)
For those who aren't already aware, anyone can now download firmware for almost any Samsung device any time that they want, via the various firmware download tools posted here on XDA like SamFirm or Frija. There are threads and info about them here on XDA so I won't waste time explaining - do a search if you're not already familiar with these tools. But they only provide whatever the latest/newest/current version is - nothing older. I pay for a subscription to a site that gets the official releases (usually) before they hit the firmware download tools, so that's where my files come from.
This is not a "beginner's guide to Odin flashing" -type post/thread, so I won't list basic, step-by-step flashing instructions. My threads are geared towards those who already know what they're doing. If you're new to manually flashing Samsung firmware (or haven't done it in a long time), I recommend you consult one of those "beginner's" guides- there are tons of them here on XDA.
Happy flashing!
https://www.androidfilehost.com/?w=files&flid=282951
Notes:
- DON'T QUOTE THE OP WHEN YOU REPLY, kthx
- I have lots of threads just like this one for other Samsung flagships, if it interests you. For those who have already made use of my previous threads for a different device and are upgrading to a Note 9, welcome back
- My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc
- it's quite time consuming to download the files, zip them up, and upload them to AFH. And, I do threads like this for every single Sx and Note x model, so I won't be uploading every single version. The only full builds that I upload are ones where I get access to a new bootloader and/or Android version early, before they hit the firmware download tools.
- My naming method for folders on AFH is: build - bootloader - Android version
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- HOME CSC file keeps data intact; using the other CSC will wipe data. Flashing USERDATA will also wipe data.
- Since AT&T doesn't allow their firmware to be publicly available (for any of their devices), I'll try to always upload at least one USERDATA per bootloader increment for AT&T (and Cricket, if they get this model). I'll also upload any full builds if AT&T is the only carrier to get that specific build, because you won't be able to find the files anywhere else.
- For identifying USERDATAS, and to know what region/CSC to use in the firmware download tools if you're downloading yourself:
AIO = Cricket (not available via firmware download tools)
ATT = AT&T (not available via firmware download tools)
BST = Boost Mobile
CCT = Xfinity Mobile (Comcast)
CHA = Spectrum Mobile (Charter)
DSH = Dish Network
SPR = Sprint
TMB = T-Mobile
TMK = Metro PCS
USC = US Cellular
VZW = Verizon (available via firmware download tools, but Manual Entry is required - Auto will not work)
XAA = U1 firmware
- the correct procedure for switching from one carrier's firmware to another carrier's firmware is:
1. Flash full U1 firmware package including non HOME CSC
2. Upon boot, insert a SIM of the carrier whose firmware you want
3. Watch for the popup that says "reboot to apply new carrier settings" etc, and do it
4. After that restart completes, reboot back to Download mode and flash the full U firmware package, with the USERDATA file of the carrier whose firmware you want
Bootloader 2 added - build SGA
iBowToAndroid said:
Bootloader 2 added - build SGA
Click to expand...
Click to collapse
Thank you, thank you! Now, is it possible to just flash the user data? Or do I need to flash everything again?
rygaul44 said:
Thank you, thank you! Now, is it possible to just flash the user data? Or do I need to flash everything again?
Click to expand...
Click to collapse
That's not enough information. I would need to know what firmware you have now, and what firmware you're trying to go to
iBowToAndroid said:
That's not enough information. I would need to know what firmware you have now, and what firmware you're trying to go to
Click to expand...
Click to collapse
I'm currently on N960USQS2CSGB with my phone being on AT&T's network. Originally it was a Verizon note 9 and I swapped the SIM card. I then flashed the unlocked firmware to it to try to get VoLTE to work, but that didn't work so I flashed N960USQS2CSGA to the phone in hopes that I could get AT&T's firmware working. If I'm understanding correctly the USERDATA is where all the AT&T specific software and code is, so I'm wondering if I flash just the USERDATA, could I get the AT&T specific features to work. I got the OTA update to N960USQS2CSGB but that didn't fix the issue.
rygaul44 said:
I'm currently on N960USQS2CSGB with my phone being on AT&T's network. Originally it was a Verizon note 9 and I swapped the SIM card. I then flashed the unlocked firmware to it to try to get VoLTE to work, but that didn't work so I flashed N960USQS2CSGA to the phone in hopes that I could get AT&T's firmware working. If I'm understanding correctly the USERDATA is where all the AT&T specific software and code is, so I'm wondering if I flash just the USERDATA, could I get the AT&T specific features to work. I got the OTA update to N960USQS2CSGB but that didn't fix the issue.
Click to expand...
Click to collapse
Well, whose firmware/bloat do you have right now?
iBowToAndroid said:
Well, whose firmware/bloat do you have right now?
Click to expand...
Click to collapse
I'm assuming AT&T since some of their apps installed themselves and I have an AT&T boot logo, but I didn't flash the USERDATA when I flashed it back to the N960U firmware from the N960U1.
rygaul44 said:
I'm assuming AT&T since some of their apps installed themselves and I have an AT&T boot logo, but I didn't flash the USERDATA when I flashed it back to the N960U firmware from the N960U1.
Click to expand...
Click to collapse
Then you already have all of their stuff. Flashing USERDATA isn't going to make a difference
iBowToAndroid said:
Then you already have all of their stuff. Flashing USERDATA isn't going to make a difference
Click to expand...
Click to collapse
Thanks! I guess I'll be buying a new phone then, because I'm missing calls. The phone has to drop down from LTE to make or receive a call and it takes several seconds. I've had people call me and it ring all the way through before my phone steps down. When I make a call it takes about 10-15 seconds before it rings out. Oh well, I appreciate your help and quick replies!
rygaul44 said:
Thanks! I guess I'll be buying a new phone then, because I'm missing calls. The phone has to drop down from LTE to make or receive a call and it takes several seconds. I've had people call me and it ring all the way through before my phone steps down. When I make a call it takes about 10-15 seconds before it rings out. Oh well, I appreciate your help and quick replies!
Click to expand...
Click to collapse
Then that probably means that you don't have VoLTE in your area, or that you have poor signal in your area. I'm not sure that changing phones is going to help
iBowToAndroid said:
Then that probably means that you don't have VoLTE in your area, or that you have poor signal in your area. I'm not sure that changing phones is going to help
Click to expand...
Click to collapse
That was my original thought, but my wife has an AT&T branded note 9 that she bought direct from AT&T and hers works correctly. I'm trying to hold out for the Galaxy Fold, but I may end up going ahead and getting an AT&T note 10
rygaul44 said:
That was my original thought, but my wife has an AT&T branded note 9 that she bought direct from AT&T and hers works correctly. I'm trying to hold out for the Galaxy Fold, but I may end up going ahead and getting an AT&T note 10
Click to expand...
Click to collapse
Then maybe they won't provision your IMEI for VoLTE because they know it's not originally their device. They do that with wifi calling
Up
iBowToAndroid said:
Then you already have all of their stuff. Flashing USERDATA isn't going to make a difference
Click to expand...
Click to collapse
Before you buy a new phone, try flashing the latest AT&T update from here along with the user data from this thread if that download doesn't contain it. (It should). I'm trying to download to verify but it's only downloading at 1 MB/s for me.
iBowToAndroid said:
Then maybe they won't provision your IMEI for VoLTE because they know it's not originally their device. They do that with wifi calling
Click to expand...
Click to collapse
I figured as much, thought I'd try everything though. Again, thanks for your help!
---------- Post added at 06:58 PM ---------- Previous post was at 06:47 PM ----------
Bober_is_a_troll said:
Up
Before you buy a new phone, try flashing the latest AT&T update from here along with the user data from this thread if that download doesn't contain it. (It should). I'm trying to download to verify but it's only downloading at 1 MB/s for me.
Click to expand...
Click to collapse
I won't get my hopes up but I'll definitely try this.
rygaul44 said:
I figured as much, thought I'd try everything though. Again, thanks for your help!
---------- Post added at 06:58 PM ---------- Previous post was at 06:47 PM ----------
I won't get my hopes up but I'll definitely try this.
Click to expand...
Click to collapse
Worth a shot if the next step is an entirely new phone.
---------- Post added at 02:46 PM ---------- Previous post was at 01:59 PM ----------
iBowToAndroid said:
These are used for converting from one carrier's U firmware to AT&T's, or from U1 firmware back to U firmware with AT&T features and bloat. I know these are much tougher to find than other carriers' files - they can't be obtained from SamFirm or SamMobile. So I'll be uploading at least one for each bootloader version. Firmware is universal on U models so you can use the other 4 Odin files from any other firmware of the same build. Can probably even mix and match builds (as long as the Android version is the same), if you can't find files for the exact same build. Can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader.
- I remove the .md5 from each file solely for faster flashing (Odin won't check the hash without it). Rest assured, the files are perfectly fine and safe - Odin has a million safechecks built in.
- My naming method for AFH folders is: build - bootloader - Android version.
So "SAT - 1 - 9.0" means the full build number ends in SAT, it's bootloader version 1, and it's Android 9.0. When bootloader and Android versions increment, the first build to have those changes will have its folder notated appropriately.
- USERDATAs for any other CSCs can be gotten from SamFirm - for the latest version. If you need an old USERDATA for a CSC that's not commonly found on SamMobile (ACG, LRA, TFN, etc), let me know and I can probably get it.
https://www.androidfilehost.com/?w=files&flid=282951
Click to expand...
Click to collapse
Do you ha e the user data for SGB-2? I saw that you have SGA-2. Interchangeable? Or if they are not, do you have SGB-2?
Noob question but if I do flash the N960USQU2CSGA firmware for AT&T with the USERDATA provided here, I should be good for my unlocked Note 9 which is on N960U1UES2CSF9 right?
Also I would be able to get future updates OTA since I have an AT&T sim, right?
Thanks!
xAliasx said:
Noob question but if I do flash the N960USQU2CSGA firmware for AT&T with the USERDATA provided here, I should be good for my unlocked Note 9 which is on N960U1UES2CSF9 right?
Also I would be able to get future updates OTA since I have an AT&T sim, right?
Thanks!
Click to expand...
Click to collapse
Yes, you should then be on AT&T's update schedule
iBowToAndroid said:
Yes, you should then be on AT&T's update schedule
Click to expand...
Click to collapse
Thanks a lot! Did the flash and the OTA for the August update worked on my unlocked Note 9. Bad news is that the Wifi calling doesnt work still.
xAliasx said:
Thanks a lot! Did the flash and the OTA for the August update worked on my unlocked Note 9. Bad news is that the Wifi calling doesnt work still.
Click to expand...
Click to collapse
Just a note, if you are in the us, Google voice offers native wifi calling, if you really need it. I've always had a Google voice number that I use and give out as opposed to my usual mobile number, so it works really well for me.
Please Help!!!
I have the samsung galaxy note 9 F/DS what file would I need to flash to make my phone an at&t phone. I really want the wifi calling and enhanced messaging features. I recently got an OTA update that allowed me to be able to do volte calls but still no video calling wifi calling or enhanced messaging. Please help.
Related
I originally flashed from US to CE1 .374 w/ us oem fix. Not sure why I didn't use the custom UK that everyone else was using, but now I'm lagging behind in the updates. Can I use newflasher to switch between versions or is that just asking for trouble? I thought i saw somewhere about flashing and not losing user data, but that probably is for staying in the same verison?
also, after doing the us oem fix, can you update through ota? or do you have to reflash everytime?
Tron510 said:
I originally flashed from US to CE1 .374 w/ us oem fix. Not sure why I didn't use the custom UK that everyone else was using, but now I'm lagging behind in the updates. Can I use newflasher to switch between versions or is that just asking for trouble? I thought i saw somewhere about flashing and not losing user data, but that probably is for staying in the same verison?
also, after doing the us oem fix, can you update through ota? or do you have to reflash everytime?
Click to expand...
Click to collapse
You can flash new firmware without loosing your data. Use Xperiafirm to download the firmware of your choice. If you are looking for UK firmwares to flash, I would go with '1310-6856 Customized UK' as this is unbranded and you won't get any carrier bloatware in it.
Unpack newflasher into the same folder as the firmware. If you don't want to loose your data remove userdata_XFLASH.sin. Then start newfalsher.
I don't think OTA updates will work as you're in the worng region, but I'd be happy if someone corrected me on that.
I would hold off flashing until the new 47.1.A.5.51 is available for UK Customized, it should be any day now.
yip im on UK Customized, and its taking ages for the rollout to happen, but I think i will just wait as I found that when I changed regions before . The region that I switched to got rolled out at a different time the next rollout out.
I guess sony change the regions for very release.
OTA will work for you i.e you will get the UK Customized OTA if your in the states.
billbond4 said:
yip im on UK Customized, and its taking ages for the rollout to happen, but I think i will just wait as I found that when I changed regions before . The region that I switched to got rolled out at a different time the next rollout out.
I guess sony change the regions for very release.
OTA will work for you i.e you will get the UK Customized OTA if your in the states.
Click to expand...
Click to collapse
Thanks,
and it shouldn't undo the us oem fix from before?
Nope, it will stay on whatever region your using currently
Tron510 said:
I originally flashed from US to CE1 .374 w/ us oem fix. Not sure why I didn't use the custom UK that everyone else was using, but now I'm lagging behind in the updates. Can I use newflasher to switch between versions or is that just asking for trouble? I thought i saw somewhere about flashing and not losing user data, but that probably is for staying in the same verison?
also, after doing the us oem fix, can you update through ota? or do you have to reflash everytime?
Click to expand...
Click to collapse
I called Sony and asked them this question. "If I buy a UK phone from England and use it in the US, will updates take away the fingerprint sensor?" This was the answer, "No. If you install Sony Xperia Companion to your computer and do your updates that way, it will always update to UK version specs."
Hi, i would like to do a flash from UK/HK rom to CE1. Is there risky regarding TA or anything else ? Could i loose my camera and fingerprint usage ?
Thx
Sent from my G8441 using XDA-Developers Legacy app
zegoo said:
Hi, i would like to do a flash from UK/HK rom to CE1. Is there risky regarding TA or anything else ? Could i loose my camera and fingerprint usage ?
Thx
Sent from my G8441 using XDA-Developers Legacy app
Click to expand...
Click to collapse
The answer to your question is 5 posts up
& no you won't loose your TA keys
Oops !
Thx a lot, not seen...
Sent from my G8441 using XDA-Developers Legacy app
zegoo said:
Oops !
Thx a lot, not seen...
Sent from my G8441 using XDA-Developers Legacy app
Click to expand...
Click to collapse
and you do continue to get OTA updates of the region/brand you flashed.
After using newflasher to update to customized DE 47.1.A.7.1 saving my userdata with no problems, i decided to update to the newest 47.1.A.8.49 using the same method, and am having a few problems. first, when i startup, memory app and software update both have errors and stop. then settings have weird characters instead of %s.
I tried flashing back to .7.1 but went into a bootloop.
I flashed back to .8.49 and it works, but still has those problems that initally made me try flashing back to .7.1
Any ideas?
thanks
wonder if i'm doing something wrong when trying to preserve user data.. i'm trying to go from CustomUK (my phone is on 47.1.A.2.374) to Custom CE1 (which is on A.8.49). i downloaded the firmware files via XperiFirm, and removed the user data.sin file. I also replaced the OEM.sin file with the US version, then used newflasher. but my phone gets stuck in a boot loop, and i have to resort to wiping user data.
Tron510 said:
After using newflasher to update to customized DE 47.1.A.7.1 saving my userdata with no problems, i decided to update to the newest 47.1.A.8.49 using the same method, and am having a few problems. first, when i startup, memory app and software update both have errors and stop. then settings have weird characters instead of %s.
I tried flashing back to .7.1 but went into a bootloop.
I flashed back to .8.49 and it works, but still has those problems that initally made me try flashing back to .7.1Any ideas?
Click to expand...
Click to collapse
I did the same, flashed the DE 47.1.A.7.1, it worked perfectly. Then last night I got an OTA update via 'sony update' on my phone. I let it do it's thing and it's been working fine ever since. Perhaps go back to 7..1 and let Sony update it?
itspoots said:
wonder if i'm doing something wrong when trying to preserve user data.. i'm trying to go from CustomUK (my phone is on 47.1.A.2.374) to Custom CE1 (which is on A.8.49). i downloaded the firmware files via XperiFirm, and removed the user data.sin file. I also replaced the OEM.sin file with the US version, then used newflasher. but my phone gets stuck in a boot loop, and i have to resort to wiping user data.
Click to expand...
Click to collapse
Pretty sure it would have worked if you had just removed the userdata.sin. I moved from different firmware & region using this method and it worked fine. I don't know what OEM.sin does, but mixing them up from different regions is probably the issue.
The attached screen shot shows some of the text errors in my update. Anyway to fix this kind of stuff?
Thx
this explains why i couldn't flash back to .7.1.
I'm on Customized UK .2.374 with the US OEM file. It's a US model on Cricket Wireless. So far I haven't been notified of any OTAs, even after checking in settings several times over the last few days, but Xperifirm shows .5.51 as being available for Customized UK. Based on the replies in this thread, it sounds like I'm supposed to get the UK OTA, but it hasn't shown up yet.
Has anyone in the US on the UK firmware with US OEM file actually seen an OTA yet? Ideally I'd like to keep getting OTAs and avoid flashing every update...
(This would be so much less painful if Sony had just enabled the fingerprint scanner in the US...)
Have you tried with the Xperia Companion on a PC?
Didgesteve said:
Pretty sure it would have worked if you had just removed the userdata.sin. I moved from different firmware & region using this method and it worked fine. I don't know what OEM.sin does, but mixing them up from different regions is probably the issue.
Click to expand...
Click to collapse
I have a US model XZ1C and had to copy the US model OEM.sin file when flashing to the CustomUK firmware.
---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------
jrbmed08 said:
I'm on Customized UK .2.374 with the US OEM file. It's a US model on Cricket Wireless. So far I haven't been notified of any OTAs, even after checking in settings several times over the last few days, but Xperifirm shows .5.51 as being available for Customized UK. Based on the replies in this thread, it sounds like I'm supposed to get the UK OTA, but it hasn't shown up yet.
Has anyone in the US on the UK firmware with US OEM file actually seen an OTA yet? Ideally I'd like to keep getting OTAs and avoid flashing every update...
(This would be so much less painful if Sony had just enabled the fingerprint scanner in the US...)
Click to expand...
Click to collapse
I was in the same boat. I was on the CustomUK firmware with US OEM file, and after I saw Xperifirm update to .5.51, i never saw it update via OTA on my phone. Ended up flashing to the Customized CE1 version since that is up to date on .8.49
itspoots said:
I have a US model XZ1C and had to copy the US model OEM.sin file when flashing to the CustomUK firmware.
---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------
I was in the same boat. I was on the CustomUK firmware with US OEM file, and after I saw Xperifirm update to .5.51, i never saw it update via OTA on my phone. Ended up flashing to the Customized CE1 version since that is up to date on .8.49
Click to expand...
Click to collapse
Thanks. Do you think it's because we're not on a UK carrier or because of the hybrid firmware from flashing the US OEM file?
Anyone else on the same setup...please let us know if you're also not getting OTAs.
jrbmed08 said:
Thanks. Do you think it's because we're not on a UK carrier or because of the hybrid firmware from flashing the US OEM file?
Anyone else on the same setup...please let us know if you're also not getting OTAs.
Click to expand...
Click to collapse
The OTA's are checked based on a combination of the parameters found in the OEM partition and the system partition.
Specifically these found in the /oem/system-properties/cust.prop file:
ro.semc.version.cust=1310-4371
ro.semc.version.cust_revision=R8B
And these in the /system/etc/prop.default file:
ro.semc.version.sw=1307-7511
ro.semc.version.sw_revision=47.1.A.2.324
It builds a web query from the parameters like this:
http://fuas.sonymobile.com/fuas/services/updates?cdfId=CUST&cdfVer=CUST_REVISION&channel=cable&clientName=Xperia%20Companion%20Win&clientVersion=1.7.2.0&devId=IMEI&lang=en-US&model=G8441&securityState=HWC_Yoshino_Com_001&swId=SW&swVer=SW_REVISION&tac_mc=NO_IDEA&updateFormat=image
You can see the complete URL for your phone in the Xperia Companion logs.
Just look for a line starting with: http://fuas.sonymobile.com
So although you have an older SW_REVISION, if it's newer than the firmware available for CUST then a firmware update isn't offered.
What this means is that Sony is providing OTA's that are essentially based on your OEM region and the US region only has version 47.1.A.2.324 available.
So if you have newer firmware than that, you aren't offered the update.
This also means that if you are offered an update, it will be the US version of the OTA which may cause problems when it tries to patch binaries from a different region's partition.
I haven't been able to get my hands on any OTA files yet, so I don't know what's in them or probability of an OTA breaking a phone with mixed region firmware bits.
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
sFranKv said:
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
Click to expand...
Click to collapse
Does doing that wipe my device? Or do I get to keep my stuff?
I wanted to add this for anyone who kept tapping the register button but was simply returned to the banner like nothing happened.
If this is happening and you dont get a toast msg saying "thank you for your support of the One UI Beta" and no OTA follows, try deleting the (beta) Samsung + app data, rebooting and try again.
I tried all day before doing this and got the OTA 5 mins after wiping app data.
Nachorl250 said:
Does doing that wipe my device? Or do I get to keep my stuff?
Click to expand...
Click to collapse
Nope, its a regular update so no need to wipe anything
Already try my apps and games (fortnite, arena of valor) and they work perfect!
Ed Murray said:
I wanted to add this for anyone who kept tapping the register button but was simply returned to the banner like nothing happened.
If this is happening and you dont get a toast msg saying "thank you for your support of the One UI Beta" and no OTA follows, try deleting the (beta) Samsung + app data, rebooting and try again.
I tried all day before doing this and got the OTA 5 mins after wiping app data.
Click to expand...
Click to collapse
Tried everything, to be honest I was just sure that the Samsung+ app would check where you are in the world and if your not on the US it will simply not let you join the beta, the method above worked flawlessly for me!, I'm running One UI at the moment with the dark theme and its awesome!
sFranKv said:
So I bought my note 9 three weeks ago, it was ATT carrier branded, since I don't need/like any carrier bloat, I just flashed the unlocked firmware to it, until today its working with no problems at all.
So today I learned that the One UI beta came out, I log on my Samsung+ app I got the banner and hit register but nothing... it will simply send me back to the start, probably because i'm offshore who knows. well I started looking around tried with a VPN, tried spoofing my location, clear cache, clear data ( did this multiple times ) but it will simply not let me join the beta.
So I keep on looking and I find this website https://firmware.science/ it will allow you to download the OTA file and flash it using recovery mode!
Sure I wont get the otas automatically on my phone, but I can simply download then again and flash then as they come out.
I hope this helps anyone like that just wanted to install the latest software!
Note!:
This doesn't mean that your are part of the beta, but means that you will have the beta software on your phone!
Click to expand...
Click to collapse
I have the N960U (T-Mobile) and I am on version ARK1. My version isn't in the list of options? Or will this not work for the 960U from T-Mobile?
BigMosely said:
I have the N960U (T-Mobile) and I am on version ARK1. My version isn't in the list of options? Or will this not work for the 960U from T-Mobile?
Click to expand...
Click to collapse
Keep in mind that this Beta Update its just for the unlocked firmware, if you want to flash the update you need to first flash this firmware: https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/download/N960U1UES1ARJ9/244752/
After that you will be able to flash the Beta Update
sFranKv said:
Keep in mind that this Beta Update its just for the unlocked firmware, if you want to flash the update you need to first flash this firmware: https://www.sammobile.com/firmwares/galaxy-note9/SM-N960U1/XAA/download/N960U1UES1ARJ9/244752/
After that you will be able to flash the Beta Update
Click to expand...
Click to collapse
Can you flash the unlocked firmware without loosing data?
BigMosely said:
Can you flash the unlocked firmware without loosing data?
Click to expand...
Click to collapse
Yes, I did. No data loss.
I flashed the same zrkp from firmware. Science on my us unlocked note 9 with arj9 firmware. It did a full factory reset. I would have done so anyway as I always do with major updates.
Working flawlessly so far.
Edit: 2 exceptions found. Themes are not working and cannot connect to my gear s3. Android wear watch works as expected.
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
papashex said:
I flashed the same zrkp from firmware. Science on my us unlocked note 9 with arj9 firmware. It did a full factory reset. I would have done so anyway as I always do with major updates.
Working flawlessly so far.
Edit: 2 exceptions found. Themes are not working and cannot connect to my gear s3. Android wear watch works as expected.
Click to expand...
Click to collapse
Yea themes are not on beta for some reason, good it worked for you!
GBPackerFanForLife said:
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
Click to expand...
Click to collapse
I would not know, I guess we need to wait until beta 2 update and see, probably won't be getting it and we will need to download the new OTA and flash again on recovery
GBPackerFanForLife said:
Question what happens when you go into settings an click on Software update does it do anything..Just curious..I have the ATT variant an I'm planning on flashing the Unlocked Firmware..
Click to expand...
Click to collapse
Ok. First of all. Green and gold till I'm dead and cold.
Second of all, if you flash the U1 firmware and sign up for the beta, then you'll get OTAs automatically through settings.
If you flash the U1 firmware and can't get into the beta program, you can download the update.zip from firmware.science. You will have the official beta build, but you won't get updates through settings, because you aren't part of the beta program.
When I run Odin soon as I goto add the AP file Odin freezes an says not responding..I'm useing Windows 10 on my laptop..Any ideas??Also I have put the correct files in odin but it fails Everytime.. I do the BL an the AP an the CP an then for the CSC I use the Home CsC is that correct then hit start??I can't get it to work at all..do I put any file in USERDATA slot???
GBPackerFanForLife said:
When I run Odin soon as I goto add the AP file Odin freezes an says not responding..I'm useing Windows 10 on my laptop..Any ideas??Also I have put the correct files in odin but it fails Everytime.. I do the BL an the AP an the CP an then for the CSC I use the Home CsC is that correct then hit start??I can't get it to work at all..do I put any file in USERDATA slot???
Click to expand...
Click to collapse
That is normal. Just wait. It will eventually load the AP file. If you're flashing the U1 firmware, there is no Userdata file, so you don't use that slot.
Make sure you are using the modified version of ODIN 3.13.1 and run it as an administrator. There are links to it on XDA. Or if you go to the main beta thread there's links to it in the thread.
Just put the files in their respective slots. BL in BL, AP in AP, etc...
CSC_OYN performs a factory reset. HOME_CSC does not wipe the phone. I always use CSC_OYN when switching from carrier firmware to U1 firmware or vice versa, but it's up to you.
After everything is all loaded up in ODIN, put your phone in download mode. Power off. Then hold power, Bixby, and volume down button all at the same time until it boots to a blue-green screen. Then press volume up to continue.
Plug your phone into your computer and hit start. Then sit back and wait. This will take a while.
That's all the steps. If you have any issues, I encourage you to use the search bar on the forum. These steps and solutions to any issues you may run into have been posted many times in several threads. The search bar is your friend and should always be the first thing you do before posting questions.
Mr. Orange 645 said:
That is normal. Just wait. It will eventually load the AP file. If you're flashing the U1 firmware, there is no Userdata file, so you don't use that slot.
Make sure you are using the modified version of ODIN 3.13.1 and run it as an administrator. There are links to it on XDA. Or if you go to the main beta thread there's links to it in the thread.
Just put the files in their respective slots. BL in BL, AP in AP, etc...
CSC_OYN performs a factory reset. HOME_CSC does not wipe the phone. I always use CSC_OYN when switching from carrier firmware to U1 firmware or vice versa, but it's up to you.
After everything is all loaded up in ODIN, put your phone in download mode. Power off. Then hold power, Bixby, and volume down button all at the same time until it boots to a blue-green screen. Then press volume up to continue.
Plug your phone into your computer and hit start. Then sit back and wait. This will take a while.
That's all the steps. If you have any issues, I encourage you to use the search bar on the forum. These steps and solutions to any issues you may run into have been posted many times in several threads. The search bar is your friend and should always be the first thing you do before posting questions.
Click to expand...
Click to collapse
I wonder since I'm not useing the modified version of Odin that's why it keeps Failing on me..
GBPackerFanForLife said:
I wonder since I'm not useing the modified version of Odin that's why it keeps Failing on me..
Click to expand...
Click to collapse
Yes. That's why I said use the modified version.
I'm assuming since I installed the Firmware then the Beta One Samsung + app won't open..then if I click on the Samsung Members app it says Beta but everything i click on say I'm not registered for the Beta..is that because I manually install the Beta update file..So basically Everytime a new beta version comes out I'm going to have to manually install it..
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
One thing I have noticed on the new Unlocked version of the Firmware an being on the Beta software is that the Stereo speakers on the phone aren't as loud as they were when I was running the ATT version Firmware..Any ideas..
GBPackerFanForLife said:
I'm assuming since I installed the Firmware then the Beta One Samsung + app won't open..then if I click on the Samsung Members app it says Beta but everything i click on say I'm not registered for the Beta..is that because I manually install the Beta update file..So basically Everytime a new beta version comes out I'm going to have to manually install it..
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
One thing I have noticed on the new Unlocked version of the Firmware an being on the Beta software is that the Stereo speakers on the phone aren't as loud as they were when I was running the ATT version Firmware..Any ideas..
Click to expand...
Click to collapse
Yes, you are not part of the official beta.
As far as speaker loudness I have no idea.
I have been using Note9 Exynos 128GB Singapore version. Last update was on October'19. I'm yet to get Android 10 update. Need to know is there anyone facing same issue? Anyone have any update on getting OTA for Singapore version?
According to Samsung, the note 9 in all Versions will not get Android 10 before February 2020. My Provider here in Europe told me the same, so i made oan update with odin.
But anyway, the update is officially not out yet, according to samsung.
crystalpepe said:
According to Samsung, the note 9 in all Versions will not get Android 10 before February 2020. My Provider here in Europe told me the same, so i made oan update with odin.
But anyway, the update is officially not out yet, according to samsung.
Click to expand...
Click to collapse
If I do update using odin, will I need to do rooting? One I update using Odin, will there be official update coming regularly?
It hasn’t been release yet in Singapore.
Samsung said February. However today is Feb 26 and still nothing. The gang of three (Singtel, Starhub and M3) have to put their rubbish in the rom so they won’t meet the deadline I think. Every year the same story. Singapore gets less frequent update than other markets making Samsung phones a real security hazard. I have to praise Apple for cutting the telcos and going on their own update cycle.
I applied the update on my Note 9 but I am having battery life issues. Have to use power saving mode all the time if not the battery is gone within half a day. I will do a full reset once the official XSP built for Singapore is out.
My wife's s9 has received the update. Me on the other hand, note 9, still nothing. They are Soo freaking slow with updates.
I downloaded and flashed the German rom from sammobile website using odin. Now my note 9 is running One UI 2 and Android 10 with Feb 2020 security patch. Everything seems to be working well so far
Note: when flashing using Odin, select "home csc" to preserve user data, or "csc" for full wipe. Personally I did a full wipe
Using N960F bought from M1, using on Gomo network (previously Starhub)
Can you please teach me how to update my NOTE 9 128gb variant from STARHUB? I'm getting frustrated about this. Everyone in the whole world got the android 10 update, Singapore is always last on the list.
fabienpascal said:
It hasn’t been release yet in Singapore.
Samsung said February. However today is Feb 26 and still nothing. The gang of three (Singtel, Starhub and M3) have to put their rubbish in the rom so they won’t meet the deadline I think. Every year the same story. Singapore gets less frequent update than other markets making Samsung phones a real security hazard. I have to praise Apple for cutting the telcos and going on their own update cycle.
I applied the update on my Note 9 but I am having battery life issues. Have to use power saving mode all the time if not the battery is gone within half a day. I will do a full reset once the official XSP built for Singapore is out.
Click to expand...
Click to collapse
You should be getting it soon. As I got the Android 10 update a couple of months after it was released in Germany.
All the countries using the N960F Variant received the Android 10 update. There is even up to 4 different built with bug fixes and security updates.
Last built released in Singapore: Oct 24...
DzunjaBien said:
Can you please teach me how to update my NOTE 9 128gb variant from STARHUB? I'm getting frustrated about this. Everyone in the whole world got the android 10 update, Singapore is always last on the list.
Click to expand...
Click to collapse
You can follow these steps (works for both telco and retail models, so will work on your Starhub model too):
1. Download the firmware for N960F model from sammobile ( I downloaded both UK BTU and German DBT rom and both worked - currently using the German one, I think it doesn't matter which country the firmware is designed for as long as it isn't tied to a specific carrier).
Note: the rom is quite big, around 5GB so be patient. I left my laptop on overnight while the rom downloaded.
2. Unzip the rom and you should see 5 files inside the folder
3. Use Odin to flash the files (please backup all data before attempting to make any modification to your software - I used Samsung cloud to back up phone settings and manually backed up everything else to micro sd)
a) download latest odin version and unzip it. Run the exe
b) Add the respective files. The BL, AP, CP and CSC files are named accordingly. Make sure to select the correct files for each selection while flashing. To preserve data on your phone, select the home csc file instead of csc. Selecting csc will wipe the entire phone giving you a clean reset.
c) your phone needs to be booted to recovery mode in order to flash the rom
4. Enjoy your Samsung note 9 with Android 10
If unsure, just google for detailed instructions on how to use odin.
Hope it helps!
bomblim said:
You can follow these steps (works for both telco and retail models, so will work on your Starhub model too):
1. Download the firmware for N960F model from sammobile ( I downloaded both UK BTU and German DBT rom and both worked - currently using the German one, I think it doesn't matter which country the firmware is designed for as long as it isn't tied to a specific carrier).
Note: the rom is quite big, around 5GB so be patient. I left my laptop on overnight while the rom downloaded.
2. Unzip the rom and you should see 5 files inside the folder
3. Use Odin to flash the files (please backup all data before attempting to make any modification to your software - I used Samsung cloud to back up phone settings and manually backed up everything else to micro sd)
a) download latest odin version and unzip it. Run the exe
b) Add the respective files. The BL, AP, CP and CSC files are named accordingly. Make sure to select the correct files for each selection while flashing. To preserve data on your phone, select the home csc file instead of csc. Selecting csc will wipe the entire phone giving you a clean reset.
c) your phone needs to be booted to recovery mode in order to flash the rom
4. Enjoy your Samsung note 9 with Android 10
If unsure, just google for detailed instructions on how to use odin.
Hope it helps!
Click to expand...
Click to collapse
You can actually use samfirm or frija(both in xda) to download the firmware within 5mins
bomblim said:
You can follow these steps (works for both telco and retail models, so will work on your Starhub model too):
1. Download the firmware for N960F model from sammobile ( I downloaded both UK BTU and German DBT rom and both worked - currently using the German one, I think it doesn't matter which country the firmware is designed for as long as it isn't tied to a specific carrier).
Note: the rom is quite big, around 5GB so be patient. I left my laptop on overnight while the rom downloaded.
2. Unzip the rom and you should see 5 files inside the folder
3. Use Odin to flash the files (please backup all data before attempting to make any modification to your software - I used Samsung cloud to back up phone settings and manually backed up everything else to micro sd)
a) download latest odin version and unzip it. Run the exe
b) Add the respective files. The BL, AP, CP and CSC files are named accordingly. Make sure to select the correct files for each selection while flashing. To preserve data on your phone, select the home csc file instead of csc. Selecting csc will wipe the entire phone giving you a clean reset.
c) your phone needs to be booted to recovery mode in order to flash the rom
4. Enjoy your Samsung note 9 with Android 10
If unsure, just google for detailed instructions on how to use odin.
Hope it helps!
Click to expand...
Click to collapse
All noted! Thank you very much. Last question. My Note 9 from Starhub is still on plan, and only for starhub carrier. Can I change the firmware even if this one still not finished on payment?
DzunjaBien said:
All noted! Thank you very much. Last question. My Note 9 from Starhub is still on plan, and only for starhub carrier. Can I change the firmware even if this one still not finished on payment?
Click to expand...
Click to collapse
Yup this is no issue. Flashing the official samsung rom via Odin is like manually updating the software and we are not making any "illegal" modification which can trip Knox, so no worry about warranty being voided.
I have attached a screenshot of my current software info. As you can see, my handset was bought from M1 shop. After I flashed a non-Singapore rom, the original carrier info remains intact so I can use the phone without any issue. In your case, after flashing the rom, your carrier info will still remain as Starhub
If you manage to update your phone successfully to Android 10 with no issue, just post it here so that others can update their phones too. Keeping my fingers crossed for you!
Reminder: Please backup everything before updating to be on the safe side
I'm back! I followed your instruction and the instruction from Sammobile. Everything went well! So far no problem after updating to Android 10. At first I was worried that when I upgrade it, my phone will be locked or bricked because I'm still paying it monthly at Starhub. But now I can still use my phone. I made sure to back up first using Samsung Smart Switch. I love the android 10 update. Everything becomes smooth and fast! Thank you very much!
Edit before publishing: I started writing this for all variants other than sprint, but I'll now make a separate thread for variants that have kdzs and those that don't, otherwise this will be a mess.
Firstly, keep in mind that no one is responsible if you end up bricking your device! There is currently no way to recover from a hard brick other than sending your phone in for repair, so make sure you follow every single step carefully if you wish to proceed!
Additionally, flashing an xbl through DD may not pass randomly even if it appears that it has worked, so be aware of the risks. Only at&t users will need to flash the xbls anyway since that is the only variant other than sprint which does not have kdzs available.
Users with the AT&T variant who are stuck on pie: temp root only works on android 10, as such you will unfortunately not be able to bootloader unlock your device. The firehose may leak at some point in a few months, and you will be able to unlock (and update manually) if it does.
The process for unlocking bootloaders on models other than the sprint one (specifically At&t for this guide) is practically identical; however, it uses different xbl_config.img and xbl.img files, which need to be specific for your device from the pie firmware.
The version naming may not be the exact same for other models, but you just have to ensure that you are on the March patch or below. If you are on April, you can find the guide to switch slots and do so in order to revert to March. To STOP UPDATES, fully uninstall or disable the update center packages either with ADB or package disabler pro for LG, which you can easily find online.
So I repeat, you're going to follow the sprint g8 bootloader unlocking guide, but you have to use the xbl and xbl_config for your device rather than the ones provided in the sprint guide. The engineering abl is the same, but I'll include it here anyway so that you don't have to mess around with any of the files provided in the sprint g8 guide.
Now, steps that are to be ignored and steps that may differ slightly:
Keep in mind that I'm only mentioning what you should be aware of and what may be different, but you still have to follow the guide written by BrandonB1218 in general.
1a: Of course, you still need a vulnerable firmware, and sadly AT&T does not provide kdzs, so you cannot bootloader unlock if you are on the May patch.
You can Ignore this: I found that another method that most likely stops updates is following this guide on youtube. It's supposed to bypass frp lock, but it also gets by all the LG agreements you have to accept, so it will ask you to agree to these if you ever open up the software update option in settings and will probably not update if you don't.
2: Some people had issues with different versions of the mroot script, so try all of them before you come asking for help please. I also suggest that you just temp root without running the temp root magisk setup as you may end up bricking if you accidentally flash a module or make magisk flash a patched boot img (DO NOT FLASH ANYTHING OTHER THAN WHAT'S INCLUDED IN THE GUIDE).
I suggest running the backup script and the commands to make sure you're completely safe, but make sure you keep them separate because a lot of the partitions included in the commands that @BrandonB1218 mentioned are device specific and include your IMEI. The backup script should only backup the partitions that aren't device specific such as system, and this is probably the one you'll need if at all because you shouldn't be touching other partitions. STILL DO BOTH THOUGH
3a: Yes, you have to run the command to find out which slot you're on, but you will not flash anything from the pie or 20d sprint backup that's listed there, or else you will likely brick.
3b and 3c: This should all be the same: If your active slot is A, follow 3b, and if your active slot is B, follow 3c. The commands should also be the same, just with different files.
If your active slot is A, but the files included for your device are also named xbl_a.img, for example, you can just rename them to fit with the command.
Otherwise, you can just change this, for example,
dd if=/storage/emulated/0/Download/xbl_b.img of=/dev/block/bootdevice/by-name/xbl_b
to this:
dd if=/storage/emulated/0/Download/xbl_a.img of=/dev/block/bootdevice/by-name/xbl_b
You also need to flash the engineering laf, so either rename the file or change the command so it works. The link is embedded
Overall, its just important that you take the right file in the first part of the command and flash it to the correct partition of the correct slot in the second part.
If I remember correctly, the method to boot into fastboot is hold vol- and power until the screen goes black (while the phone is plugged into the computer) and then to let go of power as soon as that happens.
4a and 4b: You do not want to do either of these as the boot img and other partitions vary per variant. I unfortunately do not have the magisk patched At&t boot img, but you can patch it yourself from the backup you made and flash it. It might be good to do this beforehand, but you could also just temp root again and dd flash it.
Alternatively, you can flash the metaphysics 1.7 kernel with twrp and magisk included, but you still have to follow the rest of the twrp installation in the sprint g8 bl unlocking guide. TWRP is the same for all US variants.
Congrats! You should now be bootloader unlocked and ready to go at this point. If you ever find yourself unable to boot on the slot which DOES NOT have the engineering abl, you can always switch to the slot with the engineering abl, go to fastboot, and fastboot flash your backed up partitions.
Credits:
Obviously to BrandonB1218, for writing the sprint g8 bootloader unlocking guide
vl48 for basically answering all my questions and providing the needed files
j4nn for writing the temp root
Mr. Zhu for twrp
KamioRinn for metaphysics
Anyone else who contributed in telegram to get this to work!
Amazing! Can't wait to do this. I'll report back when I get this phone unlocked.
Thanks for taking the time.
Files can't be downloaded dead link
blumix said:
Files can't be downloaded dead link
Click to expand...
Click to collapse
No issues here
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Pietrobell86 said:
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Click to expand...
Click to collapse
No sorry. Not sure exactly what your problem is, but it might be solvable with root
Shtiff1 said:
No issues here
Click to expand...
Click to collapse
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
Click to expand...
Click to collapse
I am talking about the AT&T_G8.zip
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
@antintin zip not downloading, FYI
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
I can't find it, sorry. I'm on Verizon
Hey, thanks for the guide. I'm rather worried about trying this as LG's newer models are so darn easy to brick. AT&T variant has no LG Bridge support which is incredibly stupid. At least we have kind people like you helping us free our phones
My LG G8 is a secondary phone right now, and as such, I'm very interested in trying this out. Unfortunately, the download link for AT&T_G8.zip give me a 404.
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Espen115 said:
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Click to expand...
Click to collapse
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
antintin said:
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
Click to expand...
Click to collapse
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
lightningdude said:
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
Click to expand...
Click to collapse
Why would it have to be removed?... I'll just upload it when I get home and have time
antintin said:
Why would it have to be removed?... I'll just upload it when I get home and have time
Click to expand...
Click to collapse
Just out of consideration for space in your account, in case you were low on free space. I also didn't notice that it was a < 3MB file.
so is someone going to reupload the file or what? cant even download it from the op attachment.
does this even work with 20m or are those of us out of luck?
File Broken
Anyone has the copy of AT&t_G8.zip? Its 404 now.
MaemoToWindows said:
Anyone has the copy of AT&t_G8.zip? Its 404 now.
Click to expand...
Click to collapse
Always has been.
I have it but it won't let me add it
Can u email it to me? [email protected]
I didnt spot the message about losing GearVR and now having upgraded my GearVR is not functional. It says I cannot go back but... this is XDA so, can i ??
Also not sure if I can re-install the Oculus GearVR app (can't see it on PlayStore) so does anyone know which APKs I need to install as well?
on my s10+ i get se same Issue. According official samsung information, it seems that gear VR do not run on android 12. I did not find any solution for now.
Methanoid said:
I didnt spot the message about losing GearVR and now having upgraded my GearVR is not functional. It says I cannot go back but... this is XDA so, can i ??
Also not sure if I can re-install the Oculus GearVR app (can't see it on PlayStore) so does anyone know which APKs I need to install as well?
Click to expand...
Click to collapse
Sorry don't know anything about gearVR, but no, if the bootloader version has increased, which I believe it does when going to A12, then you can't downgrade.
I'm pretty sure there is no xda 'work'a'round' for that, haven't seen one and everything I've read indicates not possible. Do some searching I guess to be positive, but one prereq to bootloader unlock is being on a specific BL version, and even their directions indicate if you're above that version, nothing you can do.
cheers
Thanks for replying... I guess I am boned
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
tin2404 said:
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
Click to expand...
Click to collapse
You have the S10+, from what I see, the most recent BL version is 6 on both a11 and the new a12, so that fits the requirements.
It looks like for at least some of the S10 firmware upgrades, the BL version changes, thus u cannot go back if that's the case. Not all A12 updates are out for the S10, so we don't know yet if the BL version will change for them.
Yes.I think they left compatible downgradable bootloader for those users who didn't saw info about GearVR support as a last chance to revert.
I presume,as we learned from previous updates, in future releases of A12 downgrade will not be possible because of their privacy paranoia.
AsItLies said:
You have the S10+, from what I see, the most recent BL version is 6 on both a11 and the new a12, so that fits the requirements.
It looks like for at least some of the S10 firmware upgrades, the BL version changes, thus u cannot go back if that's the case. Not all A12 updates are out for the S10, so we don't know yet if the BL version will change for them.
Click to expand...
Click to collapse
I have the S10 and from what I can tell the BL version is also 6 on my A12 update.
Does this mean I can just use odin to load a "compatible downgradable bootloader" and I will be able to downgrade back to 11? Does my phone have to be unlocked to do this?
Assuming I back up all my data, will I be able to go back to 11 without compromising my xfinity number, security, ect.? I am simply looking for the best way to just revert back to 11 and reload everything I was using before.
Johnm77 said:
I have the S10 and from what I can tell the BL version is also 6 on my A12 update.
Does this mean I can just use odin to load a "compatible downgradable bootloader" and I will be able to downgrade back to 11? Does my phone have to be unlocked to do this?
Assuming I back up all my data, will I be able to go back to 11 without compromising my xfinity number, security, ect.? I am simply looking for the best way to just revert back to 11 and reload everything I was using before.
Click to expand...
Click to collapse
Well as far as I know you can, but that's from what I've read, not from doing the exact scenario you speak of. Sometimes we just have to try it to know for sure. I have read for sure the if the BL isn't the same version, you can't go back. And no, the phone does not have to be unlocked.
good luck
AsItLies said:
Well as far as I know you can, but that's from what I've read, not from doing the exact scenario you speak of. Sometimes we just have to try it to know for sure. I have read for sure the if the BL isn't the same version, you can't go back. And no, the phone does not have to be unlocked.
good luck
Click to expand...
Click to collapse
Thank you for your help!
I figured the most recent update of A11 from
Galaxy Firmware - Samsung Galaxy S10 SM-G973U (CHA) | G973USQU6GUJ3
This Firmware flash for Samsung Galaxy S10 with the Phone Model Number SM-G973U for region 🇺🇸 United States with CSC code CHA and R(Android 11) OS.
galaxyfirmware.com
is what I would need.
The Baseband I have from A12 currently is G973USQU6HULD, so from what was said here the BL ver. 6 means I should be able to do it.
Model #, Country, region/carrier from the above link all match my specs. So if I'm to understand correctly all I should have to do is backup and then use the firmware with odin to flash to my device using tin2404's procedure from above? (Flash all A11 stock firmware package and choose CSC instead of Home_csc !)
tin2404 said:
I successfuly reverted to Android 11 G975XXSEFUJ2 from Android 12 since I saw issue about GearVR...IF you are on first release of A12 you can downgrade.
Flash all A11 stock firmware package and choose CSC instead Home_csc !
Click to expand...
Click to collapse
Doesn't choosing CSC clear all the app data and basically factory reset it? Wouldn't I want to use Home_CSC, or does it not then work properly?
Johnm77 said:
Doesn't choosing CSC clear all the app data and basically factory reset it? Wouldn't I want to use Home_CSC, or does it not then work properly?
Click to expand...
Click to collapse
Update:
Successfully used odin to revert to os11, had to factory reset after odin completed, then I just reloaded my backup.
After more research I decided to block all future updates using ADB and this method:
No more headaches with my software!
Actually, it is neccessery to choose clear CSC to erase leftovers..Choosing Home_CSC brings various of errors possible.
Workaround is doing TWRP backup on SD Card then after clear flashing restoring ONLY data partition.