Related
Meizu comes with locked bootloader and it's vulnerability is not found for root.
So kingroot can also not root these devices
But with flyme(yun os) account you can get system privileges (root)
Another issue is for Some firmware there is no access to flyme account
"mzaccount" named app present in system apps which can be opened by nova activity like function of apps (use nova launcher, or lmt activity(lmt app then set activity mzaccont to open)
Then register your account Then go to option then tick the system privileges to get root
Just after selecting the system privileges device reboots do not afraid
After that you can give root permission to apps
Anyway second good news...
On meizu phones you can use xposed framework (apps )
You need an update.zip(firmware) in outermost part of your internal =sdcard/update.zip(better if you check it and install through recovery; first time)
Choose arm64 xposed framework for 64 bit phones like m2 note/mini
Then install your xposed framework (flash using flashfire apk by chainfire ; it may take upto 30 minute to complete in *black* screen don't afraid).
Before installation xposed you should wipe dalvik chache and chache.
When your device booted you may see app optimization starting again and again but don't worry it'll be completed.Complete installation and boot to system may take upto 1 hour so keep patience.
If you stuck in bootloop(just in case) then swich off for 15 seconds and reboot recovery and update through recovery.
I'm not responsible if any bad happens to you.
Don't delete update.zip(firmware). Put it as /sdcard/update.zip forever.(who knows when will you stuck in bootloop)
Don't flash rom with flashfire.
#####UNLOCK BOOTLOADER####
Remember by unlocking bootloader your all files(in internal) and data+ apps will be cleared
Things you'll need
1. Unlock script + recovery
(a) for meizu m2here
(b) for mx4
(C) for m1 note
2. Auto adb driver installer here
3. adb+key.exe here
4. Minimal adb and fastboot here
5. Apps- busybox free,terminal emulator ,super su
**Now see this video in YouTube**
THIS IS A PROBLEM WITH MEIZU USERS IF THEY SEEING A LONG BOOT TIME THEN HORRIFICALLY SOMETIMES THEY CAN NOT BOOT TO RECOVERY OR FASTBOOT BUT TRY WITH COOL MIND IT'LL BE DONE :laugh:
Don't afraid if you seeing bootloop let it complete
Time expected
1. for setting up driver and adb 10 minutes
2. for su binary update 5 minute
3. for install busybox 3 minutes
4. after unlocking bootloader may take time upto 2 hours in bootloop
5. in meizu boot animation takes upto 25 minutes
keep in mind
1. Try not to modify too deeply .
2. Tick usb debugging.
3. Try not to flash Rom or recovery on meizu devices without unlocking bootlaoder and deep knowledge.
4. Don't install xposed framework if you are not aware of risk .
5. Don't give file explorers root for always .
6. Don't try to delete system apps only freeze .
7. Flyme os/yun os is heavily modified Rom so don't need other theming or modification.
Sorry for my bad English
HIT THANX IF I HELPED
IF YOU HAVE ALREADY INSTALLED XPOSED IN YOUR MOBILE UNDER THE LIGHT OF THIS POST THEN PLEASE WRITE YOUR SUGGESTION/EXPERIENCE HERE SO THAT OTHER FOLLOWERS CAN BE GUIDED AND GAIN BELIEVE IN THIS METHOD
FRIENDS PLEASE REPORT WORKING AND NOT WORKING XPOSED MODULES HERE .
nasir.da.vinci said:
Meizu comes with locked bootloader and it's vulnerability is not found for root.
So kingroot can also not root these devices
But with flyme(yun os) account you can get system privileges (root)
Another issue is for Some firmware there is no access to flyme account
"mzaccount" named app present in system apps which can be opened by nova activity like function of apps (use nova launcher, or lmt activity(lmt app then set activity mzaccont to open)
Then register your account Then go to option then tick the system privileges to get root
Just after selecting the system privileges device reboots do not afraid
After that you can give root permission to apps
Anyway second good news...
On meizu phones you can use xposed framework (apps )
You need an update.zip(firmware) in outermost part of your internal =sdcard/update.zip
Then install your xposed framework (flash using flash Gordon=http://forum.xda-developers.com/attachment.php?attachmentid=2366442&d=1383402896)
If you stuck in bootloop then swich off for 15 seconds and reboot recovery and update through recovery
I'm not responsible if any bad happens to you
Don't flash rom with flash Gordon
keep in mind
1. Try not to modify too deeply .
2. Tick usb debugging.
3. Try not to flash Rom or recovery on meizu devices without deep knowledge.
4. Don't install xposed framework if you are not aware of risk .
5. Don't give file explorers root for always .
6. Don't try to delete system apps only freeze .
7. Flyme is/yun os is heavily modified Rom so don't need other theming or modification.
Sorry for my bad English
Click to expand...
Click to collapse
that is working for mx5?
thanks
eduardolobre said:
that is working for mx5?
thanks
Click to expand...
Click to collapse
Not tested but you can try ....
If flash Gordon not works then try flashfire"app.
Flash fire takes sometime 1 hour for flashing
Don't forget to put update.zip firmware in the root of sdcard
Hello,
Your tutorial about xposed also works on lollipop flyme 4.5.7 I ?
Thanks!
It will work on any meizu mobile ..no matters its locked or unlocked bootloader ...but dont try to use deep theming apps neither you'll face bootloop. If you face any type of bootloop (wait 30 minutes) then update the firmware through the native/stock flyme recovery
Here is the link to top themes https://doc-0c-2s-docs.googleuserco...384/*/0Bz7HPQ9NJ9NCWmJwSW9XRGpKODg?e=download
I have not tried this if it has paid themes then don't go ahead and install only free themes.Love and support meizu.
https://doc-0c-2s-docs.googleuserco...384/*/0Bz7HPQ9NJ9NCWmJwSW9XRGpKODg?e=download
Access deny
Sent from my MX5 using Tapatalk
http://forum.xda-developers.com/meizu-mx/help/meizu-mx5-flyme-5-xposed-how-t3290023
This one is on flyme os 5 and for me it seems easier, because the xposed is installed in about 30 sec.
kubas_inko_cz said:
http://forum.xda-developers.com/meizu-mx/help/meizu-mx5-flyme-5-xposed-how-t3290023
this one is on flyme os 5 and for me it seems easier, because the xposed is installed in about 30 sec.
Click to expand...
Click to collapse
that is great but it is not recomended for noob at least with locked bootloader devices
nasir.da.vinci said:
that is great but it is not recomended for noob at least with locked bootloader devices
Click to expand...
Click to collapse
Your right because it is nade JUST for MX5 and it have locked bootloader
Please where is the download link for xposed framework?
Sent from my Letv X500 using Tapatalk
Search exposed for lollipop in Google then go to xda and download sdk22arm64 for 64bit devices
Hello guys, please i need help on reviving my meizu m2 note. It is stuck in bootloop after trying to install Xposed Framework. The boot up is just stuck in the FLYME LOGO. The major problem now is that the phone fails to enter RECOVERY MODE else i would have wiped data/cache or even flash UPDATE.ZIP. The phone enters fastboot mode though but the bootloader is locked so, i cant flash anything via fastboot mode.
Please, help me out.
Misleading title. Clickbait
agssssss
Is there any method to unlock meizu mx4 pro ?
After installing the lollipop update I lost the rooting to the phone.
I rooted my phone again but to be sure for the next time,is there a way to root Lenovo a6000 plus permanently?
When u flash new rom, you have to root again, no way for permanent exept root option include in the rom
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
GuestStar said:
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
Click to expand...
Click to collapse
Dude sometimes root doesn't install properly i don't know why... I am on stock with 1.4Ghz oc kernel... Thing happens to me is that whenever i reboot my phone. Root stops working and says su binary needs to be updated.. I just have reinstall again and again to keep it working after boot.. So do u have any to solve it?
MukulGamer said:
Dude sometimes root doesn't install properly i don't know why... I am on stock with 1.4Ghz oc kernel... Thing happens to me is that whenever i reboot my phone. Root stops working and says su binary needs to be updated.. I just have reinstall again and again to keep it working after boot.. So do u have any to solve it?
Click to expand...
Click to collapse
For me root still work even on reboot. To root my phone, i flashed SuperSU.zip with custom recovery twrp. How about you? Did you using same thing like me or by apps like KingRoot.apk?
GuestStar said:
You wanted to root again hah? Flash SuperSU.zip (based on my knowledge stock LL cannot/hard to root withe root.apk like kingroot. So, i think the latest tricks is flash the supersu.zip) but still... if you are Advanced User if not dont trying it
Click to expand...
Click to collapse
Yup obviously.. By SU... I never use kingroot... Well i know it shouldn't have happened... Btw fresh rom install will solve it.. But i don't wanna do that.. Setting up phone again and again suks.. I just asked it because i thought if you might have had this problem! Thanks btw
To clear things up. Think of root as a system module (binary) ("su" module located in "xbin"). Each time you install a new OS, core partitions need to be formated (/cache, /data, and ofc /system). If the SuperUser module is not pre-installed in the new firmware you are flashing, it can be additionally obtained through Chainfire's installation zip. Nearly all custom ROMs have it and will work just fine, with some needing user input to activate it (Settings > Dev Settings > Root Access). While stock ROMs will NEVER have root capabilities pre-loaded.
So, all in all:
No, there is no such thing and will never be, as permanent root. Everything is being overwritten all the time.
Rooting and re-rooting the A6000 is safe and easy.
Hey all,
After my rooting experience with marshmallow, I used that with 7.1.1 and have had no issues. MODS: This was my approach to rooting 7.1.1. I apologize in advance for creating this thread if it's not necessary yet since XDA has given me so much help, I'm returning the favor.
NOTE: for those that want to roast me on this thread and/or flame me, don't do it. We are all noobs at one point or another. I have provided no links but have supplied the filename to the best in my capacity.
XDA gang,
After numerous attempts to root nougat, I tried this approach. This was the same approach I took w/ marshmallow.
I used Odin3_v3.12.3
selected 7.1.1 – look for filename j700tuvu3bqi5 NOTE: uncheck auto reboot. I do\did because in my experience, I encountered a boot loop.
after odin processes the flash, I disconnected the usb cable and did a battery pull.
Boot up your phone and let your phone build the recovery. After your phone reboots after the recovery, do a battery pull when the samsung splash screen starts to display itself.
Enter stock recovery and perform a cache, dalvik, and factory reset. Reboot from recovery.
Do a battery pull when the samsung splash screen starts to display itself. Boot back into download mode while holding volume down, home button, and power button. Let go of the buttons when the download mode screen comes up.
Use odin again and click on the AP button – select twrp_3.0.3-1_sm-j700t_23217. I found and downloaded this from XDA. Click start on odin and let odin do it thing. Disconnect the usb cable and do a battery pull.
Enter twrp recovery while holding volume up, home button and power button. Release buttons when twrp comes up.
Here, you will need to flash the latest supersu. I used v2.82-SR5. Also download no-verity-no-encrypt-ashyx.zip (big ups to ashyx for creating this)
Install these 2 files and reboot. NOTE: your phone will reboot twice – no cause for alarm.
After your phone boots up into nougat, go through the setup and reboot your phone.
After doing all of this, I've had zero issues. It may seem arduous but I found it necessary for my goal.
Did you have any issues with unlock screen lag on pin;/pattern?
There are reports and my own experience with this on a 7.0.0 version of otherwise identical process as yours to root. conclusion seems to be the no-verity-no-encrypt patch causes this, and that this patch (or something functionally identical) is integrated into supersu 2.82 versions.
edit - what model phone did you do this one? 7.1.1 not available for the j730g yet, unfortunately.
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
leo31 said:
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
Click to expand...
Click to collapse
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
DullPeon said:
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
Click to expand...
Click to collapse
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
leo31 said:
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
Click to expand...
Click to collapse
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
fullofhell said:
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
Click to expand...
Click to collapse
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
leo31 said:
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
Click to expand...
Click to collapse
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
fullofhell said:
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
Click to expand...
Click to collapse
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
leo31 said:
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
Click to expand...
Click to collapse
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
fullofhell said:
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
Click to expand...
Click to collapse
this is the 2nd time i root my device.
the first time i rooted my a3, i didn't face any lag and never laggy while unlocking screen.
but the problem is i forgot how i rooted it. which files did i flashed. which tutorial did i follow.
but no problem so far , because the fingerprint unlock does not give any lag.
Hi guys,
S7E Exynos International 935F here.
Is it possible to temp flash TWRP just to install Magisk?
Is it possible to flash anything useful using stock recovery? (Which seems to happen after booting with vol up+ home + power and waiting for abit)
Will the modded/patched boot image trip knox?
Main objective is to do a titanium backup, wipe the phone, reinstall minimum stuff + app data for that minimum stuff.
Will a ROM like Black Diamond be considered custom and thus trip knox?
Thanks!
TWRP = trip knox.
ivoryroot ( Xperia) for Samsung?
I think not, knox is not drm keys
Airbag888 said:
Hi guys,
S7E Exynos International 935F here.
Is it possible to temp flash TWRP just to install Magisk?
Is it possible to flash anything useful using stock recovery? (Which seems to happen after booting with vol up+ home + power and waiting for abit)
Will the modded/patched boot image trip knox?
Main objective is to do a titanium backup, wipe the phone, reinstall minimum stuff + app data for that minimum stuff.
Will a ROM like Black Diamond be considered custom and thus trip knox?
Thanks!
Click to expand...
Click to collapse
Any custom binary (whether twrp or samsung based custom roms or aosp based custom roms) will trigger knowx bit..
And no you can't install anything useful in stock recovery. Twrp isn't that heavy lol. You can keep it because it is 1000% more useful then stock recovery : )
And no, you cannot even flash magisk without twrp ; )
Want twrp-less root ? And a systemless too like magisk ? Try cf auto root- create your own root file (you can choose system less option there! ) and flash it using odin, other options like magisk or super su require twrp..
Sent from my S7 Edge using XDA Labs
shah22 said:
Any custom binary (whether twrp or samsung based custom roms or aosp based custom roms) will trigger knowx bit..
And no you can't install anything useful in stock recovery. Twrp isn't that heavy lol. You can keep it because it is 1000% more useful then stock recovery : )
And no, you cannot even flash magisk without twrp ; )
Want twrp-less root ? And a systemless too like magisk ? Try cf auto root- create your own root file (you can choose system less option there! ) and flash it using odin, other options like magisk or super su require twrp..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
@shah22 Thanks!
Sorry if I'm being thick.
You mentioned custom binary - do you mean firmware or does that include recovery?
I was under the impression that installing systemless root like magisk (or as you mention cf auto root) would not trigger knox and also be hidden from detection from google and/or banking type apps
My main reason for root (temp twrp) would be to either be able to do a nandroid of my system or titanium before having to wipe everything. From what you're telling me that's not going to happen.
I went through a bunch of root-less apps like smart switch for example that never saved application data, only the apk
Would you say there's a custom ROM that offers several features similar to stock but performs better with better battery life and is mature enough to be a daily driver? I saw Black Diamond but I'm cautious and I realise knox will blow but right now outside of s-health I don't think I have any 'knox' data
Anyway thanks for your time
Airbag888 said:
@shah22 Thanks!
Sorry if I'm being thick.
You mentioned custom binary - do you mean firmware or does that include recovery?
I was under the impression that installing systemless root like magisk (or as you mention cf auto root) would not trigger knox and also be hidden from detection from google and/or banking type apps
My main reason for root (temp twrp) would be to either be able to do a nandroid of my system or titanium before having to wipe everything. From what you're telling me that's not going to happen.
I went through a bunch of root-less apps like smart switch for example that never saved application data, only the apk
Would you say there's a custom ROM that offers several features similar to stock but performs better with better battery life and is mature enough to be a daily driver? I saw Black Diamond but I'm cautious and I realise knox will blow but right now outside of s-health I don't think I have any 'knox' data
Anyway thanks for your time
Click to expand...
Click to collapse
Flashing any firmware or recovery NOT signed by samsung triggers knox bit irreversibly, so flashing anything other then samsung stock WILL result in knox being triggered.. so now you know bruh xD
Any root systemless or not, any rom which is modified will trigger knox. Till now there is NO root method which doesn't triggers knox..
If you want fast stable rom, you can try black diamond rom yeah.. but i will recommend flashing latest stock oreo rom for your region and then flashing twrp+magisk plus debloat it and add any other mods you want. This way it may get less bugs then custom rom, and maybe more stable and faster, upto your preference..
And yeah, triggering knox causes samsung pay, secure folder / encryption to not work properly.. some other samsung related services and some banking apps too..
Sent from my S7 Edge using XDA Labs
shah22 said:
Flashing any firmware or recovery NOT signed by samsung triggers knox bit irreversibly, so flashing anything other then samsung stock WILL result in knox being triggered.. so now you know bruh xD
Any root systemless or not, any rom which is modified will trigger knox. Till now there is NO root method which doesn't triggers knox..
If you want fast stable rom, you can try black diamond rom yeah.. but i will recommend flashing latest stock oreo rom for your region and then flashing twrp+magisk plus debloat it and add any other mods you want. This way it may get less bugs then custom rom, and maybe more stable and faster, upto your preference..
And yeah, triggering knox causes samsung pay, secure folder / encryption to not work properly.. some other samsung related services and some banking apps too..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Haha that does clear things up thanks!
I used to try/flash custom ROMs back in the day (think nexus 1, S2, S3) then got too busy (2 kids popped up plus more work responsibilities) to delve into the community to keep up on what can and cannot be done.
My biggest gripe right now is there's no 'stock' method to nandroid where you actually save application data =\
Anyway I also naively thought you could push a custom recovery not to be flashed but just to run in fastboot so you could perform the nandroid / other stuff.. guess not
I do appreciate your advice on the way forward. I wonder if I can easily copy my s-health data to g-fit for example and be done with it :shrug:
I want to root my phone due to its huge benefits but also at the same time I want to keep my OTAs
Is it possible even if I will install them manually (but the data remains with no wipe) ?
And if so, how can I do this and whats the best way?
Thanks in advance and sorry if the language was bad <3
Tsunaimy said:
I want to root my phone due to its huge benefits but also at the same time I want to keep my OTAs
Is it possible even if I will install them manually (but the data remains with no wipe) ?
And if so, how can I do this and whats the best way?
Thanks in advance and sorry if the language was bad <3
Click to expand...
Click to collapse
Yes it's possible with a little workaround, to temporarily switch to stock Recovery (from TWRP, if you had it installed) and to stock Boot (from the one patched by Magisk) during the OTA upgrade - OTA will fail if it finds not the stock images of Recovery and Boot
After the upgrade you just flash the new Boot patched by Magisk (and flash TWRP if you will)
Or you flash TWRP and flash Magisk from TWRP
Below is a post how I recently upgraded from QFJEUXM 12.0.2 to 12.0.3. Btw, I downloaded zip and initiated OTA manually because I didn't want to wait more days to be pushed for OTA, but that's just a small detail not important for the way how to do it:
https://forum.xda-developers.com/showpost.php?p=83791185&postcount=93
Ofc, all my data, apps, settings, and Magisk modules were preserved
Generally, in the Redmi K20/Mi 9T Guides section on XDA you can find (at least two) threads about how-to root, i.e. install Magisk
Those threads describe the way to install Magisk by installing Magisk Manager, patching the Boot image, then flashing it from Fastboot (I prefer that way).
In that case TWRP is not needed (but it can be also installled)
Threads and guides are maybe old (since MIUI 11) but it doesn't matter, it's always the same method (essentially the same as in my post I gave you the link above, its part about returning back to Magisk after the OTA upgrade)
If you follow those guides you must pay attention that you patch the boot.img for exactly that (new) stock MIUI you do have and that you now use new Magisk (not some old versions as in the guides)
Alternatively, you flash TWRP by Fastboot, then flash Magisk zip from TWRP and then you install Magisk Manager
All those methods are described in other threads and posts.
Anyway, you must first unlock the Bootloader, again there is thread with a guide, or just google for how to unlock Bootloader on Xiaomi
Btw, some custom TWRP versions and Orange Fox do have Advanced options for upgrading MIUI and to keep Magisk, but when I did it that way for upgrading from QFJEUXM 11.0.5 to 12.0.2, it made me Factory reset and I lost all my files on Internal memory (it was generally an issue for the others who upgraded from MIUI 11 to MIUI 12 by flashing OTA through custom recovery)
Hence now for upgrading to 12.0.3 I didn't want to risk and did it as above
zgfg said:
Yes it's possible with a little workaround, to temporarily switch to stock Recovery (from TWRP, if you had it installed) and to stock Boot (from the one patched by Magisk) during the OTA upgrade - OTA will fail if it finds not the stock images of Recovery and Boot
After the upgrade you just flash the new Boot patched by Magisk (and flash TWRP if you will)
Or you flash TWRP and flash Magisk from TWRP
Below is a post how I recently upgraded from QFJEUXM 12.0.2 to 12.0.3. Btw, I downloaded zip and initiated OTA manually because I didn't want to wait more days to be pushed for OTA, but that's just a small detail not important for the way how to do it:
https://forum.xda-developers.com/showpost.php?p=83791185&postcount=93
Ofc, all my data, apps, settings, and Magisk modules were preserved
Generally, in the Redmi K20/Mi 9T Guides section on XDA you can find (at least two) threads about how-to root, i.e. install Magisk
Those threads describe the way to install Magisk by installing Magisk Manager, patching the Boot image, then flashing it from Fastboot (I prefer that way).
In that case TWRP is not needed (but it can be also installled)
Threads and guides are maybe old (since MIUI 11) but it doesn't matter, it's always the same method (essentially the same as in my post I gave you the link above, its part about returning back to Magisk after the OTA upgrade)
If you follow those guides you must pay attention that you patch the boot.img for exactly that (new) stock MIUI you do have and that you now use new Magisk (not some old versions as in the guides)
Alternatively, you flash TWRP by Fastboot, then flash Magisk zip from TWRP and then you install Magisk Manager
All those methods are described in other threads and posts.
Anyway, you must first unlock the Bootloader, again there is thread with a guide, or just google for how to unlock Bootloader on Xiaomi
Btw, some custom TWRP versions and Orange Fox do have Advanced options for upgrading MIUI and to keep Magisk, but when I did it that way for upgrading from QFJEUXM 11.0.5 to 12.0.2, it made me Factory reset and I lost all my files on Internal memory (it was generally an issue for the others who upgraded from MIUI 11 to MIUI 12 by flashing OTA through custom recovery)
Hence now for upgrading to 12.0.3 I didn't want to risk and did it as above
Click to expand...
Click to collapse
I really appreciate your reply but I kinda don't know much info to understand most of what u said
My last time with root was about 3 years ago with king root on Mi A1 and I didn't care about updates then
so it's my very first time with magisk and TWRP and that stuff
Could u tell me what is the best method of u mentioned to keep my files and everything with no delete and also makes me able to upgrade Official ROM with no deletes
After this i'll start digging to learn but I want to know what should I dig for
Thanks bro
Tsunaimy said:
I really appreciate your reply but I kinda don't know much info to understand most of what u said
My last time with root was about 3 years ago with king root on Mi A1 and I didn't care about updates then
so it's my very first time with magisk and TWRP and that stuff
Could u tell me what is the best method of u mentioned to keep my files and everything with no delete and also makes me able to upgrade Official ROM with no deletes
After this i'll start digging to learn but I want to know what should I dig for
Thanks bro
Click to expand...
Click to collapse
Unlocking Bootloader usually takes to wait 7 days=168 hours, hence you have enough time to read?
Unlocking Bootloader:
https://c.mi.com/thread-1857937-1-1.html
Unlocking Bootloader: and Installing TWRP, OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
- for step 6, installing TWRP, use TWRP I'm giving you below
- instead of 7, execute this command:
>> fastboot oem reboot-recovery
- step 7, don't Format Data (unless you really go to install custom ROM, otherwise you don't need to)
- stop here for installing TWRP
Suggesting you to use this TWRP, 3.4.0.2 from OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
- every time you boot to TWRP, you must type in your Android screen unlock pin, TWRP needs to be able to read/write to Data and Internal memory
Learn about using ADB and Fastboot:
https://www.makeuseof.com/tag/use-adb-fastboot-android/
- you can't do things with ADB that require root, but you can read
- similarly, fastboot commands mostly require unlocked Bootloader, but you can read
- google yourself
About installing Magisk, read in these threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
- if you have time, go through the whole threads, you will see variations
- don't worry if talking about MIUI 11, same applies for MIUI 12, you will just need to download your MIUI 12 recovery/zip firmware, will give you link below
- I'll give you below the link for the latest Magisk
MIUI firmwares, download, etc:
https://androidfilebox.com/tips/how-to-install-miui-recovery-rom/
https://androidfilebox.com/tips/how-to-install-miui-fastboot-rom/
https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
https://xiaomifirmwareupdater.com/miui/davinci/
https://codeexercise.com/xiaomi-all-android-mobile-secret-code-list/amp/
Various methods to extract stock Recovery, Boot, Persist and Persistbak partitions:
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Magisk documentation and download:
https://github.com/topjohnwu/Magisk/blob/master/README.MD
- read the docs
- I would suggest you to use Canary (don't worry, Stable is far behind), hence you will only need to download Magisk Manager Canary (then follow XDA guides I gave you above)
zgfg said:
Unlocking Bootloader usually takes to wait 7 days=168 hours, hence you have enough time to read
Unlocking Bootloader:
https://c.mi.com/thread-1857937-1-1.html
Unlocking Bootloader: and Installing TWRP, OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/guide-unlock-bootloader-flash-xiaomi-eu-t3952443
- for step 6, installing TWRP, use TWRP I'm giving you below
- instead of 7, execute this command:
>> fastboot oem reboot-recovery
- step 7, don't Format Data (unless you really go to install custom ROM, otherwise you don't need to)
- stop here for installing TWRP
Suggesting you to use this TWRP, 3.4.0.2 from OP post #1:
https://forum.xda-developers.com/mi-9t/how-to/recovery-unofficial-twrp-3-4-0-1-t4135159
- every time you boot to TWRP, you must type in your Android screen unlock pin, TWRP needs to be able to read/write to Data and Internal memory
Learn about using ADB and Fastboot:
https://www.makeuseof.com/tag/use-adb-fastboot-android/
- you can't do things with ADB that require root, but you can read
- similarly, fastboot commands mostly require unlocked Bootloader, but you can read
- google yourself
About installing Magisk, read in these threads:
https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
- if you have time, go through the whole threads, you will see variations
- don't worry if talking about MIUI 11, same applies for MIUI 12, you will just need to download your MIUI 12 recovery/zip firmware, will give you link below
- I'll give you below the link for the latest Magisk
MIUI firmwares, download, etc:
https://androidfilebox.com/tips/how-to-install-miui-recovery-rom/
https://androidfilebox.com/tips/how-to-install-miui-fastboot-rom/
https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
https://xiaomifirmwareupdater.com/miui/davinci/
https://codeexercise.com/xiaomi-all-android-mobile-secret-code-list/amp/
Various methods to extract stock Recovery, Boot, Persist and Persistbak partitions:
https://forum.xda-developers.com/mi-9t/how-to/root-k20-indian-rom-v10-3-6-0-twrp-t3958566
Magisk documentation and download:
https://github.com/topjohnwu/Magisk/blob/master/README.MD
- read the docs
- I would suggest you to use Canary (don't worry, Stable is far behind), hence you will only need to download Magisk Manager Canary (then follow XDA guides I gave you above)
Click to expand...
Click to collapse
bro I can`t really thank u enough for the effort
as I got it:
1- Unlock bootloader
2- Install TWRP (the version u provided)
3- Install Magisk (last link u provided) right?
Is there any step of those that is risky or unsafe that may brick the phone ?
PS: On mi unlock application it says all phone data will be erased !
what should I do ?
By unlocking Xiaomi phone you won't lose anything but previous user data stored in phone, unlike ASUS phone losts OTA permanentry.
So make a backup, also I recommend you first picking your secondaly phone, not your daily using one.
Tsunaimy said:
bro I can`t really thank u enough for the effort
as I got it:
1- Unlock bootloader
2- Install TWRP (the version u provided)
3- Install Magisk (last link u provided) right?
Is there any step of those that is risky or unsafe that may brick the phone ?
PS: On mi unlock application it says all phone data will be erased !
what should I do ?
Click to expand...
Click to collapse
As described, TWRP is optional, not needed for Magisk/root but it would be useful to have, so yes, install TWRP
Instructions for unlocking Bootloader say to do Backup. Copy photos and files from Internal memory to PC.
Export contacts to CVS file and also copy to PC.
Backup to Google your Google accounts, contacts, WhatsApp, etc.
Use Settings, Additional settings, Backup, and cooy to PC.
You can also use Settings, MIUI account to backup things
Installations of Magisk and TWRP will not erase data. Generally, they are not risky unless you make really stupid mistake like flashing TWRP img file to System partition instead of to Recovery partition and so - that's why you have instructions how to use Fastboot command to flash TWRP
It's more risky if you go to use e.g. MiFlash (you don't need for TWRP and Magisk), then people can screw up things and need authorized EDL support