Hey, I'm trying to update my phone, and when I start downloading the update the process bar proceeds for about one second and then i get "installation problem" error in the update screen.
Any idea why?
I'm using OnePlus 8T (KB2003) on Oxygen OS 11.0.9.9.KB05AA, Trying to update to Oxygen OS 11.0.10.10.KB05AA.
My phone is rooted, but I have updated in the past, and everything worked fine.
You will have to restore the stock 11.0.9.9 boot image before you can install the 11.0.10.10 update. The update checks the status of the current system before starting the update process to make sure it's fully stock.
There's various threads on how to update if you're rooted.
The thing is, I updated this phone with root already several times.
After rechecking I noticed that before I restored images like you said.
I guess I just forgot this part.
Anyways, thank you very much!
Related
Dear all,
Hope you are doing great, I was downloading and installing automatic updates just fine and the other week got a notification about a new update of over 1.4 gbs and the automatic installer was not possible to do and requested me to download it and installing it manually. I downloaded the Rar and everything was going smooth and when I enter TWRP I installed at first shoot without doing any wipe or clear cache or data.
All was installed and it told me to restart the phone, I did that and vroom a vibrating sound happen and got me back to the main screen of Poco and then to TWRP and show me 3 workarounds to clear data and cache and the last resort do a clean flash rom.
I had to end with the last option since I was unable to install the update. What could be gone wrong here? I am back at stock now and I am very sad that this fricking update break all the custom firmware and got me bootlooped
I look for your inputs and maybe I can try again.
Thank you!
You must install Android 11 firmware for newer versions of Arrow as it has switched to OSS vendor.
I was on arrow os 11 so Android 11 was on there, the issue was when I was installing the new update from surija I believe si called the developer.
Do you guys have an idea what did I did wrong? Should You recommend staying vainilla stock miui 12 with root privileges or arrow 11?
Thank you!
I was able to flash the latest version update but I am having a System UI is not responding and got WIFI broken so if anyone is installing this update be careful, does anyone installed the last arrow OS update?
I am currently having issues with the last update, I think I will stick with no updates on the firmware
Sorry I am posting multiple updates on my thread, but I tested it and definetly the last update from Surya break the OS when you login you do not have WIFI and is showing the error I mentioned UI system unresponsive. I installed the version from April from Arrow OS and all works like a charm.
So if anyone reads this be careful with latest release from Surya 5/14 version
Yes, i can confirm. The version I used initially was from april 30. The update from may caused bootloop. I'll be turning off updates when I restore it with miflash.
The main reason I went with arrow is that it is selinux enforcing and supports safety net. But this really makes me think..
@SebixWolf The problem may have been that you flashed arrowos from the wrong miui version. I just miflashed back to the original regional version, flashed twrp again and flashed the R firmware. See https://forum.xda-developers.com/t/...ng-flashing-custom-rom.4274891/#post-85002889
I was having a bunch of issues updating my phone. I kept receiving a System Update Installation Failed error. I tried local using the zip downloaded directly from OnePlus support and it wouldn't work. It said that there was no update available when trying to use the update setting. Long story short...it just wasn't working. I then proceeded to use the MSM Tool to completely erase and reset the phone. STILL wouldn't work. I randomly came across someone saying you needed OxygenOS 9.0.9 before 10..tried it and it worked perfectly. Sigh.
I wanted to save someone else the hassle and document it here with the error I was receiving. Good luck! I got OOS 9.0.9 HERE if anyone needs it and I'm allowed to link.
@bam099
Thanks for sharing the link for 9.0.9
Out of interest which version were you upgrading from and which version MSM tool were you trying?
My OP6 is still on 9.0.8 as I've not had the inclination to go through the hassle of a full reset to restore to factory (BL is unlocked, TWRP is installed, was rooted but got rid of that due to constant hassle with banking apps detecting root and magisk hide not working for all my bank apps)
Now that 11 is released as stable I'm probs going to to the full return to factory stock and then upgrade straight to 11 (once the early adopters have found the first bugs and OP patch them ) but if 9.0.9 was needed to update to 10.x.x I guess the same will be needed for 11.
Surprisingly I took a little bit of notes so I could go back if I wanted to (and I wouldn't waste time searching for issues like this weird 9.0.9 thing I found). I was on 9.0.6 (Build Number A6003_22_190528).
I would imagine that 9.0.9 is going to be needed to get to 11 (I'm on 11 now but I went from 10 so I'm not positive about what is required).
If you download the stock ROM for 9.0.9 can't you upgrade it? I THINK TWRP can flash the update but I'm sure there's some kind of an issue with an unlocked BL and upgrading via the stock app.
I don't recall what version of the MSM tool I used...I was frustrated at that point and not taking notes haha. I keep remembering 4.0.4 so if that sounds right for MSM then that's what I used. But I think any of the ones you see on a guide would work. Good luck with it!
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.
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.
Running stock OOS 13 on my 8t. I am rooted with stock kernel .
Attempting to update to kb2005_11.F.62. Tried Through system update , Fails every time at 28% .
Also tried Using oxygen updater, fails same at 28% .
I've tried other updater apps that OnePlus oxygen updater suggested, no luck .
I set " auto update " within developer options , as OnePlus website States to do in my situation.
I deleted the downloaded OTA file and retried .
Not sure what else to try at this point .
Any ideas fellow oneplus users?
Where might I find the 11.f.62 full image ? I am on the international kb2005 handset.
Seems to be root is the case of problems.
OTA check for modifications on your system before installation.
If it finds any, it aborts installation.
So look through this great guide, on how to temporary unroot, install update and root again.
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
Avoid this update if you haven't updated yet. I just got the green vertical line 12 days after updating.
OTA fail
I have a stock 8T KB2005 Android Version 13 security update October 5,2002
System update KB2005_11.F.620 will not install. I have tried downloading multiple times.
install fails just nothing happens
any suggestions would be appreciated
anyone else not recommending upgrade?
airtimeca said:
OTA fail
I have a stock 8T KB2005 Android Version 13 security update October 5,2002
System update KB2005_11.F.620 will not install. I have tried downloading multiple times.
install fails just nothing happens
any suggestions would be appreciated
anyone else not recommending upgrade?
Click to expand...
Click to collapse
Did you enable "Automatic System Updates" in Developer options?
I was sure it was, but I enabled it.
I have been successfully updating for a couple of years
BUT
"There was an issue while preparing to restart. Please try again later."
still no luck