Hello,
I wanted to ask what to do to pass SafetyNet on a rooted Moto-Z?
I have atm stock rom, but custom kernel, TWRP and of course unlocked bootloader.
Root is needed for some apps, so would it be possible to root the device for example with Magisk and flash stock recovery and stock kernel?
Thanks
Dëmön said:
Hello,
I wanted to ask what to do to pass SafetyNet on a rooted Moto-Z?
I have atm stock rom, but custom kernel, TWRP and of course unlocked bootloader.
Root is needed for some apps, so would it be possible to root the device for example with Magisk and flash stock recovery and stock kernel?
Thanks
Click to expand...
Click to collapse
You could try this if you're feeling lucky...
https://forum.xda-developers.com/moto-z/help/how-to-lock-bootloader-t3577782/page2
https://forum.xda-developers.com/2015-moto-g/general/guide-pass-safetynet-custom-roms-t3603609/page6
Dëmön said:
Hello,
I wanted to ask what to do to pass SafetyNet on a rooted Moto-Z?
I have atm stock rom, but custom kernel, TWRP and of course unlocked bootloader.
Root is needed for some apps, so would it be possible to root the device for example with Magisk and flash stock recovery and stock kernel?
Thanks
Click to expand...
Click to collapse
That's what I have:
1. Stock ROM
2. unlocked BL
3. no TWRP (doesn't matter, you can just boot to TWRP from fastboot, no need for flashing)
That's what I did: (working)
1. updated to latest available OTA (optional)
2. flashed TurboZ custom kernel via TWRP, this kernel removes the dm-verify flag (with the flag, this will trigger SafetyNet for an open BL and CTS profile mismatch)
3. reboot to system
3. flashed Magisk v12.0 via TWRP
4. reboot to system
5. Download&Install (or update) "Magisk Manager" and "phh's SuperUser" from Play Store, check if root is working (should so)
6. in Magisk Manager settings check/switch on "Magisk Hide"
7. reboot
8. in Magisk Manager or any other "SafetyNet-Test" app, check if SafetyNet passes
9. profit?
sometimes it seems to be necessary to do a reboot when it doesn't pass the test or it's loading way to long for a check (encountered this 2 times so far)
Thanks for the answers.
It was enough to unroot and flash Magisk.
The phone is rooted with MagiskSU.
A lot of apps are now working but not all, the ones that are not working are telling that the phone is rooted.
Of course I am using MagiskHide.
Is it possible to make all apps working?
Thanks
Dëmön said:
Thanks for the answers.
It was enough to unroot and flash Magisk.
The phone is rooted with MagiskSU.
A lot of apps are now working but not all, the ones that are not working are telling that the phone is rooted.
Of course I am using MagiskHide.
Is it possible to make all apps working?
Thanks
Click to expand...
Click to collapse
SafetyNet is green?
(CTS profile match and basic integrity must be true for this)
Gesendet von meinem XT1650 mit Tapatalk
Yes, SafetyNet is green.
Dëmön said:
Yes, SafetyNet is green.
Click to expand...
Click to collapse
Then it should work with all apps. Which app doesn't work?
Gesendet von meinem XT1650 mit Tapatalk
For example the app from my creditcard "barclaycard" is showing massage that the device is rooted.
Only way I know so far is something like xprivacy, which does require xposed...
Gesendet von meinem XT1650 mit Tapatalk
Related
This guide provides all the steps and patches required to root the Stock system and having Xposed installed while maintaining SafetyNet (Android Pay, Pokemon Go, etc) compatibility. There are some problems of this method that Magisk is supposed to fix, however the latest Magisk v10 is not supporting our stock ROM yet.
The prerequisites of this guide is to have the bootloader unlocked and TWRP recovery.
DOWNLOADS
The recipe require the following ingredients to be downloaded to your internal or external storage:
1. TWRP 3.0.3 (This is the last release at this moment). more info in the Official Thread. Thanks to @jcadduono . TWRP 3.0.2 can't succesfully flash SuperSU 2.79
2. Default Stock ROM for your phone (Required only if you have modified your system or boot partition). You can download them from this thread. Thanks to @DrakenFX . You can alsouse any other custom ROM based on stock such as ZADMix or HelsAx7 SubMix (both tested).
3. SuperSU v2.79. more info in its official thread.
4. SUhide 0.55. More info in its official thread. Thanks to Chainfire.
5. SafetyNet-KCAL Kernel patch, thanks to @jcadduono also for this one!
6. Xposed v86.2 So far only this version is compatible with SUhide.
7. Material Design Xposed Manager app by DVDandroid. More info about this release in its official thread.
8. Root Switch 1.3.3.2 app. Thanks to shakalaca. More info in its official thread.
INSTALLATION
1. Do a backup of your system, I recommend Boot+System+Data partitions. The next steps will modify at least your boot and data partitions, and some Xposed modules will modify also your system partition.
2. If you already have TWRP 3.0.3 then just boot to recovery and proceed to step 3. If you are still using TWRP 3.0.2 please upgrade to the latest TWRP 3.0.3 and reboot to recovery again.
3. I recommend to flash the default Boot and System Partitions and reboot directly to recovery. You can also use any other custom ROM based on the stock ROM such as ZADMix or HelsAx7.
4. All this step must be done without leaving TWRP. Flash SuperSU 2.79 adding also the zips for SUhide 0.55, Xposed v86.2 and the SafetyNet Kernel patch in that order. They must be flashed together. Without leaving TWRP, navigate from the main menu to Advanced > Terminal, introduce the command reboot disemmcwp and the system will reboot by itself once or twice while configuring the settings for SuperSU. Do not be alarmed.
5. Install Xposed Manager and Root Switch apps.
6. Now you have your system fully rooted and you can now install Xposed modules. However you will see the test app SafetyNet Helper reporting a validation failure. Do not worry about it anymore! When you want to initiate a SafetyNet sensitive application (Android Pay or Pokemon Go among others), just open Root Switch and disable root, no need to reboot. SafetyNet will pass and all your apps will work. You can see that Xposed continue working even after disabling root since it was started before. Do not forget to enable root again otherwise new apps requiring root won't load.
Magisk v10+ promises auto root hide per app, but sadly our stock ROM is not yet supported and the method psoposed here requires the user to disable root before loading any SafetyNet protected app.
Enjoy
Reserved for future Magisk guide.
Has anyone managed to get this working on A2017G/B09? I've had a few attempts, forcing systemless SuperSU, but it hangs at the "AXON" boot screen
H0lmEd said:
Has anyone managed to get this working on A2017G/B09? I've had a few attempts, forcing systemless SuperSU, but it hangs at the "AXON" boot screen
Click to expand...
Click to collapse
At what point of the guide is it hanging at the Axon boot screen? after step 4? Have you ensured that the SafetyNet patch is the last thing you flashed before boot?
I just did this on my B29 A2017U phone and it worked perfectly, can switch root on and off with the root switcher and Safetynet passes fully with root set to off.
My previous attempts were all thwarted by the bootloader being unlocked, so that patch to the kernel works great. I'll be backing this up with twrp and getting a little more adventurous (really want to try the BeastMode kernel) soon.
Much thanks for making it nice and simple, Oki !
Oki said:
At what point of the guide is it hanging at the Axon boot screen? after step 4? Have you ensured that the SafetyNet patch is the last thing you flashed before boot?
Click to expand...
Click to collapse
I'm on the same configuration (A2017G B09). I did a step by step installation/reboot/installation/reboot. The Problem is with suhide. After installing suhide the boot process will stick in the Axon screen.
tron1 said:
I'm on the same configuration (A2017G B09). I did a step by step installation/reboot/installation/reboot. The Problem is with suhide. After installing suhide the boot process will stick in the Axon screen.
Click to expand...
Click to collapse
You do not have to reboot after SUhide. The files at step 4 have to be flashed together without leaving TWRP otherwise it won't work.
Oki said:
You do not have to reboot after SUhide. The files at step 4 have to be flashed together without leaving TWRP otherwise it won't work.
Click to expand...
Click to collapse
In theory you're right. But how do like a bugfix to be done if you don't know at which point you're failing?!?
tron1 said:
In theory you're right. But how do like a bugfix to be done if you don't know at which point you're failing?!?
Click to expand...
Click to collapse
The last patch fixes some problems created by SuperSU, SUhide and Xposed. This is why all the patches in step 4 have to be flashed together without leaving TWRP and in the specified order, otherwise it wont work on stock ROMs.
That looks way complicated. What's wrong with the easy way of flashing Magisk V10 + Phh Superuser r266? This has worked on all my devices since the November security patch broke suhide. Magisk now takes care of the flag to hide bootloader unlock status so no need for a kernel patch too. Then flash systemless Xposed by topjohnwu if you want that and you can turn it on and off in Magisk Manager if you want to use Android Pay, play Pokemon Go, etc.
Hi,
I have a A2017G running B08, already unlocked and witch SuperSU 2.79. Just the older version of TWRP.
Can I just upgrade the TWRP and proceed with step 4 and so on? Hate to go back to stock...
Tia,
Cheers,
/Cacti
Tikerz said:
That looks way complicated. What's wrong with the easy way of flashing Magisk V10 + Phh Superuser r266? This has worked on all my devices since the November security patch broke suhide. Magisk now takes care of the flag to hide bootloader unlock status so no need for a kernel patch too. Then flash systemless Xposed by topjohnwu if you want that and you can turn it on and off in Magisk Manager if you want to use Android Pay, play Pokemon Go, etc.
Click to expand...
Click to collapse
For some reason Magisk is not compatible with the Axon 7 kernel. Not yet. This is why it is so complicated and requires a guide. Last time I tested this was yesterday using Magisk v10.2 and phh Superuser r2, and they still failed to root the system.
le_cactus said:
Hi,
I have a A2017G running B08, already unlocked and witch SuperSU 2.79. Just the older version of TWRP.
Can I just upgrade the TWRP and proceed with step 4 and so on? Hate to go back to stock...
Tia,
Cheers,
/Cacti
Click to expand...
Click to collapse
Yes you can try to begin with step 4 with SUhide on. It should work. However I recommend you to upgrade to TWRP 3.0.3 and do the whole step 4.
Gr8. Thanks.
Cheers,
/Cacti
Oki said:
The last patch fixes some problems created by SuperSU, SUhide and Xposed. This is why all the patches in step 4 have to be flashed together without leaving TWRP and in the specified order, otherwise it wont work on stock ROMs.
Click to expand...
Click to collapse
Not quite sure I understand you.
I've tried doing this on A2017g, b09;
0) wipe data/system/boot
1) flash stock Boot stack + System stack zips in twrp 3.0.3 unlocked bl
2) rebooted straight to recovery
3) flashing SuperSU wrote to system so I had to start again but forcing systemless (in terminal; echo "SYSTEMLESS">/data/.SuperSU
4) flash supersu, suhide
5) flash xposed
6) flash the safety net/kcal patch
7) reboot
And I still get stuck on "AXON" boot screen
H0lmEd said:
Not quite sure I understand you.
I've tried doing this on A2017g, b09;
0) wipe data/system/boot
1) flash stock Boot stack + System stack zips in twrp 3.0.3 unlocked bl
2) rebooted straight to recovery
3) flashing SuperSU wrote to system so I had to start again but forcing systemless (in terminal; echo "SYSTEMLESS">/data/.SuperSU
4) flash supersu, suhide
5) flash xposed
6) flash the safety net/kcal patch
7) reboot
And I still get stuck on "AXON" boot screen
Click to expand...
Click to collapse
SuperSU 2.79 installs in systemless mode, no need to set systemless.
Regarding your problem, please try this. Instead of rebooting using the button, open the terminal in TWRP and type "reboot disemmcwp". I hope this was your problem.
This doesn't work for me. Steps:
1. complete wipe
2. install b29 boot stack
2. install b29 system
3. install super su 2.79
4. install su hide 0.55
su hide comes back with an error that says it can't find super su and I should make sure I've installed 2.79 or greater.
edit:
I missed the part in step 3 where you say "reboot directly to recovery". I tried that, but it rebooted to system instead and now I lost TWRP entirely.
edit2:
fastboot flashed twrp again and once in recovery I was able to get through step 4
edit3:
Now it's just stuck on the axon logo. Tried force reboot and the same thing.
Are you sure you tested this from scratch? I have the US version of the axon 7.
Oki said:
SuperSU 2.79 installs in systemless mode, no need to set systemless.
Regarding your problem, please try this. Instead of rebooting using the button, open the terminal in TWRP and type "reboot disemmcwp". I hope this was your problem.
Click to expand...
Click to collapse
I have tried it and am stuck on the same stage also even after using "reboot disemmcwp".
I followed all of your steps and am using an A2017G B08.
corpdecker said:
I just did this on my B29 A2017U phone and it worked perfectly, can switch root on and off with the root switcher and Safetynet passes fully with root set to off.
My previous attempts were all thwarted by the bootloader being unlocked, so that patch to the kernel works great. I'll be backing this up with twrp and getting a little more adventurous (really want to try the BeastMode kernel) soon.
Much thanks for making it nice and simple, Oki !
Click to expand...
Click to collapse
Don't install beast mode yet, from my experience all the steps from op worked fine until I flashed beast mode and it broke safetynet.
lexman098 said:
This doesn't work for me. Steps:
1. complete wipe
2. install b29 boot stack
2. install b29 system
3. install super su 2.79
4. install su hide 0.55
su hide comes back with an error that says it can't find super su and I should make sure I've installed 2.79 or greater.
edit:
I missed the part in step 3 where you say "reboot directly to recovery". I tried that, but it rebooted to system instead and now I lost TWRP entirely.
edit2:
fastboot flashed twrp again and once in recovery I was able to get through step 4
edit3:
Now it's just stuck on the axon logo. Tried force reboot and the same thing.
Are you sure you tested this from scratch? I have the US version of the axon 7.
Click to expand...
Click to collapse
Are you using TWRP 3.0.3? SuperSU 2.79 installs fine and in systemless mode when flashed with the latest TWRP. TWRP 3.0.2 can't flash it properly.
Yes this method has been tested, not only with stock Roms, but also with ZADmix.
If you are doing a complete cleanup before flashing the ROM, boot into system at least once after installing the ROM so the data tree structure is setup. You actually don't need a full cleanup.
Kingo64 said:
I have tried it and am stuck on the same stage also even after using "reboot disemmcwp".
I followed all of your steps and am using an A2017G B08.
Click to expand...
Click to collapse
H0lmEd said:
And I still get stuck on "AXON" boot screen
Click to expand...
Click to collapse
Please ensure you have flashed the right stock ROM for your unit. I have modified Ingredient 2 in the OP since it was highly misleading. Ensure you have unlocked bootloader, TWRP 3.0.3 and flash the right ROM for your system: ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip and ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip. And boot to the system at least once before continue to the rest of the procedure.
I tested it and this works:
Bought N950F DS.
Instaled TWRP as in this guide:
https://forum.xda-developers.com/showpost.php?p=73817280&postcount=3
Part 3 - Magisk.
I did not flash custom rom, i wanted to stay on stock. (no system format)
Flashed Magisk 14.5
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Boot into system, configure in Magisk
install xposed (api 25),
finally you will have after few reboots xposed v89.
(Install some modules, but remember to backup in TWRP before every module installation.
For me, some of them caused TouchWiz to not show on start, had to do few reboots (bixby + power + volume down long press).
For example do not install firefdskit.
GravityBox is working fine for me now.
Also Kmod for whatsapp.)
In this state Android Pay wont work.
To get it working there is currently only one option i know:
Install this:
RootSwitch 1-3-3-16
https://www.asus.com/zentalk/tw/for...5MjEyfDVlYzZhYzljfDE1MTM3NDk3NzN8MHwxNzM1NDI=
After installing DO NOT TOUCH TOP ROOT SECTION.
Only use xposed section:
Switch xposed to off, soft reboot, install Android Pay, add card.
Whenever you need to pay in shop you have to do it (turn xposed off), later you can switch on, soft reboot and use modules.
Waiting for better way....but everyone says that Android Pay will never work with xposed so this is currently only option for me since phone without xposed is unusable.
You can also just install Xposed with magisk, and then you can enable/disable the xposed module whenever you need safetynet
Interceptor777 said:
You can also just install Xposed with magisk, and then you can enable/disable the xposed module whenever you need safetynet
Click to expand...
Click to collapse
in xposed settings?
I did that but SN wont allow for that, fail.
xtam said:
in xposed settings?
I did that but SN wont allow for that, fail.
Click to expand...
Click to collapse
No, you disable the Xposed module in magisk. That basically.uninstalls Xposed on next boot. And you can re-enable it.
Interceptor777 said:
You can also just install Xposed with magisk, and then you can enable/disable the xposed module whenever you need safetynet
Click to expand...
Click to collapse
Interceptor777 said:
No, you disable the Xposed module in magisk. That basically.uninstalls Xposed on next boot. And you can re-enable it.
Click to expand...
Click to collapse
no, in magisk 14.5 i have few modules installed, but there is no xposed, when i was installing xposed magisk told me to download xpsed apk installer, so xposed is separated, not as uncheckable module.
Hi all?
Can someone confirm that we can be on stock rom while using magisk and twrp?
I mean replace stock recvery by twrp, root with magisk and continue to use stock rom instead of flashing custom rom.
I m on iron man rom (custom) wich is very nice. I want to try the lastest samsug rom (lastest firmware BQKG) with twrp, magisk and xposed?
Do you think it s possible without any issue like popup error windows or other problems?
Thank for your help
What cpu?
Does this work for snapdragon orrr...?
@RyleyDyck
RyleyDyck said:
Does this work for snapdragon orrr...?
Click to expand...
Click to collapse
Depends.
Definitely check the Snapdragon root section and check your Bootloader version, how to is described in the SamFail thread.
@jkr192
jkr192 said:
Hi all?
Can someone confirm that we can be on stock rom while using magisk and twrp?
I mean replace stock recvery by twrp, root with magisk and continue to use stock rom instead of flashing custom rom.
I m on iron man rom (custom) wich is very nice. I want to try the lastest samsug rom (lastest firmware BQKG) with twrp, magisk and xposed?
Do you think it s possible without any issue like popup error windows or other problems?
Thank for your help
Click to expand...
Click to collapse
You could, yes. There's no rule to must have a custom rom in order to use Magisk/ have root. Just be sure to check the "How-To root" thread for simple instructions.
@xtam
xtam said:
no, in magisk 14.5 i have few modules installed, but there is no xposed, when i was installing xposed magisk told me to download xpsed apk installer, so xposed is separated, not as uncheckable module.
Click to expand...
Click to collapse
Not sure how that is, but you installed Magisk first and then Xposed with Magisk.
It's by that definition a Module of Magisk, which you can just disable inside Magisk regardless what Xposed's actual status is (ON or OFF).
No need to worry, just toggle it OFF inside Magisk. Your Xposed apps may FC, but that's the tradeoff for being able to use SafetyNet at will.
I just noticed that my kenzo bypasses safetynet on lineage os 15.1 20180323 build by lokmansiu. I can install Netflix from playstore, run super Mario run and pokemon go without any problems, also tested on safetynet test app. But I cant understand how is this possible provided I didnt even install magisk.
though I have not rooted the rom,
my bootloader is locked(used edl mode to flash twrp and then the rom)
can anyone plz tell if this is even normal??
@[email protected] said:
I just noticed that my kenzo bypasses safetynet on lineage os 15.1 20180323 build by lokmansiu. I can install Netflix from playstore, run super Mario run and pokemon go without any problems, also tested on safetynet test app. But I cant understand how is this possible provided I didnt even install magisk.
though I have not rooted the rom,
my bootloader is locked(used edl mode to flash twrp and then the rom)
can anyone plz tell if this is even normal??
Click to expand...
Click to collapse
No root = no problem.
You only fail SafetyNet if you use SuperSU to root your phone or forget to use Magisk Hide when rooting using Magisk.
SafetyNet also fails if you use Xposed Framework
Noter2017 said:
No root = no problem.
You only fail SafetyNet if you use SuperSU to root your phone or forget to use Magisk Hide when rooting using Magisk.
SafetyNet also fails if you use Xposed Framework
Click to expand...
Click to collapse
But i always use custom ROMs without root and still the safetynet test still always failed
The only difference between this and previous scenario is that my bootloader is locked and the selinux in this ROM is hopefully enforcing...are they the reason?
how did you install twrp in edl mode with bootloader locked?
arnabbandopadhyay said:
how did you install twrp in edl mode with bootloader locked?
Click to expand...
Click to collapse
Follow the instruction from this video:
https://www.youtube.com/watch?v=xExKvog5RP4
Tip: You can install twrp version of your choice. Just download twrp of your choice and rename it to recovery.img and place it in TWRP_ZCX/images folder (delete existing recovery.img file inside the image folder).
This method doesnot unlock the bootloader.
Nabin Pokhrel said:
Follow the instruction from this video:
Tip: You can install twrp version of your choice. Just download twrp of your choice and rename it to recovery.img and place it in TWRP_ZCX/images folder (delete existing recovery.img file inside the image folder).
This method doesnot unlock the bootloader.
Click to expand...
Click to collapse
I don't know why but it didn't work for me. Still uncertified.
I recommend you flash Magisk to enable root access. Then use it with its "hide detection" feature (it is the default setting). It will mask your root access and unlocked bootloader from SafetyNet detection. Have a try.
@[email protected] said:
I just noticed that my kenzo bypasses safetynet on lineage os 15.1 20180323 build by lokmansiu. I can install Netflix from playstore, run super Mario run and pokemon go without any problems, also tested on safetynet test app. But I cant understand how is this possible provided I didnt even install magisk.
though I have not rooted the rom,
my bootloader is locked(used edl mode to flash twrp and then the rom)
can anyone plz tell if this is even normal??
Click to expand...
Click to collapse
Because selinux is finally set as enforcing. Probably next updates of other roms will be enforcing too
arnabbandopadhyay said:
I don't know why but it didn't work for me. Still uncertified.
Click to expand...
Click to collapse
Because new build comes with selinux = enforcing
That means you are good to go
If that is permissive then you'll get error in bypassing safety net without magisk.
May I ask if use this method and later on want to revert back to a completely stock Miui ROM how do I do that on my kenzo device. Do I just use the mi flash tool and flash the original stock ROM back?
In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Tysovwik said:
In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Click to expand...
Click to collapse
yes
Usually you don't even have to flash TWRP recovery if you want to keep original recovery, you can just boot it with "fastboot boot twrp.img".
Just a FYI, the latest magisk 17 has not been working for me. Magisk 16 works just fine.
I am on the xiaomi.eu rom
I'm on latest xiaomi.eu and Magisk 17.1 is working fine
bartekm01 said:
I'm on latest xiaomi.eu and Magisk 17.1 is working fine
Click to expand...
Click to collapse
After I flash magisk 17.1 , my mipad 4 can't use LTE
簡_OvO said:
After I flash magisk 17.1 , my mipad 4 can't use LTE
Click to expand...
Click to collapse
That's strange... I've using magisk on 6 device's and never had this sort of problems. Uninstall magisk and check if it's working again
@簡_OvO
On what Rom you have this problem with Magisk ?
I use Mi Pad 4 LTE and Magisk 17.1 on AOSP 8.1_v25 and everything works as it should.
Magisk it has nothing to do with Modem/Baseband he patching Kernel.
After using Magisk uninstaller or restore stock Kernel works for you LTE ?
bartekm01 said:
That's strange... I've using magisk on 6 device's and never had this sort of problems. Uninstall magisk and check if it's working again
Click to expand...
Click to collapse
After I flash again, it can work well
---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------
Andro_Nicus said:
@簡_OvO
On what Rom you have this problem with Magisk ?
I use Mi Pad 4 LTE and Magisk 17.1 on AOSP 8.1_v25 and everything works as it should.
Magisk it has nothing to do with Modem/Baseband he patching Kernel.
After using Magisk uninstaller or restore stock Kernel works for you LTE ?
Click to expand...
Click to collapse
I use MIUI10.I cannot understand why.But after I flash magisk again,LTE works well.
Could you please explain where I find the mipad 4 boot image when using this method to patch it?
When choosing the option in magisk manager to patch boot image I have to search for the original boot image to patch as the app doesn't point staight to it...
Many thanks
@Tysovwik, I see you want keep miui. You have to block overwriting recovery by original one. I have seen option for it in twrp, but i have not tested it. The same you can have if you use special zip package.
Twrp has second option for auto install magisk 17.1, but i installed it from zip file (twrp labeled 20.12.2018 can have 18.0)
is this the best way to Root a Mi Pad 4 LTE ?
A long time ago someone said:
Tysovwik said:
In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Click to expand...
Click to collapse
My plan is to follow this process.
Does anyone know if I still have to do step (1) ? or how that is done ?
Some noobie questions.
I already have TWRP installed in my Mi pad 4, and want to keep my original MIUI rom
To install Magisk what should I do next?
Just flash magisk from twrp?
Do I need to flash no-verify-opt-encrypt.zip?
Select any option of wipe in twrp before flashing Magisk?
If I get a bootloop can I just use Magisk unistaller?
soulgazer said:
Some noobie questions.
I already have TWRP installed in my Mi pad 4, and want to keep my original MIUI rom
To install Magisk what should I do next?
Just flash magisk from twrp?
Do I need to flash no-verify-opt-encrypt.zip?
Select any option of wipe in twrp before flashing Magisk?
If I get a bootloop can I just use Magisk unistaller?
Click to expand...
Click to collapse
I would wipe cache /dalvik cache before and wipe cache again after flashing. But yeah, just flash the magisk zip. You check in the settings under security if your device is encrypted, which I'm guessing it probably is already. In which case there's no need to flash no verify encrypt zip. Unless you want to have no encryption. In which case you'll have to start all over, complete format in twrp then flash magisk and no encrypt zip before first boot.
If you want to stay encrypted (assuming you are already), just flash magisk. I haven't done it in a while! So not sure if magisk manager will be installed with zip flash, if it's not there when you boot to system, just download and install latest magisk manager. You can always then download a root checker app from playstore to be sure all went well.
Good luck dude
I have a pocophone f1 which I attempted to root.
I already unlocked it using my MI account with MI unlocker on windows.
I installed TWRP 3.2, as well as SupersU.zip in TWRP.
I go and check root access using various root checker apps from playstore but i have no root access. One of them says that my supersu $Path does not contain a binary.
I tried uninstalling superSu using the supersSu uninstaller.zip in TWRP and then attempted flashing magisk, but i got the error about patched boot image. I wiped everything and then flashed stock global ROM for miui 11. Still i get the patched boot image when trying to flash magisk.
Any ideas?
Follow this
Silvershot said:
I have a pocophone f1 which I attempted to root.
I already unlocked it using my MI account with MI unlocker on windows.
I installed TWRP 3.2, as well as SupersU.zip in TWRP.
I go and check root access using various root checker apps from playstore but i have no root access. One of them says that my supersu $Path does not contain a binary.
I tried uninstalling superSu using the supersSu uninstaller.zip in TWRP and then attempted flashing magisk, but i got the error about patched boot image. I wiped everything and then flashed stock global ROM for miui 11. Still i get the patched boot image when trying to flash magisk.
Any ideas?
Click to expand...
Click to collapse
Just uninstall SuperSU root and root again with magisk! There is unroot option in the SuperSU app which you have to use or:
https://forum.xda-developers.com/showpost.php?p=63615067
@Silvershot
My POV: Noone needs to install TWRP to root phone's Android.
jwoegerbauer said:
@Silvershot
My POV: Noone needs to install TWRP to root phone's Android.
Click to expand...
Click to collapse
i just followed a tutorial on xda. what simple method do you know to root a poco f1? i need root urgent
abhi_tech said:
Just uninstall SuperSU root and root again with magisk! There is unroot option in the SuperSU app which you have to use or:
https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
thanks for your reply. I already mentioned i used the supersu uninstaller.zip from the link you provided. but magisk still says the boot image is patched...
Silvershot said:
i just followed a tutorial on xda. what simple method do you know to root a poco f1? i need root urgent
Click to expand...
Click to collapse
It's clear that something has gone very wrong. Instead of wasting time with troubleshooting, I recommend that you restore the phone to its original state via re-flashing its Stock ROM and when that's done retry to root its Android the proper way.
FYI: Once TWRP got installed on phone, you can't get rid off of it unless you re-flash phone's Stock ROM.
jwoegerbauer said:
It's clear that something has gone very wrong. Instead of wasting time with troubleshooting, I recommend that you restore the phone to its original state via re-flashing its Stock ROM and when that's done retry to root its Android the proper way.
FYI: Once TWRP got installed on phone, you can't get rid off of it unless you re-flash phone's Stock ROM.
Click to expand...
Click to collapse
i flashed stock rom. i already said it.... still the problem exists
Silvershot said:
i flashed stock rom. i already said it.... still the problem exists
Click to expand...
Click to collapse
If you flash phone's Stock ROM then neither Magisk nor TWRP is existing , you can't run either of them ...
jwoegerbauer said:
If you flash phone's Stock ROM then neither Magisk nor TWRP is existing , you can't run either of them ...
Click to expand...
Click to collapse
yea, i flashed stock rom, then installed TWRP.
i will now flash stock rom again. i wiped everything using TWRP first.
could you tell me what to do once i flash stock rom again?
i attached a screenshot of trying to flash Force Encryption Disabler V4 for Magisk 18. even the disabler doesnt work... please someone help! i am working with stock clean rom. what is going on
0
Silvershot said:
could you tell me what to do once i flash stock rom again?
Click to expand...
Click to collapse
I could but I don't want to: IMO you simply didn't get it - you do anything without questioning the meaning.
Happy fiddling around with Magisk etc.pp.
jwoegerbauer said:
I could but I don't want to: IMO you simply didn't get it - you do anything without questioning the meaning.
Happy fiddling around with Magisk etc.pp.
Click to expand...
Click to collapse
why are you on this forum if you dont want to help? i explicitly said i tried both supersu and magisk. or how can i root without these 2? why do you say i didnt get it? im pretty sure i did the steps correctly
Silvershot said:
why are you on this forum if you dont want to help?
Click to expand...
Click to collapse
ROFL
BTW: Being active in this forum does not force me to give help in every case. Accept it.
Seppppx said:
You don't have to disable encryption to use magisk. Atleast I think from my experience.
This is the step-by-step tutorial.
1. Flash this global stock miui with TWRP. https://c.mi.com/in/miuidownload/detail?device=1700355 (if this is not the official ROM please correct me, there are a lot of fakes there)
2. Flash Magisk with TWRP. Download and flash it from this github repo. DO NOT DOWNLOAD IT FROM ANYWHERE ELSE!
https://github.com/topjohnwu/Magisk/releases
3. Reboot
Click to expand...
Click to collapse
thank you. this worked. i was using older version of magisk. the latest one did the trick.