Stuck in fastboot, Please help... - Google Pixel 3 Questions & Answers

I have followed these instructions (https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359) step by step... after step 8 however I could not get out of the fastboot. the device is not recognized anymore...
I hope someone can help me
i know my mistake now. i have downloaded an old firmware
Link for the Picture

0v3rdr1v3 said:
I have followed these instructions (https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359) step by step... after step 8 however I could not get out of the fastboot. the device is not recognized anymore...
I hope someone can help me
i know my mistake now. i have downloaded an old firmware
Link for the Picture
Click to expand...
Click to collapse
Hi, this error appears due to the fact that in the guide for installing magisk there is an old link to the latest system image, and since you now have the latest version of the system, you are simply flashing an older kernel to a newer system, today you also encountered this problem, the decision is banal.
First, you need to download the latest image on the official website of the manufacturer (you have it installed at the moment), get the kernel from this image and flash it through the fastboot, then patch this kernel image in the magisk, and only after that flash the patched kernel. I will slightly simplify your task at the moment, but after the next update you will have to do all the steps yourself.
ust flash this image through the fastboot in boot slot. patched boot.img

Related

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root

[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?

Can't update

My device is rooted and i have installed a TWRP recovery, & i want to update it, but always stuck at the recovery mod with ERROR 7!! help plz
This is because you're trying to update without flashing back stock recovery.img of your firmware build, and TWRP isn't able to analyze and confirm the update package as valid before starting the update process.
To update correctly, extract the recovery.img (32MB like) from your update package (probably you'll need to downlaod the update.zip of your actual firmware if you didn't stored a copy) using Huawei Update Extractor program, flash it by ADB in the same way you flashed TWRP and once done, update again. Then you can flash TWRP again.
RedSkull23 said:
This is because you're trying to update without flashing back stock recovery.img of your firmware build, and TWRP isn't able to analyze and confirm the update package as valid before starting the update process.
To update correctly, extract the recovery.img (32MB like) from your update package (probably you'll need to downlaod the update.zip of your actual firmware if you didn't stored a copy) using Huawei Update Extractor program, flash it by ADB in the same way you flashed TWRP and once done, update again. Then you can flash TWRP again.
Click to expand...
Click to collapse
So you mean that i should update it via computer?
And I should install the root again, or just the TWRP?
And plz can u tell me how to download the version of my device? Knowing that the frimware update is downloaded by the Huawei updater, So can I copy it?
Thanks for the help!
KhalidZH said:
And plz can u tell me how to download the version of my device? Knowing that the frimware update is downloaded by the Huawei updater, So can I copy it?
Thanks for the help!
Click to expand...
Click to collapse
I take the chance to leave you a guide that i used too, in which is well explained how to correctly update a rooted device and how to grab all the necessary files required for updating. Check it out https://forum.xda-developers.com/honor-6x/how-to/guide-ota-update-rootet-h6x-t3684758
Let me know if you solve this!
RedSkull23 said:
I take the chance to leave you a guide that i used too, in which is well explained how to correctly update a rooted device and how to grab all the necessary files required for updating. Check it out https://forum.xda-developers.com/honor-6x/how-to/guide-ota-update-rootet-h6x-t3684758
Let me know if you solve this!
Click to expand...
Click to collapse
Thank you for helping me, I'll try to follow the steps and tell you the result!
RedSkull23 said:
I take the chance to leave you a guide that i used too, in which is well explained how to correctly update a rooted device and how to grab all the necessary files required for updating. Check it out https://forum.xda-developers.com/honor-6x/how-to/guide-ota-update-rootet-h6x-t3684758
Let me know if you solve this!
Click to expand...
Click to collapse
Hello friend, i know it took me so long to respond this. but i actually forgot about it, now i remembered.
I tried to follow the steps but i didnt understand how to flash the stock recovery.img and flash stock boot.img, also this magisk i dont have...
So please if u can lead me to a video or try to explain further...
Sorry for my late respond... Peace out

S7 G930F stuck in a bootloop after attempt to install TWRP

Hi everyone!
I wanted to finally flash a custom ROM on my G930F (vanilla, with the latest official update) and started by installing TWRP (twrp-3.3.1-0-herolte.img.tar) via Odin (3.13.1) following this guide: https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770.
Everything was going smoothly until step 9, because after swiping right I tried rebooting before flashing anything (found a thread on Reddit advising to just follow the guide without proceeding with rooting as indicated in the last steps). So now I'm stuck in a bootloop and I have no idea what to do, I can only access Download mode but that's it.
How do I solve this problem?
Step 10 included scenarios for both if you want root, or if you just want to boot successfully
Did you download and flash the dm-verity and force encryption disabler zip as per the step 10?
Repeat steps 6-10 and flash that zip
Beanvee7 said:
Step 10 included scenarios for both if you want root, or if you just want to boot successfully
Did you download and flash the dm-verity and force encryption disabler zip as per the step 10?
Repeat steps 6-10 and flash that zip
Click to expand...
Click to collapse
Thanks for answering!
Yes I figured out, installed TWRP via Odin again and then tried flashing that thing without wiping as shown in the video, but then I got some error messages and the device wouldn't boot up again, telling me I had to do a wipe. So I just went into recovery and did a factory reset.
Now I'd like to flash LineageOS but I'm not so sure anymore since I've had so many problems, and I have a few questions:
Do I need to reinstall TWRP?
Do I need root?
What version of LineageOS should I download?
Is there a guide for flashing LineageOS on the S7?
trim1_ss said:
Thanks for answering!
Yes I figured out, installed TWRP via Odin again and then tried flashing that thing without wiping as shown in the video, but then I got some error messages and the device wouldn't boot up again, telling me I had to do a wipe. So I just went into recovery and did a factory reset.
Now I'd like to flash LineageOS but I'm not so sure anymore since I've had so many problems, and I have a few questions:
Do I need to reinstall TWRP?
Do I need root?
What version of LineageOS should I download?
Is there a guide for flashing LineageOS on the S7?
Click to expand...
Click to collapse
Do I need to reinstall TWRP?
No TWRP will remain until you remove it or flash stock firmware.
Do I need root?
Not required to flash custom Rom's but useful
What version of LineageOS should I download?
Look at the ROM section and read up on which one you want, there are several different ones and builds so the choice is yours.
Is there a guide for flashing LineageOS on the S7?
There is always a guide contained in the post for the ROM usually at the beginning. The process of flashing Rom's is generally the same no matter what Rom you use.

T-Mobile IN2017 Root Method?

All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
SilverZero said:
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
Click to expand...
Click to collapse
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
stompysan said:
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
Click to expand...
Click to collapse
Works great. Thanks!
BostonDan said:
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
Click to expand...
Click to collapse
Post below yours worked for me but I appreciate the advice on backups and what to watch for. I haven't installed TWRP yet, just booted it and installed.
SilverZero said:
Works great. Thanks!
Click to expand...
Click to collapse
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
stompysan said:
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
Click to expand...
Click to collapse
Following up on this just in case you know anything new. My IN2017 just updated to A11 without any action on my part, and I lost root. Is there a TWRP or patched boot img that you know of for us on TMo now?
There is no working twrp for us on Android 11. I also haven't seen a patched boot image of 11.0.1.3.IN55CB around yet. I have that firmware extracted on my laptop so I could grab the boot image and patch it for you, but I won't be able to do that until later tomorrow. If no one else has it out or if you don't find it before I can get to it, I'll post it up.
Edit: Here's the patched boot image: Magisk Patched Boot IMG TMO 11.0.1.3

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

Xiaomi Mi A2 Lite 11.0.18.0 / Magisk 21.4
or
Hi, big thanks for this. I'd rather patch the image myself, using a tutorial like this one – https://www.thecustomdroid.com/root-xiaomi-mi-a2-a2-lite-android-pie-magisk/. Where do you get the stock images?
Is this the right place? https://c.mi.com/oc/miuidownload/detail?guide=2 (search for "Mi A2 Lite")
Or this one? https://c.mi.com//miuidownload/detail?device=1700354
Thanks, I figured it out. The newest version can be downloaded at https://c.mi.com/oc/miuidownload/detail?guide=2, extract it using `tar xvzf daisy_global_images_V11.0.18.0.QDLMIXM_20210126.0000.00_10.0_286d778cee.tgz` on Linux and the boot.img is located in the images/ directory. Then you can follow the guide at https://www.thecustomdroid.com/root-xiaomi-mi-a2-a2-lite-android-pie-magisk/ to create the patched image and boot from it.
mariansam said:
Hi, big thanks for this. I'd rather patch the image myself, using a tutorial like this one – https://www.thecustomdroid.com/root-xiaomi-mi-a2-a2-lite-android-pie-magisk/. Where do you get the stock images?
Is this the right place? https://c.mi.com/oc/miuidownload/detail?guide=2 (search for "Mi A2 Lite")
Or this one? https://c.mi.com//miuidownload/detail?device=1700354
Click to expand...
Click to collapse
you can find updates here https://xiaomifirmwareupdater.com/miui/daisy/
depends how everyone uses to update his phone, but i always use fastboot file with xiaomiflash, it's only 2 clics and avoids me to care about uninstall magisk.
also the original boot.img is inside so just copy it on phone, magisk patch the file and then i fastboot boot the patched
hi! thanks for your work!
I've tried to update my phone, like I always do, restoring 11.0.17 boot stock image first, but I get an update error.
Any suggest?
u can try as i use to do, explained in message above
I tried but Xiaomi Flash doesn't work properly on my PC, I am afraid of losing data on phone.
Why am i unable to update after flashing stock boot image, like I always do??
Anyone having trouble?

Categories

Resources