Hey Folks,
something strange is goin on with my SGS. i installed JG5 by MoDaCo, but i have some Problems. It shows the superuser whitelist app, but whenever i open a root app, it still keeps requesting root, though its already listet in the whitelist. Also i tired to install Clockworkmod via ROm Manager. That worked for one time, now if i boot into recovery, clockworkmod recovery is gone....
what im a doin wrong?
Okay, i found a kernel update that did it. seems like the MoDaCo rom hast a problem with su and stuff!
Thread closed at OP's request
Related
Hi all, i just recently rooted my i9000m (baseband version I9000UGJL2) with psneuter on superoneclick, easy stuff, i came from a desire z so in comparison the root process was much easier, anyways i
went to rom manager, flashed CWM, reboot into recovery, and voila, stock 3e recovery, no reinstall packages option, and apply update.zip not working. What's wrong?
nevermind, searched it on forums, used CFroot
Had the exact same problem, you will need to do this in order to make it work. If you dont have it already download Root Explorer from the Market to apply this fix.
http://forum.xda-developers.com/showthread.php?t=909213
I got a vega today for half price,
So wanted to try out the honeycomb beta rom,
For some reason I could get adb to work from the USB driver zip,
But the drivers for the elocity a7 did work and it installed as android adb device,
Trying to run the windows bat file, kept getting device not found,
I should have tried on my MacBook but instead installed z4root and rom manager,
Rooted with z4root and then ram rom manager,
Installed clockwork recovery and click on the option install rom,
The vega rebooted and installed vegacomb,
It's working a bit sluggish at times,
Now trying to install another rom but rom manager doesn't reboot into recovery when I click that option,
Is there another way to do this???
Or can't I downgrade from vegacomb..
Problem sorted,
Uninstall rom manager and reinstall,
Working fine now
Superuser not work
ROM Manager saying i need to root my phone. Please help completely lost.
Open superuser, hit menu, toggle permissions on, reboot.
And get rid of ROM Manager
Need More help didn't work
I don't use CM, but if it comes with the newest version of SuperUser (3.04 I believe), then that's likely the problem. Uninstall it and install an older version.
R&R SU with one in this link
http://forum.xda-developers.com/showthread.php?t=1297612
I too had thought I lost root access w/ latest SU (3.04 I believe).
Installed 3.0 in above link and everything back to normal now, i.e, root apps functioning normally.
Just be careful not to update app through Market to 3.04; I haven't found a way to stop it prompting me to update. Can't detach from Market via TB because SU doesn't appear in apps list.
i'm on 3.4 with no issues but ive lost root flashing other roms with 3.0. weird
Do what HipKat says.
Hey guys so i got a brand new GT I9500 today and first thing i did was attempt to root it. I've installed CWM + Clicked root device + New Method..
Now after rebooting and what not; Root checker shows that it IS rooter, meanwhile whenever i launch SuperSU it just shows the loading symbol.. Nor can any applications take root access. To top it off, i cant uninstall/update/reinstall supersu from now ..
Any suggestions?
Thanks
EDIT:
As dumb as it may be.. Somehow my SU updated via play store which messed up the binaries. I reinstalled SuperSU from CWM package and voila! Perfect now.
previse said:
Hey guys so i got a brand new GT I9500 today and first thing i did was attempt to root it. I've installed CWM + Clicked root device + New Method..
Now after rebooting and what not; Root checker shows that it IS rooter, meanwhile whenever i launch SuperSU it just shows the loading symbol.. Nor can any applications take root access. To top it off, i cant uninstall/update/reinstall supersu from now ..
Any suggestions?
Thanks
EDIT:
As dumb as it may be.. Somehow my SU updated via play store which messed up the binaries. I reinstalled SuperSU from CWM package and voila! Perfect now.
Click to expand...
Click to collapse
Check this out http://galaxys4root.com/galaxy-s4-root/how-to-root-galaxy-s4-cwm-method/
Or Flash this Custom Auto-root Kernel
I currently have the 4.4.2 Google Play edition rom by Danvdh installed. I was performing a backup to flash the new 4.4.3 through CWM.
After the backup, there was a message that root may be lost and if I should fix it. I selected 'Yes'.
After the reboot, I no longer have root access. I have tried to re-root with motochopper and it continues to fail.
Can I restore a backup to regain my root? Or is there another way to regain my root access?
I tried searching for similar issues but could not find one that addressed my problem specifically.
Thanks in advance.
FIXED!!!
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
tuffgong2k3 said:
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
Click to expand...
Click to collapse
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
sway8966 said:
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
Click to expand...
Click to collapse
Ahhh, thanks sway. I obviously did not find that section. I thought I had the latest CWM, but I guess I didn't. Time to update.