Database Users

[Q] Can't update after deleting stock apps

I've been trying to update from 4.1.2 to 4.2.2, but I deleted some stock apps and now the update is failing. I've tried flashing it manually and OTA, and various other things, but nothing has helped so far. Has anyone else had this problem?

The OTAs are for use with [size=+2]unmodified[/size] factory ROMs.

bftb0 said:
The OTAs are for use with [size=+2]unmodified[/size] factory ROMs.
Click to expand...
Click to collapse
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.

wipeout4wh said:
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
Click to expand...
Click to collapse
My post tells you that you have the wrong expectation about what OTAs are capable of... and that you are probably the 200'th dude to come in here and say
"Wahhh! The OTA doesn't work on my heavily modified stock ROM!".
If you want it to work without exerting any mental effort, return the /system, boot, and recovery partitions back to 100% pure stock corresponding to whatever release your original ROM was based upon, and run the update. Then re-flash your recovery and re-perform all your /system mods, starting with a flash of the same root kit you started with.
Note that the the update you are contemplating also includes a bootloader update - performed the safest way possible (signature checking performed by the existing boot loader). Doing it the manual way (via fastboot) is quite dangerous, even for experts. If you have a 3g version there is also a radio update which also should not be attempted in any other way than via a pure stock OTA install including use of a stock recovery.
Make a full Nandroid backup before you begin anything - and get a copy of that backup off of the tablet as well as a failsafe measure. If you screw things up moving forward, at least you will be able to start over from where you are right now.
If you have been operating using best practices, you should already have a nandroid backup of the pure-stock /system & boot images. TWRP allows you selectively restore individual partitions. Few users seem to know how to actually make a backup of stock recovery partitions, but you can get that out of oldblue910's archive site - find the link in the OTA thread.
good luck

wipeout4wh said:
I figured that out when I tried to update. I can't flash it either, so your post doesn't really help.
Click to expand...
Click to collapse
He's telling you the plain and simple truth. Want the OTA- as it stands, you're out of luck. Either return to stock and then flash the OTA, or flash the 4.2.2 factory image. That's it. Nothing more. That anyone even bothered to answer this uselessly redundant thread is a miracle in and of itself.
Sent from my Nexus 7 using Tapatalk HD

[SOLVED] Cascading failures leading to bootloop and softbrick

Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.

Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.

Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.

93-14 hasn't been leaked yet. So you'll be stuck for now.

Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.

pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.

Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?

pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.

I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.

jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:

While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what

Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.

Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.

How do I fix a bootloop?

The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.

Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!

SmilingPerson said:
The phone is a Moto g7, Verizon river xt1962-1, rooted with Magisk and TWRP.
I wanted to update to Magisk 19.4, so I made a TWRP backup and ran the unroot patch and went back to 19.3, but I still had the problem, so I decided to restore from the backup. After the backup, I am stuck in a bootloop, the whole "Your device is unlocked and cannot be trusted" screen over and over. I can get into TWRP, but no backup that I have tried will fix the boot loop. I tried a few things that just seemed obvious to me, clearing the cache and whatnot, but I am still stuck. I have adb and fastboot at the ready, but I don't know where to go from here.
I do not even know what build I am running, I cannot get into System / About to see, and I am not savvy enough to know any other way to find out. I know that it was current stock, missing only the most recent patches.
Is there a way that I can restore my phone? I would be grateful for any help. Damn, I love this g7 so much more than the Note phones that I had been using for years, but I was at least a little familiar with them. Thanks for any help.
Click to expand...
Click to collapse
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img

WoKoschekk said:
Try to flash the stock boot.img and you'll be fine. If you haven't got a stock boot.img you will find a backup of it in your /data partition (magisk does a backup of it by default). Just unpack the TWRP backup of your /data or download the latest firmware to get a boot.img
Click to expand...
Click to collapse
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud ?

zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.

