Related
Hey everybody, if you've already opened up this thread, you already have my gratitude for seeing what my problem is.
If you haven't already caught on, I want to unroot my Samsung Galaxy S4. I have no idea why I decided to root it in the first place (maybe because that's what everybody else was doing? maybe because I'm just stupid? who knows), but now I really need to unroot it because I need the latest firmware.
The thing is, I've done a lot of stupid stuff to try and unroot it. I know, I should have looked for help instead of going out and doing stupid stuff on my own, but.. well, I don't really have an excuse - I'm just an idiot. My phone is still fully functional, but the device status is custom. But let me just tell you what happened.
1. I decided that I didn't want this phone to be rooted anymore. I opened up SuperSU and investigated the settings, and found an option to uninstall the phone. I decided to just go with it, and I uninstalled it. Everything went smoothly, nothing big happened, and before I knew it, SuperSU wasn't there anymore and everything seemed okay.
2. But it wasn't. I checked my device status, but it was custom. I was so confused. Wasn't it meant to be back to normal now? SuperSU wasn't there anymore, but it was still.. rooted? I turned on my S4 on Download mode. It said that it was still custom (or something similar to that, I don't remember the specific word). By now, I was confused and scared - what have I done?!
3. I searched around the internet for tutorials, and one in particular told me to download TriangleAway. Sweet, an app that unrooted and all I had to do was sit back and relax and let it do it's job! So I downloaded it and... it said that I didn't have SuperUser permissions or that I was unrooted. WHAT. I re-downloaded SuperSU and it said "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" JESUS CHRIST, tell me something I don't know, SuperSU! You're useless to me!! How could something be rooted yet unrooted at the same time? Life is so hard.
So now I'm sitting here, typing on my laptop, wondering what I could do to fix everything that transpired today. I searched up tutorials, but none of them had the same specifics on their phone as mine was. You see, my phone's baseband version is different from most. I have no idea why, but I'll list everything specific out here:
Model number: GT-I9505
Android version: 4.2.2
Baseband version: I9505XXUBMG4 (and for some reason, there is barely any help regarding this baseband, is it really rare to have this or something? or is is just the same as the I9505XXUBMGA? I don't know, so I don't want to take the risk)
If you've read and got up to here, you are already in my gratitude. If you help me, you have my thanks, and even if you don't, you still have my thanks for reading thus far.
If you could please help me, it would make this world just a little bit better! Thank you in advance. If you need any more information, please just tell me and I'll do the best I can to provide you with it.
Nyxdan said:
Hey everybody, if you've already opened up this thread, you already have my gratitude for seeing what my problem is.
If you haven't already caught on, I want to unroot my Samsung Galaxy S4. I have no idea why I decided to root it in the first place (maybe because that's what everybody else was doing? maybe because I'm just stupid? who knows), but now I really need to unroot it because I need the latest firmware.
The thing is, I've done a lot of stupid stuff to try and unroot it. I know, I should have looked for help instead of going out and doing stupid stuff on my own, but.. well, I don't really have an excuse - I'm just an idiot. My phone is still fully functional, but the device status is custom. But let me just tell you what happened.
1. I decided that I didn't want this phone to be rooted anymore. I opened up SuperSU and investigated the settings, and found an option to uninstall the phone. I decided to just go with it, and I uninstalled it. Everything went smoothly, nothing big happened, and before I knew it, SuperSU wasn't there anymore and everything seemed okay.
2. But it wasn't. I checked my device status, but it was custom. I was so confused. Wasn't it meant to be back to normal now? SuperSU wasn't there anymore, but it was still.. rooted? I turned on my S4 on Download mode. It said that it was still custom (or something similar to that, I don't remember the specific word). By now, I was confused and scared - what have I done?!
3. I searched around the internet for tutorials, and one in particular told me to download TriangleAway. Sweet, an app that unrooted and all I had to do was sit back and relax and let it do it's job! So I downloaded it and... it said that I didn't have SuperUser permissions or that I was unrooted. WHAT. I re-downloaded SuperSU and it said "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" JESUS CHRIST, tell me something I don't know, SuperSU! You're useless to me!! How could something be rooted yet unrooted at the same time? Life is so hard.
So now I'm sitting here, typing on my laptop, wondering what I could do to fix everything that transpired today. I searched up tutorials, but none of them had the same specifics on their phone as mine was. You see, my phone's baseband version is different from most. I have no idea why, but I'll list everything specific out here:
Model number: GT-I9505
Android version: 4.2.2
Baseband version: I9505XXUBMG4 (and for some reason, there is barely any help regarding this baseband, is it really rare to have this or something? or is is just the same as the I9505XXUBMGA? I don't know, so I don't want to take the risk)
If you've read and got up to here, you are already in my gratitude. If you help me, you have my thanks, and even if you don't, you still have my thanks for reading thus far.
If you could please help me, it would make this world just a little bit better! Thank you in advance. If you need any more information, please just tell me and I'll do the best I can to provide you with it.
Click to expand...
Click to collapse
Once you flash root the custom word wont get away unless you use triangle away to get rid of it that the use of triangle away and if you want stock :
Download latest firmware for your model and flash it through Odin done.
Why do you take the hard route?
You know you can just flash the stock rom you want with Odin? No need to unroot etc.
Hey! So recently I got a Samsung Galaxy J3 and was wondering if it was possible to get Xposed on it? Flashing a Zip is not an option, by the way.
Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).
Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD
krasCGQ said:
Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.
darknaio said:
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.
Click to expand...
Click to collapse
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD
krasCGQ said:
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
I would agree with you, as I had TWRP on my last phone and liked it quite a bit. I just don't know which phone's TWRP to try and how to try and flash it on there. Do I do it through Odin? Theres (if I recall correctly) a TWRP for the Samsung Galaxy J2 and J5, on either side of my J3 (Which it's so odd that the newer phone came out with a "series" number in the middle like that). Which would you suggest I do, J2 or J5, or neither?
darknaio said:
Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).
Click to expand...
Click to collapse
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.
darknaio said:
am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick
Click to expand...
Click to collapse
I know what you mean. Every time I restart my phone I have to re-root it if I want to do something with it. Luckily I don't really need root on this phone. Mainly because of the lack of things you can do with it. Hoping to see something come out of this though
EqiiKxDude said:
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.
Click to expand...
Click to collapse
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.
darknaio said:
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.
Click to expand...
Click to collapse
Yeah I mainly used Xposed on my previous phone to make it look more like Lollipop but since this phone comes with it I don't need it as much. And I didn't know you were able to unbrick this phone? I would have saved about $40 if I knew that ? well then yeah we should probably try one of them. I think we should go with the newest one though
Thats what I was thinking, but I don't know which J series came out before the J3 this year or I'd try that one. And yep, luckily able to unbrick it thanks to Odin. Actually unbricked it from even worse than a boot loop, I accidentally destroyed my recovery somehow so I couldn't even boot into that and do a factory reset, but thankfully Odin's separate from the recovery so it still worked. End of the day if you can at least get your phone recognized by your computer and can flash something onto it, flashing stock = unbrick (usually).
I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.
Curtis1973 said:
I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.
Click to expand...
Click to collapse
I have the same thing, temp root that's lost when I reboot. I've already had to go the Odin route with the original firmware so I've got my backup covered. I'm also working with the dev behind Super Sume and he thinks he has the issue resolved, if not he's going to teamview with me to try and get past this. If we manage to solve the problem I'll post the results and subsequent steps here. Hopefully this will lead to root sticking through reboot. If so then at minimum may be able to solve -some- of the problems. Though I don't know if this will fix Xposed not working, as it always caused me to boot-loop in the past (only solved by going into TWRP and rebooting from there) and even if root sticks the only way to flash Xposed according to current theories is to do so from custom recovery, which I haven't found one for this device yet.
Have you been able to get a custom recovery on your J3? If so that would be the other key part to solving a lot of these problems. If I get the Super Sume to work and someone else can manage to get a custom recovery working, maybe that'll be the start of this device's support here =D.
No but I believe by repacking an edited firnware you can add xposed that way.
Curtis1973 said:
No but I believe by repacking an edited firnware you can add xposed that way.
Click to expand...
Click to collapse
Unfortunately I wouldn't know the first thing about editing a firmware, much less be able to add Xposed lol. Could that be a way to manually add custom recovery? Or are we still dependent on someone making a version compatible with this phone?
will need a custom recovery built for the device. with proper root you could then use flashify to install it to the device. root opens the door for everything. temp root will never get much except ability to debloat the device.
---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------
i reached out to chainfire in hopes of cf auto root for the j3. but have not heard back. but does not mean i wont. will see. otherwise i will keep on trying what i can.
Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?
EqiiKxDude said:
Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?
Click to expand...
Click to collapse
Ive been seeing that too and ignoring/swiping it away. Not sure what it is though.
my system is edited so im not getting update pushes. probably nothing significant.
Curtis1973 said:
my system is edited so im not getting update pushes. probably nothing significant.
Click to expand...
Click to collapse
Your J3 is modified? Temp root, or something else?
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.
I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?
Mike_77712 said:
I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?
Click to expand...
Click to collapse
I had one time where I got Magisk working with the Superstarz ROM on the SM-G550T1. I don't remember what I did tbh, but it took hours of rebooting, frustrating hanging, etc.. Upon one of the Magisk modules I flashed after it did work, of course to my sadness it stopped working. Nandroid backups are so crucial and I just stopped making so many changes before a backup these days. Sure you can't speed demon through and get all your wildest fantasies to come true overnight, but I find making incremental progress with backups to me more sustainable. Anyways, I tried many times, many setups, and ultimately wasted many hours trying to "win" with this phone. I'd honestly highly recommend sticking with SuperSu by Chainfire as it has always just worked. That means no Android Pay, no Pokemon Go, and prolly others I haven't considered. I too wanted to have my cake and eat it... For Safetynet to pass and la la la. Truth be told, it is a royal pain in the arse!!! If YOU STILL DARE, you would definitely want to make sure you start with a stock ROM boot image and BACK IT UP #1. If you are using a custom ROM it may not allow you to fully unroot and go back to a stock img because it doesn't find one to revert to. For Magisk to pass SafetyNet and work at full capacity, you must start there. If you go to the trouble of going all the way back to stock, please upload one for all of us and make sure to include your phone/os specs from about phone. From stock, flash custom recovery BEFORE ROOT, within recovery back up boot, upload for us and yourself. Now, you have a legit revertible img to go back to in case you can't from Magisk/SuperSu. Phh's Superuser was a nightmare btw, never worked correctly. There's no way to unroot and go back to a stock boot img that I found unless you first back up from TWRP or custom recovery. Long answer, more than you bargained for no doubt, but hopefully something to be gained from. Really though... if all you want is for Snapchat to work and can live without Android Pay/Pokemon Go. Here's an easier method: uninstall Xposed, unroot, log into Snapchat (let it save a login token), root, re-install Xposed, Titanium Backup Snapchat, it should hold up from there. Did it once, forget if that's entirely right, but search and ye will find exact threads. I just said to hell with Snapchat, Pokemon Go, and Android Pay. I'd rather settle for Chainfire's Superuser's stability, Xposed (more mods), & less overall B.S. Sorry if that isn't the best possible answer, or what exactly you were sought. I did however want to share some of my experience (many, many, many hours of tinkering). All in all, I finally decided to order a new digitizer/lcd to repair an old OnePlus One that I have had laying around. I plant to fix it and migrate because I'll tell ya right now... ppl just aren't gonna do much more for this model than what you see out there. Perhaps I'm being a pessimist, but also realist... I've been waiting around looking for something to come, too lazy to attempt re-compilation of code myself, and no one else has yet. Magisk can be a nightmare to the ninth gate's extreme degree. It is possible, not saying it can't be done. Have patience, or it won't that's for sure. Just really have to mess up... lots of times... over and over, and over and over and over again. Learn, read XDA, and be stubborn/patient as hell until you get there. Document your progress so you know what you did and maybe you can help someone else. Other times it's more advantageous pick what matters, settle, and focus on something else. :good:
From my understanding you need a clean install, unroot with SU (or install SU as systemless (?)),wipe internal, and follow instructions to install Magisk... I'm not totally sure though, also install the Magisk module.
Mike_77712 said:
I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?
Click to expand...
Click to collapse
I just successfully rooted with Magisk & modded a few things out with it, only issue seemz to be systemless xposed but ill crack that shell when need be . Let me know if any1 is in need of help doing the same.
woahOppO999 said:
I just successfully rooted with Magisk & modded a few things out with it, only issue seemz to be systemless xposed but ill crack that shell when need be . Let me know if any1 is in need of help doing the same.
Click to expand...
Click to collapse
Can you please share the steps you followed to root ON5 pro using magisk.
Also if you can list the modules u have from magisk.
Let me start by saying I never gave rooted phones much though. I knew of them but never even knew anyone that ever had one. I figured the Galaxy S8 (G950U) would be a good phone to start with:laugh: Since it was my first rooted phone I couldn't resist experimenting, a lot. So I would flash this flash that, whatever I thought had a very small chance of working i flashed, lol. I usually would end up having to fireing up Odin and flashing the most important files on my PC, Partcyborg's awesome work, which I can flash with my eyes closed basically by now :laugh: Some things I would flash would just cause me to lose root though. It's driving me nuts not to be able to get it back without Odin. I could use Odin+Partcyborg's rom and have it back in 15 minutes, but I'm tired of being feed I'm ready to hunt, lol.
The thing is, I still have TWRP Safestrap custom recovery that I can access. I flash Supersu, it appears to flash fine but changes nothing, not even an SU icon in the app drawer. I did make SupoerSU Pro a system app a while ago, was that a mistake? I see it in the Apps list in Settings but I can't do much there except disable it and enable it (no it's not disabled,lol)
How can I get root back using custom recovery only? What should I have checked in Safestrap when flashing SuperSU?, Cache, System, Modem, etc? If anyone would care to explain some of the reasons I lose root but not custom recovery it would really calm my curiosity . I'm sure it would help a lot of other noobs also.
Boot animations is another thing that I find very interesting. Trying to change it has been the cause of at least 10 factory resets
I go to /system/media/ and swap out Booitanimation.zip, change the permission then I either get no change or I have reflash with Odin. What is all the files labeled Battery _000 Battery _001 Battery_002 all the way to Battery_100? Does the resolution need to be exactly the same as stock?
Is my rooted S8 not as rooted as other rooted phone? Lol, does that sentence make sense? Because of its locked bootloader and lack of custom roms is why I ask. Am I an idiot for buying a S9+ (G965U) since I love having root? I was hoping someone "cough...Part...cough cough...cyborg would be on it. If not though, no big deal. I do still have the S8 and still use it a lot even though it has no service, lol. Amazing phones not so amazing bootloaders though:laugh:
Thanks for reading. If you only skimmed it, thank you also. I know it's very long, lol. I just found something called a Combination Rom. Since I still have Safestrap I'm gonna do what I usually do, flash it and ask questions later:laugh:
Gregbmil1 said:
Let me start by saying I never gave rooted phones much though. I knew of them but never even knew anyone that ever had one. I figured the Galaxy S8 (G950U) would be a good phone to start with:laugh: Since it was my first rooted phone I couldn't resist experimenting, a lot. So I would flash this flash that, whatever I thought had a very small chance of working i flashed, lol. I usually would end up having to fireing up Odin and flashing the most important files on my PC, Partcyborg's awesome work, which I can flash with my eyes closed basically by now :laugh: Some things I would flash would just cause me to lose root though. It's driving me nuts not to be able to get it back without Odin. I could use Odin+Partcyborg's rom and have it back in 15 minutes, but I'm tired of being feed I'm ready to hunt, lol.
The thing is, I still have TWRP Safestrap custom recovery that I can access. I flash Supersu, it appears to flash fine but changes nothing, not even an SU icon in the app drawer. I did make SupoerSU Pro a system app a while ago, was that a mistake? I see it in the Apps list in Settings but I can't do much there except disable it and enable it (no it's not disabled,lol)
How can I get root back using custom recovery only? What should I have checked in Safestrap when flashing SuperSU?, Cache, System, Modem, etc? If anyone would care to explain some of the reasons I lose root but not custom recovery it would really calm my curiosity . I'm sure it would help a lot of other noobs also.
Boot animations is another thing that I find very interesting. Trying to change it has been the cause of at least 10 factory resets
I go to /system/media/ and swap out Booitanimation.zip, change the permission then I either get no change or I have reflash with Odin. What is all the files labeled Battery _000 Battery _001 Battery_002 all the way to Battery_100? Does the resolution need to be exactly the same as stock?
Is my rooted S8 not as rooted as other rooted phone? Lol, does that sentence make sense? Because of its locked bootloader and lack of custom roms is why I ask. Am I an idiot for buying a S9+ (G965U) since I love having root? I was hoping someone "cough...Part...cough cough...cyborg would be on it. If not though, no big deal. I do still have the S8 and still use it a lot even though it has no service, lol. Amazing phones not so amazing bootloaders though:laugh:
Thanks for reading. If you only skimmed it, thank you also. I know it's very long, lol. I just found something called a Combination Rom. Since I still have Safe-strap I'm gonna do what I usually do, flash it and ask questions later:laugh:
Click to expand...
Click to collapse
so the boot animations off top of my head are now located in something something and your carriers folder...The can be changed
Is it actually not rooted or is su just not responding
I have had it where the prompt never comes up and granting all just never works either normally a few reboots later it starts....
the custom rom thing is most def cause of locked boot-loader....
Up til boot-loader revision 2 is all we have root for and cannot be downgraded 3 and up....
I have myself tried flashing stock system img and then su and busy box from safe strap and up til now even this has been a no go...
Safe-strap is cool but basically No better than flashfire.IMO.
I am working with the possible bluetooth fix right now and have bricked and flashed 20 times over in the last 12 hours...
It actually is not rooted anymore after I flashed what claimed to be a boot animation for the G950U. If I open the SuperSU app it points me to a non-working site that has directions on "How to root". Plus all of the apps I have downloaded that require root all tell me I'm not rooted. Oddly enough though I was able to flash Xposed and had a green light once I opened it, (remember I still had SafeStrap recovery) it could only be accessed manually. I was shocked and yet even more confused, lol. I only tried out 2 modules before I reflashed Partcyborgs files again. Again, I was very confused as to why the modules actually worked but root only apps would start , only Xposed modules. I did only try 2 though AdBlocker Reborn and SpeedUp, both acted as if everything was normal . I wonder if it had something to do with making SuperSU a system app, which it no longer is since I reflashed with Odin.
Thanks for the info on the Bootanimation, but still I can't even delete the one I have now, for educational purposes only, Haha. It is a pretty freaking sweat bootanimtion Partcyborg included. I can't find it though T-Mobile (G950U) btw