Database Info

[Q] Kitkat 4.4.1 update

I have a N5 stock/rooted. Does this mean I will have to unroot just to update my phone to KitKat 4.4.1 when it comes out? I would prefer to keep the stock ROM but want the camera upgrades that 4.4.1 is supposed to offer.

so reroot if you are going to have to unroot, big deal. if you want to update from the stock update, you will lose root. then all you have to do is flash a custom recovery then flash the latest supersu in your recovery. it takes about 3-4 minutes of work(without toolkits)..

simms22 said:
so reroot if you are going to have to unroot, big deal. if you want to update from the stock update, you will lose root. then all you have to do is flash a custom recovery then flash the latest supersu in your recovery. it takes about 3-4 minutes of work(without toolkits)..
Click to expand...
Click to collapse
Ok. So you are saying that I can unroot, upgrade to 4.4.1, then flash a backup recovery from something like TWRP and be all set? I was under the impression that flashing a custom recovery will also wipe out the current OS version.

shampiaj said:
Ok. So you are saying that I can unroot, upgrade to 4.4.1, then flash a backup recovery from something like TWRP and be all set? I was under the impression that flashing a custom recovery will also wipe out the current OS version.
Click to expand...
Click to collapse
flashing a custom recovery doesnt wipe anything(except the stock recovery). unlocking the bootloader wipes data, not the recovery

simms22 said:
flashing a custom recovery doesnt wipe anything(except the stock recovery). unlocking the bootloader wipes data, not the recovery
Click to expand...
Click to collapse
Thanks.

Doesn't ADB side-loading still work with custom recovery?

You need to unroot
shampiaj said:
I have a N5 stock/rooted. Does this mean I will have to unroot just to update my phone to KitKat 4.4.1 when it comes out? I would prefer to keep the stock ROM but want the camera upgrades that 4.4.1 is supposed to offer.
Click to expand...
Click to collapse
Yes, you need to unroot to recive the OTA, in my case, i have a custom rom, so i will go stock if the update improves perfomance,because i have installed the camera fix v 1.3 and I'm happy with it

jt3 said:
Doesn't ADB side-loading still work with custom recovery?
Click to expand...
Click to collapse
I was just about to copy the steps you posted before your edit! If side loading works for OTAs (which i need the answer for as well), that writeup you had posted would've been clutch!

AceKingNYC said:
I was just about to copy the steps you posted before your edit! If side loading works for OTAs (which i need the answer for as well), that writeup you had posted would've been clutch!
Click to expand...
Click to collapse
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
EDIT: In my original response post, I'd noted that the OP was obviously familiar with ADB, since he'd rooted his Nexus, I left that out of this post, so if you're wondering what the heck ADB is, that's why this post seems incomplete. ADB is part of the Android SDK. There are many other threads that cover its installation and use, but it's a good tool to have, even if you don't root (for side-loading updates, via the above steps, for example... no root required!).

jt3 said:
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
Click to expand...
Click to collapse
That would be key if this works... guess we shall have to wait and see. So with this method you theoretically won't have to unroot/re-root or lose any data/settings, correct?

shampiaj said:
That would be key if this works... guess we shall have to wait and see. So with this method you theoretically won't have to unroot/re-root or lose any data/settings, correct?
Click to expand...
Click to collapse
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.

jt3 said:
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
Click to expand...
Click to collapse
Yeah, I'm stock/rooted but have flashed some mods. Luckily I keep all the .zip files so it sounds like the worst case scenario is that I'd have to re-flash the mods and re-root, which isn't a big deal. And I always make a nandroid before I do something. I'm more worried about data loss since it's taken me weeks to get to where I am now
Thanks for all this information, dude.

There's going to be boat loads of these exact same threads all over General, Q/A and Development when the update is released. Not sure why there isn't a sticky pertaining to OTA updates with regard to root, recovery, etc to curb all these posts.
To the OP, just use ADB and manually flash the images you want. Then simply flash SuperSU in recovery. Done.
If you don't know how to use ADB, then you need to do yourself a favor and learn about it. It'll save you time in the long run and you'll realize that GUI and CLI toolkits aren't necessary.

jt3 said:
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.
Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.
---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------
Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.
Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
Click to expand...
Click to collapse
This is super clutch ! I thanks alot for this
Im rooted/unlockled BL and have TWRP. I havent done ANYTHING else, not even Titanium backup for fear it would affect my ability to OTA. So it seems that I should be good right?

