Database Info

[Q] Showcase- cant root after installing CM7

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).

SuperSU

Hmm, I wonder if devs will start packaging this in their ROMs instead...
http://forum.xda-developers.com/showthread.php?t=1538053
I'd like to report that I've been using it all day with no issues. Anyone else?

estallings15 said:
Hmm, I wonder if devs will start packaging this in their ROMs instead...
http://forum.xda-developers.com/showthread.php?t=1538053
I'd like to report that I've been using it all day with no issues. Anyone else?
Click to expand...
Click to collapse
I've seen it but never thought of trying it. Might include it in a experimental black ice build
If I helped, give thanks, if you please.
........Death before dishonor........
Team inferno
Leader

I'm using it right now.
I added it in my Kang instead of superuser.
Everything is working as expected.
Sent from my HTC Panache / Darkside CM7.2 using xda premium.

SprigganMaster said:
I'm using it right now.
I added it in my Kang instead of superuser.
Everything is working as expected.
Sent from my HTC Panache / Darkside CM7.2 using xda premium.
Click to expand...
Click to collapse
Nice. Yeah I haven't had a single issue.

Anything with Black Ice would be great..although I cant imagine it being better! I dont know why, but Ive tried most of the top roms from the dev section, & i absolutely love Black Ice and what it has done in terms of performance! My phone is snappy as it has ever been..
Sent from my Black Ice'd Glacier using xda premium

I've tried to run this on my Desire S with Endymion and every time I open it it says...............
"There is no SU binary installed and SuperSU cannot install it. This is a problem!"
Any ideas?

Did you uninstall super user app you had before you tried to install super su? I believe someone on the original thread had that happen and that was the problem. Worth a shot

Andy3105 said:
I've tried to run this on my Desire S with Endymion and every time I open it it says...............
"There is no SU binary installed and SuperSU cannot install it. This is a problem!"
Any ideas?
Click to expand...
Click to collapse
Did you flash the zip (found in the supersu release thread) in recovery, or just install from the market?
Just getting it from the market won't install the binary needed.
The zip also deletes the SU app and binary. Its the best method for installation.

johnson8cyl said:
Did you uninstall super user app you had before you tried to install super su? I believe someone on the original thread had that happen and that was the problem. Worth a shot
Click to expand...
Click to collapse
I didn't uninstall the original Superuser app that came with rom first, no, I have just tried to and it won't let me.............????
estallings15 said:
Did you flash the zip (found in the supersu release thread) in recovery, or just install from the market?
Just getting it from the market won't install the binary needed.
The zip also deletes the SU app and binary. Its the best method for installation.
I did flash the zip files via recovery but it didn't uninstall the original SU app, any ideas?
Click to expand...
Click to collapse

Obviously, you can't uninstall system apps in the usual way. You need to use something like Titanium backup, or use ADB shell.

Ok, so I went into Root Uninstaller and uninstalled the standard Superuser app but I still get the same message, what is really weird is that whenever an app launches that requires superuser access that Supersu screen pops up and everything works as usual.........
Obviously it's working but I still get that same damn message.......

Andy3105 said:
Ok, so I went into Root Uninstaller and uninstalled the standard Superuser app but I still get the same message, what is really weird is that whenever an app launches that requires superuser access that Supersu screen pops up and everything works as usual.........
Obviously it's working but I still get that same damn message.......
Click to expand...
Click to collapse
Use root explorer or es file manager to copy /system/xbin/su to system/bin/

estallings15 said:
Use root explorer or es file manager to copy /system/xbin/su to system/bin/
Click to expand...
Click to collapse
I rolled back to my previous backup and installed from the Market as recommended in the Supersu thread and did what you said but it still happens.....

Then I'm out of ideas. I'm sorry.

SuperSu vs Super User

I have find a new supersu here
http://forum.xda-developers.com/showthread.php?p=23427715
It is working good so far. Is it possible to remove the original super user bundeled with the custom roms. Or it can get some bad effect on custom rom.

Yerp saw this back in march...see it's been updated....:thumbup:
Thx

Probably not that great. Superuser is used universally for a reason.

wayzata said:
Probably not that great. Superuser is used universally for a reason.
Click to expand...
Click to collapse
guess you know this because.....
Actual it is....but you prob installed it and ran it huh?

