The phone was up-to-date with OOS12 before and I downloaded the OOS13 upgrade within the system.
The installation seems to be working fine, but after the reboot, when doing the "new agreement" in the new OS, the next button is not working, and the phone goes into a reboot cycle.
Now it is just an endless cycle, which I can turn off but can not get off.
Can anyone please explain why this occurred, and is there any solution?
Another wired thing is that I have actually tried to update to OOS13 two times, the first time I updated manually, and the same problem occurred. But for some reason which I don't know, the phone just reversed itself back to the functioning OOS12 with all the data. I thought there are something wrong with the pack so the second time I just update through the system and the same issue occurred as described above.
How can I trigger that again? Just to at least make my phone back functional.
you can use the msm tool to restore the device to a working factory condition and than use oxygen updater to download the updates and install the update with system updater and use the local install option.
let me know how it goes!
JedidroidX said:
you can use the msm tool to restore the device to a working factory condition and than use oxygen updater to download the updates and install the update with system updater and use the local install option.
let me know how it goes!
Click to expand...
Click to collapse
nope, that still doesn't work, the phone is in that reboot cycle again.
T0ucHF1sh said:
nope, that still doesn't work, the phone is in that reboot cycle again.
Click to expand...
Click to collapse
You were able to boot the device after the MSM tool flash but if you update to OOS 13 the devices goes in bootloop again?
if msm tool was successful and still a boot issue than it sounds like a hardware issue. Perhaps look into to using the correct msm tool regarding you phones variant as that would be the correct firmware for the phone and hopefully would resolve the boot issue. For instance I have a tmobile variant so I would use the msm tool to restore that networks firmware. I don't know what else it could be!
JedidroidX said:
if msm tool was successful and still a boot issue than it sounds like a hardware issue. Perhaps look into to using the correct msm tool regarding you phones variant as that would be the correct firmware for the phone and hopefully would resolve the boot issue. For instance I have a tmobile variant so I would use the msm tool to restore that networks firmware. I don't know what else it could be!
Click to expand...
Click to collapse
do Chinese versions hardware have a differences with the global one and it kept me away from allowing to upgrade to oos13? Tbh I thought not so but it is probably the only explanation beside the hardware issue, maybe it is time to switch to a new phone....
T0ucHF1sh said:
do Chinese versions hardware have a differences with the global one and it kept me away from allowing to upgrade to oos13? Tbh I thought not so but it is probably the only explanation beside the hardware issue, maybe it is time to switch to a new phone....
Click to expand...
Click to collapse
It is possible that you need the correct msm tool, I speak from experience as when my fingerprint sensor and camera would not work due to heavy modification I did to the super image. After trying to restore with the global msm tool for my T-Mobile variant all was flashed correctly but still camera and fingerprint issue was not resolved. The only way was with the T-Mobile msm tool. The tool you need shouldn't be too hard to find. If its Chinese than I believe that would be HydrogenOS msm tool, after using that msm tool all should boot properly than you can convert it to OxygenOS and try to update again. If it messes up again at least you would know how to recover it to working condition.
Note: I believe the issue involves a different persist partition as I'm guessing for certain hardware to be slightly different. So the correct msm would be significant to a fully factory restored working firmware.
When I bought my 8T, it said it was a KB2000 (so, Chinese) but came with OOS 11 (KB05AA) installed, so I've used the KB05AA MSM Tool for OOS 11.0.7.9 (many times) and I've never had issues.
T0ucHF1sh said:
How can I trigger that again? Just to at least make my phone back functional.
Click to expand...
Click to collapse
It seems after unsuccesful update your phone rebooted to another slot with a working system prior to update.
You change slots using fastboot in bootloader using fastboot --set-active=other.
Related
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
Hello all,
I ****ed up, what I feel is big time?
I accidentally fat fingered the "install and restart" button for an OTA update for OOS12 on my rooted stock OOS11. From what I learned during my research phase of rooting my OP9, that's a big no no and can cause a lot of problems. When the phone booted back up I have no touch input at all. I have a mouse plugged into my phone and can use the phone that way and I am currently backing up as much as I can in the event I have to wipe my phone.
My question is, can I just dirty flash the previous OOS11 image I was running to go back to before the OOS12 OTA got applied? Just wanted to get the general consensus before I ruin my **** further.
I'm running stock recovery, stock OOS11.2.4.4 with Magisk, MagiskHide and not much else.
Much appreciated!
To my what i know you have to downgrade from 12 to 11 ect. I managed to get to global.
I messed up, and updated mine to 12. and from what i learned. my touch screen did not work due to the fact my update was for a global 9 pro, Not my oneplus 9-tmobile version. In the end I had to use the india msm tool to get back to working
warglock said:
Hello all,
I ****ed up, what I feel is big time?
I accidentally fat fingered the "install and restart" button for an OTA update for OOS12 on my rooted stock OOS11. From what I learned during my research phase of rooting my OP9, that's a big no no and can cause a lot of problems. When the phone booted back up I have no touch input at all. I have a mouse plugged into my phone and can use the phone that way and I am currently backing up as much as I can in the event I have to wipe my phone.
My question is, can I just dirty flash the previous OOS11 image I was running to go back to before the OOS12 OTA got applied? Just wanted to get the general consensus before I ruin my **** further.
I'm running stock recovery, stock OOS11.2.4.4 with Magisk, MagiskHide and not much else.
Much appreciated!
Click to expand...
Click to collapse
I would def recommend just MSM back to stock 11.2.4.4, I was in your same situation before and I always had the touchscreen issues if I was rooted when I upgraded to OOS12. I think I tried flashing back to 11 and just ended up soft bricking my device and having to MSM anyway. Also like the commenter said above I had to use the Indian MSM but Ive been able to use the Global MSM now with no issues so if thats what your're on Id recommend trying that one first and only using the Indian MSM if that one gives you errors.
So I'm running into this same problem and absolutely can not upgrade to OOS12. Each time, by display will not respond to touch. I went back to 11 via MSM (HAD TO USE OP9 Pro INDIA) because OP screwed something up with these phones.
I have tried multiple ways, went back to OOS 11, installed latest OOS 11 without root. Locked bootloader, Installed latest OOS 11 twice via system update to make sure everything was clean. Installed OOS 12 update and same problem.
Same problem here.....
I have installed the msm india and then the official android 11 for OP 9. After that the OP9 runs on Android 11. After that i have closed the bootloader and try the msm with the eu rom and i gets the "device not match image" error. Maybe i have the new rom for op9 installed and the productnumber is still on op9p ? Now i am going back to a custom rom. is there an option to get the fully working camera on a custom rom?
DerBaLu841 said:
Same problem here.....
I have installed the msm india and then the official android 11 for OP 9. After that the OP9 runs on Android 11. After that i have closed the bootloader and try the msm with the eu rom and i gets the "device not match image" error. Maybe i have the new rom for op9 installed and the productnumber is still on op9p ? Now i am going back to a custom rom. is there an option to get the fully working camera on a custom rom?
Click to expand...
Click to collapse
To get back to the correct ROM, boot to TWRP and flash the signed full zip to each slot.
Hello
I was originally on the LineageOS ROM, and used the MSM tool to go back to stock firmware/rom. I updated all the way up to the newest A12 update... and tried to use the msm tool again to go back and now my phone will not recognize the sim card and freezes and crashed randomly every few minutes. I've tried clearing the cache and whatnot in the recovery menu and nothing helps.
Edit:
So I finally got this issue to stop. The MSM tool I was using was pretty outdated and something about it wasn't sitting right with the phone. I downloaded a more updated version of the MSM tool and the issue is fixed entirely I believe.
During this issue I was experiencing
-Random freezes and restarts
-Sim card not reading
-OEM Unlock being greyed out where it never has been before
If anyone is experiencing this issue feel free to reply on here or DM me and I can upload and post the exact MSM tool that I used to fix this issue.
duzzqqqq said:
Hello
I was originally on the LineageOS ROM, and used the MSM tool to go back to stock firmware/rom. I updated all the way up to the newest A12 update... and tried to use the msm tool again to go back and now my phone will not recognize the sim card and freezes and crashed randomly every few minutes. I've tried clearing the cache and whatnot in the recovery menu and nothing helps.
Edit:
So I finally got this issue to stop. The MSM tool I was using was pretty outdated and something about it wasn't sitting right with the phone. I downloaded a more updated version of the MSM tool and the issue is fixed entirely I believe.
During this issue I was experiencing
-Random freezes and restarts
-Sim card not reading
-OEM Unlock being greyed out where it never has been before
If anyone is experiencing this issue feel free to reply on here or DM me and I can upload and post the exact MSM tool that I used to fix this issue.
Click to expand...
Click to collapse
Would be great if you can post a link to the msmtool. I'm going through the same issue right now
gingerboy92 said:
Would be great if you can post a link to the msmtool. I'm going through the same issue right now
Click to expand...
Click to collapse
You still need it? I don't have a direct link to the specific one I have, could only upload the one I currently possess. And this is for the TMobile variant.. You could also try different USB ports, different cable, oem cable that came with the phone, etc.
duzzqqqq said:
You still need it? I don't have a direct link to the specific one I have, could only upload the one I currently possess. And this is for the TMobile variant.. You could also try different USB ports, different cable, oem cable that came with the phone, etc.
Click to expand...
Click to collapse
I tried extracting newer version from op9 file. Works great for a couple of days until the phone upgraded to android 12 by its own and the problem started again.
My global one plus 8 also randomly reboots (every ±5 minutes). The firmware with the MSM tool does not change the situation in any way, but only exacerbates (The phone stopped seeing imei and lost the function of calling) I need help
Westy089 said:
My global one plus 8 also randomly reboots (every ±5 minutes). The firmware with the MSM tool does not change the situation in any way, but only exacerbates (The phone stopped seeing imei and lost the function of calling) I need help
Click to expand...
Click to collapse
In the event that you cannot bring your device from the dead via the MSM Tool, you might be a candidate for a replacement device.
Can you send the link to MSM tool because i have the same problem. Thank you.
Moaz Adel said:
Can you send the link to MSM tool because i have the same problem. Thank you.
Click to expand...
Click to collapse
MSM Tool.
So today has been.......Less than fun. Started off wanting to update my phone so i made a TWRP back up, downloaded the latest Oxygen OS and that's where my problems started. I accidentally flashed the Android 12 build. Immediately lost my data and TWRP recovery so I stupidly tried to flash it like I did before without stopping to think if there may be anything different in how it's done Android 12.....After it said it was successfully flashed I went and restated the phone.... and now It's stuck in crashdump mode or fastboot mode.
I originally I thought I would be fine. I've used the MSM download tool before and there were plenty of guides about this exact problem but for some reason it failed (my only guess is because I used the EU version and my phone was originally a T-mobile version that I converted to the EU version? I said that the Image didn't match so that was my best guess) and now the phone isn't even being recognized in ADB when in fastboot (I checked before I ran MSM) so I can't even try to flash the other one....
If anyone knows of ANYTHING that might work, that would be amazing!
P.s. Trust me, I KNOW this is all on me and I know I should've done more research before going through with it but I figured it would be just like every other dirty flash smh.
Blackest Pain said:
So today has been.......Less than fun. Started off wanting to update my phone so i made a TWRP back up, downloaded the latest Oxygen OS and that's where my problems started. I accidentally flashed the Android 12 build. Immediately lost my data and TWRP recovery so I stupidly tried to flash it like I did before without stopping to think if there may be anything different in how it's done Android 12.....After it said it was successfully flashed I went and restated the phone.... and now It's stuck in crashdump mode or fastboot mode.
I originally I thought I would be fine. I've used the MSM download tool before and there were plenty of guides about this exact problem but for some reason it failed (my only guess is because I used the EU version and my phone was originally a T-mobile version that I converted to the EU version? I said that the Image didn't match so that was my best guess) and now the phone isn't even being recognized in ADB when in fastboot (I checked before I ran MSM) so I can't even try to flash the other one....
If anyone knows of ANYTHING that might work, that would be amazing!
P.s. Trust me, I KNOW this is all on me and I know I should've done more research before going through with it but I figured it would be just like every other dirty flash smh.
Click to expand...
Click to collapse
You can't use TWRP on OOS 12, though you might be able to install the OOS 12 zip using TWRP if you're on OOS 11.
Check your drivers if you can't connect to the phone in bootloader mode. You might need to simply reinstall it (I've had to do this a number of times).
You might be able to switch active partition it might save you I had something similar happen changing partion helped me get back into adroid
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.