I will almost certainly sideload the update, as I've never had a device get an OTA less than a week after it has gone live.
Assuming a bone-stock, unrooted Nexus 5, should I consider returning the phone to the factory-set Dalvik JIT instead of the ART compiler (been using this since day one) prior to side loading the downloaded OTA update (when that becomes available)?
Sent from my Nexus 5 using Tapatalk

Guys, maybe I missed something, but I did a totally different thing on my Nexus 7. When The first release of 4.4 released, I flashed manually with flash-all.sh. Then I flashed TWRP, and rooted my N7. Couple of days later I received OTA update, I didn't do anything just clicked to the flash update. It is reboot my device, and the OTA successfully installed automatically from the TWRP, and rebooted my N7. After this I reboot my device to TWRP and flashed the superuser.zip. I rebooted the N7 and everything works well.
This way is not possible to receive and install the next OTA for N5?
Sent from my Nexus 7 using Tapatalk

Okay, got the 4.4.1 update. Here's the scoop.
My N5 is unlocked and rooted with CWM. I've installed one root application, which increases my vibrate intensity to 100% (N5 is defaulted to 63%), otherwise, i'm bone stock.
Applied sideload via directions I posted previously. There are a couple steps that change due to the different recovery, but they were easy to figure out (like, where to choose "update from sideload"). Once I rebooted after the sideload, I got the "Android is upgrading" message (good sign). Once it finished, I was running 4.4.1. (KOT49E).
I did lose root though. A quick reboot into recovery mode showed that I'd lost CWM too, and was back to the stock recovery. Reinstalled CWM and rerooted. Back to normal.
Here's the link, for anyone who wants it: KRT16M to KOT49E Update.

I have it on root and CWM also. I get to the step of install from sideload. I use CWM to say "install from sideload" and it starts ADBd but i can't connect to it via the pc. If i am in just android i can ADB. So something is up there.

jt3 said:
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.
Download the update.zip from Google to your PC that you would like to install on your Nexus.
Move the file into your Platform-Tools folder.
Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.
To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.
Type: adb devices
You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.
Still at the command prompt, type: adb reboot bootloader
Your device will now reboot to the bootloader.
Use Volume Down on your device to until you see “Recovery.”
Select it with the Power button.
Your device will boot to an Android logo with a exclamation mark.
To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).
You will now be in stock recovery.
With Volume Down, highlight “apply update from ADB.” Press Power to choose it.
Back to your PC command prompt, type: adb sideload <filename of update.zip>
If your adb is working properly, you should see the file transfer to your device in adb.
Once that finishes, your device will begin to update. Be patient, it takes a bit.
Once it has finished, simply reboot and enjoy the update.
Click to expand...
Click to collapse
jt3 said:
Okay, got the 4.4.1 update. Here's the scoop.
My N5 is unlocked and rooted with CWM. I've installed one root application, which increases my vibrate intensity to 100% (N5 is defaulted to 63%), otherwise, i'm bone stock.
Applied sideload via directions I posted previously. There are a couple steps that change due to the different recovery, but they were easy to figure out (like, where to choose "update from sideload"). Once I rebooted after the sideload, I got the "Android is upgrading" message (good sign). Once it finished, I was running 4.4.1. (KOT49E).
I did lose root though. A quick reboot into recovery mode showed that I'd lost CWM too, and was back to the stock recovery. Reinstalled CWM and rerooted. Back to normal.
Click to expand...
Click to collapse
So steps 13 and 14 in your list were done in CWM recovery instead of the stock recovery, correct? So if you're attempting the sideload using a custom recovery (I have TWRP), step 14 will be just choosing "apply update from ADB" or similar depending on which recovery you use. Everything else should be the same. Just wanted to make sure I understood your steps before attempting it myself.
Thanks!
---------- Post added at 01:12 PM ---------- Previous post was at 01:02 PM ----------
Alternatively, could we just grab the stock recovery image for 4.4 and reflash that using fastboot and apply the OTA when it lands on the phone? I'm thinking about doing that for my wife's Nexus 4.

Has anyone else lost 'reboot' from the power menu? I did have the Advanced 4 way reboot menu mod installed, but restored stock menu before TWRPing the update. It this a side effect of that or just 4.4.1?