I have deleted the /system/app/SuperUser.apk through Root Explorer
SuperSu is working fine.
(It should only be done after installing SuperSU from the market, then run it a popup will come up asking to update binary say yes.)

Bought it a while back to support Chainfire.

wayzata said:
Probably not that great. Superuser is used universally for a reason.
Click to expand...
Click to collapse
And you would be wrong. SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted. (This was a pain for me for CM9 work when combined with their new "don't default to root in ADB" policy. ADB not going straight to root + broken su = pain)
Most I9100 and N7000 firmware developers have switched over, and when on Touchwiz firmwares I have too. Superuser's one advantage - it's open source which is why it is in CM9, I don't believe SuperSU is.

Entropy512 said:
And you would be wrong. SuperSU comes from a well respected developer (Chainfire), and was created because Superuser has some major bugs that ChainsDD still hasn't fixed - such as su crashing if Android wasn't fully booted. (This was a ****ing pain in the ass for me for CM9 work when combined with their new "don't default to root in ADB" policy. ADB not going straight to root + broken su = pain)
Most I9100 and N7000 firmware developers have switched over, and when on Touchwiz firmwares I have too. Superuser's one advantage - it's open source which is why it is in CM9, I don't believe SuperSU is.
Click to expand...
Click to collapse
Would you recommend using SuperSU over superuser in CM9?

stratatak7 said:
Would you recommend using SuperSU over superuser in CM9?
Click to expand...
Click to collapse
Not in CM9

Entropy512 said:
Not in CM9
Click to expand...
Click to collapse
so for any ROM other than cm9, you recommend it? and if so, how would you recommend we install? i assume we need to install it first, then update, then delete the "regular superuser"?

TDuran said:
so for any ROM other than cm9, you recommend it? and if so, how would you recommend we install? i assume we need to install it first, then update, then delete the "regular superuser"?
Click to expand...
Click to collapse
Just for kicks, I installed it and tried it. This probably isn't the "proper" method and you could possibly mess something up but anyway here is what I did: 1. Delete superuser.apk from your app folder in /system. 2. In Play store download superSU and install. It will ask you to update binaries. Do it and you should be golden.
**Delete files at your own risk** I used Root explorer and make sure you mount app folder as r/w before deleting and then put it back to normal when you're done.

failed... on galnet miui.. time to reinstall old SU

I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them

Working great for me on the infuse and the nook. Both cm9. CF is a great dev.
Sent from my NookColor using Tapatalk 2

ndhanta said:
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Click to expand...
Click to collapse
Yes. Many Rom devs include SU.
Sent from my Emancipated Infuse having Communion.

ndhanta said:
I have flashed the infusion kernel and old super user came back again. It means rooted kernel got Super User pre-packed with them
Click to expand...
Click to collapse
This is one of the reasons I removed autorooting from my kernels.
In my case, I just flashed the CWM-flashable SuperSU package in CWM - It will automatically remove legacy Superuser I believe.
I personally would like to see it in CM9 (or at least the Superuser problems that caused Chainfire to write SuperSU fixed) - but I believe that the free version of Superuser is open source while SuperSU is not (I could be wrong about this).

I am not getting any source information of SuperSu. It seems closed source.

Entropy512 said:
This is one of the reasons I removed autorooting from my kernels.
In my case, I just flashed the CWM-flashable SuperSU package in CWM - It will automatically remove legacy Superuser I believe.
I personally would like to see it in CM9 (or at least the Superuser problems that caused Chainfire to write SuperSU fixed) - but I believe that the free version of Superuser is open source while SuperSU is not (I could be wrong about this).
Click to expand...
Click to collapse
SuperSU is free on the market (there is also a $$ pro version). I'm seeing the same thing ndhanta is with the infusion kernel. There is a script called install_su.sh which does the old ef su install but I haven't been able to track down the parent script that calls it, or figure out where the $source and $dest variables are being set... I'm assuming it may be possible to stop the script from performing the su install by changing the modify date of the file specified in the $dest var.
Any chance a version of the 4.4.12 GB kernel might materialize that supports OC? (Or an update to the infusion kernel that removes the su installer?) This would help eliminate the issue...

I just Re-rooted my SGS2 and I now have SU and SuperSU ??
Im assuming that SuperSU was installed automatically with the root ROM??
I have puirchased the Pro Version of SU .. so is it safe to Remove SuperSU without messing something up ?

