Database Users

Convert Canadian 6045i to US 6045i with all updates (performance, stagefright, etc).

Be very careful doing this, you could brick your phone if you aren't - you have been warned.​
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware - it is also the same as your device ID if you type 'adb devices' with your phone hooked up with USB debugging enabled for adb commands.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!​

To save you some pain you can more thank likely flash the system image and boot without wiping your /data.....if for some reason you ran into issues you'd still be able to go into factory recovery and do a reset which deletes data.
Also to anyone who actually uses AVG the pro version is free on amazon appstore today only.
Also you don't have to INSTALL twrp...you can opt to only boot into it using the instructions in the system image thread if you prefer to keep stock recovery.
If I had to bet I'd say you'll get the USA notifications but we will find out on next update.

famewolf said:
To save you some pain you can more thank likely flash the system image and boot without wiping your /data.....if for some reason you ran into issues you'd still be able to go into factory recovery and do a reset which deletes data.
...
Also you don't have to INSTALL twrp...you can opt to only boot into it using the instructions in the system image thread if you prefer to keep stock recovery.
Click to expand...
Click to collapse
Totally correct on the TWRP thing, though I prefer it to stock recovery, and updates work just fine with TWRP as well.
As for the not wiping - again, correct, I just come from the 'do a total wipe' school of flashing things, to avoid any possible weirdness

purple.epod said:
Be very careful doing this, you could brick your phone if you aren't - you have been warned.​
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!​
Click to expand...
Click to collapse
When restoring the UE40 firmware the first time you go into system update checker you need to delete the existing UE40 update as it kept it around...you should then be able to check updates as normal.

Manually update
At the end of your post, you say that you update manually.. where do you get your update ?

Manually update
At the end of your post, you say that you update manually.. where do you get your update ?
Click to expand...
Click to collapse
I mean that when the next update comes out, if I can't use the OTA update, I'll wait for someone to upload it here, and then I'll manually apply it. If you follow the directions in my post, you'll be totally up-to-date as of August 15th, 2015 - I'm referring to the next update, whenever that may be.

Thanks for the guide!
Was able to update my Canadian idol 3 without installing twrp
Just fastbooted into it and did a backup of my old CDN setup and restored with the file above the whole update process took about 15min
If **** hits the fan I can still restore back to the original CDN ROM with twrp and my backup.
Dt2w works every time now and chrome scrolling is vastly improved definately worth updating. I may flash back to Canadian system image when they finally release it

To anyone on stock Canadian firmware please post once an OTA is available (and what carrier you are on)

anyone else have lost LTE and get bad network speeds after converting? I had 60mbps with canadian firmware and now i get around 5mbps and lots of network drops.