[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.

Device unauthorized in Recovery mode

I am looking for help as I cannot find anything on the Internet.
Situation:
I have rooted Pixel with December updates. I thought that it is high time to update it to February security updates.
I was trying to use OTA update and according to instruction ( https://developers.google.com/android/ota ) I should reboot to Recovery mode.
I am using Windows 10 x64.
Problem:
In Recovery mode I cannot connect via adb to phone. I am getting:
C:\WINDOWS\system32>adb devices
List of devices attached
0B041JEC216220 unauthorized
What is strange is fact that before I restarted to Recovery I had no problem and I even used adb to reboot to Recovery using below commands:
C:\WINDOWS\system32>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
0B041JEC216220 device
C:\WINDOWS\system32>adb reboot recovery
Tried solutions:
1. Removing adb keys on PC and Phone not helping.
2. Revoking USB debugging authorizations
3. Disabling / enabling USB debugging
4. Removing LeMobile ADB driver and installing official from https://developer.android.com/studio/run/win-usb
Any ideas what I can do next?

Are your platform tools up to date? You should be on 30.0.5.
Do you have a fastboot connection?
You could always remove the -w with a text editor and flash-all with the factory image

Edmontonchef said:
Are your platform tools up to date? You should be on 30.0.5.
Click to expand...
Click to collapse
Yes, I have the newest one.
Edmontonchef said:
Do you have a fastboot connection?
You could always remove the -w with a text editor and flash-all with the factory image
Click to expand...
Click to collapse
Yes, I have and I thought about it too, but I was afraid about such "dirty" flash. It seems that there is no other way, so I will try it and let know if adb is fixed after flash.

I did flash without -w and for adb in Recovery mode the same situation. At least I have updated ROM and it seems that everything works. Thanks!

I'm having the same issue...
TomekUser said:
I did flash without -w and for adb in Recovery mode the same situation.
Click to expand...
Click to collapse
you did what?
man, i miss the times where anyone could update his google phone without being a developer

When you download the stock rom from Google website and unpack the zip file, you will find there script flash-all.
In side that script one of the last commands has -w flag. If you don't want to wipe your user partition you can remove it, save the script and run it to flash the new stock.

ok, worked for me but lost root

narf0815 said:
ok, worked for me but lost root
Click to expand...
Click to collapse
Because you flashed stock rom - no surprise here. Patch boot.img with magisk or take the one which are published on forum and flash it one more time.

the one from here?
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com

narf0815 said:
the one from here?
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't have time to read whole thread to verify it. For sure you can find version matching your system version here:
[Stock/Rooted Boot Images] Pixel 4a [NOV 02]
We have stock factory boot images, I'm only posting the latest builds. The rooted android 10 images are rooted with latest Magisk 20.4 The rooted 11 images are rooted with latest Magisk Canary 4e0a3f5e You will still need to install the...
forum.xda-developers.com

i'm on p5 (wasn't even aware this is a p4a thread ) and i was able to patch the boot.img from stock image. thanks!

TomekUser said:
I did flash without -w and for adb in Recovery mode the same situation. At least I have updated ROM and it seems that everything works. Thanks!
Click to expand...
Click to collapse
did you find a solution for the original problem in the end?
i flashed the complete firmware then as well, just as you did, but i’m still curious as to why my devices (our devices) remain "unauthorized" in stock recovery. tried all of the mentioned solutions as well, no luck, perfectly "authorized" in the os itself, as well as in fastboot mode, just not in recovery ..

frank93 said:
did you find a solution for the original problem in the end?
i flashed the complete firmware then as well, just as you did, but i’m still curious as to why my devices (our devices) remain "unauthorized" in stock recovery. tried all of the mentioned solutions as well, no luck, perfectly "authorized" in the os itself, as well as in fastboot mode, just not in recovery ..
Click to expand...
Click to collapse
No, I did not

TomekUser said:
No, I did not
Click to expand...
Click to collapse
after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.

Try adb kill-server
Then adb start-server
fastboot reboot bootloader
Fastboot Devices
She should be authorized

frank93 said:
after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.
Click to expand...
Click to collapse
Sir you have no clue how much it is helpful for everyone like me who were scratching their heads on this error.

frank93 said:
after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.
Click to expand...
Click to collapse
your a life saver. I was totally stuck in recovery for updating ota of pixel 6 pro.

A simple solution is to unplug usb cable from phone.
kill the adb server: adb kill-server
restart the server: adb start-server
boot your phone into recovery mode.
select update using ADB.
once is ask for the package plug your phone back into the usb
type: adb devices.
Its should show your device and state sideload instead of unauthorized...
then type: adb sideload (package name.zip)
Hope this helps...

just hold Vol- during boot, login in safe mode, plug cable, authorize, profit. you can also simply reboot in full root mode afterwards as magisk already sorted out the problem.
-> all modules are disabled for your convenience, no need to delete and reinstall modules, just tick box again to reenable
-> phone is an airplane mode for your convenience, so that you don't leak some info w/privacy plugins temporarily off

I got the similar issue
> adb devices
abcdefgh device
> adb reboot fastboot
> fastboot reboot recovery
> adb devices
abcdefgh unauthorized
Do you know how to fix the device unauthorized in recovery mode?

Help: OTA Update bricked my rooted phone

;Just going to spell out exactly what I've done and what's happening, partly to get my own story straight.
KB2005 running Android version 11.0.9.9.KB055A
Rooted with Magisk, TWRP not installed
This morning, got OP8T Security update for 11.0.10.10.KB05AA
I read the instructions on how to OTA update rooted phones, and followed them carefully:
Spoiler: Step-by-step description of my actions
Restored Stock Boot Image in Magisk
Pressed "Uninstall Magisk" button
Selected "Restore images"
Installed OTA Update, but did not reboot
Restored Root in Magisk Manager
Pressed "Install" button
Selected "Install" option
Selected "Install to Inactive Slot (After OTA)"
Selected "Let's Go" to confirm
Once complete, selected "Reboot" button
After rebooting, my wifi no longer worked.
Checked Settings > System
Still said 11.0.10.10 Update available
Checked Magisk
Don't recall exactly what I did next
I may have restored stock image in Magisk to retry the OTA update
Then the OTA Update rebooted my phone
What's happening now:​Phone boots to recovery:
Boot reason:
Boot reason: fs_mgr_mount_all
Unable to parse kernel log. For more debug information,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
>adb devices
List of devices attached
e0260e42 unauthorized
>adb pull /mnt/vendor/op2/rbr_log
adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
When I reboot to fastboot, the screen says:
FastBoot Mode
PRODUCT_NAME - kona
VARIANT - SMB UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - e0260e42
SECURE BOOT - yes
DEVICE STATE - unlocked
>fastboot devices
returns no response
Halp!

cheshyre said:
;Just going to spell out exactly what I've done and what's happening, partly to get my own story straight.
KB2005 running Android version 11.0.9.9.KB055A
Rooted with Magisk, TWRP not installed
This morning, got OP8T Security update for 11.0.10.10.KB05AA
I read the instructions on how to OTA update rooted phones, and followed them carefully:
Spoiler: Step-by-step description of my actions
Restored Stock Boot Image in Magisk
Pressed "Uninstall Magisk" button
Selected "Restore images"
Installed OTA Update, but did not reboot
Restored Root in Magisk Manager
Pressed "Install" button
Selected "Install" option
Selected "Install to Inactive Slot (After OTA)"
Selected "Let's Go" to confirm
Once complete, selected "Reboot" button
After rebooting, my wifi no longer worked.
Checked Settings > System
Still said 11.0.10.10 Update available
Checked Magisk
Don't recall exactly what I did next
I may have restored stock image in Magisk to retry the OTA update
Then the OTA Update rebooted my phone
What's happening now:​Phone boots to recovery:
Boot reason:
Boot reason: fs_mgr_mount_all
Unable to parse kernel log. For more debug information,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
>adb devices
List of devices attached
e0260e42 unauthorized
>adb pull /mnt/vendor/op2/rbr_log
adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
When I reboot to fastboot, the screen says:
FastBoot Mode
PRODUCT_NAME - kona
VARIANT - SMB UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - e0260e42
SECURE BOOT - yes
DEVICE STATE - unlocked
>fastboot devices
returns no response
Halp!
Click to expand...
Click to collapse
For future reference: https://forum.xda-developers.com/t/updates-thread.4188149/post-85517871
Comments:
- stock recovery doesn't support adb connectivity
- I also lost bootloader/fastboot connectivity after the 10.10 update, but it was a simple matter of updating the driver in Windows (Device Manager>Update driver for the device>Browse my computer>Let pick from list>Android bootloader interface).
- you may be able to get the phone to start if you restore the stock 10.10 boot image (attached, md5: 6fa5cc81a8e7e2878ac220e4216d4a52)
- otherwise you may need to use the MSM tool.

BillGoss said:
- I also lost bootloader/fastboot connectivity after the 10.10 update, but it was a simple matter of updating the driver in Windows (Device Manager>Update driver for the device>Browse my computer>Let pick from list>Android bootloader interface).
Click to expand...
Click to collapse
Because I'm now double- and triple-checking everything before I make a change...
Driver version is 11.0.0.0 - is that the latest? And, if not, where can I get the update?
[Also, the driver says manufacturer is "LeMobile" -- is that correct?]

Oh thank gd - fastboot devices is now listing my device...
(I also noticed an new release of platform-tools on developer.android.com which I installed)
I feel so much more hopeful

cheshyre said:
Because I'm now double- and triple-checking everything before I make a change...
Driver version is 11.0.0.0 - is that the latest? And, if not, where can I get the update?
[Also, the driver says manufacturer is "LeMobile" -- is that correct?]
Click to expand...
Click to collapse
I have the Google USB drivers installed. See https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/

Hokay, so, I've been proceeding very deliberately, trying to look at all the options before taking action...
After updating my PC's driver & adb, I was able to
Code:
fastboot boot twrp.img
Poking around at the various menu options, without (yet) making any changes (I think)
Thru TWRP's terminal, I grabbed md5sums for the various boot.imgs on my devivce, and compared them to the ones previously pulled or downloaded to my PC:
/dev/block/by-name/boot_a matched 11.0.9.9.KB055A patched by Magisk
/dev/block/by-name/boot_b matched the stock 10.10 boot image attached above
/dev/block/bootdevice/by-name/boot same as boot_a
Also, TWRP's Reboot menu said Current Slot = A
Following BillGoss's advice above (which hasn't led me astray yet), Reboot > Slot B seems like the logical next step. Right?
(What does "Fix Recovery Bootloop" under Advanced do?)

