Database Users

[Q] Some questions on the current state of Verizon S5 hacking

So we just upgraded my wife's phone to the S5 on Verizon, and I've spent a few minutes going through the forum here and want to make sure I understand the current state of hacking on this phone, along with some other questions:
1) Root is possible - which will provide full access to the system for modification? (TiBu, Xposed, etc)?
2) No bootloader unlock - so standard custom ROM flashing is not available.
3) Ability to use "safestrap" - which as best as I can tell allows you to multi-boot custom ROMs by bootstrapping them from defined partitions in internal memory(?)
Some additional questions:
4) What are the drawbacks to safestrap booting compared to the standard custom ROM flash with a custom recovery? I mean, yes the method is different, but are there limitations on the functionality of custom ROMs flashed using this method? Does it detract from anything, or does it just mean a little more development must go into making a safestrap ROM?
5) I see some posts regarding SELinux being enabled in the kernel and no working fix yet. What actual impact does having SELinux in Enforcing mode have on the system for custom tweaking, etc?
6) Is it possible (and easy enough) to bring the phone back to complete stock if required. Either for return purposes, or because you deleted something and can't get OTA, etc.
7) In general, when all is said and done, what are the tangible areas which the S5 is locked to the extent that it truly diminishes the custom experience?
I am getting myself the M8, and spending most of my time figuring things out on there. My wife preferred the S5 and although she isn't a "power user" she may eventually want some things that the custom ROM can't provide. I'm hoping root and Xposed will be enough for those things - but we are still within our return window and if I deem the S5 just doesn't have the features, we may try something else....though it seems that most everything on Verizon is locked down except maybe the M8.
TIA

1) Root is possible - which will provide full access to the system for modification? (TiBu, Xposed, etc)?
Correct
2) No bootloader unlock - so standard custom ROM flashing is not available.
Correct
3) Ability to use "safestrap" - which as best as I can tell allows you to multi-boot custom ROMs by bootstrapping them from defined partitions in internal memory(?)
In essence, this is how we are loading custom ROMs. Technically you could use it for multiple ROMs, it seems like the consensus is to just load your custom ROM to the primary slot and not switch between multiple.
Some additional questions:
4) What are the drawbacks to safestrap booting compared to the standard custom ROM flash with a custom recovery? I mean, yes the method is different, but are there limitations on the functionality of custom ROMs flashed using this method? Does it detract from anything, or does it just mean a little more development must go into making a safestrap ROM?
The drawback is no custom kernels and no ROMs like CM or AOSP because of that.
6) Is it possible (and easy enough) to bring the phone back to complete stock if required. Either for return purposes, or because you deleted something and can't get OTA, etc.
Yes.
7) In general, when all is said and done, what are the tangible areas which the S5 is locked to the extent that it truly diminishes the custom experience?
Having a locked bootloader does limit the ROM choices in that we will only get Touchwiz-based options, but that isn't necessarily a huge deal.

jcollier said:
1) Root is possible - which will provide full access to the system for modification? (TiBu, Xposed, etc)?
Correct
2) No bootloader unlock - so standard custom ROM flashing is not available.
Correct
3) Ability to use "safestrap" - which as best as I can tell allows you to multi-boot custom ROMs by bootstrapping them from defined partitions in internal memory(?)
In essence, this is how we are loading custom ROMs. Technically you could use it for multiple ROMs, it seems like the consensus is to just load your custom ROM to the primary slot and not switch between multiple.
Some additional questions:
4) What are the drawbacks to safestrap booting compared to the standard custom ROM flash with a custom recovery? I mean, yes the method is different, but are there limitations on the functionality of custom ROMs flashed using this method? Does it detract from anything, or does it just mean a little more development must go into making a safestrap ROM?
The drawback is no custom kernels and no ROMs like CM or AOSP because of that.
6) Is it possible (and easy enough) to bring the phone back to complete stock if required. Either for return purposes, or because you deleted something and can't get OTA, etc.
Yes.
7) In general, when all is said and done, what are the tangible areas which the S5 is locked to the extent that it truly diminishes the custom experience?
Having a locked bootloader does limit the ROM choices in that we will only get Touchwiz-based options, but that isn't necessarily a huge deal.
Click to expand...
Click to collapse
So when using safestrap do you actually overwrite your main ROM in the slot, or you would have your main (factory) ROM loaded as normal, and then your custom in a separate slot? In effect, you could toggle between those if wanted? If so, I might load a custom for her to play with while not interrupting her normal usage. If she prefers it, we could eventually switch her over.
Where in the ROM/RAM are these custom ROMs actually placed and how big are they as in how do they affect the overall storage on your device if you opt to use one? I assume if you were to switch between more than one you would probably have to install all your apps, etc on each one.
What you said about touch-wiz only makes sense though I suppose it isn't that bad of a thing especially with all the proprietary goodies that Samsung has. I would expect that AOSP or CM mods might have problems recreating some of those features anyway.
Thanks again

TraderJack said:
So when using safestrap do you actually overwrite your main ROM in the slot, or you would have your main (factory) ROM loaded as normal, and then your custom in a separate slot? In effect, you could toggle between those if wanted? If so, I might load a custom for her to play with while not interrupting her normal usage. If she prefers it, we could eventually switch her over.
Where in the ROM/RAM are these custom ROMs actually placed and how big are they as in how do they affect the overall storage on your device if you opt to use one? I assume if you were to switch between more than one you would probably have to install all your apps, etc on each one.
What you said about touch-wiz only makes sense though I suppose it isn't that bad of a thing especially with all the proprietary goodies that Samsung has. I would expect that AOSP or CM mods might have problems recreating some of those features anyway.
Thanks again
Click to expand...
Click to collapse
I believe most people are just overwriting the main ROM and that is what I have done. I believe I recall issues when loading into the other slots.
I can't speak to the specific partition the custom ROMs are stored on when using other slots, sorry.

jcollier said:
I believe most people are just overwriting the main ROM and that is what I have done. I believe I recall issues when loading into the other slots.
I can't speak to the specific partition the custom ROMs are stored on when using other slots, sorry.
Click to expand...
Click to collapse
Last I knew, safestrap slots are virtual disks on the data partition. Safestrap hijacks the boot process and remaps /system, /data, et al to the appropriate virtual disk for that slot.
If you flash to the main slot, you would be overwriting the stock rom, which may have drastic consequences. I highly recommend flashing your custom rom to a slot other than the stock rom slot.
When I had my Droid Razr, kexec was used to hot boot a new kernel. Support for kexec may not be available for the S5 though, denying us custom kernels.

fcsager said:
Last I knew, safestrap slots are virtual disks on the data partition. Safestrap hijacks the boot process and remaps /system, /data, et al to the appropriate virtual disk for that slot.
If you flash to the main slot, you would be overwriting the stock rom, which may have drastic consequences. I highly recommend flashing your custom rom to a slot other than the stock rom slot.
When I had my Droid Razr, kexec was used to hot boot a new kernel. Support for kexec may not be available for the S5 though, denying us custom kernels.
Click to expand...
Click to collapse
From what I've read, safestrap with the s5 has problems with rom slots. Most people having small problems here and there are on a rom slot, and when they flash the rom to stock slot most of they're problems go away. I think this is mentioned in the safestrap thread itself.
From what I understand, make a backup of your stock rom, then format, then flash rom choice on stock slot. That way if something screws up you can restore your stick backup.

fcsager said:
If you flash to the main slot, you would be overwriting the stock rom, which may have drastic consequences. I highly recommend flashing your custom rom to a slot other than the stock rom slot.
Click to expand...
Click to collapse
SafeStrap on the S5 is very buggy if you are using a ROM slot other than stock and is HIGHLY recommended by all the devs to use stock slot.
There will be no drastic consequences if you decide to use your stock slot. Just make sure you make a backup of your stock ROM before wiping it. If, by chance, something does go wrong, you can always ODIN back to stock and start over.

So being that the common/accepted practice is to install a ROM to the stock slot (which I did) its probably a good idea to go back in and resize the ROM slot to the smallest size allowable correct? Were never going to be using it so why not? Can this be done easily without affecting the ROM installed in the stock slot?

chetqwerty said:
So being that the common/accepted practice is to install a ROM to the stock slot (which I did) its probably a good idea to go back in and resize the ROM slot to the smallest size allowable correct? Were never going to be using it so why not? Can this be done easily without affecting the ROM installed in the stock slot?
Click to expand...
Click to collapse
You could just delete all ROM slots and call it a day.

MrHyde03 said:
You could just delete all ROM slots and call it a day.
Click to expand...
Click to collapse
Wow, I over thought that a tad aay! lol of course you can do that, thanks man!

