Develop Bugs

Uninstall Magisk Module from stock recovery

I installed a Magisk Module, called Notch killer or something to that effect from magisk downloads. Reboot caused my phone to not boot, but be stuck on the boot animation forever.
Is there a way to uninstall the module alone or recover the system without losing data. I am more concerned about the storage card data and would like to keep that for sure. Any insights / help is greatly appreciated.

srikaran said:
I installed a Magisk Module, called Notch killer or something to that effect from magisk downloads. Reboot caused my phone to not boot, but be stuck on the boot animation forever.
Is there a way to uninstall the module alone or recover the system without losing data. I am more concerned about the storage card data and would like to keep that for sure. Any insights / help is greatly appreciated.
Click to expand...
Click to collapse
If u search properly there is already a thread about this

v.konvict said:
If u search properly there is already a thread about this
Click to expand...
Click to collapse
Thanks for the pointer. I did go through all the threads and did find similar issue already addressed. For anyone that's keen, I ended up installing the stock boot.img and that ensured that I could boot. Out of curiosity, I tried to flash the patched boot.img and that ended up in the same loop again. Will search further as to how to remove that module first and then flash the patched boot.img, that should work somehow, not sure yet.
https://forum.xda-developers.com/oneplus-7t/help/magisk-modules-causing-bootloop-t3981427

OK, finally got everything back to running the way it was. After getting the stock boot image, to root it again, I followed the following steps.
1. Download the full OTA image
2. Install Payload Dumper
3. Extract recovery.img using the Payload Dumper from the full image (Payload.bin)
4. Extract the recovery.img using Android Image Kitchen.
5. Modify the default.prop to enable adb in ramdisk folder
6. Repackaged the recovery.img
7. Flashed the modified recovery.img to recovery partition.
8. Booted to recovery.
9. On the PC, went into adb shell, navigated to /data/adb/modules and identified the rogue magisk module and deleted that folder completely.
10. Booted back to bootloader
11. Flashed the stock recovery back to the recovery partition.
12. Rebooted to recovery, just to verify that everything was intact.
13. Rebooted to bootloader
14. Installed the patched boot.img for root
15. Reboot the system
That made it work as it was before without any issues. Thanks a ton to the great community that had already solved these issues. Here are the links to the forum posts and tools used.
How to Root: https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Patched boot.img (10.3.0, Indian version): https://forum.xda-developers.com/oneplus-7t/how-to/oneplus-7t-10-3-0-indian-hd1901-t4021047
Payload Dumper: https://github.com/vm03/payload_dumper
Android Image Kitchen: https://forum.xda-developers.com/showthread.php?t=2073775
ADB in recovery: https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
Remove Magisk Modules: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-twrp-root-module-uninstall-t4002843

10.0.11 Global - ADB Enabled - Insecure Recovery
I've tested it on my OP7T, worked for me.
https://drive.google.com/file/d/1FgngmAJQ-GKc0nIjngcspkU_xzwb-Y7T/view?usp=sharing
Please follow this guide on how to remove magisk modules
https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677

How To Guide Root achieved! Here's how to root the Red Magic 6 and Red Magic 6 Pro

I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!
Join our Discord Channel
Join the Red Magic 6 & 6 Pro [XDA Developers Forums] Discord Server!
Check out the Red Magic 6 & 6 Pro [XDA Developers Forums] community on Discord - hang out with 1 other members and enjoy free voice and text chat.
discord.gg
Youtube Video Tutorial:
UPDATED VIDEO:
For all those websites that claim the RM6 can be rooted with Kingroot, Kingoroot, iRoot, SuperSU... They are MISLEADING you into downloading their software. In other words, they are full of BS and you should INGORE them at all costs as Magisk is the ONLY proper way to root the RM6.
DO NOT USE KINGROOT, iROOT, KingoROOT, or ANY OTHER THIRD-PARTY ROOTING TOOLS PLEASE!! They steal your DATA and sell it. Magisk does not steal anything.​
This procedure will require a wipe of your data.. TWICE! I'll explain why.
When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.
However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.
Requirments
1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!
Here are the steps!
​1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"
2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip
3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
I ended up Downloading Termux from the playstore and extracting it with python on my phone.
When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!
4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.
Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.
5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop
6. Type fastboot flash boot magisk_patched.img
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. From the bootloader, reboot into your recovery and perform another factory reset!
9. Reboot the phone and voila! You now have root access!
Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!
So far I've installed the Xposed Framework and some Magisk modules. All seems to work really well.
Happy Modding!
​

