how do I change system font after rooted with magisk? - ZTE Axon 7 Questions & Answers

My axon 7 a2017u is rooted with magisk. I tried to change to a new font with ifont, it looks working, I but after reboot, I don't see the font changed. how do I change system font after rooted with magisk? Thanks

xdataibai said:
My axon 7 a2017u is rooted with magisk. I tried to change to a new font with ifont, it looks working, I but after reboot, I don't see the font changed. how do I change system font after rooted with magisk? Thanks
Click to expand...
Click to collapse
you probably have write protection on or something like that. Hook the phone up to a PC, make the adb connection, then "adb reboot disemmcwp". You can't do that via terminal or the TWRP command line.
Try that and tell me. It may not work.

Try TypeFace from playstore

Choose an username... said:
you probably have write protection on or something like that. Hook the phone up to a PC, make the adb connection, then "adb reboot disemmcwp". You can't do that via terminal or the TWRP command line.
Try that and tell me. It may not work.
Click to expand...
Click to collapse
What is disemmcwp for? disable emmc write protection? How do I know if I have write protection? I enabled modify system in twrp when first time install twrp.

WesTD said:
Try TypeFace from playstore
Click to expand...
Click to collapse
How is typeface different from ifont? Is there any app that can show what is the current font before change it?

xdataibai said:
What is disemmcwp for? disable emmc write protection? How do I know if I have write protection? I enabled modify system in twrp when first time install twrp.
Click to expand...
Click to collapse
Just follow the damn instructions :laugh:
emmcwp has nothing to do with system modification on twrp

Choose an username... said:
Just follow the damn instructions :laugh:
emmcwp has nothing to do with system modification on twrp
Click to expand...
Click to collapse
It doesn't work. I think it is some kind of write protection. Magisk cannot retain the root request after reboot, it prompts the root request pop-up again when app runs. I tried supersu, during flash, I see something like systemless mode detected..., but flash successful, but when supersu runs, it says no root detected

Related

unlock system file after root?

I have the phone rooted and bootloader unlocked. i still cannot modify the /system files. it's gives an error when changing permissions in a root explorer.
rmyc said:
I have the phone rooted and bootloader unlocked. i still cannot modify the /system files. it's gives an error when changing permissions in a root explorer.
Click to expand...
Click to collapse
This goes on Questions and Answers
You can fix it easily with a command. I assume that you have ADB on your computer, if not download the 15 seconds ADB installer
Connect your phone to your computer, enable USB debugging. Open CMD with admin privileges (just in case). Issue 'adb devices', if the phone appears, you're good to go. Otherwise check that the phone is unlocked, do it again, and allow the connection if a dialog appears.
Issue 'adb reboot disemmcwp' and you should be done
thanks alot, i really appreciate it. now i just need to figure out the delayed whatsapp msgs and this phone will be perfect
rmyc said:
thanks alot, i really appreciate it. now i just need to figure out the delayed whatsapp msgs and this phone will be perfect
Click to expand...
Click to collapse
Oh I hate that. The only fix I found was to reinstall the system (full wipe, then reinstall). If you find a way to fix it without doing thay, please tell!
Full system? Do you know which version.? I'm on marshmallow B29
rmyc said:
Full system? Do you know which version.? I'm on marshmallow B29
Click to expand...
Click to collapse
You obviously have to wipe everything. Use DrakenFX's files if you have an A2017U (over at the custom stuff thread). The version numbers are so different that I have no idea what Nougat for the U is...
Choose an username... said:
You obviously have to wipe everything. Use DrakenFX's files if you have an A2017U (over at the custom stuff thread). The version numbers are so different that I have no idea what Nougat for the U is...
Click to expand...
Click to collapse
are you on nougat? because nougat is fine but i'm required to run marshmello
rmyc said:
are you on nougat? because nougat is fine but i'm required to run marshmello
Click to expand...
Click to collapse
Okay use DrakenFX's M zips instead, it's the same

This is how I got root (Magisk) on my Pixel 2.