jpfk said:
anyone else have lost LTE and get bad network speeds after converting? I had 60mbps with canadian firmware and now i get around 5mbps and lots of network drops.
Click to expand...
Click to collapse
I'm not in canada but I would think if more folks were experiencing issues like that they would have mentioned them here already. Did you do a factory reset and start clean or did you keep your previous data around after changing firmware? In this case I'd really recommend starting clean with the exception of using tools like Titanium Backup to backup all your user apps+ their data (or you can use Helium if you don't have root).

famewolf said:
I'm not in canada but I would think if more folks were experiencing issues like that they would have mentioned them here already. Did you do a factory reset and start clean or did you keep your previous data around after changing firmware? In this case I'd really recommend starting clean with the exception of using tools like Titanium Backup to backup all your user apps+ their data (or you can use Helium if you don't have root).
Click to expand...
Click to collapse
I had cleared the cache and did a factory reset only after i confirmed the flash of the US firmware was ok. (i have a really bad SD card which keeps unmounting and didnt want to risk being stuck with a non-functional device). In addition to the network problems i also still had the performance issues everyone mentionned was fixed in latest update. I just did a complete wipe and flashed the US again, now the performance is much much better but i still get only H+ with about 7mbps instead of LTE. But the good thing is the drops seems to have stopped.

jpfk said:
I had cleared the cache and did a factory reset only after i confirmed the flash of the US firmware was ok. (i have a really bad SD card which keeps unmounting and didnt want to risk being stuck with a non-functional device). In addition to the network problems i also still had the performance issues everyone mentionned was fixed in latest update. I just did a complete wipe and flashed the US again, now the performance is much much better but i still get only H+ with about 7mbps instead of LTE. But the good thing is the drops seems to have stopped.
Click to expand...
Click to collapse
you probably tried this but... check that the APN didn't get changed/reset from when lte was working.

That was actually the problem, i did not realize it was a different APN for LTE so it looked normal when I first checked. Thank you very much

Has anyone gotten the Canadian stagefright update pushed to their phone yet?

doesn't work for me!
purple.epod said:
Be very careful doing this, you could brick your phone if you aren't - you have been warned.​
Okay, so, us Idol 3 users in Canada are stuck waiting for Alcatel to have any updates blessed by our cell carrier (Bell/Virgin, Telus/Koodo) before we're "allowed" to get them. And as we all know, Canadian cell carriers aren't exactly prompt about this sort of thing. So what's an enterprising XDA user to do, then? Why, convert your device to a US model, of course!
Step 1: Install TWRP
That can be done with this thread here, courtesy of @DallasCZ
Step 2: Download the latest US firmware
That can be done by downloading this file here, courtesy of @famewolf
Step 3: Flashing
Okay, so first, BACK UP YOUR EXISTING FIRMWARE. Take a system image, or nandroid, as your choice may be. Be sure to back up the boot partition as well, in case you ever want to go back to stock Canadian firmware! Then, do the following:
Decompress the US firmware
Copy the decompressed 1970-01-22--16-43-23_LRX22G_release-keys folder into your TWRP/Backups/XXXXX/ folder on your External SD card or USB-OTG storage, where XXXXX is your device ID assigned by TWRP when you backed up your existing firmware - it is also the same as your device ID if you type 'adb devices' with your phone hooked up with USB debugging enabled for adb commands.
Wipe everything *but* External SD and USB-OTG in TWRP. (This entire wipe may not be needed, but as @KashRaman pointed out, if you don't at least wipe cache, you could have issues after flashing the new firmware)
DO NOT REBOOT - go back, and select Restore in TWRP. Pick the US firmware backup.
Flash *both* the boot and system image.
Reboot System. If your phone does the same as mine, it will seem to get stuck on the 'Alcatel/Smart Move' animation. Hold power until the phone turns off, then turn it back on. It should quickly go to 'Upgrading Android'.
You're done! Set up your device, and feel free to install SuperSU, remove bloatware (AVG? Ugh), etc.
I didn't even need to add APN info for Virgin Mobile, it already set up the Bell Canada APN - worked right away out of the box.
One comment to note - I do not know that a Canadian device converted to a US one can get OTA updates, as I believe Alcatel uses some sort of IMEI identification to see what OTA ought to be passed to a device, but I'm unable to confirm this. Of course, I'm personally fine with just manually updating when need be, but that's up to you to decide if you are as well.
AS ALWAYS, BE CAREFUL, DO THIS PROCESS AT YOUR OWN RISK
Don't forget to thank @DallasCZ and @famewolf for their posts/uploads making this possible!​
Click to expand...
Click to collapse
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread http://forum.xda-developers.com/idol...dates-t3163745
I also have the twrp-2.8.7.0-idol3 installed on my phone.
I also followed this thread
to find the way to install that ROM, without success. i also installed the root from the zip file in the twrp, but again without success!! but when i open from the twrp the directory TWRP/Backups/XXXXX/ and i copy the .win and the .win.md5 files the phone doesn't see the when i click restore

i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread
Click to expand...
Click to collapse
This guide is for converting a Canadian 6045i to a US 6045i - both are identical models with simply slightly different software. It won't work with a European 'Y' model like you said you have.

punkal said:
i downloaded the zip restore file for my phone (Model: 6045Y(Europe) Firmware: 5.0.2-010 06) from this thread http://forum.xda-developers.com/idol...dates-t3163745
I also have the twrp-2.8.7.0-idol3 installed on my phone.
I also followed this thread
to find the way to install that ROM, without success. i also installed the root from the zip file in the twrp, but again without success!! but when i open from the twrp the directory TWRP/Backups/XXXXX/ and i copy the .win and the .win.md5 files the phone doesn't see the when i click restore
Click to expand...
Click to collapse
Step 1) Make a backup on the device so it creates the directory path you need.
Step 2) Take the time datestamp folder from the backup you have and put it in the folder that has the other time datestamp folders. It's not a complicated process. Installing the "root" from the zip file does you no good because the time datestamp folders need to be under a folder with your device id (ie what shows up when you do adb devices).
While the restore process IS the same your questions should be asked in the system image thread if you don't have a 6045i.
According to @petrov.0 it's better for you to install the official 10 06 update (or his modified one in the system image thread) as it updates files in SEVERAL partitions other than system and boot. Again discussion needs to be there.
Apologies to @purple.epod. This will hopefully redirect folks back to the system image thread. I have a line that states to follow your restore tutorial but use their own backup but did not intend for them to be asking questions HERE.

purple.epod said:
This guide is for converting a Canadian 6045i to a US 6045i - both are identical models with simply slightly different software. It won't work with a European 'Y' model like you said you have.
Click to expand...
Click to collapse
Now i understand why it doesn't work. And where can i find the rom for my as i have everything wiped? do you know i only found ROM Arde-Dev-Team-v1_5.0.2 but it doesn't work!
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
famewolf said:
Step 1) Make a backup on the device so it creates the directory path you need.
Apologies to @purple.epod. This will hopefully redirect folks back to the system image thread. I have a line that states to follow your restore tutorial but use their own backup but did not intend for them to be asking questions HERE.
Click to expand...
Click to collapse
Unfortunately i can bakup anything as i have wiped everything on the phone!:crying:
I know i'm really stupid, but i do that as it was a step as a process of installing a new ROM as mine was corrupted!:crying:

punkal said:
Now i understand why it doesn't work. And where can i find the rom for my as i have everything wiped? do you know i only found ROM Arde-Dev-Team-v1_5.0.2 but it doesn't work!
---------- Post added at 11:44 AM ---------- Previous post was at 11:40 AM ----------
Unfortunately i can bakup anything as i have wiped everything on the phone!:crying:
I know i'm really stupid, but i do that as it was a step as a process of installing a new ROM as mine was corrupted!:crying:
Click to expand...
Click to collapse
Why are you posting this HERE when even the message you quoted states questions should be asked in the system image thread?

famewolf said:
Why are you posting this HERE when even the message you quoted states questions should be asked in the system image thread?
Click to expand...
Click to collapse
Really sorry!
i've been taken by terror and panic.!

Almost Full Nougat TWRP flashable zip

I say ALMOST because you must have either used the manual (adb) method to upgrade to Nougat, or flashed the v30b_update.zip to use this. If you are on MM, this will more than likely brick your phone.
OK, so after testing, here is the complete Nougat zip. It is every partition from the v30b KDZ except boot, system, and recovery (obviously), so you keep TWRP. This has the modem, tz, and rpm partitions. If you flashed the other zips that I posted with the individual partitions, no worries, reflashing them does not hurt anything, and I am not going to make yet another zip. Some people may want to just flash the minimal needed to get to Nougat so they can restore MM TWRP backups if they need / feel like it.
You can dirty flash this on top of my v30b_update.zip, but you are better off doing a factory reset (full wipe). I could have included the wipe in the zip, but this way -- YOU can decide.
Also, you MUST have an H901. Not an H900, not an F600, not a BMW, or Audi, or Toyota. Again, if you have anything other than an H901, this will brick your phone.
This fixes the front facing camera issue with 4x3 5mp (it was the aboot partition that solved that FYI). Can't say what else it may have fixed that I didn't even know was broken. I also can't say what functionality may be LOST -- that is why I am posting this.
If you flash this, and suddenly something doesn't work that used to, please post in this thread. Same goes if something suddenly STARTS working.
Download here
SHA1: b1ac20a6eaccf2dfbd22c09886ddcd03ab638ec3
If you want to be able to revert to MM, then you need to make a FULL backup of your phone, and I don't mean with TWRP.
* adb reboot recovery
* adb shell
# this will give you a list of all the partitions
* ls /dev/block/bootdevice/by-name
* exit
# You then need to backup all the partitions
* adb pull /dev/block/bootdevice/by-name/<just go through them in order> <name of partiton>.img
# example
* adb pull /dev/block/bootdevice/by-name/aboot aboot.img
* adb pull /dev/block/bootdevice/by-name/modemst1 modemst1.img
# do this for EVERY partition
# you will need 64gigs of space on your PC to hold everything even if the phone is empty since dd stores zeros.
# Now, if you ever want to revert, you do the reverse, and just flash each one of these with dd and you will be right back to where you are.
-- Brian

