Database Info

(TMO) Oxygen OS 11 Open Beta 1 No Service

This is just for a simple discussion. I've tried flashing the open beta, and since Developer Preview 4 I've not been able to get service. Flashing other modem versions ends up breaking the phone. The new modem is also ~ half the size of the old versions.
Anyone had any luck?

I'm on DP4, should I back up my modem before updating?
Edit: It works perfectly for me on TMobile converted.

Dameon87 said:
This is just for a simple discussion. I've tried flashing the open beta, and since Developer Preview 4 I've not been able to get service. Flashing other modem versions ends up breaking the phone. The new modem is also ~ half the size of the old versions.
Anyone had any luck?
Click to expand...
Click to collapse
Did you flash Global 10.5.12 first?

I can't get any 5G with global or beta. Might need to see what's going on when I return to stock.

shaneg79 said:
Did you flash Global 10.5.12 first?
Click to expand...
Click to collapse
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.

Dameon87 said:
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.
Click to expand...
Click to collapse
Did you backup your modem before?

shaneg79 said:
Did you backup your modem before?
Click to expand...
Click to collapse
No, I've tried flashing the modem from 10.5.12 from fastboot as extracted from the payload.bin

Dameon87 said:
No, I've tried flashing the modem from 10.5.12 from fastboot as extracted from the payload.bin
Click to expand...
Click to collapse
Then you will have to flash back to the T-Mobile firmware and upgrade to 10.5.20 then reunion bootloader backup your modem and everything then covert

I have my tmobile op8 on the open beta and this was the only way I was able to have service.
1. Msm to tmobile 10.5.7
2. Flash unlock token
3. Unlock bootloader
4. Flash global 10.5.7 (I still had service at this point, and I did not flash any modem)
5. Downloaded oxygen updater apk from chrome (to avoid restoring everything from the Google play store just yet)
6. Updated to 10.5.12
7. Switched oxygen updater settings to download open beta and then flashed from system settings (still had service, no modem flash)
8. Reset the phone from settings (to go through set up and restore all my data from play store)
This was just what I had done and it did work for me so good luck if you decide to try. I only did the chrome apk file for oxygen updater to avoid having a bunch of data on my phone when going to the beta. I haven't had any weird bugs and it's been smooth for me

Not sure why some are having this issue, I have signal with no issues on beta. I was on .12 and went to beta.

I had this issue on my other OnePlus 8, a data wipe fixed my signal entirely.

Dameon87 said:
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.
Click to expand...
Click to collapse
That sucks. I was on 10.5.12 a couple nights ago. Decided to try DP4 because all the hype about copying OneUI was making me interested. I loved OneUI on all my Samsung devices. Missed it actually!
When I flashed DP4 I loved it. I checked this morning for Beta 1 OTA after seeing it was out. It downloaded and installed. No issues at all. I have not rooted or anything else.
The only thing I did diff was I was on DP4 before OB1. However, this really should not matter. The beta is expected to be flashed from 10.5.x AFAIK so that should not be the problem.
What's weird about this phone though, I am always seeing people reporting issues with signal after flashing. I dont get it. I have yet to loose signal. Not to say I have not had ****ty signal, thats just T-Mobile where I am at. But I can say with the latest T-MO update and the latest Beta 1 I can hit almost 100 megs down. Before these updates I was getting about 10 megs. ON all devices in my house on all carriers known to man. Occasionally I could get 11 megs down
pro_granade said:
I'm on DP4, should I back up my modem before updating?
Edit: It works perfectly for me on TMobile converted.
Click to expand...
Click to collapse
Yep, me too! I was pretty happy to have good speeds, and the latest OOS.

Ok I'm on 10.5.20 do I need to downgrade first or can I flash straight to global 10.5.12

Question [HELP]Fat fingered OOS12 OTA update on rooted stock OOS11 and now I have no touch input.

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.

Need help updating metro version moto one 5g ace from 10 to 11. Rooted

