Develop Bugs

[Q] Magisk Error 1

Good evening guys
I have a Xiaomi 5s stock rom MIUI9 with TWRP 3.2 (capricorn)
I was using the old supersu.apk to have root privilegs. I remove it completly to install the Magisk but I'm getting error 1
Follow the pictures...
As you can see I have the unlock boot, twrp, stock rom and not rooted... Tried others topics and tips to install the Magisk but It wont work...
What should I do?
(Xiaomi forum I saw a guy he installed the stock rom and full restored and he continues with error:1)
Resolution:
Change TWRP 3.2.1-1 to TWRP ZCX
Download stock rom (same as you're using)
Open the .iso with winrar or other software
Get the boot.img and put it in smartphone sdcard
Reboot in the recovery mod
Select install and change to install a IMG
Select boot.img and the partition BOOT
Install the magisk (feel free to put any version, I used v14)
Reboot and enjoy! :laugh:
PS: You dont need to unistall first your root because it'll be replaced when you install the stock boot.

Use magisk 15.2, make sure zip file not corrupt.

Even better use TWRP 3.2.1.1 and flash Magisk 16. That combination has some serious bugs ironed out.

BajinganTengik said:
Use magisk 15.2, make sure zip file not corrupt.
Click to expand...
Click to collapse
I tried with Magisk 15.3 and failed, same error. (ERROR:1)
8166uy said:
Even better use TWRP 3.2.1.1 and flash Magisk 16. That combination has some serious bugs ironed out.
Click to expand...
Click to collapse
I'm using the TWRP 3.2.1-1 is the same thing, I saw in Xiaomi Forum about the TWRP ZCX but I dont know what is the difference...
Does anyone have a fix to it?
Resolved, tip in the first post.

You could try the Xiaomi.eu ROM which has better support for rooting and adds some polish to MIUI (and also implements every weekly beta release of the official repo). Does require a clean install though.

8166uy said:
You could try the Xiaomi.eu ROM which has better support for rooting and adds some polish to MIUI (and also implements every weekly beta release of the official repo). Does require a clean install though.
Click to expand...
Click to collapse
Thank you for your advise, but I prefer the stock rom, btw I already fixed it too xD

Bootloop after installing magisk

hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img

sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?

Search for recovery.img and boot.img in stock rom and flash in fastboot mode.

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?

mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!

Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?

allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,

regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.

try this n give us the result

TWRP fails to boot on Android 11, 'Error verifying the received boot.img: Invalid Parameter'

I successfully rooted the phone using Magisk, and looking at how to install LineageOS, I saw I needed TWRP first. I followed all the instructions, but when I use fastboot to boot twrp.img, I get the following error message, "Error verifying the received boot.img: Invalid Parameter". Searching for an answer, I saw there was an old issue with TWRP with the Pixel 3a XL and Android 10, but I found nothing more recent about Android 11.
I thought maybe I shouldn't have rooted the phone first, so I reflashed with the stock boot.img and tried TWRP again, but that doesn't solve it. Any idea how I can boot TWRP? Or is there a way to install LineageOS with TWRP? Thanks!
Build # RQ2A.2100505.002
TWRP image twrp-3.5.2_9-0-bonito.img

Twrp doesn't work currently for android 10+
You don't need it to install lineage, just flash the lineage recovery and follow the wiki install guide.
Install LineageOS on bonito | LineageOS Wiki
wiki.lineageos.org

If TWRP does not work on Android 10+ what are we doing about flashing custom roms? Booting the TWRP and then sideloading the ROM?
I need help. When I try to boot TWRP(assuming its possible) I get an error :invalid parameter, error verifying the boot image. I am on Android 11. Yes, Ive used the search function or else I would not have found this thread.
I do not want to flash lineage, but the instructions are vague in other ROM threads.

I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.

Captain_Throwback said:
I just built a TWRP that works on Android 11. I wasn't sure how much interest there was in it, though, so I didn't bother posting it anywhere. I'll consider it once I clean up the source a bit.
Click to expand...
Click to collapse
Please post it! It would be greatly appreciated!

ncrawler said:
Please post it! It would be greatly appreciated!
Click to expand...
Click to collapse
I posted it on Telegram here: https://t.me/pixel3a/161825

Captain_Throwback said:
I posted it on Telegram here: https://t.me/pixel3a/161825
Click to expand...
Click to collapse
Thank You! I've been waiting for this!

I cant get your twrp and magisk to work together? I can only get one or the other working.

ncrawler said:
I cant get your twrp and magisk to work together? I can only get one or the other working.
Click to expand...
Click to collapse
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?

Captain_Throwback said:
Boot TWRP, copy image to device, use Install Image -> Install Recovery Ramdisk to install TWRP, then flash Magisk.apk.
I've done it a bunch of times and it works fine. Is that what you're doing?
Click to expand...
Click to collapse
Done it about 10 times and never boots again

ncrawler said:
Done it about 10 times and never boots again
Click to expand...
Click to collapse
with or without lmza kernel

ncrawler said:
with or without lmza kernel
Click to expand...
Click to collapse
No idea what to tell you. It works for users in the TG group and it works for me. That's the exact process I'm using. You can alternatively try the Advanced -> Flash Current TWRP option and then flash Magisk and see what happens.

Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?

ncrawler said:
Thanks! I think I got it! Think I was using the wrong Magisk! I Guess I still have to use lmza kernel to pass integrity in magisk?
Click to expand...
Click to collapse
I have no idea about any specific kernel or integrity checks in Magisk. I only build TWRP.

Redmi Note 8 Pro: Custom Recovery Won't Boot.

Hello!
This is my first time trying to install a custom recovery.
I tried installing TWRP with no success...
for some weird reason, it just won't boot into TWRP or anything else... not even OrangeFox.
Here is what i've done:
- Unlocked the bootloader using the official Xiaomi unlock tool (which took a whole week :/)
- Downloaded the official TWRP img from here: https://dl.twrp.me/begonia/twrp-3.6.0_9-0-begonia.img.html
- Flashed it using fastboot flash recovery twrp.img while the phone was in fastboot mode
The flash was successful according to the fastboot terminal, on the phone screen it was fine as well with no errors.
When trying to boot to recovery, the phone hangs on a black screen for a few seconds, and then restarts until i release the volume up button.
I have tried OrangeFox as well, and got the same result.
What you might ask:
- Was the phone rooted?
| No, it was not rooted.
- Any changes to the firmware?
| No, it was 100% stock, just with an unlocked bootloader.
- What region?
| Global.
- Have you tried older versions of TWRP?
| Yes, and i even tried OrangeFox.
- What is the MIUI / Android version?
| MIUI: 12.5.5.0 - Android: 11
- Did you boot back to MIUI after you exited fastboot?
| No, it turns out that MIUI will replace the recovery to stock if i boot back into it. so, no.
i tried powering it off and then accessing recovery using power button + volume up
- Have you tried multiple times?
| My headache says yes.
- HaVe yOu SeArcHed XdA aT alL???/??/?/
| Yes, i did. I found some people with the same issue, but these threads had no answers.
- Not enough information
| Tell me what you want to know please.
Thanks in advance!

electric fish said:
MOD EDIT: Link RemovedHello!
This is my first time trying to install a custom recovery.
I tried installing TWRP with no success...
for some weird reason, it just won't boot into TWRP or anything else... not even OrangeFox.
Here is what i've done:
- Unlocked the bootloader using the official Xiaomi unlock tool (which took a whole week :/)
- Downloaded the official TWRP img from here: https://dl.twrp.me/begonia/twrp-3.6.0_9-0-begonia.img.html
- Flashed it using fastboot flash recovery twrp.img while the phone was in fastboot mode
The flash was successful according to the fastboot terminal, on the phone screen it was fine as well with no errors.
When trying to boot to recovery, the phone hangs on a black screen for a few seconds, and then restarts until i release the volume up button.
I have tried OrangeFox as well, and got the same result.
What you might ask:
- Was the phone rooted?
| No, it was not rooted.
- Any changes to the firmware?
| No, it was 100% stock, just with an unlocked bootloader.
- What region?
| Global.
- Have you tried older versions of TWRP?
| Yes, and i even tried OrangeFox.
- What is the MIUI / Android version?
| MIUI: 12.5.5.0 - Android: 11
- Did you boot back to MIUI after you exited fastboot?
| No, it turns out that MIUI will replace the recovery to stock if i boot back into it. so, no.
i tried powering it off and then accessing recovery using power button + volume up
- Have you tried multiple times?
| My headache says yes.
- HaVe yOu SeArcHed XdA aT alL???/??/?/
| Yes, i did. I found some people with the same issue, but these threads had no answers.
- Not enough information
| Tell me what you want to know please.
Thanks in advance!
Click to expand...
Click to collapse
Download this one:
MOD EDIT: Link Removed
After phone in Fastboot mode, just run file 1.FlashBrpMiuiA11Unified.bat and it will flash and boot in twrp automatically.

Kirasu2080 said:
Download this one:
MOD EDIT: Link Removed
After phone in Fastboot mode, just run file 1.FlashBrpMiuiA11Unified.bat and it will flash and boot in twrp automatically.
Click to expand...
Click to collapse
Wow it actually worked! Thank you so much!
just wondering, why didn’t it work with how I did it? It seems like it also installed a modified version of TWRP.

electric fish said:
Wow it actually worked! Thank you so much!
just wondering, why didn’t it work with how I did it? It seems like it also installed a modified version of TWRP.
Click to expand...
Click to collapse
Best one until now. Encryption not broken (It broke on almost other Twrp, your data will be encrypted and just can Sideload). You can see in Advanced some more things like Magisk Install (If you want to root), patch vbmeta, fstab files (for f2fs),...

Kirasu2080 said:
Best one until now. Encryption not broken (It broke on almost other Twrp, your data will be encrypted and just can Sideload). You can see in Advanced some more things like Magisk Install (If you want to root), patch vbmeta, fstab files (for f2fs),...
Click to expand...
Click to collapse
Cool.
I’m sorry, but I really want to know what i did wrong that it didn’t work when I tried using fastboot?

electric fish said:
Cool.
I’m sorry, but I really want to know what i did wrong that it didn’t work when I tried using fastboot?
Click to expand...
Click to collapse
I think because it's for Android 9. If it for A11, it will be 3.6.0_11 like that. If you want for more other stuff, join Telegram group. All new things update there.

Kirasu2080 said:
I think because it's for Android 9. If it for A11, it will be 3.6.0_11 like that
Click to expand...
Click to collapse
Oh, so the modification were in place just to make it work on a current version of Android?
By the way, I’m planning on installing a custom rom as well.
I want pixel experience, it shouldn’t cause any problems, right?
(I don’t have an SD card, I want to do it from internal storage)

electric fish said:
Oh, so the modification were in place just to make it work on a current version of Android?
By the way, I’m planning on installing a custom rom as well.
I want pixel experience, it shouldn’t cause any problems, right?
Click to expand...
Click to collapse
I eddited old post, read again.
And for PE+ and PPUI rom, these one are the most dangerous roms. But because you already in 12.5.x, your hardbrick chance will be 5%. Some reported that still have chance for hardbrick even follow guide on these roms.
You can follow their Flash guide on Telegram (Find rmn8p official or PE_begonia). And they have unbrick method incase bad things happen, better near PC while flash that.

You can use Salih-Sonar's TWRP if you want decryption.
Just search "begonia-oss" on google and download the "TWRP-MIUI 12.5" one.
Also if you plan on switching roms this recovery will not work (learned that the hard way)
To prevent stock rom replacement,delete "recovery-from-boot.p" inside /system or /vendor

Im on MIUI 12.0.8 Android 10, with Bootloader unlocked.
I wanna flash TWRP to use custom rom, i tried alot TWRP ver, flash success but won't boot.
Any advice here?

dangtoi1993 said:
Im on MIUI 12.0.8 Android 10, with Bootloader unlocked.
I wanna flash TWRP to use custom rom, i tried alot TWRP ver, flash success but won't boot.
Any advice here?
Click to expand...
Click to collapse
i use the same version too
try unified recoveries they worked for me

having the same problem please help I'm on Android 11...

Lchoden said:
having the same problem please help I'm on Android 11...
Click to expand...
Click to collapse
Disable AVB 2.0.
Flash proper TWRP that is compatible with your MIUI/Android.
Then it should boot normally

Canny1913 said:
Disable AVB 2.0.
Flash proper TWRP that is compatible with your MIUI/Android.
Then it should boot normally
Click to expand...
Click to collapse

Have tried every thing when I input the command prompt everything goes well...device detected But when I flash the last command.. It boots into its miui version... Fast boot recovery.. Using windows 7...

How can I diasble it,, haven't installed twrp..

Lchoden said:
Have tried every thing when I input the command prompt everything goes well...device detected But when I flash the last command.. It boots into its miui version... Fast boot recovery.. Using windows 7...
Click to expand...
Click to collapse
Install it again, then use "fastboot reboot-recovery" to boot directly to twrp. then using the file manager find and delete /vendor/recovery-from-boot.p

Development [CLOSED] Deleted

Deleted

Does this need a12 firmware? If so you should post dtbo and vendor_boot images.

gillim74 said:
Does this need a12 firmware? If so you should post dtbo and vendor_boot images.
Click to expand...
Click to collapse
wait for official Update

The boot image isnt working at all, after restarting into recovery mode i end up in bootloader. im on the latest oos 11 (11.2.10.10 BA)
edit:
sadly there are no install instructions on how to flash, found out that oos 12 is needed and the flash files are in the download repo (Image files folder)

A - Reboot to bootloader
fastboot flash dtbo "dtbo.img"
fastboot flash vendor_boot "vendor_boot.img"
fastboot flash boot "boot_img"
B - Fastboot reboot recovery
Perform factory data reset
Apply update from sideload
adb sideload "file name.zip"
C -Reboot system

OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.

Flashed yesterday without any issues. To get the boot, vendor_boot, and dtbo i used payload extraction. Changelog states CTS to pass by default, however it fails until Zygisk is enabled. Custom FOD icons are not working. Audio & mic (oos12) bug is present. Flashed BluSpark kernel about an 1hr. ago. Without issue.
Overall seems to be very stable with many options! Great Job! LE2125.

Flashed this but was having issues with haptic/vibrate feedback, they're not working.

Fyi BluSpark kernel fixes this

Advali said:
Flashed this but was having issues with haptic/vibrate feedback, they're not working.
Click to expand...
Click to collapse

cave.man1908 said:
Fyi BluSpark kernel fixes this
Click to expand...
Click to collapse
Bluspark doesn't work on LE2120. Already tried this 3x and it f'd up my phone and had to reinstall again.

Absolutely gorgeous ROM! Do I understand that I can flash this coming from OOS12 without the need to downgrade to android 11?
If so, can somebody please explain what changed since the first A12 ROMs were released as they warned against flashing from OOS12 directly.

Reremoll said:
Absolutely gorgeous ROM! Do I understand that I can flash this coming from OOS12 without the need to downgrade to android 11?
If so, can somebody please explain what changed since the first A12 ROMs were released as they warned against flashing from OOS12 directly.
Click to expand...
Click to collapse
Yes you flash this over OS12. make sure u have OS12 on both slots(if ur on c48 just download and local update once again to have on both sides). Then u have to download this rom, extract it on ur pc, so u can flash(in fastboot) dtbo, vendor_boot and boot. Then boot to recovery, wipe and adb sideload rom.

blu-spark kernel doesn't work on this rom, tried it. But it seem unfortunately it doesn't work on this rom.

break.cold said:
blu-spark kernel doesn't work on this rom, tried it. But it seem unfortunately it doesn't work on this rom.
Click to expand...
Click to collapse
I flashed BluSpark to elixir yesterday without issue. Weird. Im le2125

I've tried 4 roms yday and blu spark sometimes make you bootloop or doesn't want to flash which is weird.
After a few rom re-installs it worked on every rom I tried.

cave.man1908 said:
I flashed BluSpark to elixir yesterday without issue. Weird. Im le2125
Click to expand...
Click to collapse
I tried blu-spark of StagOS, Pixel Extended, Project ELixir, it keep sending me back to fastboot menu, however, its works on riceDroid without issue.

OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.

sourav24071999 said:
OnePlus 9 Pro (lemonadep) of Project Elixir has been dropped due to bad behavior of the maintainer.
So no more official support and we recommend not to flash builds which isn't available in OFFICIAL website.
Click to expand...
Click to collapse
Well, I wouldn't have had "bad behavior" if you weren't trying to control what I did with my own Telegram group.

MOD ACTION:
Thread closed since OP has been edited removing content.