reserved

reserved #2

Awesome!! full Naugat... so when is debloated version coming? I tried to debloat, but even removing non essential T-Mobile apps gives me bootlloop, or if you can tell me which apps are safe to remove will be a huge help ...
Thanks for you work man only active developer for H901, and I know you have allot on your plate but you are our only hope... Cheers!!

A full debloat is a very tedious process, so it is bottom of the barrel. If someone else doesn't jump in, I will eventually release one though.
-- Brian

Thanks again! Just installed. Tested the only thing I encountered on the update.zip and it is confirmed fixed with this.
Keep up the good work! :thumbup:
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
zeexhan said:
Awesome!! full Naugat... so when is debloated version coming? I tried to debloat, but even removing non essential T-Mobile apps gives me bootlloop, or if you can tell me which apps are safe to remove will be a huge help ...
Thanks for you work man only active developer for H901, and I know you have allot on your plate but you are our only hope... Cheers!!
Click to expand...
Click to collapse
I've removed all the Tmobile apps that I don't want or need and I haven't gotten any bootloops.
Just have to remove that apps entire folder. Also removed some Google apps I didnt want.

so...this does not include the N modem then? and the first update.zip does? cause i thought i saw the first update.zip it say flashing modem..

Please disregard, thank you

Is these fix front camera
Sent from my LG-H818 using XDA-Developers Legacy app

sumitverma1 said:
Is these fix front camera
Sent from my LG-H818 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes this will fix the front facing camera bug that was mentioned in the update.zip thread.

I notice this seems to include a RPM partition. So do we need to flash your add-on.zip still for the nougat power management? It sounds like all we need now is update.zip and this along with SuperSU ? Awesome work btw. My battery life overnight after flashing this was 1 percent loss with WiFi and Bluetooth on. You should combine your update and this camera/misc fix zip together.

First post updated to answer that and some other questions.
-- Brian

I flashed this new add-on or full partition zip
cleared my Dalvik cache and my regular cache and well I didn't fell like re entering all my mods and settings so I didn't do the full wipe. noticed the new boot loader right away can pause boot now lol. I didn't have the camera bug but am wondering how this latest zip will do with my battery some one posted it helped there overnight only running 1% will post if I find more things it affected "can't hurt things" and I'm happy with the mods N 7.0 can run so I'm even deleting my MM 6.0 BACKUPS. No need to have that option anymore. I do wonder about kernels, the old sound mod, and https://forum.xda-developers.com/tm...-msm-8992-cpu-io-ram-interactive-gov-t3351478

Any plans to track down where the rollback counter is getting incremented and remove that part?

@famewolf anti-rollback version wasn't incremented even if you took the OTA or flashed the KDZ. It was version 2 on MM, and it is still version 2.
I have no idea why people are having a problem flashing back to v20L (it passes the rollback check in LG UP -- but then fails later in the flash). Makes no sense....
-- Brian