Do u have rom V3:10

chocolote4444 said:
I've been up 24 hours dealing with bootloops. I finally found a way to root the phone and have it boot up!
This procedure will require a wipe of your data.. TWICE! I'll explain why.
When you unlock the bootloader, it wipes your data. Normally you only have to wipe it once, flash the patched boot.img file with magisk, and be done.
However, it seems that users will need to perform another factory reset after flashing the patched boot image. I have no idea why but it works. Please make a note of this as it will be required or you will be stuck in a bootloop.
Requirments
1. Global ROM file
2. A payload dumper
3. Magisk APK to patch the boot img
4. A computer!
Here are the steps!
​1. Unlock your bootloader. Make sure you enable OEM unlock in developer options. This WILL WIPE YOUR DEVICE! The command to unlock your bootloader is "fastboot flashing unlock"
2. Download the global rom from here: https://rom.download.nubia.com/Europe/NX669J/V312/NX669J-update.zip
3. You will need to download a payload dumper tool. This is due to the firmware being in a .bin file (payload.bin). Follow the link below on how to extract the global firmware:
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
I ended up Downloading Termux from the playstore and extracting it with python on my phone.
When you get it extracted, just move the boot.img and vbmeta.img files to your Desktop and on your phone Place it somewhere on your internal storage where you will remember!
4. Download Magisk Manager onto your phone and install it. Select install "patch a file" option and select the boot.img you put on your phone.
Let magisk patch it. It will end outputting a file like "Magisk_Patchedxxx.img" Go ahead and copy that file to your Desktop.
5. Go onto your computer and open up command prompt. Change your directory to the Desktop ex. cd c:/Users/Your Name/Desktop
6. Type fastboot flash boot magisk_patched.img
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification vbmeta vbmeta.img
8. From the bootloader, reboot into your recovery and perform another factory reset!
9. Reboot the phone and voila! You now have root access!
Another thing to mention is that SafteyNet does NOT pass even with MagiskHide enabled. Please keep that in mind!
Edit:
Xposed Framework DOES work!
​
Click to expand...
Click to collapse
would be the same process for version V4.12?

Masacr3 said:
would be the same process for version V4.12?
Click to expand...
Click to collapse
Yes. Mine is showing up as still 4.12

Are you SURE it doesn't pass SafetyNet? The Magisk check is broken download SafetyNet Checker from the app store and see what it says...

mslezak said:
Are you SURE it doesn't pass SafetyNet? The Magisk check is broken download SafetyNet Checker from the app store and see what it says...
Click to expand...
Click to collapse
I does not pass safety net. I've tested every testing app on the Play Store. I'll keep looking for a solution though.

chocolote4444 said:
7. Now make sure you have vbmeta.img on your desktop as well. We need to disable verity on the device. Type fastboot --disable-verity --disable-verification vbmeta vbmeta.img
Click to expand...
Click to collapse
You're missing the "flash" command inside, as such:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
A couple of questions:
1: does the phone retain full functionality? radio (BT/A2DP/different wifi bands/fingerprint scanner/camera)?
2: have you tried using an empty vbmeta?

