Hi Guys.
I'm a noob trying to root my Chacha. This phone is a parrallel import, language options are Singapore English and Thai, the plug is a euro 2 round pin and it was unlocked for carrier.
I bought an XTC clip and S-off is done. So far so good.
Then I followed this guide here: http://forum.xda-developers.com/showthread.php?t=1184118
But when installing Titanium backup (with the intent of removing facebook etc) I get the message that Titanium cannot get root access. Usually preceded by a superuser error and forceclose or report options.
Typing "su" into a terminal window gives me "permission denied".
So I went back to the very good guide here: http://forum.xda-developers.com/showthread.php?t=1184118
and I noticed I get the following messages when installing PH06img.zip. "No image" followed by "no image or wrong image".
Any ideas?
Hmm, you have stopped reading the thread after the first two posts.
There is a problem with superuser (the application itself is buggy). Go to Market and update superuser to latest version. That should fix everything.
Otherwise you'll have to use the complicated method (re-flash stock, reinstall CWM, superuser, start superuser, start Titanium).
Superuser has updated itself several times (it comes up with a random, "that was cool, do it again" loop) and ends up on version 3.0 (binary).
But that doesn't seem to help. I'm still getting (process com.noshufou.android.su) has stopped.
Titanium still tells me it can't acquire root privilieges as well.
I've tried clearing the app data to fix the force-close but with no success.
Is there a walk through for the complicated method? TIA.
Is SU 3.02 or 3.04 worth a try?
Yeah, that's the version. Not only the binaries, the application itself needs updating. Get the latest one from market.
Haha, I have it. After 12 hours.
Superuser 2.6.3 worked. I found the files here: goo-inside.me/superuser/
The latest version is no use at all. I had been trying with 3.0.5
Weird. 3.0.5 Should work fine.
Superuser is a GREAT app but latest update is horrible. Blocks all rooted access apps and causes major forces closes and freezes. I emailed the developers with NO reply. Had to move Su to my SD card and uninstall it entirely. Guess its a waiting game now.
Sent from my EVO 4G running R3CHARED ROM using XDA Premium App
Am I the only one with fully functional superuser? I've set it to auto-allow access from preferences.
Alex, which phone do you have? Do you have access to Market, Titanium, spare parts etc......?
Sent from my EVO 4G running R3CHARGED ROM using XDA Premium App
It is very strange indeed.
I tried the 3.0.5 version install about 5 times over 8 hours. Interspersed with trying everything else I could google up. No luck, same force-close result each time.
Then I started trying 3.0.4 and 3.0.2 with no luck, eventually I found in that very long SU thread a reference to 2.6.3. So I found it on goo.inside.me and it worked.
Related
would have just asked in :
http://forum.xda-developers.com/showthread.php?t=1142872&page=67
but i don't have enough posts, and don't want to spam a bunch of useless "cool" posts to get my count up.
Anyways,I did every thing in that topic and have CM7 running fine on my Cell South Showcase. But, i don't seem to have root access superuser is there but seems to do nothing. i tried checking via the terminal with just a "su" command and got nothing. Tried Superoneclick (my go to rooter for awhile) and it just hangs at "looking for device" . and, Z4 seems to not work with 2.3.4 phones.
So is there any fix to this, or have i just hit some crazy bug?
I have seen some people allude to changing the kernel, but the last time i tried to upgrade/change the kernel on this phone i had to save it via odin
Don't you HAVE to be rooted in order to run cm7?
i know, it breaks all logic
i just know i cant grant superuser to anything, busybox installer says it isnt rooted, and Titanium cant do anything
thenumber5 said:
i know, it breaks all logic
i just know i cant grant superuser to anything, busybox installer says it isnt rooted, and Titanium cant do anything
Click to expand...
Click to collapse
Clear data on superuser app and/or uninstall/reinstall it.
Ah,I see.. yes, try above. If no. Maybe wipe and reflash?
ok cleared the data, did nothing
can you ever uninstall/reinstall superuser?
thenumber5 said:
ok cleared the data, did nothing
can you ever uninstall/reinstall superuser?
Click to expand...
Click to collapse
Yup just an app
Also:
i have already flashed via Odin back to stock once and did the whole CM7 flash again from a fully clean rom
ok, Flashed Superuser 3.0 beta 3
no go, says my SU binary is out of date, and the app crashes when it tries to update it
checked my bin and xbin, both have a "SU" file in them
in terminal when i CD in to both folders and try to run "SU" i get an error that looks like it is trying to relocate a library and failing to do so
Can i just download the new SU binary my self and manual drop it in to the folders?
well that didnt work, cant modify anything in the system folder so i cant delete that old "SU" and replace it with the one from the superuser 3.0 apk
LOL
well i got it to let me replace the SU in /bin but not in /xbin
so now i got some half confused phone, i can grate Superuser "superuser" but when it tries to update or do any thing the log says "gaining root access....fail"
i still dont know how i have have a CM7 phone that by it very nature is rooted that thinks it is not rooted
ok for anyone who cares, i just gave up flashed via odin back to stock and tried the MIUI port, worked great once i fangled MMS in to working again
I had a similar problem, at which point I grabbed stericson's busybox app from the market which allowed me to flash a working busybox which after a reboot or two and running the installer again fixed me up..there is an app called root checker that can give info on su, superuser.apk, and busybox installs
I am almost positive that when I used jrummys busybox installer our killed root access on my phone. I had superuser.apk but without busybox it was rather useless as no apps could get root. the fix was flashing busybox 1.19.0 and leaving it in xbin and letting the app do its thing once I had rebooted.. then I rebooted again and everything was fine! after bring rooted for so long I don't think I could function without it!
for others out there, my experience has been this: stay weary of the jrummy busybox installer...its never given me anything but problems...and honestly unless busybox is borked, or ya have a damn good reason to upgrade or downgrade my suggestion is to leave it! the potential problems that can arise (for me every time, using jrummy's version..3 times) can be a pain!
Sent from my SCH-I500 using XDA Premium App
i had the same issue but dont recall if it was CM7 that did it or not but i think it was.
i had to completely blow out the phone and start from scratch.
if i recall, CM7 uses a different version of SuperUser and it just want bonkers on me but completely blowing everything out reformatting and everything seemed to work.
If you're on CM7 already, you should be rooted. If not, try SuperOneClick (Google).
I got my HTC One X about a week ago now for AT&T. Almost immediately, I tried rooting but ran into an odd issue.
Before rooting I had installed Apex launcher. There is an option in the settings to enable Root Helper, which previously would give an error message of something like, "This device does not have root access"
I went through the rooting procedure as detailed here on my mac. The script didn't work at first until I realized I had to switch it to Unix from DOS (Didn't look at the script before running) after I fixed it, it ran and rebooted twice and everything looked normal. Now I tried using the apex root abilities and it just froze and crashed.
So I booted up windows and tried using that to root, but the exact same thing happened. It seems to recognize my root, but not actually give any permissions.
I've tried using other root apps such as uninstallers,titanium backup, etc and all of them just freeze when trying to get elevated permissions.
Is there something wrong with my phone or the way I did the root?
Have you tried clicking on the su app? I had to upgrade mine.
Sent from my HTC One XL using XDA
Yea load up the Su app and ugrade binaries. That should fix the issue. Ive had issues like this on other phones.
You could also try running paulobrien's root method. That's what I used, and my phone's good.
jason.hamilton said:
Yea load up the Su app and ugrade binaries. That should fix the issue. Ive had issues like this on other phones.
Click to expand...
Click to collapse
I've also had a situation where the Busybox version installed on a custom ROM on my HTC Flyer tablet interfered with some apps (like Titanium). Make sure Busybox is up to date. I even had to install a different Busybox installer in order to get it to work right on my Flyer in that particular instance. I had to use the JRUMMY16 version in the market, and not the Stericson installer (which seem the most popular).
No packages were installed with the root.
I'll try using paulobrien's method later and hopefully that will work.
THE BACKGROUND:
I am running stock rooted US .29 on my UnLocked TF300T. The first time I rooted I did the downgrade, rooted and used Voo Doo RootKeeper and then updated OTA to the current FM.
Things were running kind of slow, and I knew that I wanted to start using ROMs once they became a little more stable. So I decided to unlock my device, install CWM and use the "root-signed.zip" to flash root with CWM.
Everything was working fine. I then tried a custom ROM, and it was a little too rough for me. I am not experienced to be testing bet ROMs yet. So I flashed back to the stock FM (.29) and then rooted again using "root-signed.zip".
THE PROBLEM:
The problem is that the Liberty ROM Toolbox Pro isn't fully functioning. I have tried re-installing it, re-installing my FM and rooting it different ways, etc., etc...
No matter what I do, everything seems to work in the ROM Toolbox except for that I cannot:
- Uninstall ANY Apps (system, root, or DL'd Apps).
- Can't make any changes in the "Auto Start Manager".
When I try to uninstall an App:
- The "Super User" notification pops up like normal saying that ROM Toolbox had been granted permission.
- The ROM Toolbox notification pops up like normal showing that it is being un-installed.
- Then it all stops like it normally does except for that the App still remains there.
- Also, a RED bar slides up from the bottom (of the window in ROM Toolbox) saying that the un-installation "failed".
When I try to change things in Auto Start:
- The exact same thing that happen in App Manager. Nothing changes and the red "failed" notification bar pops up.
THE QUESTION:
Why is this happening in ROM Toolbox when all of my other Root Apps are working fine?
What can I do to fix it?
Thank You
-h3llsdr0id
I'm not sure what is going on to be honest. I have tested this on all my devices and they are all working.
I'm guessing maybe the pm command is somehow not working properly on your phone. In the App Manager try clicking on details and find the package name you want to uninstall. Then go to the terminal emulator and run the following command:
pm uninstall <package name>
If you get a "success" then it uninstalled correctly. If not, please let me know the output. I do not check forums on a regular basis so please email this to me.
Thanks.
After finally getting my HTC Status (ChaCha), rooted (the first phone I got rooted) with XTC Clip (this is a device to unlock the bootloader and carrier lock on HTC phones), ClockworkMod, and SuperUser. After updating it that night, the apps I had granted root permissions stopped being able to use root functions (like ES Explorer's root read/write function) or not all, except for AdFree, which continued to keep most ads at bay. Now SuperUser no longer shows any apps listed, and attempts to update the binaries but gets stuck at "Gaining root access" and crashes eventually. The Update Fixer program gets stuck at 'Waiting for root access', not unlike Titanium Backup Pro, which is stuck at 'awaiting root access'. I also tried Super Super User as well, and it was stuck on "The SU binary needs to be updated. Continue? Installing, please wait ..." After more than an hour of waiting, I quit. Same for SuperUser Update Fixer. I also uninstalled the SuperUser update and found that didn't fix anything. I reinstalled Titanium Backup Pro too, same results. I have read that some folks have had success installing Busybox (separate from Tiny Busybox that is part of SuperUser), but I don't see how I would install it if I can't get root permissions! After reading the comments posted on Google Play about SuperUser following the update, I can see plenty of people have had various sorts of problems with SuperUser now. Any thoughts on how to remedy this, besides badgering the author of the software? (I did post feedback to Google Play, nothing hostile or anything, trying to be as precise as possible.)
I'll start out by saying I'm a total noob at this whole android rooting process, hence why I'm posting a thread here rather than posting a reply in the appropriate thread. I rooted and unlocked my phone using this guide: http://forum.xda-developers.com/showthread.php?t=1762709&nocache=1
I opted for the "flashing rooted stock ROM" option.
As the title of my post states, after installing CM10.1, I open superuser to update binary and everything appears to work fine until the very end, it reads "making sure new su works...fail!". Now when I restore back to rooted TW, I have no problem updating the su binary. I've tried Superuser update fixer, I've installed busybox; i cant find any other solution on Google. Any ideas?
The CM file I downloaded is: cm-10.1-20130714-NIGHTLY-d2vzw.zip
Gapps file is: gapps-jb-20130301-signed.zip
Liam1987 said:
I'll start out by saying I'm a total noob at this whole android rooting process, hence why I'm posting a thread here rather than posting a reply in the appropriate thread. I rooted and unlocked my phone using this guide: http://forum.xda-developers.com/showthread.php?t=1762709&nocache=1
I opted for the "flashing rooted stock ROM" option.
As the title of my post states, after installing CM10.1, I open superuser to update binary and everything appears to work fine until the very end, it reads "making sure new su works...fail!". Now when I restore back to rooted TW, I have no problem updating the su binary. I've tried Superuser update fixer, I've installed busybox; i cant find any other solution on Google. Any ideas?
The CM file I downloaded is: cm-10.1-20130714-NIGHTLY-d2vzw.zip
Gapps file is: gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
Make sure your using the latest version of the Superuser app, another option would be to try using SuperSU as an alternative to the Superuser app. Also is root access functioning normally for you?
Sent from my SCH-I535 using xda premium
Hi and thanks for the reply.
Yes superuser is up to date and I've tried supersu. Root seems to be functioning as I can open apps that require root access.
But when I try to restore missing apps via titanium backup, I get a msg saying "restore finished, 'x' elements failed". X being the number of apps I try to restore
Sent from my SCH-I535 using xda app-developers app
Check to see if the root apps are granted root access.
chevyowner said:
Check to see if the root apps are granted root access.
Click to expand...
Click to collapse
When I open SuperSU, it has a list of apps with superuser status. Is that what you mean? I can run root apps and as far as I can tell they're functioning, with the exception of when I try restoring apps with Titanium Backup
Also, right after I flashed CM10.1, I made a backup right away. Not sure if it means anything, but If I wipe/reset and restore the CM10.1 backup, and the first thing I do is try updating the binary in Superuser, it reads "checking installed version: 9 com.Android.Settings", until I open SuperSU and "update binary". Then if I go to Superuser, it'll say "checking installed version: 1.41:Superuser" as I imagine it should. But at this point I still run into "making sure new su works..fail!"
Superuser has no problem updating when I'm on my rooted stock. I'm sure I messed up somewhere along the way while flashing CM10.1, I just don't know where