Related
I have a Nexus 6 as of 2 days ago and I have several questions about root.
Will I loose encryption?
Will I loose the ability to update my phone with new firmware through the handset > settings?
Can the phone be un-rooted in the event there is a warranty claim?
No, Yes, Yes
Thanks and can i root my nexus 6 and keep encryption? I heard that unlocking bootloader will wipe the device?
Milamber said:
I have a Nexus 6 as of 2 days ago and I have several questions about root.
Will I loose encryption?
Will I loose the ability to update my phone with new firmware through the handset > settings?
Can the phone be un-rooted in the event there is a warranty claim?
Click to expand...
Click to collapse
1. No
2. Yes
3. Yes
Unlocking the boot loader will wipe the device. You can have root and encryption.
Verstuurd vanaf mijn Nexus 6 met Tapatalk
I had a question about Nexus 6
I rooted it a few days ago with magisk seamless root I think it was and I went and changed the Rom from unholy 7.1 to pure Nexus and i reinstalled supersu ect and it says it's not rooted! Root checker even says it's not. Any ideals on how it could have happened. "I didn't do a factory reset at all by the way"
[email protected] said:
I had a question about Nexus 6
I rooted it a few days ago with magisk seamless root I think it was and I went and changed the Rom from unholy 7.1 to pure Nexus and i reinstalled supersu ect and it says it's not rooted! Root checker even says it's not. Any ideals on how it could have happened. "I didn't do a factory reset at all by the way"
Click to expand...
Click to collapse
When you install a new rom, it depends on the rom whether it is rooted; it doesn't preserve your old rooting.
Most roms come unrooted. Just flash the root of your choice from recovery (twrp). Note that Magisk and SuperSu are different rooting solutions; you need to select only one - most people prefer Magisk.
If you're using SuperSU, you must use the last beta release (2.82SR5). Also please understand that SuperSU, while the proper version should work for the last Pure Nexus release, it is not supported and development had ended.
The boot.img is what gets modified by root (either Magisk or SuperSU). If you attempt to install one, then the other, you must dirty flash the ROM in between. A failed installation of either will prevent the installation of the other one.
Not factory resetting is fine, but after changing ROMs, you must always clean flash - wipe system, data, dalvik and cache BEFORE flashing the new ROM.
When flashing the same ROM, you can dirty flash - wipe at least dalvik and cache.
Between different root methods, your dirty flash should include wiping system as well before reflashing (dirty flashing) the ROM. This is because there is an addon.d script that gets installed to system to help root survive ROM updates. This script will interfere with the installation of a different root package.
The addon.d script could also be removed from system instead, but that requires root, or adb with root access.
As long as data is not wiped, your user apps and settings will survive ( that's why it's a dirty flash).
Always clean flash between different ROM installations, such as unholy to Pure Nexus.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
When it comes to updating your device through the system/settings. A.) Nexus 6 will no longer get official updates. B.) Root will not interfere with official custom ROM updates i.e Lineage OS ota packages. C.) The only way to flash updates on a custom. ROM usually is through TWRP.
Rondeau79 said:
When it comes to updating your device through the system/settings. A.) Nexus 6 will no longer get official updates. B.) Root will not interfere with official custom ROM updates i.e Lineage OS ota packages. C.) The only way to flash updates on a custom. ROM usually is through TWRP.
Click to expand...
Click to collapse
Yeah it wouldn't update or anything. I ended up flashing it all stock and sold it lol I did the exact same thing to my Nexus 6p smh got a DU rom that is 8.1 like my nexus and got gapps 8.1 but went with nano. Could that be a issue or nah? Lineage os works fine but I don't care for the setup lol
[email protected] said:
Yeah it wouldn't update or anything. I ended up flashing it all stock and sold it lol I did the exact same thing to my Nexus 6p smh got a DU rom that is 8.1 like my nexus and got gapps 8.1 but went with nano. Could that be a issue or nah? Lineage os works fine but I don't care for the setup lol
Click to expand...
Click to collapse
Gapps have nothing to do with firmware updates and root. If you want stock updates on a device then move on to another handset. The Nexus line is done and will no longer be supported by Google. The Android OS as a whole will largely be discontinued eventually as well. Magisk is the only supported root function now as well. Move on to what works for you.
Rondeau79 said:
Gapps have nothing to do with firmware updates and root. If you want stock updates on a device then move on to another handset. The Nexus line is done and will no longer be supported by Google. The Android OS as a whole will largely be discontinued eventually as well. Magisk is the only supported root function now as well. Move on to what works for you.
Click to expand...
Click to collapse
Which phone would you suggest? I have thought about getting a different phone. Seen two pixel 2 on eBay that I'm about to buy. One has a broken screen supposedly and the other has a bad logic board
---------- Post added at 03:10 AM ---------- Previous post was at 03:04 AM ----------
runekock said:
When you install a new rom, it depends on the rom whether it is rooted; it doesn't preserve your old rooting.
Most roms come unrooted. Just flash the root of your choice from recovery (twrp). Note that Magisk and SuperSu are different rooting solutions; you need to select only one - most people prefer Magisk.
Click to expand...
Click to collapse
I hear where ur coming from...how can I tell the difference in a rooted and unrooted Rom? Sorry I'm really new to rooting phones and what not.
I know it worked in my Nexus 6 just fine and I rooted the phone before I installed
[email protected] said:
Which phone would you suggest? I have thought about getting a different phone. Seen two pixel 2 on eBay that I'm about to buy. One has a broken screen supposedly and the other has a bad logic board
---------- Post added at 03:10 AM ---------- Previous post was at 03:04 AM ----------
I hear where ur coming from...how can I tell the difference in a rooted and unrooted Rom? Sorry I'm really new to rooting phones and what not.
I know it worked in my Nexus 6 just fine and I rooted the phone before I installed
Click to expand...
Click to collapse
I have not looked into a new device for a while. I would suggest a one plus 5 or a mid range Moto device. Look into something easy to modify, ie. Unlocking the bootloader, root, and custom recovery. Browse XDA forums on different devices for development support and so forth.
As far as checking root. Google play store has various root check apps that you download and simply check for root. It will say rooted or not.
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.
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs
Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,
Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.
Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.
Hi! So a brand new MI 9 owner here wondering about a few things in regards to rooting the phone (without TWRP). My main concerns are, 1) is there still a waiting period to unlock the bootloader? 2) Does rooting cause some system apps to not work properly? For example in my previous phone the cost for rooting (or unlocking bootloader) was terrible camera quality.. And 3) can I still get regular system updates without having to manually flash a full rom?
Oh and a bonus question! Has anyone tried if there's any way to use Xperia keyboard on this phone? It's the only keyboard that hasn't made me want to go toss my phones in the river...
Not sure if there's any way to root mi9 without twrp, someone will hopefully correct if i'm wrong, but i've not heard of one - you need the advanced options twrp offers over stock recovery to flash magisk, but i may be wrong. Perhaps you may be able to extract ur boot img or something and inject magisk, so it's pre-rooted, but i don't know how to do that, sorry. Most peoples banking apps work in most places using magisk hide but i've read that some banks/regions require further work. Not heard of any reports of camera degradation tho.
Why don't you wanna flash twrp? Yes, there's a waiting period to unlock bl. Not sure about the keyboard, don't have it
reg66 said:
Not sure if there's any way to root mi9 without twrp, someone will hopefully correct if i'm wrong, but i've not heard of one - you need the advanced options twrp offers over stock recovery to flash magisk, but i may be wrong. Perhaps you may be able to extract ur boot img or something and inject magisk, so it's pre-rooted, but i don't know how to do that, sorry. Most peoples banking apps work in most places using magisk hide but i've read that some banks/regions require further work. Not heard of any reports of camera degradation tho.
Why don't you wanna flash twrp? Yes, there's a waiting period to unlock bl. Not sure about the keyboard, don't have it
Click to expand...
Click to collapse
Well this was at the top of the Mi 9 Guides, News & Discussion page here: [TUTO] Complete tutorial to root MI9 without TWRP (Keeps intact encryption of the MI9. Encryption is always good and I haven't needed TWRP much before so I figured that's the best option for me. Oh and no, there's no wait time anymore. Just downloaded the unlocker and it gave me the green light to go ahead. Bought the phone yesterday..
Kuunkulta said:
Well this was at the top of the Mi 9 Guides, News & Discussion page here: [TUTO] Complete tutorial to root MI9 without TWRP (Keeps intact encryption of the MI9. Encryption is always good and I haven't needed TWRP much before so I figured that's the best option for me. How do I find out how long of a wait I still have ahead?
Click to expand...
Click to collapse
Ah OK, hadn't seen that thread. Good luck with it all. Download Mi unlock tool and it'll tell you how long to wait, maybe 720 hours.. There is a thread for instant unlock, but it's only worked on a few cases
You definitely want to flash Magisk via TWRP, because you will need a few modules there that really improve the phone, are absolute must haves.
omgomg said:
You definitely want to flash Magisk via TWRP, because you will need a few modules there that really improve the phone, are absolute must haves.
Click to expand...
Click to collapse
Such as?
reg66 said:
Such as?
Click to expand...
Click to collapse
Such as bump audio bitrate when recording up to 6ch, 960kbs; Youtube Vanced, Netflix (yes, if you root it, you will need magiskhide or no Netflix), liboemcrypto disabler; Cloudflare DNS; Viper4Android (this one quite optional, but makes such a difference).
---------- Post added at 03:53 AM ---------- Previous post was at 03:52 AM ----------
Kuunkulta said:
Well this was at the top of the Mi 9 Guides, News & Discussion page here: [TUTO] Complete tutorial to root MI9 without TWRP (Keeps intact encryption of the MI9. Encryption is always good and I haven't needed TWRP much before so I figured that's the best option for me. Oh and no, there's no wait time anymore. Just downloaded the unlocker and it gave me the green light to go ahead. Bought the phone yesterday..
Click to expand...
Click to collapse
I don't know what's your doubt, but mauronofrio's TWRP keeps the encryption per default.
omgomg said:
Such as bump audio bitrate when recording up to 6ch, 960kbs; Youtube Vanced, Netflix (yes, if you root it, you will need magiskhide or no Netflix), liboemcrypto disabler; Cloudflare DNS; Viper4Android (this one quite optional, but makes such a difference).
---------- Post added at 03:53 AM ---------- Previous post was at 03:52 AM ----------
I don't know what's your doubt, but mauronofrio's TWRP keeps the encryption per default.
Click to expand...
Click to collapse
Really? If the encryption is preserved with it, I don't see any reason not to go TWRP. Can't believe I've missed that, I try to do my research before posting Thanks for the tip!
Yeah, encryption is on, I've never had my phone with a decrypted ROM. Using mauronofrio's TWRP -35 currently.
Hey guys, please help me out. Since Samsung has now released the Stable android 10 update for S9, please find a way to root it. I am not able to root nor install custom kernel ElementalX on it.
I'm waiting for that too. No point in installing Android 10 until root works for me.
same question.
Ideally without wiping data if at all possible
thanks
Matce said:
same question.
Ideally without wiping data if at all possible
thanks
Click to expand...
Click to collapse
I wouldn't recommend that on a main upgrade. It can give unwanted consequences. I always advocate doing a full reset on these.
---------- Post added at 09:49 AM ---------- Previous post was at 09:02 AM ----------
Oh, btw, for my part it has to be a Magisk or similar root, since any visible root prevents me from using many apps I need to have, like VIPPS (Norwegian money transfer app), mobile banking, Google Pay and so on.
Mastiff said:
I wouldn't recommend that on a main upgrade. It can give unwanted consequences. I always advocate doing a full reset on these.
---------- Post added at 09:49 AM ---------- Previous post was at 09:02 AM ----------
Oh, btw, for my part it has to be a Magisk or similar root, since any visible root prevents me from using many apps I need to have, like VIPPS (Norwegian money transfer app), mobile banking, Google Pay and so on.
Click to expand...
Click to collapse
Thats the new verify thing from samsung.
The part is, that the system mount point is after init process. The init part has a dynamic mounting part and that is the problem actually.
The recovery rooting is also not working, of part from mounting issue.
I have check the mounting part, with a rooted recovery. At the moment we can not mount the system partition rw.
One way is to find a way patch the init part....but the way is open.
I hope john can help us....
Android 10 root solution found. Installed alexndr rom based on stock android 10. Working flawlessly with ElementalX kernel. Super smooth & snappy. This rom comes preloaded with Magisk root 20.3 & all the unnecessary stuff removed. Just flash the rom in twrp. No problems in flashing without wipeing data/factory reset. Completely stock looking firmware. No extra app added. Please check it out if anyone wants root on Andorid 10. Links below.
Alexndr Rom : https://forum.xda-developers.com/ga...-development/rom-u1arc5-devbase-v5-2-t3764822
Elemantal X Custom kernel : https://forum.xda-developers.com/ga...lopment/kernel-elementalx-1-00-s9-s9-t3767753
harshkumar07 said:
Android 10 root solution found. Installed alexndr rom based on stock android 10. Working flawlessly with ElementalX kernel. Super smooth & snappy. This rom comes preloaded with Magisk root 20.3 & all the unnecessary stuff removed. Just flash the rom in twrp. No problems in flashing without wipeing data/factory reset. Completely stock looking firmware. No extra app added. Please check it out if anyone wants root on Andorid 10. Links below.
Alexndr Rom : https://forum.xda-developers.com/ga...-development/rom-u1arc5-devbase-v5-2-t3764822
Elemantal X Custom kernel : https://forum.xda-developers.com/ga...lopment/kernel-elementalx-1-00-s9-s9-t3767753
Click to expand...
Click to collapse
After this modification, is the system "/" partition read/write "rw" mountable?
I wouldn't call that a solution, I'm guessing that this ROM isn't available in Norwegian Telenor version.
harshkumar07 said:
Android 10 root solution found. Installed alexndr rom based on stock android 10. Working flawlessly with ElementalX kernel. Super smooth & snappy. This rom comes preloaded with Magisk root 20.3 & all the unnecessary stuff removed. Just flash the rom in twrp. No problems in flashing without wipeing data/factory reset. Completely stock looking firmware. No extra app added. Please check it out if anyone wants root on Andorid 10. Links below.
Alexndr Rom : https://forum.xda-developers.com/ga...-development/rom-u1arc5-devbase-v5-2-t3764822
Elemantal X Custom kernel : https://forum.xda-developers.com/ga...lopment/kernel-elementalx-1-00-s9-s9-t3767753
Click to expand...
Click to collapse
Hey I'm on stock Android 10 already. How do I go about this? Flash TWRP and then this ROM? That's it?
TheXGX said:
Hey I'm on stock Android 10 already. How do I go about this? Flash TWRP and then this ROM? That's it?
Click to expand...
Click to collapse
Yes. Correct. 1st TWRP, then this rom. If you want to use any Custom Kernel like White Wolf or ElementalX, flash custom kernel after flashing the rom, then Magisk after it.
https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974
Read carefully.
Caveat is that if you delete system apps you'll bootloop on restart