Database Develop

[Q] Change SKU from CN to US or WW, how?

Hi kids, as per title, my issue is quite simple: I (unfortunately) live in China, and my pad came with CN firmware. I realized that it also came with no gapps installed, and that's a bummer. I'm about to root it, so I'll be able to install gapps as system apps manually one by one, but that's a huge waste of time and it's not an elegant solution, too.
This said, how can I -SAFELY- change my SKU version from CN to WW or US? After rooting, can I do the manual update procedure and put the unzipped FW from Asus in the microsd card etc etc? Or is there some other way?
P.S. I'm not planning to install any recovery at the moment: I actually received my pad last week, and I hard-bricked it in 30 minutes following the recovery install guide in the dedicated thread (too lazy to link it now, but it's just out there in the other forum - I didn't follow the now locked one, I followed the other one, where so many people seemed so happy with the result -__-). Luckily either the seller of my tab or the asus service desk he sent the tablet too were too dumb to realize I dabbled with it... and they restored the system for free although you could see UNLOCKED on the screen at boot anyhow that's why I'm NOT installing recovery now, not until there's a tested "official" version I can just slap in with ROM Manager. So, do I need a recovery to change my CN to WW or US? Or it can be done some other way?
Cheers!

UoMoTaLpA said:
Hi kids, as per title, my issue is quite simple: I (unfortunately) live in China, and my pad came with CN firmware. I realized that it also came with no gapps installed, and that's a bummer. I'm about to root it, so I'll be able to install gapps as system apps manually one by one, but that's a huge waste of time and it's not an elegant solution, too.
This said, how can I -SAFELY- change my SKU version from CN to WW or US? After rooting, can I do the manual update procedure and put the unzipped FW from Asus in the microsd card etc etc? Or is there some other way?
P.S. I'm not planning to install any recovery at the moment: I actually received my pad last week, and I hard-bricked it in 30 minutes following the recovery install guide in the dedicated thread (too lazy to link it now, but it's just out there in the other forum - I didn't follow the now locked one, I followed the other one, where so many people seemed so happy with the result -__-). Luckily either the seller of my tab or the asus service desk he sent the tablet too were too dumb to realize I dabbled with it... and they restored the system for free although you could see UNLOCKED on the screen at boot anyhow that's why I'm NOT installing recovery now, not until there's a tested "official" version I can just slap in with ROM Manager. So, do I need a recovery to change my CN to WW or US? Or it can be done some other way?
Cheers!
Click to expand...
Click to collapse
Not sure if you can, but if you could i think the only way would be to an offical Asus ROM with a different SKU manually via fastboot. But since you already had problems installing a custom recovery this might not be for you.
I think remembering when i owned the TF300 and Jelly Bean (or was TF101 with ICS?) came out that the only way at first was to flash the US-version of the ROM (since WW wasn't out yet). Which is what i did and i hadn't any problem. A week or so later when the WW version came out I went back to WW.
But i'm really not certain anymore. Maybe someone else knows if it's possible or not.

Not possible
Sent from my SGH-T889 using XDA Premium 4 mobile app

actually it is if rooted and have cwm or something.
it will let you flash any firmware. though there are risks of bricking.
I did the same on my old acer was an AU now it`s ww because ww had less bloat ware and the 4.1 had been out for 2 months and au didn`t get it and i was impatient

malos1984 said:
actually it is if rooted and have cwm or something.
it will let you flash any firmware. though there are risks of bricking.
I did the same on my old acer was an AU now it`s ww because ww had less bloat ware and the 4.1 had been out for 2 months and au didn`t get it and i was impatient
Click to expand...
Click to collapse
flashing official firmware for a different SKU will cause issues

AngryDinosaur said:
flashing official firmware for a different SKU will cause issues
Click to expand...
Click to collapse
only if the hardware is different i.e. dock jpn has diff buttons. some brands have diff wifi hardware depending on region etc.
however in the case of au and ww acer the tab is the same besides pre-loaded bloatware.
as is the case for most of the versions of tf701. cn jp and TW would probably not be wise to go to ww or us due to the dock but i can`t be certain.
It might just mean the language ime buttons won`t function but it might also mean the dock won`t function at all.

malos1984 said:
only if the hardware is different i.e. dock jpn has diff buttons. some brands have diff wifi hardware depending on region etc.
however in the case of au and ww acer the tab is the same besides pre-loaded bloatware.
as is the case for most of the versions of tf701. cn jp and TW would probably not be wise to go to ww or us due to the dock but i can`t be certain.
It might just mean the language ime buttons won`t function but it might also mean the dock won`t function at all.
Click to expand...
Click to collapse
I'm pretty sure i did it, but i didn't have a dock, so it was the tablet only. Didn't run it that long either, like 3-4 days, so maybe it was too short to see what didn't work anymore...
I was trying to find back the post here on XDA, but i think it has been rewritten when the WW-version came out.

What's beneficial to flash a different sku Rom?
Sent from my SGH-T889 using XDA Premium 4 mobile app

Benefit is that on CN SKU I got no gapps and in return I got a boatload of chinese crapware. No google play. No maps. No gmail.
I'm actually struggling with the vendor to take it back, since as it is now, it's actually nothing more than a paperweight:
-Bootloader can't be unlocked, since the unlock software calls home to Asus, and my SN is not recognized.
-Since bootloader is locked, I can't root.
-Since I can't root, I can't install Gapps, I can't do basically anything.
Would a working nvflash let me fix all this? Or with a locked bootloader I'm definitely screwed? Would it be worth the wait?

if ur sn is not recognised then its a knock off or stolen from asus factory imo
i would force a refund

malos1984 said:
if ur sn is not recognised then its a knock off or stolen from asus factory imo
i would force a refund
Click to expand...
Click to collapse
...and in the end that's what I did. I loved the concept, but the actual thing was crippled. I leveraged the double-SN-thingy and the hardware connector issue, and after some discussion I got my refund. Bought a note 10.1 2014, not what I wanted, due to lack of keyboard and battery life, but it seems it's the second best tablet around (in my opinion).
I would have been happier with a working Asus, but problems were too many. At least the note does what it promises, even though it promises "less", and I never even used the S-pen once since I unboxed it.

Just picked up this device, any tips?

So I've been out of the Android Phone loop for a while and was just wondering if there were any general tips or things to know about the Z3C? Any essential apps or features?
I've not updated to Marshmallow yet (running 5.1.1) and I don't really feel the need to, If I'm not mistaken it makes the root process a bit more fiddly, though the non-removable notification is somewhat annoying. Can it be turned off?
Quick question on root too, which I assume can only be achieved through unlocking the bootloader. Will it void my warranty with Sony? Given the issues with cracked screens and phones not really being waterproof, I'm not sure if it's actually worth doing.
I've got the Phone through Vodafone, is there anyway to remove the SIM lock myself?
I've been through the Stickies and whilst they contain useful information that'll surely come in handy later, the FAQ section is pretty limited, so I figured I'd ask here
Thanks in advance

UndisputedGuy said:
So I've been out of the Android Phone loop for a while and was just wondering if there were any general tips or things to know about the Z3C? Any essential apps or features?
I've not updated to Marshmallow yet (running 5.1.1) and I don't really feel the need to, If I'm not mistaken it makes the root process a bit more fiddly, though the non-removable notification is somewhat annoying. Can it be turned off?
Quick question on root too, which I assume can only be achieved through unlocking the bootloader. Will it void my warranty with Sony? Given the issues with cracked screens and phones not really being waterproof, I'm not sure if it's actually worth doing.
I've got the Phone through Vodafone, is there anyway to remove the SIM lock myself?
I've been through the Stickies and whilst they contain useful information that'll surely come in handy later, the FAQ section is pretty limited, so I figured I'd ask here
Thanks in advance
Click to expand...
Click to collapse
You don't need to unlock the bootloader to be able to root your phone. A good place to start is the thread on how to back up your TA partition and rooting (don't be tempted by Kingroot)
Unless you want a custom CM rom I wouldn't bother trying to unlock your bootloader, it disables features on the phone, starting with breaking the camera.
This thread about going from a rooted phone back to stock is interesting. I'd say you don't need to root your phone, but it gets a lot more interesting when you do.
The top app for if you get root is Titanium Backup, it lets you control individual apps, 'freezing' them so they stop working, but not actually uninstalling them. Great for getting rid of all the bloatware that comes with phone providers (like Sim Lock), or even manufacturers. It also lets you back up an app and all the associated data that goes with it, so if you wipe you phone to change the rom, you can put all the apps back and the state they were in at the touch of a button. There's lots of other cool root apps, but TA is my favourite.
As long as you stick to stock then you can't go wrong, don't be afraid to play, there's plenty of people on the thread here to give you a hand.
SLIM 5 is a good stock 5.1.1 rom with lots of cool tweeks and doesn't mean you have to unlock your bootloader.
Edit: Rooting your phone doesn't void your warranty. But if you face any problems with your phone that means it's going back to the service centre, just put a stock build back on (no root) and do a factory reset. That way they cannot complain about the software config. They will do a factory reset anyway, before they send it back, along with an update to the latest rom. So be prepared and take everything off your phone beforehand.

Man, that's pretty much all the information I need in one post. Thanks a bunch man, I'll read through the links in some more detail.
I did see that Rooting guide earlier, but given how it mentioned using Flashtool and DRM Keys, I thought it'd surely void my warranty so didn't have a proper look.
SLIM also seems like a good shout, though I'm assuming I'd lose access to Sony's OTA updates if I were to flash it and there doesn't seem to be a Marshmallow version yet. Actually, that said, would I even have access to OTA updates if I stay stock but rooted?
Thanks again

UndisputedGuy said:
Man, that's pretty much all the information I need in one post. Thanks a bunch man, I'll read through the links in some more detail.
I did see that Rooting guide earlier, but given how it mentioned using Flashtool and DRM Keys, I thought it'd surely void my warranty so didn't have a proper look.
SLIM also seems like a good shout, though I'm assuming I'd lose access to Sony's OTA updates if I were to flash it and there doesn't seem to be a Marshmallow version yet. Actually, that said, would I even have access to OTA updates if I stay stock but rooted?
Thanks again
Click to expand...
Click to collapse
Marshmallow has only been out a few weeks, so it's still full of bugs and problems at the moment. I would stick to 5.1.1. for at least another month, or until 6.1 reaches the Z3c.
No, if you install a custom rom then you wont get Sony OTA updates, but most rom developers base their builds on the latest firmware releases anyway, usually adopting a new release within one or two weeks.
Slim 5 is possibly the best stock Lollipop build there is and there will be no more updates for Lollopop now. There is a Slim MM build, but even though Wajk has been working his magic, it still has several bugs that need to be ironed out. If you are going down the MM route, don't be tempted by Concept or Beta, that need you to unlock your bootloader to root. Stick with a pre-rooted stock or a customised stock with root built in.

