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 :/
Related
So, after learning that Motorola was not going to give us a software update for the Atrix 4G, I decided to take a chance and unlock the bootloader and flash a custom rom. I flashed CyanogenMod 7 Olympus (cm-7-20120923-NIGHTLY-olympus) and I love it! I made a backup of the stock rom and then a backup of CM7 after I had it set up the way I like it for the most part.
My only problem: I lose root access randomly... without rebooting... without doing anything! SU is there, and the superuser apk is there, and they come up as granting superuser permission, but the apps say they don't have access. Even trying to update the binary says "failed" when gaining root access.
I've been scouring forums and the net looking for similar problems. Rebooting doesn't fix it. I've tried downloading and flashing SU 3.1.3 from recovery (wipe cache & dalvik cache, then install from zip), and that didn't work. I then tried the same for 3.2-RC3, and no luck there. I've ran Fix Permissions just to try, and that did not work either. Somewhere, someone posted to reflash the ROM. Instead, I just restored a backup, and it comes back for a few days... then it stops working again.
Any suggestions on how to fix this or what could cause it? I don't mind restoring the backup again, but I'd like to keep it from happening if at all possible.
twomoses said:
So, after learning that Motorola was not going to give us a software update for the Atrix 4G, I decided to take a chance and unlock the bootloader and flash a custom rom. I flashed CyanogenMod 7 Olympus (cm-7-20120923-NIGHTLY-olympus) and I love it! I made a backup of the stock rom and then a backup of CM7 after I had it set up the way I like it for the most part.
My only problem: I lose root access randomly... without rebooting... without doing anything! SU is there, and the superuser apk is there, and they come up as granting superuser permission, but the apps say they don't have access. Even trying to update the binary says "failed" when gaining root access.
I've been scouring forums and the net looking for similar problems. Rebooting doesn't fix it. I've tried downloading and flashing SU 3.1.3 from recovery (wipe cache & dalvik cache, then install from zip), and that didn't work. I then tried the same for 3.2-RC3, and no luck there. I've ran Fix Permissions just to try, and that did not work either. Somewhere, someone posted to reflash the ROM. Instead, I just restored a backup, and it comes back for a few days... then it stops working again.
Any suggestions on how to fix this or what could cause it? I don't mind restoring the backup again, but I'd like to keep it from happening if at all possible.
Click to expand...
Click to collapse
Try going in to Manage Applications and clear su data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
upndwn4par said:
Try going in to Manage Applications and clear su data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Click to expand...
Click to collapse
Thanks for the quick reply. I cleared the cache for Superuser (couldn't believe I didn't think to do that in the first place), and now it will not prompt to grant or deny. I try to update the binary, and it stops at "Gaining root access..." and doesn't show okay or failed. I tried to run the Superuser Update Fixer, and it says that the signatures are okay. When I try to force it, it does the exact same thing as Superuser: it hangs at "Gaining root access..."
It may be worth noting that I have to force-close Superuser the first time I open it after clearing cache. After that, it opens but only does the above mentioned.
twomoses said:
Thanks for the quick reply. I cleared the cache for Superuser (couldn't believe I didn't think to do that in the first place), and now it will not prompt to grant or deny. I try to update the binary, and it stops at "Gaining root access..." and doesn't show okay or failed. I tried to run the Superuser Update Fixer, and it says that the signatures are okay. When I try to force it, it does the exact same thing as Superuser: it hangs at "Gaining root access..."
It may be worth noting that I have to force-close Superuser the first time I open it after clearing cache. After that, it opens but only does the above mentioned.
Click to expand...
Click to collapse
Open a terminal emulator and type su and hit enter. If you don't see #, you are not properly rooted.
upndwn4par said:
Open a terminal emulator and type su and hit enter. If you don't see #, you are not properly rooted.
Click to expand...
Click to collapse
Nothing happens in terminal emulator.
Now my question is, (and forgive my n00bness) since CM7 came rooted, do I follow the normal steps to re-root the phone through adb? I've never seen how to root a custom rom, but that may be because the process is exactly the same.
twomoses said:
Nothing happens in terminal emulator.
Now my question is, (and forgive my n00bness) since CM7 came rooted, do I follow the normal steps to re-root the phone through adb? I've never seen how to root a custom rom, but that may be because the process is exactly the same.
Click to expand...
Click to collapse
Nothing happens? No error ("not found" or "permission denied" or something like that)?
Go to the Play Store and download Root Checker, and check for root with that also.
I don't know the answer to your question since most users root, unlock, then flash a ROM. If it were me, I would try to root as if it were GB 236.
upndwn4par said:
Nothing happens? No error ("not found" or "permission denied" or something like that)?
Go to the Play Store and download Root Checker, and check for root with that also.
Click to expand...
Click to collapse
That is correct. I ended up having to kill the terminal emulator too. It just sits there with nothing displaying.
I ran root checker, and all I get is the loading circle in the middle that says "Please wait for Root Check to complete. System appears to be running very slow." Nothing else was running slow, so I rebooted my phone again.
I don't know what changed, but now I have root again! Many thanks upndwn4par!
My guess is clearing data in Manage Applications did the trick. Anyway, glad it is working!
Another method for checking if you are rooted properly.
EDIT: nevermind, now I see it's been discussed already. :stupid:
Off topic: I seriously want to borrow your signatures tho!
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
USB Debugging stays on usually because I don't connect my phone to a computer I don't know.
When this started, I was still getting the toast messages saying access granted, but it wasn't actually working. Somewhere along the line of steps it started working again tho.
twomoses said:
Off topic: I seriously want to borrow your signatures tho!
Click to expand...
Click to collapse
Absolutely!
upndwn4par said:
Absolutely!
Click to expand...
Click to collapse
Done!
Solved: This fixed my problem!
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
So, props to you Sabbelknoken! I suddenly lost root again the same way I had before. I came back through this thread to revisit my steps, and I found that my USB Debugging was off. (I think I turned it off so one of my computers would stop asking me for the drivers. Not important.) I turned it on and it immediately began working!
Just wanted to concur...
Thanks to Sabbelknoken!! I had this same problem with my Droid Charge running Tweaked 3.0. Nothing was getting root and everything was hanging on "Gaining root access..." I tried SuperSU, re-installing Titanium Backup, Superuser, SuperSU, Superuser Update Fixer, Root checker, I cleared data, rebooted several times...over and over.
Then sure enough, my dang "USB Debugging" was not checked. Checked it, and now I'm happily rooting again. *whew* Thought I was going to have to re-Odin my ROM. Ick.
Thank again everyone!
su losing root usb debug etc
I too get su issues from time to time. mostly with stock roms when i flash a fruitcake or gingerbread. and recently one of the leak roms. just type d su in terminal emulator an got $ instead of #. I hope that means im properly rooted . I have a couple of one click root apps on my computers just incase i need to reroot. one is superoneclick 2.33 shortfuse and the other is motofail. then i make sure to install busybox and upate the binary. i also have su update fixer, superuser elite, and supersu. as well as rootchecker.
two thing I did not know were that 1. usb debugging is not just for transferring files or connecting to the computer. I used to turn it off sometimes and then wonder why superuser had problems. 2. how to see you are rooted by typing su in terminal.
From what i understand the one click methods are not ideal as they do not always work. but I usually try them first . If they are outated and dont work i end up rooting by command prompt. some times it woul take me cloose to an hour trying different things. never knew it was usb debugging turned off that causes most root failures. Did some reading and realized that if i allow su permission for terminal emulator, then type su again i get#. good to know.
activate USB debugging
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
Thanks for that simple tip. I was having the same problem, the "Allow" dialog didn't appear for any application request and Root Checker was only saying: "Device seems to be running really slow"
I was 2 or 3 days looking for the solution to this problem, because it is my first time rooting and I can't believe something as simple as activating USB debugging is not really explained in the rooting guide I used.
I hope that now Titanium and ROM Toolbox Pro work properly.
Hello,
I require some help as my phone has been acting really weird recently. I first bought a Samsung Galaxy S3 GT-I9300 earlier in September that was loaded with ICS. I am currently in Singapore and I got the phone from Starhub.
I attempted to root the phone in ICS, and succeeded in doing so. There were no problems at that point in time.
Recently, there was an update notification that kept prompting me to update to Jelly Bean. There were a few options if I wanted to postpone it: Update now, Remind in 30 minutes, 1 hour, and 3 hours. I found it really irritating, so I eventually just clicked to update it now.
The update went as planned, but when I restarted my phone, my SuperSU refuses to work. When I go into it, it tells me "The SU binary needs to be updated. Continue?" But when I click "Continue", it says Installation Failed! I have tried going to settings, disabling Superuser, and then attempting to use superuser to update the binary. It did not work. When I attempted to disable superuser under settings>SuperSU, it says "Uninstallation failed!"
I attempted to de-root using a guide from GalaxyS3Root website, which told me to download Odin Lite, Odin Kernel and Triangle Away.
However, Triangle Away refuses to work with an error message "Unfortunately, Triangle Away has stopped".
The Odin Lite also refuses to work by saying "Could not detect device model".
Am at a loss as to what to do now...
Tried using Titanium Backup as well, but it seems to be unable to back up my files without using Root.
Please help!!
You have several options. Easiest ones: just backup your stuff and either flash the lastest leak (ELK4) which is already rooted and has extra goodies or simply wipe your phone (get into recovery and factory reset it). Your rom (JB) wasn't rooted to begin with so you won't have root anymore. There's probably a way to do it without wiping but i usually don't bother. It's generally less of a hassle to backup and wipe.
Edit: oh sorry, missed the part where you couldn't backup without root. To be honest, i never use titanium, it always causes problems when i restore stuff. I just backup what i need by hand (sms's with a sms backup app, find my save's files, etc)
Thanks
kaynpayn said:
You have several options. Easiest ones: just backup your stuff and either flash the lastest leak (ELK4) which is already rooted and has extra goodies or simply wipe your phone (get into recovery and factory reset it). Your rom (JB) wasn't rooted to begin with so you won't have root anymore. There's probably a way to do it without wiping but i usually don't bother. It's generally less of a hassle to backup and wipe.
Click to expand...
Click to collapse
Thanks for the speedy reply!
To backup my stuff, I just have to plug my phone to my computer and drag &drop everything, yes?
Sorry I'm very new to the whole android thing, and I'm not very tech-savvy to begin with. When you say Flash the latest leak, how do I do this?
If I factory reset my phone now will I brick it?
That's such an overkill. Just boot into recovery mode and root your phone again with Odin. There are plenty of guides around.
michelleyabc said:
The update went as planned, but when I restarted my phone, my SuperSU refuses to work. When I go into it, it tells me "The SU binary needs to be updated. Continue?" But when I click "Continue", it says Installation Failed! I have tried going to settings, disabling Superuser, and then attempting to use superuser to update the binary. It did not work. When I attempted to disable superuser under settings>SuperSU, it says "Uninstallation failed!"
Click to expand...
Click to collapse
this is because after the update, your phone is no longer rooted.
michelleyabc said:
However, Triangle Away refuses to work with an error message "Unfortunately, Triangle Away has stopped".
Click to expand...
Click to collapse
Triangle Away is not required for rooted, it just resets a counter to 0. nothing very much to it.
michelleyabc said:
The Odin Lite also refuses to work
Click to expand...
Click to collapse
I think the best thing u can do right now is.
1. titanium backup to SD.
2. load a new rom via odin 3.04
3. install cf root to root the phone via odin 3.04
4. install titanium backup and restore your phone.
i know it can be very annoying because all the singaporean ah beng hp shops has no idea now to repair the phone.
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.
Hello! I am an extremely newbie in rooting so this is my issue. I just rooted my S4 I9505XXUGNH8. I used odin and the root file from chainfire. It passed. So I thought there' s no problem but after 5 hours or so, when I lock my phone it restarts. Plus my bluetooth won't turn on. So I saw this option in SuperSU that I presumed will unroot my phone. I clicked it and say yes. I restarted my phone, the said app was not there anymore. Checked root checker and it says no proper root access or something like that so I thought I already unrooted my phone. I tried even SRS Root, it says that my device has no root. But the issues were still there. I tried to create new file from my sd card so I was expecting it will not work because of that Kitkat sd card restriction stuff but it worked. I tried to update my firmware but the phone didn't allow me because it was modified. So reinstall SuperSU again, and it says SU Binary not found, like that. Now I really have no idea what to do. Please help me. Thanks and sorry for my novel like post.
AdamSanJuan said:
Hello! I am an extremely newbie in rooting so this is my issue. I just rooted my S4 I9505XXUGNH8. I used odin and the root file from chainfire. It passed. So I thought there' s no problem but after 5 hours or so, when I lock my phone it restarts. Plus my bluetooth won't turn on. So I saw this option in SuperSU that I presumed will unroot my phone. I clicked it and say yes. I restarted my phone, the said app was not there anymore. Checked root checker and it says no proper root access or something like that so I thought I already unrooted my phone. I tried even SRS Root, it says that my device has no root. But the issues were still there. I tried to create new file from my sd card so I was expecting it will not work because of that Kitkat sd card restriction stuff but it worked. I tried to update my firmware but the phone didn't allow me because it was modified. So reinstall SuperSU again, and it says SU Binary not found, like that. Now I really have no idea what to do. Please help me. Thanks and sorry for my novel like post.
Click to expand...
Click to collapse
Seems like you might have used the auto root package from another firmware version as this sounds like some kernel issues. Since you know Odin works, then you can just reset and reinstall the NH8. This will get everything backup and running again (you can try not wiping, but possible issues can arise from this too - fair warning and best to backup internal storage to PC for safe keeping). As far as rooting goes afterwards, put Chainfire's SuperSU zip on your phone, find an updated custom recovery such as TWRP, Philz, or CWM and install via Odin. Once installed, you must immediately boot to recovery before the OS loads so you can use the recovery to install the zip or the stock system will rewrite the original recovery to it. Then you will be rooted with no other changes to the phone that could affect functionality or usability.
AdamSanJuan said:
Hello! I am an extremely newbie in rooting so this is my issue. I just rooted my S4 I9505XXUGNH8. I used odin and the root file from chainfire. It passed. So I thought there' s no problem but after 5 hours or so, when I lock my phone it restarts. Plus my bluetooth won't turn on. So I saw this option in SuperSU that I presumed will unroot my phone. I clicked it and say yes. I restarted my phone, the said app was not there anymore. Checked root checker and it says no proper root access or something like that so I thought I already unrooted my phone. I tried even SRS Root, it says that my device has no root. But the issues were still there. I tried to create new file from my sd card so I was expecting it will not work because of that Kitkat sd card restriction stuff but it worked. I tried to update my firmware but the phone didn't allow me because it was modified. So reinstall SuperSU again, and it says SU Binary not found, like that. Now I really have no idea what to do. Please help me. Thanks and sorry for my novel like post.
Click to expand...
Click to collapse
The root for I9505XXUGNH8 is there any just one click root and don't have to use computer
Sent from my GT-I9505
Hi,
I bought a Nexus 5 on amazon, and when it came in, it went through the setup process as if it were a brand new phone. However, as soon as it got to the home page, i noticed that SuperSU was installed, and it was in the app drawer. I did not want a rooted phone, so i installed root checker to see if the phone was rooted. Root checker said it was not rooted, so i thought i was safe to uninstall superSU. But when I launch superSU, it gives me a popup that says that there is no supersu binary installed or something, and i can't access the app further than that. Is there any way to uninstall it otherwise? I also went to the play store to uninstall it but it just says that it will uninstall all updates. Also, if i install marshmallow, will that fix the problem? i heard that the OTA update for M will remove root, supersu, etc.
thanks
EvilLemon said:
Hi,
I bought a Nexus 5 on amazon, and when it came in, it went through the setup process as if it were a brand new phone. However, as soon as it got to the home page, i noticed that SuperSU was installed, and it was in the app drawer. I did not want a rooted phone, so i installed root checker to see if the phone was rooted. Root checker said it was not rooted, so i thought i was safe to uninstall superSU. But when I launch superSU, it gives me a popup that says that there is no supersu binary installed or something, and i can't access the app further than that. Is there any way to uninstall it otherwise? I also went to the play store to uninstall it but it just says that it will uninstall all updates. Also, if i install marshmallow, will that fix the problem? i heard that the OTA update for M will remove root, supersu, etc.
thanks
Click to expand...
Click to collapse
did you try settings>apps>
is superSu listed in under downloaded tab?
sd_shadow said:
did you try settings>apps>
is superSu listed in under downloaded tab?
Click to expand...
Click to collapse
yes, it is listed there, and when i click on it, it gives me options to force stop it, uninstall updates, or disable it. But i heard that if i try to install OTA updates on the phone, it will stop halfway cause the updates now check for stuff like supersu
EvilLemon said:
yes, it is listed there, and when i click on it, it gives me options to force stop it, uninstall updates, or disable it.
Click to expand...
Click to collapse
If there is no option to uninstall, it is on the system partition, you will need to root to remove it, or better reinstall stock firmware.
the devices was rooted at some time and it was not unrooted correctly, I would not allow the device to update ota, because you just do not know if stock rom is complete.
But i heard that if i try to install OTA updates on the phone, it will stop halfway cause the updates now check for stuff like supersu
Click to expand...
Click to collapse
yes, that is possible.
see the nexus 5 forum http://forum.xda-developers.com/google-nexus-5
at look for how to restore stock rom
sd_shadow said:
If there is no option to uninstall, it is on the system partition, you will need to root to remove it, or better reinstall stock firmware.
the devices was rooted at some time and it was not unrooted correctly, I would not allow the device to update ota, because you just do not know if stock rom is complete.
yes, that is possible.
see the nexus 5 forum http://forum.xda-developers.com/google-nexus-5
at look for how to restore stock rom
Click to expand...
Click to collapse
I have decided to give back the phone, I really don't want that kinda risky device on me for the next 2 years... however, will i be able to factory reset it before i send it back? or will the phone mess up? (when i initially got the phone, i THINK it was factory reset because i had to go through the default android setup process) i just don't want the next owner to gain any of my information or anything even if i delete everything i have on it so far and disconnect my google account
EvilLemon said:
I have decided to give back the phone, I really don't want that kinda risky device on me for the next 2 years...
Click to expand...
Click to collapse
Yes, that is probably safest option
however, will i be able to factory reset it before i send it back? or will the phone mess up? (when i initially got the phone, i THINK it was factory reset because i had to go through the default android setup process) i just don't want the next owner to gain any of my information or anything even if i delete everything i have on it so far and disconnect my google account
Click to expand...
Click to collapse
factory reset should be safe.
flashing firmware, is what the seller should have done, before shipping