I would like the piggyback off this thread since I also just got my S5 a couple days ago. I have an OTA update pending, I'll attach a screenshot of my current version number here but should I not update it until I root it or is it still possible to root with the latest software? After I do root it should I lock the file that is used to detect new versions?

If you have not updated, do not update, use towelroot to root, then freeze SDM using Titanium Backup

Ok, did that, that was easy. Quick read through of that thread says he works for Google now and people who updated basically shot them selves in the foot for that method, is that about right?
What should I do after I root, download SuperSU? Anything else I should need?
EDIT: Oh, it already restored SuperSU from my app sync so I don't even need that.

I had the ne9 version and immediately odin flashed to NCG and rooted. Then I SU'd, busyboxed, then safestrapped. Flashed alliancerom over my system after testing it on a different partition. So now I have alliancerom running and have customized the heck out of it.

berfles said:
I would like the piggyback off this thread since I also just got my S5 a couple days ago. I have an OTA update pending, I'll attach a screenshot of my current version number here but should I not update it until I root it or is it still possible to root with the latest software? After I do root it should I lock the file that is used to detect new versions?
Click to expand...
Click to collapse
berfles said:
Ok, did that, that was easy. Quick read through of that thread says he works for Google now and people who updated basically shot them selves in the foot for that method, is that about right?
What should I do after I root, download SuperSU? Anything else I should need?
EDIT: Oh, it already restored SuperSU from my app sync so I don't even need that.
Click to expand...
Click to collapse
Yes, it's possible to root the latest firmware(NE9). See here: http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
And with any luck we should be able to keep root on any subsequent updates if not with the kernel swap method with other methods.

Need a little confirmation....

Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.

Oniyuri said:
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Click to expand...
Click to collapse
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone

Alessandro's said:
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Click to expand...
Click to collapse
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.

Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Then you install lollipop stock, make root , flash recovery and then flash cm13

Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.

GDReaper said:
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
Click to expand...
Click to collapse
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?

Oniyuri said:
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Click to expand...
Click to collapse
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.

GDReaper said:
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
Click to expand...
Click to collapse
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.

Oniyuri said:
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Click to expand...
Click to collapse
The only concern is about the warranty. Since your phone is some years old, I doubt that is an issue for you anymore.
By losing memory you mean losing data or actually losing storage space?
Either way, I haven't heard of anyone with such a problem around here.
Nor about somebody with a fried motherboard.
There might have been some unfortunate cases, but this is to be expected when you modify your device. There always is a risk of damage, it doesn't matter if it's by rooting or by flashing a ROM.

I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.

Oniyuri said:
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Click to expand...
Click to collapse
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.

GDReaper said:
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
Click to expand...
Click to collapse
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?

Oniyuri said:
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Click to expand...
Click to collapse
1) Is not mandatory, it's just recommended. The only exception is if your device is a Verizon or AT&T phone, then don't - and I repeat - don't update or you risk losing the possibility of any custom ROM flashing or rooting due to the locked bootloaders.
2) and 3) CWM and TWRP backups do not have cross-compatibility. If you backup with CWM you have to restore with CWM.

Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.

robcore said:
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
Click to expand...
Click to collapse
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.

Oniyuri said:
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Click to expand...
Click to collapse
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?