cheshyre said:
Hokay, so, I've been proceeding very deliberately, trying to look at all the options before taking action...
After updating my PC's driver & adb, I was able to
Code:
fastboot boot twrp.img
Poking around at the various menu options, without (yet) making any changes (I think)
Thru TWRP's terminal, I grabbed md5sums for the various boot.imgs on my devivce, and compared them to the ones previously pulled or downloaded to my PC:
/dev/block/by-name/boot_a matched 11.0.9.9.KB055A patched by Magisk
/dev/block/by-name/boot_b matched the stock 10.10 boot image attached above
/dev/block/bootdevice/by-name/boot same as boot_a
Also, TWRP's Reboot menu said Current Slot = A
Following BillGoss's advice above (which hasn't led me astray yet), Reboot > Slot B seems like the logical next step. Right?
(What does "Fix Recovery Bootloop" under Advanced do?)
Click to expand...
Click to collapse
(done) Can anyone share 11.0.8.12.KB05AA boot.img
Boot loop after incremental OTA (magisk restore image and repatch). So... can someone Success upgraded share the boot.img ? Thanks.
forum.xda-developers.com
I have exact same experience when update to 11.0.8.12.
Incremental OTA will not install if your system are modified, but your boot_a is patched, i guess you magisk patch inactive slot before OTA reboot, some how it patched current slot, maybe flash stock 11.0.9.9 boot.img to slot_a can solve it.

