Just thought I'd post my experience with installing this since I ran across a problem that was posted earlier in this thread but remained unanswered...at least by what I could find when searching. For reference, I'm running CM7.1 Nighly 229.
When installing BusyBox 1.18.2 via the installer, I changed the installation path to /system/bin in an effort to isolate it from the BusyBox used by Titanium Backup. The install completed successfully, but when I then tried to run the script in Script Manager, it told me I 'must be suid to work properly' (may not be the exact syntax, sorry). I went back into the BusyBox Installer and it too told me I did not have root access, and it told me to try removing the BusyBox Installer from SuperUser. I tried this, but to no avail. Also, any other program that required root access (Titanium Backup, ROM Manager, etc.) refused to function.
Luckily I made a nandroid before trying the script, so I restored it and this time when running the BusyBox Installer, I let it install to the default location (/system/xbin, I think) and everything went smoothly after that.
Thanks for all the effort on this script,
sleepy
Phone: Sprint Nexus S 4G ROM: CM10.1 Nightlies Recovery: ClockWorkMOD 5.8.0.2 Touch Cannibal Open Touch v2.1 CPU Settings: ONDEMAND Min: 200Mhz Max: 1000Mhz19 576 Radio: 2.42.01.04.29 Tweaks: V6 SuperCharger : 3G TurboCharger : KickAss Kernel
Sent from my Galaxy Ace on GLSMT 2.1 with XDA app.
/data/misc/wifi/wifi folder
Quote:
Originally Posted by sleepyEDB
Hi,
Just thought I'd post my experience with installing this since I ran across a problem that was posted earlier in this thread but remained unanswered...at least by what I could find when searching. For reference, I'm running CM7.1 Nighly 229.
When installing BusyBox 1.18.2 via the installer, I changed the installation path to /system/bin in an effort to isolate it from the BusyBox used by Titanium Backup. The install completed successfully, but when I then tried to run the script in Script Manager, it told me I 'must be suid to work properly' (may not be the exact syntax, sorry). I went back into the BusyBox Installer and it too told me I did not have root access, and it told me to try removing the BusyBox Installer from SuperUser. I tried this, but to no avail. Also, any other program that required root access (Titanium Backup, ROM Manager, etc.) refused to function.
Luckily I made a nandroid before trying the script, so I restored it and this time when running the BusyBox Installer, I let it install to the default location (/system/xbin, I think) and everything went smoothly after that.
Thanks for all the effort on this script,
sleepy
I tried putting installing bb to the bin folder once... fubarred everything lol
But TBackup is uneffected by the system's busybox - it uses it's own 1.18.4 internally and for it's own use
BTW I found a bug... when switching launchers with options 11 -13 I get repeated entries in the *.prop file and the *rc file...
So while I'm fixing that I'm gonna enhance the 97bulletproof and 1shot scripts so they spit out info
I tried putting installing bb to the bin folder once... fubarred everything lol
Yes. Fubar is definitely the correct term. It was _not_ happy!
Quote:
Originally Posted by zeppelinrox
But TBackup is uneffected by the system's busybox - it uses it's own 1.18.4 internally and for it's own use
I've read the same thing, but it was definitely affected by the botched BusyBox install. When I opened TB, it failed it's little startup check, saying that BusyBox was not found and root could not be achieved (or something to that effect).
Not debating what we all know to be true, just wanted to report what happened to me and how I fixed it. Thank Science for nandroid backups!
sleepy
Phone: Sprint Nexus S 4G ROM: CM10.1 Nightlies Recovery: ClockWorkMOD 5.8.0.2 Touch Cannibal Open Touch v2.1 CPU Settings: ONDEMAND Min: 200Mhz Max: 1000Mhz19 576 Radio: 2.42.01.04.29 Tweaks: V6 SuperCharger : 3G TurboCharger : KickAss Kernel
try clearing caches and dalvik cache also go to the screen that shows what wireless networks you can connect to and forget all of them now turn wifi off and on again now the wifi networks should now work properly
XDA Developer TV Producer Kevin wants to help make your … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?