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

busybox not installed properly

i have a samsung epic 4g. iused super1click but it is saying that busybox was not installed properly and now rooted apps are saying i do not have root access but root checker says i have root access please help

download "busybox installer" from the android market. you can install the latest busybox from it

i installed busybox installer but it is sayin it is already installed but not installed correctly

go into /system/xbin and /system/bin and look for the file "busybox." delete it and try installing it again with busybox installer

i have tried that in both system/bin and system/xbin but it will not delete. do i need a specific file management app

nalanotae said:
i have tried that in both system/bin and system/xbin but it will not delete. do i need a specific file management app
Click to expand...
Click to collapse
i forgot to mention that you will need to mount your system as read/write. to do this, a file management app would be very helpful. root explorer in particular (a paid app, but as you may already know there are always ways to get apps for free; that is all i will say about warez as it is prohibited on xda). in root explorer, you can mount your phone between r/w (read/write) and r/o (read only). once you mount it as r/w, i believe you can now delete those files

one other thing i forgot to mention, i keep getting a notification that my su binary is outdated when i click to update it says fail.
ok so i was able to delete the busybox files out of the 2 folders but when i went to install it with the busybox app it says "it looks like busybox is installed but it does not appear to be the version that you selected to have installed, you may want to try the intalation again but this using a different istalation location." i try a different location and check my root checker and it keeps telling me that busybox is installed incorrectly

as i have not used superoneclick before, i have no knowledge about the su binary being updated. i used z4root to root my phone.
your best bet is to do one of the following:
a) if you can unroot your phone, then do so (i believe superoneclick allows you to unroot your phone). then try rooting it again using z4root. download z4root from here and tell me what options it gives you when you open the app (it should say either temporary root and permanent root; select permanent root). z4root should work on your phone as it has the same requirements as superoneclick (which is having android version 2.2/2.2.1)
b) if step a didnt work, post in the superoneclick thread for help. but step a should work

Nexus 5
Rooted
Stock image
Used nexus root toolkit
Busy box crashes when attempting to install from within busybox
Says not installed
Used root explorer to check system/bin
And
System/xbin
No filename that says busybox
Not sure what to do.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
Resolved
Set system to r/w at boot as root.
Launched bb
Says installed

mjs1231 said:
Nexus 5
Rooted
Stock image
Used nexus root toolkit
Busy box crashes when attempting to install from within busybox
Says not installed
Used root explorer to check system/bin
And
System/xbin
No filename that says busybox
Not sure what to do.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
Resolved
Set system to r/w at boot as root.
Launched bb
Says installed
Click to expand...
Click to collapse
I have this same issue on my Nexus 6, i also used Nexus Root Toolkit, how did you set your system to r/w at boot as root?

I am not able to install buzybox due to "try to installing to a different location that may resolve isuue..please help me

I know this is old!
Hello readers,
I am aware that my resolution might not help everyone but it will definitely help some. This might only help if you are rooted and using the SuperSu app..
I know this is a really old thread. But there might still be people out there that have this problem and are having a hard time finding the the answer for it. I was just 5 mins prior searching on google for an answer but could not find one.
And so how did I fix it you may ask? (I hope)
Well long story short I turned the following option of in the SuperSu application: "Mount namespace separation"
I thought of this because I had seen a pop-up message when using Titanium Backup that if I experience problems, I should disable that option. And it was probably referring to the Titanium Backup app alone and not any other. But I gave it a shot and it worked.
In detail for those who need it:
It does not matter if you have the Busybox (by Stephen (Stericson)) application installed during this or not. (I had it uninstalled during)
Open the SuperSu app, swipe left on the screen twice so you get to the Settings page (or just click the Settings tab)
Scroll down until you see the option "Mount namespace separation".
If it is activated, disable it.
Reboot
Go ahead and install Busybox if you haven't.
Open Busybox and wait for it to load completely
Click install
Hurray!