***Bootloader must be unlocked as a prerequisite.
11/4/2017 - Scroll down to find new method that doesn't require TWRP.
You will need to download the alpha version of twrp, snoke kernel r7-p2-root and magisk 14.3 (1437)
1. Reboot phone to bootloader.
2. fastboot flash boot Snoke-R7-P2-Root.img
3 fastboot boot twrp-3.1.1-alpha1-walleye.img
4. Once in twrp, start adb sideload.
5. From cmd, adb sideload Magisk-v14.3(1437).zip
6. Reboot and enjoy root!!!!!
All credit comes from this post.
11/4/2017 - Post updated.
Just wanted to add this as another option for those who may find this method easier. No TWRP needed.
multi_rom_user said:
I just found a much faster and easier way to install magisk on the wonderful Pixel 2...
1. Download Magisk Manager 5.4.0 apk
2. Open app and tap install
3. Use the patch boot img option.
4. Locate the patched_boot.img within internal sd/MagiskManager and move it to root of phone memory.
5. Send that file to your pc.
6. Boot to bootloader.
7. Input command into cmd "fastboot flash boot patched_boot.img"
8. Reboot and you have latest root package or whichever you downloaded.
Click to expand...
Click to collapse
giant22000 said:
You will need to download the alpha version of twrp, snoke kernel r7-p2-root and magisk 14.3 (1437)
1. Reboot phone to bootloader.
2. fastboot flash boot Snoke-R7-P2-Root.img
3 fastboot boot twrp-3.1.1-alpha1-walleye.img
4. Once in twrp, start adb sideload.
5. From cmd, adb sideload Magisk-v14.3(1437).zip
6. Reboot and enjoy root!!!!!
All credit comes from this post.
Click to expand...
Click to collapse
I gave this a shot on the XL. Couldn't get it to sideload. Maybe I'm doing the sequence wrong. Doing something wrong. Doesn't see the file. Thanks for the guide
mac796 said:
I gave this a shot on the XL. Couldn't get it to sideload. Maybe I'm doing the sequence wrong. Doing something wrong. Doesn't see the file. Thanks for the guide
Click to expand...
Click to collapse
Are you enabling sideload once booted into twrp?
giant22000 said:
Are you enabling sideload once booted into twrp?
Click to expand...
Click to collapse
Been a long time since I sideload. But I flashed the root kernel, then booted TWRP, then advanced, side load then swiped, gave me an error about no encryption but started then I opened command window in folder I had magisk beta file, entered command. I got error, no such file I believe
So the command your entering is:
"adb sideload C:\your\computers\filepath\Magisk-v14.3(1437).zip" ?
mac796 said:
Been a long time since I sideload. But I flashed the root kernel, then booted TWRP, then advanced, side load then swiped, gave me an error about no encryption but started then I opened command window in folder I had magisk beta file, entered command. I got error, no such file I believe
Click to expand...
Click to collapse
Doesn't work on XL. Currently don't know exactly why.
giant22000 said:
So the command your entering is:
"adb sideload C:\your\computers\filepath\Magisk-v14.3(1437).zip" ?
Click to expand...
Click to collapse
Yep that's what I did.
Chronzy said:
Doesn't work on XL. Currently don't know exactly why.
Click to expand...
Click to collapse
Ok I thought I was doing it right thanks.
I see. I was just about to mention.
Worked perfectly for me thanks brother!
Thanks! Is it working for the Pixel 2 XL too? Did anyone try?
DJBhardwaj said:
Thanks! Is it working for the Pixel 2 XL too? Did anyone try?
Click to expand...
Click to collapse
See 3 and 4 posts above yours
Sent from my Pixel 2 using Tapatalk
giant22000 said:
You will need to download the alpha version of twrp, snoke kernel r7-p2-root and magisk 14.3 (1437)
1. Reboot phone to bootloader.
2. fastboot flash boot Snoke-R7-P2-Root.img
3 fastboot boot twrp-3.1.1-alpha1-walleye.img
4. Once in twrp, start adb sideload.
5. From cmd, adb sideload Magisk-v14.3(1437).zip
6. Reboot and enjoy root!!!!!
All credit comes from this post.
Click to expand...
Click to collapse
thanks for providing/testing this.
does root stick even after subsequent reboots? are root apps (like adaway, TiBu, Root Explorer, etc.) working as they should? any screenies would be helpful.
jco23 said:
thanks for providing/testing this.
does root stick even after subsequent reboots? are root apps (like adaway, TiBu, Root Explorer, etc.) working as they should? any screenies would be helpful.
Click to expand...
Click to collapse
This process seems to work perfectly. Adaway works as expected, and root persists after a reboot. Big thanks to those who worked on it!
I keep trying and it keeps failing.
C:\Users\gohan\AppData\Local\Android\sdk\platform-tools>adb sideload Magisk-v14.3(1437).zip
opening 'Magisk-v14.3(1437).zip'...
connecting...
falling back to older sideload method...
error: closed
Edit: For those of you like myself who have never sideloaded anything before, you need to actually enable the feature first in TWRP before you can use it. >_<
mac796 said:
I gave this a shot on the XL. Couldn't get it to sideload. Maybe I'm doing the sequence wrong. Doing something wrong. Doesn't see the file. Thanks for the guide
Click to expand...
Click to collapse
GohanBurner said:
I keep trying and it keeps failing.
C:\Users\gohan\AppData\Local\Android\sdk\platform-tools>adb sideload Magisk-v14.3(1437).zip
opening 'Magisk-v14.3(1437).zip'...
connecting...
falling back to older sideload method...
error: closed
Edit: For those of you like myself who have never sideloaded anything before, you need to actually enable the feature first in TWRP before you can use it. >_<
Click to expand...
Click to collapse
Do you have the lastest adb/fastboot running or is it an older version?
giant22000 said:
Do you have the lastest adb/fastboot running or is it an older version?
Click to expand...
Click to collapse
Yes. I have latest. Some one already said it doesn't work on xl
For XL i did the following
fastboot flashing unlock-critical for bootloader
then followed the instructions but used the Taiwen TWRP version
going to reboot it now and test but it looks better than before!
Thank you
Thank you for the efforts and information sharing here. Using the Snoke kernel and the root process outlined here I was able to enable native tethering on the Pixel 2.
This is hugely appreciated!
giant22000 said:
You will need to download the alpha version of twrp, snoke kernel r7-p2-root and magisk 14.3 (1437)
1. Reboot phone to bootloader.
2. fastboot flash boot Snoke-R7-P2-Root.img
3 fastboot boot twrp-3.1.1-alpha1-walleye.img
4. Once in twrp, start adb sideload.
5. From cmd, adb sideload Magisk-v14.3(1437).zip
6. Reboot and enjoy root!!!!!
All credit comes from this post.
Click to expand...
Click to collapse
Works great! Thanks to the original discovery and for the succinct instructions.
Can someone whose Pixel 2 is rooted add "ro.debuggable=1" to their build.prop? That should enable the Pixel Visual Core Developer Option (Camera HAL HDR+ in Settings --> system --> developer options)

