Related
http://imgur.com/7mxqR4v
I want to set my system as rw but it fails everyway i do it. I tried Adb Shell but it doesnt work even though no error appears after entering in the code line. Ive tried the google play store app to enable rw for system, but it also does not work. After each of these steps i attempt to move an apk to system/app to check if its working. But it fails everytime. Also, when i attempt to use the rooting too in es explorer, it says my device is not compatible or needs root. Although titanium back up and battery calibrator, both which requires root. Work pefectly fine. I have supersu 2.7.1 on a Galaxy S5 g900t 5.1.1
Have you actually gone through the rooting process? everything I've just read indicates you haven't, and you don't actually tell us you have done so. Some of the functions in the apps you mention don't require access to root, so they may *appear* to work correctly.
I use SD Maid on my rooted phone, but I can also use it on my kids unrooted tablets....The same for root explorer....
The only difference is that some of the processes in these apps don't work on my kids tablets.....
Simply installing SuperSU from the playstore will not give you root access.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Have you actually gone through the rooting process? everything I've just read indicates you haven't, and you don't actually tell us you have done so. Some of the functions in the apps you mention don't require access to root, so they may *appear* to work correctly.
I use SD Maid on my rooted phone, but I can also use it on my kids unrooted tablets....The same for root explorer....
The only difference is that some of the processes in these apps don't work on my kids tablets.....
Simply installing SuperSU from the playstore will not give you root access.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
"Although titanium back up and battery calibrator, both which requires root. Work perfectly fine"
SuperSu 2.7.1 is not compatible with Galaxy S5 5.1.1 Stock
Frankie_Xenon said:
"Although titanium back up and battery calibrator, both which requires root. Work perfectly fine"
SuperSu 2.7.1 is not compatible with Galaxy S5 5.1.1 Stock
Click to expand...
Click to collapse
It appears you've answered your own question then.....One of those cases where a little prior research would have prevented the need to start a thread here on XDA.....I guess you live and learn....
http://i.imgur.com/rVnFwJM.jpg
Hello everyone,
My Moto X Pure edition is on the way on the mail. I'm already excited to root it and get twrp on it. However, I believe the phone will come with android lollipop installed, and I should get an option for an OTA update for android 6.0.
My question is: Should I root my phone and install twrp BEFORE receiving the update, or after? I plan to use WinDroid Toolkit to root my phone and install twrp (seems to be the easiest way) so have any of you done it while having 6.0 already installed?
Your phone will most likely arrive with 6.0 pre-installed on it. You can't take an OTA with TWRP installed. I can't answer the WinDroid question.
Edit: It will most likely come with 6.0 already assuming you purchased it from Motorola.
quakeaz said:
Your phone will most likely arrive with 6.0 pre-installed on it. You can't take an OTA with TWRP installed. I can't answer the WinDroid question.
Edit: It will most likely come with 6.0 already assuming you purchased it from Motorola.
Click to expand...
Click to collapse
Thanks a lot for your help! It's good that the phone will most likely come with MM. Does Motorola also offer an OTA update to 6.0.1?
I wanted to flash a pre-rooted stock-based ROM because I thought it would be easier to get root. Although, my preference really would be to get the stock update, then just root that. The only reason I wanted to flash an already rooted ROM was because it seems kind of tricky to root it haha. Is the systemless root by ivcarlos the easiest way to root MM? Or have you perhaps found another way to root it on MM?
Additionally, just to make sure before I go on with anything: I should first let the clean phone upgrade to android 6.0.1, AFTER that I should unlock the bootloader, followed by installing TWRP and root, correct? @vertigo_2_20
Thank you for any help you can give me!
Henryy97 said:
Thanks a lot for your help! It's good that the phone will most likely come with MM. Does Motorola also offer an OTA update to 6.0.1?
I wanted to flash a pre-rooted stock-based ROM because I thought it would be easier to get root. Although, my preference really would be to get the stock update, then just root that. The only reason I wanted to flash an already rooted ROM was because it seems kind of tricky to root it haha. Is the systemless root by ivcarlos the easiest way to root MM? Or have you perhaps found another way to root it on MM?
Additionally, just to make sure before I go on with anything: I should first let the clean phone upgrade to android 6.0.1, AFTER that I should unlock the bootloader, followed by installing TWRP and root, correct? @vertigo_2_20
Thank you for any help you can give me!
Click to expand...
Click to collapse
IIRC, that's how I did it (OTA 6.0.1 > unlock bootloader > flash TWRP > root), though I did miss some things along the way that I only found out about after the fact, so I've included warnings about those thing here. Before I rooted, I read the following (and a LOT more, but these are the primary ones I based how I did it on):
ivcarlos' method, which you mentioned
And this, which is what I followed for rooting, though I don't remember why. I also had to use 2.62-3 as mentioned in the instructions vs 2.65 which is mentioned at the end as verified working, since it didn't work for me.
I ran across this as well, probably when 2.65 didn't work, and there's some good tidbits in there, worth reading through.
I also found this, but only after I finished rooting with the other method, and I didn't have the time to mess with it. I don't know enough to say whether it's really a better method or not, but something worth checking out if you have the time.
Just make sure you backup anything you want to keep (phone log, texts, pictures, etc) before unlocking the bootloader. I recommend SMS Backup & Restore with Titanium Backup as a secondary backup. Then, use fastboot to back up your recovery before flashing TWRP (I didn't know to do this until too late). Also, make sure you back up your /system and /boot partitions (don't need /data, since you're dealing with a freshly wiped phone from unlocking the bootloader, so nothing there to back up) with TWRP (and store the backups on the external SD card and/or your computer) as soon as you get TWRP flashed, before you do anything else.
Remember, anything you do that modifies /system can potentially break the "systemless" aspect of this root, thereby breaking Android Pay as well as the ability to receive OTA updates. Examples of things that might do this are AdAway (there's apparently a systemless file that needs to be flashed before installing it, which I didn't realize until too late, so mine may be broken already) and battery apps like GSam and BetterBatteryStats. I've yet to get an answer on if these really do break it, though. One that definitely will is Xposed, but I just found there's a systemless version, so when I get time I plan on trying that out. I think even if you do break it you can just a) reflash your backup (/recovery, /boot, & /system) then take an OTA and reflash TWRP and re-root, or b) flash the updated partitions from the OTA then reflash recovery and re-root. Of course, any of those things that changed /system (AdAway, Xposed, battery apps, etc), will probably be broken by this, and I believe they're supposed to be uninstalled first and reinstalled after.
I wouldn't doubt if I've screwed something up, so hopefully somebody can correct me on anything I did, as well as provide more information regarding the breaking of systemless.
vertigo_2_20 said:
IIRC, that's how I did it (OTA 6.0.1 > unlock bootloader > flash TWRP > root), though I did miss some things along the way that I only found out about after the fact, so I've included warnings about those thing here. Before I rooted, I read the following (and a LOT more, but these are the primary ones I based how I did it on):
ivcarlos' method, which you mentioned
And this, which is what I followed for rooting, though I don't remember why. I also had to use 2.62-3 as mentioned in the instructions vs 2.65 which is mentioned at the end as verified working, since it didn't work for me.
I ran across this as well, probably when 2.65 didn't work, and there's some good tidbits in there, worth reading through.
I also found this, but only after I finished rooting with the other method, and I didn't have the time to mess with it. I don't know enough to say whether it's really a better method or not, but something worth checking out if you have the time.
Just make sure you backup anything you want to keep (phone log, texts, pictures, etc) before unlocking the bootloader. I recommend SMS Backup & Restore with Titanium Backup as a secondary backup. Then, use fastboot to back up your recovery before flashing TWRP (I didn't know to do this until too late). Also, make sure you back up your /system and /boot partitions (don't need /data, since you're dealing with a freshly wiped phone from unlocking the bootloader, so nothing there to back up) with TWRP (and store the backups on the external SD card and/or your computer) as soon as you get TWRP flashed, before you do anything else.
Remember, anything you do that modifies /system can potentially break the "systemless" aspect of this root, thereby breaking Android Pay as well as the ability to receive OTA updates. Examples of things that might do this are AdAway (there's apparently a systemless file that needs to be flashed before installing it, which I didn't realize until too late, so mine may be broken already) and battery apps like GSam and BetterBatteryStats. I've yet to get an answer on if these really do break it, though. One that definitely will is Xposed, but I just found there's a systemless version, so when I get time I plan on trying that out. I think even if you do break it you can just a) reflash your backup (/recovery, /boot, & /system) then take an OTA and reflash TWRP and re-root, or b) flash the updated partitions from the OTA then reflash recovery and re-root. Of course, any of those things that changed /system (AdAway, Xposed, battery apps, etc), will probably be broken by this, and I believe they're supposed to be uninstalled first and reinstalled after.
I wouldn't doubt if I've screwed something up, so hopefully somebody can correct me on anything I did, as well as provide more information regarding the breaking of systemless.
Click to expand...
Click to collapse
Thank you for your reply! I'll read the links you sent me, although from what I can see the "root done right" is for the nexus 6, and if it works for the moto x pure it doesn't seem to be overall that much beneficial over the systemless root.
What exactly is the effect of breaking the "systemless" aspect of the root? For example, if I install AdAway, what will happen? I didn't really get that from your post.
Perhaps after all this process, I'll write a how-to guide, heh
So according to your experience, SUPERSU 2.62-3 is the adequate version to use for android 6.0.1?
Thanks again!
Henryy97 said:
Thank you for your reply! I'll read the links you sent me, although from what I can see the "root done right" is for the nexus 6, and if it works for the moto x pure it doesn't seem to be overall that much beneficial over the systemless root.
What exactly is the effect of breaking the "systemless" aspect of the root? For example, if I install AdAway, what will happen? I didn't really get that from your post.
Perhaps after all this process, I'll write a how-to guide, heh
So according to your experience, SUPERSU 2.62-3 is the adequate version to use for android 6.0.1?
Thanks again!
Click to expand...
Click to collapse
My understanding is that breaking it will render Android Pay inoperable and will make it so you can't take an OTA, though as I mentioned, it seems you still can by reverting back, it's just a LOT more work. But again, as I said, I'm not completely sure and I haven't been able to get an answer.
As for the supersu version, it doesn't really matter, because you'll just update it once you're rooted and booted into the OS. I just found that, despite what that post said, 2.65 did not work for me, so I had to flash 2.62-3 which did. Not a big deal, was just a little frustrating and scary when 2.65 didn't work because I was worried that I broke something and that the method wasn't going to work.
Edit: Good catch BTW on the link having to do with the Nexus. I didn't even look at what sub-forum it was in. At least it's one less thing to worry about for now, though I do hope it spreads to more devices, because we could always use more, not to mention better (assuming it is) ways of doing things.
vertigo_2_20 said:
My understanding is that breaking it will render Android Pay inoperable and will make it so you can't take an OTA, though as I mentioned, it seems you still can by reverting back, it's just a LOT more work. But again, as I said, I'm not completely sure and I haven't been able to get an answer.
As for the supersu version, it doesn't really matter, because you'll just update it once you're rooted and booted into the OS. I just found that, despite what that post said, 2.65 did not work for me, so I had to flash 2.62-3 which did. Not a big deal, was just a little frustrating and scary when 2.65 didn't work because I was worried that I broke something and that the method wasn't going to work.
Edit: Good catch BTW on the link having to do with the Nexus. I didn't even look at what sub-forum it was in. At least it's one less thing to worry about for now, though I do hope it spreads to more devices, because we could always use more, not to mention better (assuming it is) ways of doing things.
Click to expand...
Click to collapse
Thanks. I am aware that you can revert back to lollipop, and do the update from there whenever you want to update to a newer OTA MM update. However, my real question is, what does it mean to break the systemless aspect? I know that it will prevent further OTA updates, but will xposed work as it should, etc? If I am rooting my device, it's really to get xposed. So, if it means that I must revert to an unrooted stock rom everytime I wanna update, then so be it. I just want to make sure that breaking the systemless root aspect will not make the ROM unstable. Will it?
Henryy97 said:
Thanks. I am aware that you can revert back to lollipop, and do the update from there whenever you want to update to a newer OTA MM update. However, my real question is, what does it mean to break the systemless aspect? I know that it will prevent further OTA updates, but will xposed work as it should, etc? If I am rooting my device, it's really to get xposed. So, if it means that I must revert to an unrooted stock rom everytime I wanna update, then so be it. I just want to make sure that breaking the systemless root aspect will not make the ROM unstable. Will it?
Click to expand...
Click to collapse
I think you'll find all the info you're looking for and more in those links. But in summary, as I said, AFAIK the only consequence is breaking OTAs. It does not prevent you from using xposed, rather xposed is one of the things that breaks it. Systemless is so called because it roots without affecting the /system partition, therefore preventing the breaking of Android Pay and allowing OTAs. Once /system is modified (unclear if at all or just beyond a point), these two will no longer function. So if you "break" the systemless root by doing stuff that modifies /system (i.e. xposed, etc), you basically now have a standard (non-systemless) root, which simply negates the benefits it provides. But as far as I could tell, systemless is the only option anyway, so you just do it since it works and it's easy, then you either are careful not to break it if Pay/OTAs are important to you, or if you don't care about those then you just do whatever you want just as if you were rooted in the traditional way. But as I said, once I get the time, I plan to try out the systemless xposed, though it may not matter since I might have already broken it, but may as well, and maybe it'll mean not having to uninstall it when it comes time to take an OTA. If you play with it and figure it out, let me know.
vertigo_2_20 said:
I think you'll find all the info you're looking for and more in those links. But in summary, as I said, AFAIK the only consequence is breaking OTAs. It does not prevent you from using xposed, rather xposed is one of the things that breaks it. Systemless is so called because it roots without affecting the /system partition, therefore preventing the breaking of Android Pay and allowing OTAs. Once /system is modified (unclear if at all or just beyond a point), these two will no longer function. So if you "break" the systemless root by doing stuff that modifies /system (i.e. xposed, etc), you basically now have a standard (non-systemless) root, which simply negates the benefits it provides. But as far as I could tell, systemless is the only option anyway, so you just do it since it works and it's easy, then you either are careful not to break it if Pay/OTAs are important to you, or if you don't care about those then you just do whatever you want just as if you were rooted in the traditional way. But as I said, once I get the time, I plan to try out the systemless xposed, though it may not matter since I might have already broken it, but may as well, and maybe it'll mean not having to uninstall it when it comes time to take an OTA. If you play with it and figure it out, let me know.
Click to expand...
Click to collapse
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Henryy97 said:
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Click to expand...
Click to collapse
I bought my phone ~5-6 months ago. When I got it, the MM update was waiting (released late last year). Probably ~2 months later, another update came through. Since then, nothing. So it looks like probably 3 maybe 4 a year. I'd rather be rooted with all the benefits than get a small update, though I'd really rather have both.
6.0.1 is not out yet although there is a reteu version posted which works great. Rooting is as simple flashing su 2.62-3 with twrp.
lafester said:
6.0.1 is not out yet although there is a reteu version posted which works great. Rooting is as simple flashing su 2.62-3 with twrp.
Click to expand...
Click to collapse
I'll check it out. Do you mind sharing the link to that version just in case? I am very confused now though, because @vertigo_2_20 says he has 6.0.1, and you say you didn't get it. Perhaps location matters? Can you elaborate a little bit more?
And actually, I've just realized: I think I was looking at too many outdated posts perhaps with all the complicated root procedures such as the one by ivcarlos. The guide that amit.lohar made is very simple which is the one vertigo kindly shared in this OP. One final question @vertigo_2_20 (sorry for so many questions). Does the method by amit.lohar work for 6.0 anddd 6.0.1? I would assume so since they're pretty much very similar. What is your take on this?
I assumed I was on 6.0.1 because I received a system update after being on MM, so I don't know what else it could be. Though it does just say 6.0 in settings. Regardless, I only did it a few weeks ago, so if you're fully updated, you'll be the same as what I was. Even if not, I would think it wouldn't matter. As long as you do a back up before messing with things, worse case scenario is you screw something up and restore the backup.
Henryy97 said:
I'll check it out. Do you mind sharing the link to that version just in case? I am very confused now though, because @vertigo_2_20 says he has 6.0.1, and you say you didn't get it. Perhaps location matters? Can you elaborate a little bit more?
And actually, I've just realized: I think I was looking at too many outdated posts perhaps with all the complicated root procedures such as the one by ivcarlos. The guide that amit.lohar made is very simple which is the one vertigo kindly shared in this OP. One final question @vertigo_2_20 (sorry for so many questions). Does the method by amit.lohar work for 6.0 anddd 6.0.1? I would assume so since they're pretty much very similar. What is your take on this?
Click to expand...
Click to collapse
No I don't get links for people... this forum is small and easy to read. Dev section has one pre loaded with franken and there are two threads in general.
Henryy97 said:
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Click to expand...
Click to collapse
If receiving the OTA updates is something you really want, systemless root will allow you to get them with a lot less effort. The trick is knowing which of the apps that require root privileges will end up modifying your system. Avoid the ones that will and you can enjoy root with less work to get updates. If the only root required apps you are interested in modifies the system, then it will be a matter of what you value more.
Sent from my awesome phone!
That reminds me of another thing I haven't yet figured out. If /system is modified, I'm assuming the OTA will still show up and just won't install, but I wonder if it won't even show up anymore. Anyone know?
aybarrap1 said:
If receiving the OTA updates is something you really want, systemless root will allow you to get them with a lot less effort. The trick is knowing which of the apps that require root privileges will end up modifying your system. Avoid the ones that will and you can enjoy root with less work to get updates. If the only root required apps you are interested in modifies the system, then it will be a matter of what you value more.
Sent from my awesome phone!
Click to expand...
Click to collapse
Ahhh! I guess I'll just flash ROMS to update my phone then because I need my xposed Besides, after 6.0, if we want root, we can only get the systemless one anyway, right?
Also, I did not quite understand something about systemless root. If the root is 'systemless', then how can apps still edit the system? I've read up that after a memory wipe, the root will actually go away but what happens if I have apps that already modified the system? I just don't quite get how the apps can get into the system and modify it, if the root itself cannot do that because it is systemless. Am I getting the wrong idea here? I've read, and read, and read. I can't find an answer to that :/ According to what you have said though, if I were to get an app that modifies the system, then it would essentially *break* the systemless aspect of it, right? Therefore, it just becomes a normal root?
I feel like I'm going in circles now so I hope someone will be able to explain this for me or just point me in the right direction!
Systemless root does not mean root doesn't have access to /system, it simply means a way of gaining root access without modifying the /system partition, because if you gain root with the old methods, which DO modify /system, it breaks Android Pay and OTAs. Root still has access to modify system, hence why you have to be careful in installing apps, xposed, etc, because if they have root access, they can modify it, and if they do, your systemless root just became useless. The whole point is to NOT modify it so as to keep those certain functions intact, but it doesn't prevent you from doing so after gaining root.
vertigo_2_20 said:
Systemless root does not mean root doesn't have access to /system, it simply means a way of gaining root access without modifying the /system partition, because if you gain root with the old methods, which DO modify /system, it breaks Android Pay and OTAs. Root still has access to modify system, hence why you have to be careful in installing apps, xposed, etc, because if they have root access, they can modify it, and if they do, your systemless root just became useless. The whole point is to NOT modify it so as to keep those certain functions intact, but it doesn't prevent you from doing so after gaining root.
Click to expand...
Click to collapse
My experience was rooting 5.1.1 on the new phone. I backed up at every stage. I tried a few roms, no big deal. I liked 5.1.1 better due to micro sd card usage. I stupidly allowed the OTA to attempt to install. I knew it would fail but hoped it would stop nagging. The result I did not expect was phone continually rebooting on its own, trying to complete the update. After it completed the reboot it would start to shut down and begin the reboot process again. I restored a backup and froze the Motorola Update app with Titanium Backup. Problem solved. Don't do what I did!
Why would you want to stay on L? M is so much better. Between Doze and permission control, you'll have better battery life and more privacy and security. Not to mention the increased security from having more up-to-date software. I'd recommend just taking the update.
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
Was wondering about this too. Not entirely confident about what things to reflash in case things go wrong otherwise wouldve tried this.
So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?
reddrago said:
So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?
Click to expand...
Click to collapse
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...
tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.
piskr said:
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.
Click to expand...
Click to collapse
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?
tdgillihan said:
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?
Click to expand...
Click to collapse
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.
ultramag69 said:
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...
Click to expand...
Click to collapse
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.
piskr said:
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.
Click to expand...
Click to collapse
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.
piskr said:
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.
Click to expand...
Click to collapse
If you're running a custom ROM it may or may not work. Some are saying it does and others not. But if we're talking about the A7 here that'll be stock for now.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...
ultramag69 said:
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...
Click to expand...
Click to collapse
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.
tdgillihan said:
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Don't know , I just downloaded the root manager Tenfars recommended from play store...
It works fine...
Are there any new reports on this subject? I have been able to successfully install Magisk and PHH SU on a Nexus 6P , but using the identical procedure on my Axon 7 (U) does not work. I am puzzled.
Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.
lokissmile said:
Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.
Click to expand...
Click to collapse
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?
lokissmile said:
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?
Click to expand...
Click to collapse
that's my thought too, since magisk seems not to create a log in /cache as it should and doesn't reaveal itself via logcat it looks like it doesn't realy get executed.
The guys in the common magisk were not realy able to help, guess we have to dig more into the init.rc script / boot.img patch. But might be that it get's fixed with v7 anyway, hope @topjohnwu is able to get it done quickly (or maybe has some ideas he how to debug it more, i didn't get an answer from him in the common, probably way too crowded magisk thread - goddamn pokemongo!)
Subscribing. Would like to get this working as well.
Edit: I've gone ahead and opened up a thread so it is easy to find: http://forum.xda-developers.com/axon-7/how-to/guide-installing-magisk-systemless-phhs-t3524270
We're up to Magisk V9 now and it still doesn't work. I'm almost certain it has to do with the execution of the patched boot.img, due to the write-protected /system partition. I finally got it working by using the the method in the guide I posted.
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Great job keep us posted
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
I think you would need a boot.img that disables it. Or you can disable encryption manually and erase all data to keep it disabled.
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
@jcadduono can help you to have a perfect job about TWRP ...
Ask him on irc ...
Backup failed because /data cannot be mounted, which suggests a mismatch twixt TWRP and device. Decided to push on and try to root. This failed, so that stock firmware had to be installed. I've hacked a number of phones and tabs here, so I was itching to see what could be done with existing N7 mods. Now I know.
It looks as though we need recovery etc specific to FE. Not sure we will have the numbers for it, though. If anyone has any ideas...
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
Your a brave man for trying this and the first to do so on here so thank you!.
As for the encryption on all the last few sammy devices ive had/have including the original Note 7 once you flash twrp you have to format data in twrp (not wipe mind you...format) to remove encryption.
We also had to then flash a zip to deal with dm verity but now SU does that anyway and also keeps the device decrypted when you reboot.
Id hazard a guess and say if you formatted and flashed SU this might actually work.
Now that we know flashing twrp (which was my main worry) and then odin stock without any issues this just got alot less risky.
sent from my Note FE, S8 plus, S7 edge or S6
Well I'm traveling now and will give this a go when I return home. Question: does DM Verity and Magic's or SU root require a a Note FR boot image to work or can they simply patch the boot image?
force70 said:
Your a brave man for trying this and the first to do so on here so thank you!.
As for the encryption on all the last few sammy devices ive had/have including the original Note 7 once you flash twrp you have to format data in twrp (not wipe mind you...format) to remove encryption.
We also had to then flash a zip to deal with dm verity but now SU does that anyway and also keeps the device decrypted when you reboot.
Id hazard a guess and say if you formatted and flashed SU this might actually work.
Now that we know flashing twrp (which was my main worry) and then odin stock without any issues this just got alot less risky.
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
Ah, I followed directions I found on the N7 forum, from which I assumed that SU would do the encryption. This is the first time I have come up against this barrier. I was resigned to possibly not having root, but from what you say I now think we might well manage it.
I've had a number of narrow shaves with various devices, so I felt that I could find my way out of any difficulty I encountered hacking the FE (maybe just fool's luck) . While cortez.i will try it at some stage, I am tempted to dive back in and see what happens.
Incidentally, sammobile didn't have the K variant firmware (may have now). I found it through google on a vietnamese site.
Just found this comprehensive guide to removing dm-verity:
http://www.theandroidsoul.com/disable-dm-verity-forced-encryption-galaxy-note-7/
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
zamzenos said:
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
Click to expand...
Click to collapse
You are THE MAN !!!!
WOOOOOOOOOO
wolfgart said:
You are THE MAN !!!!
WOOOOOOOOOO
Click to expand...
Click to collapse
I second that!
You shoukd be able to freeze security log agent with TIBU or package disabler pro to get rid of that message
force70 said:
I second that!
You shoukd be able to freeze security log agent with TIBU or package disabler pro to get rid of that message
Click to expand...
Click to collapse
I uninstalled the log agent with Titanium, ripped out all the Knox, still getting that message. I think I'll backup progress so far and restart FE from within the warning message and see what happens...**
Thank you both for the kudos. But some work still to be done. I'm finding some apps won't start - unfortunately some of them important. It's OK for now - I'm not using the FE yet - but need to get some real benefits from root, otherwise it's back to stock with Adhell (tho' I'd say sammy will spike that soon). Maybe folk with more tech xp than I have can work out what's wrong here.
**Restart from within Security boots into Recovery - in this case TWRP. Looks like a response to the decrypted state, and is set off by any root level action. Can we get rid of this?
zamzenos said:
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
Click to expand...
Click to collapse
which root package did you use, Magix or SU and did you have to use no verity disable zip?
EDIT: Nevermind, i'm rooted with SuperSU. have a 4 hour plane ride home so i'll have plenty time to checkout root before i get home..
cortez.i said:
which root package did you use, Magix or SU and did you have to use no verity disable zip?
EDIT: Nevermind, i'm rooted with SuperSU. have a 4 hour plane ride home so i'll have plenty time to checkout root before i get home..
Click to expand...
Click to collapse
Just curious if Knox is now tripped,by using SU ?
For myself,I'm not too worried about it either way,but,those interested in root may want to know,for future Samsung Pay use/possible resale value loss due to Knox 0x1/etc....
KOLIOSIS said:
Just curious if Knox is now tripped,by using SU ?
For myself,I'm not too worried about it either way,but,those interested in root may want to know,for future Samsung Pay use/possible resale value loss due to Knox 0x1/etc....
Click to expand...
Click to collapse
Yes sir as soon as you flash twrp its tripped.
And we need twrp for SU so no way around it.
sent from my Note FE, S8 plus, S7 edge or S6
force70 said:
Yes sir as soon as you flash twrp its tripped.
And we need twrp for SU so no way around it.
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
I figured that much hadn't changed since I last rooted/ROM'd a Samsung device,thanks for confirming. :good:
Again,for myself,it's not much of an issue,I plan on keeping this phone for the long haul (at least 1-2 yrs) & loss of Samsung Pay/Android Pay is of no consequence to me.
KOLIOSIS said:
I figured that much hadn't changed since I last rooted/ROM'd a Samsung device,thanks for confirming. :good:
Again,for myself,it's not much of an issue,I plan on keeping this phone for the long haul (at least 1-2 yrs) & loss of Samsung Pay/Android Pay is of no consequence to me.
Click to expand...
Click to collapse
Ive never cared about knox either....and this phone I will keep until it dies or I do lol
force70 said:
Ive never cared about knox either....and this phone I will keep until it dies or I do lol
Click to expand...
Click to collapse
+1
LMFAO,let's hope for the former................... :highfive:
so... after renaming SecurityLogAgent.apk from TWRP, i've had no problems running root apps, modifying build.prop, etc. google Adaway Vesion 3.2 and install this version and it will configure hosts files without issue (at least on my device). will continue testing and report findings should things changes. thanks @zamzenos for risking your device to confirm that the Note 7 version of TWRP is working.
cortez.i said:
so... after renaming SecurityLogAgent.apk from TWRP, i've had no problems running root apps, modifying build.prop, etc. google Adaway Vesion 3.2 and install this version and it will configure hosts files without issue (at least on my device). will continue testing and report findings should things changes. thanks @zamzenos for risking your device to confirm that the Note 7 version of TWRP is working.
Click to expand...
Click to collapse
The Adaway update worked. Thanks for that. I followed the N7 forum guide, except that I formatted data using TWRP, and used SU as advised. I uninstalled the log agent with Titanium (and as much of Knox as I could find). I no longer get security notifications, but something is still being tripped by any root activity. The apps that won't start don't require root, for instance, Adobe Reader, and sms and call log restore apps. I cannot see any common cause here. SDfix (latest version) says it can't find any groups, so can't do its work.
I'll nose around the S7 & 8 forums and see if any of these problems are turning up there (dev on the N7 was seriously interrupted by the problems caused by sammy's battery restrictions).
Hi!
I want to hide su binary from my phone temporarily to trick apps into thinking that my phone is not rooted. I thought I could just rename su binary from TWRP but I could not find that. It's not inside /system/xbin/ or /system/bin/.
It's more complicated than that.
You may simply need to check your Play Integrity responses. See this thread.
For more details on how the Magisk patch works, see this post. Don't start arbitrarily messing with things, though.
Start with the basics, though. Which apps are failing? Make sure you are using the Play Integrity fix. Add those apps to DenyList just to be safe. If they are Samsung specific apps, be aware that Knox Guard is tripped by flashing modified/custom firmware, and cannot be reversed, even if the device is returned to stock.
Thanks!
V0latyle said:
It's more complicated than that.
You may simply need to check your Play Integrity responses. See this thread.
For more details on how the Magisk patch works, see this post. Don't start arbitrarily messing with things, though.
Start with the basics, though. Which apps are failing? Make sure you are using the Play Integrity fix. Add those apps to DenyList just to be safe. If they are Samsung specific apps, be aware that Knox Guard is tripped by flashing modified/custom firmware, and cannot be reversed, even if the device is returned to stock.
Click to expand...
Click to collapse
I rooted my phone with TWRP 3.1.0.0 and SuperSU 2.7 instead of Magisk. How much of it still applies and how much does not? I actually rooted it like 5 years ago already, now I just have app that does not like rooted phone.
sysctl said:
Thanks!
I rooted my phone with TWRP 3.1.0.0 and SuperSU 2.7 instead of Magisk. How much of it still applies and how much does not? I actually rooted it like 5 years ago already, now I just have app that does not like rooted phone.
Click to expand...
Click to collapse
I'd recommend switching to Magisk. Chainfire hasn't been in the scene for years.
V0latyle said:
I'd recommend switching to Magisk. Chainfire hasn't been in the scene for years.
Click to expand...
Click to collapse
Tnx. Will attempt this. How should I do that? Should I click "full unroot" from SuperSU? Will I also loose my data and apps or will it just unroot? Or should I do it from TWRP instead?
sysctl said:
Tnx. Will attempt this. How should I do that? Should I click "full unroot" from SuperSU? Will I also loose my data and apps or will it just unroot? Or should I do it from TWRP instead?
Click to expand...
Click to collapse
Unrooting won't wipe data. It doesn't matter how you do it.
V0latyle said:
Unrooting won't wipe data. It doesn't matter how you do it.
Click to expand...
Click to collapse
Tnx.
Also SuperSU asked if I want to disable Knox when it first started. Do you happen to know how to revert that? Would like to revert my phone to pre-SuperSU state in that regard as well. Just in case. Also will I be more vulnerable to viruses/malware when it stays disabled? Or should this knox question be separate topic already? Didn't want to spam this forum too much but it's also not connected to original question that much.
sysctl said:
Tnx.
Also SuperSU asked if I want to disable Knox when it first started. Do you happen to know how to revert that? Would like to revert my phone to pre-SuperSU state in that regard as well. Just in case. Also will I be more vulnerable to viruses/malware when it stays disabled? Or should this knox question be separate topic already? Didn't want to spam this forum too much but it's also not connected to original question that much.
Click to expand...
Click to collapse
I honestly don't know that much about Knox but having it disabled doesn't make your device any more vulnerable than being rooted. Be mindful of what you install, and don't grant root access to apps you don't trust.