runningnak3d said:
@famewolf anti-rollback version wasn't incremented even if you took the OTA or flashed the KDZ. It was version 2 on MM, and it is still version 2.
I have no idea why people are having a problem flashing back to v20L (it passes the rollback check in LG UP -- but then fails later in the flash). Makes no sense....
-- Brian
Click to expand...
Click to collapse
Ok, I'll chalk it up to my friend trying to go back to MM without restoring all partitions then because you made it clear a normal restore wasn't gonna do it. I think they tried using flashfire. I'm not upgraded yet.

Will this fix the battery drain issue or is it the same as flashing the fix?

Could you make a fix for just the front facing camera for those who flashed the update.zip and don't want to re-reset and flash?

@k00lguy105 I dunno. Some people were getting better battery life, others worse. Try it -- you can always revert.
@xxcmb3k3xx It was the aboot partition that fixed the camera. The thing is, I don't know the consequences of flashing JUST the aboot without all the other boot loader partitions. I will make you a zip if you want to try it, but I can tell you now that aboot is not something you want to mess with without 100% certainty of the outcome. I was convinced that the 808 could always be recovered with the SD card, but aboot is the one part of the boot process that will turn your phone into an unrecoverable brick.
If you don't want to wipe, then don't -- it is safe to dirty flash this. I only recommend wiping because that way you are guaranteed to not have problems. At least wipe cache, and as I said above, if bad comes to worse you can always revert.
-- Brian

runningnak3d said:
@k00lguy105 I dunno. Some people were getting better battery life, others worse. Try it -- you can always revert.
@xxcmb3k3xx It was the aboot partition that fixed the camera. The thing is, I don't know the consequences of flashing JUST the aboot without all the other boot loader partitions. I will make you a zip if you want to try it, but I can tell you now that aboot is not something you want to mess with without 100% certainty of the outcome. I was convinced that the 808 could always be recovered with the SD card, but aboot is the one part of the boot process that will turn your phone into an unrecoverable brick.
If you don't want to wipe, then don't -- it is safe to dirty flash this. I only recommend wiping because that way you are guaranteed to not have problems. At least wipe cache, and as I said above, if bad comes to worse you can always revert.
-- Brian
Click to expand...
Click to collapse
I just dirty flashed and everything seems to be working fine, I'll update for battery later.

Can't mount system partition in order to backup TWRP

Hope someone could help me with this issue. Im trying to back up the rom with TWRP by selecting data,boot,system.
However the system image is not there. Found other threads where people had this issue but seemed just unticking the read only helped for them.
At first system partition was ticked in the mount and read only was unticked but the system partition was not apearing in the back up section.
Tried to reflash twrp by installing img from twrp - booting into bootloader and then recovery.
After reinstalling twrp did not solve it as i now :
read only unticked, the system partition is ussualy unselected and when I tick system and reboot into recovery its unselected again.
Did anyone come accross this issue?
If I flash a new ROM I will not be able to restore if system partision is not available as that is the os correct?

Can no one help me with this?
I have tried to update the twrp to newer unoficial version. I am still unable to mount system.
Once I select system in mount and reboot in recovery its just deselected and not visible in the back up.
please help

Wow, surprised you've had no responses. Particularly now with so many of us spending all our time at home on the comp. Anyway, I've been having a slew of problems lately with my Pixel 2 XL which has been requiring Factory Resets which really suck because they delete all my data, and on this last reset, Google won't even restore my homescreen layouts/apps, etc.
So I've decided to finally take the time to install TWRP and start creating Nandroid backups like the old days, but there are a number of issues these days that we didn't have in the old days. In some ways it's easier to unlock, root, and install custom recoveries these days (heck I barely needed to use ADB), but it's also fraught with pitfalls and buggy quirks. Like, this slot a/b deal, and the way that TWRP now wants you to swipe your pattern to decrypt your files, but it doesn't work. And I'm still not sure I trust Magisk, etc.
I am having the same issue, I can't create backups in TWRP because system won't mount, etc., but I'll dive in when I have more time and see if I can help you out with what I discover. I'll post back here soon. For now I have to leave and perform my "essential job". I wish this whole pandemic debacle happened 2 years ago when I was already working remotely from home with a healthy paycheck each week.
Good luck and talk soon...
---------- Post added at 03:58 AM ---------- Previous post was at 03:45 AM ----------
Gotta run but this might help you get a start in the right direction:
https://youtu.be/T-7neHzSIvc

