Database Info

[GUIDE] Getting started - Unlock->TWRP->root->OTA updates

As there seems to be no such guide yet and it took me quite a while to get all this information together, I thought of giving back something by putting information together for others to start.
This guide is meant for the CLT-L29 (dual SIM). Rebranding and switching your CLT-L09 (single SIM) to dual is not subject of this guide and is not adviced.
This is for a Huawei P20 Pro CLT-L29 with factory reset. Please bear with me if there really is a step missing as I try to reproduce this for the documentation with an already bootloader unlocked and previously rooted phone (root should be gone after [factory] resetting via eRecovery).
A collection of all tools used can be found here.
As always, you are doing this on your own risk, no one else can be held responsible for this.
Cheat sheet
eRecovery
The recovery sitting in the "recovery" partition. eRecovery is Huawei's recovery that is able to fix your phone by downloading the latest OTA update via WiFi if you got stuck in a boot loop for several reasons.
To boot into eRecovery:
Power down your phone (if you are stuck in a boot loop simply continue with the next step).
Hold volume up until you end up in eRecovery.
Setup your WiFi access and let it recover your phone.
If unsure, "wipe data/factory reset" to get rid of any leftovers you messed up.
Reboot and be happy that you have not fully bricked your phone.
TWRP
The recovery typically flashed to the "recovery_ramdisk" partition. TeamWin Recovery Project is what you typically use to flash ROMs, to root the phone and to install OTA updates.
Do NOT flash TWRP into "recovery" partition or you will lose eRecovery and the ability to easily recover your semi-bricked phone via WiFi!
To boot into TWRP (once flashed):
Power down your phone (if you are stuck in a boot loop simply continue with the next step).
Hold volume up and power until you end up in TWRP.
Unlock your bootloader
Get your bootloader unlock code from here https://emui.huawei.com/en/unlock_detail (available until mid of July I think). Some report to have to wait 24/48h to get their code via mail, I got mine directly.
Register via mail and do not get confused that you can not select USA or Germany or whatever country, simply use location Hong Kong.
Make sure you select "EMUI above 5.0" when entering your phone data (P20 Pro comes with EMUI 8.x).
Connect your phone via ADB. There are tons of HowTos about this, so I will not be covering this here.
Use Tool All In One to check that you can talk to your device via ADB. It will also help you installing the correct ADB USB drivers.
Unlock your bootloader using Tool All In One.
Reboot back into system.
Flash TWRP
Make sure no lock screen or other locking is set:
"Settings > Security": Remove fingerprint, face or password locking, simply set to none.
Enter developer mode, should already been done for unlocking the bootloader.
Setting > System > Developer options: Disable the display lock.
Download latest ADB & Fastboot as I will continue with the rest on command line.
Verify connection to your phone with "adb devices", this should list your phone.
Reboot into fastboot by using "adb reboot bootloader".
Verify connection to your phone with "fastboot devices", this should list your phone.
Flash TWRP by Pretoriano80 with "fastboot flash recovery_ramdisk twrp_clt_0.1.img". This TWRP is able to access the encrypted internal storage! TWRP is flashed to "recovery_ramdisk". This ensures that you can still access eRecovery if something goes wrong.
Remove the USB cable.
Reboot into TWRP. If you do not boot directly into TWRP the Huawei eRecovery might replace TWRP again. Once you booted into TWRP you are fine for future reboots.
Use "Keep Read Only" for the system partition.
Make a backup!!!
Backup your phone to internal storage (USB stick via USB-OTG adapter failed for me):
Select "Backup".
Tick all partitions (scroll down and tick all).
Swipe to Backup.
Select "Reboot System", "Do Not Install".
Back in Android make a copy of your backup located in your internal storage "/TWRP/" to an external location like your PC. Keep the backup on your phone to be able to go back quickly to this point via TWRP.
Root the stock ROM
Place "Magisk-v16.4-Beta.zip" onto the internal storage.
Power off the phone and remove the USB cable.
Boot into TWRP.
Install root and Magisk Manager:
Select "Install".
Select "Magisk-v16.4-Beta.zip"
Tick "Reboot after installation is complete".
Swipe to confirm Flash.
Select "Do Not Install".
Back in Android start "Magisk Manager" and check that it is green and therefore rooted.
Install an OTA (Over The Air) stock update
PC method
Method involving ADB based on this guide.
First make sure no OTA update gets installed automatically as this will end up in booting into TWRP and failing with the update.
Go to "Settings > System > System Update".
Open the three dots menu on the top right and select "Update Settings".
Disable automatic update download via WiFi as once updates are downloaded the phone will bug you to update and maybe tries to update itself during the night!
Start in Android but do not download the OTA update yet.
Verify connection to your phone with "adb devices", this should list your phone.
Reboot into fastboot by using "adb reboot bootloader".
Verify connection to your phone with "fastboot devices", this should list your phone.
Flash "recovery_ramdisk_nocheckP20.img" with "fastboot flash recovery_ramdisk recovery_ramdisk_nocheckP20.img". For official OTA updates that you would regularly get, the "nocheck" feature should not be needed but does not harm. This will remove TWRP and you have to flash it again after the OTA update has finished.
Reboot into Android by using "fastboot reboot".
Remove the USB cable.
Download your OTA update via "Settings > System > System Update".
Let the phone reboot to install the OTA update and follow the update until you are back in Android with your new firmware version.
Install TWRP and root again.
Standalone method
Deprecated/wrong method based on this guide.
Read first!!!
While this method should do no harm it will only ever update to CLT-L29 8.1.0.128a(C432) [hw/eu] as this is what is inside the file "update.zip" that you can currently download and that gets installed by "HuRUpdater_0.3.zip" in the same folder. This was not clearly explained in the source thread, therefore sorry about this wrong information. If you intend to update to this stock ROM continue, otherwise use the "PC method".
I will check about the best way to install OTA updates without PC interaction in the next couple of days (currently waiting for 130+ getting rolled out for me for some investigations regarding the OTA process).
First make sure no OTA update gets installed automatically as this will end up in booting into TWRP and failing with the update.
Go to "Settings > System > System Update".
Open the three dots menu on the top right and select "Update Settings".
Disable automatic update download via WiFi as once updates are downloaded the phone will bug you to update and maybe tries to update itself during the night!
Place the following files into a folder on the internal storage (for sure not all are required but this is part of the little information not clear right now):
"HuRUpdater_0.3.zip"
"recovery.img"
"update.zip"
"update_all_hw.zip"
"update_data_public.zip"
Go to "Settings > System > System Update" and check for an update.
Download the OTA update.
Do not reboot when prompted.
Make sure no lock screen or other locking is set:
"Settings > Security": Remove fingerprint, face or password locking, simply set to none.
Enter developer mode, should already been done for unlocking the bootloader.
Setting > System > Developer options: Disable the display lock.
Power down the phone.
Boot into TWRP.
Install "HuRUpdater_0.3.zip". Do not get irritated if it tells you it is for CLT-L09 instead of CLT-L29, everything is fine.
Wipe dalvik cache before rebooting.
Reboot back into Android.
Check "Magisk Manager" to see if root got removed. TWRP might get removed as well. If TWRP or root got removed, repeat the install for one or both like before.
In my case only root got removed but TWRP was kept functional. If this is the case for you as well, simply flash "Magisk-v16.4-Beta.zip" via TWRP again.
Changelog
2018-06-21
Updated/corrected wrong information collected about installing OTA updates standalone (without PC). Until further notice use the PC method.