Hello, i have bought busybox pro but i can't manage to install it through the app, in /system/xbin, i only have one file named "dexlist" and in /system/bin i have many files but none named busybox, when i try to install busybox on /su/bin, i get a message: "it looks like the installation of busybox was not successful / try installing it to a different location that may resolve the issue", but i tried differ'ent locations and it didn't work
---------- Post added at 09:03 PM ---------- Previous post was at 08:53 PM ----------
don't forget to reboot after unchecking "mount namespace separation" !! if not it won't work. my phone was quite long to reboot though...
it still doesn't work for me... on huawei p8 lite 2017 (PRA-LX1)

I'm still using the old version not BusyBox V+ .. anyone tried the latest version? it seems quite confusing and I couldn't execute scripts

Busybox
Example if use custom rom viper10 you can set system r/w in tweak > misc

lovemajj said:
Hello readers,
I am aware that my resolution might not help everyone but it will definitely help some. This might only help if you are rooted and using the SuperSu app..
I know this is a really old thread. But there might still be people out there that have this problem and are having a hard time finding the the answer for it. I was just 5 mins prior searching on google for an answer but could not find one.
And so how did I fix it you may ask? (I hope)
Well long story short I turned the following option of in the SuperSu application: "Mount namespace separation"
I thought of this because I had seen a pop-up message when using Titanium Backup that if I experience problems, I should disable that option. And it was probably referring to the Titanium Backup app alone and not any other. But I gave it a shot and it worked.
In detail for those who need it:
It does not matter if you have the Busybox (by Stephen (Stericson)) application installed during this or not. (I had it uninstalled during)
Open the SuperSu app, swipe left on the screen twice so you get to the Settings page (or just click the Settings tab)
Scroll down until you see the option "Mount namespace separation".
If it is activated, disable it.
Reboot
Go ahead and install Busybox if you haven't.
Open Busybox and wait for it to load completely
Click install
Hurray!
Click to expand...
Click to collapse
Hey, really glad you posted this even though you said it was old, and I'm still on it :laugh: but the combo of your solution, and mounting my /system as "r/w" through Root Explorer worked on my 6P on Oreo!! (OPR6)
Thanks again!! :good:

Williquah said:
Hey, really glad you posted this even though you said it was old, and I'm still on it :laugh: but the combo of your solution, and mounting my /system as "r/w" through Root Explorer worked on my 6P on Oreo!! (OPR6)
Thanks again!! :good:
Click to expand...
Click to collapse
What exactly do you mean by "and mounting my /system as "r/w" through Root Explorer" can you explain further? I can't get Busybox to install after OPR6 update

idbl_fanatic said:
What exactly do you mean by "and mounting my /system as "r/w" through Root Explorer" can you explain further? I can't get Busybox to install after OPR6 update
Click to expand...
Click to collapse
I'd be happy to help. It's been a little while and I haven't repeated the process yet so forgive me if I'm not super clear, even though I think I should be.
So what I meant was get the app Root Explorer ($3.99 on the app store) I don't know how 'piracy' is really looked at on XDA, though I can't imagine well, but you can download the Root Explorer 'pro' apk, and then - as long as it helps - purchase the app from GPlay to make sure to support the devs, which is what I did.
So to get to the actual process - should be quite easy as I did this on OPR6 myself - open Root Explorer, navigate to the "root" tab at the top. Then you should see "Mounted as r/o" and right next to it, a button that says "Mount R/W". Toggle that button, and the text on the left should state "Mounted as r/w", then try to install busybox (however you prefer - I used BusyBox Free by Stephen (Stericson) like I always do).
Hope you are successful with that method, please keep me updated with your outcome so I can help as best as I can.

