Database Info

How to handle future updates on mi a1

I present a simple step wise guide on flashing updates on mi a1.
1.Keep one systen unrooted and second rooted
2.Download update in unrooted system
3.Update will be flashed on rooted system
4.Reboot after successful updation
5.If it boots then ok
6.If doesn't boot then attach your phone with pc in fastboot mode and set_active x and reboot (here x is the updated system a /b.
7.Now you will boot into updated system.
8.Now you can flash twrp and root this system as before.
9.Your other system will again be unrooted and can be used to download updates.
Thanks and enjoy
Happy flashing
???????

Thanks for the guide .
I have updated to october patch and i also successfully rooted my device.

How to boot to a/b partition?

Rakibboss said:
How to boot to a/b partition?
Click to expand...
Click to collapse
Via fastboot command
Fastboot set_active a or b
Then fastboot reboot

Could not able to update i received october update my phone both slots are unrooted i uninstalled xposed then i relocked the bootloader but still it says installation problem?

Ranjithksr said:
Could not able to update i received october update my phone both slots are unrooted i uninstalled xposed then i relocked the bootloader but still it says installation problem?
Click to expand...
Click to collapse
Did you flashed the stock September boot img ?

aymahalawa said:
Did you flashed the stock September boot img ?
Click to expand...
Click to collapse
yes

How to know which partition is rooted in our phone?

Mr.Crucial said:
Via fastboot command
Fastboot set_active a or b
Then fastboot reboot
Click to expand...
Click to collapse
I lost the root.. i followed the instructions

Rakibboss said:
I lost the root.. i followed the instructions
Click to expand...
Click to collapse
Please read carefully.
I mentined to flash root and twrp to updated system as before in step 8

I'm not able to boot into the unrooted partition which has the August patch. Fastboot set_active b and fastboot --set_active -b doesn't work.
I've updated the slot a to September patch and rooted it as well.
Also wanted to know that with this process, if I boot into the slot b, with previous build, would I have to download the September patch(1+gb) and then the October one(118 mb)?

myksh said:
I'm not able to boot into the unrooted partition which has the August patch. Fastboot set_active b and fastboot --set_active -b doesn't work.
I've updated the slot a to September patch and rooted it as well.
Also wanted to know that with this process, if I boot into the slot b, with previous build, would I have to download the September patch(1+gb) and then the October one(118 mb)?
Click to expand...
Click to collapse
You can boot into twrp from fastboot and set active any partition from recovery.
The only drawback is that one system will remain old and you have to download full update package which will be larger in size

Mr.Crucial said:
You can boot into twrp from fastboot and set active any partition from recovery.
The only drawback is that one system will remain old and you have to download full update package which will be larger in size
Click to expand...
Click to collapse
Thanks for the clarification.
Again, will this be the same next month and the next?

I got bootloop when installing october security patch......
I have unlocked bootloader and also rooted my phone using CF-auto-root but when try to install october security update after reboot my phone got bootloop.....
So, what do i do now ?

Bhagyesh19 said:
I got bootloop when installing october security patch......
I have unlocked bootloader and also rooted my phone using CF-auto-root but when try to install october security update after reboot my phone got bootloop.....
So, what do i do now ?
Click to expand...
Click to collapse
Follow all steps carefully

im rooted in B with latest Sep...booted into A and updating to Oct. will this update slot B which is rooted as well?
then i can just set B active again and boot into twrp or flashfire and install supersu? then ill have updated Oct B with root? is my understanding clear? also A will be updated to oct or will it remain on Aug? kindly confirm asap thanks

rexisrex said:
im rooted in B with latest Sep...booted into A and updating to Oct. will this update slot B which is rooted as well?
then i can just set B active again and boot into twrp or flashfire and install supersu? then ill have updated Oct B with root? is my understanding clear? also A will be updated to oct or will it remain on Aug? kindly confirm asap thanks
Click to expand...
Click to collapse
Your b will be updated but a will remain as before.
But follow steps carefully .

Mr.Crucial said:
Your b will be updated but a will remain as before.
But follow steps carefully .
Click to expand...
Click to collapse
I updated from a and rebooted from system update screen. It rebooted to 'a' and my 'a' also got updated to Oct..but made b active and booted. It booted. But no root as expected. Rebooted to fastboot and booted into twrp, mounted system and flashed supersu and rebooted to system b...but stuck at mi splash...so again got into fastboot and booted (not flashed) cf auto root Oct boot.img. now on reboot it just booted fine and voila flash fire took root on startup!! So now I have 2 Oct slots and one rooted and another unrooted...had to setup all build.prop edits/ and system file changes to get root mods working again..but that's worth the effort...all's working and it just took flat 15mins including mods...so thanks for the idea..
for guys who are facing issues setting boot a/b active, kindly download latest fastboot and adb and use the following code
"fastboot --set-active=x" (x being a or b) there are 2 hyphen before set...

