Related
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.
[GUIDE] NOOB-Friendly STEP-BY-STEP Instructions to Install Monthly OTA updates on Rooted Essential PH-1
Introduction: I know there are many threads already posted that answer how to install OTA on rooted devices but unfortunately they get lost in massive threads that are often not NOOB friendly. I do not claim to be an expert but I have spent a long time reading threads and found the method I will detail below the easiest for me to follow on a monthly basis. I will do my best to give credit where credit is due to the original authors but my apologies in advance if I miss anything.
Just to start the prerequisites I have are a Windows 10 PC, Essential PH-1, with Stock OS and stock unlocked Bootloader. I have tried using TWRP in the past but I found this method simpler. I don't know whether my instructions will work for you or not if you already have TWRP installed but I can let one of the experts respond and I will be happy to update the guide based on feedback.
Part 1 - Downloads
Start by downloading the following items and storing them locally on your PC if you don't have them already
Download the latest OTA Monthly build from here: https://www.essential.com/developer/current-builds Note: Just check off that you are looking for "Current Builds" and click "Submit Form" and then click "Download (OTA)" link beneath the newest release you want.
Download the newest stock boot image here from bmg1001's google drive Credit:bmg1001
(FIRST TIME ONLY) Download and install the Windows driver (if you don't already have on your computer) from here: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
(FIRST TIME ONLY) Download ADB tool (if you don't have already on your computer) from here: https://developer.android.com/studio/releases/platform-tools.html This link is directly from Essentials site here in their "Before Sideloading" section it is the link entitled "You'll need the latest ADB tool"
To continue you must have developer options USB Debugging enabled which I presume was already done previously if your phone is rooted but if not you must do so before proceeding.
To Enable Developer Options: Settings App> System> About Phone> Scroll Down to Bottom and tap 7 times on the "Build Number"
To Enable USB Debugging: Settings App> Developer Options> USB Debugging (Set to Enabled)
Part 2 - Sideload the OTA Update
DISCLAIMER: This method if done properly should not wipe any of your data, however I take no responsibility and it is always advisable to back up your data before proceeding with any updates if you wish. I will be honest that I have now done this several times and never had any issues.
Unzip the ADB tool (link above in downloads section is for "platform-tools") and save it to a folder easily accesible on your computer (for this demonstration I will use "C:\platform-tools")
Copy the OTA update file to your ADB folder i.e. "C:\platform-tools" and rename it "OTAupdate.zip" (it is not necessary to rename it, just makes this simpler for the guide)
Verify the checksum of the image. I use hashtab which allows you to right click on any file and click properties and see the hashes as a tab in the properties menu. The SHA-256 is listed right under the OTA download link just copy and paste it in to the hashtab to verify
Remove your PIN / Password before sideloading by going to Settings> Security & Location> Screen Lock> Set it to None (this probably isn't necessary I just do it as a precaution)
Plug Essential Phone into computer and make sure that it says USB Debugging Enabled
Open the folder "C:\platform-tools" in Windows File Explorer and hold shift and right click in the window and you select the option "Open Powershell window here" from the context menu (works in Windows 10 can't speak for earlier Windows versions). If you don't see it the first time Shift+right click on a different part of the empty white window and you should see it appear.
Verify your device is properly connected by typing
Code:
adb devices
and you should see your device listed
Type
Code:
adb reboot recovery
Note:If you're unable to use ADB to reboot into recovery, you can use the key combination for your device. While device is off to boot into Recovery mode, press and hold Volume-Up button while pushing Power button to boot.
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen. Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command:
Code:
adb devices
Then check that your device shows up with “sideload” next to its name
Run the following command:
Code:
adb sideload OTAupdate.zip
where OTAupdate.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
At this point you should have a stock updated essential device but without root. The remainder of this guide will use Magisk to restore your device to root.
Part 3 - Re-root your Device with Magisk
Copy newest boot image from here that you downloaded earlier to a folder directly on your phone. I personally put it in my "Download" folder on my phone so I can find it easily
Open Magisk Manager and click Install>Install>Patch Boot Image
Select the boot image from step 1 and then let Magisk proceed in creating a patched image file
Copy the file "magisk_patched.img" file that Magisk just created from your device back to the computer and put it in the ADB folder "C:\platform-tools"
Plug in phone and open powershell same as before (shift+ right click> Open Powershell window here)
Type
Code:
adb reboot bootloader
to reboot your phone into fastboot
Confirm your phone is in fastboot by typing
Code:
fastboot devices
Then check that your device shows up with “fastboot” next to its name
Execute the command
Code:
fastboot flash boot magisk_patched.img
Restart your phone and you are done! Don't forget to put your phone PIN/Password back if you disabled security in the earlier step.
You should now have a successfully updated phone with full ROOT access with Magisk. I know that this guide seems like a lot of steps but it really goes very quickly, I just tried to be detailed and NOOB-Friendly.
Hope this helps all of my fellow XDA members!! Please share any and all feedback. Thanks!
Full credit goes to this thread for helping me with everything: [GUIDE] Rooting your Essential PH-1
The way I do *updates* is different (not the initial TWRP/ root).
I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.
Boot to TWRP, and do a complete nandroid.
Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.
This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.
The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.
The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.
I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]
If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.
One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
The way I do *updates* is different (not the initial TWRP/ root).
I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.
Boot to TWRP, and do a complete nandroid.
Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.
This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.
The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.
The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.
I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]
If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.
One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
you know i just finished writing my own guide to do it after i had trouble with the sticky posts. for me, magisk couldnt find the stock boot so i had to pretty much redo it. i did most things with back-to-stock and fastboot. but now i really wanna try your method through twrp. i been using the patched_twrp_magisk_stock.img images which have twrp and magisk in the same image. using your method, in twrp, could i flash the ota, the patched_twrp_magisk_stock.img, switch slots in twrp, flash patched_twrp_magisk_stock.img again, then switch back to the original slot and reboot system? thanks!
this thread has the patched_twrp_magisk_stock.img images
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
@andypiznti
There's no need to manually switch slots. And no reason to flash the TWRP *installer* file twice. The first time it runs, it patches both slots.
IMHO, trying to control slots is what gets people into trouble.
I do pay attention to what slot I'm on before I start though. In TWRP, if you go to the reboot menu, it will tell you. But the way I flash, I stay on the slot I started with. The OTA will always flash to the opposite slot - which should be the inactive slot. Flashing the TWRP *installer* file just once, patches both slots.
Just wipe dalvik (and cache but there is no cache partition so it will error - just ignore the error) then reboot to system like we've done after custom ROMs for years.
The next boot, the bootloader knows to switch to the slot with the newest OS.
After a successful boot, when you return to TWRP, you'll see the slot is the opposite one from when you started. But you didn't need to do any slot switching.
Don't force things. Let the slots take care of themselves.
I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.
Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...
ktmom said:
@andypiznti
I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.
Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
ok that answers a lot. thanks! the guide i made for myself had me flashing the stock image with bts. i was curious about the full boot after an update, i was thinking the same thing in that it might cause problems with magisk, but i also thought twrp would cause problems too. the reason i mentioned switching slots and flashing is the all-in-one img only flashes to one slot at a time, i believe.
heres my guide for reference, its kinda long. but these were the exact steps i followed and was successful. had to flash the img twice, kept rebooting into recovery if i didnt.
Applying OTA for Essential Phone when Magisk doesn't have stock boot
Boot to recovery with Magisk
Back up at least system and boot
Boot to bootloader with TWRP
Extract back to stock (BTS) for CURRENT INSTALLED VERSION, not the update BTS version
Once in bootloader, connect phone->old phone plug, SSD plug
Run flashallnowipe.bat, once bootloader reboots, select Start, unplug phone
Uninstall Magisk like a regular app
Do OTA->settings->advanced->system update
after reboot->reboot while holding volume down until in download/fastboot mode
***REMEMBER!! Flash on the opposite slot of the current slot
***so if im on slot a, flash slot b.
make sure to extract Essential_ADB_and_FASTBOOT.zip in BTS folder then->cmd-here.exe
fastboot getvar current-slot
***
fastboot flash boot_a dec_patched_twrp_magisk_stock.img
fastboot flash boot_b dec_patched_twrp_magisk_stock.img
***Switch to other slot
fastboot --set-active=a
fastboot --set-active=b
***Just to double check, REMEMBER!! Flash on the opposite slot of the current slot
fastboot getvar current-slot
***
fastboot flash boot_a dec_patched_twrp_magisk_stock.img
fastboot flash boot_b dec_patched_twrp_magisk_stock.img
***Switch back to orig slot
fastboot --set-active=a
fastboot --set-active=b
On the phone fastboot menu, select Start, unplug phone
Manager asks if you wanna install it, no, it downloads the wrong one, maybe works now?
Install Magisk Manager->https://github.com/ianmacd/MagiskBuilds
IT HAS TO BE THIS APK, Download any apk version from above github, install
when you open Manager, then download the newest apk, dont update image
Manager and Image update daily, ignore till next month OTA
Click to expand...
Click to collapse
hssxda said:
The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...
Click to expand...
Click to collapse
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.
@andypiznti. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.
My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
I don't know what more I could do to make the point it's not necessary to work about slots in TWRP.
Click to expand...
Click to collapse
Well, all of your posts describing your method contains the word "slot" multiple times so it is obviously a relevant concern otherwise you wouldn't have mentioned it. My post did not contain the word even once...
I see no need to use TWRP. What advantage does it have?
ktmom said:
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.
@andypiznti. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.
My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
oh yes, definitely doing that next time. thanks!! i found this post thats exactly your method in a little less words.
https://forum.xda-developers.com/es...1-1-nmj20d-t3701681/post78194778#post78194778
Jeebus...
We didn't like the other 15 goddamn threads with the same topic...
XDA is cancer
what works for me at the time to flash the patched image was
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
note: i am on pie
thanks for the guide.
Really helped lots, thank you.
January update is out, who might like to patch boot.img with TWRP and Magisk?
kma_29 said:
January update is out, who might like to patch boot.img with TWRP and Magisk?
Click to expand...
Click to collapse
Go to the stock room thread
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).
https://forum.xda-developers.com/showpost.php?p=76828139&postcount=1264
morphius88 said:
OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).
https://forum.xda-developers.com/showpost.php?p=76828139&postcount=1264
Click to expand...
Click to collapse
Thanks
@bmg1001 are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip
jionny said:
@bmg1001 are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip
Click to expand...
Click to collapse
Yep, I have it in the same Google Drive folder where the other month's images are posted.
bmg1001 said:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
Click to expand...
Click to collapse
Sorry chalk that up to me not paying attention. I was looking for it after Jan but its actually the first one listed. Thanks!
bmg1001 said:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
Click to expand...
Click to collapse
Hi one more thing, this is my third time updating and rooting via this method. The last two times worked flawlessly however this time I did update the OTA but when I try to reroot and go to adb devices I see my phone listed then when I reboot recovery it does however when I try fastboot devices my phone does not show and nothing happens, any help will be appreciated
Rooting the Pixel 6a is just about as easy as any other factory unlocked pixel, but because so many people have had issues with unlocking their bootloaders, I figured I'd post my exact personal steps I took when a Pixel 6a came into my tech shop to be rooted, and I discovered the current bug with Rooting
What You'll Need:
- June 2022 Firmware OTA Update Installed at least: Do this on device. Do Not download the OTA update from google's firmware website.
- ADB/Fastboot/Google Drivers for Windows: I use this to install- ADB 15sec Installer
- Magisk Manager APK: Github - Magisk Github Releases
- Firmware Matching Currently Installed: Google FW page - Google Official Firmware Downloads - you need this for the boot.img file
- A Windows Computer
- A USB-C cable to connect to your phone to the computer
OEM Unlock Bug
With early units sold by Google, they're shipping with a bug where OEM Unlock stays grayed out. Here's the only way I got around this issue
1.) Log out of any Google Account on the device
2.) Connect to Wifi, check for updates without your sim card in the device. There is a bug where it will potentially download the update for your carrier sim
3.) At minimum, you should get the June 2022 security patch update. Run the update and remember which update it is for when you download the firmware to get boot.img
4.) When the update is finished, Factory Reset your device either from settings or Android recovery
5.) Go through Android setup without sim card in, and don't connect to wifi, finish setup without logging into a google account or anything
6.) When setup is done, connect to wifi and put your sim back in.
7.) Pay attention in your notifications for "Preparing your Device" notification.
8.) When that notification pops up, enable Developer options (tap build number a bunch of times)
9.) OEM Unlock should be possible to enable now. Also enable USB Debugging
Pre-Root Setup
1.) Install Magisk Manager from Github
2.) Use 7zip (or any other ZIP opening program) to extract the boot.img from your firmware download from google
-- the boot.img is inside another zip file that's in the download from google. very easy to get
3.) Put the Boot.img on your phones internal storage
4.) Open Magisk Manager, and select your Boot.img from internal storage. Patch the boot.img to make it a rooted boot.img
5.) With your phone connected to the computer, move the magisk_patched.img from sdcard/downloads to your computer
6.) If USB debugging is properly enabled, now you can open CMD and reboot to bootloader with
Code:
adb reboot bootloader
Unlocking the bootloader
1.) With the device connected, OEM Unlock enabled, and booted to bootloader, you can unlock the bootloader with the following command
Code:
fastboot flashing unlock
-- If nothing changes on your phone screen, use Device Manager to make sure the device is recognized via google drivers: vid here on that - Quick Fastboot Drivers Install Tutorial
2.) On your phone, use the volume keys to select Unlock Bootloader, then hit the power button, device should reboot back to bootloader
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
4.) Now you can reboot back into your device and you should be rooted!
Code:
fastboot reboot
Congrats! Now you're bootloader unlocked and rooted! GrapheneOS is already available if you want a degoogled rom, haven't seen another rom pop up yet
all done from there
updating your device when rooted
I do not have a pixel 6a specifically for this right now to confirm this will work, but on every other device with OTA's, this has been my process.
1.) Download your OTA using the system update part of Settings
2.) When it pops up and is ready to restart to finish installing the update, DO NOT CLICK RESTART IN SETTINGS/SYSTEM UPDATE
3.) Go to Magisk Manager, and select Install next to Magisk
4.) Select "Install to Inactive Slot (After OTA)
5.) When its done patching the boot partition, hit restart in Magisk
Your OTA Update is now rooted
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
ctfrommn said:
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
Click to expand...
Click to collapse
here it is and does and works perfectly well thank you for everything.
Im starting work on my custom kernel now so hopefully MVK for Bluejay will be ready in the coming days/weeks.
Zaxx32 said:
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
Click to expand...
Click to collapse
As this thread ages, not everyone will have the June 2022 update. That's why I suggested/put the steps in to do it themselves with matching firmware to what their device is on.
benji said:
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Click to expand...
Click to collapse
This DID NOT work for me. That's why I wrote this up the way I did.
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
If you're bootloader is already unlocked, you just have to flash the patched magisk boot img, correct. I wrote this up for those having issue with not having the ability even if it is an unlocked from google device
frank93 said:
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
Click to expand...
Click to collapse
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
KaptinBoxxi said:
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
KaptinBoxxi said:
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
Click to expand...
Click to collapse
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
stormcrank said:
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
Click to expand...
Click to collapse
they will warranty replace if it for sure fails still. Its a silly situation, but mistakes happen
binary**# said:
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
Click to expand...
Click to collapse
I may not be very active on XDA, but have been rooting and rom'ing devices since the palm pre, first android phone was the droid x. I've never heard of this step, its never been needed. Its an extra pointless step that is just tethered root. You don't need to do it. As long as you don't download a random Boot.img, like the one for some reason attached to a reply on this thread and get it yourself from the firmware matching your device OR flashing Magisk via TWRP/Lineage Recovery with adb sideload, there's no reason to fastboot boot the boot.img.
You may have never run into an issue flashing a boot image but I've built thousands of roms and kernels and have learned the hard way more than once to measure twice, cut once.
That said, as long as you're simply patching a stock boot.img it's likely not an issue.
Followed all steps, on SD2A.220601.003SD2A.220601.003. OEM unlock still greyed
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Voxilli said:
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Click to expand...
Click to collapse
Yes, each update will require reflashing a patched kernel for the new build.
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Good call...I guess I've never messed with that as I flash so many kernels anyway.
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
That's what I've done with my OnePlus 7T for the last three years. Any repercussions for doing it this way versus patching the kernel?
I don't wanna risk the on device ota via restoring images through magisk again
Does the following check out?
I'd greatly appreciate if someone, perhaps @V0latyle could look over it, you already helped me a lot the last time.
Download ota, as well as firmware and check if boot.img got updated (or perhaps someone on an updated phone can check but idk how to even check your boot version)
Either patch new boot.img or keep the old one at hand if it didn't get updated
Disable all magisk modules and reboot
Go to magisk -> uninstall -> restore images and reboot
Go in sideload mode and sideload the ota
Reboot to system so the ota can complete
Turn off and boot again from magisk patched boot.img
Direct install through magisk and enable modules
Reboot so modules work and done
All those reboots might not be necessary but I don't know if f.e. magisk modules immediately stop affecting the system after disabling them or if a reboot is required to fully disable them, same with unrooting, even after restoring images the current system has still root so I might need to reboot before sideloading.
I know that technically I don't need to unroot at all for sideloading to work but I really want to make this as safe as it can get.
G5-User7080 said:
I don't wanna risk the on device ota via restoring images through magisk again
Does the following check out?
I'd greatly appreciate if someone, perhaps @V0latyle could look over it, you already helped me a lot the last time.
Download ota, as well as firmware and check if boot.img got updated (or perhaps someone on an updated phone can check but idk how to even check your boot version)
Either patch new boot.img or keep the old one at hand if it didn't get updated
Disable all magisk modules and reboot
Go to magisk -> uninstall -> restore images and reboot
Go in sideload mode and sideload the ota
Reboot to system so the ota can complete
Turn off and boot again from magisk patched boot.img
Direct install through magisk and enable modules
Reboot so modules work and done
All those reboots might not be necessary but I don't know if f.e. magisk modules immediately stop affecting the system after disabling them or if a reboot is required to fully disable them, same with unrooting, even after restoring images the current system has still root so I might need to reboot before sideloading.
I know that technically I don't need to unroot at all for sideloading to work but I really want to make this as safe as it can get.
Click to expand...
Click to collapse
No need to unroot or restore images. You can disable modules if you want. Just sideload the OTA, and live boot the old patched image, then perform Direct Install in Magisk.
By the way, instead of creating a new thread, you could have asked this question in an existing one...
V0latyle said:
By the way, instead of creating a new thread, you could have asked this question in an existing one...
Click to expand...
Click to collapse
Perhaps I could have, I am hoping that this way it might be easier to find for others than having to look somewhere on the 30th post of a thread that is about a bricked device after ota.
V0latyle said:
No need to unroot or restore images. You can disable modules if you want. Just sideload the OTA, and live boot the old patched image, then perform Direct Install in Magisk.
Click to expand...
Click to collapse
mhh I see, I'm just a little scared of the ota process after what happened the last time so I wanna be like extra sure nothing can go wrong.
Doesn't help that I don't really understand what OTA's do exactly..
That I don't have to unroot when flashing factory makes sense as I'm just overwriting boot anyway.
Is an OTA the same thing essentially? Like is it basically a bunch or partitions in a zip that get flashed over whatever is there previously?
Meaning all things that could go wrong or get checked happen through the system update app rather than through the OTA itself?
Also you are saying "unroot or restore images", is that not the same thing?
And let's say boot gets updated and I live boot the older outdated image, does that not matter at all?
why do you wanna take the OTA route if you already downloaded the complete firmware package anyway? i’ll do a firmware flash (instead of OTA) without wiping each month and that’s it, i’ll even patch boot.img before flashing (and flash it directly together with the rest of the new firmware). works just fine.
frank93 said:
why do you wanna take the OTA route if you already downloaded the complete firmware package anyway? i’ll do a firmware flash (instead of OTA) without wiping each month and that’s it, i’ll even patch boot.img before flashing (and flash it directly together with the rest of the new firmware). works just fine.
Click to expand...
Click to collapse
This sounds like the "Quick Method" mentioned here:
https://www.xda-developers.com/how-to-install-ota-updates-keep-root-google-pixel-phone/
You're doing that?
frank93 said:
why do you wanna take the OTA route if you already downloaded the complete firmware package anyway? i’ll do a firmware flash (instead of OTA) without wiping each month and that’s it, i’ll even patch boot.img before flashing (and flash it directly together with the rest of the new firmware). works just fine.
Click to expand...
Click to collapse
As far as I understood sideloading OTA is the most safe and uncomplicated way
media-fort said:
This sounds like the "Quick Method" mentioned here:
https://www.xda-developers.com/how-to-install-ota-updates-keep-root-google-pixel-phone/
You're doing that?
Click to expand...
Click to collapse
yes, sounds like that’s "my way" of doing it. originally got this from a magisk-issue-comment here, basically it’s a "complete firmware flash with an already patched boot.img, no wipe", and that’s it. never done an OTA/sideload for years tbh.
G5-User7080 said:
Perhaps I could have, I am hoping that this way it might be easier to find for others than having to look somewhere on the 30th post of a thread that is about a bricked device after ota.
Click to expand...
Click to collapse
Well, I had thought there were existing guides in this section, but either I was mistaken or they've been buried.
G5-User7080 said:
mhh I see, I'm just a little scared of the ota process after what happened the last time so I wanna be like extra sure nothing can go wrong.
Doesn't help that I don't really understand what OTA's do exactly..
Click to expand...
Click to collapse
Maybe explaining it could help you. I'll do so in response to your questions below.
G5-User7080 said:
That I don't have to unroot when flashing factory makes sense as I'm just overwriting boot anyway.
Click to expand...
Click to collapse
Exactly.
G5-User7080 said:
Is an OTA the same thing essentially? Like is it basically a bunch or partitions in a zip that get flashed over whatever is there previously?
Click to expand...
Click to collapse
Regardless of whether installed through system update or via sideload, the OTA package always installs to the other slot - if you're currently running on slot A, it installs to slot B, and vice versa. See A/B (Seamless) System Updates
G5-User7080 said:
Meaning all things that could go wrong or get checked happen through the system update app rather than through the OTA itself?
Click to expand...
Click to collapse
OTA through system update doesn't always seem to work for rooted users; some have suggested that it may be necessary to restore images in Magisk to pass verification checks in order for the update to succeed. Others, like me, don't bother with the OTA updates anymore because 1) OTA through system updates just don't seem to work and 2) Magisk patching inactive slot still seems to have issues. I personally prefer to use the factory images, but the OTA method is technically safer.
OTA sideload should always work, and AFAIK it doesn't matter what state your device is in. It overwrites whatever is on the currently inactive slot; there's no need to remove modules or restore images or unroot as the boot image gets overwritten with the new boot image.
G5-User7080 said:
Also you are saying "unroot or restore images", is that not the same thing?
Click to expand...
Click to collapse
No, they aren't.
When your device boots, it loads the contents of the /boot partition into memory - ramdisk and kernel. This remains in memory while the system is running.
Hence, if the boot image has been patched, you'll boot with root.
When you perform "Restore Images" in Magisk, this uses root access to restore the unpatched image to /boot. But, since the patched boot image was already loaded into RAM, you still have root.
If you reboot at this point, you'll lose root because the now unpatched boot image is loaded into memory.
G5-User7080 said:
And let's say boot gets updated and I live boot the older outdated image, does that not matter at all?
Click to expand...
Click to collapse
Yes and no.
After an OTA update, you want to let the system boot with the new boot image. This is because the boot image has a signature that matches the system image; if these don't match, the update engine determines that the update was a failure, and will recycle you back to the original slot. So, the boot image that the system loads after the update has to be the new one. It doesn't matter if it's been patched or not - you could, for example, download the factory image, extract the boot image from it, patch the boot image in Magisk, then sideload the OTA, force your phone to boot into bootloader, and flash the new patched image.
Patching to inactive slot in Magisk is supposed to avoid all this, and can only be used if you update through system. It works like this:
You're rooted on the February release on slot A.
You restore images in Magisk, but do not reboot.
You install the OTA through system updates. This installs to slot B
When it prompts you to reboot to finish the update, instead you go back to Magisk and use Patch Inactive Slot - this uses root access to perform the Magisk patch on the new boot image in /boot_b
You then reboot, and the system switches to slot B, and loads with root because you patched the boot image.
However, this doesn't seem to be working for everyone. Some phones don't even "see" the OTA update is available for some reason.
Therefore, this is the method I recommend you use to install the OTA update:
Download the OTA update for your device from Pixel OTA Images
In Magisk, go to Reboot > Reboot to recovery
Once in recovery mode, hold Power and click Volume Up. Then, select "Apply update from ADB" and connect your phone to your computer.
On your PC, open a command line in your ADB Platform Tools folder, and type adb sideload <path to OTA zip> - to make this easier, just drag and drop the OTA zip into the command window.
Once the update completes, let your phone boot to system. You will not have root, so it won't matter if you didn't disable Magisk modules.
Let the system complete the post-update work (there's a notification with a gear icon) and get stabilized. Wait a few minutes.
Assuming you still have USB debugging enabled, use ADB to reboot to bootloader: adb reboot bootloader or you can just do it manually - reboot your device and hold Volume Down
You can now live boot an older patched boot image: fastboot boot <drag and drop patched boot image>
You should boot with root. Note: if your phone bootloops, see my note below)
In Magisk, go to Install > Direct Install. This uses the "temporary root" of the patched image you've loaded into memory to patch the new boot image
Reboot once more. You should now be on the new boot image with root.
If your phone boot loops, double check to make sure you're still on the latest update. You can check this in Settings > About, but it's also displayed on the notification windowshade under the Quick Settings tiles. Make sure this matches the OTA image you just installed. If it doesn't, this means that your device has recycled back to the "old" slot for some reason, and you'll have to start over.
If you want to play it safe, you can use this guide to extract the new boot.img from the OTA payload. You'd then patch this manually in Magisk, and after installing the update, you'd reboot to bootloader and flash to /boot.
If you still bootloop on the new boot image after patching, you probably need to disable Magisk modules. You can do this via command line:
adb --wait-for-device shell magisk -remove-images
frank93 said:
yes, sounds like that’s "my way" of doing it. originally got this from a magisk-issue-comment here, basically it’s a "complete firmware flash with an already patched boot.img, no wipe", and that’s it. never done an OTA/sideload for years tbh.
Click to expand...
Click to collapse
Damn, I tried this and it seems that my PC cannot write the image to the Pixel 6a?!
Do I have old ADB drivers or whats the reason for that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit:
Sry, I'm not involved here all the time. Figured it out myself. Reason for the failure were the freakin' platform_tools_r34. Switched to r33 and worked straight away..
https://forum.xda-developers.com/t/...el-7-pro-support-thread.4505287/post-88134573
V0latyle said:
Well, I had thought there were existing guides in this section, but either I was mistaken or they've been buried.
Click to expand...
Click to collapse
Not in the 6a forum as far as I'm aware, there might be more in the Pixel 6 forum, but I've already seen your guide that covers all kinds of methods.
V0latyle said:
the OTA package always installs to the other slot
Click to expand...
Click to collapse
Wouldn't it make sense to restore the unrooted boot partition on the currently active slot given that OTA will switch me to the currently inactive slot?
So that after the OTA procedure I'm in the same situation as now, being on a rooted slot with having the original unrooted slot as sort of "backup".
V0latyle said:
there's no need to remove modules or restore images or unroot as the boot image gets overwritten with the new boot image.
Click to expand...
Click to collapse
I think it was on the magisk ota guide but im not sure, that it said that it's important to disable all system modifying modules before attempting an update.
While all modules I use should by systemless,.. I think?.. I still think it's just easier to disable them all and re-enable them later, just to avoid trouble and make it easier to write in a guide, as in "just disable them and don't bother checking if theyre really all systemless".
V0latyle said:
After an OTA update, you want to let the system boot with the new boot image.
Click to expand...
Click to collapse
Yes, that was my intention, let it boot normally without touching anything to complete the OTA.
Didn't know I would have to wait a few minutes after already being in the system tho to wait for the notification, I'll look out for that.
V0latyle said:
In Magisk, go to Reboot > Reboot to recovery
Once in recovery mode, hold Power and click Volume Up. Then, select "Apply update from ADB" and connect your phone to your computer.
Click to expand...
Click to collapse
Is this equivalent to the way you described in your Pixel 6 guide?
As in doing adb reboot sideload to go to sideload mode, followed by adb sideload ota.zip
V0latyle said:
If your phone boot loops, double check to make sure you're still on the latest update.
Click to expand...
Click to collapse
If it bootloops how would I even get back into system?
Why would it even bootloop, if there is a known cause can't I just avoid whatever is causing it to begin with?
I mean I don't assume I'll bootloop following the steps carefully but this time I'll post and wait for replies before just nuking everything like last time ^^
V0latyle said:
If you want to play it safe, you can use this guide to extract the new boot.img from the OTA payload.
Click to expand...
Click to collapse
Yes, I'd prefer to make it as safe as possible.
Is the boot.img extracted from the OTA the same as the one from the according firmware?
Would be easier to just extract that on PC.
Oh and two more question that came to mind.
When restoring images through magisk it replaces the rooted boot partition with the stock one.
But root only disappears on next reboot.
So can I restore images and then directly do adb reboot sideload followed by doing the OTA?
Meaning I don't need to do one reboot back to system to sort of "complete the unrooting preocedure"?
Is that the same for magisk modules?
If I want to disable them just in case, do I need to reboot once after for them to like get removed from the system or are they instantly disabled the moment I press the "disable module" switch?
G5-User7080 said:
Not in the 6a forum as far as I'm aware, there might be more in the Pixel 6 forum, but I've already seen your guide that covers all kinds of methods.
Wouldn't it make sense to restore the unrooted boot partition on the currently active slot given that OTA will switch me to the currently inactive slot?
So that after the OTA procedure I'm in the same situation as now, being on a rooted slot with having the original unrooted slot as sort of "backup".
Click to expand...
Click to collapse
Not if you're going to sideload the OTA. There's no point to doing so.
G5-User7080 said:
I think it was on the magisk ota guide but im not sure, that it said that it's important to disable all system modifying modules before attempting an update.
While all modules I use should by systemless,.. I think?.. I still think it's just easier to disable them all and re-enable them later, just to avoid trouble and make it easier to write in a guide, as in "just disable them and don't bother checking if theyre really all systemless".
Click to expand...
Click to collapse
Yeah, this is the "safe" option. I just use MHPC + USNF mod + systemless hosts so I don't bother disabling, but those who use Xposed or other more "invasive" system mods might want to.
G5-User7080 said:
Yes, that was my intention, let it boot normally without touching anything to complete the OTA.
Didn't know I would have to wait a few minutes after already being in the system tho to wait for the notification, I'll look out for that.
Click to expand...
Click to collapse
This is because it seems to take a few minutes for the system to "get happy" and decide that all is well, and if you live boot an older boot image before it does so, it will assume the update failed and recycle back to the old slot.
G5-User7080 said:
Is this equivalent to the way you described in your Pixel 6 guide?
As in doing adb reboot sideload to go to sideload mode, followed by adb sideload ota.zip
Click to expand...
Click to collapse
Yep. The commands and the method is exactly the same for all Pixel devices. The only thing that is different are the files. Only the Pixel 7 / 7 Pro are slightly different in that we have to patch init_boot instead of boot.
G5-User7080 said:
If it bootloops how would I even get back into system?
Click to expand...
Click to collapse
Use the command I gave you: adb --wait-for-device shell magisk --remove-modules while booting
G5-User7080 said:
Why would it even bootloop, if there is a known cause can't I just avoid whatever is causing it to begin with?
Click to expand...
Click to collapse
There isn't a known cause, the exception being trying to boot an old boot image without letting the system complete the update post-reboot as described above
G5-User7080 said:
I mean I don't assume I'll bootloop following the steps carefully but this time I'll post and wait for replies before just nuking everything like last time ^^
Yes, I'd prefer to make it as safe as possible.
Is the boot.img extracted from the OTA the same as the one from the according firmware?
Would be easier to just extract that on PC.
Click to expand...
Click to collapse
Yes. It's just packaged differently.
Since Payload Dumper requires Python, I've found it simpler to just use the factory image - although if you're at that point, you may as well just flash the factory image anyway.
G5-User7080 said:
Oh and two more question that came to mind.
When restoring images through magisk it replaces the rooted boot partition with the stock one.
But root only disappears on next reboot.
So can I restore images and then directly do adb reboot sideload followed by doing the OTA?
Meaning I don't need to do one reboot back to system to sort of "complete the unrooting preocedure"?
Click to expand...
Click to collapse
I never suggested you'd need to reboot after restoring images. Once you've restored the original boot image, that's what is in the boot partition. It takes effect immediately. What doesn't take immediate effect is what's currently running in memory, which is why I pointed out that upon a reboot, your device will load the unpatched image because that's what's in the partition. But, as I explained above, there's no point to restoring the original boot image if you're sideloading the OTA. The only time this ever appears to be necessary is when you're taking OTA through system update.
G5-User7080 said:
Is that the same for magisk modules?
If I want to disable them just in case, do I need to reboot once after for them to like get removed from the system or are they instantly disabled the moment I press the "disable module" switch?
Click to expand...
Click to collapse
I am honestly not sure about this one, but since we are talking about OTAs, the point is moot - when the update completes and the phone reboots, it's booting an unpatched boot image, meaning there's no way for the modules to load. It doesn't matter if you've made changes to system, either, because the system partition also has two slots - system_a and system_b
The only thing that MIGHT matter is when you boot the patched image, because if you haven't disabled modules, they will load during boot, and if one of them causes a bootloop for whatever reason....It still shouldn't matter because in this case, the device -should- try to boot the same slot again, and since you never patched the new boot image, it will boot without root.
V0latyle said:
I am honestly not sure about this one, but since we are talking about OTAs, the point is moot - when the update completes and the phone reboots, it's booting an unpatched boot image, meaning there's no way for the modules to load. It doesn't matter if you've made changes to system, either, because the system partition also has two slots - system_a and system_b
Click to expand...
Click to collapse
yea it seems like its the same as restoring images, it disables them but obviously they are already loaded for the current session and probably don't get "unloaded", they just won't load again from the next boot on, so I don't think there would be any need to reboot, except when you want to do something in system that requires modules to be disabled.
So it seems like we'll have to wait til like the 20th for the march update, so I'll just go straight for the april one.
Considering what you said, would this be the correct procedure, just to confirm?
Extract boot.img from factory image and patch it, then move it to pc.
In Magisk app, disable all modules.
On pc do adb reboot sideload and after rebooting in download mode adb sideload ota.zip
Choose "reboot system" from menu or use adb reboot... does that command work in download mode?
Let it reboot, unlock, wait for the update completed notification to appear.
Confirm that adb debugging is still enabled and the version number below quick tiles matches the update, then do adb reboot bootloader.
Live boot the new magisk patched boot.img with fastboot boot patched_boot.img.
Magisk app -> Install -> Direct Install, then re-enable all modules and reboot.
done
Additionally, I'm wondering what all the different "menus" are for.
Like first there is bootloader where you can flash partitions through the fastboot command and enter recovery or boot system.
Then there is the recovery that... doesn't really do anything when it's stock?
Then there is sideload or download mode that is accessed from the recovery.
Then there is adb fastboot, does that bring you to the fastbootd screen? I have no idea what that is for.
G5-User7080 said:
yea it seems like its the same as restoring images, it disables them but obviously they are already loaded for the current session and probably don't get "unloaded", they just won't load again from the next boot on, so I don't think there would be any need to reboot, except when you want to do something in system that requires modules to be disabled.
So it seems like we'll have to wait til like the 20th for the march update, so I'll just go straight for the april one.
Considering what you said, would this be the correct procedure, just to confirm?
Extract boot.img from factory image and patch it, then move it to pc.
In Magisk app, disable all modules.
On pc do adb reboot sideload and after rebooting in download mode adb sideload ota.zip
Choose "reboot system" from menu or use adb reboot... does that command work in download mode?
Click to expand...
Click to collapse
ADB commands work in recovery mode, yes.
G5-User7080 said:
Let it reboot, unlock, wait for the update completed notification to appear.
Confirm that adb debugging is still enabled and the version number below quick tiles matches the update, then do adb reboot bootloader.
Live boot the new magisk patched boot.img with fastboot boot patched_boot.img.
Magisk app -> Install -> Direct Install, then re-enable all modules and reboot.
done
Click to expand...
Click to collapse
If you're going to download the factory image, why not just use Pixel Flasher to perform a factory flash? Contrary to popular belief, flashing the factory image itself does not wipe data. OTA updates are still the "safest" way but I've been using the factory image for a couple years now on my Pixel 5 and have never had a problem.
G5-User7080 said:
Additionally, I'm wondering what all the different "menus" are for.
Like first there is bootloader where you can flash partitions through the fastboot command and enter recovery or boot system.
Then there is the recovery that... doesn't really do anything when it's stock?
Then there is sideload or download mode that is accessed from the recovery.
Then there is adb fastboot, does that bring you to the fastbootd screen? I have no idea what that is for.
Click to expand...
Click to collapse
Bootloader is used for flashing bootloader, modem, and boot.
Recovery mode is a small kernel in of itself that can perform functions that the bootloader can't, and provides a software interface to perform a "safe" recovery should the device stop working - like flashing an OTA.
Sideload mode is part of that recovery software interface - it allows you to serve OTA files over ADB
Fastbootd is "userspace fastboot" that allows advanced flashing functions.
More information on fastbootd
V0latyle said:
If you're going to download the factory image, why not just use Pixel Flasher to perform a factory flash? Contrary to popular belief, flashing the factory image itself does not wipe data. OTA updates are still the "safest" way but I've been using the factory image for a couple years now on my Pixel 5 and have never had a problem.
Click to expand...
Click to collapse
cause I'd need to remove the -w from the update command in the flashall.bat as well as possibly add --skip-reboot
I can see the day coming when I simply forget doing that and wipe my device by accident.
Or when using pixel flasher I might just forget to untick the wipe option.
I want to use a method that ideally I only have to prepare once, say if I could just make a "flash factory without wipe" script that works every time, but due to changing version numbers I have to use the new script every time.
G5-User7080 said:
cause I'd need to remove the -w from the update command in the flashall.bat as well as possibly add --skip-reboot
Click to expand...
Click to collapse
You don't have to use the script. Learn to do the commands manually. You don't have to skip reboot either, but if you want to flash a patched boot image, it helps.
G5-User7080 said:
I can see the day coming when I simply forget doing that and wipe my device by accident.
Or when using pixel flasher I might just forget to untick the wipe option.
Click to expand...
Click to collapse
Pixel Flasher settings are persistent....
G5-User7080 said:
I want to use a method that ideally I only have to prepare once, say if I could just make a "flash factory without wipe" script that works every time, but due to changing version numbers I have to use the new script every time.
Click to expand...
Click to collapse
You seem to misunderstand how flashing the factory image works. You don't have to use the script. Learn to use ADB and fastboot commands manually. You can follow my guide for the 6 Pro here; the commands are all the same.
Otherwise, you can use Pixel Flasher. All you have to do is set it up once, and the settings persist even after updates. This is what I've gone to as a means to simply free myself for other tasks while my phone is updating; I used to do it manually.
frank93 said:
yes, sounds like that’s "my way" of doing it. originally got this from a magisk-issue-comment here, basically it’s a "complete firmware flash with an already patched boot.img, no wipe", and that’s it. never done an OTA/sideload for years tbh.
Click to expand...
Click to collapse
If you flash a full factory image via fastboot (without wiping the device in that process), is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?
And can I stay logged into my Google Account on the device before flashing as well?
I don't want to brick my device, therefore I've always deleted these Login infos before full flashing process.
But after each full flash, it's always very annoying to add all that info again, for each banking app, for Google pay and so on....
media-fort said:
If you flash a full factory image via fastboot (without wiping the device in that process), is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?
And can I stay logged into my Google Account on the device before flashing as well?
Click to expand...
Click to collapse
i never logged out or deleted anything before flashing. it "feels" like an OTA, i just flash (without wipe) and after the next boot the device is ready to be used.
media-fort said:
If you flash a full factory image via fastboot (without wiping the device in that process), is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?
And can I stay logged into my Google Account on the device before flashing as well?
Click to expand...
Click to collapse
Flashing a full firmware w/o wiping = OTA update. Since an OTA won't delete anything of your settings/data, a full firmware flash w/o wiping will do the same.
All settings, data and apps are stored on /userdata. When saying "without wiping", then it means "do not erase /userdata".
WoKoschekk said:
Flashing a full firmware w/o wiping = OTA update. Since an OTA won't delete anything of your settings/data, a full firmware flash w/o wiping will do the same.
All settings, data and apps are stored on /userdata. When saying "without wiping", then it means "do not erase /userdata".
Click to expand...
Click to collapse
Almost, but not quite.
Flashing the full factory firmware installs it to the currently active slot and can be done regardless of what version you're already on; if you try to flash the system update alone, it'll complain if it doesn't see the right bootloader and radio version but you can use --force to get around that
Flashing the OTA installs it to the currently INACTIVE slot and can only be done when you're on an OLDER version.
V0latyle said:
Almost, but not quite.
Flashing the full factory firmware installs it to the currently active slot and can be done regardless of what version you're already on; if you try to flash the system update alone, it'll complain if it doesn't see the right bootloader and radio version but you can use --force to get around that
Flashing the OTA installs it to the currently INACTIVE slot and can only be done when you're on an OLDER version.
Click to expand...
Click to collapse
yes, that's right. but regarding to the question
media-fort said:
is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?
Click to expand...
Click to collapse
it doesn't matter which slot is active.
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su
chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse
MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.
I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs