Related
I've been waited for Magisk v21 released by John Wu this morning, but I ran into some problems
What I've done
- download stock image file from Google official site
- follow the instruction given by John Wu at GitHub wiki
- run command
Code:
adb shell magisk --remove-modules
- when i flash the patched boot.img file, it stuck on the *G logo* with progress bar under it.
- After a certain period of time, it comes back to bootloader with a prompt saying: "no valid slot to boot".
What i've tried:
- redo all processes, no working
- switch active slot to both a & b, none working
- re-patch the stock boot.img file use different Magisk Manager version. The ones i tried: v8.0.0-Beta(offers Magisk v21), v8.0.0-Stable(offers Magisk v20.4), Canary version (offers Magisk Canary who claims to support android 11)
- change the command
HTML:
fastboot flash boot ***.img
to
HTML:
fastboot flash boot_a ***.img
&
HTML:
fastboot flash boot_b ***.img
then run
HTML:
fastboot reboot
. same result as said before
Basic info:
- Device: Pixel 3 (blueline), android 11 (build number RP1A.200720.009), latest android security update & Google play system update.
- Magisk: Magisk Manager v8.0.0 (released hours ago), Magisk v21 is suppose to be installed
Is patched boot.img filesize ~32 or ~64mb?
I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.
done
dmk16 said:
Is patched boot.img filesize ~32 or ~64mb?
Click to expand...
Click to collapse
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler
red stapler said:
I ran into the same problem. My phone is a Pixel 2 XL running Android 11. However, I was not patient enough to wait for the "no valid slot to boot" message. After waiting for 5-10 minutes, I did a factory reset.
I followed the installation instruction that were posted by John Wu.. (As a new user, I am not allowed to post an outside link)
The displayed Magisk installation messages do not suggest a problem:
- Device platform: arm64-v8a
- Copying image to cache
- Unpacking boot image
- Checking ram disk status
- Stock boot image detected
- Patching ram disk
- Repacking boot image
***************************
Output file is written to
/storage/emulated/0/Download/magisk_patched.img
***************************
- All Done!
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version. For instance, with Magisk 20.4 and Android 10, the file sizes of boot.img and magisk_patched.img were 41943040 and 25747456, respectively. Thus, the patched file was smaller than the original.
Click to expand...
Click to collapse
Seems like we're in the same boat here lol, is this enough proof for a legit bug issue to John?
red stapler said:
The boot.img and magisk_patched.img files have both a file size of 41943040 bytes. This is a different from previous Magisk version.
Click to expand...
Click to collapse
DaddyTony said:
the stock & patched boot.img are both 65535KB large, which is weird and also mentioned by @red stapler
Click to expand...
Click to collapse
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
[MagiskBoot] Pad boot images to original size with zeros
Click to expand...
Click to collapse
nogaff said:
The patched boot image is supposed to be the same size as the original now.
From the v21 changelog:
Click to expand...
Click to collapse
Glad to hear, hope this indicates patch is successfully done?
Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11
So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).
I forgot to mention that I didn't install or use a custom recovery, such as TWRP. Using the stock recovery.
73sydney said:
Why not:
adb reboot bootloader
fastboot boot twrp-xxxx.img
adb push magisk-xxxx.zip /tmp
adb shell twrp install /tmp/magisk-xxxx.zip
adb reboot system
Let the magisk zip update script figure everything out...
Its what i do on Pixel 2 XL, works every time...10/11
Click to expand...
Click to collapse
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?
Didgeridoohan said:
So far, what we've seen that is causing issues with Android 11 and Magisk is usually either having incompatible modules installed (the brand new Safe Mode should take care of that, see the FAQ for details), or having TWRP installed to your device (it'll cause a conflict and the device won't boot, install the stock recovery and only use TWRP booted).
Click to expand...
Click to collapse
I forgot to mention that i run this command before install magisk patched boot.img
Code:
adb pm shell magisk --remove-modules
I didn't have TWRP installed on my device, don't seem to have TWRP for Pixel 3 on android 11.
DaddyTony said:
Sorry but i don't think Pixel 3 have Teamwin (TWRP) support of android 11?
Click to expand...
Click to collapse
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it
73sydney said:
Theres no TWRP support of my Pixel 2 XL either, but it works
We just dont install it, we fastboot to it
Click to expand...
Click to collapse
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
Due to this reason, we no longer recommend installing Magisk through custom recoveries on modern devices.
Click to expand...
Click to collapse
BTW he also said the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
--------------------
edit:
Just find out Pixel 3 (blueline) has **NO** official support of TWRP v3.4+, but Pixel 3 XL (crosshatch) has it. How ironic.
and I wonder if TWRP v3.4+ support android 11?
DaddyTony said:
Just tried boot into TWRP img, failed. It just says:
Code:
FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
Googled it & find out TWRP's a deprecated/no longer recommended way to install Magisk. And according to John Wu's installation instruction, it is no longer supported in modern models.
BTW he also says the "patch image" method is guaranteed to work 100% lol, should we let him know hhh
Click to expand...
Click to collapse
Hmmm, disappointing
Ive literally tried the image patch method once, a lot of faffing about, I always use the TWRP method, easy peasy at least for older device
....we no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support.
Download the Magisk installer zip
Reboot to custom recovery
Flash the zip and reboot
Check whether Magisk Manager is installed. If it isn’t installed automatically, manually install the APK.
Click to expand...
Click to collapse
Guess ill be happy to remain a legacy device user
This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11
Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?
polyxn said:
Hey all, i have a pixel 2 XL and I'm also stuck in bootloop. However i can't find how to do a factory reset. Could you help me?
Click to expand...
Click to collapse
Which version of Android?
Do you have TWRP installed?
If you do people have been posting that going to Advanced, then tapping Fix Bootloop may work
Otherwise find the boot image of the ROM you have installed, and flash that to the device
If youre on Android 11 on the Pixel, as i found out myself via bootloop, do NOT install TWRP, just fastboot to it to flash zips
M66B said:
This saved my day:
Code:
fastboot --set-active=b
You might need to use "a" instead.
In my case the kernel was loaded and started and Android startup was hanging.
I guess we have to wait until this is fixed.
Edit: Pixel 3a XL, latest Android 11
Click to expand...
Click to collapse
I used this command (and tried to boot in slot a), the patched img still won't boot.
Did you managed to flash Magisk with patched boot file?
Here are all the boot.img and recovery.img of OxygenOS 11.0.0. Since TWRP isn't ready yet, I guess a lot of people need it if they didn't keep their root permissions.
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
OOS 11.0.0 EU:
boot.img
boot.img (Magisk v22 patched)
recovery.img
OOS 11.0.0 GLOBAL:
boot.img
recovery.img
OOS 11.0.0 INDIA:
boot.img
recovery.img
Please note: I'm not responsible for anything you do to your device. You use these files at your own risk. I will not provide any further .img files nor ask me for patched files. Any contribution with patched boot.img files is welcome of course. Also note although I'm a moderator, this thread is neither official nor in any way more or less trustworthy than any other contribution by other awesome members!
Would I be able to keep my phone rooted with this after updating?
This is very useful
thanks
jman12311 said:
Would I be able to keep my phone rooted with this after updating?
Click to expand...
Click to collapse
No, unless you use the Magisk patched EU version. Otherwise always install the update, then use the Magisk Manager to patch the inactive slot and then (only then!) reboot. Then you'll keep root.
Otherwise use the stock boot.img and patch with Magisk Manager. Then flash the patched image via fastboot. There are plenty of tutorials on XDA
Hi i installed the update already but didn't reboot what is the solution to keep root ?
Janusk22 said:
Hi i installed the update already but didn't reboot what is the solution to keep root ?
Click to expand...
Click to collapse
1. Install Magisk manager app
2. Open the app and choose "Install to inactive slot (After OTA)"
3. Reboot!
already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it
Janusk22 said:
already now i have a magisk module who is making bootloop i already have access to adb via recovery how to remove it
Click to expand...
Click to collapse
Use USB debugging and a PC with the code:
Code:
adb wait-for-device shell magisk --remove-modules
If USB debugging isn't enabled, flash the stock boot.img (without root), boot it, enable ADB debugging and allow the connection to the PC. Then flash the patched boot.img and execute the command above
That is assuming you have a OnePlus 7T Pro which doesn't have a decryptable recovery. Otherwise you can simply flash the Magisk uninstaller
But i have a error I think that i cannot write in system
I have always : cannot be accessible
Thanks i just had to run the command when i rebooted
Is just me or GPS takes more time to "fix" satellites?
FSadino said:
Is just me or GPS takes more time to "fix" satellites?
Click to expand...
Click to collapse
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.
Macusercom said:
Not longer than usual. But I often had GPS fix issues with my 7T Pro where it takes 5-10 minutes despite using A-GPS.
Click to expand...
Click to collapse
I calibrated the A-Gps again, let's see if that was it. Thank you
Hi I was wondering if you could possibly share the android 11 update file I have a Oneplus 7T Pro HD1910 currently on OOS 10.1.14 It would be awesome if you can PM me. I've tried downloading from Oygen Updater it fails at 98% also on XDA forum the download fails. I'd really appreciate it. Thanks
Macusercom said:
As I only have a EU device I can only provide a patched boot.img for that device. But with the original .img files it should be easy to patch and flash it yourself. To make it clear: boot.img and recovery.img are stock unless said otherwise. They've just been extracted from the payload.bin inside the respective OOS update zip file.
Click to expand...
Click to collapse
Hey, could you please share the payload.bin extract procedure?
Ia possible to use this files to back to stock rom from lineageos 18.1? If yes, can someone help me and give me the procedure how to do this?
For all the "EU" and "global" files, I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.
WARNING: THIS IS EXPERIMENTAL BETA MEANT FOR DEVELOPERS AND TESTERS NOT AS DAILY DRIVER
Caution: Android 11 builds are incompatible with Android 12. Beware!
Credits:
@Woomymy
@J6idot
@mastersenpai05
@myst33d
https://github.com/notmyst33d
Developers WoomyMy, J6idot , mastersenpai05 and Myst33d have helped develop an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
https://github.com/RedmiNote10S/recovery_device_xiaomi_rosemary
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
TWRP 3.6+ Development Build status, fixes, bugs and downloads: [here]
TWRP -3.6.2_11-2
NameModifiedTWRP-3.6.2_11-208/03/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update TWRP sources
DONT INSTALL THIS ON MIUI 13
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
TWRP-3.6.2_12-rc1
NameModifiedTWRP-3.6.2_12-rc108/04/2022
Changelog
Sync TWRP sources
Add support for Android 12 decryption
Fix booting on MIUI13
DONT INSTALL THIS ON MIUI 12.5
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With custom recovery
Download TWRP .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
MIUI 13 vendors: COMPATIBLE
MIUI 12 vendors:
A11 GSI / MIUI 12 system: FULLY INCOMPATIBLE
A12 GSI: COMPATIBLE, but you CAN NOT flash the boot.img, you need to flash the UPDATE ZIP using a custom recovery / Magisk
OrangeFox-R11.1_1-Unofficial
NameModifiedOrangeFox-R11.1_1-Unofficial07/01/2022
Changelog
Fix brightness when max brightness is 255
Render GUI at 60FPS
Reposition statusbar icons and remove top offset
A lot of code cleanup
Update OrangeFox sources
DONT INSTALL THIS ON MIUI 13
Update Magisk OrangeFox addon to v25.2
Install instructions
Without TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With custom recovery
Download OrangeFox .ZIP installer and flash it in recovery (you can also use adb sideload for recoveries like LineageOS recovery)
Compatibility
Android 11 Roms: YES
Android 12 Roms: NO
Older versions:
NameModifiedBeta-07-11-30-202112/17/2021
🗞 Changelog
Sync TWRP sources (Version number updated to 3.6.0)
Symlink /dev/block/bootdevice -> /dev/block/platform/bootdevice (required by some scripts like OrangeFox installer)
Allow flashing VBMeta
Disable "Reflash TWRP after flashing ROM". (Causes AVB problem when installing MIUI, can still be done manually)
Build ZIP TWRP installer
Publish build logs for more transparency
Known bugs
Mounting Adopted storage
Vibrator
NameModifiedRC-01-01-09-20221/9/2022
🗞 Changelog
Fix Bootctrl
Fix vibrator
Known bugs
Mounting Adopted storage
TWRP Version 3.6.1_11-1
NameModifiedTWRP-3.6.1_11-13/13/2022
🗞 Changelog
Fix BootCTRL
Update TWRP sources
Fix vibrator
Enable DT2W in recovery
Install instructionsWithout TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download TWRP .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Install -> Install Image -> Select stock boot.img -> “Flash to: Boot”)
Next, go in Advanced -> Flash current TWRP and swipe to flash TWRP.
Reboot and enjoy!
With TWRP/OrangeFox
Download TWRP .ZIP installer and flash in recovery
TWRP Version 3.6.2_11-1
NameModifiedTWRP-3.6.2_11-16/14/2022
🗞 Changelog
Sync TWRP sources
Orangefox Recovery Version R11.1_1-Beta
NameModifiedOrangeFox-R11.1_1-Beta3/13/2022
🗞 Changelog
Fix BootCTRL
Update OrangeFox sources
Fix vibrator
Enable DT2W in recovery
Update Magisk OrangeFox addon to 24.2
Install instructionsWithout TWRP/OrangeFox
Note: You need a copy of your ROM boot.img
Click to expand...
Click to collapse
This device DOES NOT support fastboot boot twrp.img
Click to expand...
Click to collapse
Reboot your phone into fastboot mode
Download Blank VBmeta and flash it using fastboot flash vbmeta vbmeta.img
Next, download OrangeFox .IMG file and flash it using fastboot flash boot IMAGE_NAME.img
Reboot into recovery mode (fastboot reboot recovery)
When booted into recovery, reflash stock boot.img (Select stock boot.img -> “Flash to: Boot”)
Next, go in Menu -> Flash current OrangeFox and swipe to flash OrangeFox.
Reboot and enjoy!
To get Fox addons working, you need to reflash OrangeFox .zip file
With TWRP/OrangeFox
Download OrangeFox .ZIP installer and flash in recovery
Nice, it's beta 2
to apply encrypt patch, you must decrypt first.
So
- you have to disable security password/fingerprint in your parameter first.
- then reboot in recovery
- format data
- reboot again to recovery and apply patch.
How to use redmi note 10s unofficial twrp recovery
test (beta 2) after disabling security (fingerprint and pin)
- flashing magisk.zip -> ok
- backup -> ok
- restore -> ok
- MTP internal SD -> ok
- MTP external SD -> nok, file manager stuck on it (win10 or linux mint)
Please full prosses explain and 1 question flash fastboot method
This the link of the Official Tutorial from the Unofficial TWRP Website:
unofficial twrp 3.6.1 Root Redmi Note 10s (rosemary) - unofficial twrp
Download unofficial twrp 3.6.1 root Redmi Note 10s, user who own Redmi Note 10s can root it by following the below instructions
unofficialtwrp.com
Great
miravision said:
Developer WoomyMy has released an unofficial TWRP for rosemary - xiaomi redmi note 10s
Installation Video:
Code:
https://www.mediafire.com/file/f4zcls9sgi3nkoj/352+redmi+note+10s.rar/file
http://www.mediafire.com/file/p3zhivru97bdlke/no-verity-opt-encrypt-6.1.zip/file
Since this is not yet official, only proceed if you are competent enough and brave.
(If you need instructions on how to flash, please do not flash this with fastboot method)
Feel free to discuss any bugs or issues and fixes so that everybody can benefit from our findings.
Click to expand...
Click to collapse
I'm sorry but, do you atleast have the permission to share this?
Also, WommyMy should be the guy to upload it, not you.
Edit: thanks for fixing the thread
Also you're missing the device tree.
Hello. As one of the developpers of this TWRP DT, I am not really OK with that.
Firstly, you linked the wrong device tree Real link here
Also, I didn't published this on XDA because this TWRP is still in BETA. And it contains major bugs, like flashing dynamic partitions in fastbootd. Even if bugs will me fixed, I was planning to wait a release candidate before publishing the release here (this will require even more testing, if people want to help us testing, this will be even better).
So please, can you delete this or add clear warnings about the beta state?
Regards, Woomy
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Woomymy said:
@miravision I think we should also add credits to people like @J6idot , @mastersenpai05 and Myst33d who did a great job helping building twrp.
Click to expand...
Click to collapse
Yes, I believe they should get their work credit.
Will be fix soon.. don't too hurry.
mastersenpai05 said:
Will be fix soon.. don't too hurry.
Click to expand...
Click to collapse
Thanks bro
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Wow., Hoping for releasing custom roms for our handsets.,keep up the good work devs
Katho536 said:
Keeps restarting when i try to flash a custom ROM from xiaomi eu, any Fix please ?
Click to expand...
Click to collapse
Xiaomi eu has no support for 10s iirc
No support for Mediatek devices on Xiaomi.eu, Global.rom and other
@miravision can u provide the vbmeta.img file?
Original post updated with attached vbmeta.img
langithitam said:
@miravision can u provide the vbmeta.img file?
Click to expand...
Click to collapse
Hi and thanks for sharing
Is it possible just to boot from TWRP recovery via Fastboot without flashing it on the phone?
I have also a Poco X3 NFC with stock MIUI 12.5 with Magisk root, but with stock recovery (so I can do all OTA updates) where I'm doing the same.
When I need it, I just do
fastboot boot TWRP-file.img
Thanks
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
blocky3321 said:
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
Click to expand...
Click to collapse
Because the ota cancel magisk robot. U have to repatch new boot.img and reflash magisk
PhotonIce said:
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
Click to expand...
Click to collapse
with the older versions i get suck in a boot loop and with the new version there is no root
blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
wetito said:
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
Click to expand...
Click to collapse
i tried the boot and vbmeta it didnt work got stuck in a boot loop
It you have 12.5.4 firmware working 100% I have flashed on my device
wetito said:
It you have 12.5.4 firmware working 100% I have flashed on my device
Click to expand...
Click to collapse
tried again and got suck on the miui screen on fastboot reboot
blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
PhotonIce said:
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
Click to expand...
Click to collapse
use magisk 24.1, because 24.2 it's a beta. it's buggy. my files are patched with 24.1
blocky3321 said:
tried again and got suck on the miui screen on fastboot reboot
Click to expand...
Click to collapse
1. Download the fastboot version of your rom here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I prefer 12.5.4 as it's not buggy, laggy as MIUI 13 and it has navigation button shortcuts, a new cool feature. Remind again, you must download Type fastboot, not Type recovery
2. Unzip downloaded rom, look for [rom name] folder -> images -> boot.img file
3. Copy that boot.img to your phone storage, any phone is fine
4. Run Magisk 24.1 on the any phone that got the boot.img file
5. Press Install
6. Choose Select and Patch a file
7. Navigate and choose the copied boot.img
8. You'll get something like this in your phone storage: magisk_patched-24100_VDv7z.img
9. Copy magisk_patched-24100_VDv7z.img to your PC
10. Install ABD 15 seconds installer, if not already done so
11. Get phone to fastboot mode
12. Use this command to enter fastbootd
Code:
fastboot reboot fastboot
13. Flash empty vbmeta.img:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Where is this vbmeta.img from? Check downloaded rom folder, look for [rom name] folder -> images -> vbmeta.img file
14. Use this command to flash your Magisk patched img:
Code:
fastboot flash boot magisk_patched-24100_VDv7z.img
Reminder: Each time Magisk patches an img file, it changes name randomly, so don't blindly input this command, you must change name too: fastboot flash boot [magisk patched boot name].img
15. Reboot to your phone's rom:
Code:
fastboot reboot
REQUIREMENTS - BL UNLOCKED
You need to be on VERSION : RMX3312_11.C.12_IN_202304230924
If not on RMX3312_11_C.12 version - download the entire OTA PACKAGE from the above link & LOCAL INSTALL
Reboot to Bootloader adb reboot bootloader or Power + Volume Down
Take the ROOT BOOT image from the zip file given below and PASTE it in platform tools folder
FLASH the ROOT BOOT IMAGE fastboot flash boot RMX3312_11.C.12_ROOTBOOT.img
Type - fastboot reboot
Finished - Now your Realme GT2 - RMX3312 is now ROOTED!
P.S. : FLASH ON BOTH SLOTS
To keep ROOT when you receive an OTA update
DOWNLOAD THE OTA UPDATE
Let it UNZIP
When it shows - INSTALL / REBOOT TO INSTALL option, put to recents - Open MAGISK
There in MAGISK - SELECT THE INSTALL OPTION on the TOP RIGHT
& then select INSTALL TO INACTIVE SLOT (AFTER OTA) OPTION
Click on OK on the POP-UP MENU in MAGISK
NOW THE DEVICE WILL REBOOT - UPDATE TO THE LATEST OTA & STILL KEEP ROOT!
DOWNLOADS : Both STOCK & ROOT boot images are attached below in one ZIP FILE!
Each Boot Image is 192MB & the compressed ZIP FILE below is 72.6MB.
NOTE : I'm NOT RESPONSIBLE FOR BRICKS, STONES, BLASTS, WIPES etc. of RMX3312
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
gx7x said:
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
Click to expand...
Click to collapse
He means you need to run the flash boot command for each slot
for instance your system runs on a slot, as soon as you type the
fastboot flash boot [boot image]
if it shows writing boot_a
then you need to type
fastboot flash boot_b [boot image]
to flash in the b slot also
if it shows writing boot_b
then you need to type
fastboot flash boot_a [boot image]
to flash in the a slot also
and you can pass the safteynet easily even when in root, u can use zygisk and magiskhide to pass the safteynet and you can run any banking app you want
Please do not use the boot images provided if you have not updated to the current latest version
Note: EU version boot image might be different so don't try
p.s you can extract boot images yourself from any version you want!
Stano36 said:
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
Click to expand...
Click to collapse
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
b0nb0n3v said:
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
Click to expand...
Click to collapse
We have two partitions so that if one fails the other can safely boot however most of us are careless and flash on both partitions so it's not really helpful for us
How to root gt 2 running on pixel os?
_PsyDuck_ said:
How to root gt 2 running on pixel os?
Click to expand...
Click to collapse
extract the pixel os file & patch the boot image using magisk & flash the magisk patched boot image
Thanks