Mr.Crucial said:
I present a simple step wise guide on flashing updates on mi a1.
1.Keep one systen unrooted and second rooted
2.Download update in unrooted system
3.Update will be flashed on rooted system
4.Reboot after successful updation
5.If it boots then ok
6.If doesn't boot then attach your phone with pc in fastboot mode and set_active x and reboot (here x is the updated system a /b.
7.Now you will boot into updated system.
8.Now you can flash twrp and root this system as before.
9.Your other system will again be unrooted and can be used to download updates.
Thanks and enjoy
Happy flashing
???????
Click to expand...
Click to collapse
What if i don't have windows system, I have mac so can't take risk to get bootloop because It's not going to twrp through hardware keys, so please give solution for this

paras_143 said:
What if i don't have windows system, I have mac so can't take risk to get bootloop because It's not going to twrp through hardware keys, so please give solution for this
Click to expand...
Click to collapse
I think you can go to fastboot with hard keys then boot into twrp and follow the steps by setting active partition in twrp

[GUIDE] Rooting Mi A1 without TWRP

Device will be wiped if your bootloader isn't already unlocked.
Obviously, before doing this, you should enable OEM unlocking and ADB debugging in Developer Options. Also you should have ADB and Fastboot on your system (meaning they work on any directory). I use this version, just accept the installation of both the ADB/Fastboot drivers and the Google Device Drivers and you should be good to go.
Below you can find the untouched boot.img for the version you are on (or you can extract them yourselves, guide at the bottom of the thread):
2018:
March (V9.5.9.0.ODHMIFA) (OTA)
April (V9.5.10.0.ODHMIFA) (OTA)
May (V9.5.11.0.ODHMIFA) (OTA)
June (V9.6.2.0.ODHMIFE) (OTA)
June (V9.6.3.0.ODHMIFE) (OTA)
July (V9.6.4.0.ODHMIFE) (OTA)
August (V9.6.5.0.ODHMIFE) (OTA)
September (V9.6.6.0.ODHMIFE) (OTA)
October (V9.6.7.0.ODHMIFE) (OTA)
November (V9.6.8.0.ODHMIFE) (OTA)
December (V10.0.3.0.ODHMIFE) (OTA)
2019:
January (V10.0.4.0.ODHMIFE) (OTA)
January (V10.0.4.0.PDHMIXM) (OTA)
February (V10.0.5.0.PDHMIXM) (OTA)
March (V10.0.7.0.PDHMIXM) (OTA)
April (V10.0.8.0.PDHMIXM) (OTA)
May (V10.0.9.0.PDHMIXM) (OTA)
June (V10.0.10.0.PDHMIXM) (OTA)
July (V10.0.11.0.PDHMIXM) (OTA)
August (V10.0.12.0.PDHMIXM) (OTA)
September (V10.0.13.0.PDHMIXM) (OTA)
October (V10.0.14.0.PDHMIXM) (OTA)
November (V10.0.15.0.PDHMIXM) (OTA)
December (V10.0.16.0.PDHMIXM) (OTA)
Here we go:
GENERATING THE PATCHED BOOT.IMG
0. Download a suitable UNTOUCHED boot.img from above or extract one yourself by using the OTA links and dumping the image using the guide on the bottom of this thread.
To check which one is suitable for you go to Settings -> System -> About phone and check your build number. (e.g September 2019 one should be PKQ1.180917.001.V10.0.13.0.PDHMIXM)
1. Install Magisk Manager
2. Open the app and press Install on the prompt (It should prompt you to install the latest version).
3. Tap on Install on the prompt and then "Patch Boot Image File".
4. Select the untouched boot.img through your File Explorer. Wait for it to do its thing.
The patched_boot.img was created and it should be located at /storage/emulated/0/Download/patched_boot.img.
UNLOCKING THE BOOTLOADER
1. Move the patched_boot.img to your PC
2. Connect the device to your computer and open a Command Prompt
3. Check that ADB works with:
Code:
adb devices
Should say:
Code:
XXXXXXXXXXXX device
where the X's are a unique ID.
4. Boot into fastboot mode with:
Code:
adb reboot bootloader
(Yes you can obviously boot into bootloader by using Volume Down+Power Button etc)
5. You should be in fastboot mode. Check that it works properly:
Code:
fastboot devices
Should say:
Code:
XXXXXXXXXXXX fastboot
The device will be wiped after the next step.
6. Now we are going to unlock the device's bootloader with:
Code:
fastboot oem unlock
7. At this point the device is unlocked. Now do:
Code:
fastboot reboot
And let the phone boot
8. After booting, go into fastboot mode again with:
Code:
adb reboot bootloader
BOOTING INTO THE PATCHED IMAGE AND INSTALLATION
You should now be in fastboot mode from the last section.
1. Boot into the patched_boot.img that you generated earlier with:
Code:
fastboot boot patched_boot.img
The phone should boot normally and shouldn't take too long. For me it was the same boot time as always.
2. Now open Magisk Manager and press Install
3. When prompted tap onto Install and then choose "Direct Install (Recommended)"
Let it do its thing and then choose Reboot.
You should now have a rooted phone with Magisk without using TWRP.
Do not relock your bootloader or your device probably won't boot because you are rooted.
PAYLOAD DUMPING
Requirements: python3, protobuf (do python -m pip install protobuf after having installed python3)
1. Download the desired OTA (full OTA needed, not incremental ones, should probably be 1GB+)
2. Download the zip of the python script on github
3. Extract the script (both .py's) and inside the folder extract the payload.bin from the OTA archive
4. Now run:
Code:
python payload_dumper.py payload.bin
Wait for it to be done and you should have all the images in the same directory. With those, you can either just use the boot.img or even create a fastboot flashable OTA with a script.
Cheers!

Thank you very much, I just got my hands on the phone and wanted to root without wiping. Unfortunately when I try to patch the boot.img the resulting image is a zip file that cannot be used.

The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).

