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!
Related
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
QuesteU said:
Bare with me, I'm a total noob and I hold my hands up, I got a galaxy note 8.0, rooted it fine then I went to install CM 13 for it following partially instructions partially my own knowledge and now it's muffed. No matter how many times I tried it wouldn't work and I was messing around with it all night last night and all day today and in my infinat wisdom I removed all OS from it full stop. I have been sat here for 6 hours trying to put cm on it (tried 11, 12 and 13) tried installing stock marshmallow I downloaded from some site, and even some other ROM I can't remember off the top of my head (the logo is a horse's head or something) and yep nothing what so ever i have tried several different boot thingies like twrp and it always fails when I try to install the ROM, I know I should have backed up and I thought I had using titaniumbackup but that went with the OS. It's currently got twrp on it and I can get into that and connect it Odin (I think that's what it's called) but that's all I can do. Is it fixable or is it scrap? >.<
Update, after putting it down and thinking about it from another perspective I worked out a fix, it's back running 4.4.2 and works fine (on my note I will say the latest update of the Google app causes a problem with the system UI if you have Google now as your launcher) I'll update with full details in the morning in hopes that if anyone else has a similar problem this will help.
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried any of the CM based roms from xda ? You may only need to update your recovery. Both of these should work on your device
https://forum.xda-developers.com/ga...0-1r61-rom-resurrection-remix-v5-7-3-t3449444
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-n51xx-t3533329
Latest twrp
https://forum.xda-developers.com/galaxy-note-8-0/development/recovery-twrp-2-8-5-0-t3035004
Good Luck
Sawdoctor
Long story short I updated to Android 10, didnt like that there wasn't any good way to root as TWRP hasn't updated yet, and downgraded back to Android 9. Before all of this, saying 'OK Google' would bring up the assistant, and after downgrading back to Andoid 9 saying 'OK Google' does nothing, and opening it either by longpressing home or using active edge does work. However, doing it this way there is a few second delay between the assistant popping up, and the assisistant being able to take voice input. It seems like my microphone should always be active, but it isn't. Voice match is set up and enabled, and power save mode is off. Help would be appreciated, thanks.
SirHappyCatIII said:
Long story short I updated to Android 10, didnt like that there wasn't any good way to root as TWRP hasn't updated yet, and downgraded back to Android 9. Before all of this, saying 'OK Google' would bring up the assistant, and after downgrading back to Andoid 9 saying 'OK Google' does nothing, and opening it either by longpressing home or using active edge does work. However, doing it this way there is a few second delay between the assistant popping up, and the assisistant being able to take voice input. It seems like my microphone should always be active, but it isn't. Voice match is set up and enabled, and power save mode is off. Help would be appreciated, thanks.
Click to expand...
Click to collapse
Did you factory reset your device? If not, you should try to do so as you are downgrading to an older version so it's very likely that your "new" configuration (created by Android 10) is no longer compatible to Android 9.
AndDiSa said:
Did you factory reset your device? If not, you should try to do so as you are downgrading to an older version so it's very likely that your "new" configuration (created by Android 10) is no longer compatible to Android 9.
Click to expand...
Click to collapse
I restored a Nandroid backup of Data, System Image, and Boot. I had this issue when I first rooted my phone after I bought it, but I forgot if it fixed itself or how I fixed it.
If I remember correctly, there was a version of the ExperiementalX kernel that broke voice commands a while back. If you run that kernel, perhaps the backup was made with that older version. The current versions certainly fixed the issue.
That being said, rooting on Android 10 is not hard even though you can't use TWRP. These instructions are pretty easy to follow.
sic0048 said:
If I remember correctly, there was a version of the ExperiementalX kernel that broke voice commands a while back. If you run that kernel, perhaps the backup was made with that older version. The current versions certainly fixed the issue.
That being said, rooting on Android 10 is not hard even though you can't use TWRP. These instructions are pretty easy to follow.
Click to expand...
Click to collapse
I actually tried to root using the boot image patching method, but it did not work, so I switched back. I am using EX kernel so I will look into that, thank you.
I was already on the latest version (1.06) and after doing some reading it seems like the issue only affected 1.03 and below. I reflashed anyway and the issue is still present And as for why I still don't want to use Android 10, I really like the ability to create Nandroid backups with TWRP.
Hi Team,
On the latest OOS 10.3.2. Have done multiple resets, downgraded using msm tool to OOS 5.1.3 and then manually updating them. Factory reset done a couple of times.
Anyone can help?
Currently running Magisk 20.4, bootloader unlocked.
Same here
I even tried using msmtool and even installing custom rom still no luck in fixing this issue . Most irritating part about this is not able to use auto rotate .
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
oldmanz said:
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
your the best man i can finally use other ROMs again
my fix was to use oneplus 7 port on my 6 but it was annyoing me
oldmanz said:
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
Thank you kind person. For more than two months I tried to return the phone to normal operation and all to no avail. So I came across your post and now my phone is full again. Thank you very much.
oldmanz said:
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
Thanks a lot man !!!!
Following your steps, the automatic brightness and also the automatic screen rotation works for me again.
Thank you @oldmanz
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
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