Hello everyone,
While trying to unroot my redmi note 8t (with magisk),
I forgot to click on "uninstall" in the application and I directly flashed the boot.img of the official ROM with fastboot.
I'm stuck at the "MIUI" step.
I tried to reflash the modified boot.img from magisk but without result.
Thanks a lot for your help.
a bit lost, this is a boring redmi 8 subforum, not the note 8 ;P
Redmi Note 8
The Redmi Note 8 is a 6.3" phone with a 1080 x 2340p resolution display. The Qualcomm Snapdragon 665 is paired with 4/6/8GB of RAM and 64/128GB of storage. The main camera is 48+8+2+2MP and the selfie camera is 13MP. The battery has a 4000mAh capacity.
forum.xda-developers.com
its a good thing you kept backups of the boot.imgs. try testing by booting to system after each tests. technically after you manually reflashed the original boot.img youve already uninstalled magisk and are all good to boot, try wiping dalvik+caches. if that also fails try to reflash the patched boot.img, rename and flash magisk.apk to uninstall.zip, and wiping caches. if all else fails, backup your data and get ready for a format data/factory reset. reflashing fw is a last resort.
the normal method of uninstalling magisk is by either uninstalling it by the app, or renaming the .apk as uninstall.zip. on older magisk versions manually uninstalling does work, but i havent tried it on v23.
Related
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.
i recently bought the k20 pro with the 512gb storage and i wanted to root with magisk because a few games are not working.
the thing is i dont know where to start. i dont want to brick my phone.
miui version is 10.3.3 and is being identified as mi 9t pro.
ok so i followed a guide and finished installing twrp and magisk but after flashing magisk it know boots into the mi recovery menu. any help?
more info
Xiaomi K20 pro premium
Miui global 11.0.1
TWRP 3.3.1-25
magisk 2.0.1
if i install magisk version i get a boot loop to TWRP and if i use older versions i get a boot loop to mi recovery.
any help please?
That could be encryption issue. Please format data (Not wipe) to remove encryption and flash dfe (to disable force encryption) and magisk (for root).
Kiesport said:
That could be encryption issue. Please format data (Not wipe) to remove encryption and flash dfe (to disable force encryption) and magisk (for root).
Click to expand...
Click to collapse
i tried flashing dfe and magisk after but i get some error when flashing magisk. i ended up installing the eu rom and now the apps works.
When I try to install a ROM, no problem installing TWRP and flashing a ROM.
But when I restart, whatever the ROM it systematically restarts on TWRP.
Everything is back to normal when I reinstall the MiUi ROM.
I installed vbmeta, TWRP is kept even with the MiUi ROM.
I tried to install a ROM on MiUi but nothing happened, TWRP is launched systematically after restarting.
I tried with several versions of TWRP but nothing worked.
Also with LOLz kernel with and without; and Magisk too.
Sleep on it !
you have to format DATA and not Wipe !
Hello guys! I'm new here and don't know where to get help. My phone (Xiaomi 4g [phoenix]) has a weird bootloop to it.
I installed Miui 13 eu rom via the name of file is "windows_fastboot_first_install_with_data_format" now I get a bootloop that goes back to TWRP.
When i checked the my storage on my pc it only shows TWRP folder only. i don't know what to do. i've been sitting the whole day trying to figure to fix my phone.
I downloaded a Miui 12 and installing it via twrp. now after a few minutes of waiting and still get backs to TWRP.
1999romelx said:
Hello guys! I'm new here and don't know where to get help. My phone (Xiaomi 4g [phoenix]) has a weird bootloop to it.
I installed Miui 13 eu rom via the name of file is "windows_fastboot_first_install_with_data_format" now I get a bootloop that goes back to TWRP.
When i checked the my storage on my pc it only shows TWRP folder only. i don't know what to do. i've been sitting the whole day trying to figure to fix my phone.
I downloaded a Miui 12 and installing it via twrp. now after a few minutes of waiting and still get backs to TWRP.
Click to expand...
Click to collapse
wrong subforum, heres the poco x2 subf
Xiaomi Poco X2
The Xiaomi Poco X2 is a 6.67" phone with a 1080x2400p resolution display. The Qualcomm SDM730 Snapdragon 730G chipset is paired with 6/8GB of RAM and 64/128/256GB of storage. The main camera is 64+8MP and the selfie camera is 20+2MP. The battery has a 4500mAh capacity.
forum.xda-developers.com
sounds like your data got wiped, thats why theres only a twrp folder in internal. you should prolly full flash a fastboot rom since you mightve missed a few important steps
Hi Fonzacus
Please tell me
What is the reason for flashing that vbmeta img?
Is it always necessary when clean flashing latest crdroid custom ROM?
johndaog said:
Hi Fonzacus
Please tell me
What is the reason for flashing that vbmeta img?
Is it always necessary when clean flashing latest crdroid custom ROM?
Click to expand...
Click to collapse
sorry for the super late response
its supposedly for bypassing android verfied boot (avb). it blocks unauthorized roms from booting. if you search for 'what is vbmeta', we literally get no info at all and mainly speculations (no official docs etc). imho it does seem true
Hello to all,
I tried 1 year ago to root my POCO M3 Pro 5G but could not succeed to install TWRP unofficial for this model because of the problem of non-existent recovery partition (see https://forum.xda-developers.com/t/...oco-m3-pro-5g-redmi-note-10-5g.4474375/page-2) In short I bricked my device several times and then I had a boot with a weird screen that disappeared when I updated to MIUI 13.
Today I am on Android 12 MIUI global 13.0.3 and I would like to install magisk manager without the help of TWRP and I have the default recovery of MIUI with which I can not install anything.
I had also followed the procedure described https://forum.xda-developers.com/t/...urself-and-optionnal-debloat-privacy.4337693/ but without success impossible to flash on A or B : error messages : too many links, the partition does not exist (see screen shot in PJ), no emulator etc
The bootloader is still unlocked
I would like to root my phone and use Magisk manager modules such as Skvalex without damage or install root apk with spyware and trojan.
Do you have any solutions for me?
Thank you very much for your answers.
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
Ok tx I'll try this method and let you know
install magisk via fastboot is the easiest way for rooting. and more safe than using custom recovery. follow the guides with more attention. bad twrp can damage bootloader. bad flash of stock can damege device
i think the twrp have broked your boot, and i suppose u have flashed a wrong stock rom.
before made other damage, if can enter into fastboot: be sure to download right firmware. and flash it without relock option. if u dont do this, the risk is a serious hard brick. for who is not able to do a simply procedure like rooting, an hard brick is impossible to repair . be carefull
I have rooted my phone with magisk without any recovery, you just have to modify boot.img and flash it using fastboot.
I followed this method- https://www.getdroidtips.com/root-poco-m3-pro-5g/
Good evening
Thanks for your 2 answers.
I finally succeeded in laboriously rooting and patching on A and B but the modops on https://www.getdroidtips.com/root-poco-m3-pro-5g/ are incomplete and/or inaccurate. For example it is necessary to specify that it is necessary to download not the recovery version of the ROM but the fastboot version which is not underlined in the text of the link and other details of this type which avoid wasting time other example to find in the repertory the file of the patch.img even not hidden difficult to find even with the way and invisible via the directory of windows.
I have the root and I have installed modules on Magisk manager finally after the first attempt 12 months ago.
Cheers
I have a Redmi Note 10 pro (Sweetin) Indian Variant and I have rooted it using magisk. Can I get update my device or will face things like loosing root or bootloop?
Device Name: Redmi Note 10 pro
Region: India
Code name: Sweetin
Magisk Version: 26.0
Recovery / Fastboot: Fastboot
OS: MIUI 13
For recovery update/upgrade, not really. You will lose your root yes but that's because boot.img will be replaced by stock ROM, in this case, you'll just have to reflash magisk after. Also, I advise to temporarily disable all modules before updating to avoid bootloops. If bootloop ever happened and magisk modules might be the culprit, just head to /data/adb/ and delete the modules folder.
For fastboot update, yes, root will be lost too.
BigChungus321 said:
For recovery update/upgrade, not really. You will lose your root yes but that's because boot.img will be replaced by stock ROM, in this case, you'll just have to reflash magisk after. Also, I advise to temporarily disable all modules before updating to avoid bootloops. If bootloop ever happened and magisk modules might be the culprit, just head to /data/adb/ and delete the modules folder.
For fastboot update, yes, root will be lost too.
Click to expand...
Click to collapse
If bootloop happens in fastboot update what should I do? I won't be able to go into the /data/adb right?
Hehe_boi said:
If bootloop happens in fastboot update what should I do? I won't be able to go into the /data/adb right?
Click to expand...
Click to collapse
Well yes, but it rarely happens. I recommend upgrading through recovery methods anyways. I've only ever use fastboot when downgrading. Upgrading through recovery ensures that you'd still have access to your data after upgrade.