robcore said:
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
Click to expand...
Click to collapse
Well, so far, the chromecast is only plugged into my tv and basically did the setup by itself only for the google cast app on my phone to not recognize it when it said that it's ready to cast. I've ran out of things to do aside from going to the google forums (which I've already done). I'm starting to wonder if it's my phone that's causing all the issues.

File-Based Encryption (Direct Boot) & Root

Hello all! I turned on the Direct Boot File Based Encryption last night (I wanted to do a fresh install anyway)and this morning discovered a new TWRP version. In a moment of pure stupidity I flashed it and sideloaded SuperSU v2.76 which soft bricked my phone, leaving me pretty lonesome through my workday. My own fault for sure for not checking, but I noticed something odd.
Though TWRP installs fine and appears to work normally, upon closer inspection all the folders on the device were encrypted gibberish titles and were empty. So I'm guessing they're not playing nice. I've looked around a bit but haven't found any other info, does anyone know if there are plans to support this mode? Has anyone heard anything? Am I crazy?

Same thing happened to me.

Encryption like this will never work with custom recoveries. It is something you give up when you mod your device. It is not meant for rom flashers.

zelendel said:
Encryption like this will never work with custom recoveries. It is something you give up when you mod your device. It is not meant for rom flashers.
Click to expand...
Click to collapse
Is there no way to root a device that is using FBE then?

Has anyone gotten any sort of answer when it comes to FBE and root? I enabled it also and I don't want to run the risk of bricking my N6P. Does this mean that if we enable this setting we will forever be stuck with stock android? If this is the case how is it that they plan to root the new Pixel phones which will come with this enabled by default?

Aggro_Monkey3000 said:
Has anyone gotten any sort of answer when it comes to FBE and root? I enabled it also and I don't want to run the risk of bricking my N6P. Does this mean that if we enable this setting we will forever be stuck with stock android? If this is the case how is it that they plan to root the new Pixel phones which will come with this enabled by default?
Click to expand...
Click to collapse
The whole point is that they don't want it to be rooted. Google sees root for what it is. A security hole.

Root & Encryption on Nougat?

Is there any way to make this work?
Since CF-autoroot doesn't work in nougat, I dunno how to make this work..
I don't know if is even possible, because as soon as i flash TWRP I cannot encrypt it again..
anyone?

For now only way is to install TWRP + SuperSU then flash old recovery
Im not sure but for this process you dont need no-verity-opt-encrypt..
Im on 7.0 Nougat and waiting better way to root it, i dont want custom recovery and i hear when you install TWRP bootloop is granted in 50/50 attempts

Talentooman said:
For now only way is to install TWRP + SuperSU then flash old recovery
Im not sure but for this process you dont need no-verity-opt-encrypt..
Im on 7.0 Nougat and waiting better way to root it, i dont want custom recovery and i hear when you install TWRP bootloop is granted in 50/50 attempts
Click to expand...
Click to collapse
But you tried that method? (Flashing TWRP + SuperSU and then back stock recovery)
Crap... Nougat is really nice, but some basic stuff is missing for me... encryption and Xposed

insaned said:
But you tried that method? (Flashing TWRP + SuperSU and then back stock recovery)
Crap... Nougat is really nice, but some basic stuff is missing for me... encryption and Xposed
Click to expand...
Click to collapse
im really sad, so i install custom recovery, flash Nougat debloated rom with root preinstalled and now i lose my CSC, *#060# or any other code not working.. im now on 7.0 UK version stock firmware and UUID codes not working ..

Root and encryption aren't working right now. Chainfire (SuperSU Dev) and a few other users are trying to get it to work.
For the time being, the most you can do is use a ROM like Helios and pick the encryption option. You won't have root but you can flash mods to /system in TWRP
My current setup is
Helios
Stock Kernel
Encrypted
Dual Speaker Mod
Private Mode Works
S Health Works
AppLock Works
Android Pay Works
Banking Apps Work

Galactus said:
Root and encryption aren't working right now. Chainfire (SuperSU Dev) and a few other users are trying to get it to work.
For the time being, the most you can do is use a ROM like Helios and pick the encryption option. You won't have root but you can flash mods to /system in TWRP
My current setup is
Helios
Stock Kernel
Encrypted
Dual Speaker Mod
Private Mode Works
S Health Works
AppLock Works
Android Pay Works
Banking Apps Work
Click to expand...
Click to collapse
Well, It's an option... the most interesting mods that I used were with Xposed anyway, and for that the wait is going to be longer.
The device not encrypted is not very nice though... I guess eventually I just try it out meanwhile.
Thanks for the heads up @Galactus

Just out of curiosity, why do you guys "insist" on encryption? I still don't understand the repercussions of a decrypted device, let alone those of an encrypted device. I genuinely don't know. This is not a sarcastic or passive aggressive question!

nitrous² said:
Just out of curiosity, why do you guys "insist" on encryption? I still don't understand the repercussions of a decrypted device, let alone those of an encrypted device. I genuinely don't know. This is not a sarcastic or passive aggressive question!
Click to expand...
Click to collapse
Mainly data protection.
If my phone is stolen with encryption, once the thief turns the phone off that is it. The phone won't even fully load without my password. Sure, he can fully wipe the phone but this will also delete all of my data. Once reported stolen, it will simply be an expensive media player. Nougat also doesn't let you turn the phone off by using the power button unless you enter the phones password, so that helps using Android device manager or say Cerberus to locate the phone or enable it to play a loud alert
Without encryption. The thief can simply go into TWRP and take all the data

How about sd card encryption? Is this also not possible with rooted nougat? I just tried it and am stuck at the "checking sd card" message since hours. However the device is still working.

Have you rooted your phone yet?

Hello,
I've been meaning to root my phone for a while now but I have a couple of questions.
Firstly, how have your experiences been? I see a lot of threads where people have bricked their phones which makes me fearful of doing the same. Is it really that difficult to root and install a new rom on this phone? Are there any guides that worked best for you? Any suggestions?
Also, how difficult is it to return back to stock? I see a lot of issues with IMEI and broken WiFi and what not.
Finally, the reason why I wish to root now is because the warranty is voided and I am bored of stock. I do prefer using AdAway over adguard because it works seamlessly and also, I'm having facing issues with the earpiece volume. Mi seems to have turned it down a bit and it's pretty low right now and from what I remember, custom kernels were able to crank it up a while back. Is that still the case?
Any help would be appreciated. Thank you!

Ive rooted, unrooted, installed roms, and revert back to stock. So far, Ive only bricked my phone once when installing magisk (on oreo). Wifi issue is only present when you move from custom rom back to stock rom (sadly Ive ran into this and theres no way to fix it). IMEI issue is only present when youre downgrading from stock pie to oreo or nougat (which Ive also ran into, unfortunately). Unrooting is as easy as rooting, just flash the uninstaller zip, thats it. But however, DONT INSTALL TWRP ON PIE, youll get system is destroyed message (agian, Ive also ran into this, fml. Solved by flashing with mi flash). I hope you get the idea now.

what? i have twrp installed on pie (custom rom) and work like a charm!
i use cosmicdan twrp.

riccetto80 said:
what? i have twrp installed on pie (custom rom) and work like a charm!
i use cosmicdan twrp.
Click to expand...
Click to collapse
Oh sorry, I meant stock pie

WhatzIt2Ya said:
Ive rooted, unrooted, installed roms, and revert back to stock. So far, Ive only bricked my phone once when installing magisk (on oreo). Wifi issue is only present when you move from custom rom back to stock rom (sadly Ive ran into this and theres no way to fix it). IMEI issue is only present when youre downgrading from stock pie to oreo or nougat (which Ive also ran into, unfortunately). Unrooting is as easy as rooting, just flash the uninstaller zip, thats it. But however, DONT INSTALL TWRP ON PIE, youll get system is destroyed message (agian, Ive also ran into this, fml. Solved by flashing with mi flash). I hope you get the idea now.
Click to expand...
Click to collapse
Don't spread false truths. I have had pie custom ROM installed since it was available for our device and have never once had system is destroyed message. I think you mean you cannot flash twrp on STOCK pie, just hotboot it.
It has never been easier too root and flash custom roms.
Also if you ever want to go back to stock or may have to for any reason just stay with stock.
I don't see any need in going back to stock,custom roms are better. Imo.
Peace ✌?

cheffy11 said:
Don't spread false truths. I have had pie custom ROM installed since it was available for our device and have never once had system is destroyed message. I think you mean you cannot flash twrp on STOCK pie, just hotboot it.
It has never been easier too root and flash custom roms.
Also if you ever want to go back to stock or may have to for any reason just stay with stock.
I don't see any need in going back to stock,custom roms are better. Imo.
Peace ?
Click to expand...
Click to collapse
I tried some custom roms and decided to go back to stock.
In order to go back I flashed the stock zip uploaded here: https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
worked like a charm. Also I was able to flash magisk by hotbooting twrp.

cheffy11 said:
Don't spread false truths. I have had pie custom ROM installed since it was available for our device and have never once had system is destroyed message. I think you mean you cannot flash twrp on STOCK pie, just hotboot it.
It has never been easier too root and flash custom roms.
Also if you ever want to go back to stock or may have to for any reason just stay with stock.
I don't see any need in going back to stock,custom roms are better. Imo.
Peace ✌?
Click to expand...
Click to collapse
Open your eyes before commenting mate.

WhatzIt2Ya said:
Open your eyes before commenting mate.
Click to expand...
Click to collapse
Fair enough. I missed that. But stock is still whack. Custom all the way.

If you want to root, use custom ROMs. Don't use root with stock.