Related
I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.
Devo7v said:
I've been using an E6653 for the last few months with the Customized UK firmware (32.2.A.0.253). I was initially using it unmodified with Android Pay, then about a month ago Magisk was developed that allowed you to use root and Xposed and still pass SafetyNet checks so I could still use Android Pay. Due to the cat and mouse game with Google, I didn't think having root/Xposed was worth it any more so I decided to flash the stock ROM again which should have wiped everything. I've reflashed the firmware 3 times, but I can't seem to pass SafetyNet checks anymore.
In addition to flashing the stock firmware with Flashtool, is there something else I should be doing? Any help would be appreciated.
Click to expand...
Click to collapse
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Devo7v said:
I found the answer to my own question. Apparently Google updated SafetyNet yesterday to detect an unlocked bootloader. If you have an unlocked bootloader then your device fails SafetyNet checks. I guess I'm never going to be able to use AndroidPay.
https://www.reddit.com/r/Android/comments/587ss9/psa_android_safetynet_now_tripped_by_unlocking/
Click to expand...
Click to collapse
inteltecra1700 said:
Hi,
Noobish question but do you mind telling me how you got magisk installed?
I'm rooted, unlocked bootloader and restored DRM keys bu honestly, that was hectic.
Should I simply flash the lastest FTF from flash tools and then install TWRP then flash Magisk, OR do I have to go into much more steps such as create boot img etc. Also, will I lose my DRM keys? how would I replace them? If u don't mind, just give me bullets of the step, I think i can manage to find the files.
I'm really looking for clarity and assurance. As clear as the forums are, or supposed to be, I find it noisy and sometimes it's hard to filter through all the dialogues.
Click to expand...
Click to collapse
It sounds like you're on a fully functioning stock ROM with an unlocked bootloader. If that is the case, then it's pretty easy to get Magisk up and running. The first thing you need to do is get TWRP on your phone, to do that you need to flash a kernel that supports entering TWRP recovery from boot. There are a few kernels that allow you to do that, I am using AndroPlus v38. There is a newer version of AndroPlus, but there have been mixed reports of being able to enter TWRP.
To Flash a new Kernel and TWRP:
Download the latest kernel from https://kernel.andro.plus/ and place the <boot.img> within the zip file in the same folder with the fastboot.exe
Download the version of TWRP from https://dl.myself5.de/ and place the <recovery.img> in the same folder with the fastboot.exe
In the the folder with fastboot.exe, shift+right click and run cmd as admin
Reboot phone in to fastboot mode (hold down the volume up while plugging in usb)
Once the phone is detected type 'Fastboot devices' to make sure you device is detected.
If it's detected flash the kernel by typing the following command 'Fastboot flash boot <boot.img>' (without <>)
Then type 'Fastboot flash recovery <recovery.img>' (without <>)
Once done flashing type 'Fastboot reboot', and make sure you press volume up when the yellow led is showing
Once you've made sure that you can enter TWRP, things will be much easier from here on out. To get Magisk up and running:
Head over to the official Magisk thread and download both the Magisk Manager v2.1 apk and the Magisk v8 zip file to your phone (http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Reboot your phone and enter TWRP by pressing the volume up key when the yellow led is showing
Flash the Magisk v8 zip file. This will patch Magisk into your kernel (boot.img), so if you ever want to get rid of Magisk and it's mods, just reflash your kernel either by using Fastboot or by flashing the kernel zip file through TWRP.
Once Magisk has been successfully flashed, reboot your phone
When you phone has booted up install the Magisk Manager v2.1 apk that you downloaded earlier. If everything went right, the Magisk Manager should show that everything is installed and up to date.
I hope that helps, let me know if you have any other questions.
When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?
piet3r said:
When I used to above procedure I get an error 'Response payload validation failed'. I have searched a lot in the internet and have seen a lot of people with the same bug. But I couldn't find a solution to this problem. Any ideas?
Click to expand...
Click to collapse
Google has added more checks to SafetyNet and the procedure above no longer works. The issue is the AndroPlus kernel does not pass SafetyNet so anything you do after that will pass either. Maybe @AndroPlus will get some time to look into it and add some fixes. In the meantime I need to find another kernel that will pass SafetyNet, but I haven't had time to try.
Maybe you could try some other kernels and let us know if you find anything that works.
Most Nexus phones users use magisk in order to be able to have root and xposed and also be able to easily pass safetynet check tests in order to be able to get OTA updates.
Well now magisk 14.4 works on our device and OTA updates should work just fine according to this https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Of course when Android Oreo rom comes out we should wait before applying it just to be sure that magisk and twrp will work on that rom so that we wont be left without root after updating (or brick the device.
I wrote a guide for installing magisk 14.4 on our device having 2nd october OTA installed, i copy it here so that more people can see it.
DISCLAIMER - USE AT YOUR OWN RISK! Bellow steps worked for my device but they might brick yours, you might lose warranty etc.!!!!!!
I am not a developer, I am just a user that wants to have the new phone setup like the older phones in my possession before using it as the main everyday phone.
All below packages are here due to the hard work of the people who made them. If you use them, give them the appropriate credits. This is also the reason that I don't attach any files in this post, I only give links to download the packages on the the forum threads/ sites I also found them.
Here I just show a combination of packages/ programs that worked.
PREREQUISITES:
1) Read the whole guide before starting. Make sure you are familiar with all the terms used and you understand what you are doing in each step.
2) I advise you to firstly download all the needed packages and have them in a folder in your computer and also make a copy of them in your phone and then start with the steps of this guide.
3) In this guide I use a windows pc. Fastboot commands are written in cmd. If you use a pc with another operating system, just make sure you can use adb/ fastboot commands and that you can also use miflash or another tool to flash the rom to your phone.
4) Make sure you have correct adb drivers installed in your pc. For this guide I have used adb-setup-1.4.3.exe from this thread.
So this is the step by step procedure with links:
Flash official rom with miflash
rom image: Here is the latest rom. (tissot_images_7.10.14_20171014.0000.00_7.1_d791bf99f4.tgz is the image I used while writing this guide)
miflash: MiFlash2017-7-20-0.zip
Boot to freshly flashed rom,
Install second october OTA update (75mb),
Do reboot and wait a few minutes until the update is installed.
If you have not done any changes to your device (other root like supersu, old magisk verision etc) you can ignore above step.
From settings-->developer options:
Usb debuging on
OEM unlocking on
Just to be on the safe side for magisk manager app also go to Settings --> Security and enable Unknown sources.
Then shutdown phone, boot phone to fastboot with Vol- & power button,
send the command "fastboot oem unlock" in order to unlock bootloader.
Phone reboots by it self if I remember correctly.
Boot to rom, now being unlocked, and see the splash screen to see if it says "Unlocked" to be sure that it is unlocked.
Then shut down the phone.
Again boot phone to fastboot with Vol- & power button,
boot twrp (just boot, not flash) with command "fastboot boot recovery.img"
recovery-3.1.1-1
From twrp, install Magisk-v14.4-20171103-073038
It installs magisk 14.4 but magisk manager apk version installed with this is 14.0.
So, in order to have magisk 14.4, reboot to rom, uninstall magisk manager and then install Magisk Manager 5.4.0 (as suggested by matcho13579) MagiskManager-v5.0-20170513.apk
The problem now with this version of magisk manager is that it installs modules correctly and they work just fine, but the installed modules are not listed in magisk manager modules page (they work but they cannot be seen). That means that you cannot disable a single module, you have to enable magisk core mode to disable all of them or normal mode to have all modules enabled - I hope this will be fixed in a newer version. Magisk-v14.4-20171103-073038 zip file as I said installs magisk manager 14.0 which also appears to be working, but I did all tests on my device with MagiskManager-v5.0-20170513.apk installed.
Next, inside magisk manager downloads, search and install xposed framework sdk 25 systemless by topjohnwu.
After installation is completed reboot phone (phone boot takes some time at this step).
Then install this Xposed installer apk -material design XposedInstaller_by_dvdandroid_31_10_17.apk.
Now you have October 2nd update rom in your device, magisk 14.4 & xposed framework.
If you select magisk core only mode (which disables magisk modules), have enabled magisk hide and hide it form all apps except the ones you want to have root access, the device passes safetynet and theoretically you can install OTA updates (xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled), according to this link
Inside magisk manager you can also install this MiA1Plus_V1.01 module in order to enable camera2api & EIS, to be able to use google camera application.
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working, I have not tested it thoroughly though:
https://forum.xda-developers.com/showpost.php?p=73340439&postcount=2
https://forum.xda-developers.com/attachment.php?attachmentid=4317286&d=1509267532
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Aman301582 said:
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Click to expand...
Click to collapse
Recovery is included in boot.img
tidschi said:
Recovery is included in boot.img
Click to expand...
Click to collapse
Which means I'll lose root after flashing ?
Aman301582 said:
Which means I'll lose root after flashing
Click to expand...
Click to collapse
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
blackyz01 said:
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
As I have written in the first post "xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled"
This means that if you enable magisk core mode which disables all modules or if you disable xposed framework module, it passes safetynet.
tidschi said:
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
Click to expand...
Click to collapse
Okay, managed to get stock recovery back. But 2nd ota is not installing. Always fails
Why install old Magisk Manager? New one seems like it works, unless I am missing something..
ilpanos said:
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working
Click to expand...
Click to collapse
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
matcho13579 said:
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Click to expand...
Click to collapse
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
suryaabadsar said:
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
Click to expand...
Click to collapse
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Will we lose root after an OTA update?
You have to do the procedure as described in the link I have provided in the first post. I am putting it again here:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
ilpanos said:
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
Click to expand...
Click to collapse
I'm currently using the normal version and everything is working as intended.
That's why I ask, because it might not work the same way with Magisk (I used CF-Root + SuperSU + standard Xposed method)
ilpanos said:
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Click to expand...
Click to collapse
I HAVE UNROOT PHONE WITH THE SAME METHOD AND RE-LOCK BOOTLOADER WITH FASTBOOT COMMAND fastboot oem lock
NOW OTA WILL WORK PROPERLY ON MY PHONE.?
Thanks for the perfect guide.
One side note: official ROM on the provided link is already version .30, so no need to boot into the ROM and install the updates, the update is already merged in
@ilpanos hello mate! I just ordered my A1 from Trading Shenzhen. I have an clear conception what to do with my A1 when it has arrived. So therefore I am collecting some knowledge about flashing and modding (I am not a beginner, but not familiar with A/B partitions). Your thread is very useful here, many thanks.
I have still one question and maybe you can answer it: i would like to remove the google apps from the system, but I don't know if this works just like usual (to remove it from /system/app or priv-app). The reason is that I am using microG instead gapps.
Or will removing files and folders screw up something?
Thanks in advance!
Cheers!
Well, the thing is that by even mounting system partition as read-write ,and of course doing any change - even adding a line in build.prop - disables the ability to do OTA updates. You will have to reflash the new rom for each update. This is the purpose of this thread, to show that there is a way to mod root etc systemlessly without loosing the ability to update (of course under certain conditions).
Hi,
I'm looking for a solution to root Huawei Mate 20. I couldn't find much on web search about this topic.
I am also not able to find a way to install TWRP or unlock boot loader.
Any ideas?
Sent from my HMA-L29 using Tapatalk
My phone got an update about a week ago. The details didn't mention Anything about boot loader unlocking but when I checked after the update, there was the ability to unlock the bootloader.
I have already opened the developed settings since november but the bootloader unlock option was greyed out and could not be turned on. I read a post from a different thread that his phone recently got an update with the option to turn on the bootloader unlock option. I have been regularly checking for update since I read that post and so last week I finally got it. I am now able to toggle the switch but I did not finish the process because I want to make sure it doesn't cause any warranty issues. I have been a Samsung user and I am very familia with the "warranty void 0x1" issue so I always waited until my warranty was over before rooting my phone. That way everythung has been tried and tested before I take a leap. If you do get the update please post your experience in unlocking the bootloader and eventually rooting your phone.
Sent from my HMA-L29 using Tapatalk
Maybe try kingroot? If it gets the job done on the pro version it might do it here as well.
Found it: https://www.techdroidtips.com/install-custom-rom-huawei-mate-20-cwm-twrp/ https://www.techdroidtips.com/root-huawei-mate-20/
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Hi please create a new thread how to root the phoneee?
Oem unlock is back :cyclops:
Hi, I can't find Twrp for huwaei Mate 20 can you help me?
Wysłane z mojego HMA-L09 przy użyciu Tapatalka
OldDroid said:
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Click to expand...
Click to collapse
Mate please help us.
EDIT:
sorry, now found your post: https://forum.xda-developers.com/mate-20/how-to/guide-manual-updating-firmware-t3892686
so only way to get root it's paying for bootloader code?
OldDroid said:
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Click to expand...
Click to collapse
Did you test it on EMUI 9.1 Roms?
Seems it doesn't work. I tried patching using the Canary build mentioned above and even used 19.0.
Neither of them worked, The end results is a bootloop.
Any ideas ?
JazonX said:
Did you test it on EMUI 9.1 Roms?
Seems it doesn't work. I tried patching using the Canary build mentioned above and even used 19.0.
Neither of them worked, The end results is a bootloop.
Any ideas ?
Click to expand...
Click to collapse
nope, my international mate 20 didn't receive 9.1 yet.
Regards
There is info about root EMUI 9.1 for mate 20X on XDA. "[GUIDE] Root AL00 EMUI 9.1"- https://forum.xda-developers.com/mate-20-x/how-to/guide-root-al00-emui-9-1-t3938483. You need Ramdisk for your device and patche it. Also it is possible to extract Ramdisk from full firmware. Now i have a problem to download full firmware for my phone - HMA-L29 9.1.0.310(C10E10R2P1). I tried https://support.halabtech.com/index.php?a=downloads&b=folder&id=35991 but it is impossible to download zip file. Is there another way to get this firmware?
Look this thread, the firmare was upload in google drive.
https://forum.xda-developers.com/mate-20/how-to/emui-9-1-t3943112/page6
ZTNL said:
Look this thread, the firmare was upload in google drive.
https://forum.xda-developers.com/mate-20/how-to/emui-9-1-t3943112/page6
Click to expand...
Click to collapse
Thank you! Downloaded from https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=149496 at last.
Now I have root root for HMA-L29, 9.1.0.300(C10E10R2P1) through Magisk 19.4 (Magisk Manager 7.3.3 ). I had root for 9.0.0.245 with the same Magisk. Downloaded firmware HMA-L29 9.1.0.310(C10E10R2P1) from https://support.halabt…e&c=download&id=149496 , extracted RECOVERY_RAMDIS.img, copied to mate 20 9.0.0.245, patched by Magisk. File is magisk_patched9.1.img. It can be downloaded from https://drive.google.c…Jq_6WNOxgdY5nK4VxLHE86. Then flashed RECOVERY_RAMDIS.img from 9.0.0.245 by adb, updated to 9.1.0.300(C10E10R2P1) and flashed magisk_patched9.1.img by adb. That's all.
Need Unlocked Bootloader?
vstrglv said:
Thank you! Downloaded from https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=149496 at last.
Now I have root root for HMA-L29, 9.1.0.300(C10E10R2P1) through Magisk 19.4 (Magisk Manager 7.3.3 ). I had root for 9.0.0.245 with the same Magisk. Downloaded firmware HMA-L29 9.1.0.310(C10E10R2P1) from https://support.halabt…e&c=download&id=149496 , extracted RECOVERY_RAMDIS.img, copied to mate 20 9.0.0.245, patched by Magisk. File is magisk_patched9.1.img. It can be downloaded from https://drive.google.c…Jq_6WNOxgdY5nK4VxLHE86. Then flashed RECOVERY_RAMDIS.img from 9.0.0.245 by adb, updated to 9.1.0.300(C10E10R2P1) and flashed magisk_patched9.1.img by adb. That's all.
Click to expand...
Click to collapse
Could you give a short tutorial of how you did that? Did you have to unlock bootloader?
I guess that unlocked bootloader is required to flash boot image, but I hope to be wrong
Yes, I have unlocked bootloader.
vstrglv said:
Yes, I have unlocked bootloader.
Click to expand...
Click to collapse
Where did you get the bootloader unlock codes? HW no longer support to release it...
I got unlock code on this forum from Crys18 on 30.03.2019 for $6.
Root on EMUI 10
Has anyone rooted the new EMUI 10? Can you give me a how to?
vstrglv said:
I got unlock code on this forum from Crys18 on 30.03.2019 for $6.
Click to expand...
Click to collapse
How can I contact him?
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/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Thank you :fingers-crossed:
I'm still on Android 8.1 and waiting stable Android 10
a1291762 said:
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/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
ony89 said:
can i use this patch update is 10.0.20.0. with new magisk without ubl n twrp, it just install magisk manager 2.04 and select this image for root acces thanks before.
Click to expand...
Click to collapse
If you have a locked bootloader, you can't do anything.
Magisk and root is separate to TWRP on this phone. This image will help you get Magisk installed.
Instructions here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626
a1291762 said:
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/
I had to make a new patched boot for 10.0.18.0 with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.18.0_204.img.gz
The March update is 10.0.20.0. I have a patched boot with Magisk 2.04
https://yasmar.net/xda/patched_boot_10.0.20.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_10.0.20.0.img.gz
According to the update screen, March update is for Pie only. Android Q users must wait
Click to expand...
Click to collapse
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Thank you!
wassupjg said:
Hi a1291762, as a noob could I ask you a few questions please?
Wanting to downgrade from Q to Pie, could I used your 10.0.20.0 vanilla boot with the Mi Flash Tool using the steps here, and then if I wanted to add root I could use the 10.0.20.0 patched boot with the guide here?
Click to expand...
Click to collapse
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
a1291762 said:
You might want to check that people have been able to downgrade. I know that pie-oreo caused a modem issue.
You need a fastboot image to downgrade. Unless MiFlash has magic (I have never used it).
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Looks like you'll have to downgrade to 10.0.18.0 and then apply the 10.0.20.0 update, since I do not see a fastboot for 10.0.20.0.
You won't need the vanilla boot image because it is in the fastboot image.
One you have 10.0.20.0 installed you can use the 10.0.20.0 patched boot to install Magisk.
Click to expand...
Click to collapse
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
wassupjg said:
Much appreciated, I had thought your vanilla boot and the fastboot images were the same things, once I downgrade to 10.0.18.0, how would I apply the 10.0.20.0 update as I assume the next xiaomi system update would skip straight to the latest Q build?
Click to expand...
Click to collapse
I'm not totally sure...
There are links to the OTA zips around. A thread about Android 10 showed how to install one using the stock recovery... I guess the same works for 10.0.20.0?
As a Linux user I would be inclined to try and use command line tools to install the OTA zip... But I don't even know if that's a thing
wassupjg said:
...
Click to expand...
Click to collapse
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
a1291762 said:
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
Click to expand...
Click to collapse
Thanks dude, I did find it here in the posts, I guess the OP isn't updated anymore, I've just had too many problems with Q, it sucks imo, once I back up everything I'll give it a go, by any chance do you know any good app and general backup apps that make things easy?
wassupjg said:
by any chance do you know any good app and general backup apps that make things easy?
Click to expand...
Click to collapse
I bought titanium backup pro a long time ago and still use it. Back in the day, the free version was annoying for whole device restore. But it's let me move across 5 devices and saved me from losing data on many occasions so I consider it money well spent.
I backup and then rsync /sdcard to a computer daily (CLI tools from cron). For restore I copy the files back (if needed) and then restore.
I only backup user apps, call history and SMS. System apps don't restore properly these days.
If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
Hi, thank you for the guide. I am very new here and I have some questions that I hope you can answer before I proceed.
First of all, I assume I should back up my device on an external medium if I screw the pooch. With that in mind, do you have any suggestions/ links on guides that can help me with that? If not, I'm sure I can do some good digging to find something suitable.
Second, I'm not exactly sure what "Bonito" is and from what I have seen from googling, it seems to be connected to the LineageOS operating system. Is this different from the current, factory OS that my phone is running? Is there a way to root my device without changing the factory OS if that's the case? If not, that's okay, I don't mind switching to an open-source OS that seems to have a good reputation.
Third, is the guide supposed to be followed sequentially with the first step being, "Spoiler: Downloads" and the last step being, "Spoiler: Pass SafetyNet?" Or are the first 3 steps, "Spoiler: Downloads", "Spoiler: Unlock Bootloader" and, "Spoiler: Initial Root / Create Master Root Image" are essential steps and the subsequent steps afterwards are based on personal needs? Ideally, using Android Flash Tool seems painless and foolproof which is perfect for me. Afterwards, I will attempt to copy the Spoiler: Pass SafetyNet" step.
Fourth, what is your take on using Android Flash Tool vs TOOL ALL IN ONE for flashing? TOOL ALL IN ONE seems even more painless and fool-proof and apart from backing up, seems easier. But I would love your take on this?
Feel free to answer any or none of these questions. I know it's a lot but id rather ask questions to a staff member before proceeding?
Thanks again for the guide!
Cheetah_Bear said:
Hi, thank you for the guide. I am very new here and I have some questions that I hope you can answer before I proceed.
First of all, I assume I should back up my device on an external medium if I screw the pooch. With that in mind, do you have any suggestions/ links on guides that can help me with that? If not, I'm sure I can do some good digging to find something suitable.
Click to expand...
Click to collapse
Without root, there is no way to do a full backup including app data. The best you can do is sync your Pixel with your Google account.
Cheetah_Bear said:
Second, I'm not exactly sure what "Bonito" is and from what I have seen from googling, it seems to be connected to the LineageOS operating system. Is this different from the current, factory OS that my phone is running? Is there a way to root my device without changing the factory OS if that's the case? If not, that's okay, I don't mind switching to an open-source OS that seems to have a good reputation.
Click to expand...
Click to collapse
"Bonito" is Google's internal name for the device and has little to do with the software. The Pixel 5 is "redfin", the 5a is "bramble", the Pixel 2 was "walleye".
As far as rooting your device, yes - if you follow this guide, you will gain root on the stock OS. I am currently using my Pixel 5 with the OEM firmware, patched with Magisk.
Cheetah_Bear said:
Third, is the guide supposed to be followed sequentially with the first step being, "Spoiler: Downloads" and the last step being, "Spoiler: Pass SafetyNet?" Or are the first 3 steps, "Spoiler: Downloads", "Spoiler: Unlock Bootloader" and, "Spoiler: Initial Root / Create Master Root Image" are essential steps and the subsequent steps afterwards are based on personal needs? Ideally, using Android Flash Tool seems painless and foolproof which is perfect for me. Afterwards, I will attempt to copy the Spoiler: Pass SafetyNet" step.
Click to expand...
Click to collapse
This guide is not sequential; I provided different instructions for different scenarios. The downloads are simply the resources you will need. To attain root, simply follow the instructions under "Initial Root". When the June update is released, you can update using your method of choice, and follow the relevant instructions to regain root.
Cheetah_Bear said:
Fourth, what is your take on using Android Flash Tool vs TOOL ALL IN ONE for flashing? TOOL ALL IN ONE seems even more painless and fool-proof and apart from backing up, seems easier. But I would love your take on this?
Click to expand...
Click to collapse
I personally do not like using third party tools, and I simply use adb/fastboot. The Android Flash Tool is simply for flashing factory firmware and cannot flash custom images.
Cheetah_Bear said:
Feel free to answer any or none of these questions. I know it's a lot but id rather ask questions to a staff member before proceeding?
Click to expand...
Click to collapse
No worries. It sounds like you have a lot to learn but you're at the right place; XDA is full of knowledgeable people who can help you out.
Cheetah_Bear said:
Thanks again for the guide!
Click to expand...
Click to collapse
Thank you for your appreciation.
Well, with a bit of hard work and head-bashing into my desk, my phone is fully rooted and backed up. I want to extend my thanks again for this guide. I'll be sure to return when the next updates roles around.
I am still trying to play around with Safety Net and my financial app. YASNAC says my Saftey Net passes, but my finance app won't open because it's still, somehow, detecting root, even after being placed under the Deny List.
Regardless, that is a problem for another day. Today is a day of celebration because my phone is rooted and rocking.
Thank you again.
Cheetah_Bear said:
Well, with a bit of hard work and head-bashing into my desk, my phone is fully rooted and backed up. I want to extend my thanks again for this guide. I'll be sure to return when the next updates roles around.
I am still trying to play around with Safety Net and my financial app. YASNAC says my Saftey Net passes, but my finance app won't open because it's still, somehow, detecting root, even after being placed under the Deny List.
Regardless, that is a problem for another day. Today is a day of celebration because my phone is rooted and rocking.
Thank you again.
Click to expand...
Click to collapse
Make sure you're using USNF and MHPC; DenyList alone won't do it.
You may also have to block the Play Store due to Play Protect.
Can I do anything with my 3a XL if the OEM debugging is greyed out? Honestly, is it really moddless?
BadRx said:
Can I do anything with my 3a XL if the OEM debugging is greyed out? Honestly, is it really moddless?
Click to expand...
Click to collapse
Most likely not. There is no way to force unlock. If you bought a branded variant like Verizon, unlocking the bootloader is not possible.
V0latyle said:
Most likely not. There is no way to force unlock. If you bought a branded variant like Verizon, unlocking the bootloader is not possible.
Click to expand...
Click to collapse
Why is that? I find that sooo... disturbing. From a hobbyist point of view this is just so unacceptable. You mean to tell me that I can't flash the chips somehow on this phone? Now there was a way carrier lock... you mean to tell me there is no way to carrier unlock? Not even the carrier? That's... just hard to believe.
BadRx said:
Why is that? I find that sooo... disturbing. From a hobbyist point of view this is just so unacceptable. You mean to tell me that I can't flash the chips somehow on this phone? Now there was a way carrier lock... you mean to tell me there is no way to carrier unlock? Not even the carrier? That's... just hard to believe.
Click to expand...
Click to collapse
I'm talking about bootloader unlock. It is a well known fact, having been established since the original Pixel (if not the Nexus series) that Google devices sold through carriers such as Verizon are not bootloader unlockable. This is why if you want a completely unlocked device, you must buy directly from Google.
As far as carrier unlock...that depends on the carrier. If you bought your device from Google, it's already carrier unlocked. But if you bought it through a carrier, they may or may not unlock it depending on their own policies. I don't know what Verizon's is, but most US carriers will allow carrier unlock as long as 1) there is no lien on the device (it's paid off) and 2) your account is not under contractual obligations.
It may seem weird to you, but they're protecting their investments. You can't reasonably expect a carrier to provide you a device at a discount with no restrictions. Either buy used from Swappa, or new full price from Google, and use the carrier only as a carrier. If you buy a phone through them, don't expect the same freedom.
Hi, before spamming all my stuff here, is this the right place to ask for help in the process of rooting (installing magisk and patching the boot.img) my pixel 3a XL?
thank you
Alex
4L3xN3t said:
Hi, before spamming all my stuff here, is this the right place to ask for help in the process of rooting (installing magisk and patching the boot.img) my pixel 3a XL?
thank you
Alex
Click to expand...
Click to collapse
Did you read the OP?
V0latyle said:
Did you read the OP?
Click to expand...
Click to collapse
yes, I spent much more time on reading it and preparing the needed stuff than doing the process
if you're referring to the warning, yes, I'm quite familiar with ADB, Magisk, Android and Root, but not 100%. I've played with some devices in the past, but the last before the 3aXL was a Nexus6 and a lot of thing changed in the root process and I'm a bit confused.
anyway, if it's ok, I would try to explain what's appening, I got a bootloop at the last step of rooting
Alex
4L3xN3t said:
yes, I spent much more time on reading it and preparing the needed stuff than doing the process
if you're referring to the warning, yes, I'm quite familiar with ADB, Magisk, Android and Root, but not 100%. I've played with some devices in the past, but the last before the 3aXL was a Nexus6 and a lot of thing changed in the root process and I'm a bit confused.
anyway, if it's ok, I would try to explain what's appening, I got a bootloop at the last step of rooting
Alex
Click to expand...
Click to collapse
What Android build are you on? Did you update?
What version of Magisk are you using?
What process did you use to root?
V0latyle said:
What Android build are you on? Did you update?
What version of Magisk are you using?
What process did you use to root?
Click to expand...
Click to collapse
ok, well, so, as I said I've an unlocked Pixel 3aXL with a stock ROM (bonito-sp2a.220505.006).
I'm on a fresh configured PC and just downloaded the latest platform-tools, USB driver, factory image, Magisk 25.2 canary.
Followed the guide in this page for the initial root, so I installed magisk, took the boot.img from the factory image, copied into the phone and patched via Magisk app. copied the patched boot.img into my platform-tools folder and flashed on the phone from the recovery via fastboot.
Now, after rebooting, the bootloop came. I just fix it flashing back the factory image, but of corse i'm still not rooted.
Maybe something related to the two boot_a and boot_b slots?
reading the boot.img flashing log it said it was flashed on boot_a (unfortunately i didn't check the actual slot before, I suppose was still boot_a) but then when i flashed the factory image to get rid of the bootloop it went on boot_b.
So I suspect I could have a misalignment beetween the two slot, but I'm not sure at all and anyway don't know exactly how to align them.
thank you
4L3xN3t said:
ok, well, so, as I said I've an unlocked Pixel 3aXL with a stock ROM (bonito-sp2a.220505.006).
I'm on a fresh configured PC and just downloaded the latest platform-tools, USB driver, factory image, Magisk 25.2 canary.
Followed the guide in this page for the initial root, so I installed magisk, took the boot.img from the factory image, copied into the phone and patched via Magisk app. copied the patched boot.img into my platform-tools folder and flashed on the phone from the recovery via fastboot.
Now, after rebooting, the bootloop came. I just fix it flashing back the factory image, but of corse i'm still not rooted.
Maybe something related to the two boot_a and boot_b slots?
reading the boot.img flashing log it said it was flashed on boot_a (unfortunately i didn't check the actual slot before, I suppose was still boot_a) but then when i flashed the factory image to get rid of the bootloop it went on boot_b.
So I suspect I could have a misalignment beetween the two slot, but I'm not sure at all and anyway don't know exactly how to align them.
thank you
Click to expand...
Click to collapse
No, there's no "misalignment" between slots. Each slot has its own partitions, and the system will boot from whatever slot is active. So, since you're on Slot A, the system will load the boot image from /boot_a, and run the system from /system_a. It doesn't cross over.
When I asked "what build" are you running, I meant which Android release, not your phone type. I also asked how you updated - factory image or OTA?
Where did you download Magisk from? There is no "25.2 canary". The current Canary is 25203, but Stable should work just fine.
I suspect you may be doing something wrong, hence the bootloop. Rule of thumb: When you encounter a problem. ALWAYS make sure you're doing everything right, and don't assume there's something wrong with the system until you have gone back through the instructions and made sure you're doing everything correctly.
Word of advice: When someone asks you specific questions, make sure you answer all of them with as much detail as possible. The more information we have, the better we are able to help you.
V0latyle said:
No, there's no "misalignment" between slots. Each slot has its own partitions, and the system will boot from whatever slot is active. So, since you're on Slot A, the system will load the boot image from /boot_a, and run the system from /system_a. It doesn't cross over.
When I asked "what build" are you running, I meant which Android release, not your phone type. I also asked how you updated - factory image or OTA?
Where did you download Magisk from? There is no "25.2 canary". The current Canary is 25203, but Stable should work just fine.
I suspect you may be doing something wrong, hence the bootloop. Rule of thumb: When you encounter a problem. ALWAYS make sure you're doing everything right, and don't assume there's something wrong with the system until you have gone back through the instructions and made sure you're doing everything correctly.
Word of advice: When someone asks you specific questions, make sure you answer all of them with as much detail as possible. The more information we have, the better we are able to help you.
Click to expand...
Click to collapse
ok, sorry, you're right, I lost something.
I wrote "bonito-sp2a.220505.006" because it thought it gives the information that I'm on the last available update for this phone of android 12.1. I always updated via OTA (I think it could be also interesting to know that I hadn't Magisk installed or any other modification at the time of the last update).
about Magisk I assumed that "25203" means "a release (the third?) of the 25.2", my fault...but anyway yes, I have the canary 25203, used it instead of the stable because sometimes in the past with other phones using it was the solution to some installation issues but I think this is not the problem.
I repeated the process (only the 9 steps of the "Spoiler: Initial Root / Create Master Root Image" guide) more than once, so I'm trying to understand if there might be something else wrong or corrupted.
partially unrelated question about the slots: if I force to boot from the slot A I'm supposed to go back to the bootloop, right?
Did you have anything in mind about this?
thank you
4L3xN3t said:
ok, sorry, you're right, I lost something.
I wrote "bonito-sp2a.220505.006" because it thought it gives the information that I'm on the last available update for this phone of android 12.1. I always updated via OTA (I think it could be also interesting to know that I hadn't Magisk installed or any other modification at the time of the last update).
about Magisk I assumed that "25203" means "a release (the third?) of the 25.2", my fault...but anyway yes, I have the canary 25203, used it instead of the stable because sometimes in the past with other phones using it was the solution to some installation issues but I think this is not the problem.
I repeated the process (only the 9 steps of the "Spoiler: Initial Root / Create Master Root Image" guide) more than once, so I'm trying to understand if there might be something else wrong or corrupted.
partially unrelated question about the slots: if I force to boot from the slot A I'm supposed to go back to the bootloop, right?
Did you have anything in mind about this?
thank you
Click to expand...
Click to collapse
I generally recommend against switching slots unless absolutely necessary, and especially not if you update via OTA. The reason for this is if you force the device to boot from the "old" slot, Anti-Rollback Protection will kick in and cause a boot loop.
Since you're able to boot with the unpatched image, just flash that for the time being. Your device has to finish up the update after booting, and the rooted image can sometimes cause a problem with this. Once the device has been running for a bit, say 10 minutes or so, you should be able to safety flash the patched image.
Were you rooted before?
V0latyle said:
I generally recommend against switching slots unless absolutely necessary, and especially not if you update via OTA. The reason for this is if you force the device to boot from the "old" slot, Anti-Rollback Protection will kick in and cause a boot loop.
Since you're able to boot with the unpatched image, just flash that for the time being. Your device has to finish up the update after booting, and the rooted image can sometimes cause a problem with this. Once the device has been running for a bit, say 10 minutes or so, you should be able to safety flash the patched image.
Were you rooted before?
Click to expand...
Click to collapse
The last update was done in May, so I think I waited way more than 10minutes
I really can't remember if I rooted when I bought it, with android 10, but if so (with magisk anyway), after the upgrade to 11 I didn't root again for sure.
4L3xN3t said:
The last update was done in May, so I think I waited way more than 10minutes
I really can't remember if I rooted when I bought it, with android 10, but if so (with magisk anyway), after the upgrade to 11 I didn't root again for sure.
Click to expand...
Click to collapse
Hmm. I am not sure why you are having problems now. The only thing I can suggest is flash the factory image using the instructions in the OP; you can also use the Android Flash Tool. You shouldn't need to wipe your device. Double and triple check to make sure you're patching the correct boot image, maybe post some screenshots or something (use spoilers) to show what you're doing. 99% of the time, if you are using the correct software, the problem is likely Magisk modules or incorrect patching.
V0latyle said:
Hmm. I am not sure why you are having problems now. The only thing I can suggest is flash the factory image using the instructions in the OP; you can also use the Android Flash Tool. You shouldn't need to wipe your device. Double and triple check to make sure you're patching the correct boot image, maybe post some screenshots or something (use spoilers) to show what you're doing. 99% of the time, if you are using the correct software, the problem is likely Magisk modules or incorrect patching.
Click to expand...
Click to collapse
when I flash the factory image (as I did l 2days ago), I use the "flash-all.bat" included in the original zip after I delete the "-w" from "fastboot -w update imagexyz.zip" and this way it doesn't wipe the phone.
I'll try again in the nex days (hope to have time in the weekend) doing some screenshot
stay tuned.
thank you