rabaker07 said:
Wow, surprised you've had no responses. Particularly now with so many of us spending all our time at home on the comp. Anyway, I've been having a slew of problems lately with my Pixel 2 XL which has been requiring Factory Resets which really suck because they delete all my data, and on this last reset, Google won't even restore my homescreen layouts/apps, etc.
So I've decided to finally take the time to install TWRP and start creating Nandroid backups like the old days, but there are a number of issues these days that we didn't have in the old days. In some ways it's easier to unlock, root, and install custom recoveries these days (heck I barely needed to use ADB), but it's also fraught with pitfalls and buggy quirks. Like, this slot a/b deal, and the way that TWRP now wants you to swipe your pattern to decrypt your files, but it doesn't work. And I'm still not sure I trust Magisk, etc.
I am having the same issue, I can't create backups in TWRP because system won't mount, etc., but I'll dive in when I have more time and see if I can help you out with what I discover. I'll post back here soon. For now I have to leave and perform my "essential job". I wish this whole pandemic debacle happened 2 years ago when I was already working remotely from home with a healthy paycheck each week.
Good luck and talk soon...
---------- Post added at 03:58 AM ---------- Previous post was at 03:45 AM ----------
Gotta run but this might help you get a start in the right direction:
Click to expand...
Click to collapse
Any update? My TWRP couldn't mount system either

rabaker07 said:
Wow, surprised you've had no responses. Particularly now with so many of us spending all our time at home on the comp. Anyway, I've been having a slew of problems lately with my Pixel 2 XL which has been requiring Factory Resets which really suck because they delete all my data, and on this last reset, Google won't even restore my homescreen layouts/apps, etc.
So I've decided to finally take the time to install TWRP and start creating Nandroid backups like the old days, but there are a number of issues these days that we didn't have in the old days. In some ways it's easier to unlock, root, and install custom recoveries these days (heck I barely needed to use ADB), but it's also fraught with pitfalls and buggy quirks. Like, this slot a/b deal, and the way that TWRP now wants you to swipe your pattern to decrypt your files, but it doesn't work. And I'm still not sure I trust Magisk, etc.
I am having the same issue, I can't create backups in TWRP because system won't mount, etc., but I'll dive in when I have more time and see if I can help you out with what I discover. I'll post back here soon. For now I have to leave and perform my "essential job". I wish this whole pandemic debacle happened 2 years ago when I was already working remotely from home with a healthy paycheck each week.
Good luck and talk soon...
---------- Post added at 03:58 AM ---------- Previous post was at 03:45 AM ----------
Gotta run but this might help you get a start in the right direction:
Click to expand...
Click to collapse
handydandy said:
Any update? My TWRP couldn't mount system either
Click to expand...
Click to collapse
Which phone, firmware/ROM and which TWRP - who and how can anybody respond if basic info is not provided
This is forum for Xiaomi Mi 9T/Redmi K20 - for issues on Pixels, please use forums for those phones (how can you expect to get answers for Pixels here)
Be also aware that TWRP does not support yet phones released with Android 11 (like Pixels with A11)
On Mi 9T/Redmi K20, use the official TWRP 3.4.0.0 - it properly mounts partitions
If using unofficial TWRPs, report to them, or to the custom/unofficial ROMs you're maybe using

**PERSIST REQUEST** Enrollment Problem

If you can help me fix this i will donate you for your time
Somehow deleted messed up Persists and need a backup.