adwinp said:
You're missing the "flash" command inside, as such:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
A couple of questions:
1: does the phone retain full functionality? radio (BT/A2DP/different wifi bands/fingerprint scanner/camera)?
2: have you tried using an empty vbmeta?
Click to expand...
Click to collapse
Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.
As for flashing empty vbmeta images, I have not tried it. I know some devices you may have to flash an empty vbmeta img at last resort but I was able to boot it up using the stock vbmeta.

chocolote4444 said:
Everything still works except the fingerprint. When the bootloader is unlocked, the fingerprint stops working.
As for flashing empty vbmeta images, I have not tried it. I know some devices you may have to flash an empty vbmeta img at last resort but I was able to boot it up using the stock vbmeta.
Click to expand...
Click to collapse
Thx for responding.
1: Would you be able to test/comfirm if the fingerprint scanner is restored when relocking the bootloader using either the rooted boot.img or the stock one?
2: The same issue with fp calibration is faced by RM 5S/G users; can you check if the calibration fix in these forums works also for the RM6?
3: Lastly, have you tried flashing the latest phh GSI to see if it's working?

Yes usually you just flash stock vbmeta.img via fastboot: fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification should try it out...

adwinp said:
Thx for responding.
1: Would you be able to test/comfirm if the fingerprint scanner is restored when relocking the bootloader using either the rooted boot.img or the stock one?
2: The same issue with fp calibration is faced by RM 5S/G users; can you check if the calibration fix in these forums works also for the RM6?
3: Lastly, have you tried flashing the latest phh GSI to see if it's working?
Click to expand...
Click to collapse
Fingerprint scanner should work after relocking the bootloader. As for flashing a GSI, there's no custom recovery for this device yet so I can't test any GSI roms yet.

chocolote4444 said:
Fingerprint scanner should work after relocking the bootloader. As for flashing a GSI, there's no custom recovery for this device yet so I can't test any GSI roms yet.
Click to expand...
Click to collapse
In this case, would you be able to run the following tests & share findings?
1: reflash stock boot, relock BL - check if fingerprint scanner is fixed
2: flash rooted boot.img (disable vbmeta), relock BL - check if fingerprint is fixed
If that would be the case, we could copy the calibration data from such a device; the data would be in /mnt/vendor/persist/goodix - I checked the stock ROM & it's not in there meaning it probably gets copied over during boot or mount-binded.
The last theory I want to check is the link between BL lock status & the fingerprint scanner - if some people have reported success with fixing the scanner with the builtin tool, there's a chance that the system framework or some other app is checking for the bootloader lock status & disabling the fingerprint if the former is unlocked. I've dumped the stock firmware but couldn't find a goodix dedicated apk, hence my hunch that it's a framework overlay. We would need to identify where the code is stored, decompile, find the security checking routine, disable, recompile & check agian - assuming it's not in any of the native libraries or the binary.
Assuming the access to the fingerprint scanner is indeed baked into the framework, using an AOSP GSIs would mean that the system would get unrestricted access to the fingerprint scanner, thus no blocking issue.
Thus (& addressing the 2nd part of your previous response), I'd suggest a 3rd test:
3: flash phh GSI or LOS GSI. The reason for the latter is because LOS usually has a wider range of hardware supported via hardware overlays.
You don't need a custom recovery to flash GSIs as these are fastboot images, so the following should suffice:
Code:
fastboot flash system gsi.img
fastboot -w

Umm Sir, got some problem with the global rom i patched it from your link. i cannot save any photos even screenshot. its nothing on my gallery. it seems it is not saving any photo. i hope you can teach me to solve it. thanks in advance

whincloud01 said:
Umm Sir, got some problem with the global rom i patched it from your link. i cannot save any photos even screenshot. its nothing on my gallery. it seems it is not saving any photo. i hope you can teach me to solve it. thanks in advance
Click to expand...
Click to collapse
Do a factory reset as you need to properly reinitialize package IDs, SELinux contexts & permissions.