Appreciate the assistance, going to go ahead and root now and then perhaps try out SLIM 5. Some of the MEGA links seemed to be down so I just grabbed a Global FTF, couldn't seem to find an unbranded UK one.
I shouldn't have updated immediately once I got the phone

UndisputedGuy said:
Appreciate the assistance, going to go ahead and root now and then perhaps try out SLIM 5. Some of the MEGA links seemed to be down so I just grabbed a Global FTF, couldn't seem to find an unbranded UK one.
I shouldn't have updated immediately once I got the phone
Click to expand...
Click to collapse
For the purposes of downgrading so you can root, it really doesn't matter which build you choose.

Didgesteve said:
For the purposes of downgrading so you can root, it really doesn't matter which build you choose.
Click to expand...
Click to collapse
Just a quick question, at Step 26 could I just use SLIM 5? Seems much more convenient if that's the case.
Oh, and using OTA updates is going to lose me my root now, right?

UndisputedGuy said:
Just a quick question, at Step 26 could I just use SLIM 5? Seems much more convenient if that's the case.
Oh, and using OTA updates is going to lose me my root now, right?
Click to expand...
Click to collapse
Yes, once you have recovery you can download Slim onto your phone and flash that. Don't forget to update SuperSU from the playstore.
No, you wont get any OTA updates with a custom stock, but Slim is up to date with the most recent Lollipop build.
Sony PC Companion will not update your phone either once you have a custom rom on. If you flash stock and then connect it, it will push MM onto it. But you will loose root and there's no easy way to get it working.
Stick with 5.1.1. for another month, wait for 6.1 to come out, and then possibly a couple of weeks after that Wajik will have made an incredible MM rom to flash, that will be as up to date as they come, then just flash that in exactly the same way.
Edit: Once you start to follow a developers thread, they announce updates to roms almost as quick as the Sony release, so don't worry that it will get out of date, just make sure to subscribe to the thread where your rom comes from. Slim 5 for example releases an OTA update, to move from 4.9 to 5, it's a lot smaller than the entire rom and only has updates, but flashes the same way.