We are in a similar situation, my adb wasn't fully working, couldn't root on 10.5.4, msm and went back to stock, realized my adb wasn't fully working, I did the OTA to 10.5.5 and then I rooted, lost fingerprint read. Personally, I value root far more than fingerprint function, already started customizing the phone so can't be bothered to wipe the phone. I am pretty sure you would regain the fingerprint function if you go back to fully stock. If you can't be bothered to do it yourself, I think it's just a matter of time until a toolkit that does it for you is updated for the 8 pro.

t-mizzle said:
We are in a similar situation, my adb wasn't fully working, couldn't root on 10.5.4, msm and went back to stock, realized my adb wasn't fully working, I did the OTA to 10.5.5 and then I rooted, lost fingerprint read. Personally, I value root far more than fingerprint function, already started customizing the phone so can't be bothered to wipe the phone. I am pretty sure you would regain the fingerprint function if you go back to fully stock. If you can't be bothered to do it yourself, I think it's just a matter of time until a toolkit that does it for you is updated for the 8 pro.
Click to expand...
Click to collapse
ive done used MSM Brick Fix along with just about every other stock. Nothing has worked only reason i am so panicky over it is being used for a project that im working on and really need all features to work

Is this for Global or EU? Have a look in my thread if you need an EU persist. I ended up bricking mine trying to fix it.
This seems quite a wide spread issue, MSM doesn’t fix it either

If no one can provide you with a fix, I would use adb to flash the stock boot image. If you are wiped and fully stock again, did you go through the setup again, if so, did the enrollment fail there or did it fail when you manually went there? I just don't see why it would fail when the phone is in the stock "first bootup" mode.

It fails during first setup, during any setup. Even after a full flash with msm tool. I think the persist partion somehow gets messed up.
All I had done is flashed stock boot img was then reset.

Interesting. Did you at any point have a working fingerprint scanner? I did, until I rooted.

Guitarfreak26 said:
It fails during first setup, during any setup. Even after a full flash with msm tool. I think the persist partion somehow gets messed up.
All I had done is flashed stock boot img was then reset.
Click to expand...
Click to collapse
you forgot to convert the persist image before flashing thats what caused your brick most likely.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
Dewaynelives said:
If you can help me fix this i will donate you for your time
Somehow deleted messed up Persists and need a backup.
Click to expand...
Click to collapse
If you on EU then there is a persist image on the Root thread. But remember you need to convert it to a raw img from sparse image before flashing.
Google simgtoimg tool

Yeah I didn’t convert it I think that was the issue.
And yes my fingerprint sensor worked perfectly up until a factory reset then nothing. On the other thread, Zige advised that Oneplus Finland are aware of the issue and said a fix will roll out ?

Guitarfreak26 said:
Yeah I didn’t convert it I think that was the issue.
And yes my fingerprint sensor worked perfectly up until a factory reset then nothing. On the other thread, Zige advised that Oneplus Finland are aware of the issue and said a fix will roll out ?
Click to expand...
Click to collapse
Ot..Oneplus Finland sound funny..Cause its a Chinese company and i am Finnish myself

Nekromantik said:
you forgot to convert the persist image before flashing thats what caused your brick most likely.
Click to expand...
Click to collapse
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.

dladz said:
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
Click to expand...
Click to collapse
yes you just need the tool google simage2img
as long as you have a backup of the partition and can use the tool and have access to fastboot it can be saved as far as I know.
other user lost access to fastboot as he used MSMtool to revert back to stock so locked bootloader. If you want to flash the persist do not use msmtool

Nekromantik said:
yes you just need the tool google simage2img
as long as you have a backup of the partition and can use the tool and have access to fastboot it can be saved as far as I know.
other user lost access to fastboot as he used MSMtool to revert back to stock so locked bootloader. If you want to flash the persist do not use msmtool
Click to expand...
Click to collapse
Not that i have this happened to me but still. Witch is broken, msmtool or phones sofrware? I am using linux so msm would be pointless for me. Just out of coriousity and knoledge i am asking