6T Cant get past loading screen

I'm on a rooted OP 6T, I installed TWRP and Magisk when I first got it on release day. I was using systemize to system install my GCam apk, rebooted and now I cant go any further than the dots loading screen. I tried a date wipe, still cant get any further. I want to try uninstalling magisk or the individually modules but I can't figure out how I do that. When I try to access my files through recovery they seem to be encrypted so I don't know how to get the uninstall zip flashed. Can someone please help
update
I got the magisk uninstaller sideloaded but it says magisk is not installed, is there a way I can just go back to stock and clear everything? I havent installed a custom rom just unlocked and rooted
If you're able to go to download mode then ADB sideloading should help you.
There's bunch of tutorials on how to do that on the forum.
geminium said:
If you're able to go to download mode then ADB sideloading should help you.
There's bunch of tutorials on how to do that on the forum.
Click to expand...
Click to collapse
not sure what downloading mode is, but I did get into ADB sideload mode. I tried sideloading the magisk uninstallers so I could get rid of whatever module caused the issue, but I got the reply that magisk isn't installed. So now Im not sure what to do from here besides trying to go fully back to stock, which Id rather not
Grab a stock boot.img in the fastboot stock ROM thread in general section and flash it with fastboot to replace the magisk modified one
Striatum_bdr said:
Grab a stock boot.img in the fastboot stock ROM thread in general section and flash it with fastboot to replace the magisk modified one
Click to expand...
Click to collapse
The system is modified. Maybe gonna have to sideload the whole firmware package ~1gb. I'm pretty sure this is the reason everything in magisk is systemless. Maybe contact the developer about the mod and see if they know a way to get it to work for your situation?
stryver said:
The system is modified. Maybe gonna have to sideload the whole firmware package ~1gb. I'm pretty sure this is the reason everything in magisk is systemless. Maybe contact the developer about the mod and see if they know a way to get it to work for your situation?
Click to expand...
Click to collapse
It is not the system partition that is modified (that's the point for a systemless app...) It's boot and data (magisk puts here the img it needs to mount virtually and execute all the magisk modules you installed). You got nothin to lose to flash boot.img first and if it doesn't work you restore system and data
Striatum_bdr said:
It is not the system partition that is modified (that's the point for a systemless app...) It's boot and data (magisk puts here the img it needs to mount virtually and execute all the magisk modules you installed). You got nothin to lose to flash boot.img first and if it doesn't work you restore system and data
Click to expand...
Click to collapse
OP stated that they used a systemizer app to install gcam to the system, doesn't that mean there is now a modification in the system? Which would explain why the data format is not working.
stryver said:
OP stated that they used a systemizer app to install gcam to the system, doesn't that mean there is now a modification in the system? Which would explain why the data format is not working.
Click to expand...
Click to collapse
No it's all virtual, the physical partition system is not modified.
Again, what do you have to lose by flashing boot.img...
Striatum_bdr said:
No it's all virtual, the physocal partition system is not modified
Click to expand...
Click to collapse
That's true for magisk, but installing any apps to system via 3rd party root app will cause the apps to survive factory resets, right? So if say, new system app was causing any conflicts, those conflicts will also survive.
stryver said:
That's true for magisk, but installing any apps to system via 3rd party root app will cause the apps to survive factory resets, right?
Click to expand...
Click to collapse
Again what do you have to lose by flashing boot img? Your phone doesn't boot... At worse it won't boot and you'll have to come back to factory by fastboot the would system
Striatum_bdr said:
Again, what do you have to lose by flashing boot.img...
Click to expand...
Click to collapse
Sorry I'm not trying to be argumentative, I'm merely speaking what makes sense to me
Endless speculation can be ended by experimentation...
Striatum_bdr said:
Endless speculation can be ended by experimentation...
Click to expand...
Click to collapse
Agreed, now where is OP to confirm our speculation??
And by the way App Systemizer is systemless so it doesn't touch system partition, first sentence of the module description
Striatum_bdr said:
And by the way App Systemizer is systemless so it doesn't touch system partition, first sentence of the module description
Click to expand...
Click to collapse
I was just going to check this, never used it myself. Probably should have checked before speaking. Lesson learned lol oh well
Again, sorry if I came off argumentative.
Next thing that comes to mind for OP is that there is a difference between 'wiping data' and 'formatting data'. If you just wiped, try to format data. I had a bootloop from uninstalling a magisk module and quickly recovered by formatting.
stryver said:
Agreed, now where is OP to confirm our speculation??
Click to expand...
Click to collapse
I ended up just downloading the OnePlus tool and stock fajita rom and taking it back to stock. Still not sure exactly what caused the problem, I did everything over again with no issues the second time around

Anyone tried Magisk HD8 7th Gen?

Hi, just got around to rooting my Kindle. Currently using SuperSu, curious if anyone has used Magisk with this tablet? Any reason not to do so?.
Thanks in advance.
I've debated doing this as well, as I don't like having to default grant everything root access.
As far as I understand though, none of your root apps/su requests can modify the system partition, so I haven't tried it yet.
@diplomatic is this true for the bootless root method without dm-verity?
No, you can modify /system if there's no dm-verity, @Kctucka
diplomatic said:
No, you can modify /system if there's no dm-verity, @Kctucka
Click to expand...
Click to collapse
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Kctucka said:
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Click to expand...
Click to collapse
Thanks, guys!
SuperSU access workaround
Kctucka said:
I've debated doing this as well, as I don't like having to default grant everything root access.
.....
Click to expand...
Click to collapse
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Dan_firehd said:
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Click to expand...
Click to collapse
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Kctucka said:
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Click to expand...
Click to collapse
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Yeah will do! I'll probably try it tomorrow or the day after.
koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
So far, all of my root apps detect root, except for titanium backup. I've messed around with it for a bit but haven't been able to figure it out. I'm guessing it has something to do with the location of the su binaries.
Also of note, FlashFire did not work at first. I realized that this is because the timebomb method we used along with the older app version, was from before Magisk existed. I grabbed the latest version of FlashFire from apk mirror, and it started without issues. I haven't tested by flashing anything yet though.
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
All in all, this is a pretty solid root method, but obviously non ideal due to the locked bootloader.
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Kctucka said:
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
Click to expand...
Click to collapse
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into this after so long I feel like a n00b again.
koop1955 said:
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into thhis after so long I feel like a n00b again.
Click to expand...
Click to collapse
That option was all I did to remove SuperSu. Then I followed the instructions here:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
Didn't take long to get it working.
And the time change was to get the version of FlashFire working that was compatible with the version of SuperSu we could run. See this post for more info if you're curious:
https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-xposed-t3722252
But with this new method, the most recent version of FlashFire works, as it's compatible with Magisk. The older version of FlashFire I had is not.
Also, I'm a noob myself. That's why I tagged diplomatic again, to correct the dumb things I might have said
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
koop1955 said:
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
Click to expand...
Click to collapse
That's awesome! Would that pass signature verification? Or would it be through hacked fastboot?
Also, that'd make it much easier to set up the device after a softbrick. FlashFire would be good to flash backups right away.
Kctucka said:
.....
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
.....
Click to expand...
Click to collapse
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Dan_firehd said:
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Click to expand...
Click to collapse
My kernel tweaks were done with KA Mod Reborn, using the "apply on boot" setting:
https://forum.xda-developers.com/android/apps-games/approot4-0-ka-mod-reborn-v18-t3714105
I added 260 MB ZRAM with a swapiness of 10. You can also tweak low memory killer, laptop mode, and a whole bunch of other dials that I don't mess with as I don't fully understand what they do.
Kernel changes could also be done with a number of different apps that do similar things.
Unfortunately, the bootless root method doesn't give root on boot, so it and also most Magisk modules won't work. Can't think of a workaround currently.
Kctucka said:
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Click to expand...
Click to collapse
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
That's super beneficial then, you can swap back and forth easily depending on what you need.
diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
How about just swapping the install-recovery.sh script for suboot.sh on devices that don't have dm-verity?
I think that's pretty much what SuperSU does as well.
That would give root much earlier during boot and not depend on the extra App.
Probably doesn't even need to run mtk-su each boot then either.
Yeah, that's on the right track, @k4y0z. What you can probably use is a modified SU_MINISCRIPT section of suboot.sh, at least as a starting point. That is the code that needs to be run as root. What should be changed is the path to the magiskinit & magisk binaries. Those could be placed somewhere on /system. You would only need mtk-su if selinux needs to be permissive. But I suspect it does for the 'magiskpolicy --live' call. (But then how does SuperSU handle it with enforcing?)

can I root my mi 9t temperorly

Is there a way to get temp root for some time then disable it
Why don't you flash Magisk and then uninstall it?
Depends on what you want to achieve with getting temporary root. If you want to make a backup of your untouched phone, you could try to boot into the latest twrp (test) version or and get temporary root trough an adb shell.
for what purpose?
flamedrops said:
for what purpose?
Click to expand...
Click to collapse
Like to access net cut to remove hackers for some Intruders on my network
Medeon said:
Depends on what you want to achieve with getting temporary root. If you want to make a backup of your untouched phone, you could try to boot into the latest twrp (test) version or and get temporary root trough an adb shell.
Click to expand...
Click to collapse
No I mean on Android not twrp if correctly understood.
And that adb shell how to do this ?? Please answer me
batman957 said:
No I mean on Android not twrp if correctly understood.
And that adb shell how to do this ?? Please answer me
Click to expand...
Click to collapse
First I would like to say, do your research before you post a question here. The answers to your questions are literally one Google or XDA search away from you. Having said that, your best bet would probably be Kingoroot although I can't promise you it will work. I have tried it once on an older phone, but I did not succeed. But you could try.
If it's not working, the only way to gain root access is to unlock the bootloader of your phone. This will void your warranty. It's up to you to decide whether it's worth it or not. It will probably take a week or longer for Xiaomi to grant you to unlock the bootloader.
Here is a noob friendly guide on how to install and use adb and fastboot
Ones installed go and download this version of twrp recovery and put it inside your adb (or platform tools) folder. Download the latest version of Magisk, Magisk manager and Magisk uninstaller from here and put it inside of your phone's internal storage.
Inside your settings tap the MIUI version 7 times to "become a developer". Then go to developer options and switch adb debugging on.
Follow the adb and fastboot guide, but don't flash this recovery to your phone. Instead in your cmd or terminal type:
Code:
adb devices
Code:
adb reboot bootloader
This will boot your phone in fastboot mode, then type:
Code:
fastboot boot <your_downloaded_twrp.img>
Replace <your_downloaded_twrp.img> with the actual name of the image. This will boot you into twrp recovery without flashing it to your phone. Probably you will be welcomed with a menu with a slider that says "swipe to allow modifications" don't swipe, just choose "keep system read only". In the menu choose Install (install a zip) and flash the latest Magisk from your internal storage.
Reboot to system and you have root access. If Magisk manager is not installed yet, install the .apk file you downloaded. If you want to unroot the phone boot into twrp ones again and flash the Magisk uninstaller.
batman957 said:
Like to access net cut to remove hackers for some Intruders on my network
Click to expand...
Click to collapse
I used netcut also and i used magisk root.
Medeon said:
First I would like to say, do your research before you post a question here. The answers to your questions are literally one Google or XDA search away from you. Having said that, your best bet would probably be Kingoroot although I can't promise you it will work. I have tried it once on an older phone, but I did not succeed. But you could try.
If it's not working, the only way to gain root access is to unlock the bootloader of your phone. This will void your warranty. It's up to you to decide whether it's worth it or not. It will probably take a week or longer for Xiaomi to grant you to unlock the bootloader.
Here is a noob friendly guide on how to install and use adb and fastboot
Ones installed go and download this version of twrp recovery and put it inside your adb (or platform tools) folder. Download the latest version of Magisk, Magisk manager and Magisk uninstaller from here and put it inside of your phone's internal storage.
Inside your settings tap the MIUI version 7 times to "become a developer". Then go to developer options and switch adb debugging on.
Follow the adb and fastboot guide, but don't flash this recovery to your phone. Instead in your cmd or terminal type: This will boot your phone in fastboot mode, then type: Replace <your_downloaded_twrp.img> with the actual name of the image. This will boot you into twrp recovery without flashing it to your phone. Probably you will be welcomed with a menu with a slider that says "swipe to allow modifications" don't swipe, just choose "keep system read only". In the menu choose Install (install a zip) and flash the latest Magisk from your internal storage.
Reboot to system and you have root access. If Magisk manager is not installed yet, install the .apk file you downloaded. If you want to unroot the phone boot into twrp ones again and flash the Magisk uninstaller.
Click to expand...
Click to collapse
Alright thanks for the help an effort
batman957 said:
Alright thanks for the help an effort
Click to expand...
Click to collapse
Sure, no problem. Forgot to mention, if you decide to unlock the bootloader all your personal data (including internal storage) and apps will be wiped. So make a backup beforehand. Helium is a non root app that you could use for that purpose.
You could also relock the bootloader again, but that's a whole other tutorial by itself.
Medeon said:
Sure, no problem. Forgot to mention, if you decide to unlock the bootloader all your personal data (including internal storage) and apps will be wiped. So make a backup beforehand. Helium is a non root app that you could use for that purpose.
You could also relock the bootloader again, but that's a whole other tutorial by itself.
Click to expand...
Click to collapse
Just I forgot to ask can i use twrp temperorly as you said to install magisk then return back to the stock recovery and still have magisk available
batman957 said:
Just I forgot to ask can i use twrp temperorly as you said to install magisk then return back to the stock recovery and still have magisk available
Click to expand...
Click to collapse
Yes, you don't flash twrp recovery to the phone if you just boot into twrp recovery. It boots the image in your phone's RAM.
Medeon said:
Yes, you don't flash twrp recovery to the phone if you just boot into twrp recovery. It boots the image in your phone's RAM.
Click to expand...
Click to collapse
What about magisk
batman957 said:
What about magisk
Click to expand...
Click to collapse
When you install magisk trough twrp, you flash the zip file which cleverly patches parts of your boot and data partition. It does it systemlessly, so it won't modify the system. You can easily reverse this procedure by flashing the magisk uninstaller. It will bring your phone back in the state it was before rooting.

Categories

Resources