zenful said:
Sounds like you'll need to fastboot flash a stock rom to your phone, use TWRP to get into the bootloader/fastboot mode, and also sounds like you messed up the boot.img when you were trying to go through that process. I just updated the Magisk app from within the app itself - no issues there. Might be a good time to update to a newer stock rom as well, might as well take advantage of the situation amirite?
But just for different options, here may be some useful links
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
idk about this one but looks like it may help
https://forum.xda-developers.com/moto-g7/how-to/how-to-fix-g7-xt1962-1-stuck-bootloader-t3917792
this next one has the flashboot commands you'd need to also update your ROM
https://forum.xda-developers.com/moto-g7/how-to/moto-g7-xt1962-1-riverretail9-0ppos29-t3969067
Keep in mind, I haven't used either one of the methods in either links and I am not responsible for anything that occurs from your actions.
Anyways, good luck!
Click to expand...
Click to collapse
Thanks man, I really appreciate it! I did take advantage of the opportunity to update, something that had been bugging me for a while anyway.
I had updated Magisk to the beta through Manager, but a problem came up and I needed to step back to the stable version. That was where I messed up.
In a way though, it was just as well, since it forced me to spend a little time reading about the G7 ecosystem, something I really hadn't done much of yet. It used to be fun keeping up and flashing nightlies, etc, but over the past few years, it has got away from me. If it wasn't for a few specific things, I would almost stay stock. But I get uncomfortable thinking about the ridiculous amount of personal information a stock phone releases about us, so things like Signal and xPrivacylua are important to my sense of well being. Even if some of it is placebo.

SmilingPerson said:
Mate, I can't thank you enough, now I am back up.
I took advantage of the oppotunity to do a Titanium backup and flash the latest firmware, since I was still running old security updates.
I am not sure why the TWRP backups caused a bootloop, that concerns me. I am diligent about making one before any significant change, and now I see that none of them were good. It might be that the backup I applied included boot, and somehow that caused an issue.
In any case though, thanks a million. I would PM you a beer, but they tend to go flat when they hit the first ATM gateway. Hops and TCP encapsulation don't seem to be compatible, especially at > 9600 baud
Click to expand...
Click to collapse
I'm glad to hear that! Don't worry about the beer!
I had similar issues with my Moto g6+... Either the /data encryption or Magisk is the reason for a failed backup. Both can cause a bootloop. But it's always good to have a stock boot.img.

I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?

arkansawdave74 said:
I'm reading this because of the same issue in a Moto G7 Power. I haven't been able to make it restore a backup at all of either stock or custom. Oh, it will restore it just won't boot. I think it has something to do with the A&B system slots. We use a TWRP that was made for system with A&B slots but then we flash a copy partition zip That I'm not sure what it does. Maybe I should take it apart and have a look. . Has anyone been able to restore a backup in the G7?
Click to expand...
Click to collapse
Do a full restore of boot, system and data.
Is data...
...encrypted => Then format data (not wipe!!) and reboot into system. When you see the "Welcome Screen" turn off your device and boot into TWRP again. Restore data and it should be fine.
...unencrypted => Then format data and restore data (w/o reboot!!)

Wifi/bluetooth keep trying to turn on but fail everytime.