dladz said:
Is that something that should be common knowledge for users who are opting to root and have a tinker.
It's it easy enough to convert? It's there any way to save your device if this happens?
I know @guitarfreak has had a lot of issues and I think it's heading for RMA right Gfreak?
We need a thread about this.
Click to expand...
Click to collapse
Yeah it’s in Poland now at the service centre. I asked for a refund for now as I’m not sure what’s happening with it. I hadn’t crossflashed anything prior to the sensor stopping. So I’m not sure what’s causing the fault.
---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------
pyry666 said:
Not that i have this happened to me but still. Witch is broken, msmtool or phones sofrware? I am using linux so msm would be pointless for me. Just out of coriousity and knoledge i am asking
Click to expand...
Click to collapse
Previously with OP the MSMTOOL would fix anything. Even when moving over to AOSP ROMs. Now it seems the tool can not fix the partion. So when I flashed wrong partion then tried to fix again with the tool it locked the boot loader but wouldn’t boot into OS.

Guitarfreak26 said:
Yeah it’s in Poland now at the service centre. I asked for a refund for now as I’m not sure what’s happening with it. I hadn’t crossflashed anything prior to the sensor stopping. So I’m not sure what’s causing the fault.
---------- Post added at 01:24 PM ---------- Previous post was at 01:23 PM ----------
Previously with OP the MSMTOOL would fix anything. Even when moving over to AOSP ROMs. Now it seems the tool can not fix the partion. So when I flashed wrong partion then tried to fix again with the tool it locked the boot loader but wouldn’t boot into OS.
Click to expand...
Click to collapse
I know that. I am interested is it msmtool failure or something in os

From my understanding from looking across the forums the persist partion hasn’t been touched by MSM for a while. Which would mean it’s an OS fault.
Does the boot img even touch the persist partion as that’s the only thing that had been touched prior to the fault? I don’t have enough understanding on persist as I’d never seen the issue before lol

pyry666 said:
I know that. I am interested is it msmtool failure or something in os
Click to expand...
Click to collapse
this has nothing to do with msmtool.
msmtool was used by people to try and fix the fingerprint issue.
This only should happen if you flash wrong version boot img. If you do that then you will loose fingerprint.
Some people have lost fingerprint even if they said they used correct boot img.
only way to bring fingerprint back is to flash persist img back onto phone. but you need to use simg2img tool which converts the posted img from sparse to raw. you can only flash raw images.
when you extract the img from phone its in sparse format and not raw

Nekromantik said:
this has nothing to do with msmtool.
msmtool was used by people to try and fix the fingerprint issue.
This only should happen if you flash wrong version boot img. If you do that then you will loose fingerprint.
Some people have lost fingerprint even if they said they used correct boot img.
only way to bring fingerprint back is to flash persist img back onto phone. but you need to use simg2img tool which converts the posted img from sparse to raw. you can only flash raw images.
when you extract the img from phone its in sparse format and not raw
Click to expand...
Click to collapse
Im on Int version is there any way for me to fix it? i dont know anyone with the device myself so i have no way to get the file

Nekromantik said:
you forgot to convert the persist image before flashing thats what caused your brick most likely.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
If you on EU then there is a persist image on the Root thread. But remember you need to convert it to a raw img from sparse image before flashing.
Google simgtoimg tool
Click to expand...
Click to collapse
im on int myself . whats messed u is i have not flashed any files from other regions to cause this so i guess it has to do with root?

Dewaynelives said:
im on int myself . whats messed u is i have not flashed any files from other regions to cause this so i guess it has to do with root?
Click to expand...
Click to collapse
Well, in my case it has been caused by a factory reset. Yes, I was rooted before that, but everything worked fine - so maybe rooting was the cause and it became evident after the reset.
Oh, and I was only on EU ROM - so no cross-country flashing.
I'll wait for Oneplus fixing this, for me there is too little understanding what happens when flashing persist from a different phone.

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