Can only thank you again, successfully rooted and got recovery. Not sure how much I'm really fond of SLIM, just had a very brief mess around but something felt a bit off about the Launcher and the icons even after messing with the settings. It was only very brief though, perhaps there's more useful stuff there.
Might go simply stock/rooted but given there isn't a simple .zip for it it's a bit long winded
Thanks for all your help here, this is pretty much the ideal state I wanted my phone to be in upon receiving it, had no idea unlocking the bootloader wouldn't be necessary. Guys like you help make this site in my opinion, I half just expected a couple of snide answers telling me to just read the forum

Think I will be moving back to stock, just a question on the front though
Am I going to have to build my own pre rooted image (steps 27-32) each time there's an OTA update and I want rooted stock?
Sorry, hopefully that's the last thing from me
Sent from my D5803 using XDA-Developers mobile app

UndisputedGuy said:
Think I will be moving back to stock, just a question on the front though
Am I going to have to build my own pre rooted image (steps 27-32) each time there's an OTA update and I want rooted stock?
Sorry, hopefully that's the last thing from me
Sent from my D5803 using XDA-Developers mobile app
Click to expand...
Click to collapse
There are several 'stock' options, that are flashable zips
Pre-Rooted Firmwares-Recovery-SuperSU, although you need to click on 'older files'
Or another stock thread here
But by now you should be able to start finding these threads on your own

Yeah, I've time to have a proper look through now so will do that. I saw the thread earlier, but didn't seem to notice a pre rooted .zip for the latest 5.1.1 firmware in the OP. There was one in the comments though, thanks once again

Question Question regarding root and updates?

Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.

paul_cherma said:
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
Click to expand...
Click to collapse
1- Probably not usually the root or recovery will block OTA updates from installing, even if they download.
2- If you lose root, you can USUALLY re-root assuming the same root method wasnt patched. If it was patched, a new root method (though probably still through magisk) will be needed. If this is the case, its up to the dev to find that method, you might be without root for a while.
3-if you debloat, and receive an OTA, your will probably need to de-bloat again, thought I havent personally had experience with this.
Why are you rooting? Just to de-bloat? If so, root isn't really necessary...

As someone who's been in the rooting stage for many years, i can answer your questions.
1. You can not update your phone through OTA updates after rooting the device, as the device was modified in an unauthorized way. And since you own a galaxy phone, the e-fuse within the motherboard will blow and knox will be permanently blown. You can no longer use samsung pay, google pay, and any other app that uses the safetynet api, even after you unroot the device.
2. You will lose root every time you update. You will need ODIN on your PC in order to properly update your firmware and to re-root your device by following the procedure again that you used to root your device, unless samsung patched the method you used to root your device. You can always check what bootloader version you're on within the firmware. For example, on the galaxy S8, the firmware version is N950U1UES5CRG9. The 5th to last number of the firmware will tell you. In this case, N950U1UES5CRG9 is the 5th bootloader version. Keep this in mind once samsung starts to update your phone often.
3. You will have to debloat again from scratch. In order to fully update your device through ODIN, you need to download the full firmware file containing an AP (Firmware), BL (Bootloader) , CP (Modem), and CSC (Carrier File) and manually flash them.
Do keep in mind, it is possible to soft brick or even hard brick your device, so back up your data frequently if you decide to tinker with your device.

Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.

paul_cherma said:
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
Click to expand...
Click to collapse
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.

HighOnLinux said:
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
Click to expand...
Click to collapse
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?

Twodordan said:
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Click to expand...
Click to collapse
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.

HighOnLinux said:
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
Click to expand...
Click to collapse
I mean xprivacy on xposed was the must have killer feature for any android device to turn your device into anything other than a privacy nightmare. If we can't do that any more we are f'd.
[EDIT] Looks like the new version of xprivacy, xprivacyLua is still supported for android 11, with magisk and EdXposed or LSPosed:
[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
XPrivacyLua Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy). Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data...
forum.xda-developers.com
XPrivacyLua/README.md at master · M66B/XPrivacyLua
Really simple to use privacy manager for Android 6.0 Marshmallow and later - XPrivacyLua/README.md at master · M66B/XPrivacyLua
github.com

Samsung S10 firmware issue

Good day.
I use the Samsung S10 G973U variant. I've been unable to flash the U1 firmware into it using odin. It always fails.
Attached is my current software info
Also, I never get OTA updates. I don't live in the US.

