Oneplus 9 EU version LE2113 has been restored via MSM. OTA updated to latest OOS 11 ok but OOS12 OTA's always fail at the rebooting stage. The "powered by Android" screen blinks briefly, screen goes black until it boots back to OOS 11.
Anyone know how to make the official OTA's work? I want to keep the bootloader locked and ultimately get the phone updated to C.62.
I've tried various approaches: clearing data in Google Services Framework app, installing Google OTA Repair.apk (didn't seem to work), wiping in the OnePlus recovery.
It's no problem to unlock, boot twrp and flash the builds that way, but relocking bootloader is impossible when on OOS 12.
I had the same problem.
Just flash this with twrp
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
rivercz said:
I had the same problem.
Just flash this with twrp
Click to expand...
Click to collapse
Thanks, but as I said, I want to keep the bootloader locked and get oos12 ota's to boot in the locked state. there's no problem updating with unlocked bootloader but it won't lock again after.
Yeah i have same problem, then we just need to wait when someone upload msm with c.47
Ever find a fix? Same problem with LE2115. Used MSM tool and now can't update past 11.2.10.10
I no longer have this phone.
RIP OnePlus. Good while it lasted...
Related
I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Have u not read anything in these forums, tutorials or anything?
There are like 50 threads on how to upgrade and about the new partitions for op6, it is even clear when u installed twrp too
dRakeNNNN said:
I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Click to expand...
Click to collapse
Hi, just to clarify when you install an OTA on the oneplus 6 it uses the new partitioning system which is different so to remedy the situation just try reflashing TWRP enchilada installer using fastboot.
cschmid44 said:
Hi, just to clarify when you install an OTA on the oneplus 6 it uses the new partitioning system which is different so to remedy the situation just try reflashing TWRP enchilada installer using fastboot.
Click to expand...
Click to collapse
Previously, i've installed Beta(unofficial) version of TWRP, now i want to re-install TWRP with Official version , do i need to remove or do something firstly?
To fix it just download the official TWRP for oneplus 6 from the official team win recovery project page and then you put that on your phone, and flash using your currently installed TWRP then after that make sure you also install the root package as installing the new version of TWRP will modify the new boot image, Also a good time to mention that it will install in both slots (Seamless update slots) Treble slots if you will just to be aware.
cschmid44 said:
To fix it just download the official TWRP for oneplus 6 from the official team win recovery project page and then you put that on your phone, and flash using your currently installed TWRP then after that make sure you also install the root package as installing the new version of TWRP will modify the new boot image, Also a good time to mention that it will install in both slots (Seamless update slots) Treble slots if you will just to be aware.
Click to expand...
Click to collapse
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
dRakeNNNN said:
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
Click to expand...
Click to collapse
Just follow one of the many upgrade guides. Skip the part about upgrading to 5.1.6 but for the rest follow the steps exactly. No need to explain all this in yet another thread imo. You'll need a pc though.
that's would be great if twrp can be flashed and stays there without wiping as well as root.
Pleasssseeeeee read before creating a new thread
dRakeNNNN said:
I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Click to expand...
Click to collapse
Wait!
Don't install 5.1.6 ROM because OP has retired it. The last version availabe on OP site is the 5.1.5.
MuttleyMB said:
Wait!
Don't install 5.1.6 ROM because OP has retired it. The last version availabe on OP site is the 5.1.5.
Click to expand...
Click to collapse
I'm using 5.1.6, so far so good. I don't have any issue on 5.1.6. ?
Sent from my OnePlus6 using XDA Labs
dRakeNNNN said:
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
Click to expand...
Click to collapse
You can't boot into twrp because it's not there anymore. The OTA created a completely stock version of the OS that you're now booted on. You need to reinstall twrp and magisk according to the posted guides. This is going to be the case with all OTAs. The stock updater looks for root, and when it's there, it installs a complete OS, not an incremental update.
I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?
I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well
In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.
I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?
Hi,
After ignoring the notification to update to Android 11 for over a month, I finally gave in an tried the update today.
I normally run stock OOS ROM with TWRP and Magisk, and updates are always fairly simple, let the OS update, overwriting the recovery and losing root, plug in to the PC and just `fastboot boot` the TWRP image, and then flash TWRP and Magisk on the phone itself, and bobs your teapot.
Alas, Android 11 shat all over those plans. With all the news out about Android 12 being in Beta, I had forgotten that Android 11 was so new to OP7Pro. Correct me if I wrong, but TWRP doesn't seem to work, which was my first mistake, but now Magisk has moved to a "need to patch the boot.img" model, which I hadn't seen before?
Anyways, after attempting to patch my own boot.img, I can no longer boot anything; phone just gets past the bootloader unlocked warning, then reboots into recovery.
I panicked then and attempted to flash one of the flashable Android 10 images from Mauronofrio's thread, which I think made things worse; now it just reboots repeatedly.
Any help appreciated, thanks!
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
I managed to use the MSM Download Tool from the last time I bricked my phone, which got me back to a bootable Android 10. Not much worse in life than losing all my data but better than a brick.
mc_teo said:
Woops, I actually have a Oneplus 7 Pro (not a 7T). Can I move a thread myself?
(...)
Click to expand...
Click to collapse
You cannot
But we gladly do this for you (as I just did)! Remember that you can always report your own posts for any type of forum maintenance you may need.
At your service and stay safe!
Timmy
Forum Moderator
A fix for your failed patched boot.img is just flashing the stock boot.img.
For upgrading (official OTA) and keep root, after installation finishes don't reboot and go to magisk, select install to the inactive slot and reboot, after reboot your phone will have the lastest update without loosing root.
And the best way to restore your phone is using msmtool
Hi everyone! I have a question! Does anyone know how to install a custom rom on the oneplus 9 t mobile with OOS 12? Do I have to downgrade or can I install a rom that has android 12 by default?
My version its LE2117_11_C.19
You should firstly update to the latest OOS12 update TMo gives us. After that unlock bootloader (as per the guide here on the fourms) via unlock code method (you will have to wait for TMo to send that your way as it's device specific) and then follow the instructions from the rom provider.
I'm running StagOS on my TMo OnePlus 9 without issues since their last release, before that ran Lineage, Jaguar, Nameless. As long as you are updated to latest OOS and with an unlocked bootloader, you can flash any rom on here provided you follow their instructions. If you brick your phone you can use the modified MSM tool I posted on one of my threads to un-brick and bring back to life your phone (keep a backup of your data though)
RandomLatinDude said:
You should firstly update to the latest OOS12 update TMo gives us. After that unlock bootloader (as per the guide here on the fourms) via unlock code method (you will have to wait for TMo to send that your way as it's device specific) and then follow the instructions from the rom provider.
I'm running StagOS on my TMo OnePlus 9 without issues since their last release, before that ran Lineage, Jaguar, Nameless. As long as you are updated to latest OOS and with an unlocked bootloader, you can flash any rom on here provided you follow their instructions. If you brick your phone you can use the modified MSM tool I posted on one of my threads to un-brick and bring back to life your phone (keep a backup of your data though)
Click to expand...
Click to collapse
so can i follow any tutorial to install any rom if i have unlocked bootloader next to sim? since I tried once to change to global and it worked, I put a module and my cell phone and the phone bricked, with the MSM Tool I was able to recover the OOS t mobile version, but I thought I had to downgrades OOS 11 to install any rom and I never did anything again because of fear for the brick
sorry for my bad English
Yasser.d said:
so can i follow any tutorial to install any rom if i have unlocked bootloader next to sim? since I tried once to change to global and it worked, I put a module and my cell phone and the phone bricked, with the MSM Tool I was able to recover the OOS t mobile version, but I thought I had to downgrades OOS 11 to install any rom and I never did anything again because of fear for the brick
sorry for my bad English
Click to expand...
Click to collapse
Yes, that's it. Basically have your phone updated to the latest OxygenOS TMobile can give you,; Have your phone SIM Unlocked AND Bootloader Unlocked and then follow all the steps the Developers of the ROM you choose give for the installation.
If any rom specifically asks for OxygenOS 11, then the same steps are applied except instead of latest OS versión, the one the Dev asks for
Then I will start the installation of some rom that I like on top of the latest update of tmobile OOS 12, do you recommend any specific one that is pixel experience or similar performance?
RandomLatinDude said:
Yes, that's it. Basically have your phone updated to the latest OxygenOS TMobile can give you,; Have your phone SIM Unlocked AND Bootloader Unlocked and then follow all the steps the Developers of the ROM you choose give for the installation.
If any rom specifically asks for OxygenOS 11, then the same steps are applied except instead of latest OS versión, the one the Dev asks for
Click to expand...
Click to collapse
For example, when I go to the official lineageOS 19.1 page, it says that the compatible devices are all except mine LE2117, do I continue to install anyway?
Hi, I did something stupid and need some help please.
I got the bootloader unlock code for my KB2007 - Unlock went well, no issues.
Then I proceeded to download and install the latest official TWRP - Also no issues, I was in the custom recovery, created some backups etc.
After that, I followed the instructions to install Lineage OS as posted here:
Install LineageOS on kebab | LineageOS Wiki
wiki.lineageos.org
I flashed the dtbo and vbmeta partitions as instructed and proceeded with adb sideloading the copy-partitions-20220613-signed.zip file - Somewhere around here is where things went south.
I was not able to access/read my data partition anymore, and attempted to flash the lineage-recovery. After a reboot, I'm now stuck in the bootloader (fastboot). When I select Recovery mode, the phone just goes black. I also can no longer "fastboot boot twrp.img" - Error: "Failed to load/authenticate boot image: Load Error".
After checking the guide one more time I noticed it says the device has to be on Android 12, which mine was not (it was still in factory condition - Android 11). So that was likely the problem.
So now the big question is can I recover from this state? If yes, what's the best way to do so?
Thanks so much!
FreeDee said:
Hi, I did something stupid and need some help please.
I got the bootloader unlock code for my KB2007 - Unlock went well, no issues.
Then I proceeded to download and install the latest official TWRP - Also no issues, I was in the custom recovery, created some backups etc.
After that, I followed the instructions to install Lineage OS as posted here:
Install LineageOS on kebab | LineageOS Wiki
wiki.lineageos.org
I flashed the dtbo and vbmeta partitions as instructed and proceeded with adb sideloading the copy-partitions-20220613-signed.zip file - Somewhere around here is where things went south.
I was not able to access/read my data partition anymore, and attempted to flash the lineage-recovery. After a reboot, I'm now stuck in the bootloader (fastboot). When I select Recovery mode, the phone just goes black. I also can no longer "fastboot boot twrp.img" - Error: "Failed to load/authenticate boot image: Load Error".
After checking the guide one more time I noticed it says the device has to be on Android 12, which mine was not (it was still in factory condition - Android 11). So that was likely the problem.
So now the big question is can I recover from this state? If yes, what's the best way to do so?
Thanks so much!
Click to expand...
Click to collapse
Restore to stock via MSM.
You must update to OxygenOS 12 before installing lineageos 19.1 or you will brick.
The lineagsos guide is wrong and I bricked my device by following it too.
For now, you can only unbrick it with msmtool.
[OP8T][OOS TMO KB09CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Then OTA to OOS 12, then install LOS19.1.
Thanks guys! I was able to restore the device using the MSM tool
I intend to keep it on OOS 11 (and potentially flash LOS18.1), because KB2007 is the T-Mobile variant and based on what I read dual sim only works with OOS 11.
The problem is it is becoming increasingly difficult to find instructions (or even downloads) for anything but the very latest versions :/
FreeDee said:
Thanks guys! I was able to restore the device using the MSM tool
I intend to keep it on OOS 11 (and potentially flash LOS18.1), because KB2007 is the T-Mobile variant and based on what I read dual sim only works with OOS 11.
The problem is it is becoming increasingly difficult to find instructions (or even downloads) for anything but the very latest versions :/
Click to expand...
Click to collapse
You can also use KB2007 OOS 13 beta 1 which works with dual sims.
Rootk1t said:
You can also use KB2007 OOS 13 beta 1 which works with dual sims.
Click to expand...
Click to collapse
Thanks! Yeah, I also read about that, and it does indeed sound like a potential way to go.
Do you know if anyone has figured out yet what makes this "beta 1" special in that it allows dual sims? I think I also read it's no longer possible with beta 2.
FreeDee said:
Do you know if anyone has figured out yet what makes this "beta 1" special in that it allows dual sims? I think I also read it's no longer possible with beta 2.
Click to expand...
Click to collapse
As far as i know, it's still unknown what makes beta 1 work in dual-sim mode.