When I try to enable wifi (or bluetooth), it says 'Turning on...' underneath the icon but the process never succeeds.
Note:
-Under About > Status I see no MAC address for Wifi or Bluetooth.
-Phone is not rooted.
-Bootloader is unlocked.
-No custom recovery.
-Airplane mode is off.
-I am able to access the internet when I put in my SIM card and use my cellular data.
-EDIT: Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
-EDIT: I keep my SIM out of this phone (it's in my fully working phone). Can insert if need be.
My attempts to solve this issue (none have worked):
-I updated to OxygenOS 11.
-I booted into recovery and wiped everything, including cache. I also did a System Reset.
-I went to Settings > System > Reset Wifi, mobile and Bluetooth. I also did Erase all data (factory reset) in the same place.
Is there anything else left to try? Is there a way to flash the modem image maybe, I remember having to do that with my Nexus 4 many years ago.
Thanks!

A factory reset never finds the root cause. A virus or an old load are the only reasons to use it otherwise find the root cause. Usually a bad setting. If it's software caused the solution is right in front of you.
Network reset, worth a shot.
Clear system cache, can't hurt.
Clear data in sim card tool kit apk.
Both are probably redundant since you already did a hard reset, but try anyway.
Otherwise...
Bad sim card (try reseating it or replace otherwise) , corrupted firmware, or defective hardware.

Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.

dladz said:
Which phone do you have? I've seen this when a user has had a Chinese version and converted to global then when they updated to 11 it all went wrong.
If you're not using a converted Chinese phone then it could very well be your boot image. Extract it using payload then flash it.
If not that then MSM restore your current firmware.
Click to expand...
Click to collapse
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.

bassamanator said:
Sorry, what is **MSM** restore?
Under About phone the Model is listed as IN2025. The Build number is Oxygen OS 11.0.2.2.IN11AA.
So I extracted all the images(?) using payload and very foolishly decided to
Code:
fastboot flash modem modem.img
The phone doesn't boot up anymore/remains stuck in loading phase (spinner...). I did a
Code:
fastboot flash boot boot.img
+ wipe + factory reset but still stuck in loading phase.
Any ideas as to how I can fix my mistake?
I appreciate all your help guys.
Click to expand...
Click to collapse
Ah yea that's not good. 2025 AFAIK is global mainly sold in the US.
The MSM tool is in discussion I believe and it's a tool you use to restore your phone using EDL mode, to get to EDL.
Power off your phone.
Connect it to your computer (if it turns on again turn it back off)
Then open up the MSM tool and press and hold volume up and down
Your computer will recognise the the device and at this point you should start the process as it will try again to reboot shortly after without any input from you.
This is the thread you need.
[OP8PRO][OOS 11AA/BA/DA] 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
Bare in mind this will relock your bootloader but it's easy to get that back unlocked.
Any questions regarding the tool just ask in the thread.
(you shouldn't need to providing you download the right one)
Download the latest firmware within the tool. If you get stuck don't just guess, ask someone.

@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.

So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?

bassamanator said:
So I flashed OnePlus8ProOxygen_15.O.32_OTA_0320. No wifi. I extracted the boot.img and then flashed it via fastboot. Still no wifi.
Anything else that I can try?
I guess this is a hardware problem?
Click to expand...
Click to collapse
But now you have bt?

blackhawk said:
But now you have bt?
Click to expand...
Click to collapse
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.

bassamanator said:
No bluetooth either. Same exact issue as with the Wifi, it says Turning on... then it doesn't.
Click to expand...
Click to collapse
How/when did it start? Anything happen to the phone?

bassamanator said:
@dladz
So I've managed to unbrick the phone using that tool. Thanks.
I'm going to install the latest oxygenos again, extract the boot.img from that zip, and flash it again as per your recommendation.
Click to expand...
Click to collapse
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com

blackhawk said:
How/when did it start? Anything happen to the phone?
Click to expand...
Click to collapse
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.

bassamanator said:
I got the phone used right before Christmas. It still had the protective plastic on it until I removed it today. It really is in mint condition (or looks to be). I've been away and finally got around to moving things over from my old oneplus 3T.
It's certainly possible that I bought a lemon but at this point I'd like to just fix it if I can.
Click to expand...
Click to collapse
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device

dladz said:
So if you've used that tool then it'll have relocked your bootloader.
Did you unlock it again? AFAIK you can't flash another boot image unless you unlock it again.
The only other thing i can recommend (if you really don't want to RMA)
Would be to downgrade to 10 but in all fairness that really shouldn't even be an option at this point, you've flashed a clean OS back as oxygen would have, you've updated via the official OTA route.
No I think it's time to contact OnePlus for an RMA.
Unless someone else had seen this issue personally I haven't.
Had you rooted in the past btw? Flashed many magisk modules??
I find it highly unlikely that they could survive this but you could potentially try the magisk removal command, can never remember it it's in my payload dumper guide.
If no one else chimes in I'd say it's an RMA, I've not seen it before, it's strange.
Also (and please don't put it on here) but is your IMEI missing too?
This could be your EFS partition if so.
Edit: found this super old thread for the OnePlus one, same issue.
I think this is fixable, potentially remotely from OnePlus and or anyone else who has access to the updated tool, might be worth mentioning in the MSM thread if you haven't already.
PS: don't follow the guide in the link btw it's for the 1+1 lol, in just putting it here as a reference
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
EDIT: the phone has 2 IMEI numbers.

bassamanator said:
Yes I had to oem unlock again.
As far as I know the phone was not rooted but it's a used phone. Superficially it's in mint condition, I just removed the plastic film just earlier. I'll post in the MSM thread and checkout the new one you posted.
Click to expand...
Click to collapse
I've already posted in the MSM thread for you.
What about your fingerprint? Is that still working?

dladz said:
I think it's fixable now I really do
From what I've been reading I think it's a mixture of partitions that have been borked z namely the EFS and potentially the persist.img partition if the same position structure exists that did back in the day.
With that in mind are you able to use your fingerprint? I only ask as persist is linked to it so if that's not working then we may have a correlation between problems.
If it is then it's a ? Over the theory.
I'll keep reading but from what I can gather it seems that EFS and persist at least were linked, can't be sure if they are this point.
Have a look at that link I sent see if anything raises a flag for you, bare in mind it's for an older device
Click to expand...
Click to collapse
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?

bassamanator said:
So I've never registered my fingerprint on a smartphone, ever, but I thought I would register one of my toes just to figure this thing out. When I get to the Fingerprint Setup screen I get the following error: Enrollment was not completed. Fingerprint registration error, please try again.
Does this help narrow down the issue?
Click to expand...
Click to collapse
Yea for me it does, it shows there's a correlation between the persist problem and the EFS problem and a direct connection to your IMEI or Mac address issue.
With this in mind I would recommend the persist.img fix thread..
Getting that working may be key to solving the Mac / IMEI problem.
At this point nothing is going to hurt.

Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.

dladz said:
Here is the thread you'll need.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Now I have not been through this but again it can't hurt at this point.
Click to expand...
Click to collapse
I was about to say, I want to try something along the lines of
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
Click to expand...
Click to collapse
or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.

bassamanator said:
I was about to say, I want to try something along the lines of or something along those lines from this post https://forums.oneplus.com/threads/no-imei-and-no-efs-backup.322534/page-4#post-14545355 on that old oneplus forum thread you posted.
I'll try the new link you posted instead though.
IMEI is fine btw, the phone dials and connects just fine to cellular.
Click to expand...
Click to collapse
Ok don't do the EFS fix you do not have an EFS back up.
Give this a shot
go to data/misc/wifi (required root)
-backup file wpa_supplicant.conf in this folder which contains usename and password wifi
- delete all file in this folder
- turn on wifi ( if you careful, you can reboot )
- now you can connect to wifi
- recovery file wpa_supplicant.conf
This isn't my writing. The English is a little broken but you get the point

Patched 11.0.12.12.KB05AA ROM for rooted users - install from Fastbootd!!!

[UPDATE]:
**********
I got sick of my phone telling me I needed to update but I couldn't because I'm rooted. So finally got around to patching the last full ROM today w/ the incremental.
This is the fastbootd w/ flash_all.bat script to update to 11.0.12.12.KB05AA. The package for KB05AA (Global/US) is not yet available, hence I'm still making it available here. Be sure to alter the flash script (remove the "rem" before boot.img and recovery.img if you DO NOT want to keep your custom kernel + TWRP) ****************
3.14 GB file on MEGA
mega.nz
THIS IS ONLY FOR 11.0.9.9.KB05AA, BUT READ IT ANYWAY!!!!: ***************
I think this is the first time anyone has actually made a working incremental update for a rooted OOS device, or any with a payload.bin update method that I know of. This method doesn't require any wiping and TWRP / rooted boot.img / custom OOS kernel can be installed right after the script finishes (or left on the device), and you don't even change your active slot (usually, incremental updates will flash to the inactive slot).
I won't get into that many specifics except it was EXTREMELY DIFFICULT, but it works now. Read here if you want to do it yourself in the future, or on another phone. Should work on just about any phone that uses payload.bin files https://forum.xda-developers.com/t/...11-0-9-9-kb05aa-posted.4314677/#post-85425949
You may have to edit the .bat file to pick your RAM type (the lp5 ones are for devices with LPDDR5; it is preset for most of the phones using the LPDDR4 RAM). On the Op8T at least you can do this from adb shell:
adb shell getprop ro.boot.ddr_type; where a 0 is LPDDR4 and 1 is LPDDR5 ram. If it's 1 returned, you need to flash the lp5 files instead of the same named otherwise files in the .bat file (so edit it).
That weird -cow stuff is temp files that prevented the update from working. Not documented anywhere I could find (well, minimally explained by Google), took hours to figure out they were filling the super partition up. I had to re-engineer a Linux project (linked above) to get this working, and have officially updated from 11.0.8.13 to 11.0.9.9 COMPLETELY now. While rooted, without switching slots, and TWRP installed.
You just have to ensure you're on the latest ADB and Fastboot tools and an adb reboot bootloader, followed by a fastboot reboot fastboot should get you there. You can check with: fastboot getvar is-userspace
If it says yes, you're in fastbootd. It actually will work with TWRP installed, I found out later, as long as you reboot in TWRP to fastboot and confirm with the command above you're in fastbootd.
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/tag/v1.7 has a script that will get you the Latest ADB and Fastboot and put it in a folder for you.
I uploaded it to Mega. Just use some common sense and look at the flash_all.bat file before flashing. I'd write more but I'm tired as hell from getting this working. Now we'll never have to wait for an incremental update while rooted again, at least in the foreseeable future.

I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145

g96818 said:
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
Click to expand...
Click to collapse
That never worked for me and others, Always resulted in either bootloop or booting back to previous build

nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.

g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....

nujackk said:
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
Click to expand...
Click to collapse
It's good that you found a band-aid fix.

nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
Of course I tried that solution first, it didn't work on my device.
I'm glad it did on others' devices, kudos to you for posting it (and I DO appreciate your work), but this is the only one that worked on mine. Why? Who knows. I also followed another guide that didn't work. Or else I wouldn't have wasted all my time making this (it took many, many hours to assemble). I'm not saying it's the best solution (I really hope someone just uses what I put in the other thread and assembles it into an easier format for others to use), but I have a full time job (2 actually) so I can't work on it anymore. But it works, no data loss, and TWRP can be installed. Until the next incremental update comes out, then I'll post another version using the tools I used for this, if your build doesn't work on my device. But only when I have the time...

g96818 said:
It's good that you found a band-aid fix.
Click to expand...
Click to collapse
LoL band-aid fix... Call it whatever you want, it works.
It's actually a patched 11.0.8.3.KB05AA with the incremental update applied to it for 11.0.9.9.KB05AA. So it flashes to the active slot and TWRP / rooted custom kernel can all be installed at the same time, even while you are still rooted with Magisk, and even if TWRP is installed. No data loss. I never claimed perfection on this project, just that it works for me.
Keep doing what you're doing, I'll keep doing what I'm doing. We both just aim to help others anyway. I just couldn't get any other method to work so I came up with this one, extending on the incomplete / abandoned work of others. I didn't come up with Payload extraction. Never claimed to. I didn't come up with fastbootd flashing either.
All the forked and modified code is at my GitHub repo. The fork goes back to several other devs' forks (mine is the 3rd modified fork).

Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.

mslezak said:
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
Click to expand...
Click to collapse
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot

5star02707 said:
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
Click to expand...
Click to collapse
I think maybe you misunderstood what I did in this thread. I patched a full ROM with the incremental update of 11.0.9.9.KB05AA. So while OnePlus does not have a full ROM available for download (yet), it is available for download here.
Yeah the method you propose is the "normal" rooted way, but if you're rooted already it forces you to full ROMs not OTAs. You'll be on 11.0.8.3.KB05AA. The goal here is to get on 11.0.10.10.KB05AA (someone NOT ROOTED could download the OTA update using Oxygen Updater and upload it here so I could make a patched version for those that want to keep their root / custom kernel / TWRP / etc and avoid the hassle of unrooting first, which wipes your data partition). At least my Oxygen Updater won't let me download incremental updates even with Magisk Images removed (don't try this unless you're on Op8 / Op8 Pro; some people are having big system update issues on Op8T incremental hence why this thread exists.) It jacked up my system pretty bad (Magisk images removed, Settings / System / System Updates method) until after a boot.img and super restore from TWRP. Not all devices were setup the same (mine is a US carrier converted to US KB05AA). To my knowledge, no direct download has been posted for KB05AA incremental update. Here or on TG. If you have found one, please post a link here. The only one out I've seen works on European ROMs. OnePlus always does KB05AA last for whatever reason.

11.0.10.10.KB05AA posted with caveats - please back up your data as suggested in case the Phone Services APK doesn't fix your SIM after a flash, and you end up formatting the data partition. You may want to try some other methods or just plan on restoring (not with TWRP Alpha in my experience).

mslezak said:
Guys, bad news. So 11.0.10.10.KB05AA incremental does something to the data partition and kills your SIM access.
...
Click to expand...
Click to collapse
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).

BillGoss said:
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
Click to expand...
Click to collapse
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.

@mslezak, When I get an update I:
- use a terminal session (you could also use ADB) to restore the stock boot and recovery (this way I don't lose root yet)
- install the update but don't reboot
- copy the new boot image and patch it
- turn on airplane mode (to avoid SafetyNet and certification issues in the next step)
- reboot the phone and the updated system comes up
- flash the patched boot image and TWRP in fastboot/bootloader
- reboot and disable airplane mode
This is basically @osm0sis' process from https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
No, I'm not saying flash to both slots, because that will make it impossible to fall back to the current system if the update fails (though this is meaningless if you're manually flashing partitions).
I've got into the habit of syncing active to inactive (after I'm happy with the update) simply because it's required when going from OOS to a custom ROM (I use a shell script based on the LineageOS sync zip). And, after the sync, I can now access the data partition from the inactive slot (which wasn't the case just after the update due to the different keys).

mslezak said:
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
Click to expand...
Click to collapse
Thats not very hacked/hacked at all, and quite a few use that setup

xstefen said:
Thats not very hacked/hacked at all, and quite a few use that setup
Click to expand...
Click to collapse
LoL I gave up fastbootd flashed to 11.0.10.10.KB05AA and formatted data, let Google download everything it backed up, and am back in business. Just have a lot of apps to login to / Magisk modules to add / etc.
So yeah my patched 11.0.10.10.KB05AA works but the data must be formatted or the SIM doesn't work (at least for me; I don't know if anyone else has tried it since I just posted it a few hours ago; it could be that it works for some without causing issues, I don't have any idea). The goal was to not have to mess up the data partition.... but I can't control what OnePlus does in their updates... Try what worked for others posted here first I'd suggest, or just make solid backups of everything knowing you're going to likely need to reinstall / re-login to everything and format the data partition. New pin, new fingerprint, etc. Re-login to your wifi blah blah.
It's still a full unreleased ROM so I posted it for those that don't mind taking backups (outside of TWRP) if they want to keep root & TWRP on the new release... Yeah a pain to setup if you aren't warned to use another backup method (maybe there is a better backup method, maybe Migrate (app store early access) is developed enough for easy transfer now, I know many people said it worked well in the past but haven't been following the updates. Still free).

