Related
Ok so I've seen a lot of confusion on how to correctly flash OxygenOS on your brand new OnePlus 5, and also how to correctly and easily root your phone.. This guide aims to clear up any confusion regarding this. Ready? Let's move on.
Q: What's the difference between International and Chinese versions of the OnePlus 5?
A: Hardware-wise there is absolutely no difference between the 2 versions. In terms of software, the international version runs OxygenOS (OOS) while the Chinese version runs HydrogenOS(H2OS). H2OS has no Google services pre-installed and is generally not recommended for use outside China. Both OxygenOS and HydrogenOS are official updates by OnePlus.
Q: I bought a Chinese phone. How do I install OxygenOS then?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update.
2. Place it in the root of your internal memory. Basically don't put the file in any folder.
3. Go to Settings > System updates, press the gear icon and select Local upgrade.
4. Choose the file, the phone will boot into recovery and everything is done.
Q: OK I want to root my phone but I don't want to lose Android Pay, Netflix, Pokemon GO etc. Is it possible?
Simple answer: Yes. Long answer: Maybe not in the long run.
Why is that so? You see, back in the old days there were little downsides to rooting. Alas, Android Pay and Pokemon GO came along, and in an effort to tighten up security, Google implemented this thing called
SafetyNet. Basically it's a measure to test your system integrity, meaning that any modification to system will trigger SafetyNet and many apps will be "locked down". Android Pay and Pokemon GO will not work,
and Netflix won't show up on Google Play anymore. Some devices even check for unlocked bootloader, but apparently not the OnePlus 5, so you don't have to switch to a custom kernel to root.
To overcome this problem, the brilliant minds at XDA came up with system-less root. Chainfire was the first to implement it in SuperSU, but right now nobody uses SuperSU anymore. Magisk is the new kid in town,
and quite frankly much better IMO.
Q: Alright enough talk, how do I root the phone?
A: Patience my young Padawan. I will get to that in a moment. But here are some things you have to know.
1. Rooting involves unlocking your bootloader, and ALL YOUR DATA WILL BE WIPED. Keep a backup and move everything in your internal memory somewhere else.
2. Magisk may beat SafetyNet now, but there is no guarantee this will always be the case. So your SafetyNet enabled apps may not work all the time.
3. OTA updates from OnePlus will work differently when you are rooted. But hey that's what this guide is for. :good:
Easy rooting guide
1. Install ADB drivers.
2. Go into settings > about phone. Press the build no. a few times to activate developer options.
3. Turn on developer options, OEM unlocking and USB debugging.
4. Connect phone to PC and allow ADB access on phone. Wait for drivers to finish installing.
5. Download and install this simple tool on your PC.
6. Download one of the 2 TWRP recoveries below.
TWRP Official
xdvs23's TWRP
7. Open the All-in-One tool and make sure your device is recognised as OnePlus 5. Click on Unlock bootloader. Your bootloader is now unlocked and all your DATA WILL BE WIPED!
8. Select the "and boot it" arrow and click flash TWRP, click manual mode and choose the TWRP.img file you downloaded earlier.
9. After everything is done, your phone should now boot into TWRP successfully. Do not reboot yet.
10. On your PC, download the latest version of Magisk. Place the zip file onto your phone using USB and flash it with TWRP. Clear cache and reboot into system.
11. You should now see a new app called Magisk Manager. Check for updates!
12. However, do keep in mind not to mess around the system. If you need something, check to see if there any Magisk Modules available. There is also a small repo in the downloads section in Magisk Manager. Also Adaway works great with Magisk. Just make sure to turn on systemless host file in Magisk manager.
14. Congrats you are now rooted!:highfive:
Q: Alright now that I'm rooted, how do I get official updates?
A: 1. Download the latest OxygenOS from here. Download the full zip and NOT the OTA update. Place it on your phone. Make sure you also have your Magisk zip.
2. Boot into TWRP. Press the volume button when the bootloader unlocked screen comes up. Use volume buttons and power button to select recovery.
3. Flash the OxygenOS zip file. DO NOT reboot yet!
4. Tap the home button and flash Magisk. Clear cache.
5. Reboot into system and you are done!
Hope this guide is simple enough for you guys to understand. It might seem daunting at first, but practice makes perfect.
Also it is not a requirement to root, most people get by fine without ever rooting. But we are not like normal people, are we? Why else would we be on XDA then?
Further questions
Q1: Why Magisk and not SuperSU?
A: Besides the fact that Magisk is being constantly updated to bypass SafetyNet, it is also open-source. Wish I could say the same for SuperSU, the app is not what it used to be. Chainfire is no longer aware of the changes made in his app and I for one am not willing to take my chances with a shady developer. I had countless bad experiences with Chinese apps, many of them created by large companies. Check out this thread for more info.
Q2: Why exactly is HydrogenOS not recommended for use outside China?
A: Besides the aforementioned lack of Google apps, HydrogenOS is also tweaked differently from OxygenOS. It is significantly more aggressive in killing apps and not letting them run in the background, as you would expect with the number of rogue apps in China, made worse by the fact that there is no Play Store in China. OxygenOS on the other hand has a limit of 32 apps in memory, which I guess is a nice compromise between performance and battery life.
Reserved just in case. Probably will never need it though.
to be fair, there are still lots of people using SuperSU..
What should I do if I still want to use SuperSU?
2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.
ipredatorv said:
2 noob questions @jasonwsc or anyone who knows
How about wiping dalvik and cache?
And how about encryption? Do I need to remove my fingerprint/security pattern before flashing OR rooting?
Thanks a lot for your help, the OP5 will be the first phone I can actually root. My old Xperia Z (2013) had a locked bootloader that was not unlockable haha.
Click to expand...
Click to collapse
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.
iamelton said:
to be fair, there are still lots of people using SuperSU..
Click to expand...
Click to collapse
Ningyou Higeki said:
What should I do if I still want to use SuperSU?
Click to expand...
Click to collapse
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
jasonwsc said:
Wiping Dalvik and cache is usually done after flashing a ROM in TWRP. Not that big of deal now that many apps use ART, but still good to do to prevent app crashes.
No need to remove fingerprint security before rooting.
Click to expand...
Click to collapse
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk
ipredatorv said:
Thanks for the clarification!
I only asked about wiping dalvik/cache because some other people here recommended that, as it may help to fix my battery drain issue.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It might help with your battery drain issue, but chances are some apps are running in the background draining your battery.
Google services not working
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.
Nishatian1 said:
I have installed oxygen OS in my chinese version OP5 following above method. However, after installing oxygen OS my google play store isnt working. When I open google play store, it stucks on checking info.
Click to expand...
Click to collapse
Just a wild guess, but are you still in China? Check your VPN before trying to access the Google Playstore. Otherwise, remove the Playstore and download the most recent Playstore apk from a website like apkmirror. If they offer multiple versions, go for ARM 64.
Sent from my ONEPLUS A5000 using Tapatalk
jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?
jasonwsc said:
Just flash SuperSU zip instead of Magisk.
I don't know why anyone still uses SuperSU though. For one, it's sold to a Chinese company and is no longer open source. Not to mention it doesn't pass SafetyNet at all.
Click to expand...
Click to collapse
I got my Chinese OP5 two days ago and went through the whole procedure of unlocking, rooting, and flashing OxygenOS. Now I see that somebody took the time to write a nice guide on how to do it. Thanks @jasonwsc! I really wish I had this available to me already. I am sure it's gonna be a great help to others though!
I wasn't aware that SuperSU had been sold to a Chinese company through and that it is no longer open source. Knowing what I know now I regret flashing SuperSU yesterday and would love to switch to Magisk.
My question would be: what's the "proper way" to switch from SuperSU to Magisk? Just unroot via SuperSU and flash Magisk, or is there a better, cleaner way?
Edit:
Nevermind, just searched it and there's a super nice guide here.
Ningyou Higeki said:
I'm a little tired of tuning my phone now. And I don't care about SafetyNet. BTW, how's Magisk's compatibility now?
Click to expand...
Click to collapse
Magisk works fine, have no issues so far.
Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?
Moazamali said:
Hello,
I have the opportunity to receive an OP5T (128 GB)
from China. The ROM will be Hydrogen OS and not Oxygen OS.
I would like to be sure that the procedure used to install Oxygen OS will be the same as for the OP5?
Click to expand...
Click to collapse
Yes it's the same. Just flash the firmware file for OP5T instead of the OP5.
i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks
nayemohd said:
i have international model oneplus 5. My phone was bricked, so i unbricked the phone by flashing h2os. I have rooted my phone with supersu and unrooted it again by flashing stock recovery. i want to now flash my phone with oxygenos. i have tried but no success. Please guide me with correct method.
Thanks
Click to expand...
Click to collapse
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.
strongst said:
See here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003 it might be useful to format internal storage.
Click to expand...
Click to collapse
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?
kimon60 said:
Good morning all,
I have the same problem. Installed a H2os on a international oneplus 5.
Didn't like it so much so I formatted the system and installed the open beta 26.
However if I want to use the latest recovery either to clear cache or davlik cache I get a bunch of errors.
Any idea why?
Click to expand...
Click to collapse
Which h2os version and which recovery version did you use(file names please)? What do you mean with formatting the system? What did you wipe or format exactly?
I'm currently on a stable build of Oxygen OS 5.0.2 Oreo and I was thinking of rooting my phone using Magisk.Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta. I'll have to unlock the bootloader and flash TWRP but this is where the confusion comes in - Can I root a stable build of OOS? Will I have to switch to beta to root? Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP. So can someone please explain what that Issue really is and will it arise in my case? And if someone can just give me a guide on how to root it, I'll really appreciate it. And are there any known issues which arise after successfully rooting OOS 5.0.2?
No obstacles in rooting stable OOS and no problems should arise after doing it. You just need to make a backup of all your data, unlock bootloader, flash TWRP, flash Magisk and go.
If you trigger dm-verity, tyou have two choices - either ignore it on every reboot or follow a guide about removing it.
anshikohri said:
I'm currently on a stable build of Oxygen OS 5.0.2 Oreo and I was thinking of rooting my phone using Magisk.Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta. I'll have to unlock the bootloader and flash TWRP but this is where the confusion comes in - Can I root a stable build of OOS? Will I have to switch to beta to root? Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP. So can someone please explain what that Issue really is and will it arise in my case? And if someone can just give me a guide on how to root it, I'll really appreciate it. And are there any known issues which arise after successfully rooting OOS 5.0.2?
Click to expand...
Click to collapse
All things that you are mentioning show clearly that you didn't pay attention to all the basic info for rooting a 3/3T.
Why do u need a guide for Oreo, when you have a guide for nougat?
It's exactly the same method.
Also DM verity is just a warning, so why to be scared.
Maybe you should avoid doing something that you don't understand.
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
All things that you are mentioning show clearly that you didn't pay attention to all the basic info for rooting a 3/3T.
Why do u need a guide for Oreo, when you have a guide for nougat?
It's exactly the same method.
Also DM verity is just a warning, so why to be scared.
Maybe you should avoid doing something that you don't understand.
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
Well I had a Redmi 2 before this and when I tried to root my lineage Os based on oreo with magisk using the same method I used with Nougat, i bricked my device. So that's why i was a little apprehensive. But thank you for your response.
przemcio510 said:
No obstacles in rooting stable OOS and no problems should arise after doing it. You just need to make a backup of all your data, unlock bootloader, flash TWRP, flash Magisk and go.
If you trigger dm-verity, tyou have two choices - either ignore it on every reboot or follow a guide about removing it.
Click to expand...
Click to collapse
Will I run into trouble with xposed or substratum on OOS?
anshikohri said:
Will I run into trouble with xposed or substratum on OOS?
Click to expand...
Click to collapse
No, if you use compatible modules and themes. I had no problems using both on OOS. Please note that if you install Xposed, you won't be able to use SafetyNet protected apps (Android Pay, Pokemon Go, Snapchat (you have to login before installing Xposed to make it work) etc.).
anshikohri said:
Well I had a Redmi 2 before this and when I tried to root my lineage Os based on oreo with magisk using the same method I used with Nougat, i bricked my device.
Click to expand...
Click to collapse
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
anshikohri said:
Most of the guides that I've seen had users root using a nougat based version of OOS or they were on beta.
Click to expand...
Click to collapse
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
anshikohri said:
Also, I'm a little scared about whether this DM-Verity issue will arise or not if I try to root or flash TWRP.
Click to expand...
Click to collapse
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
anshikohri said:
And are there any known issues which arise after successfully rooting OOS 5.0.2?
Click to expand...
Click to collapse
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.
redpoint73 said:
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.
Click to expand...
Click to collapse
That certainly cleared all my doubts and my inhibitions. Thank you so much for taking the time to address my questions.
anshikohri said:
That certainly cleared all my doubts and my inhibitions. Thank you so much for taking the time to address my questions.
Click to expand...
Click to collapse
You're certainly welcome. There is a "Thanks" button you can click for any posts that you found helpful, if you care to do so.
And a constructive criticism on forum etiquette: please don't quote a whole huge long post, like you did for my response. I know it's the default when responding to include a quote. But simply delete what isn't directly relevant (maybe keep a few lines, as appropriate) in the interest of keeping the forum free of clutter; and avoid folks have having to scroll down a whole screen/page which is just my post in duplicate. You can still edit the previous post, if you like.
Good luck on rooting. I'm sure it will go fine. Welcome to the dark side.
redpoint73 said:
And a constructive criticism on forum etiquette: please don't quote a whole huge long post, like you did for my response. I know it's the default when responding to include a quote. But simply delete what isn't directly relevant (maybe keep a few lines, as appropriate) in the interest of keeping the forum free of clutter; and avoid folks have having to scroll down a whole screen/page which is just my post in duplicate. You can still edit the previous post, if you like.
As you can see, I'm new to this, so forgive me. I'll keep this in mind the next time I post something and Thank You for your advise and your help.
Click to expand...
Click to collapse
redpoint73 said:
You aren't being specific enough when you say "same method". The general method is often similar. But you will virtually never use the exact same steps when rooting different Android builds (such as Nouget vs. Oreo). In particular, you always need to use updated versions of files for TWRP and Magisk. By definition, the root exploits will change between Android versions. So using old version Magisk is basically asking for a "soft brick". Not a real brick. It usually just means you need to use the correct version Magisk in order to recover. Or at worst, flash recovery image (or restore TWRP backup - which you should always have a backup of the stock ROM before rooting) then root with the proper files. Don't know anything about your old phone - but I'll guess this is what happened (which is a common enough scenario).
Similarly, you should also use the most current version TWRP. Older versions may sometimes work, depending on the situation. But Oreo (vs. Nougat) in particular, TWRP had to be updated to be compatible. Meaning you must use a Oreo-compatible version of TWRP to avoid problems. Short story, use current version TWRP to avoid problems.
Current versions are:
TWRP 3.2.1-0
Magisk v16.0
Also proceed with the knowledge that this device is very hard to brick. Just flashing TWRP and Magisk will not brick it (not a true brick anyway - a "soft" brick is easy to recover from as already described). Just make sure you are using Magisk for the OP3/3T (not some other device) and the risk is virtually zero. Even in the case of a brick, this device has an unbricking tool. Just be sure to take the following precautions:
- Make a TWRP backup of the stock ROM before you flash Magisk (always amazed at how many folks skip this!) or otherwise have the stock recovery image available in case anything happens. Basically always have a backup plan!
- Find the unbrick tool, and again have it available (at least bookmarked) in case you need it.
- Most importantly, read and understand all the steps and concepts before you begin. As another already mentioned, it seems your knowledge about some of the concepts is a bit lacking.
---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------
Beta or Stable doesn't matter. I don't know if I've ever seen a root guide specific to the Beta version, so I'm not even sure what you are talking about.
As far as the guides being for Nougat, I've already addressed that above. Basically, everything is the same, except the file versions (use updated TWRP, Magisk) so that is why nobody has bothered posting new guides for every OOS build.
DM-verity is just a warning screen that appears when you reboot or power-on the phone. It will go away and continue to boot normally after 5 seconds, or just press the power button to dismiss the warning.
Once the phone has TWRP and rooted, you will have the DM-verity warning screen. If you like, you can flash a patched boot image, so you don't see the DM-verity warning screen on reboot/power-on.
You will also have a very similar (but separate) warning screen once the bootloader is unlocked. Unlike the DM-verity screen, the bootloader unlocked warning is impossible to be removed. The only way to remove it is to relock the bootloader, which I would strongly warn you not to do on a modified (TWRP and root) device! The bootloader unlock warning screen is just something you live with if you are rooted (just wait the 5 seconds or press the power button to skip it).
There is also the unlikely event that DM-verity will outright prevent the OS from booting. But this shouldn't happen just from flashing TWRP and Magisk (at least not if you've done it properly). Even if this happens, just restore your TWRP backup, or flash recovery image, and start over - checking what you did (cause you probably did something wrong).
This is so vague, as to make it hard to figure out what you are even asking.
In short, No.
Long answer: Some apps will not work with root, such as banking apps and Netflix. But the Magisk "Hide" feature should work to conceal root and make these apps work. It's a whole topic in itself, so read up in existing threads if this applies to you, and you want more info.
Other than that, there isn't anything with Magisk root that I would consider an "issue" and make me want to unroot.
Click to expand...
Click to collapse
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery nd super su root but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery nd super su root but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
Please don't include page-long quotes in your post. For that matter, don't quote my posts at all, if you aren't going to refer to it, or read it.
And please only post your problem to one thread, per forum rules. It will be answered. Making more posts, will NOT get your question answered any faster. It will just confuse those trying to help you, and confuse you; jumping around to 4 different threads.
Used Twrp to flash SuperSU installed Xposed framework installer and flashed the nougat sdk.
Modules are working
Zuper
Lucky patcher
Gravitybox
3C
One tap video downloader
Few quick questions. Did you use the official Asus unlock app? Can you post a link to the twrp download?
Shakez619 said:
Used Twrp to flash SuperSU installed Xposed framework installer and flashed the nougat sdk.
Modules are working
Zuper
Lucky patcher
Gravitybox
3C
One tap video downloader
Click to expand...
Click to collapse
Where did you get the TWRP? Can you give me the link?
I want to install magisk and enable camera2 api so I can install gcam
DumDumBumBum said:
Where did you get the TWRP? Can you give me the link?
I want to install magisk and enable camera2 api so I can install gcam
Click to expand...
Click to collapse
You don't need trwp to install magisk. You can use magisk manager to patch the stock boot image, then adb push to install the patch boot image to your device. There are plenty of tutorials on how to do this here on XDA.
Cyb3rk1ll said:
You don't need trwp to install magisk. You can use magisk manager to patch the stock boot image, then adb push to install the patch boot image to your device. There are plenty of tutorials on how to do this here on XDA.
Click to expand...
Click to collapse
Yeah i know, but haven't try it myself and I usually use twrp to install it. That's why I lack the confidence to do so ?.
Have you tried rooting your zenfone 5q?
DumDumBumBum said:
Yeah i know, but haven't try it myself and I usually use twrp to install it. That's why I lack the confidence to do so ?.
Have you tried rooting your zenfone 5q?
Click to expand...
Click to collapse
I have not yet, I'm waiting for an unlock method that is reversable, I have however used magisk to patch boot images on some of my other devices that don't have twrp available.
---------- Post added at 05:50 PM ---------- Previous post was at 05:44 PM ----------
DumDumBumBum said:
Yeah i know, but haven't try it myself and I usually use twrp to install it. That's why I lack the confidence to do so ?.
Have you tried rooting your zenfone 5q?
Click to expand...
Click to collapse
Which part makes you uncomfortable? Is it patching the image or using adb push?
But bro, feels like you posted in the wrong forum. This forum is for Zenfone 5 x86 A500CG/ A501CG.
mzj4213 said:
But bro, feels like you posted in the wrong forum. This forum is for Zenfone 5 x86 A500CG/ A501CG.
Click to expand...
Click to collapse
Is there a dedicated forum for the 5q? I've looked on the app and haven't found one. I find threads for it in all kinds of places though.
Cyb3rk1ll said:
Is there a dedicated forum for the 5q? I've looked on the app and haven't found one. I find threads for it in all kinds of places though.
Click to expand...
Click to collapse
Well yeah somehow, maybe you can make a request to the moderators? Or maybe use some kind of tag temporarily?
DumDumBumBum said:
Where did you get the TWRP? Can you give me the link?
I want to install magisk and enable camera2 api so I can install gcam
Click to expand...
Click to collapse
Soon after making my original post I downloaded the stock rom from the Asus support page the same place I got the bootloader unlock app from.
After flashing I got brave or stupid and found a site that had a TWRP for the zc600kl so i said what the hell and installed the TWRP idk if I can link it here but I'm sure they'll get rid of it if it isn't.
https://mega.nz/#!OuJHnaJR!aUTwAtRcEukqOi6XMh-FKsYcM22gHEzC35YajMkSOns
It turned out to be TWRP 3.2.3.0 and works perfectly. only issue I had was during the Magisk installation, twrp couldn't mount anything. turns out it was showing my internal storage as 0 but it was an extremely easy fix! all I had to do was just change the phones storage file system from it's original to another then immediately back to the original file system (can't remember specifics) within the twrp advanced menu I think, but it worked just fine and my internal storage read the correct size. Found fix on YouTube easily.
I installed magisk flawlessly then installed xposed seamless now have the best of both and everything is working great phone is stable no issues at all I'm very pleased,
Safety net check fails but IDC I don't need it.
Ridiculously easy root I love this phone ?? oh and now I have iOS 11 Emojis lol
Hope this helps all you Zenfone 5Q zc600kl owners out there.
If anyone wishes to know anything else PM me I'll try to help.
???
Shakez619 said:
Soon after making my original post I downloaded the stock rom from the Asus support page the same place I got the bootloader unlock app from.
After flashing I got brave or stupid and found a site that had a TWRP for the zc600kl so i said what the hell and installed the TWRP idk if I can link it here but I'm sure they'll get rid of it if it isn't.
https://mega.nz/#!OuJHnaJR!aUTwAtRcEukqOi6XMh-FKsYcM22gHEzC35YajMkSOns
It turned out to be TWRP 3.2.3.0 and works perfectly. only issue I had was during the Magisk installation, twrp couldn't mount anything. turns out it was showing my internal storage as 0 but it was an extremely easy fix! all I had to do was just change the phones storage file system from it's original to another then immediately back to the original file system (can't remember specifics) within the twrp advanced menu I think, but it worked just fine and my internal storage read the correct size. Found fix on YouTube easily.
I installed magisk flawlessly then installed xposed seamless now have the best of both and everything is working great phone is stable no issues at all I'm very pleased,
Safety net check fails but IDC I don't need it.
Ridiculously easy root I love this phone ? oh and now I have iOS 11 Emojis lol
Hope this helps all you Zenfone 5Q zc600kl owners out there.
If anyone wishes to know anything else PM me I'll try to help.
Click to expand...
Click to collapse
Just tried with this and it says it's too big when flashing and fails ZF5Q ZC600kl (X017D)
slayerking said:
Just tried with this and it says it's too big when flashing and fails ZF5Q ZC600kl (X017D)
Click to expand...
Click to collapse
Same here, seems as though this twrp is for the X017DA which has a much larger size recovery compared to the regular X017D which has a stock recovery size and flash limit of 32mb. I tried for hours to get a ported twrp running on the X017D to no avail. Can someone help?
PizzaG said:
Same here, seems as though this twrp is for the X017DA which has a much larger size recovery compared to the regular X017D which has a stock recovery size and flash limit of 32mb. I tried for hours to get a ported twrp running on the X017D to no avail. Can someone help?
Click to expand...
Click to collapse
I just finished attempting to flash this recovery using my X017DA and I'm getting the file size too large error as well.
There are NUMEROUS people stating that they've rooted this phone and I'd SURE as hell love to know how.
I unlocked the bootloader at this point for nothing, and it's rather irritating.
It's bad enough I have spotty service on this phone because apparently, it doesn't support band 12 (which is crap) and ASUS refuses to cert it for VOLTE
I love the cameras, and functionality of this phone, and for the price the specs are GREAT, but this WILL be the last and only ASUS phone I'll purchase. Hell, I might even ban their computer components from my home after this fiasco.
Question!
Did you use the official Asus unlock app?
dracconus said:
I just finished attempting to flash this recovery using my X017DA and I'm getting the file size too large error as well.
There are NUMEROUS people stating that they've rooted this phone and I'd SURE as hell love to know how.
I unlocked the bootloader at this point for nothing, and it's rather irritating.
It's bad enough I have spotty service on this phone because apparently, it doesn't support band 12 (which is crap) and ASUS refuses to cert it for VOLTE
I love the cameras, and functionality of this phone, and for the price the specs are GREAT, but this WILL be the last and only ASUS phone I'll purchase. Hell, I might even ban their computer components from my home after this fiasco.
Click to expand...
Click to collapse
please tell me how you unlock the bootloader of zc600kl x017d ?
I m trying for months to do so but fail, as the official unlock apk tool is not working.
Please tell me how you unlock the bootloader on ([email protected])
I shall be very thankfull to you for this
Cyb3rk1ll said:
Few quick questions. Did you use the official Asus unlock app? Can you post a link to the twrp download?
Click to expand...
Click to collapse
oye me puedes ayudar para descargar una twrp en asus x017da me puedes dar un link
Has someone with unclocked bootloader been able to install Magisk?
It would be awesome to have root and Gpay working thanks to it
mr-mauro said:
Has someone with unclocked bootloader been able to install Magisk?
It would be awesome to have root and Gpay working thanks to it
Click to expand...
Click to collapse
I hear it should be easy enough. I'll be able to unlock on Tuesday evening and so will report back on my successes (and/or failures!)
Yes
mr-mauro said:
Has someone with unclocked bootloader been able to install Magisk?
It would be awesome to have root and Gpay working thanks to it
Click to expand...
Click to collapse
I may even try just keep stock rom and root that, by attempting to modify the boot.img, as shown in this thread:
https://forum.xda-developers.com/apps/magisk/magisk-twrp-device-encryption-t3733601/page1
Stock rom is fine for me for now and whilst I'd love to try out the EU rom, I will be happy enough to have my phone as it is now (firmware wise) but with root and all the joys that brings (app theming, ad blocking, viper4android etc).
Tuesday night I'll get to start playing around and attempting all of this. I'll definitely post a guide of whatever I'm successful with
cd993 said:
I may even try just keep stock rom and root that, by attempting to modify the boot.img, as shown in this thread:
https://forum.xda-developers.com/apps/magisk/magisk-twrp-device-encryption-t3733601/page1
Stock rom is fine for me for now and whilst I'd love to try out the EU rom, I will be happy enough to have my phone as it is now (firmware wise) but with root and all the joys that brings (app theming, ad blocking, viper4android etc).
Tuesday night I'll get to start playing around and attempting all of this. I'll definitely post a guide of whatever I'm successful with
Click to expand...
Click to collapse
My day will be Wednesday evening It get unlocked at around 11.30pm on Tuesday so I won't have enough time to play with it on Tuesday ahahaha
mr-mauro said:
My day will be Wednesday evening It get unlocked at around 11.30pm on Tuesday so I won't have enough time to play with it on Tuesday ahahaha
Click to expand...
Click to collapse
Nice! Mines 3:30pm on Tuesday so I'll rush home from work and do my best to get the EU rom flashed via trwrp
How has everyone progressed with unlocking their phone. My time has come for me to do it, but busy with work the next couple days so have to wait til then. I plan to unlock, then hopefully root so I can do a full back up, then flash a global rom on my chinese version phone. One thing I don't understand yet is do I need to install another recovery (twrp) or will the global version flash ok on the stock recovery? Thanks
perryano said:
How has everyone progressed with unlocking their phone. My time has come for me to do it, but busy with work the next couple days so have to wait til then. I plan to unlock, then hopefully root so I can do a full back up, then flash a global rom on my chinese version phone. One thing I don't understand yet is do I need to install another recovery (twrp) or will the global version flash ok on the stock recovery? Thanks
Click to expand...
Click to collapse
Check my [GUIDE] How I flashed TWRP, Xiaomi.eu rom and rooted with Magisk
perryano said:
How has everyone progressed with unlocking their phone. My time has come for me to do it, but busy with work the next couple days so have to wait til then. I plan to unlock, then hopefully root so I can do a full back up, then flash a global rom on my chinese version phone. One thing I don't understand yet is do I need to install another recovery (twrp) or will the global version flash ok on the stock recovery? Thanks
Click to expand...
Click to collapse
If you just want to flash the global version use miflash. If you want to go xiaomi.eu you have to use TWRP.
CrazyBeaver2377 said:
If you just want to flash the global version use miflash. If you want to go xiaomi.eu you have to use TWRP.
Click to expand...
Click to collapse
I just flashed blobal version as I'm in Australia and all went well. Next step is to root. I can still install twrp right? Will this end up wiping my device if I do it now?
perryano said:
I just flashed blobal version as I'm in Australia and all went well. Next step is to root. I can still install twrp right? Will this end up wiping my device if I do it now?
Click to expand...
Click to collapse
TWRP per se doesn't wipe anything but... Yes, if you didn't format yet the data partition do 'decrypt' it, you'll have to do it
Grazie amico. Sounds like I have to do it again. Didn't take long to restore from backup. Mi backup is actually very good.
With Unlocked bootloader magisk "works" but you can't update to magisk 18. It's broken for some reason. Only magisk 17 works.
xdarkmario said:
With Unlocked bootloader magisk "works" but you can't update to magisk 18. It's broken for some reason. Only magisk 17 works.
Click to expand...
Click to collapse
Magisk Canary Build v18.2 works fine on Xiaomi.eu rom, with safety net passing fully
xdarkmario said:
With Unlocked bootloader magisk "works" but you can't update to magisk 18. It's broken for some reason. Only magisk 17 works.
Click to expand...
Click to collapse
Hi, iam facing the same issue - my mi9 is on Global MIUI 10.2 Stable | 10.2.15.0
I dont want to flash any other i want to stay on stock.. - because xiaomi.eu release has only miui 9?
Or am i wrong?
Cd993's suggestion is actually works, using the latest Canary build seem to have work for me
xdarkmario said:
Cd993's suggestion is actually works, using the latest Canary build seem to have work for me
Click to expand...
Click to collapse
Thanks! For me too
I have now a Stock mi9 with stock Recovery and magisk
Greets christoph
xdarkmario said:
Cd993's suggestion is actually works, using the latest Canary build seem to have work for me
Click to expand...
Click to collapse
-chrizz- said:
Thanks! For me too
I have now a Stock mi9 with stock Recovery and magisk
Greets christoph
Click to expand...
Click to collapse
Even the latest v19 works too
I have a problem. Yesterday in between transactions suddenly my Google pay card stopped working. When I tried to add it again - I got info about root or other modification to the system. SafetyNet check was pass! I installed magisk, and hidd Google pay. Still no go.
Can't add the card.
Any thoughts?
---------- Post added at 05:53 PM ---------- Previous post was at 05:08 PM ----------
Sadly my Google pay stopped working. I made a transfer and I tried to make another one after 10 minutes only to be rejected. I tried adding the card again only to fail with info about phone modification... SafetyNet test passed ok! I tried installing magisk (19) and hid some things. But that didn't helped..
Can't add new card.
brathaneq said:
I have a problem. Yesterday in between transactions suddenly my Google pay card stopped working. When I tried to add it again - I got info about root or other modification to the system. SafetyNet check was pass! I installed magisk, and hidd Google pay. Still no go.
Can't add the card.
Any thoughts?
---------- Post added at 05:53 PM ---------- Previous post was at 05:08 PM ----------
Sadly my Google pay stopped working. I made a transfer and I tried to make another one after 10 minutes only to be rejected. I tried adding the card again only to fail with info about phone modification... SafetyNet test passed ok! I tried installing magisk (19) and hid some things. But that didn't helped..
Can't add new card.
Click to expand...
Click to collapse
My tips: clear the data of Google pay/Google play services/nfc services, use magisk hide for Google play services, Google pay, reboot. Also ensure Secure Element Position is set to HCE Wallet.
Hope that works for you!
Which custom rom is best for redmi note 8 in ANDROID 11
Opinions are different from person to person. You should do a research on this subject then choose anything to your taste. Easier this way than asking someone. In this way you'll gain knowledge and you'll be able to provide tips and advises to others.
Anyway, you should stay away from the latest update to A11 from Xiaomi!!! The official update is garbage!!! I regret so much doing this step... lost some useful and basic functions. Looks like their devs are stupid really... or just hate their customers.
Just try whatever you thing is ok for you.
MadK9 said:
Opinions are different from person to person. You should do a research on this subject then choose anything to your taste. Easier this way than asking someone. In this way you'll gain knowledge and you'll be able to provide tips and advises to others.
Anyway, you should stay away from the latest update to A11 from Xiaomi!!! The official update is garbage!!! I regret so much doing this step... lost some useful and basic functions. Looks like their devs are stupid really... or just hate their customers.
Just try whatever you thing is ok for you.
Click to expand...
Click to collapse
You are absolutely right. Android 11 update is like a diseaster
rafat.mym said:
You are absolutely right. Android 11 update is like a diseaster
Click to expand...
Click to collapse
whats the problem? mine works fine and much faster
jjsan said:
whats the problem? mine works fine and much faster
Click to expand...
Click to collapse
There must be something that makes your device smooth... maybe rom variant? Locked bootloader??
Share us more details please.
MadK9 said:
There must be something that makes your device smooth... maybe rom variant? Locked bootloader??
Share us more details please.
Click to expand...
Click to collapse
Unlocked bootlader, rooted (magisk for payment and adaway)
Rom variant is
Miui 12.0.2 RCXEUXM
Full wipe after upading to 11
Thanx.
Well, I also have an unlocked bootloader, but no Magisk and EEA Rom... but did not tried factory reset after update.
I also tried to flash Magisk but had issues with bootloop when I patched boot image and I gave up...
MadK9 said:
Thanx.
Well, I also have an unlocked bootloader, but no Magisk and EEA Rom... but did not tried factory reset after update.
I also tried to flash Magisk but had issues with bootloop when I patched boot image and I gave up...
Click to expand...
Click to collapse
ive installed magisk via twrp (renaming .apk to .zip and flashing)
i've read many posts about wiping data after upgrade
jjsan said:
Unlocked bootlader, rooted (magisk for payment and adaway)
Rom variant is
Miui 12.0.2 RCXEUXM
Full wipe after upading to 11
Click to expand...
Click to collapse
My firend, how did you fix the payment (with magisk)?
Jendrooo said:
My firend, how did you fix the payment (with magisk)?
Click to expand...
Click to collapse
5 days ago something happened and its not working for now. waiting for solution. you can search for cts profile here in forum.
Jendrooo said:
My firend, how did you fix the payment (with magisk)?
Click to expand...
Click to collapse
Android Repository
MagiskHide Props Config v6.0.2-v132 (72) ⚡Magisk Module ⚡Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Set/reset MagiskHide sensitive prop values. Change any prop values easily, and set your own custom props. ⚡️GitHub Repository ⚙Changelog: - Fix problems when trying...
t.me
Remember : A11 sux !
loopypalm said:
Android Repository
MagiskHide Props Config v6.0.2-v132 (72) ⚡Magisk Module ⚡Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Set/reset MagiskHide sensitive prop values. Change any prop values easily, and set your own custom props. ⚡️GitHub Repository ⚙Changelog: - Fix problems when trying...
t.me
Remember : A11 sux !
Click to expand...
Click to collapse
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Jendrooo said:
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Click to expand...
Click to collapse
payment is not possible even on android 10 now.
i like 11 more than 10
Jendrooo said:
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Click to expand...
Click to collapse
1-none , -----> custom rom
2-IDK about payment things
jjsan said:
ive installed magisk via twrp (renaming .apk to .zip and flashing)
i've read many posts about wiping data after upgrade
Click to expand...
Click to collapse
Managed to install Magisk again (older version...), gain root and activated OTA survival on OrangeFox Recovery. So far, no issues but still afraid to try A11 again...
MadK9 said:
Managed to install Magisk again (older version...), gain root and activated OTA survival on OrangeFox Recovery. So far, no issues but still afraid to try A11 again...
Click to expand...
Click to collapse
what were your problems?
best thing for me is setting phone to airplane mode and it lets bt on if was connected before.
and really nice and smooth system
Well, there were several bugs on my device which I was unable to sort them out and decided to go back to 12.0.4.0...
Most annoying one was the impossibility to share a file from file manager by swiping up to a file... A message came on screen telling me there is no app to handle the action on my personal profile or something like that... Whaaat?
Another bug was the 3 fingers screenshot option... Not there... Just not working... Or dynamic icons... This function also was not available anymore...
I had no patience digging for bugs, was pissed and flash the goddamn device with the previous working version of android... Was so angry that I forgot to back up my data and lost all my personal files!!!
But of course, I did not factory reset my device after A11 update... This move, should not exist!!! Why this option is never applied on iphones??? Of course they're not perfect but update after update and never, ever had issues with the device and never had to factory reset it after a major update.... Jesus Christ, this android....
well. i understand that.
3 fingers screenshot can be activated from notifications.
funny thing is possibility to activate new notification centre. its not there. unless you look for it in search. funny thing - your phone has to be in english
i was android developer for 3 years and I like this system just because these possibilities.
im rooted. i can edit hosts file and make adblock perfect and simple.
but for normal people just for using phone there is iPhone. its simple and working.
or also samsung devices are quite good but pricey
About 3 fingers screenshoot: The option was enabled in my device, so even if it was active, the function did not worked!
start camera from lock screen was moved to double volume up but also not working. ist still beta