Williquah said:
I'd be happy to help. It's been a little while and I haven't repeated the process yet so forgive me if I'm not super clear, even though I think I should be.
So what I meant was get the app Root Explorer ($3.99 on the app store) I don't know how 'piracy' is really looked at on XDA, though I can't imagine well, but you can download the Root Explorer 'pro' apk, and then - as long as it helps - purchase the app from GPlay to make sure to support the devs, which is what I did.
So to get to the actual process - should be quite easy as I did this on OPR6 myself - open Root Explorer, navigate to the "root" tab at the top. Then you should see "Mounted as r/o" and right next to it, a button that says "Mount R/W". Toggle that button, and the text on the left should state "Mounted as r/w", then try to install busybox (however you prefer - I used BusyBox Free by Stephen (Stericson) like I always do).
Hope you are successful with that method, please keep me updated with your outcome so I can help as best as I can.
Click to expand...
Click to collapse
Well that didn't work
Update, I had to change the path to /system/bin instead of /system/xbin

[Q] [Solved] Superuser: isn't asking for permissions BUT apps work

I'm confused! I have superuser installed and as of yet no app has asked for permissions; they just work. With the exception of ROM Manager which just freezes (needs long hold on back key). On previous ROMs I've flashed, requests for permissions pop up and you allow/deny etc. I've tried using the updater from the marketplace (force closes) and updating the binary (force closes). Am not able to uninstall superuser. I've turned on/off USB Debugging, fixed permissions, almost everything else I've found on the net.
As apps are working it isn't the end of the world but I'm confused about why they are working and also slightly concerned over the security aspect of apps not asking me and just running.
Apps that work without asking include: Titanium Backup, CPU Master, NSTools, File Explorer
I9020
Matr1x 15 Kernel
Orca 1 RC-0.1 (Drew Garen/BamtauMod)

What version is it? Try flashing version 3.0.7, this was the first to work with ICS if I remember correctly.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip

Hi,
According to the app it's version 3.0.7 (41).
I should've mentioned that it's an ICS ROM, sorry.

flodb113 said:
What version is it? Try flashing version 3.0.7, this was the first to work with ICS if I remember correctly.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Click to expand...
Click to collapse
You sir, are awesome! Thank you for link. I installed it and now my apps are requesting permissions.

Dynamo Nath said:
You sir, are awesome! Thank you for link. I installed it and now my apps are requesting permissions.
Click to expand...
Click to collapse
Glad you're happy with it! When ICS came out, we had to wait a week (I think) for the update to make SU work properly. Great work from the dev, as always.

superuser 3.0.7 doesnt work

I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.

try flashing su in recovery http://androidsu.com/superuser/

yeah thats exactly what i did...
I rooted my phone long ago and just got the new update so had to reroot it after installation... which seemed to work fine (with the older su-2.6.3.1) but sadly now that i got this nonworking superuser 3.0.7 (elf).zip in my phone none of my apps that need root access work
At this point im trying to figure how to go back to the older version (unless i can get this one working). Was just hoping i dont have to start all over as i cant even seem to reflash the older version - as it now gives me errors. Might just have to wipe the phone and start all over with the update.
But yeah so I updated the latest htc update and had to reroot my phone, I was able to flash the su-2.6.3.1 via CMR and this worked fine. It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.

Did you make regular Nandroid backups?
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1. I take it this isn't the case, because that backup would mean you could perform a factory restore, reflash CWM, and restore the backup. Any time you are making changes to your phone, backup before and along the way, just in case something like this happens. Titanium has its uses, but if your phone environment gets borked and you can't use it, it kind of defeats the purpose. Nandroid backups are more reliable in my book, and aren't app-dependent.
Sounds like you will have to start from scratch, although I'm unsure as to why Superuser 3.0.7 didn't work as expected. Possibly there was a conflict in moving from 2.6.3.1 to the newer version. I don't know of any specific problems 3.0.7 has with the MT4GS, and I'm running it on my phone with the latest binary without any problems. I do get an error message for one app, Quick Boot, when I use it to boot into recovery, but that doesn't stop the app from functioning as expected. I think that difficulty is related to the app itself and not Superuser.
Hopefully someone with a little more Superuser experience will chime in here. I'm afraid I don't have any ideas beyond the above.
Good luck --
--
KingCheetah