Great post. Thank you

Very good post!
Thank you to collect all this important info!
[emoji481]
P20 Pro & Tapatalk

can i use your step above to rebranding from L29c636 to l29c432? Thanks

Barcovn said:
can i use your step above to rebranding from L29c636 to l29c432? Thanks
Click to expand...
Click to collapse
Not sure, not tested and not topic of this thread.
For my understanding, why do you want to rebrand it to C432 which is the region code as far as I understand.
Is there a BIG benefit of getting OTA updates earlier or why do you want to mess around with it ?

Xcelsior said:
Not sure, not tested and not topic of this thread.
For my understanding, why do you want to rebrand it to C432 which is the region code as far as I understand.
Is there a BIG benefit of getting OTA updates earlier or why do you want to mess around with it ?
Click to expand...
Click to collapse
yes, i mean change the region code. as i use the p20 pro since April, newer firmware ususal fix/improve performance for phone or camera. however it seem the c636 update is much slower then C432. currently i have problem with facebook lagging which inhope newer firmware fix it

This is good! I'll sticky it when I get a chance later tonight. I'm mobile atm

Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there

dladz said:
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
Click to expand...
Click to collapse
They're a bit different. The debrand thread is obviously good but much more specific to debranding. This is a more generic for general How-To's

dladz said:
Maybe I'm missing something.
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
It's been here for some time.
Nothing wrong with your guide it's decent but the info provided is actually already here mate.
Root, twrp, de-brand, OTA, it's all there
Click to expand...
Click to collapse
I was reading this one as well but like matt4321 already said, it is actually for a different purpose.
And even the "ROOT ONLY" instructions are either widespread over the whole P20 Pro forum, incomplete or even outdated:
Linking to other threads with endless, partly revised instructions (on page n of the thread).
Referring to wrong official TWRP that can not use internal storage.
Hard to understand for beginners on this device (not even talking about someone who is entirely new to all of this).
Missing steps or expecting that you have already successfully flashed your first ROM (talking about advanced things like rebranding).
Don't get me wong, I am used to read a lot when it comes to custom ROMs (if you check the old part of my signature you can see that I am not actually a newbie here and my roots actually reach back to when all of the Android stuff startet at all, back when XDAs flashed HTC HD2 WinMo to Android). However I really missed a guide that actually collects all the basic information for beginners without going off roads too early.