cheshyre said:
Hokay, so, I've been proceeding very deliberately, trying to look at all the options before taking action...
After updating my PC's driver & adb, I was able to
Code:
fastboot boot twrp.img
Poking around at the various menu options, without (yet) making any changes (I think)
Thru TWRP's terminal, I grabbed md5sums for the various boot.imgs on my devivce, and compared them to the ones previously pulled or downloaded to my PC:
/dev/block/by-name/boot_a matched 11.0.9.9.KB055A patched by Magisk
/dev/block/by-name/boot_b matched the stock 10.10 boot image attached above
/dev/block/bootdevice/by-name/boot same as boot_a
Also, TWRP's Reboot menu said Current Slot = A
Following BillGoss's advice above (which hasn't led me astray yet), Reboot > Slot B seems like the logical next step. Right?
(What does "Fix Recovery Bootloop" under Advanced do?)
Click to expand...
Click to collapse
I have no idea what "Fix Recovery Bootloop" does. I've never had a recovery bootloop and that option wasn't present on my old phone.
Anyway, two things you can try:
- boot slot b and see if the system comes up cleanly now that it has stock 10.10 boot image.
- if that fails see if booting slot a comes up on 9.9 again.
If neither work it's back to MSM to reset things.

@cheshyre, you keep writing "11.0.9.9.KB055A" which I've assumed to be
"11.0.9.9.KB05AA". Can you please confirm what version you are actually running?