Title says is all, well not all. This would literally be the first update the phone got, I rooted day one out the box and keep the same firmware for flashing when switching roms, now that root is detected with a game, yes my root is depended on access to certain things, so I'm constantly rooting doing what is needed then uninstalling magisk. Very tiring. I wanted to get to Android 11, hoping no data loss, rooted if able and twrp if available for Android 11 on this one. Any pointers in the right direction would be helpful, thanks in advanced

Without taking the OTA update, I know of nothing that will get you to 11 without wiping your data. (That is why backups are good.) lolinet has 11 firmware. TWRP can be had on Telegram. Magisk is available on the github.

RETIEF said:
Without taking the OTA update, I know of nothing that will get you to 11 without wiping your data. (That is why backups are good.) lolinet has 11 firmware. TWRP can be had on Telegram. Magisk is available on the github.
Click to expand...
Click to collapse
I have all the files needed, even without root ota says you up to date security patch January 2021 lol. I heard somewhere to edit the fstab to not auto reboot, kinda like Odin with Samsung's. Then flash thru twrp, thinking that would delete twrp, but hey is 11 really better?

I don't think you can flash a stock ROM with TWRP. No, I don't think 11 is better. That is just my opinion.

RETIEF said:
I don't think you can flash a stock ROM with TWRP. No, I don't think 11 is better. That is just my opinion.
Click to expand...
Click to collapse
I honestly hate everything after 5 lol. 10 is frustrating. 11 has rw I'm doing it, hell 5g speeds 200 apps, 10 minutes lol and for splifs and giggles, imma try thru twrp, replacing recovery.img with twrp, vbmeta blanked then go into service file and flanh file and change the md5, what could go wrong?

Let us know how that worked out I have Moto one 5ga's with Comcast, mine is also rooted.

Question Any Tmo 2117 users try or use Lineage?

The 2117 model is not mentioned in official compatibility, but all the others are. Any Tmobile users running Lineage or know if it works?

I used it for a bit. Works good as any other device IMO.
Follow This guide on the official page.

Im just iffy on the whole thing- Still on A11 OOS11 and Im hearing Ill possibly need A12 firmware as a base before install? I cant just use TWRP and flash? Its been ages since I went custom (HTC One Cyanogen with CWM, I believe we were able to use TWRP as well back then) and it sounds like you need Lineage Recovery?
Can I follow that guide straight from rooted *BL unlocked A11 OOS11? No updates have been applied to my phone afaik. Disabled right away.

TimmyP said:
Im just iffy on the whole thing- Still on A11 OOS11 and Im hearing Ill possibly need A12 firmware as a base before install? I cant just use TWRP and flash? Its been ages since I went custom (HTC One Cyanogen with CWM, I believe we were able to use TWRP as well back then) and it sounds like you need Lineage Recovery?
Can I follow that guide straight from rooted *BL unlocked A11 OOS11? No updates have been applied to my phone afaik. Disabled right away.
Click to expand...
Click to collapse
Lineage updates the firmware as part of the install.

Ah thank you! Ill prolly do it after some time. I'm completely happy on 11 for now. Have it debloated and set up with xposed modules and everything.

I've used lineage before on the le2117 but decided to switch to evolution x since it's packed with features

What the battery life like between the two? I dont necessarily need features since I add everything I need with magisk\lsposed. This stock rooted rom Im on now is getting great battery life.

On both installation pages for this and EvoX, it says you need to be on A13 firmware. Is this a hard requirement? Or can I truly just flash my phone as it is currently? Stock root, A11, OOS11?
I cant do OTA updates, nor can I install downloaded updates (via the settings app) either because I converted, or its Magisk or something...
How did you get you Tmos to 13? Were you already updated before rooting? Did the OTA work after root for you? I just get install failed immediately with the downloaded package.
Any input would be appreciated Im in no rush, and I already have a backup setup for after conversion (assuming Migrate works on this phone, seems to so far).

OnePlus 8T installed OOS13 but failed to launch

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.