These are more or less the steps I'm used to when I owned my nexus phones.
I have some questions:
If I root my phone and install, let's say adaway, will I be able to receive OTA? Or I will have to flash a new image manually?
If after root I relock bootloader, will I be able to unlock it again later for further modding?
This method implies that I can return to stock anytime and relock bootloader?
Thanks for the guide and answers , great job

mangusZen said:
If I root my phone and install, let's say adaway, will I be able to receive OTA? Or I will have to flash a new image manually?
Click to expand...
Click to collapse
Yes, exactly what I am doing. I need root for some apps and besides that I am happy with the stock OTA ROM, at least for the moment. OTA updates work fine so far.
The only thing as explained in my guide is that OTA updates will fail as they boot into TWRP instead of original fastboot. Therefore you need to explicitly boot into TWRP and install the downloaded OTA update with "HuRUpdater_0.3.zip".
mangusZen said:
If after root I relock bootloader, will I be able to unlock it again later for further modding?
Click to expand...
Click to collapse
From what I have read so far re-locking your bootloader is not advised. You seem to be unable to unlock it again or at least need to request another unlock code from Huawei.
At least this is my understanding of the situation so far.
mangusZen said:
This method implies that I can return to stock anytime and relock bootloader?
Click to expand...
Click to collapse
Returning to stock is even easier if you keep eRecovery working as explained in the guide (flashing TWRP only to recovery_ramdisk partition). With eRecovery you can wipe TWRP and root and let eRecovery download and install the latest official stock ROM.
Regarding the bootloader re-locking, see my answer above.

Xcelsior said:
Yes, exactly what I am doing. I need root for some apps and besides that I am happy with the stock OTA ROM, at least for the moment. OTA updates work fine so far.
The only thing as explained in my guide is that OTA updates will fail as they boot into TWRP instead of original fastboot. Therefore you need to explicitly boot into TWRP and install the downloaded OTA update with "HuRUpdater_0.3.zip".
From what I have read so far re-locking your bootloader is not advised. You seem to be unable to unlock it again or at least need to request another unlock code from Huawei.
At least this is my understanding of the situation so far.
Returning to stock is even easier if you keep eRecovery working as explained in the guide (flashing TWRP only to recovery_ramdisk partition). With eRecovery you can wipe TWRP and root and let eRecovery download and install the latest official stock ROM.
Regarding the bootloader re-locking, see my answer above.
Click to expand...
Click to collapse
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
For what I read and understood, but I may be wrong, the problem with relocking bootloader is encountered by who used the funkyhuawei method, that alters bootloader in some way, especially to achive the mono sim - dual sim switch.
With this you cant for now re unlock the bootloader again.
But I could be wrong and be like that for everyone, will see if someone will come up with some clarifications.
It would be nice to have the ability to return to stock, lock bootloader and use warranty
[emoji14]
Thanks for your work and answers

mangusZen said:
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
Click to expand...
Click to collapse
Yes, that is basically what "HuRUpdater_0.3.zip" will do, it will flash/install an OTA update that has previously been downloaded.
Wipe cache afterwards and be happy with your new up to date stock ROM version.

Xcelsior said:
Yes, that is basically what "HuRUpdater_0.3.zip" will do, it will flash/install an OTA update that has previously been downloaded.
Wipe cache afterwards and be happy with your new up to date stock ROM version.
Click to expand...
Click to collapse
I have to rename the downloaded OTA packages for huru to work, right?

mangusZen said:
I have to rename the downloaded OTA packages for huru to work, right?
Click to expand...
Click to collapse
Not for me. Just downloaded the OTA update via the EMUI system menu in Android, rebooted into TWRP and installed (aka executed) HuRu.
HuRu did the rest for me.
Tested with 120 -> 128 OTA update.

Hi It is late at night and I am not sure if I typed fastboot flash recovery twrp_clt_0.1.img instead off fastboot flash recovery_ramdisk twrp_clt_0.1.img. How can I make sure I still have erecovery? super newbie to android rooting, please help Thank you

Amowiel said:
Hi It is late at night and I am not sure if I typed fastboot flash recovery twrp_clt_0.1.img instead off fastboot flash recovery_ramdisk twrp_clt_0.1.img. How can I make sure I still have erecovery? super newbie to android rooting, please help Thank you
Click to expand...
Click to collapse
Simplest way would be to try to boot into eRocovery:
Power off the phone.
Power on the phone until you see the "you are a baddy because you unlocked your bootloader" screen.
Hold volume up (you can already hold it when powering on the phone) until you end up in eRecovery or TWRP.
If you end up in TWRP it should still be possible to recover your eRecovery with a proper backup of the "recovery" partition from any other P20 Pro.

