Related
Assuming the phone is already unlocked?
Could not find a way... please help!
Assuming your boot loader was already unlocked, you can use abd to install a custom recovery and flash the latest superuser zip file. The SU zip is on here but I'm on my phone at the moment so you'll have to do a little searching.
That happens. Simply root your phone again using superuser.
Here is the page:
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Follow the part after the how to unlock bootloader.
Thank you, but...
I did that, put again the super user app after flashing the recovery, but it doesn't seem to work.
The super user app is still there, but it doesn't give su permissions...
(for instance, in ROM MANAGER it can't get permissions and also in a terminal doing "su")
Okay are you sure your phone is rooted?
If your answer is yes, click the superuser app. Once in there, there should be a ROM Manager logo in apps. Click that and check your status. The status should be allowed. If not on the bottom left click the button with an android face and a grey line in the middle. That will allow the app. Visa versa if you want to deny. Now just to confirm, go back to your main superuser page. Swipe left to go into log and your recent entry should be allowed for rom manager.
Now heres a tip. Back up your current rom and everything you want. Play around with the settings and apps so you know in the future what "this, that" is. If you stuff up, it doesnt matter. You have a backup. Just restore that in recovery.
dosnt work :/
the allow option doesnt work. perhaps there should be a different su file for
this version...
You may try to uninstall super user and reinstall it again. I had similar issue. And it was fixed by doing so. But I am not sure if it works for you. Good luck, mate.
Sent from my Nexus S using xda premium
danagu said:
the allow option doesnt work. perhaps there should be a different su file for
this version...
Click to expand...
Click to collapse
Google search superuser 3.0.7 and flash it while in recovery. You shouldn't have a problem unless your root process went wrong somewhere.
Sent from my Nexus S 4G using Tapatalk
Thanks!
I installed a new version and it worked
All I've done to it was root it a few days ago. Today I started getting FC's on Instagram, so I rebooted it. Now it is stuck on the GT7+ boot screen, will not go past. I can reboot it, but nogo. Recovery loads, but then it reboots. I CAN get into download mode though.
After searches here, I'm downloading Kies and Odin3-v1.85.zip.
What else do I need? Do I need a file from here: http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-T869&r=5#regiona
??? If so, which one? It's the U.S. T-Mobile 4g GT7+...
Thanks for any help!!! I'm hoping to fix it in the next hour or so before I go to work...
I *can* get to the Power + Volume Down update screen. I am DL'ing the firmware now. What do I do once I get it, how, exactly, do I update/recover it?
Also,
When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application...
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
:crying:
Fixed! It took a lot of work, but I got it. So, here is the question...
I rooted the other day, no custom ROM at all. Could this have been due to that root? That's all I can think of that might have caused this issue. I want to root again, but not sure if I should.
Thoughts?
(and before it's said, yes, it did recover, but I don't want to have to recover it again)
VisualOddity said:
Fixed! It took a lot of work, but I got it. So, here is the question...
I rooted the other day, no custom ROM at all. Could this have been due to that root? That's all I can think of that might have caused this issue. I want to root again, but not sure if I should.
Thoughts?
(and before it's said, yes, it did recover, but I don't want to have to recover it again)
Click to expand...
Click to collapse
Rooting in itself will not cause this as all root is is adding the su binary file to the system bin folder. It doesn't do anything except give you permission to access system folders. Did you also install a custom recovery too? A bad install of a custom recovery could possibly cause it to hang at reboot.
kzoodroid said:
Rooting in itself will not cause this as all root is is adding the su binary file to the system bin folder. It doesn't do anything except give you permission to access system folders. Did you also install a custom recovery too? A bad install of a custom recovery could possibly cause it to hang at reboot.
Click to expand...
Click to collapse
Nope. All I installed root related were Busy Box and Super User so I could use Titanium Backup...
Did you use titanium to remove anything?
Enviado de meu MB525 usando o Tapatalk 2
There was a thread in here about some people having problems with busybox though I have never experienced any problems with it. With so many different versions of this device it possible it could cause problems for some of them.
Ok so one day my phone is all nice and dandy, rooted as a tree, and then I go to Advence Freeze an app, and Rom Toolbox Pro tells me I no longer have root access. So I go into Titanium backup and it says the same thing. For total verification, I go to Terminal Emulator, and the "su" command gives me a "not granted" response. So while I had root yesterday, for some reason I don't have it today. The thing I'm worried about most is that I did absolutely nothing in the meantime. The phone hadn't restarted in 3 days so that wasn't it. And all I did before it unrooted itself iis use the Inkpad Notepad app, and the Boat Browser app. I didn't touch a single thing that could possibly mess something up. Root hasn't always been very "observable" on my phone. After about a week after rooting it, Superuser stopped asking me if I wanted to allow or deny new apps. But all my root apps still worked. I run no special rom, just stock 4.1.2. I have SafeStrap Bootloader installed for backups as well. I downloaded Motochopper to try to reroot my phone just a few minutes ago and the exploit ran flawlessly. No errors whatsoever. When it booted up, still no root access. To be more specific, Voodoo OTA Root Keeper tells me the device is rooted, but without root access. I also have a root backup made with that program. Can someone please tell me how to fix this because the thought of a "normal" phone is making me depressed :crying:.
Try updating your SU and see if that does anything.
RikRong said:
Try updating your SU and see if that does anything.
Click to expand...
Click to collapse
The only way I could think of doing that is from the superuser app (if you mean update the binaries) and I already tried. It fails at "gettingroot access".
miapuffia said:
The only way I could think of doing that is from the superuser app (if you mean update the binaries) and I already tried. It fails at "gettingroot access".
Click to expand...
Click to collapse
Yeah, that's what I meant. Hmmm...
RikRong said:
Yeah, that's what I meant. Hmmm...
Click to expand...
Click to collapse
Perhaps I could backup my data using SafeStrap TWRP, download stock rooted 4.3 (which I wanted since it came out), install it to rom slot 2 using SafeStrap, and then restore my data! Where's my nobel prize? lol Would that work?
miapuffia said:
Perhaps I could backup my data using SafeStrap TWRP, download stock rooted 4.3 (which I wanted since it came out), install it to rom slot 2 using SafeStrap, and then restore my data! Where's my nobel prize? lol Would that work?
Click to expand...
Click to collapse
There is no stock 4.3 ROM for us. The highest stock version would be 4.1.2. You can get CM10.2 that is vanilla AOSP, but I don't know if it would boot on SS.
RikRong said:
There is no stock 4.3 ROM for us. The highest stock version would be 4.1.2. You can get CM10.2 that is vanilla AOSP, but I don't know if it would boot on SS.
Click to expand...
Click to collapse
I see. That's why my rooted 4.3 search came up.blank. I don't mind trying CM. I tried to SS install it previously but it failed (kinda). But now that I think about it I definitely installed the wrong version. As long as I can restore my data to CM I don't mind trying it. Can I get 4.1.2, root it, and then restore data? But wait, I know my bro has 4.3 rooted he used temp unroot -> update -> restore root. Can I do that? In case you didn't notice I'm new to this :/
Hello everyone,
I rooted my Razr HD a while ago, don't remember why. Anyway, I ended up getting a new phone and switching with a friend. And now I need to unroot it so my Mom can use it.
Can anyone point me in the right direction? I know there was an automated tool somewhere but I can't locate it.
Btw, it's rooted with Safestrap. I don't know if that changes anything.
I suggest u to use universal unroot utility by MattGroff and u can uninstall safestrap normally
Sent from my XT890 using xda app-developers app
I would uninstall SS prior to un-rooting because you'll still need to get into the app to uninstall the recovery. It might not let you in if you don't have root access.
RikRong said:
I would uninstall SS prior to un-rooting because you'll still need to get into the app to uninstall the recovery. It might not let you in if you don't have root access.
Click to expand...
Click to collapse
Can you give me like a little bit more detail ? I know Android but I know nothing about the back end of it.
dontsayhate said:
Can you give me like a little bit more detail ? I know Android but I know nothing about the back end of it.
Click to expand...
Click to collapse
If you go into the actual SS app on your phone, you can uninstall recovery. Do this, prior to deleting the app. If you delete the app first, you'll never be able to delete the installed SS recovery because you need the app to do it. Uninstall recovery through the app, then delete the app, and then delete all the SS folders and backups on your internal to get you some memory space back. As for the root access thing, I'm not 100% sure, but I don't think you'll be able to open the SS app if you don't still have root access. It's a root access app but I'm not sure how that would work.
Well it looks like the phone has been set to factory..I turned it on just now, and I think my mom or dad may have done it. It works fine. But there is no SU or SS apps on the phone, I just checked. But when I boot the phone, I still get the bootloader unlocked message. Which means its something in the SD card correct? Any idea how to clean that up?
dontsayhate said:
Well it looks like the phone has been set to factory..I turned it on just now, and I think my mom or dad may have done it. It works fine. But there is no SU or SS apps on the phone, I just checked. But when I boot the phone, I still get the bootloader unlocked message. Which means its something in the SD card correct? Any idea how to clean that up?
Click to expand...
Click to collapse
If your BL is unlocked, there's no way to relock it. However, I know there are some flashable boot logos running around somewhere in this forum. Just find one and flash it in recovery.
RikRong said:
If your BL is unlocked, there's no way to relock it. However, I know there are some flashable boot logos running around somewhere in this forum. Just find one and flash it in recovery.
Click to expand...
Click to collapse
I want to clean the SD card out too though. The message is whatever. Can I do that without screwing up the phone?
dontsayhate said:
I want to clean the SD card out too though. The message is whatever. Can I do that without screwing up the phone?
Click to expand...
Click to collapse
you can go to settings/storage and erase the sd card but that wont get rid of the warning. also, if it was rooted, it still is even though the su app may have been removed.
Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
I always throw my Awaway apk into system/app. Not sure if that actually does anything, but it seems to apply more often than not. I've always had issues with adaway sometimes not applying, so you are not alone.
Myk Robinson said:
Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
Click to expand...
Click to collapse
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
EDIT: I stand corrected.
MultiDev said:
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
Click to expand...
Click to collapse
This. The modified kernel it's being worked on still but I believe it can be found in development
Sent from my HTC6525LVW using Tapatalk
Clarification
MultiDev, if I am understanding, you mean just disable AdAway because it wont work yet until a custom kernel or kernel mod is installed?
Myk Robinson said:
Evening. I had previous installed WeakSauce and SuperSU on my Verizon HTC One M8.
today, I applied S-off, and flashed ClockwordMod Recovery Unofficial.
I installed Root from inside CWM.
However, I still cannot apply host files in CWM. This suggests that I don't necessarily have full root, so perhaps I missed a vital step somewhere.
Little help? That's all i want is proper ad blocking. otherwise, this phone runs just fine with Nova Launcher
thanks,
Click to expand...
Click to collapse
download and flash this in recovery: http://download.chainfire.eu/345/SuperSU/
then open it so it can update (use recovery method when asked to update)
then run adaway
Got it
kwkw480 said:
download and flash this in recovery: http://download.chainfire.eu/345/SuperSU/
then open it so it can update (use recovery method when asked to update)
then run adaway
Click to expand...
Click to collapse
Thanks, it successfully applied after that. Apparently I missed step one in some previous instructions where it said to flash the SuperSU binary.
Last question. I assume at this point, I can uninstall WeakSauce since we have permanent proper root?
I gotta say, this was pretty easy in Linux Mint 16....
Myk Robinson said:
Thanks, it successfully applied after that. Apparently I missed step one in some previous instructions where it said to flash the SuperSU binary.
Last question. I assume at this point, I can uninstall WeakSauce since we have permanent proper root?
I gotta say, this was pretty easy in Linux Mint 16....
Click to expand...
Click to collapse
Yes, uninstall weak sauce
MultiDev said:
Unfortunately, while booted into Android, the stock kernal prevents system partition write access. You'll need to disable it.
Click to expand...
Click to collapse
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Thank you
Thank you all for replying. Nice to have such a fast response.
All this because I missed the first line of the instructions...
If Verizon customer service was as good as the fine folks on this forum....
mchief298 said:
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Click to expand...
Click to collapse
Yeah, I was wrong about that. The system partition is writable after S-off.
mchief298 said:
S-Off'd and rooted through flashable zip. Installed adaway as a system app, and it's running fine here. Nothing else changed or added.
M8, nuff said.
Click to expand...
Click to collapse
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
deeznuts said:
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
Click to expand...
Click to collapse
You don't NEED to, but it is recommended.
M8, nuff said.
This is the one app causing me problems. Adfree works problem free, but AdAway likes to keep getting stuck on "Applying...". I've got it to succeed once or twice by force closing and re-trying, but it's not reliable. I'm S-off, CWM recovery, SuperSU, and the modded kernel with RW permissions. What gives? :?
EDIT: Even tried installing Adaway as system app, problem still persists...???
EDIT2: Finally got it working. Noticed in the OP in the xda thread that there is a modded version to fix problem. All good
deeznuts said:
I also have s-off, uninstalled weak sauce, then flashed through CWM supersu.zip for full root, reboot. Downloaded latest AdAway apk found here on xda forum. I then ran apk file from my download folder, hit install. Open AdAway, click on Download fiels and apply add blocking. Now it just gets stuck on Applying... with the circle going around and around for over 15 minutes straight now! Yes i gave root access when asked. Is this normal?
Nevermind. Closed app, then reopened and it did the download thing like normal. Now says successful and applied hosts sources: 4/4.
So i'm good to go now? Does this need reboot like prompted?
Click to expand...
Click to collapse
Don't need to reboot. I never have and it works fine.
123421342 said:
Don't need to reboot. I never have and it works fine.
Click to expand...
Click to collapse
Thank you
I had to install the unsecure boot image in order for AdAway to work properly. Otherwise it just hangs on applying host files.
From what I understand, just because you're s-off still doesn't mean you have full write access. The stock kernel has the write protection modules built in.
Flashing the unsecure boot image fixed all issues I was having and I'm pretty sure if you're still having problems, flashing that will help
-HTC One m8-
I'm not disputing whether or not s-off provides full write access. But, I was able to install AdAway with full functionality without installing the unsecure stock kernel. It takes a while to download all the data and install it though (maybe 5 minutes or so?). Then, I rebooted and it's working very well. No more ads!