Update: I have done it, I could not generate my own patched image, so I had to use the one in the provided post. I still opted to install magisk beta instead of the normal one and there was no problem, now I'm rooted. Thanks again.
---------- Post added at 05:22 AM ---------- Previous post was at 05:21 AM ----------
sipollo said:
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Click to expand...
Click to collapse
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
---------- Post added at 05:23 AM ---------- Previous post was at 05:22 AM ----------
sipollo said:
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Click to expand...
Click to collapse
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.

clau1996 said:
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
Click to expand...
Click to collapse
With vol- trick wipes are only postponed. Don't boot in recovery mode and you'll be fine. If you boot pressing power and vol+ phone will be wiped.
If you boot temporary twrp phone will be wiped.

sipollo said:
With vol- trick wipes are only postponed. Don't boot in recovery mode and you'll be fine. If you boot pressing power and vol+ phone will be wiped.
If you boot temporary twrp phone will be wiped.
Click to expand...
Click to collapse
this is correct, I learned the hard way
I honestly don't understand all this patched boot img nonsense
ffs if you want root just BOOT into custom recovery via fastboot and then flash/install the beta magisk zip 16.7 in said custom recovery, that's it
Sent from my Nexus 6 using Tapatalk

I guess I should have included that if you boot into any recovery after doing the "bypass" procedure, the device will get wiped, as mentioned by the rest of you guys.
This "guide" is only if you don't intend to ever use TWRP or something similar. Anyway, will add it to the OP, sorry if anyone got screwed up because I didn't mention it.
sgloki77 said:
this is correct, I learned the hard way
I honestly don't understand all this patched boot img nonsense
ffs if you want root just BOOT into custom recovery via fastboot and then flash/install the beta magisk zip 16.7 in said custom recovery, that's it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I guess if someone wants to start off with a new install it's better and faster to just boot into TWRP and flash Magisk as you just said.
Guide is mainly targetted to people who don't want to wipe for whatever reason (whether that is data or anything).

clau1996 said:
Thank you very much, I just got my hands on the phone and wanted to root without wiping. Unfortunately when I try to patch the boot.img the resulting image is a zip file that cannot be used.
Click to expand...
Click to collapse
The resulting image should actually be a .img (or a .img.tar if you choose so in the settings) ?
Maybe you didn't look in the correct directory for the image (?)
Double check, because I did this procedure twice on my device and it worked that way.
Thanks for using the guide btw!
EDIT: whoops, should have merged with the other reply..

Thanks for the guide. Is it possible to update via OTA once we have the new update monthly and repeat the same process for rooting?

fernoct said:
Thanks for the guide. Is it possible to update via OTA once we have the new update monthly and repeat the same process for rooting?
Click to expand...
Click to collapse
I suppose it should be possible but I guess I will have to test it on the next OTA we get just to be sure.

hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks

lord bim said:
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
Click to expand...
Click to collapse
I don't think there's a way to bypass the wipe from Mi Flash tool, at least not that I know about.

michkost858 said:
I don't think there's a way to bypass the wipe from Mi Flash tool, at least not that I know about.
Click to expand...
Click to collapse
I mean if the full ROM of July has the same problem as in May when I unlock the bootloader