adwinp said:
Do a factory reset as you need to properly reinitialize package IDs, SELinux contexts & permissions.
Click to expand...
Click to collapse
thank you. it is working well now.

I did the root process, but the phone stayed in the redmagic logo and it does not start me, what is the next process? flash the stock boot.img and it won't start

@chocolote4444 please share the solution when it gets stuck on the logo

FFX2 said:
@chocolote4444 please share the solution when it gets stuck on the logo
Click to expand...
Click to collapse
I am currently looking into it

Thanks for the guide

Hi. Will this also work for Android 11 on RM 5s?

Question GSI wont boot after rooting phone - Xiaomi Redmi Note 8 (2021)

Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.

I have found that resizing GSI system partition could help flash gapps via Ex Kernel Manager directly from the phone.
My big question is if you can resize GSI system partition without TWRP? since Note 2021 does not support recovery, if yes how?
Or can you actually set bigger system partition than system image with this command ? --el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
(following manual steps for gsi installation)
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
what would be number for 20GB size in this command? --el KEY_USERDATA_SIZE 8589934592 how i can write it correctly?
i have enough space to assign big userdata partition.

CyraxMD said:
Is there any fix for this problem? I wish to have phone rooted AND use GSI
Click to expand...
Click to collapse
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..

vegan_monk said:
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
Click to expand...
Click to collapse
was not neccessary, check this guide which i maked how to do it:

CyraxMD said:
was not neccessary, check this guide which i maked how to do it:
Click to expand...
Click to collapse
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.

vegan_monk said:
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
Click to expand...
Click to collapse
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.

CyraxMD said:
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
Click to expand...
Click to collapse
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8

vegan_monk said:
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
Click to expand...
Click to collapse
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too

CyraxMD said:
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
Click to expand...
Click to collapse
sorry to disappoint u mate but its just the miui recovery

GSI has better performance than MIUI? Could you tell the pros and cons that you have found?

CyraxMD said:
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
Click to expand...
Click to collapse
After seeing your video I understand that you was able to fix your initial problem:
"The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted."
It seem that you have been able to fix that problem, havent you? Have you had any problem using rooted GSI lineage? I am very insterested in rooting my phone using a GSI rom. I am going to follow your tutorial.
thanks

How do I update rooted rom Android 11 to 12 or 13?

Hello, I want to update my device to Android 12 or 13. This is my device:
xiaomi redmi note 8 pro (begonia)
Miui Global Stable 12.5.7.0 (RGGEUXM)
Android Version: 11 RP1A.200720.011
Bootloader: unlocked
I flashed twrp with BRP3.5.2v3.1. Device is rooted, SafetyNet check in magisk failed.
How do I update to Android 12 or 13 and where do I get the images from or do I have to build them?
Will I still have root access after update?

What are you talking about?
For root:
- Unlocked Bootloader
- Working rom
- By TWRP method: Working TWRP. Flash Magisk.apk
- By Fastboot method: Take boot.img. Patch boot.img. Flash patched boot.img
- Patch vbmeta if you are using Miui. Custom rom don't need this
For pass Safetynet (Magisk v25.2)
- Enable Zygisk
- Enable Enforce Denylist
- Flash Safetynet fix 2.4.0
- Configure Denylist:
+ Google Play Store
+ Google Play Services
- Reboot
- Setting>Apps
- Clear data + storage of 2 Google stuff above
- Check if it show devide certified or not.
Some old rom need to change many props to make rom work. I will not write details here. You can search on YouTube. But i recommend to use new roms to prevent that.

