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
Related
Hi Guys,
Find attached are the stock boot.img and CF auto root boot.img from October update released today.
Flash process is the same.
cfar_xiaomi_mi-a1_tissot_n2g47h.7.10.14_t1.zip
https://drive.google.com/file/d/0ByKdTY2lxBIiSUFfNlhhcWgyUHM/view?usp=drivesdk
Stock boot.img.zip:
https://drive.google.com/file/d/0ByKdTY2lxBIiWG1vTjBoSldzTmM/view?usp=drivesdk
thanks
ravinder_rds
Uploading...
ravinder0003 said:
Hi Guys,
Find attached are the stock boot.img and CF auto root boot.img from October update released today.
Flash process is the same.
thanks
ravinder_rds
Click to expand...
Click to collapse
Hey buddy, thanks a. Lot! Can this be flashed using flashfire? I already have september rooted
Nice :good:
wow that was fast.... good job bro
No root found...
Chris_Cheekyz said:
No root found...
Click to expand...
Click to collapse
Same here, not rooted.
After fastboot flash. wait till it automatically reboots. Don't reboot it manually.
What are the complete steps to root?
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
I also got a bootloop after the October patch (was running the September patch w/ root). After installing the patch: I booted in to fastboot, flashed the rooted image (from this thread), rebooted and was fine w/ root access
It's Working Fine.
Do not reboot manualy after flashing, let the phone reboot it self.
uliek01 said:
It's Working Fine.
Do not reboot manualy after flashing, let the phone reboot it self.
Click to expand...
Click to collapse
I don't get this. My phone won't reboot by itself, if I want it to reboot, I have to execute:
Code:
fastboot reboot
How long does it take for the phone to reboot by itself?
mrsmn said:
I don't get this. My phone won't reboot by itself, if I want it to reboot, I have to execute:
Code:
fastboot reboot
How long does it take for the phone to reboot by itself?
Click to expand...
Click to collapse
1 or 2 minutes, if you reboot manualy your phone can't get root
uliek01 said:
1 or 2 minutes, if you reboot manualy your phone can't get root
Click to expand...
Click to collapse
Still won't work, here's what I did (this is with everything stock, october security update installed and using cfar_xiaomi_mi-a1_tissot_n2g47h.7.10.14_t1.zip by OP):
Code:
adb reboot bootloader
fastboot set_active b
fastboot flash boot_b boot.img
It's been 20 minutes, phone won't reboot out of fastboot by itself. Am I doing something wrong?
Am I wrong or the boot image inside cfar_xiaomi_mi-a1_tissot_n2g47h.7.10.14_t1.zip is half the size as it should be ?
tonycapuozzo said:
Am I wrong or the boot image inside cfar_xiaomi_mi-a1_tissot_n2g47h.7.10.14_t1.zip is half the size as it should be ?
Click to expand...
Click to collapse
It is indeed smaller than the original boot image. No idea if that's why it's not working for me.
I'm not familiar with cf method. I've rooted my Mi A1 previously with following the steps on September CF + root thread.
So what should I do with these files? Just run the root.bat in the cfar folder?
mrsmn said:
Still won't work, here's what I did (this is with everything stock, october security update installed and using cfar_xiaomi_mi-a1_tissot_n2g47h.7.10.14_t1.zip by OP):
Code:
adb reboot bootloader
fastboot set_active b
fastboot flash boot_b boot.img
It's been 20 minutes, phone won't reboot out of fastboot by itself. Am I doing something wrong?
Click to expand...
Click to collapse
root.bat says fastboot boot, not flash. Flash does not work
tosmopolitan said:
root.bat says fastboot boot, not flash. Flash does not work
Click to expand...
Click to collapse
I'm an idiot I run on UNIX so I never even thought to look into the root.bat file. It works now :good:
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?
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer
rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute
Won't let me simend the link
rob420p,
Please provide links.
rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!
lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
Hi sorry to hear that you got this problem and hopefully it gets fixed. I have another question: does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? Does that mean after installing, everything will be refreshed like a box opened phone?
dmj0shu4 said:
I installed the Stable Android 10 on my GM1910 via TWRP, totally forgetting about maintaining root and TWRP.
So how do I bring back TWRP and root?
fastboot boot doesn't seem to work, I managed to pull the boot.img and patch it with Magisk from another device but flashing it through fastboot ends up in an endless bootanimation.
Could anyone help me? here's a link of the boot.img i pulled, it works if you flash it without magisk patching it.
Link: https://drive.google.com/file/d/1O8lF1UDwwu0zT8ro5Q1gKKfdxF-HGPEW/view?usp=sharing
Click to expand...
Click to collapse
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
h0l said:
Run this command in fastboot so you know which is the CURRENT active slot :
Run this command so you can flash the correct slot : replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
djsubterrain said:
If you have an endless boot animation you might be trying to boot from the wrong slot, try using the fastboot set_active command to change slot, then restart
Click to expand...
Click to collapse
Which is the default active slot? Is it okay to use either of the 2?
dmj0shu4 said:
Which is the default active slot? Is it okay to use either of the 2?
Click to expand...
Click to collapse
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
djsubterrain said:
Either one should work if the rom and the rooted boot image is on it (If you are rooting). That's why you should install using TWRP, if you look in the reboot menu it will show you the active slot.
Click to expand...
Click to collapse
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
dmjoshu4 said:
I got a bit confused.
If the current slot is boot_a, i flash it in boot_b or am I supposed to flash on the one that isn't the current slot?
Click to expand...
Click to collapse
You are supposed to flash it in the one that IS the active one. Because you do want to root the slot that you'll be booting.
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
gh279760559 said:
does that mean using TWRP to completely clean the device then installing Android 10 via zip will remove TWRP and fastboot everything? I.e. everything will be refreshed like a box opened phone?
Click to expand...
Click to collapse
not everything, just twrp and root will be gone if you restarted without installing magisk to the inactive slot
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
dude, thanks for this, i was banging my head against a wall trying to get root to work. I used your patched boot img and i had the version mismatch, but i local updated my android and it has root!
dmj0shu4 said:
I would've used TWRP but it won't let me boot into it
fastboot boot [recovery.img] does not seem to work for android 10, atleast on my case
Click to expand...
Click to collapse
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Hi guys.. can you post the steps in rooting android 10??
I've already had bootloader unlocked.
Do i need to.follow the steps intended for android 9??
Like
1. Install TWRP via fastboot.. (2files)
2. Reboot to twrp.
3. Flash magisk via twrp??
Is that it?? If so. Then after reading this thread.. some of. You mentioned about boot. Img?? Patched?? What's that supposed to mean?? Sir??
Thanks. Any advice is highly appreciated..
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
And by the way..
Im on Gm1910 model. Global rom. Gm21AA build.. if that info would matter.. i dont actually need the root on android 9. Coz parallel app is working.. but now in android 10. It isnt working.. so.i need to root to grant su to game guardian.. thanks..
MigbyPie said:
I have not been able to boot TWRP either in fastboot mode - got stuck at "OnePlus Logo FastBoot" black screen.
Click to expand...
Click to collapse
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
E30Nova said:
Same.
I've read that Q/10 is different and you can't install TWRP like that anymore. Supposedly you need to use the MSM tool or the all-in-one tool but I've tried both of those and still can't boot to TWRP.
Click to expand...
Click to collapse
Hopefully there will be a solution. I had tried to update from Pie to Q10 while staying rooted and it didn't work. So I had to wipe the whole device and decided to wait for a smoother root method for my device. If you have any other ideas about rooting Q10 let me know. Thank you
h0l said:
(Almost) exactly the same here. I tired flashing a patched boot.img, it actually boots - but magisk manager gets stuck on the splash screen and some apps, including chrome, won't start. Trying to boot TWRP results in the phone getting stuck on the "fastboot mode" screen.
My only solution would be to downgrade, root, keep the upgrade this time. But because my ISP is doing some maintenance work I don't have wifi - and restoring my phone through mobile data does not seem to work correctly.
EDIT: In fastboot, neither bootloader version nor baseband version are show, product name is "msmnile". Has this always been that way?
EDIT 2, solution:
I extracted the boot.img from the device, and patched it using magisk on the same phone:
https://drive.google.com/file/d/1-Gf-6iXSFuYT5xDR-mnLKANvkXUHal9e/view?usp=sharing
Run this command in fastboot so you know which is the CURRENT active slot :
Code:
fastboot getvar current-slot
Run this command so you can flash the correct slot :
Code:
fastboot flash boot_X magisk_patched.img
replace X with the a or b from the command before.
:good:
Click to expand...
Click to collapse
You saved my life! Thank you!
But how do we get twrp now? Is there any way?
Me too. Use tool all in one but it doesnt work. Stuck at "waiting twrp boots".
Any help, thanks.
Same here any Solution?
Sent from my GM1911 using Tapatalk
---------- Post added at 08:14 AM ---------- Previous post was at 08:14 AM ----------
Stuck at Fastboot booting when flashed img and also zip
Sent from my GM1911 using Tapatalk
I updated my phone to 10 last night, followed the same guide as I have for every other update but this time I lost root for some reason.
I still have TWRP recovery on there but it can't read internal storage so I can't flash Magisk.
I tried changing file system to ext 2 then back to 4 and then repairing it as I read elsewhere and this wiped the phone obviously but internal storage seemed to be working until I set the phone up again, downloaded Magisk, rebooted to recovery and I'm back where I started, internal storage showing as 0mb in TWRP.
Any ideas how to fix?
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