Related
Hey y'all - I saw this and am wondering if this is still applicable?
I'm on v7 with phh's SuperUser r259; so if, say, the November security patch drops, I can accept, download, and install directly from the notification panel? Or am I reading this wrong?
TIA!
alamo76 said:
Hey y'all - I saw this and am wondering if this is still applicable?
I'm on v7 with phh's SuperUser r259; so if, say, the November security patch drops, I can accept, download, and install directly from the notification panel? Or am I reading this wrong?
TIA!
Click to expand...
Click to collapse
You should be able to, but you will have to reflash the magisk zip so that the boot image is re-patched. I accepted an OTA on my Nexus 6P without any issues although I did use Flashfire.
ryaniskira said:
You should be able to, but you will have to reflash the magisk zip so that the boot image is re-patched. I accepted an OTA on my Nexus 6P without any issues although I did use Flashfire.
Click to expand...
Click to collapse
I want to try to start from stock and be able to get OTA updates.
First post in phh's SuperUser states that phh's SuperUser r259 "Magisk compatible, no boot image modifications are required"
So then I am guessing we don't need to reflash Magisk again since boot image is untouched.
Also what about the recovery? Will OTA update replace the twrp and therefore, TWRP needs to be reflshed after each OTA update.
Maybe someone who experienced this can write what needs to be done in order to successfully flash OTA update.
Thanks.
Orochi77 said:
I want to try to start from stock and be able to get OTA updates.
First post in phh's SuperUser states that phh's SuperUser r259 "Magisk compatible, no boot image modifications are required"
So then I am guessing we don't need to reflash Magisk again since boot image is untouched.
Also what about the recovery? Will OTA update replace the twrp and therefore, TWRP needs to be reflshed after each OTA update.
Maybe someone who experienced this can write what needs to be done in order to successfully flash OTA update.
Thanks.
Click to expand...
Click to collapse
Yes because Magisk itself modifies the boot image. So that's why the Magisk version of PHH Superuser doesn't modify the boot image.
Also, you can use FlashFire to install OTAs and preserve the custom recovery, also you can set it to reflash Magisk after the OTA. (With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire)
ryaniskira said:
Yes because Magisk itself modifies the boot image. So that's why the Magisk version of PHH Superuser doesn't modify the boot image.
Also, you can use FlashFire to install OTAs and preserve the custom recovery, also you can set it to reflash Magisk after the OTA. (With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire)
Click to expand...
Click to collapse
But FlashFire says it needs SuperSU or cm's SU
KaMonsieur said:
But FlashFire says it needs SuperSU or cm's SU
Click to expand...
Click to collapse
PHH's Superuser technically is CM's SU, it's a fork of Koishik's Superuser that was used in CM up until MM.
ryaniskira
With PHH Superuser, SELinux needs to be in permissive mode to use FlashFire
Click to expand...
Click to collapse
I am on stock samsung kernel which is set to SELinux enforcing.
What are my options in terms of getting OTA and what needs to be done?
Do I accept OTA, then flash recovery and flash Magisk + PHH Supersuser?
Can I use Flashfire with supersu instead of PHH superuser, will it work with SELinux enforcing?
Thanks for your time.
ryaniskira said:
PHH's Superuser technically is CM's SU, it's a fork of Koishik's Superuser that was used in CM up until MM.
Click to expand...
Click to collapse
I once used SuperSU and FlashFire. But I did not set SElinux to permissive myself. Does SuperSU automatically do it?
KaMonsieur said:
I once used SuperSU and FlashFire. But I did not set SElinux to permissive myself. Does SuperSU automatically do it?
Click to expand...
Click to collapse
SELinux does not need to be set to permissive when you use SuperSU because SuperSU modifies SEPolicy to allow his apps to work with SELinux set to enforcing.
ryaniskira
So to get OTA update in a reliable way. One has to do the following steps.
1. TWRP
2. SuperSu
3. Magisk 7
4. Flashify
Let me know if this is correct?
ryaniskira said:
SELinux does not need to be set to permissive when you use SuperSU because SuperSU modifies SEPolicy to allow his apps to work with SELinux set to enforcing.
Click to expand...
Click to collapse
Thanks for your help!
Answering to my previous post.
In my case flashfire was useless as it could not detect ota zip update at all on my S5, even when I pointed flashfire to the exact location.
It is possible that the OTA zip is encrypted. I could not even open it as archive.
Even if system is untouched, updater detects custom boot image (patched by supersu) and custom recovery. I was able to fool the system by turning the device status to official. Then flashing original recovery and flashing the OTA. Of course after this, you would have to flash custom recover, root and magisk. Unless the process with stock recovery and stock boot is automated, it seems like too much work.
For now, the easiest solution is just to flash an updated firmware when it comes out. This way it will update everything while preserving your data partition.
This begs me to ask this question. Why even bother with systemless this or systemless that. At the end after flashing an updated firmware, the system partition will be overwritten whether it was systemless or not.
Orochi77 said:
Answering to my previous post.
In my case flashfire was useless as it could not detect ota zip update at all on my S5, even when I pointed flashfire to the exact location.
It is possible that the OTA zip is encrypted. I could not even open it as archive.
Even if system is untouched, updater detects custom boot image (patched by supersu) and custom recovery. I was able to fool the system by turning the device status to official. Then flashing original recovery and flashing the OTA. Of course after this, you would have to flash custom recover, root and magisk. Unless the process with stock recovery and stock boot is automated, it seems like too much work.
For now, the easiest solution is just to flash an updated firmware when it comes out. This way it will update everything while preserving your data partition.
This begs me to ask this question. Why even bother with systemless this or systemless that. At the end after flashing an updated firmware, the system partition will be overwritten whether it was systemless or not.
Click to expand...
Click to collapse
For me, the greatest benefit with Magisk is that after an update (by flashing relevant parts of the factory image) all that is needed for my different system modifications is to flash Magisk. It has cut the time it takes for me to update by a huge factor.
Didgeridoohan said:
For me, the greatest benefit with Magisk is that after an update (by flashing relevant parts of the factory image) all that is needed for my different system modifications is to flash Magisk. It has cut the time it takes for me to update by a huge factor.
Click to expand...
Click to collapse
What tool are you using to flash your firmware?
Orochi77 said:
What tool are you using to flash your firmware?
Click to expand...
Click to collapse
Big update, fastboot from my PC. Small update (monthly security update), flash boot and system image in TWRP.
Didgeridoohan said:
Big update, fastboot from my PC. Small update (monthly security update), flash boot and system image in TWRP.
Click to expand...
Click to collapse
Ok thanks. I have to use odin as I have Samsung phone.
When you flash system and boot, don't you lose root?
Orochi77 said:
Ok thanks. I have to use odin as I have Samsung phone.
When you flash system and boot, don't you lose root?
Click to expand...
Click to collapse
Flashing boot image means I need to reflash Magisk (and my custom kernel), but that's it. I use Magisk compatible phh's superuser, which means that's all I need to do. That's why I use (and love) Magisk.
I'm sorta n00b these days been years since ive been much into modding, but got a couple simple questions, i think i know the answer from what i've seen and read, but just want to verify. Save myself a bit of time if i screw it up.
My Device:
LG Nexus 5x Stock ROM 7.1.1 (Recently Flashed clean image that included Feb 2017 security patch) w/ElementalX Kernel
Magisk v11.x (whatever the most recent is, it's up to date) w/phh superuser
I want to flash the new March 2017 Security patch, ideally without losing any data or having to restore all my apps and data from backup ect.. This is what it seems i should do, i think i can use Flashfire (yes it detects my OTA packages and asks to prepare to flash):
I do backups regularly via otg to an external drive. Just completed one before this post
1. Flash OTA, allow flashfire to handle
2. (RE)flash magisk zip
3. (RE)flash phh superuser
4. (RE)flash elementalX kernel
This should leave everything as it was when i started relatively unmodified besides having the new security patch added yes?
g0d0fmischief said:
I'm sorta n00b these days been years since ive been much into modding, but got a couple simple questions, i think i know the answer from what i've seen and read, but just want to verify. Save myself a bit of time if i screw it up.
My Device:
LG Nexus 5x Stock ROM 7.1.1 (Recently Flashed clean image that included Feb 2017 security patch) w/ElementalX Kernel
Magisk v11.x (whatever the most recent is, it's up to date) w/phh superuser
I want to flash the new March 2017 Security patch, ideally without losing any data or having to restore all my apps and data from backup ect.. This is what it seems i should do, i think i can use Flashfire (yes it detects my OTA packages and asks to prepare to flash):
I do backups regularly via otg to an external drive. Just completed one before this post
1. Flash OTA, allow flashfire to handle
2. (RE)flash magisk zip
3. (RE)flash phh superuser
4. (RE)flash elementalX kernel
This should leave everything as it was when i started relatively unmodified besides having the new security patch added yes?
Click to expand...
Click to collapse
PHH Superuser is not compatible with v11
1. It is either Systemless SuperSU (installed before Magisk, or the included MagiskSU (if systemless SU is not installed before Magisk).
jhedfors said:
PHH Superuser is not compatible with v11
1. It is either Systemless SuperSU (installed before Magisk, or the included MagiskSU (if systemless SU is not installed before Magisk).
Click to expand...
Click to collapse
I did it with a previous version, and upgrade to version 11. As long as i follow those steps to get back to 11 it shouldn't matter does it? Meaning flash the other version of magisk i did to start with along with the corresponding phh su, then allow it to update to v11. This is how i got to v11. I planned on using the very same files to flash and root that i did before and allowing it to update. I read the magisk thread about the updates and changes to it. If this isn't a good idea, or just flat out won't work on that basis of trying to flash the older version and allowing the upgrade as i did initially, should i just flash magisk v11? Didn't want to stray from what worked in this regard. But yea ive read this from the magisk thread
If you're already rooted with MagiskSU, Magisk phh's superuser (not original), or Official Systemless SuperSU
Install/upgrade Magisk Manager from Play Store
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
I will have lost root by flashing the OTA, right? So say i flash just magisk v11 afterwards, what would i need to flash for root and the app to use once started?
This is the method for rooting and magisk install that i used.. Just allowed it to update to 11 after it starts. Do you mean to say this won't work again?
http://www.theandroidsoul.com/systemless-root-magisk-android/
Stock Kernel + SafetyNet Patch + DRM Fix
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox; AndroidFileHost
Sourse: 32.3.A.2.33; 32.4.A.0.160; 32.4.A.1.54
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430
There's a better way than using the boot partition. If you use the ramdisk method, and get it to a recovery partition, you can do almost anything back and forth without having to change boot images. you can just flash over everything and still maintain your recovery partition.
https://forum.xda-developers.com/showthread.php?t=3588365
https://forum.xda-developers.com/showthread.php?t=3609358
@NeoBeum
At me on stock firmware of Magisk, doesn't hide SafetyNet and therefore I compiled this kernel.
grayleshy said:
@NeoBeum
At me on stock firmware of Magisk, doesn't hide SafetyNet and therefore I compiled this kernel.
Click to expand...
Click to collapse
grab the recovery image I made and then flash it to recovery while you're using your kernel, then flash magisk I the fota/recovery partition recovery, then magisk will be able to capture the sepolicy it needs, then you should be able to flash a full ftf excluding FOTAKernel. to test, you'll have 2 recovery working. the one that's in the boot img, and recovery img.
I had this at the start, and once I got recovery to the recovery partition, ive been free to flash anything if I exclude the fotakernel wipe.
I had to add the fstab for the older Android versions. but I haven't included that in the prebuilt recovery.
magisk only needs to capture a pure system and boot image once, and it mirrors it. after that, you can load up modified kernels
IT s nice to see A kernel for nougat..
What about other functions of kernel? All stock?
emosis said:
What about other functions of kernel?
Click to expand...
Click to collapse
In the future, if I have the desire, then I will make a custom kernel with improvements.
The first will be a raised version of the kernel with 3.10.84 to 3.10.105.
emosis said:
All stock?
Click to expand...
Click to collapse
What do You mean?
Can i flash and working with LOS 14.1?
reevdre said:
Can i flash and working with LOS 14.1?
Click to expand...
Click to collapse
The kernel is only for stock firmware!
On other firmware, the stability is not guaranteed.
reevdre said:
Can i flash and working with LOS 14.1?
Click to expand...
Click to collapse
if they haven't made a recovery for LOS, I'll have a recovery twrp port for it after the Z5C gets official support for the Omni base, AOSP is completed, but there's no room on their build server for new AOSP devices
Can you update this for .160? I have the kernel. Thanks!
dlee390 said:
Can you update this for .160? I have the kernel.
Click to expand...
Click to collapse
Sony did not post the kernel sources. dev
oh ok thanks!
also, why doesn't this work with magisk like your other kernels for z5p and z5? thanks!
dlee390 said:
also, why doesn't this work with magisk like your other kernels for z5p and z5? thanks!
Click to expand...
Click to collapse
Use magisk v13.
Upd 32.4.A.0.160
Need update for 32.4.A.1.54 rom
frager45 said:
Need update for 32.4.A.1.54 rom
Click to expand...
Click to collapse
Well, I'll do it!
Upd 32.4.A.1.54.
GreyLeshy said:
Upd 32.4.A.1.54.
Click to expand...
Click to collapse
Thnaks, but wi-fi not opening...
I try press on button but not pressing...
frager45 said:
Thnaks, but wi-fi not opening...
I try press on button but not pressing...
Click to expand...
Click to collapse
Provide a screenshot of the terminal command lsmod.
I like to switch between two different developer's kernels and they seem to work better when flashed over the stock kernel and not custom kernel 2 being flashed over custom kernel 1.
My resolution to this is to restore to my stock rooted with magisk kernel then flash the other custom kernel. This results in a Magisk brick where you can't uninstall Magisk and you can't install magisk again due to the stock boot image being modified. The only answer to fix the Magisk brick is a system wipe and rom re-install.
If I uninstall between kernels, all of my Magisk settings and modules are uninstalled too if it doesn't just give the modified boot img thing again.
How can I swap between kernels while restoring stock without getting Magisk bricked?
Example: Custom Kernel 1 > Stock Kernel > Custom Kernel 2. This always leads to the Magisk brick.
Nexus 6, 7.1.2 NitrogenOS, Stock kernel, ElementalX kernel, FK Kernel.
Whenever I have to move between kernels, I do the following:
Dirty flash ROM zip (to restore the stock boot.img that ships with the ROM) or manually extract the boot.img from your ROM's flashable zip and fastboot flash it
Flash Magisk zip
Flash new kernel zip
Reboot and profit!
I haven't faced any issues ever with this process, following the order listed above. Give it a shot. Good luck! :good:
shadowstep said:
Whenever I have to move between kernels, I do the following:
Dirty flash ROM zip (to restore the stock boot.img that ships with the ROM) or manually extract the boot.img from your ROM's flashable zip and fastboot flash it
Flash Magisk zip
Flash new kernel zip
Reboot and profit!
I haven't faced any issues ever with this process, following the order listed above. Give it a shot. Good luck! :good:
Click to expand...
Click to collapse
Y no back up stock boot from the starting?
redsun_ravi said:
Y no back up stock boot from the starting?
Click to expand...
Click to collapse
Why do you need to backup the stock boot image from the beginning? It's already a part of the ROM zip that you flash. You can always dirty flash to go back to the boot image that ships with the ROM that you are using or extract it from your ROM's flashable zip.
shadowstep said:
Why do you need to backup the stock boot image from the beginning? It's already a part of the ROM zip that you flash. You can always dirty flash to go back to the boot image that ships with the ROM that you are using or extract it from your ROM's flashable zip.
Click to expand...
Click to collapse
Y unpack rom and repack boot
Y flash whole rom and loss magisk setting, fonts, adblock host and other stuff
While u can just give 10 sec to back up boot
xNotta said:
I like to switch between two different developer's kernels and they seem to work better when flashed over the stock kernel and not custom kernel 2 being flashed over custom kernel 1.
My resolution to this is to restore to my stock rooted with magisk kernel then flash the other custom kernel. This results in a Magisk brick where you can't uninstall Magisk and you can't install magisk again due to the stock boot image being modified. The only answer to fix the Magisk brick is a system wipe and rom re-install.
If I uninstall between kernels, all of my Magisk settings and modules are uninstalled too if it doesn't just give the modified boot img thing again.
How can I swap between kernels while restoring stock without getting Magisk bricked?
Example: Custom Kernel 1 > Stock Kernel > Custom Kernel 2. This always leads to the Magisk brick.
Nexus 6, 7.1.2 NitrogenOS, Stock kernel, ElementalX kernel, FK Kernel.
Click to expand...
Click to collapse
shadowstep said:
Whenever I have to move between kernels, I do the following:
Dirty flash ROM zip (to restore the stock boot.img that ships with the ROM) or manually extract the boot.img from your ROM's flashable zip and fastboot flash it
Flash Magisk zip
Flash new kernel zip
Reboot and profit!
I haven't faced any issues ever with this process, following the order listed above. Give it a shot. Good luck! :good:
Click to expand...
Click to collapse
No real need to fastboot flash it, just flash the boot.img in TWRP, only takes a second before you flash Magisk
Sent from my H1611 using Tapatalk
redsun_ravi said:
Y unpack rom and repack boot
Y flash whole rom and loss magisk setting, fonts, adblock host and other stuff
While u can just give 10 sec to back up boot
Click to expand...
Click to collapse
Repack boot? I never said that anywhere. Also, I hope you mean unzip the ROM zip file.
Anyway, backing up the boot image would serve no purpose as the OP wants to switch to a different kernel, which means a different boot image that the one he/she is using right now. It'll be pointless.
BurnedDrake said:
No real need to fastboot flash it, just flash the boot.img in TWRP, only takes a second before you flash Magisk
Click to expand...
Click to collapse
Of course the boot image can be flashed via TWRP too. I just gave that as an alternative option. Never said it has to be done a certain way.
shadowstep said:
Repack boot? I never said that anywhere. Also, I hope you mean unzip the ROM zip file.
Anyway, backing up the boot image would serve no purpose as the OP wants to switch to a different kernel, which means a different boot image that the one he/she is using right now. It'll be pointless.
Of course the boot image can be flashed via TWRP too. I just gave that as an alternative option. Never said it has to be done a certain way.
Click to expand...
Click to collapse
Oh I know, it wasn't a criticism, just one less reboot is all
Sent from my H1611 using Tapatalk
redsun_ravi said:
Y unpack rom and repack boot
Y flash whole rom and loss magisk setting, fonts, adblock host and other stuff
While u can just give 10 sec to back up boot
Click to expand...
Click to collapse
U don't lose all the magisk stuff on dirty flash. The only way u lose all that is running the magisk uninstaller. I wipe system, boot, and cache, dirty flash ROM, then magisk, then new kernel. All magisk modules, host files, settings are still present no matter what device or what ROM. Boot is included in ROM so dirty flash flashes that stock boot.img and starts fresh.
You can flash kernel with fastboot.
Extract boot.img from zip, then run
fastboot flash boot boot.img
After that you can backup boot in twrp and flash magisk.
Repeat with other kernel.
Hey guys,
So I've got an A/B device which makes taking OTA updates tremendously easy. I've actually took OTA updates with Magisk installed no problem.
The tricky part is, I use Stock ROM in combination with a custom kernel, I have backups of the stock kernel but my question is hard to ask. I'll write as clear as I can so please bare with me...
I installed the vanilla stock rom, It comes with the stock kernel. What I did was, Patch the kernel with Magisk 19.3, took a backup of it and then installed a Custom kernel with Magisk retain script on it. So my Magisk 19.3 installation was intact. Now that v19.4 is going to be released soon, I will have to install the stock kernel back. So my question is - If I install v19.4 on my custom kernel and then revert to the stock kernel which has 19.3 installed, Will it cause any trouble to my modules or will it revert back to v19.3?
TIA for any answers.
CarbonGTR said:
Hey guys,
So I've got an A/B device which makes taking OTA updates tremendously easy. I've actually took OTA updates with Magisk installed no problem.
The tricky part is, I use Stock ROM in combination with a custom kernel, I have backups of the stock kernel but my question is hard to ask. I'll write as clear as I can so please bare with me...
I installed the vanilla stock rom, It comes with the stock kernel. What I did was, Patch the kernel with Magisk 19.3, took a backup of it and then installed a Custom kernel with Magisk retain script on it. So my Magisk 19.3 installation was intact. Now that v19.4 is going to be released soon, I will have to install the stock kernel back. So my question is - If I install v19.4 on my custom kernel and then revert to the stock kernel which has 19.3 installed, Will it cause any trouble to my modules or will it revert back to v19.3?
TIA for any answers.
Click to expand...
Click to collapse
I own a 6T, so yes I'm also in the A/B scene
I have a similar setup as yours, just I'm not using Custom Kernel.
AFAIK, it's best to install Magisk on Stock Boot Image. But IMO, if you upgrade to Magisk v19.4 from your current v19.3-patched boot image, I think you'll not be facing any issues. If you do face it, you can simply dirty flash the ROM zip & that'll help you out
And regarding that question, if you restore the stock kernel, you should re-flash Magisk v19.4 zip after restoring it to avoid any issues caused by incompatibilities.
Sent from my #FlagshipKiller6T using Tapatalk
DarkSJ1998 said:
I own a 6T, so yes I'm also in the A/B scene
I have a similar setup as yours, just I'm not using Custom Kernel.
AFAIK, it's best to install Magisk on Stock Boot Image. But IMO, if you upgrade to Magisk v19.4 from your current v19.3-patched boot image, I think you'll not be facing any issues. If you do face it, you can simply dirty flash the ROM zip & that'll help you out
And regarding that question, if you restore the stock kernel, you should re-flash Magisk v19.4 zip after restoring it to avoid any issues caused by incompatibilities.
Click to expand...
Click to collapse
Upgrading is not an issue for me
It's that the stock kernel backup has v19.3 installed on the boot image. Now that v.19.4 is going to be released soon, I will have to upgrade and when the OTA comes I will have to go back to my stock kernel with 19.3 installed, I just need to know if going from v19.4 to v19.3 will give me troubles.
Cheers.
Update - I just updated my Magisk Stable v19.3 to Beta v19.4 and then rebooted my phone so my Magisk is updated. Now, I restored the stock kernel with magisk v19.3 over the custom kernel with v19.4 beta and observed that my Magisk installation reverted back to v19.3. Nothing happened to the system or my modules. So I guess it safe to downgrade but I will never recommend doing that.
So there's the answer to my question and maybe yours...
I'm new here on this site and idk if I'm doing I correctly but I need help with it. I'm a noob to rooting and Twrp stuff. I have unlocked my bootloader and have tried to watch videos about rooting and read articles but I couldn't understand. That's why I am posting this thread. Could someone explain things to me in the most simple way and how can I avoid bootloops or stuff like that if I come across one. I'd appreciate it very much.
I think it is best to start with reading the "HowTo" guides
Elinx said:
I think it is best to start with reading the "HowTo" guides
Click to expand...
Click to collapse
Alright I'll try it, thanks
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Elinx said:
I think it is best to start with reading the "HowTo" guides
Click to expand...
Click to collapse
Hello Sir, sorry to disturb you again. I have installed the adb, fastboot and fastbootd drivers. I need your help with something, should i continue with the latest version of Magisk? I have Redmi note 10 pro (sweet)
Because you are a starter, I advice to follow the guide exactly.
If you flash a lower version of Magisk, you always can update afterwards with Magisk manager
You haven't said what the reason is for root.
If you want to flash custom rom, you need Twrp or OrangeFox too
That is also done with ADB
In case of Magisk you patch the original boot.img
(that is why you need an original stock boot.img. Keep a copy for revert back)
Elinx said:
Because you are a starter, I advice to follow the guide exactly.
If you flash a lower version of Magisk, you always can update afterwards with Magisk manager
You haven't said what the reason is for root.
If you want to flash custom rom, you need Twrp or OrangeFox too
That is also done with ADB
In case of Magisk you patch the original boot.img
(that is why you need an original stock boot.img. Keep a copy for revert back)
Click to expand...
Click to collapse
Im following the guide that you have given the link for. And by update do you mean I can install new updates of the phone (because I know after rooting you can't or won't receive updates) or do you mean magisk by it? Well I want to modify and tweak with my Phone appearance and install some modules. For now Im not going for custom roms. Since I just want to root my phone for now, could you please tell me what do you mean by original stock boot.img? Because I have downloaded and extracted the rom contents that i have in my phone (following the guide). I know I am asking too much, sorry
p.s. what would you like to suggest me to use the latest version of magisk or some old version?
I mean update of Magisk.
The older versions are working with the same modules till v23
From v24 Magisk has another base (zygisk) and you need other modules
So decide which modules you need for which Magisk version, before flashing
Inside the stock rom you find boot.img and recovery.img (these are replaced by magisk.img and twrp.img)
If something goes wrong you can flash these original images back with ADB and you have stock Miui without root again and can start again with clean sheets.
Elinx said:
I mean update of Magisk.
The older versions are working with the same modules till v23
From v24 Magisk has another base (zygisk) and you need other modules
So decide which modules you need for which Magisk version, before flashing
Inside the stock rom you find boot.img and recovery.img (these are replaced by magisk.img and twrp.img)
If something goes wrong you can flash these original images back with ADB and you have stock Miui without root again and can start again with clean sheets.
Click to expand...
Click to collapse
Thank you alot. Its really helpful to me. Also I just checked that I do not have the recovery.img but the boot.img
Bilalbilly87 said:
Thank you alot. Its really helpful to me. Also I just checked that I do not have the recovery.img but the boot.img
Click to expand...
Click to collapse
If you only flash Magisk you only need boot.img
I see now what you mean
Normally inside the stock fastboot rom you find all partition images, but you recognize only the boot.img
Boot.img is one of them, also recovery.img is one of about 13 partitions.
Be sure to double check the version. It must be exactly the same as what you have now on the phone.
Elinx said:
If you only flash Magisk you only need boot.img
I see now what you mean
Normally inside the stock fastboot rom you find all partition images, but you recognize only the boot.img
Boot.img is one of them, also recovery.img is one of about 13 partitions.
Be sure to double check the version. It must be exactly the same as what you have now on the phone.
Click to expand...
Click to collapse
I have installed Twrp and Magisk As well. I was able to install some modules but with some modules I'm having this problem and I don't quite understand why. I downloaded it from GitHub like the zip file and after flashing.
Congrats with flashing Twrp and magisk
I understand you speak about Magisk modules?
As I said before, ckeck carefully for which Magisk version the module can be flashed
v.xx t/m v. 23 or v24 t/m 25.3 (zygisk)
Elinx said:
Congrats with flashing Twrp and magisk
I understand you speak about Magisk modules?
As I said before, ckeck carefully for which Magisk version the module can be flashed
v.xx t/m v. 23 or v24 t/m 25.3 (zygisk)
Click to expand...
Click to collapse
Thank you for helping me. Actually i was having problem with flashing the modules, because the contents are in the zip file in a folder and they need to be outside of any folder meaning all those files need to be in the zip instead of being in a folder in the zip. I'm good to go as i checked and its installing now.
kon kkonsay modules use krra ha hmy bhi bta
MehtabMad said:
kon kkonsay modules use krra ha hmy bhi bta
Click to expand...
Click to collapse
English forum....
Laptapper said:
English forum....
Click to expand...
Click to collapse
Laptapper, one thing is happening to my RN10P
I have Lineage Os
I have flashed your vantom kernel
Using magisk in it
Problem is my phone is heating after kernel install, i checked cpu clock speed
when i changed min* clock speed to 300 it always reset back to max
i.e. 2304Mhz min and @2304Mhz max.
MehtabMad said:
Laptapper, one thing is happening to my RN10P
I have Lineage Os
I have flashed your vantom kernel
Using magisk in it
Problem is my phone is heating after kernel install, i checked cpu clock speed
when i changed min* clock speed to 300 it always reset back to max
i.e. 2304Mhz min and @2304Mhz max.
Click to expand...
Click to collapse
For me not.
Clean install? With format data yes?
Which kernel vantom latest?
If yes, try the lineage os original kernel again.
Sorry for late reply. Everything has been working okay with modules altho i didnt install alot of them but a few. So i guess there weren't enough modules which provided me any customization for Miui 13 because i had the wrong concept. Now i want to take it a step further, i want to flash a custom rom. I have looked and searched. Have decided to go for either Pixel Exp A12 or AncientOS A12 (It has alot of customizations). Now i want to ask you a few questions that i have in mind.
1) Should I flash Custom Rom through Twrp?
2) If so, do i need to flash that Dm verity file (because when I installed twrp in my stock rom which im still using rn, they told us to do that to avoid bootloop and to keep Twrp permanent so do i also need to do it with custom rom?
3) And if its safe to flash through Twrp, Could you please tell me how to (through twrp if its safe)?
4) Which Rom should i go for? Pixel or AncientOs
lineage Os
Laptapper said:
For me not.
Clean install? With format data yes?
Which kernel vantom latest?
If yes, try the lineage os original kernel again.
Click to expand...
Click to collapse
yes the problem was with magisk module, thermal profile disabler. i removed it and everything is stable now