Xcelsior said:
Simplest way would be to try to boot into eRocovery:
Power off the phone.
Power on the phone until you see the "you are a baddy because you unlocked your bootloader" screen.
Hold volume up (you can already hold it when powering on the phone) until you end up in eRecovery or TWRP.
If you end up in TWRP it should still be possible to recover your eRecovery with a proper backup of the "recovery" partition from any other P20 Pro.
Click to expand...
Click to collapse
thank you so much for such a quick reply, can confirm that my brain was not so fried and I didn't wipe my ercovery
thank you for your amazing guide, everything worked perfectly

mangusZen said:
Ok, so to install OTA I have to use hurupdater method and flash the OTA package manually.
For what I read and understood, but I may be wrong, the problem with relocking bootloader is encountered by who used the funkyhuawei method, that alters bootloader in some way, especially to achive the mono sim - dual sim switch.
With this you cant for now re unlock the bootloader again.
But I could be wrong and be like that for everyone, will see if someone will come up with some clarifications.
It would be nice to have the ability to return to stock, lock bootloader and use warranty
[emoji14]
Thanks for your work and answers
Click to expand...
Click to collapse
Actually you don't in some cases, if your simply rooted with twrp and you want to install an OTA that's been advertised to your device. All you need to do is install the nocheck recovery IMG and then take the update, reinstall twrp and magisk after the update and you're done.
If it's an update that's not advertised to your device yet then hur updater is the way.

Was Bricked - CLT-L04 with EMUI 8.1 - the fixed ended up giving me EMUI 9 CLT-L04