McWelling said:
Good day.
I use the Samsung S10 G973U variant. I've been unable to flash the U1 firmware into it using odin. It always fails.
Attached is my current software info
Also, I never get OTA updates. I don't live in the US.
Click to expand...
Click to collapse
Be sure to look at this thread, it's all about the S10 and xflashing.
But, having done this just today, I can tell you a few things; 1) Your device appears to originally be a vzw version. That means it's a G973U, and because that variant is the 'carrier' one, there will never be updates if you have the U1 firmware (xaa) on it.
Mine is much like yours, it had xaa/xaa/tmb, so no updates either. I used the patched odin (from above thread) and selected Home_csc and updated it, kept data, updated to latest xaa firmware. Security patch of just last month, pretty cool.
cheers

AsItLies said:
Be sure to look at this thread, it's all about the S10 and xflashing.
But, having done this just today, I can tell you a few things; 1) Your device appears to originally be a vzw version. That means it's a G973U, and because that variant is the 'carrier' one, there will never be updates if you have the U1 firmware (xaa) on it.
Mine is much like yours, it had xaa/xaa/tmb, so no updates either. I used the patched odin (from above thread) and selected Home_csc and updated it, kept data, updated to latest xaa firmware. Security patch of just last month, pretty cool.
cheers
Click to expand...
Click to collapse
Thanks a lot. So would you recommend I flash a Verizon U1 firmware?
I currently use a USC G973U firmware and there are no bloatwares tho.

McWelling said:
Thanks a lot. So would you recommend I flash a Verizon U1 firmware?
I currently use a USC G973U firmware and there are no bloatwares tho.
Click to expand...
Click to collapse
So no, as there is no VZW U1 firmware. The U1 device only came with xaa, it's the us open unlocked. Canada has canadian open xac but it's a U device. That would be the only 'open' you could get and get updates, on a U device.
if yer finding the USC works for you, why change? You can flash the xaa, but you'd never get updates, have to do it manually.

All the problems I have had on my S10 started when I upgraded to Android 11, and I'm currently on 12, problems have persisted, some even worsened; issues like wifi and Bluetooth not working and "camera failed" error everytime I open the camera app.
I want to downgrade it back to Android 10, hoping those issues get fixed. The bootloader is 6, and Android 10's last bootloader is 4.
Is it possible to downgrade android 12 to 10?
Help please?

Depends on WHICH S10 you have. Snapdragon bootloaders cannot be downgraded. Exynos I believe can.
I have two Snapdragon S10+ phones with A11 and they work great. I've heard of issues with A12, which is why I have avoided it.

Thank you. I have the snapdragon S10.
I guess od have to take my loss. I'm thinking of getting the S21 and am torn between going for a SD variant and not getting OTA updates or getting the Exynos, which is known to be less reliable but get updates (Exynos is what's available in my region).
What would you recommend?

Recommendation is depending on where you are. In the US, Snapdragon is a good way to go for sure. I don't think it's as good in other countries, but I haven't really looked into that. Plus, if you ever need support in the USA, the Snapdragon would be easier as people won't be confused by the Exynos.
You may not get OTA updates, but you can always apply updates yourself with ODIN and downloads. They can also be applied as an "upgrade" in this manner, so you're not really losing anything as long as you keep up on it yourself, of course.
Honestly, I have stuck to A11 and disabled OTA updates because of the A12 concerns. I imagine I may be overthinking that, but as long as the phone works, what do I care?
What's the "SD" version you're speaking of?

schwinn8 said:
Recommendation is depending on where you are. In the US, Snapdragon is a good way to go for sure. I don't think it's as good in other countries, but I haven't really looked into that. Plus, if you ever need support in the USA, the Snapdragon would be easier as people won't be confused by the Exynos.
You may not get OTA updates, but you can always apply updates yourself with ODIN and downloads. They can also be applied as an "upgrade" in this manner, so you're not really losing anything as long as you keep up on it yourself, of course.
Honestly, I have stuck to A11 and disabled OTA updates because of the A12 concerns. I imagine I may be overthinking that, but as long as the phone works, what do I care?
What's the "SD" version you're speaking
Click to expand...
Click to collapse
schwinn8 said:
Recommendation is depending on where you are. In the US, Snapdragon is a good way to go for sure. I don't think it's as good in other countries, but I haven't really looked into that. Plus, if you ever need support in the USA, the Snapdragon would be easier as people won't be confused by the Exynos.
You may not get OTA updates, but you can always apply updates yourself with ODIN and downloads. They can also be applied as an "upgrade" in this manner, so you're not really losing anything as long as you keep up on it yourself, of course.
Honestly, I have stuck to A11 and disabled OTA updates because of the A12 concerns. I imagine I may be overthinking that, but as long as the phone works, what do I care?
What's the "SD" version you're speaking of?
Click to expand...
Click to collapse
Thank you.
SD is Snapdragon. Well, I guess it should be fine using Odin.
I was skeptical about using Odin before as I started having issues with my S10 as I updated from Android 10 to 11 with Odin, but I guess the problem is the software update and not the method of flashing it in.

Ahh, ok... yeah, SD = Snapdragon. I guess I was having a slow day yesterday, haha.
Odin flashes shouldn't be any worse than other methods - in fact, it's what you would do if you're having problems, so it may be better than OTA flashes, which are upgrade only so they can make mistakes...
Generally speaking a "clean" flash is always best on most devices, and you can only get that with Odin, so I think you'd be better off with a clean flash to any version if you've only dealt with upgrade-flashes to-date.
Again, I don't think the ROM is necessarily the problem here. I'm thinking you have a setting or app that's causing your issues. I would suggest clean flashing and then not restoring all your google backed-up stuff, so that you can start clean and add/adjust things manually. I might suggest just starting with the basics at first, and seeing if that eliminates the problem. And then adding things back in carefully (you may even record what you've added in a document or something) so you can see when the problem starts happening.
And, IMO, I recommend NOT installing ANY "power saving" app at all. You shouldn't need it, but if you do install it, then only install one, and record when you did that, so you can see what really happens after it's installed, and whether it's actually saving any power.

Downgrade from 13 to 12?

Is it possible to downgrade from 13 to 12? I think the upgrade messed up my camera. Or maybe a way to reflash the camera firmware?

If the bootloader wasn't updated you can roll it back.

How can I find out if it was updated? I have a US unlocked phone. Its updated from 11 to 12 and now to 13.

See this thread, different models but the same information applies.

blackhawk said:
See this thread, different models but the same information applies.
Click to expand...
Click to collapse
This is the build I'm on now:

RedCrane3 said:
This is the build I'm on now:
Click to expand...
Click to collapse
Hello good morning
Of course, it can be downgraded, as long as the binary number is the same... example in the image.

The bootloader version is 9 so for you to roll back that build number's 5th digit from the end needs to be the same or higher.
With stock Snapdragon's locked bootloader it's easy to get locked into an OTA upgrade you don't want if it updates the bootloader too. I have two N10+'s, one running on 9, the other 10 (can't be rolled back to 9). That's what they were loaded when bought new. They will likely remain on those versions for their service lives as they are running well. I prefer Pie though.
I could be running Android 11 or 12 but I blew them off mostly because of the scoped storage bs.
The first thing I disable is OTA updates, once bitten twice shy. Had a S4+ that got screwed up by a OTA update that couldn't be rolled back... it sucks.

Thank you guys for helping me with all of this information. I guess I have a decision to make.
I can try to rollback to Android 12 in the hopes that will fix my camera issue, or I can sit tight and hope that a future update will resolve it.
Either way, I'm beginning to regret allowing OTA updates.
I really love the hardware of this phone, especially the screen, but its not important to me to have the latest Android (security updates are important though).
I originnaly submitted the problem to Samsung through their members app and the tech who looked at it said he *thought* it was a hardware issue, but come on, what are the chances that the one camera stops working right after the update to 13 and OneUI 5? I take very good care of my phone and never drop it (certainly didn't recently, after the update), there's not a scratch on it.
I suppose its possible, but it would be an incredible coincidence...
The tech suggested I visit a service center (which for me would be a Best Buy, yikes) or call their support 800 number, but what are they going to be able to do that the tech couldn't?
I just don't know if I can trust their initial assessment - no one knows everything, and plenty of people give up on a problem and pass it off the first trouble they run into. Maybe the tech just wasn't interested in digging deeper? A quote from their answer:
"Chi request is getting timed out. Read wide camera sensor seems to be not responding to requests [...]"
I guess my question is: can a downgrade to 12 even fix the issue?
Should I wait for another update?
Or should i just heave Samsung over the side and try to install a custom ROM?
Thanks again for all your help.

You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.

blackhawk said:
You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.
Click to expand...
Click to collapse
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.

RedCrane3 said:
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.
Click to expand...
Click to collapse
That refers to the carrier not bootloader I think. Not sure about your specific model's bootloader.