As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
If the bottled version is higher on Android 12, it probably is, then you can't downgrade. In the build number, I believe it's the 5th number from the right might want to check that it with Google. If the new firmware has a higher number there NO going back...
robotov said:
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
Click to expand...
Click to collapse
Yes, it's possible, and I've done it.
robotov said:
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
Click to expand...
Click to collapse
I confirm that I also downgraded from Android 12 / One UI 4.0 (January 1 patch) to Android 11 / One UI 3.1 (November 1 patch) without problems. There were several aspects of the new version that were bothering me a lot, now I'm happy both versions are binary 3, but it will cease to be in the following versions for sure...
Hi can you help me with guidelines to upgrade to android 12? I'm using Note 20 ultra n985f/ds. It was previously a Live demo unit but is now fully functional on android 10. My csc is OXM WWD... looking forward to your help
Also I'd like to know which is better, should I just change my csc so I can receive the push for update via OTA or just follow a guideline for flashing with Odin, thanks in advance
Related
after downgrading back to android pie from one ui 2.0 android 10, my phone will not rotate in any apps, i have tried all the steps to correct this, clear cache, factory reset, install another firmware(older version)also when testing the acceleromator in settings using *#0*# , its not even detected, I cannot safely get back to android 9 without my phone working 100% and android 10 is missing alot of things I liked from 9, mostly the goodlock apps, can anyone suggest or help in any way, I have the unlocked version of the note 10 snapdragon USA, thanks
Years ago I had a Note that I fubar'd by flashing something I wasn't supposed to, and the GPS never worked right again. Your accelerometer *shouldn't* have been affected by reverting to Android 9, but if something is gonna go bad, it will happen when manually flashing firmware. Download the factory Android 9 image again, confirm MD5 hash and reflash it. If the accelerometer works, you're golden. If it doesn't, then you have three options:
1. Flash Android 10 and hope the accelerometer works. If it does, then leave it alone and learn to live with Android 10
2. Send it to Samsung for a warranty claim
3. Keep it and live with a broken accelerometer
Good luck!
I have a regular OnePlus 7 PRO (GM1913)
My bootloader is unlocked and I am rooted with Magisk on Android 10, with Oxygen 10.3.4 Stock.
something got funky with switching between apps and keyboard gets stuck sometimes and camera crashes, could be Nova launcher, could be Swiftkey, idk really
but I guess its time for a refresh to see if that fixes the problem (which I believe it will).
My Questions are:
1: How would I go on about flashing a custom ROM / latest Stock (recommendations welcome) without wiping data and keeping everything intact?
2: do I need a PC for that or can I do it "Over the air"? (sorry not fluent in this stuff since a long time)
Thank you!
Well, I'm not an expert but I've done that for the same reason as yours; ended up with the stock OxygenOS. Actually it started with stock OTA updater, ended with a brick(then unbrick)...
I've tried several custom roms, but
stock camera app is irreplaceable (Custom OS got more options, but Android 10+ is difficult to tinker with)
Even the most popular custom OS's may crash with an upgrade (especially if you tinker with your system). So whatever is wrong with it now, may got worse, or better.. Or it may get worse later(or not, who knows).
OTA doesn't do downgrades and check the signature of the package, so if something goes wrong or if you want oos back, you may need to use EDL with MSM Tools(Which, unfortunately requires a PC)
Thats why your safest bet is to:
Backup everything you can't afford to lose, then prepare an unbrick tool image if you can. You can backup without pc, but using edl or fastboot requires PC or other android device as a host device.
By the way, It's not that fun after a hundreds of reboot and flashes, so I use Linux now
Not sure if this really should be going to the noob friendly thread, but since it is a couple of questions covering various Android related issues, I figured that I will make it a separate thread after all.
1. Sometime updating an Android version would also end up updating the bootloader, at time rendering it impossible to downgrade again. Can this also happen in custom ROM (e.g. Lineage). I am asking this because I am thinking of custom ROM with newer Android version on my Galaxy S7, but may want to revert to a relatively old Android 7.0 after I am done testing.
2. Do file systems (the way application, application data are stored in the system and other information) etc. tend to stay the same as stock for a given Android version? For example between stock Android 7.1 and Lineage 14.1.
3. Same question as question 2., but between major Android versions (e.g. stock 7.1 and stock 8.0).
4. On rooted devices, can you usually update major version update without losing any data, and is it usually trouble free?
Feel free to skip reading this part, but for some background information, the reason I am asking all those questions is because one of the app I tried to restore via Titanium Backup and Swift Backup both failed. The application itself launches properly, but as soon as I restore the data, it would instantly crash and close. My guess is that this is probably caused by attempt to go from Android 6.0 to 11.0. Maybe it is the backup software or maybe something changed in the way files are stored, but whatever the reason, it just won't work.
So I am thinking that my best option is to try it to restore it on an Android 7.0 phone that I have (also on the way to be retired, and if it works, update to Android 8.0. Since Android 8.0 was the last officially released major version for that phone, and I was thinking that if it does work, perhaps I could alternatively go for an early Lineage ROM, then make gradual updates up to Android 11.0 and see if it helps the app remain unbroken. And then if it does work, perhaps I could then make a backup then restore it on the other new Android 11.0 phone that I have.
All in all, it is a silly amount of work to do just for one app.. but it is important to me, so I will exhaust every option that I can think of to find a solution.
Thanks!
Looking to revert back to android 11 and need to know what to do to not brick my phone.
Currently have an unlocked galaxy s21 plus, Odin is installed and so is a 4 file firmware package for Android 11..
I have USB debugging checked and most things backed up before I perform a factory reset..
Is there anything else that I'm missing, am I completely wrong? Sorry, it's been a long time since I've done anything like this
As long as it wasn't a OTA upgrade that also updated the bootloader version you should be able to roll back.
Make sure all critical data is redundantly backed up. Verify it's all there and readable.
So did you succeed in this?
Edit: It's downgradeable ez pz. Just download the latest Android 11 and flash via Odin. I have the Exynos version.
0rigin said:
So did you succeed in this?
Edit: It's downgradeable ez pz. Just download the latest Android 11 and flash via Odin. I have the Exynos version.
Click to expand...
Click to collapse
But what if the bootloader was updated? Maybe Snapdragon is different
JeffATL said:
But what if the bootloader was updated? Maybe Snapdragon is different
Click to expand...
Click to collapse
Probably. On the N10+'s snaps apparently it's not so you can roll back from 12 to 11 but no further. I'm still running Pie and 10 on my N10+'s and will not upgrade either.
blackhawk said:
Probably. On the N10+'s snaps apparently it's not so you can roll back from 12 to 11 but no further. I'm still running Pie and 10 on my N10+'s and will not upgrade either.
Click to expand...
Click to collapse
11 is the best iteration out of all mentioned, so I recommend you upgrade to that at least. 12 was a beta testing software, but 13 is again a step in the right direction and OneUI 5 is really becoming a powerhouse. Now if only they got rid of the bloatware, but that's also easier than ever to manage nowadays.
JeffATL said:
But what if the bootloader was updated? Maybe Snapdragon is different
Click to expand...
Click to collapse
You'll have more luck finding answers in the S21 Ultra section. Can't remember the exact bootloader versions, but if it's one of the later ones, you won't be able to revert. Android 12 is a piece of trash.
0rigin said:
11 is the best iteration out of all mentioned, so I recommend you upgrade to that at least. 12 was a beta testing software, but 13 is again a step in the right direction and OneUI 5 is really becoming a powerhouse. Now if only they got rid of the bloatware, but that's also easier than ever to manage nowadays.
Click to expand...
Click to collapse
I doubt that as cpu cycle sucking scoped storage is fully active on 11 and above. On Android 9 and 10* it isn't. Not willing to risk screwing up 2 fast, stable, clean running machines that are fulfilling their mission by changing the firmware. To hell with global elitist Google's disinformation and hype Gookill... I see you
Not vaxing my N10+'s eitherâ˜
Bloatware is easy to stop from at boot up on stock Samsung's with Package Disabler (not on Playstore). Fastest and easiest solution.
*haven't used my N10+ Android 10 much so I need to do a comparison with my other one loaded with Pie. Will a 2 5+ yo Pie load beat out a freshly loaded and configured Q load? Q seems to get slightly worse SOT, so far, but I need to play with it more as it may not be fully dialed in yet.
My oldest N10+/N975U/Pie runs like a bat out of hell. It's current load is 2.5+yo. It is my most stable platform of any OS in the last 18 years.
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that