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.
Related
Hello guys,
Yesterday I flashed my Mi 8 to get root permissions with Global V10.2.1.0 with Magisk 17.3, including Disable DM-Verity and Force Encrypt. Everything was working perfect, Magisk notified me about updating to v18, so I did, and MIUI notified me about an update (if I'm not mistaken, for 10.2.2.0).
MIUI downloaded the update and asked me to reboot to install it. It booted into TWRP and did the whole installation, apparently without issues, but then I restarted and it goes straight to TWRP.
I tried clearing cache/dalvik but nothing.
Every time I reboot and gets to TWRP, when I press the menu button to see the log, the last lines say:
Full SELinux support is present.
set_policy_failed:/datamisc
I don't know if this is relevant, but seeing a "failed" is not nice.
As an observation, the folder /data/system is full of folders, but the /system directly in root folder only has /usr/share/zoneinfo (I don't know if this is normal or not),
If the system updated to 10.2.2.0, would flashing to 10.2.1.0 set the ARB or it's safe for me to flash it again? Any ideas?
Thanks!
You need to flash Magisk again. Installing an OTA means you flash the stock boot.img so flash dm verity and magisk.
ArmedandDangerous said:
You need to flash Magisk again. Installing an OTA means you flash the stock boot.img so flash dm verity and magisk.
Click to expand...
Click to collapse
Thanks for the answer! Do I need to wipe DATA too?
EDIT: I just flashed DM-Verity and then Magisk and all good. No need to wipe data. Thanks!!
Here you can find latest boot image for OnePlus7 Pro rooted with Magisk.
ROM:
OnePlus7ProOxygen_21.E.13_OTA_013_all_1907050211_b8852b6
https://1drv.ms/u/s!AvJju0GuwXqysxoo9LNYN3wla8KX
Why do need the boot.img for root ?
I never used it for root my device.
khalisz said:
Why do need the boot.img for root ?
I never used it for root my device.
Click to expand...
Click to collapse
How old is the last phone you had?
Since Jul 9, 2019.
Cozzeck said:
How old is the last phone you had?
Click to expand...
Click to collapse
Since Jul 9, 2019.
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Does this work for the global version??
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
alexander1297 said:
Does this work for the global version??
Click to expand...
Click to collapse
The only difference between the global and the EU versions are supposed to be the LTE bands.
lichtblitz said:
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Click to expand...
Click to collapse
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Kengat said:
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Click to expand...
Click to collapse
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
lichtblitz said:
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
Click to expand...
Click to collapse
Oh cool. So like "dirty flashing". Will magisk also get killed in the proccess? I'm not sure how A/B partitions work. Do you just install magisk from twrp or do you have to somehow install it on both partitions?
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
dallasnights said:
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
Click to expand...
Click to collapse
Follow the steps on TWRP and rooting on my guide. Look in the Guides & Discussion section of XDA
Flashing this on International breaks the WiFi. Does anyone have the international version?
Hideaki02 said:
Flashing this on International breaks the WiFi. Does anyone have the international version?
Click to expand...
Click to collapse
just flash boot twrp and flash magisk there..
Arden144 said:
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
Click to expand...
Click to collapse
If you don't need TWRP, first booting it and flashing the zip takes way longer than "fastboot flash boot boot.img".
I cannot root my phone through TWRP for some reason and I would really like to use my phone with Google Pay.
K20 pro, MIUI Global 11.0.1 unlocked bootloader.
Install Magisk yourself. It will work.
Which zip did you flash? The right version of maiden
Magisk will work.
@XblackdemonX I can't install Magisk since it's giving me an error message. Tried every possible way with no luck
@Turbine1991 I have tried install "twrp-3.3.1-15-raphael-mauronofrio"
After installing it the phone is always going back to Stock rom recovery.
@XblackdemonX I can't install Magisk since it's giving me an error message. Tried every possible way with no luck
@Turbine1991 I have tried install "twrp-3.3.1-15-raphael-mauronofrio"
After installing it the phone is always going back to Stock rom recovery.
cohenelad said:
I cannot root my phone through TWRP for some reason and I would really like to use my phone with Google Pay.
K20 pro, MIUI Global 11.0.1 unlocked bootloader.
Click to expand...
Click to collapse
install magisk 19.3
Video install
https://drive.google.com/file/d/16vDfZDWBgtY8_ECB8aRWNed_6mqctY5T/view
@redmiK20ProIndonesia
Are you rebooting the device after installing TWRP? If you installed TWRP then rebooted without first trying to install Magisk it'll probably just stick the stock recovery back in place and overwrite TWRP if nothing is done to circumvent stock recovery overwrite. If this doesn't apply then no worries but thought I'd mention it.
That's also an old version of TWRP; have you tried a newer version? I'd say try fastboot boot recovery.img then immediately attempt to install Magisk. You're on MIUI11 so you'll want to go with Magisk 19.3.
cohenelad said:
After installing it the phone is always going back to Stock rom recovery.
Click to expand...
Click to collapse
You have to install Magisk to prevent the recovery from changing back to stock.
Hi.
Just after installing the .zip magisk file in twrp, my redmi k30 reboot as it should and after that it stays bricked in the bootloader. I've been able to reinstall the rom but I want to install magisk on the phone. I've tried it another time and the issue persists. Any idea of the origin of the problem? How can I install magisk?
I dont have k30, but you should flash lower version, say 19.3, it might help
lexobys01 said:
I dont have k30, but you should flash lower version, say 19.3, it might help
Click to expand...
Click to collapse
I've tried it but the issue persists
Give it another try by instaling magisk manager app first, then flash magisk from the manager. If it's still not working, remove with magisk uninstaller, rather than flashing the whole ROM, and try with 20.1
As for me I installed MIUI.eu using fastboot and then pull the boot.img from the ROM, patch it using magisk manager & fastboot flash the patched boot.img. From there you can get a proper magisk & passed all safety net check
Hi!
I have pushed my MI 9 into bootloop and need help to get it back working.
The bootloader is unlocked, Magisk and TWRP are installed. I tried to install the latest Universal SafetyNet Fix, but instead of installing it inside Magisk I have "installed" the ZIP with TWRP and wiped the delvik cache. Now the phone is in bootloop.
In the Universal SafetyNet Fix- threat I got the hint to reinstall the stock boot.img, but I am unsure how to do this and which file to use.
Can I just use one of the boot.img linked in this threat, e.g., the one in 10.2.24.0?
[Root images] Boot 10.2.24.0 & 10.2.9.0 & 10.2.26.0
Version 10.2.26.0 Version 10.2.24.0 ------------ > Stock/Root Version 10.2.9.0
forum.xda-developers.com
and install it with fastboot, i.e., "Fastboot flash boot.img" ?
Or is there another solution to my problem, e.g., uninstall the safetynet-fix-v1.1.0.zip ?
Well, I gave it a try, but it doesn't work. Now the phone doesn't even show the MIUI logo anymore. Fortunately, I had made a backup with TWRP before I tried this, and I could reflash the old boot.img with
fastboot flash boot boot.emmc.win
Now at least the MIUI logo appears again, but my original problem is still there, the phone still doesn't boot completely, but resets and goes into twrp.
Problem solved by deleting the safetynet-fix folder. Thanks to Durete for this tip!
How to Uninstall Magisk Modules Using TWRP Recovery
Removing the Magisk module manually causes bootloop. You can easily uninstall Magisk modules using TWRP recovery without resetting your device.
www.droidviews.com
Durete said:
The easy way....
How to Uninstall Magisk Modules Using TWRP Recovery | DroidViews
Click to expand...
Click to collapse