lord bim said:
I mean if the full ROM of July has the same problem as in May when I unlock the bootloader
Click to expand...
Click to collapse
Oh, yes it does. By the way, just to clarify; it's not a problem, it's a safety measure which Xiaomi implemented on the May Update and on. Otherwise your data would be at risk and easy to steal.

Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368

lord bim said:
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
Click to expand...
Click to collapse
Yes, nothing special about it

lord bim said:
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
Click to expand...
Click to collapse
After unlocking bootloader with vol- trick, if you want i uploaded last Fastboot Rom with a modified script.
You won't lose data and your bootloader will remain unlocked.
A Backup is strongly recommended (just in case).
Use Miflash.
https://1drv.ms/u/s!AnNVEh3KeCSVj94TW6xkP6Xj-CDeRg

lord bim said:
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
Click to expand...
Click to collapse
ProchyGaming said:
Yes, nothing special about it
Click to expand...
Click to collapse
I would recommend generating your own if possible.
Not sure if there's a difference tbh, however I think that, that one was patched for 16.0 and not 16.7 which makes it freeze up sometimes during boot.

thanks to all the valuable inputs the op and other have given here, so conclusion in you can install magisk without wiping data by this method, but your data will be erased the next time you boot into recovery. Also, one cannot be sure about otas as ota might trigger recovery for some stuff and then the data will be wiped. The only viable option is to just backup your data, either by titanium backup after installing magisk like mentioned in the op or just manually save necessary stuff somewhere, permanently unlock, flash twrp and then flash magisk.

One question though, why do we need to update Magisk into the beta version? Now that we have 17.0 is it necessary?

[FASTBOOT] [daisy] Patched boot.img for V11.0.7.0 (Android 10)

I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
The June update is 11.0.7.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.7.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.7.0.img.gz

Hi, when I patch the patched june update boot, my phone get stuck...
Anybody else having this issue?
Do you have any idea how to repear it?
thanks

SouSoulebarbu said:
Hi, when I patch the patched june update boot, my phone get stuck...
Click to expand...
Click to collapse
You should be able to flash the vanilla image to unroot.
If you describe the steps you took, I might be able to help more.

I first updated to 11.0.7 by OTA, the rebbot to fastboot and "fastboot boot file.img" with the proper filename, everything goes greart and my phone start automatically to reboot but after a while, nothing happens... I get stuck at the starting screen...
[edit] By the way, when I force reboot, it boot but magisk is not installed....

SouSoulebarbu said:
I first updated to 11.0.7 by OTA, the rebbot to fastboot and "fastboot boot file.img" with the proper filename, everything goes greart and my phone start automatically to reboot but after a while, nothing happens... I get stuck at the starting screen...
[edit] By the way, when I force reboot, it boot but magisk is not installed....
Click to expand...
Click to collapse
Magisk is not installed until you install it, and reboot, which you can't do until after booting a patched image.
There's a change something is not agreeing... You can download the 11.0.7.0 fastboot, copy the boot.img to your phone and use Magisk manager to patch it, then boot that.

where did you get the official fastboot rom?

sniffviper said:
where did you get the official fastboot rom?
Click to expand...
Click to collapse
From this thread
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871/

Question Why i cant updated latest QPR A13 for my pixel 6a

after download and reboot apprear this error..refer photo..

Try shutting it down, entering fastboot mode and flashing it from here.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
ok thanks..no need unlockboot loader rite?

Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader

ctfrommn said:
You can't flash anything with a locked bootloader
Click to expand...
Click to collapse
ok thanks..hmmm..

Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
For Android Flash Tool you need to have OEM unlocking enabled in developer options, but don't need to actually have the bootloader unlocked beforehand. The tool will unlock your bootloader during the process (assuming you are able to unlock the bootloader, e.g. not a Verizon model). It will also lock it afterwards if you choose to do so.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
already try..still not work

Boi. said:
already try..still not work
Click to expand...
Click to collapse
You probably need to be more specific. What exactly happened after using Android Flash Tool? How did you initially try to install QPR1B1? Are you using the latest Platform Tools? Do you have the latest USB drivers installed? Have you tried using an A to C cable using a USB 2.0 port?
If you're flashing environment is set up correctly, you can also try sideloading the OTA image.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...

Pakabidu said:
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...
Click to expand...
Click to collapse
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...

Pakabidu said:
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...
Click to expand...
Click to collapse
That is really weird behaviour for a Pixel device. I update using the stock rom method for all my pixels and never had issues. I have the Pixel 6 and the only instance I got the device is corrupt when I tried to roll back the November update to the October update causing a bootloop.
I wonder if there is something wrong with the 6A and some people having issues with the oem unlocking being greyed-out. Hopefully, Google will fix the issue with a future patch or monthly update.

General Official Android 13 firmware is now available

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