steve_77 said:
It seems as i should have stopped there as i saw that the 2.6.3.1 is an older version, so i tried flashing the latest 3.0.7 (elf) superuser -(which appeared to install just fine) but now I dont seem to have root anymore (although i see the superuser app - none of my apps that require superuser work). Ideas? Using adb .. I do see proper permissions on su at /system/bin but - for some reason SU is not working.
Click to expand...
Click to collapse
I had a similar problem before with SU after switching ROMs. Don't know if it might help but with Titanium Backup it showed that I had no busybox so I dl'ed busybox then SU wouldn't allow the apps to gain root access. Couldn't figure out what the problem was at all. Then I went to the SU app then saw that under the apps that were allowed or disallowed root access, the SU app itself was there. Once I deleted it from the list all the other apps that needed access worked fine. Hope that helps...

KingCheetah said:
You should have made a Nandroid backup through CWM after installation of Superuser 2.6.3.1.
Click to expand...
Click to collapse
Yeah i know - as fate would have it this is the one time i did not make a backup yet as i was hoping to gut out all the crap apps before doing a backup. Guess ill need to get more religious with the backups.
manimmal
Yeah i had Titanium Backup running with busy box before i had the "bright" idea to upgrade to 3.0.7 - but i guess i could try that but likely i might have to start-over from scratch (and forget about the 3.0.7 version) - unless anyone has any other ideas.
The only thing I can think of is perhaps the first su was flashed using one version of CMR and the second another version of CMR (updated after i installed rom manager perhaps)?
Even more interesting is the "su-2.3.6.1-ef-signed" with su having a datestamp of 8/17/2010; while the "Superuser-3.0.7-efghi-signed2" su version has a datestamp of 2/29/2008 - which seems a bit weird....

steve_77 said:
I tried upgrading from su 2.6.3.1 to superuser 3.0.7 over the weekend and after flashing 3.0.7 , none of my apps that required root work - is there a way around this [im using the latest update (1.63...)] Id like to update but seems stuck with older version for now - at least it works.
I did see a Superuser elite in the market... does the new version require you to pay for the license to get root (not that its about money but im just curious)?
Also yes there us an "update fixer" which requires root privileges which the new 3.0.7 version doesnt provide so i cant use that.
Click to expand...
Click to collapse
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.

Fuzi0719 said:
I'm running Superuser v3.0.7 with no problem, I flashed it in recovery. It has the su binary 3.0.3.2.
Click to expand...
Click to collapse
do you still have the exact same zip file you used to install 3.0.7 ? (perhaps you have a slightly different one then whats available on the website)
I have no doubt that it works on some peoples devices, but i just dont know why it doesn't work on my device. I am pretty much running stock rom with the latest htc update, CMR 5.0.2.7 , rom manager 5.0.0.6 , superuser 2.3.6.1, su binary 2.3.1-ef - this works ( i have root) but if i boot into recovery and install the latest su for froyo 3.0.7 I loose root. (made nandroid backup this time)
I was thinking of trying to use chainsdd "su update fixer" in the market - but dont know how to use this app.. if it helps in debug i am also having a hard time installing busybox. i use "partitions info lite" to check status of my partitions, root access, and that i have busybox installed... i tried installing it via "busybox" [Stephen (Stericson)], which didnt seem to be recognized so uninstalled and tried "busybox installer" [JRummy16] - they are probably separate issues but who knows...