Kirasu2080 said:
For root:
- Working rom
Click to expand...
Click to collapse
What means a working rom?
Kirasu2080 said:
- By TWRP method: Working TWRP. Flash Magisk.apk
Click to expand...
Click to collapse
You wrote in https://forum.xda-developers.com/t/soft-brick-bootloop-after-twrp-flash.4570389/ that twrp-3.3.1-0-begonia.img supports Android 9 only. If I want to use TWRP for A11, I should find an unofficial one by searching "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1).
How do I know, which twrp is fitting my device? Does 'working' in this case mean, the software is penetrate the system to access recovery mode or something else?
Kirasu2080 said:
- By Fastboot method: Take boot.img. Patch boot.img. Flash patched boot.img
Click to expand...
Click to collapse
Is it the same patching as mentioned here https://topjohnwu.github.io/Magisk/install.html?
Patching Images
Copy the boot/init_boot/recovery image to your device
Press the Install button in the Magisk card
If you are patching a recovery image, check the “Recovery Mode” option
If your device does NOT have a separate vbmeta partition, check the “Patch vbmeta in boot image” option
Choose “Select and Patch a File” in method, and select the boot/init_boot/recovery image
Start the installation, and copy the patched image to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot/init_boot/recovery image to your device;
for most devices, reboot into fastboot mode and flash with command:
fastboot flash boot[_x] /path/to/magisk_patched_[random_strings].img or
fastboot flash init_boot[_x] /path/to/magisk_patched.img_[random_strings] or
fastboot flash recovery /path/to/magisk_patched.img_[random_strings],
where [_x] should be _a or _b or empty depending on your device
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img (note that it may wipe your data)
Reboot and launch Magisk app (you will see a stub Magisk app if you have wipped your data; use it to bootstrap to a complete Magisk app), and you will see a prompt asking for environment fix; click and wait for the reboot
Voila!
Click to expand...
Click to collapse
Kirasu2080 said:
- Patch vbmeta if you are using Miui. Custom rom don't need this
Click to expand...
Click to collapse
What exactly is vbmeta for? For preventing to remove the custom recovery loader? Or do I mistake it with avb close 2.0?
Kirasu2080 said:
Some old rom need to change many props to make rom work.
Click to expand...
Click to collapse
What is an old rom? By date or by software?

liltechie said:
What means a working rom?
You wrote in https://forum.xda-developers.com/t/soft-brick-bootloop-after-twrp-flash.4570389/ that twrp-3.3.1-0-begonia.img supports Android 9 only. If I want to use TWRP for A11, I should find an unofficial one by searching "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1).
How do I know, which twrp is fitting my device? Does 'working' in this case mean, the software is penetrate the system to access recovery mode or something else?
Is it the same patching as mentioned here https://topjohnwu.github.io/Magisk/install.html?
What exactly is vbmeta for? For preventing to remove the custom recovery loader? Or do I mistake it with avb close 2.0?
What is an old rom? By date or by software?
Click to expand...
Click to collapse
Working rom/TWRP mean rom/TWRP that you can boot on your phone.
Ex: Official TWRP can't boot with your Miui rom. So it's not working TWRP.
For knowing which is suitable TWRP, you need to know all about unofficial TWRP and it's changelog.
Fastboot method: it's working with almost device that don't have TWRP.
Patch vbmeta or avb close 2.0 with do same purpose. You can read about vbmeta in Official TWRP flash guide
Old rom is by date. Google update many stuff but old rom can't catch up.

Question Help!!!!!! Boot failure / stuck in fastboot

Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3

jcp2 said:
Need help. I used AFT to flash April - good, I rebooted and flashed magisk patched image made with stable 25.2 - good, flashed Kirisakura Raviantha Kernel v1.0.2 - good. Magisk said update to 26.1 so I did. I did direct install to update to 26.1. My P6P rebooted ok. power off and now stuck in fastboot mode showing device state= unlocked, boot slot: a, Enter reason: boot failure. I've tried to flash stock boot.img to both slots and the new april bootloader.img to both slots....the phone won't boot past fastboot screen. It won't go into recovery mode either. Please help!!!!!!!!
PS platform tools v33.0.3
Click to expand...
Click to collapse
Try using Android Flash Tool to get back to stock.