Bricked my phone by doing the following:
Honor View 10 ROMs are compatible with P20 Pro, I installed and used them all. Then the other day they made a mod that force the EMUI 9 update so I ran it. The mod ended rebranding my entire phone to Honor View 10 followed by boot loops like crazy. So then I went into twrp and tried to format thinking it would help. It ended up deleting everything including eRecovery. The only this I had access to was fastboot. Yes I brought this on my self lol. I paid a lot for Funky Huawei but nothing worked. I tried every tool they had.
Fix: (Turns out my phone's structure is now EMUI 9\Android 9)
1- Downloaded my phone image (CLT-L04 - EMUI 9 version), extracted the update.app file from it.
2- Used EMUI extractor app to extracted everything from the update.app file (Lots of image files)
3- Noticed userdata.img wasn't in the extracted files so I downloaded multiple images that are similar models to my phone until I found it.
4- Used fastboot command to flash the userdata.img, followed by eRecovery.img, followed by the rest I pulled from that update.app file.
after about three reboots I was back into my phone except I now have EMUI 9.

My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.

QuazIqbal said:
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
Click to expand...
Click to collapse
Can you try this.
Files that you will be downloading are,
update.zip
update_full_CLT-L29_hw_eu.zip (Or whatever model of phone you have)
Get them here by searching for your model and click filelist
Prep:
a. Rename update_full_CLT-L29_hw_eu.zip to update_all_hw.zip
b. Download this Flash tool and extract in to a folder in your PC
c. Copy update.zip and update_all_hw.zip to ZIPS-HERE folder (you can find this folder where you have extracted Flash tool
How to flash Firmware
1. Double click to run the file cmd-here.exe. It opens command prompt in the same folder where you are.
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.

Vedrick said:
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.
Click to expand...
Click to collapse
Thanks for offering your help. Mine case looks different....
I have tried this, after flashing twrp in the fastboot the device fails to boot into twrp recovery, it's all black, only fastboot is accessible in the black screen.

I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?

przival said:
I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?
Click to expand...
Click to collapse
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.

QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.

QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone

Deano1889 said:
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.
Click to expand...
Click to collapse
I will do my best to answer tomorrow, God willing. Please wait
---------- Post added at 09:04 PM ---------- Previous post was at 08:55 PM ----------
black_1986 said:
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone
Click to expand...
Click to collapse
After this process your bl will be in 'locked' state. If you had my kind of downgrade brick the imeis and serial will number will not be disturbed. You may simply use your old bl code to unlock. However I messed up my oeminfo but due to my own stupidity, I'm looking to restore my imei and will try to unlock again.

If possible, could you share the files you use?

Root Question

Just trying to find out if there is a way to Root my Motorola Edge xt2063-2 US version stock firmware and unlocked bootloader all I want to do is ROOT IS THERE A WAY TO JUST ROOT any info or tips would be greatly appreciated THANKS IN ADVANCE

j.smith81 said:
Just trying to find out if there is a way to Root my Motorola Edge xt2063-2 US version stock firmware and unlocked bootloader all I want to do is ROOT IS THERE A WAY TO JUST ROOT any info or tips would be greatly appreciated THANKS IN ADVANCE
Click to expand...
Click to collapse
You should be able to root with Magisk
https://www.xda-developers.com/how-to-install-magisk/
Non-twrp method
Download Magisk manager app
https://github.com/topjohnwu/Magisk/releases/
current version Magisk Manager v8.0.7 -23 Jan 2021
Download device firmware with LMSA'S flash Rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Find boot.img in firmware folder, copy to device.
Open Magisk manager,
Select Install Magisk
Select and Patch a File
Select boot.img
Copy modified boot.img to PC
Flash modified boot.img to device.
Code:
fastboot flash boot filename.img
Reboot
Open Magisk manager to verify you have current version.
If you don't have Windows PC or not familiar with fastboot see
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
You should be able to root with Magisk
https://www.xda-developers.com/how-to-install-magisk/
Non-twrp method
Download Magisk manager app
https://github.com/topjohnwu/Magisk/releases/
current version Magisk Manager v8.0.7 -23 Jan 2021
Download device firmware with LMSA'S flash Rescue
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Find boot.img in firmware folder, copy to device.
Open Magisk manager,
Select Install Magisk
Select and Patch a File
Select boot.img
Copy modified boot.img to PC
Flash modified boot.img to device.
Code:
fastboot flash boot filename.img
Reboot
Open Magisk manager to verify you have current version.
If you don't have Windows PC or not familiar with fastboot see
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks bro I really appreciate your time just one more dumb question I done got myself too confused I've installed manager patched boot image so all thats left is flash new boot image reboot and then BAM do u do everything through manger now or u still have to fastboot adb on computer to flash

j.smith81 said:
...I've installed manager patched boot image..
Click to expand...
Click to collapse
Not sure what you mean?
When you select and patch file
Magisk will say flashing but it doesn't
You need to copy patched.img Magisk creates and flash that to phone

sd_shadow said:
Not sure what you mean?
When you select and patch file
Magisk will say flashing but it doesn't
You need to copy patched.img Magisk creates and flash that to phone
Click to expand...
Click to collapse
What I was trying to ask was can you do everything through the manager app to flash image and unzip magisk instead of connecting to computer I already patched the boot.img jus tryna do it right but I done got my brain so flustered by lookin at the different ways to go about it cause everyone is different I'm sorry dude don't mean to be a pain I need to jus walk away for the day an try again later

j.smith81 said:
What I was trying to ask was can you do everything through the manager app to flash image and unzip magisk instead of connecting to computer..
Click to expand...
Click to collapse
No you need a pc.

Been so long since I rooted a phone but the Edge was simple;
Fully charge phone - not critical, but good to make sure you have plenty of juice!
Take full backup
Unlock bootloader
Flash TWRP recovery
Download latest Magisk.zip and save it to SD Card on your phone
Boot into recovery and install Magisk.zip through TWRP
Reboot and open Magisk to complete the process.
Et voila...
I have my Barclays app working (no fingerprint for it though), and also the UK Lotto app and NO ADS!
Loving this low-cost phone and will no longer be paying £1500+ for a Samsung

Cannot get oem unlock token oneplus 8 tmobile (in2017)

So I purchased a tmobile op8 and it arrived yesterday, after setting up the phone and network unlocking (which happened basically instantaneously after applying for it which i found odd), I am currently trying to unlock bootloader in the hopes of converting it to the international firmware. I am on software version 11.0.5.7.IN55CB
The problem I am facing is that whenever i try to do "adb devices" while the phone is powered on it works and lists it, but when the phone is in fastboot mode it does not list the device. Also when i do "fastboot oem get_unloock_code" it gets stuck at waiting for devices. I have read through numerous posts both here and on the op forums talking about this and some listed solutions such as going into windows optional updates and updating google bootloader or something, while others said to check that bootloader is unlocked (i did both and didnt work). Any tips? Also, could someone please link to the correct adb and driver downloads as I am getting mixed results when searching which is the correct download.

Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Thanks, worked like a charm. Now to wait 7 business days fml

if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk

PrivyetCyka said:
if you just want the bootloader unlocked there's another way to do it instantly using EDL it's how I unlocked mine , instructions and files are here.. only works on Android 11 btw https://androidfilehost.com/?fid=7161016148664833753 if you really don't feel like installing edl and what not there is a Linux live distro that's already ready to go on the edl GitHub page you can download but just forewarning it's extremely glitchy and not used friendly lol if you need help , I can help you tho just lmk
Click to expand...
Click to collapse
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
i have t-m version and i have converted it to international software firmware also gets changed but by your self you won't be able to get 2 sim support because there is only one imei in phone. all the rom's work exacly the same as they do on global version not a single difference currently running a12 aex rom no problems at all

DamianF7 said:
would i be able to convert to international firmware with this?
also at the end of instructions it states "***** i have not had any luck being able to flash custom roms onto this device even with it unlocked so be forewarned *****" Does this mean that only using this method does not allow for custom roms, or would waiting for tmobile unlock, converting to international firmware also not work with roms?
If roms dont work on this model even after flashing international firmware then im probably not even going to unlock lol
Click to expand...
Click to collapse
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind

d.tat said:
don't forget to backup your persist.img there is some % chance it may get lost and you will have to recalibrate firngerprint sensor also back up the modem.img from twrp beacause that's has imei of your phone and if somehow you get your phone hardbricked that would be nice thing to have as a peace of mind
Click to expand...
Click to collapse
Can this be done without TWRP or does this have to be done after I root?

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great

DamianF7 said:
Can this be done without TWRP or does this have to be done after I root?
Click to expand...
Click to collapse
no root needed to install or boot into twrp

d.tat said:
you can backup persist without twrp. i'm sure modem could be backed up without twrp too but that's how i did it even tho i did not need persist nor modem image but i would suggest you do it anyways just to be safe booting into twrp in not hard at all you have to do is go info fastboot and through adb file boot into recovery ( fastboot boot "recovery" ) device will reboot in twrp and from there you just backup persist and modem take that file and save it on your computer
also important note for android 10 use twrp 3.4 and for android 11 use 3.6 and most importantly if you read the instructions on converting to global or installing twrp or custom rom carefully it will work 100% i was lazy and did it old way i used to do it on some other android phones and bricked few times but it was all good with msm tool you could restore phone from almost every state that's what made oneplus great
Click to expand...
Click to collapse
Ok, thanks for clarification

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface

DamianF7 said:
Ive run into an issue with edl mode and you seem knowledgeable. I tried to flash the international firmware with an unlocked bootloader but it turned out to be an older build and now my phone is in crash dump mode. I planned on using msmtool to downgrade to android 10 and just restart but my phone isnt detected by my pc even though i have the qualcomm drivers installed. Any tips?
edit: btw can still access fastboot mode (download mode)
so phone is recognized in fastboot but not as qhusnhub or whatever its supposed to be, its just called oneplus android bootloader interface
Click to expand...
Click to collapse
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged in and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery.
2. Flash recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery NAMEOFFILE.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Use this command "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks for the reply man. Believe it or not this is exactly what I did lol. Got it working again and am now rooted on international oos 11.

FoxyDrew said:
Just need to update drivers friend. Follow carefully.
1. Download Google fastboot drivers, unzip to get "usb_driver" folder
2. Right click file "android_winusb" and select install. Press OK on confirmation dialog.
3. Boot phone into fastboot, and connect to PC
4. Open the device manager on PC, and look for android device. Should have an orange triangle next to it
5. Right click that -> Update driver -> Browse my computer -> let me pick from a list -> Android Bootloader Interface
After success message fastboot commands will work. I'd also recommend using the lastest Fastboot Tools from Google if you have any more issues.
Have fun waiting 1-2 weeks for your unlock_code.bin file. F&^% T-Mobile lmao.
Click to expand...
Click to collapse
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!

SilverZero said:
Just wanted to say that this solved my issue of not being able to make it past the reboot into fastboot when flashing from TMo to Global using the flash-all.bat guides. I ran the batch file on a newly MSM'd 10.5.22 and when it got stuck at "waiting for device" I followed these steps and as soon as the driver was installed the batch file kicked back in and finished the flashing. Cheers!
Click to expand...
Click to collapse
Glad you got it man, worth all the trouble to get to a clean version of OOS without T-MO's junk and spying xD

FoxyDrew said:
EDL mode can be tricky. This one's not a guarantee but it always works for me.
1. Download LinageOS recovery. Make sure you put it in your fastboot/platform-tools folder.
2. Flash that recovery in fastboot mode (unlock bootloader first if you need to) with the command "fastboot flash recovery lineage-18.1-20211218-recovery-instantnoodle.img"
3. Now boot into recovery, select advanced options, and enable ADB.
4. Now you have full adb access. Make sure you're plugged on and use this command on your PC. "adb reboot edl"
5. Check MSM, should be detected now if the right drivers are installed. If not, try combinations of different USB ports and different cables (you'd be surprised)
A lot of the tutorials on here on how to get a T-Mobile version to Global firmware are wonky methods or outdated, so let me know if you continue to have issue with that.
Click to expand...
Click to collapse
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?

nmuntz said:
Thanks SO MUCH for this!! This is the only thing that allowed me to get into EDL Mode. I'm a bit stuck using MSM though. It shows my device as connected, but when I click the "Target" dropdown O2 is not an option. The only option I see is TMO. Any ideas?
UPDATE: i was able to get MSM going. Selecting the target was not needed, just needed to reboot the phone into EDL again and quickly press Start.
I'm back to stock now and just unlocked my bootloader again.
I now have a follow up question: My goal is to install Pixel Experience on my OPO8. Do I need to flash the Global ROM first or can I go straight into Pixel Experience?
UPDATE 2: no matter what I try flashing to my device I always end up getting "not allowed" errors with the critical partition. I've done the fresh MSM process three times already and always end up hitting these critical partition errors when trying to flash the global rom (or any other rom for that matter). any ideas?
Click to expand...
Click to collapse
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.

FoxyDrew said:
Do you have a T-Mobile device? If so you SHOULD be selecting "TMO" from the dropdown in MSM. Not O2 or leaving it blank. If you don't have a T-Mobile device, your using the wrong MSM tool as TMO shouldn't be an option.
Did you unlock your bootloader after MSMing back to stock? MSM Tool will automatically lock your bootloader. Also what recovery are you using to try to flash ROMs?
Also PixelExperience is dead for op8 it stopped getting updates. I'd recommend HavocOS for a "Pixel Experience". Also a well polished ROM in general.
Click to expand...
Click to collapse
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!

nmuntz said:
I'm pretty sure that this is a T-Mobile device. It registers as IN2017 which matches the description of the phone I bought off amazon but not exactly sure how else can i verify this.
I did unlock the bootloader after MSMing back to stock. One thing I noticed is that the stock image that MSM flashed has Sprint branding and not T-Mobile. maybe i'm using the wrong MSM tool? I'm using the one from this guide
I just re-did MSM; this time selecting TMO and I still got Sprint branding. is this expected?
I've been trying with multiple recoverys: the stock one, TWRP and the one that pixelexperience had. The LineageOS one you provided I only used for doing the ADB thing to boot into EDL. What recovery do you recommend I use?
I did read about PixelExperience being dead so downloaded Havoc.
can you please confirm if I should be flashing the Global ROM before flashing HavocOS? regarding the critical partition errors any ideas whats causing those?
last question is regarding adb/fastboot - been reading different things about what version to use. been doing all my last experiments using the ones from https://developer.android.com/studio/releases/platform-tools but got the same results. sorry to spam you with so many questions - appreciate your help!
Click to expand...
Click to collapse
I've never seen that MSM tool, but the one I use doesn't have any Sprint files at all. Not sure where you found that MSM but use this one for future reference.
No you don't need to flash global before a ROM.

OxygenOS A12 breaks rooting?

First let me say that I'm sorry about how this is formatted but I'm very frustrated with Oneplus right now. My troubles began when KB2005_11.C.16 downloaded. I could not take the OTA to save my life and it seems that the download disappeared before I had any opportunity to pull it off the phone. The only thing I could think of to do at this point was search the internet or unroot and try it. My searches turned up nothing useful and mostly forum posts from 2020 and 2021 but were unrelated (obviously). Unroot time it is. The phone updated with no problem but root was gone. Tried to boot a recovery through fastboot with no luck. The command rebooted the phone but hung on "Fastboot Mode". Tried other .img files just for grins and "fastboot boot" just doesn't work for me anymore. I updated the SDK Platform Tools, Xiaomi ADB bootloader interface drivers to no avail. ADB, Fastboot, and FastbootD all seem to function. Just not as I need them to. This is what I've done to rule out operator error.
Phone is Oneplus 8T (KB2005)
Restored phone from MSM to version 11.0.7.9.KB05AA (Obtained personally from Oneplus support)
Setup Wifi and only enough to check for OS updates.
Unlocked bootloader. Accidentally. All I really wanted to do was enable USB debugging. Nevertheless, it was done.
Checked for updates. Update to 11.0.11.11.KB05AA shows up.
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume.
Installing Security update...
Restart now button appears
I click Restart now
System update available 11.0.13.13.KB05AA. Tapped on notification.
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing Security update...
Restart now button appears
I click Restart now
System update available
New version:KB2005_11.C.16_1160_202204222257
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing System update...
Restart now button appears
I click Restart now
At this point OxygenOS is on Android 12
System update available
New version: KB2005_11.C.20_1200_202205262304
I click Download and install
Installation paused. Installation will continue when device isn't being used. To install now, tap Resume
Tapped Resume
Installing System update...
Restart now button appears
I click Restart now
Finally Phone is up to date
Unlocked bootoader and Developer options survived all updates
ADB reboot bootloader rebooted phone to bootloader (as expected)
fastboot reboot fastboot reboot phone to FastbootD mode (as expected)
fastboot boot anyimage.img just freezes the device with a black screen. Booting into a custom recovery this is the only way I know to pull boot.img from the device.
Untill then or until a new way becomes known to me, I'm unable to root my phone.

You should have rooted when you got to C.16. Because that's a full installation zip, you can take the payload.bin from it and use payload dumper to extract the boot image and patch the file with Magisk.
Then you could have followed the process to keep root with an incremental update.
Or, you could have rooted when you were on OOS 11 using TWRP, then kept root at each update.
These are explained in https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/

Fair enough. It does sound easy when you put it that way but here is what part of my complaint is about ...
i just reflashed with msm, unlocked bootloader, and rooted with magisk. Tested root with ADB shell, su
Checked updates again and updating failed, clicked "try again" and it failed again. This time after I clicked try again it shows that it is now trying to install C.16 so away we go ...
Oh wait. Fastboot boot doesn't boot any of my recoveries or boot.img files. I need a working custom recovery to extract a useable boot.img from my phone. Where can I find a recovery that works with C.16+?

Before you yell at me, I noticed that I left off the step of installing magisk to the other partition after the OTA. In fact, I didn't even try that yet but I have been here before and it didn't work. This time, however, it did work and I now have a rooted C.16 ready to update to C.20. I should say thank you but that doesn't sound like enough. Thank you, BillGoss. Sometimes just asking for help is enough.

My initial complaint was a bit clouded. I am reminded now trying to update to C.20, the truth of what happened. The C.20 incremental dropped and I tried to take it but it just kept resulting in "Couldn't update. Installation problem". It was because of this that I decided to unroot and try it. It did update but now I couldn't fastboot boot anyimg.img. I had no recovery.img or boot.img to further my cause. Then I went ballistic. I couldn't find an .Ota folder anywhere on my device. That just made matters worse.
I did discovery at this point that there is no longer a local update option on the update page. but there is an .apk developed by Oneplus themselves that installs a local update app.

So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?

Throg said:
So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?
Click to expand...
Click to collapse
It's clearly stated in BillGoss guide, how to install OTA and keep root.

You can pull your image through msm tool readback mode load msm tool press f8 it brings up a sub menu where you pick what you want to pull them you input oneplus all lowercase as the password on main screen press readback button then put phone into edl mode it will pull the img files out into your c:\ drive

@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?

BillGoss said:
@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?
Click to expand...
Click to collapse
I can zip my copy and pm you a drive link later

BillGoss said:
@scottlam1 I was going to try this because this would be such a help getting the boot image when there have only been incremental updates, but MSM (OOS 11.0.7.9 for KB05AA from https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/) won't accept OnePlus as the password.
Any suggestions?
Click to expand...
Click to collapse
I don't know if it matters for your build but for me I use admin privileges when you first load msm you use other no username password in readback OnePlus is lowercase one word

scottlam1 said:
I don't know if it matters for your build but for me I use admin privileges when you first load msm you use other no username password in readback OnePlus is lowercase one word
Click to expand...
Click to collapse
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.

BillGoss said:
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.
Click to expand...
Click to collapse
Ok you don't need the drive link then

BillGoss said:
That did it! I don't run it as admin, but entering "oneplus" as the password worked.
Now to play with it.
Click to expand...
Click to collapse
And make sure you hit the readback button not start first time I did it I hit start not thinking and ended up factory resetting phone

scottlam1 said:
And make sure you hit the readback button not start first time I did it I hit start not thinking and ended up factory resetting phone
Click to expand...
Click to collapse
No, I didn't make that mistake.

@scottlam1
Apart from struggling to get my PC to connect properly in EDL mode, once it did connect the readback process gave me the boot image. Woo hoo!
I made the mistake of asking for both boot_a and boot_b. But readback only produces files with <partition name>.img and, therefore, I was left with only one boot.img file (the second one).
But this means we can now get a stock boot image without needing a full OTA zip.
Thanks so much for sharing this method to pull partitions from the phone without needing root.

Throg said:
So now I'm on KB2005_11_C.11. Check for updates shows 11.C.20 incremental. This one contains the may security update. I'm currently still on February.
Anyway, when I try to update it just says "Couldn't update. Installation problem.". Does anyone know how I can get this update please?
Click to expand...
Click to collapse
Use the incremental update from oxygen updater apk and get OPLocalUpdate_For_Android12.apk it is a standalone app for local installs that they took out of the normal update in oos12 in magisk you restore images once update is installed don't restart go to magisk and install to inactive slot then you can restart if you had twrp or orange fox in 11 you had to manually restore stock recovery or the update would fail but as of now there is no twrp for a12 available so you don't have to worry about that yet