steve_77 said:
... and install the latest su for froyo 3.0.7 I loose root. ...
Click to expand...
Click to collapse
You answered your own question.
Froyo was the version of Android that predates Gingerbread.
The only official release of software for this device is on Gingerbread.
We are moving forward into Ice Cream Sandwich, but not officially.
You are basically trying to install a Windows 7 Program on Windows 95, to craft an analogy.
Stick with the gingerbread release of superuser.
The reason why the version is higher is because for the Froyo version of Android it went through more iterations.
Shame I didn't see this thread sooner, someone else had this same issue a while ago and I gave the same answer, should be around here somewhere. Would have saved you some trouble.

Some confusion here, I think...
Here's what is at ChainsDD's official site, http://androidsu.com/superuser/
Eclair/Froyo/Gingerbread/Honeycomb/IceCreamSandwich (2.1 – 4.0.3)
md5: fc462fa0630379edbe10006b1d19d9b1
Superuser-3.0.7-efghi-signed.zip | mirror | RM Web Connect
binary only
md5: 26d08a253f1883c13561d173094d70b9
su-bin-3.0.3.2-efghi-signed.zip | mirror | RM Web Connect​
The lines after the md5 codes are links for the zip files. Superuser 3.0.7, according to the dev, is applicable to all flavors of Android as listed. This is also the exact file that I flashed and am using on my phone. There is a separate file for Donut 1.6, and it also is designated 3.0.7, but with a slightly different filename: Superuser-3.0.7-d-signed.zip.
I still think updating from 2.3.6.1 is part of the problem. If you go straight to 3.0.7 after your reformatting, it should work properly.
Also, Manimal's suggestion to check that Superuser isn't disallowed within the app itself is a great idea. It's weird, but an easy fix if this is the case.
I believe the update fixer Chains has available is to correct problems with the Superuser app updating new binaries. I don't think this would be of benefit to your situation.
Chains would be the best source for help, I think; an e-mail couldn't hurt --
--
KingCheetah

2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply

So why not install the working version, and then just update the binary from within the app?
That would be one way.
Sent from a digital distance.

steve_77 said:
2.3.4 is froyo right?
Either way the one i installed (i.e. Superuser-3.0.7-efghi-signed.zip) was from the official site (http://androidsu.com/superuser)
which according to the notes shouldn't matter which version as long as its not 1.6 which it certainly isnt as its 2.3.4
will try it again... but thanks for the reply
Click to expand...
Click to collapse
Android 2.3.X is Gingerbread. Froyo is 2.2.X. Anyway, the SU you have SHOULD work, it is the same as I used. Have you tried flashing it via fastboot? I simply flashed the 3.0.7 version via recovery when I installed my ROM (stock 1.63.531.2).

[Q] Non writable /system on Stock or something else?

I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks

TraderJack said:
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
Click to expand...
Click to collapse
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.

S1L3nTShaDoWz said:
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
Click to expand...
Click to collapse
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.

UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/

TraderJack said:
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
Click to expand...
Click to collapse
Yeah on the kernel my bad, didn't see it had a normal one for non 2.23 firmware users lol, if you don't wanna use that kernel you can always use one of the other ones, maybe Faux's or Evolutionmods kernel. I actually currently use Evolutions kernel and it's quite nice. Also that ROM will work fine I believe, quite sure 1.55 is the latest OTA and if not it doesn't really matter. All though as some people have stated on your previous thread (i think?) you might as well use an optimized stock ROM such as CleanROM or ARHD (Android Revolution HD 8.1), all it is is a stock ROM thats been optimized for better performance and maybe has some tweaks to make it better. To be clear on the ARHD ROM, I stated the version because any higher version than that is for 4.4.3 which we currently don't have the firmware for.
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Glad you got your issue solved!

TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk

BadUsername said:
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.

TraderJack said:
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
Click to expand...
Click to collapse
Can't say I ever used that option, it probably just didn't flash it correctly. You may want to post the problem in the recovery thread so they know about it.
In theory it should've worked the same way as flashing the zip. The only thing I could think of is how old the binary was or the location of the flash was incorrect.
Sent from my HTC6525LVW using Tapatalk