I tried. it failed.
Flash Failed​Device failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure

jcp2 said:
I tried. it failed.
Flash Failed​Device failed to boot into userspace fastboot. This usually indicates that the build you are flashing does not boot. Device serial logs can be helpful to determine the root cause of the failure
Click to expand...
Click to collapse
Then just manually flash ROM files in fastboot

jamescable said:
Then just manually flash ROM files in fastboot
Click to expand...
Click to collapse
is there a write up somewhere with adb commands?

Use PixelFlasher and the latest full update.

AlDollaz said:
Use PixelFlasher and the latest full update.
Click to expand...
Click to collapse
tried that as well
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

I'm not sure of the commands. Fastboot flash recovery "recovery.img" , same with the other files inside the zip inside the stock rom zip file
If i ran into this issue I'd try fastboot -w and fastboot update a custom rom.

jcp2 said:
is there a write up somewhere with adb commands?
Click to expand...
Click to collapse
Most need to be flashed in fastbootd I think. So to get there, fastboot reboot fastboot. You can flash recovery( boot, dtbo and vendor boot) in regular fastboot. That should fix everything because it will fully get rid of magisk

I used AFT and forced flashed partitions / wiped (kept bootloader unlock) and it's alive again!

Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?

StanWiz said:
Simply out of curiosity - what made you update magisk? Are there "must have" features in the new release?
Click to expand...
Click to collapse
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.

Strephon Alkhalikoi said:
Release Magisk v26.1 · topjohnwu/Magisk
Changes from v26.0 [App] Fix crashing when revoking root permissions [MagiskInit] Always prefer ext4 partitions over f2fs when selecting the pre-init partition [General] Restore module files' cont...
github.com
See for yourself, but the sepolicy and Zygisk updates I would consider "must haves". Of course, if you're still running an Android 5 device you won't be happy: Magisk 26.1 dropped Android 5 support.
Click to expand...
Click to collapse
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.

StanWiz said:
I'm all for change but I don't enjoy being a guinea pig .lol
If I have an application ( magisk 25.2) that works flawlessly I will hold off a few days prior to jumping on the band wagon ( unless the new version has something I really need) - more often than not there are issues. I prefer to read about them rather than experiencing on my own skin. Hence my question.
Click to expand...
Click to collapse
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.

Strephon Alkhalikoi said:
Not everyone thinks as you do. I update as soon as a new version is released, but I also know what I'm doing.
Click to expand...
Click to collapse
It's not a question of knowledge but rather the things that are beyond ones control - possibility of bugs in the code. For example look what happened recently with platform tools.

@jcp2 With all the things you flash, you should also know what that is. Then it would be much easier for you to figure it out why your device is in an unbootable state.
Magisk, Kernel, fastbootd... have one thing in common: your boot.img!
It doesn't make sense to let Magisk patch your boot.img and installing a custom kernel without Magisk installed afterwards. In that case Magisk gets overwritten.
Your fastbootd is only a binary and located in the recovery's /sbin folder. Due to the fact that your P6P is an A/B slot device, your recovery is part of the boot.img.
Flash your stock boot.img from the image-raven-BUILD_NO.zip that you'll find inside your firmware download.

I had already tried flashing stock boot image to both slots. I had to use AFT and force flash all partions. I'm up and running/ rooted. I just have to reinstall apps .

Android flash tool is by far the easiest way to go for sure. Happy you got it fixed

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
6. fast boot flash
That ADB Command does nothing.
The correct command is:
fastboot flash boot boot.img if you want to flash the boot.img

{Mod edit: Quoted post has been deleted. Oswald Boelcke}
You should give us the correct command. The syntax is (see fastboot -h):
Code:
flash PARTITION [FILENAME] Flash given partition, using the image from
$ANDROID_PRODUCT_OUT if no filename is given.
you can't use "fast boot" for a binary that's called "fastboot(.exe)".