Yes no problem
Just update the binaries of SU.

Help with wiping and/or reinstalling busybox

Hey guys and gals,
I've got a 7.7 on stock ROM rooted using the original root method the day I purchased the tablet. I've been using my tablet happily for over a month now.
Unfortunately, late last night I opened up Google Play and started updating all my apps, including Busybox by stericson. There was a new busybox version out (1.20.1) and I decided to install it using "Smart install." I'm not sure if it tried to install to /system/bin or /system/xbin but after the install I saw the app give me an error message explaining that the install was unsuccessful. Anyways, now a lot of my root-requiring apps including Titanium Backup Pro is not functioning at all. It seems that my BusyBox installation is corrupt.
I tried using BusyBox Pro by stericson to uninstall but the corrupt busybox seems to have prevented a proper uninstall, so it still lingers. I downloaded JadeEyedWolf's root.zip from his pinned "Root" post which includes SU & BusyBox thinking that installing the root.zip from CWM Recovery would over-write the corrupt busybox. After flashing I rebooted the tablet and I still got the same corrupt busybox issues.
Anyone have any suggestions?
Thanks!
Edit: The corrupt busybox causes the Wifi to show Error when I try to turn on the radio. Not that internet is vital in repairing the tablet, but I've worked around it by tethering Bluetooth internet off of my OG HTC Evo 4G. It's strange though - I can peruse websites and view the items in the Google Play Store but it will never actually download, though the "Downloading --- " bar does display.

I had the same problem, stock rom as well. If you check the reviews for Stericson's Busybox on Google Play, the two top ones a few minutes ago both mentioned the same issue.
Trying to root again and reinstalling Superuser didn't help, neither did a factory reset (manually salvaging settings and data was a pain too).
Re-flashing the original rom fixed it, following the guide at http://forum.xda-developers.com/showthread.php?t=1469635
I switched to JRummy16 Busybox installer and it seems to work.
Surprising that no one else here mentioned the problem ...

Try this fix.

To be more specific: BusyBox installer 8.0 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Installer 8.1 and above has this bug fixed.

Had the same problem with busybox and had to re-install the rom. What does this fix do?
Sent from my GT-P6800 using xda premium

Already answered, see post above.

Deleted
Sent from my GT-P6800 using xda premium

Too late for me to try it, but thanks the same

ginkage said:
To be more specific: BusyBox installer 1.20.1 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Click to expand...
Click to collapse
Thank you so much it works well now! You're a life-saver ginkage. Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Thanks again!

Thank you so much it works well now!
Click to expand...
Click to collapse
That's why we are here.
Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Click to expand...
Click to collapse
Personally I always use /system/xbin, so that some custom kernel (like CWM) could use /system/bin if it wanted to.
BTW, the BusyBox installer bug was fixed in version 8.1, and current version is 8.2, so you should update it anyway. I was wrong to mention "1.20.1" version. Post edited.

Hi guys,
First of all, I want to apologize sincerely for the bug that my application introduced in 8.0. I didn't catch the bug because my device wasn't affected by the bug.. (I always test my app myself before releasing..yet I still miss things due to devices file structure being so different.)
At any rate, the bug was that the application symlinked all applets to Busybox. Normally, this is done if you use smart install and change the settings manually. By default smart install will not overwrite applets that are not already symlinked to Busybox.
This was not a problem with Busybox 1.20.1 but was a problem with my application and how it performed the install.
Again, I am very very sorry that this has occured, as a result I am scouring the web trying to find people with the issue and help them resolve it.
If you have this problem, it can easily be fixed by reflashing your current rom. you do not have to wipe or clear any data. Once this is done, you can download my installer, version 8.1 or greater and upgrade busybox as normal.
Please let me know if you guys have any questions.
Best Regards,
Stephen - Stericson

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Deleted

I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.

ninpo said:
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
Click to expand...
Click to collapse
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way

regius said:
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
Click to expand...
Click to collapse
A thousand thanks kind sir, I'm back in business, that was pain free
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thanks for posting this, I'm in love with my 7.7 once again.

Appreciate the response stericson. I had purchased your Pro version but even after I fixed the uninstall failed and it also did not detect superuser permissions even though SU gave a notification that Busybox Pro was granted superuser. All other root-requiring apps work. Had to refund the Pro purchase though