It dawned on me later that since the only thing that didn't work using this method going from 11.0.9.9.KB05AA to 11.0.10.10.KB05AA was phone services, that I should just include the working version in this post. Since I already did it the hard way and restored everything back to normal. AS I SAID ABOVE, IF PHONE SERVICES ISN'T ENOUGH TO FIX THE ISSUE, PM ME AND I CAN EXTRACT MORE RELATED FILES UNTIL IT WORKS AGAIN. Unfortunately, I can't just downgrade to 11.0.9.9.KB05AA and keep trying fastbootd over and over again as I don't have the time.

g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
The whole point of this is to AVOID the unbrick tool, reinstalling an outdated version, updating each new ROM build since the brick tool was made, and starting over clean. I think... Have a hunch at least we're almost there on 11.0.10.10.KB05AA with an APK install... Although just backing up everything first will always work (if you don't mind formatting your data partition) just as it's posted here already. Always an issue for us rooted users (especially on Global) since we're always last in line to get a full ROM. This IS a full ROM, payload extracted and patched with incremental updates. Still not available from OnePlus Global (KB05AA) as I checked today, so still relevant.

Ladies and Gents,
I have removed some off topic posts from this thread because I believe we could express the same meaning in more civil words. Please try to do that from now on.
Thanks.
Jerry
FSM