You're correct, my original notes did say 11.0.9.9.KB05AA;
I must've transcribed it incorrectly somewhere along the line and then kept recopying the truncated number.
I think I'm going to try booting to Slot B, which appears to have stock 11.0.10.10.KB05AA, unless somebody tells me not to very soon...

I dealt with this issue on my 3T by simply never updating it; still running build A3000_28_170104;
If AT&T hadn't forced me to update my device so they can retire 3G, I'd prolly still be using it

Changed the situation, at least...
As I said I was going to do above, I fastbooted into TWRP and selected Reboot Slot B
Now I'm stuck on a screen which says
QUALCOMM CrashDump Mode
--------------------------
de-verity device corrupted Force Dump
kernel_restart
Even long-pressing the power button won't turn it off.
(Optimistically) Next steps?

(Finally managed to power off my phone by holding both power and volume-up)

cheshyre said:
(Finally managed to power off my phone by holding both power and volume-up)
Click to expand...
Click to collapse
Yep, power+vol up gets you out of CrashDump.
You could try booting slot a.

So far, every reboot takes me back to QUALCOMM CrashDump, even with vol buttons pressed.
adb devices & fastboot devices show nothing.
I have a PC utility called USBLogView which shows all Plug & Unplug events.
My "Device Description" is no longer "OnePlus 8T" or "ADB Device" -- it's listed as "QUSB_BULK_SN:989F2271"
However, the device serial # is still being listed.
Going to try some other driver tests, but I'm nearly out of spoons for tonight.
Thanks for all your help so far, and any further suggestions are more than welcome.

cheshyre said:
So far, every reboot takes me back to QUALCOMM CrashDump, even with vol buttons pressed.
adb devices & fastboot devices show nothing.
I have a PC utility called USBLogView which shows all Plug & Unplug events.
My "Device Description" is no longer "OnePlus 8T" or "ADB Device" -- it's listed as "QUSB_BULK_SN:989F2271"
However, the device serial # is still being listed.
Going to try some other driver tests, but I'm nearly out of spoons for tonight.
Thanks for all your help so far, and any further suggestions are more than welcome.
Click to expand...
Click to collapse
One procedural "suggestion": use the reply button to respond to posts. That way the author receives a notification of your reply. Also use @ in front of user names so that they get notified when mentioned.
The other: you'll need to install the Qualcomm USB driver to use the MSM tool. That will allow the PC to recognise your phone in EDL mode and the MSM tool can reset your phone.
Go to the MSM Tool thread for all the details.

Thank you so much for all your help.
Trying to find the correct firmware version right now (most links & repos only have older builds)
Which do you think I should use, since 1 slot had 9.9, and the other had 10.10?

cheshyre said:
Thank you so much for all your help.
Trying to find the correct firmware version right now (most links & repos only have older builds)
Which do you think I should use, since 1 slot had 9.9, and the other had 10.10?
Click to expand...
Click to collapse
What you're running now has no bearing on MSM as it gets completely overwritten. I use the latest KB05AA MSM Tool.
And, you are still not using the Reply button

BillGoss said:
What you're running now has no bearing on MSM as it gets completely overwritten. I use the latest KB05AA MSM Tool.
And, you are still not using the Reply button
Click to expand...
Click to collapse
*sigh*
Automatic detection of DDR failed
Waiting for device
I'll take this over to the other thread, I suppose
(and fwiw, I did press "reply" that last time, but deleted the quoted text - that must've invalidated the "reply" tagging)

cheshyre said:
...
(and fwiw, I did press "reply" that last time, but deleted the quoted text - that must've invalidated the "reply" tagging)
Click to expand...
Click to collapse
It's not the button pressing that creates the notification, but the inclusion of the user name in the Quote tag. Ditto for the use of User tag when mentioning people with @+username.
See https://forum.xda-developers.com/help/bb-codes/

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