I recently got s-off, updated from 1.15 to 2.06, installed abp and also flashed a no ads zip file for good measure because some ads would still get through. Everything was going great until the phone randomly froze. I held down the power button and rebooted into recovery and cleared my cache and dalvik cache, thinking that may have been the problem. Upon rebooting after that, I come to find out I've lost my root access. This is so weird. I am still s-off and have the 2222222 confirmation shown when I am in the bootloader, I still have super user installed, but when I run an app that needs root, such as adaway, it says I don't have root. I downloaded root checker and it confirmed that I didn't have root. I don't understand how this could have happened. Is there anyway to regain root? I have been having the worst luck with this phone :\
terrorist96 said:
I recently got s-off, updated from 1.15 to 2.06, installed abp and also flashed a no ads zip file for good measure because some ads would still get through. Everything was going great until the phone randomly froze. I held down the power button and rebooted into recovery and cleared my cache and dalvik cache, thinking that may have been the problem. Upon rebooting after that, I come to find out I've lost my root access. This is so weird. I am still s-off and have the 2222222 confirmation shown when I am in the bootloader, I still have super user installed, but when I run an app that needs root, such as adaway, it says I don't have root. I downloaded root checker and it confirmed that I didn't have root. I don't understand how this could have happened. Is there anyway to regain root? I have been having the worst luck with this phone :\
Click to expand...
Click to collapse
Send me a PM if you want me to help you out. You need to install a custom recovery and use that to install a rooted rom and kernel. It can be a stock rooted rom. Or mostly stock however you want to do it, I'll help you set it up and teach you some things along the way.
I can teach you all kinds of things via team viewer, it wont take long and it's a necessity for having a rooted phone in my opinion. I know it can be frustrating and over whelming but it will get better I promise.
Oh and also you don't need to worry about losing s off. It's at a much lower level than anything you've mentioned touching. So it will always be there regardless because you definitely don't want to be messing with hboots or s off type stuff.
Hey, I PMed you.
Try uninstalling superuser and installing either supersu or the other superuser.
Sent from my HTC6435LVW using xda app-developers app
I can't uninstall my Superuser unless I use Titanium Backup. I tried installing SuperSU (while still having my original Superuser installed) and the SuperSU said that "There is no SU binary installed"
terrorist96 said:
I can't uninstall my Superuser unless I use Titanium Backup. I tried installing SuperSU (while still having my original Superuser installed) and the SuperSU said that "There is no SU binary installed"
Click to expand...
Click to collapse
I got your PM. I'll pick your brain about the ideal setup for your needs and how you use the DNA via gtalk. Then we'll make a plan of attack and you can update the thread with your solutions opinions etc.
As long as your opinion of me is good. Otherwise, it's prohibited. I have a green title and seniority rules
HTC EVO CyanogenMod Cant use BEATS AUDIO
CharliesTheMan said:
Send me a PM if you want me to help you out. You need to install a custom recovery and use that to install a rooted rom and kernel. It can be a stock rooted rom. Or mostly stock however you want to do it, I'll help you set it up and teach you some things along the way.
I can teach you all kinds of things via team viewer, it wont take long and it's a necessity for having a rooted phone in my opinion. I know it can be frustrating and over whelming but it will get better I promise.
Oh and also you don't need to worry about losing s off. It's at a much lower level than anything you've mentioned touching. So it will always be there regardless because you definitely don't want to be messing with hboots or s off type stuff.
Click to expand...
Click to collapse
I need help with rooting my HTC EVO to stock or CyanogenMod. With CyanogenMod my phone will not play audio/BEATS or will not open
PLAYSTORE.
How to get root back after subsequent apps are denied root?
Over the last year, this has happened several times while having different custom roms installed. It happened several times with my Galaxy S4 and S5, and recently with my Galaxy Tab S 10.5. I have not lost root on my Nexus 7 (2013). The common denominator appears to be the Samsung devices.
Through SuperSu, I have removed root, rebooted, and installed root again with CF-Root which has not given me root access.
The only way I have been able to recover to date is to do a factory rest. It is interesting to note that I would have thought that the factory rest would take me back to the Samsung rom but in the last two time that I did this on either device, I ended up with the custom rom that I just had but without root or custom recovery.
To go back to a Samsung rom, I would think that if I started the device in download mode and did a flash with odin.
But rather than go through this, is there a reason why this happens and/or is there a way to avoid it?
Lastly, is there a true way of getting root back once it stops granting root?
cyaclone said:
How to get root back after subsequent apps are denied root?
Over the last year, this has happened several times while having different custom roms installed. It happened several times with my Galaxy S4 and S5, and recently with my Galaxy Tab S 10.5. I have not lost root on my Nexus 7 (2013). The common denominator appears to be the Samsung devices.
Through SuperSu, I have removed root, rebooted, and installed root again with CF-Root which has not given me root access.
The only way I have been able to recover to date is to do a factory rest. It is interesting to note that I would have thought that the factory rest would take me back to the Samsung rom but in the last two time that I did this on either device, I ended up with the custom rom that I just had but without root or custom recovery.
To go back to a Samsung rom, I would think that if I started the device in download mode and did a flash with odin.
But rather than go through this, is there a reason why this happens and/or is there a way to avoid it?
Lastly, is there a true way of getting root back once it stops granting root?
Click to expand...
Click to collapse
Best to post such things in your device specific forum.
This forum is for the Droid DNA.
However, gaining root is as simple as downloading the latest SuperSu zip and flashing it in recovery.
Very simple to do on any rom.
Related
Okay, so I haven't as of yet seen a thread that appears to spell out this process. Most of you are talking about applying developer-modified patches to get to DI01, using Clockwork recovery, and things like that. For various reasons, some of us prefer to remain a bit closer to stock, and not worry about bricking with custom recovery software and whatnot. I'm one of those people, and I've seen questions here and there on how to go back to stock, and if root can be maintained or redone afterward, etc., so I decided to document here what I did to apply the official update to my rooted and lag-fixed Fascinate. Without further ado, here's the process I followed:
Ran the unlagfixme.bat script from http://forum.xda-developers.com/showthread.php?t=779597, which automatically reboots the phone
Used Root Explorer to remove the ".old" extension I had added to all system .apk files I considered bloatware (I chose to disable them, not delete them)
Rebooted the phone again for good measure
Downloaded the update, and let it install normally, after which root access was gone as expected (Superuser.apk and other apps that required root access were still present, but they wouldn't function)
Rooted my Fascinate again per the instructions in http://forum.xda-developers.com/showthread.php?t=779238, just like I did the first time (only had to do it once, not twice like some here have said); note that I followed all instructions except for the final one, which is installing Superuser.apk, as that application was still installed, and still worked fine after applying the proper permissions to su and busybox
Opened Root Explorer, and once again added .old to all .apk files that I wanted to disable and remove from sight
Rebooted again
Ran the lagfixme.bat from http://forum.xda-developers.com/showthread.php?t=779597 to re-apply the lag fix
Rebooted one final time to make sure everything was in still good working order
So there it is. I'm still running stock ROM, stock recovery, etc. I should be able to easily repeat this process any time there's a new OTA update, with minimal risk of bricking.
Helpful thanks, but I think I screwed up.
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
propylene22 said:
SO I got the OTA update message this morning. I have root and lagfix installed, and I ran the OTA. Everything works but I no longer have root access. SO I think I screwed up. Newb right. SO do I have to go back to the stock image? What do I need to do to recover while retaining my contacts apps etcetera. Thanks
Click to expand...
Click to collapse
Just re-root, either through adb or there was a one-click out there.
Yeah, just re-root using the original procedure you used (except no need to reinstall superuser.apk), and you should be good to go.
Sent from my SCH-I500 using XDA App
Thanks for taking the time to write that up Ivorycruncher!
How would this process differ when the Froyo update is released, also having ClockworkMod Recovery installed instead of stock recovery?
I, like you, would like to have legitimate updates installed while keeping root.
I've never installed Clockwork, so I can't comment on that. When Froyo comes out, I imagine the process will be much the same, though at this point there's no way to know if the original rooting method will still work or not after the upgrade. Also, depending on what they do with Froyo, the lag fix may not be necessary anymore, and might not work without some tweaking even if it is still needed.
Sent from my SCH-I500 using XDA App
My friend gave me a droid razr which is rooted and has a custom rom installed on it. I was able to charge the device and boot into the OS however the phone simply will not be recognized by the computer. I've tried 3 different cables to no avail, there must be something wrong with the USB port itself.
Is there any way to unroot the device and get back to stock without having to connect the phone to the computer? I am able to put the SD card into a different phone in order to transfer files to it.
Thanks alot in advance
lysdexik said:
My friend gave me a droid razr which is rooted and has a custom rom installed on it. I was able to charge the device and boot into the OS however the phone simply will not be recognized by the computer. I've tried 3 different cables to no avail, there must be something wrong with the USB port itself.
Is there any way to unroot the device and get back to stock without having to connect the phone to the computer? I am able to put the SD card into a different phone in order to transfer files to it.
Thanks alot in advance
Click to expand...
Click to collapse
Using the app SuperSU, there's an option for "full unroot" in the settings. If you plan on keeping the ROM, I wouldn't unroot if I were you. If you DON'T plan on keeping the ROM, then you're pretty much hopeless to remove it without connecting to a computer. Are you sure the drivers are installed for the device? You say the phone charges, so I doubt it's the port. Do USB options show up in the notification tray on the phone when you plug it in to a computer?
Fracta1 said:
Using the app SuperSU, there's an option for "full unroot" in the settings. If you plan on keeping the ROM, I wouldn't unroot if I were you. If you DON'T plan on keeping the ROM, then you're pretty much hopeless to remove it without connecting to a computer. Are you sure the drivers are installed for the device? You say the phone charges, so I doubt it's the port. Do USB options show up in the notification tray on the phone when you plug it in to a computer?
Click to expand...
Click to collapse
There are no usb options that appear in the notification window, and since I posted this the phone has quit charging . I'm not sure how he went about rooting the phone because when I went into the recovery, it was still the stock recovery that was installed. I did a factory reset on the device and when I booted it back up it asked me to activate before I could go any further. I tried using my sim card from my galaxy nexus but it gave me an error. I was thinking that I might bring the phone to verizon and see if it activates with a clean sim card and then look to see if it is still rooted or not.
Also, after further digging I found out that he actually did not install a custom ROM, all he did was root the device. So if I can get into the SuperSU app I will go ahead and unroot the device.
lysdexik said:
There are no usb options that appear in the notification window, and since I posted this the phone has quit charging . I'm not sure how he went about rooting the phone because when I went into the recovery, it was still the stock recovery that was installed. I did a factory reset on the device and when I booted it back up it asked me to activate before I could go any further. I tried using my sim card from my galaxy nexus but it gave me an error. I was thinking that I might bring the phone to verizon and see if it activates with a clean sim card and then look to see if it is still rooted or not.
Also, after further digging I found out that he actually did not install a custom ROM, all he did was root the device. So if I can get into the SuperSU app I will go ahead and unroot the device.
Click to expand...
Click to collapse
From what I know, the ports on the RAZR are poorly designed and prone to break. I had issues with HDMI detection a while ago and had to send it in for repairs.
Factory resets do not unroot the device.When you get the chance to use the SuperSU app (you may have to download it from the market), it should be easy to unroot it, but it's hard to say when the method isn't known.
And as far as I know, can't you just use wi-fi to complete initial setup?
Fracta1 said:
From what I know, the ports on the RAZR are poorly designed and prone to break. I had issues with HDMI detection a while ago and had to send it in for repairs.
Factory resets do not unroot the device.When you get the chance to use the SuperSU app (you may have to download it from the market), it should be easy to unroot it, but it's hard to say when the method isn't known.
And as far as I know, can't you just use wi-fi to complete initial setup?
Click to expand...
Click to collapse
Ok, I got the device activated and yeah it appears that it is still rooted. You mentioned downloading SuperSU off of the marketplace, as only Superuser was installed on the phone.
I downloaded SuperSU and when I try to open it I am getting the error ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!").
So yeah, I am not sure where to go from here, the port is still not working so I need to do something before the battery dies.
lysdexik said:
Ok, I got the device activated and yeah it appears that it is still rooted. You mentioned downloading SuperSU off of the marketplace, as only Superuser was installed on the phone.
I downloaded SuperSU and when I try to open it I am getting the error ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!").
So yeah, I am not sure where to go from here, the port is still not working so I need to do something before the battery dies.
Click to expand...
Click to collapse
Try an app like Root Checker or Got Root? to make sure the device IS rooted. I have messily unrooted a device before and while it WAS unrooted, it left Superuser and Busybox behind.
If it IS rooted, find an app of your choice (System Tuner Pro, Titanium Backup...) and uninstall root apps (Superuser). Cover up root best you can. I've handed a boot-looping device in for repairs with no carrier trouble, so I'm sure you'll be fine.
If it ISN'T... Well, you're hopeless without a computer as far as I can say.
Also, it may not help, but if your device is indeed rooted, you could also go into Superuser, swipe left and try to update the binaries so you can try SuperSU again.
Fracta1 said:
Try an app like Root Checker or Got Root? to make sure the device IS rooted. I have messily unrooted a device before and while it WAS unrooted, it left Superuser and Busybox behind.
If it IS rooted, find an app of your choice (System Tuner Pro, Titanium Backup...) and uninstall root apps (Superuser). Cover up root best you can. I've handed a boot-looping device in for repairs with no carrier trouble, so I'm sure you'll be fine.
If it ISN'T... Well, you're hopeless without a computer as far as I can say.
Also, it may not help, but if your device is indeed rooted, you could also go into Superuser, swipe left and try to update the binaries so you can try SuperSU again.
Click to expand...
Click to collapse
I'm going to try Root Checker right now to see if its actually rooted like you said. I actually updated the Superuser app earlier and SuperSU still wasn't working so I'm starting to think it may have lost root somehow.
I also tried using Superuser Update Fixer and manually flashing the SU binary file from recovery but since the phone is still on stock recovery it wouldn't work.
I was also thinking that I could try and cover up root with titanium backup as you said, that was going to be my last step but since the battery is getting lower and lower I may have to go that route and hopefully not have a problem with Verizon. I guess it also helps that the stock recovery and ROM are still installed on it.
This is just a side project for me, I have a galaxy nexus myself and I have never had any trouble with it.
UPDATE: I just used both of the root checking applications you suggested and they both say that the phone is not actually rooted. Root Checker just spit out a message saying it wasn't rooted and Got Root? said that it located busybox but could not obtain root access. I'm going to try and clean things up with titanium backup.
UPDATE 2: When I installed titanium backup, the app asked me for root permissions and I hit grant. When I open superuser it shows it as giving permission to titanium backup but I can't find Superuser in the list of applications within titanium backup itself. There has to be another way to remove superuser.
UPDATE 3: I just tried to delete the superuser.apk file using root explorer and I get a pop-up saying that it won't allow me to delete that APK because my phone is not rooted. Ugh.. now I'm stuck.
lysdexik said:
I'm going to try Root Checker right now to see if its actually rooted like you said. I actually updated the Superuser app earlier and SuperSU still wasn't working so I'm starting to think it may have lost root somehow.
I also tried using Superuser Update Fixer and manually flashing the SU binary file from recovery but since the phone is still on stock recovery it wouldn't work.
I was also thinking that I could try and cover up root with titanium backup as you said, that was going to be my last step but since the battery is getting lower and lower I may have to go that route and hopefully not have a problem with Verizon. I guess it also helps that the stock recovery and ROM are still installed on it.
This is just a side project for me, I have a galaxy nexus myself and I have never had any trouble with it.
UPDATE: I just used both of the root checking applications you suggested and they both say that the phone is not actually rooted. Root Checker just spit out a message saying it wasn't rooted and Got Root? said that it located busybox but could not obtain root access. I'm going to try and clean things up with titanium backup.
UPDATE 2: When I installed titanium backup, the app asked me for root permissions and I hit grant. When I open superuser it shows it as giving permission to titanium backup but I can't find Superuser in the list of applications within titanium backup itself. There has to be another way to remove superuser.
UPDATE 3: I just tried to delete the superuser.apk file using root explorer and I get a pop-up saying that it won't allow me to delete that APK because my phone is not rooted. Ugh.. now I'm stuck.
Click to expand...
Click to collapse
Yeah... Sorry about your luck
You could try sending it into Verizon still. They may fix it. Perhaps not for free. Even if not at all, at least it's just a side project?
That's about all I can think of :/
Greetings,
I know the easy answer to this is going to be to flash a new rom, but if I wanted to do that I would have already. I'd rather find and repair the source of the issue and learn from it.
That being said, shortly after getting my tbolt (when they were first released) I used the revolutionary root and added in VPN software for work. Being unaware that OTA updates hadn't been blocked during the rooting, the phone took an update and went into a death-boot-loop. I found a clean updated OTA rom, flashed and unrooted the phone as the VPN software didn't work well for what I intended anyway.
Great, now the phone is all back to stock (or so I thought).. After a while, another OTA update came down, it asked to update, I allowed, and it said update failed.. Repeat ad nauseum for the next several weeks. Since I was happy with the way the phone was operating, I didn't care if it got the updates or not.
So last week, I decided that since the phone is out of warranty anyway, I might as well root and get rid of some of the bloat, and while I'm at it, get rid of the damn nag screen every tine I hook it to a computer. Searched around, found thunderbolt tool 1.0.1, downed it and tried it out, and it proceeded to say unable to lock my phone.
After a little screwing around, the "update status" on the phone itself reports ROM Version: 2.11.605.9, while the tool was getting a response of 2.11.605.5, so it was using the wrong method to get into the phone. So I edited the batch file to use the .9 method no matter what it reported back, and it proceeded to root, add the recovery, and superuser.
Ahhh, life is good, the phone is rooted again, time to start doing my own customization.
Except that after a couple reboots, everything loses the root rights.
Running titanium backup says "asking for root rights" and then "titanium has been granted superuser permissions" but it just hangs there at the "asking for root rights" screen.
Wireless tether similar story... Start the app and it says "press to start tethering" and touching the screen gets "wireless tethering has been granted superuser permissions", then hangs at "please wait while starting".
Won't do anything that requires root, unless I run the tool again and select "S-off but no root", and it will go through a procedure and root will work again for a while.
Also, as I'm typing this, I discovered that it doesn't necessarily require rebooting to lose root. I had root working last night, but when I picked up the phone to get the proper messages to type, it is not showing root again, and it hasn't been rebooted since root was working.
Thoughts on how to repair this without flashing a rom?
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like OTA RootKeeper to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Milimbar said:
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like -edit- to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
Click to expand...
Click to collapse
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
I'll check out the rootkeeper.
disconnecktie said:
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Never took the .19 update, and both the tool and phone report as .05 now. (if I remember correctly the .09 reverts back to .05 to get in)
damm315er said:
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
Click to expand...
Click to collapse
What recovery are you using?
I only use 4ext and would recommend that.
The fix permissions will take up to 5 min and may not help your particular issue, but shouldn't hurt to try.
If 4ext - Boot into recovery, select tools then select fix permissions.
If CWM I think its in the advanced menu.
and If TWRP I think it is in the advanced menu again.
Good luck and listen to the others here, they go out of their way to help people a lot
Ok earlier I misread your post. I thought it said 605.19. Still though something you're doing is causing you to only get temp root. Reread the op of the allinone tool and make sure you meet the requirements before you start it. That away when you run it this time you are in the best possible situation for it to work. Trter is very helpful and if you post your issue in his thread he will probably assist you with anything you need.
Sent from my ADR6400L using Tapatalk 2
I remember having a similar problem about 6-7 months ago.
I would randomly loose root, though not as often as he is describing.
In my case it was a combination of an outdated root method and a flawed ROM.
If everything he is using is current, including the ROM, he shouldn't have an issue.
If it were me I would flash Santod's stock deodexed ROM and be done with it.
It is the stock ROM with nothing changed except it is prerooted.
I understand that you would like to "fix" this issue without flashing a ROM, however the ROM itself could be the problem. this solution is the simplest I can think of.
Using everything from the thunderbolt toolkit, so yes, 4ext.
Found and ran the fix permissions, ran for 15 minutes before it finished so we'll see how it goes.
I get what you're saying about the rom being screwed up, and am starting to think my only choice is to reflash it, so I'll start looking into a new rom.. That being said I'm still pursuing fixing this until I find a rom that serves my purpose.
Is there a good stable ICS for thunderbolt, pre-loaded with root and good battery life?
Yea the one in the post above yours. If you want something a that is faster and has better battery than it then head over to infectedrom.com and check out all the different options santod has made.
Sent from my ADR6400L using Tapatalk 2
Hey Guys,
I own a Samsung Galaxy S4 from Verizon and have followed the guide on how to root it posted on the forums. For a while things were good. My phone booted up with the correct loading screen and my device detected that I was on an official kernel. Now for reasons I'm not sure of, my phone is saying that the kernel is custom and the lock icon has returned when I restart or cold boot my phone. I'm not running custom firm ware, I'm running a stock Verizion kernel. I tried to delete SuperUser, but it isn't installed. My binaries for SuperSU are up-to-date. I'm still rooted, but I would like to get rid of the unlock icon when I boot up and I would like to get the system to recognize that this is an official kernel.
Also ES File Explorer is unable to mount r/w privilages on my phone in order to delete busybox and su so that I could try to re-root the phone again. Any help would be appreciated, thanks!!
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
Most of the time mine is gone. Maybe once a week I might see it.
sneekerpimpz said:
Theres no way so far to get rid of it. Mine actually goes back and for between custom and official all the time. Maybe when the bootloader gets unlocked it will do away with it, but until then it does no harm. So if you want to root, that's the price we pay.
Click to expand...
Click to collapse
So I managed to get rid of it. I'm not sure if it's permanent, but here's what I did. I couldn't delete the stuff in the root directory (and this was before I found solid explorer which has better root access programming than es does). So I did a factory reset and found that that worked for a while, but then I noticed that downloading Triangle Away seemed to be causing the problem because the lock icon returned after I installed it and gave it root access. So I deleted it and chose the 'unroot' option from the list of options in supersu. Then I re-rooted the phone using the guide. Now the lock icon hasn't returned, and the device status under the about phone menu says that my firmware is the official one. Another thing I noticed is that I'm running an older version of busybox (version 1.17.1 I think, as installed by motochopper).
Again I'm not sure what I did differently, or changed as a result of my method, but it seems to have worked. Perhaps someone with more development knowledge can let me know what's happened for my own personal information.
Phone has been fine, rooted with cwm5.5. This is wifey phone so I keep messing with it at a minimum. At some point I noticed it no longer has root. It runs stock 4.1.2. With a couple of root apps - such as AdAway-which is no longer working and has error message "Either subinary could not be found or you did not allow root permissions for AdAway"
Superuser app has this error "There are currently no superuser app policies." then "Superuser binary must be updated" attempting to update results to error "There was an error installing superuser. "
I rooted the phone again with the same CWM ver. file. attempted to flash superuser but it errored and aborted installation. I rebooted and installed rom manager so that I could update CWM. That errored out as well. Root verifier confirms there's no root on the phone. I have installed busy box but it has the same error message no root access.
I thought to root with CWM ver 6.0.4.6 but installation aborted. I tried TWRP but it aborted as well. Only CWM 5.5 works which my normal routed is then to flash superuser, install rom manager and then have it update to CWM to ver 6.xx. But his time none of these is working. How do I regain root?
jayinc11 said:
Phone has been fine, rooted with cwm5.5. This is wifey phone so I keep messing with it at a minimum. At some point I noticed it no longer has root. It runs stock 4.1.2. With a couple of root apps - such as AdAway-which is no longer working and has error message "Either subinary could not be found or you did not allow root permissions for AdAway"
Superuser app has this error "There are currently no superuser app policies." then "Superuser binary must be updated" attempting to update results to error "There was an error installing superuser. "
I rooted the phone again with the same CWM ver. file. attempted to flash superuser but it errored and aborted installation. I rebooted and installed rom manager so that I could update CWM. That errored out as well. Root verifier confirms there's no root on the phone. I have installed busy box but it has the same error message no root access.
I thought to root with CWM ver 6.0.4.6 but installation aborted. I tried TWRP but it aborted as well. Only CWM 5.5 works which my normal routed is then to flash superuser, install rom manager and then have it update to CWM to ver 6.xx. But his time none of these is working. How do I regain root?
Click to expand...
Click to collapse
have you tried flashing another ROM? rumor has it that custom roms contain and are pre rooted.
captemo said:
have you tried flashing another ROM? rumor has it that custom roms contain and are pre rooted.
Click to expand...
Click to collapse
Initially I had actually, but camcorder issues, modems with sporty service ... we a deal breaker. Si I just restored it to stock with kies to avoid more lip. Only thing I did was root the stock so I could install a few apps such as AdAway. I don't plan to do stock on this unless I can get get rooted stock rom.
jayinc11 said:
Initially I had actually, but camcorder issues, modems with sporty service ... we a deal breaker. Si I just restored it to stock with kies to avoid more lip. Only thing I did was root the stock so I could install a few apps such as AdAway. I don't plan to do stock on this unless I can get get rooted stock rom.
Click to expand...
Click to collapse
When I rooted my phone I was wary of using methods that would have me going through either download mode or having to install a custom recovery (which eventually became pointless since I had to do both to flash roms anways lol) but at the beginning I was trying to use something simple.. while googling I stumbled upon this http://www.kingoapp.com/ and rooted from there.. it's like a one-click root kind of thing and seems to keep the root working regardless.. maybe you wanna check it out and see if it helps, in case you loose your root again. If you wanna run your phone stock but rooted, at least after doing the restoration via keys you'll keep the stock samsung recovery.
Hope it helps!
wavv.drama said:
When I rooted my phone I was wary of using methods that would have me going through either download mode or having to install a custom recovery (which eventually became pointless since I had to do both to flash roms anways lol) but at the beginning I was trying to use something simple.. while googling I stumbled upon this http://www.kingoapp.com/ and rooted from there.. it's like a one-click root kind of thing and seems to keep the root working regardless.. maybe you wanna check it out and see if it helps, in case you loose your root again. If you wanna run your phone stock but rooted, at least after doing the restoration via keys you'll keep the stock samsung recovery.
Hope it helps!
Click to expand...
Click to collapse
Thanx for that link/suggestion. I didn't see Note i717 listed under supported devices. Did you if this app supports rooting the i717?
jayinc11 said:
Thanx for that link/suggestion. I didn't see Note i717 listed under supported devices. Did you if this app supports rooting the i717?
Click to expand...
Click to collapse
I know, it doesn't show our device, but I kind of went with the home page "root all devices" statement they had and it worked perfectly fine. I did the same with my sister's Note 2 t0ltetmo which is in fact a canadian Videotron phone I gave her and worked fine too. I do not believe that that Note 2 is in the list either, but it still worked
wavv.drama said:
I know, it doesn't show our device, but I kind of went with the home page "root all devices" statement they had and it worked perfectly fine. I did the same with my sister's Note 2 t0ltetmo which is in fact a canadian Videotron phone I gave her and worked fine too. I do not believe that that Note 2 is in the list either, but it still worked
Click to expand...
Click to collapse
Hey it worked some - I decided to test it on my old Captivate. The only thing is it doesn't install CWM/TWRP or similar. So I cannot install a custom ROM. Is it not supposed to install a custom recovery? If not how do I do that having rooted with Kingoapp?
Thanx again for suggesting this app.
jayinc11 said:
Hey it worked some - I decided to test it on my old Captivate. The only thing is it doesn't install CWM/TWRP or similar. So I cannot install a custom ROM. Is it not supposed to install a custom recovery? If not how do I do that having rooted with Kingoapp?
Thanx again for suggesting this app.
Click to expand...
Click to collapse
My pleasure, and glad to hear it worked! And no, lol, sorry. The app only roots your phone, but it does not install a recovery. The good thing about it is that at least you can run stock and use any rooted apps, like I do with my Asus HD7 (for which, unfortunately I haven't found either a custom recovery or a custom ROM to flash, so I run it stock but mess around with root apps)
However..
I looked into this Galaxy Captive thread: http://forum.xda-developers.com/showthread.php?t=2547997 and didn't find a recovery itself that could be downloadble.
So while googling I stumbled upon this: http://true-android.blogspot.ca/2013/10/how-to-install-custom-recovery-in-most.html.
I my english is good enough to understand, it would seem as if the goomanager app allows u to install recoveries directly from your phone, so you could maybe try if you wish.. If u do, please let us know how it worked, as I'm sure others also would benefit from this.
If you want a CWM recovery for either the Note i717, the Note2 T889 or the S2 T989 let me know and I'll upload them, as those are the only ones I have ATM.
Cheers!