No problem. there seems to be an issue with the application detecting root sometimes, that's why you can still try the install.
I'm looking into this issue, it just started showing up so I am not sure what is going on.

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Really appreciate this fix. On the verge of wiping out everything....
But decide to see if its busy box since its the last thing i install before all this happens....
Just to note that uninstall busybox also doesnt solve the issue...
so need to fix.

I had a lot of problems with root permissions not being granted by Superuser app. Recently I have tried SuperSu from the market and uninstalled original Superuser app (important to follow the instructions for the App! ).
My main problem was that ntfssd was not granted root permissions at startup, so I had to start it again manually. With SuperSu it is no problem. Also I use Busybox and successfully updated to the latest binary recently.

ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thank you so much for that, I had been driven crazy and had also gone through a factory reset to try and get my device back working, to no avail. Can I ask where you got the ash you're including here? It worked for my Samsung Galaxy Tab 7 Plus, on 3.2, but is it a generic enough file that it can be dropped on nearly all Android devices without any issues arising?
I only ask out of curiosity and understanding the system more.

[Q] [SOLVED] Problem with root since update to Stock JB 4.1.1

Hello,
I used "OTA RootKeeper" too "save" my root, and then updated my phone.
I had to re root manually, and since this moment when I try to install busybox or to update su binary my phone reboots.
I tried to manually remove the root (by removing the Superuser.apk and su files), to wipe /data, dalvik_cache, cache etc...
Nothing seems to solve the problem
Does anyone have an idea?
Thanks for your answers!
(Sorry for my English I'm French )

Yep, the jb update has a kernel that write protects /system, at least for the One x and Droid DNA

Is that to say Hassoon's toolkit won't work on a JB updated device?
I've just updated and I'm regretting every minute that I've used it since....

RootJunkie said:
Is that to say Hassoon's toolkit won't work on a JB updated device?
I've just updated and I'm regretting every minute that I've used it since....
Click to expand...
Click to collapse
That means root doesn't really exist on jb.. even if you install su, any changes made will be undone at a reboot

absolutelygrim said:
That means root doesn't really exist on jb.. even if you install su, any changes made will be undone at a reboot
Click to expand...
Click to collapse
What to do?

Actually the phone gets rooted fine busybox is installed, checked with Root Validator after several reboots, but it seems system partition, or something else is not mounted with write privileges.
S-On ?? Maybe? I'm not a HTC guy....

mihaiolimpiu said:
Actually the phone gets rooted fine busybox is installed, checked with Root Validator after several reboots, but it seems system partition, or something else is not mounted with write privileges.
S-On ?? Maybe? I'm not a HTC guy....
Click to expand...
Click to collapse
System is write protected.. due to the kernel, you need s-off or a different kernel, and seeing as there is no kernel source, ICS or aosp are your options. Try making a folder in /system, it should be gone after a reboot

But the files I create from TWRP recovery aren't removed after a reboot. The Superuser.apk is still here after a reboot.
So it seems that I can write to /system from recovery.
Do you know if there's a flashable zip for busybox?

I flashed the one in the JB discussion thread... I think it contains Busybox and SU and it works like a charm... It's a problem but there are workarounds...
For me everything works as long as it doesn't write data to system .
AdBlock works, it gets SU rights but it cannot write the hosts file... I will try later to use the symlink solution...
Su + Busybox
WAY LATER EDIT:
System Partition RW on JB stock roms via kernel module

mihaiolimpiu said:
I flashed the one in the JB discussion thread... I think it contains Busybox and SU and it works like a charm... It's a problem but there are workarounds...
For me everything works as long as it doesn't write data to system .
AdBlock works, it gets SU rights but it cannot write the hosts file... I will try later to use the symlink solution...
http://forum.xda-developers.com/showpost.php?p=35907661&postcount=1928
Click to expand...
Click to collapse
I just tested it and everything I used before on my phone is working again and no more unwanted reboot
Thanks a lot !

I sent a PM to TeHashX, he was asking for review on his work, and also thanked him... His work could benefit others... so make his post more visible!
Remember, that because of the kernel, AdBlock still doesn't work, basically every program that modifies /system works but only apparently. I could use Titanium very well, only Integrate in Rom option doesn't work so take care using "ROOT" on HOS JB.