Okay, I'm a little unsure where to begin. I've got a Fascinate (SCH-i500) running 2.3.5, for what it's worth. This isn't a phone specific thing though.
I recently rooted my phone via Odin and su 2.3.6.1.x.zip.
I then installed Titanium backup lite, and bought ROM-toolbox by JRummy.
I froze the crap apps like Bing with the latter, and did a full backup with Titanium Backup.
(I noticed some things in rom-toolbox didn't seem to work, like CPU adjustments, but figured that's due to the stock kernel in my SCH-i500.
So far so good.
The next morning, there's a message that the su binary is outdated, and should be 3.0.32.
I tried to update it but it failed, saying:
Downloading manifest... okay
parsing manifest... okay
latest version= 3.0.3.2
Checking installed version= 2.3.1-ef
clicked update
Fixing database... okay
Checking for busybox... okay
checking current install path... /system/xbin/su
Downloading new binary... okay
Checking md5sum... okay
Gaining root access... okay
Remounting /system as rw... okay
Copying su to /system... fail
So, looking around on the net, I found this thread:
http://www.droidforums.net/forum/droid-3-tech-support/204854-trying-update-su-binary.html
The suggestion was to use Stephens Busybox installer to update busybox.
Bad idea.
Apparently it worked for the user in that thread but not me.
When I ran it, the install (of busybox) complained that "the installation was not the version I was expecting", whatever that's supposed to mean. (I've since noticed a lot of bad reviews of that app!)
And now the su binary update failure message is different: it says the md5 for su 3.0.3.2 is invalid.
Worse, it was then that I found ROM-toolbox would no longer run, when I fire it up, it just reboots my phone. Every single time. I paid $5 for a reboot button! (I've emailed the dev for help)
I tried clearing it's data, uninstalling and reinstalling, but no joy.
The Busybox installer F'd with my symlinks and screwed things up. I then tried uninstalling busybox with the installer, but that failed miserably too.
One option is to install Busybox to /system/xbin instead of /system/bin, I might try that.
The phone is still rooted apparently, I can still run Titanium backup and some other stuff I since installed (like a term emulator).
I tried a restore from Titanium backup restoring apps and data, but that didn't really change anything, oddly.
I tried to look into nandroid backups, but finding a clearcut, up to date tutorial has proven very difficult. There's so many different versions of Android and phone hardware,and instructions that evolve and change, I'm not sure what is what. (I did however install the Java SDK and the Android SDK today..so, getting there)
At this point, I'm not sure what to do.
In the term emulator, I see a file named "busybox" under /system/bin, it's 0 kbytes. It's just an empty file, apparently. Weird.
I thought going to recovery mode and reapplying the su package might help, but it just says like invalid when I choose it.. (dammit, I forget exactly now, I'd have to retry it). It may be that I opened the zip file with WinRAR, which can change the checksum according to something I read on XDA; I might try that again, but I'm not sure it'd even matter.
Related questions:
* Did busybox come with the su package?
* Can you have more than one version of busybox installed? Titanium backup claims to use it's own "optimized" version of Busybox. Interestingly, when, in it's preferences, I tried setting it to use the my stock "system version", it could no longer get root access. Gah.. (I had to wipe it's application data to fix that, under settings | applications "clear data")
I recently rooted my phone via Odin and su 2.3.6.1.x.zip.
I then installed Titanium backup lite, and bought ROM-toolbox by JRummy.
I froze the crap apps like Bing with the latter, and did a full backup with Titanium Backup.
(I noticed some things in rom-toolbox didn't seem to work, like CPU adjustments, but figured that's due to the stock kernel in my SCH-i500.
So far so good.
The next morning, there's a message that the su binary is outdated, and should be 3.0.32.
I tried to update it but it failed, saying:
Downloading manifest... okay
parsing manifest... okay
latest version= 3.0.3.2
Checking installed version= 2.3.1-ef
clicked update
Fixing database... okay
Checking for busybox... okay
checking current install path... /system/xbin/su
Downloading new binary... okay
Checking md5sum... okay
Gaining root access... okay
Remounting /system as rw... okay
Copying su to /system... fail
So, looking around on the net, I found this thread:
http://www.droidforums.net/forum/droid-3-tech-support/204854-trying-update-su-binary.html
The suggestion was to use Stephens Busybox installer to update busybox.
Bad idea.
Apparently it worked for the user in that thread but not me.
When I ran it, the install (of busybox) complained that "the installation was not the version I was expecting", whatever that's supposed to mean. (I've since noticed a lot of bad reviews of that app!)
And now the su binary update failure message is different: it says the md5 for su 3.0.3.2 is invalid.
Worse, it was then that I found ROM-toolbox would no longer run, when I fire it up, it just reboots my phone. Every single time. I paid $5 for a reboot button! (I've emailed the dev for help)
I tried clearing it's data, uninstalling and reinstalling, but no joy.
The Busybox installer F'd with my symlinks and screwed things up. I then tried uninstalling busybox with the installer, but that failed miserably too.
One option is to install Busybox to /system/xbin instead of /system/bin, I might try that.
The phone is still rooted apparently, I can still run Titanium backup and some other stuff I since installed (like a term emulator).
I tried a restore from Titanium backup restoring apps and data, but that didn't really change anything, oddly.
I tried to look into nandroid backups, but finding a clearcut, up to date tutorial has proven very difficult. There's so many different versions of Android and phone hardware,and instructions that evolve and change, I'm not sure what is what. (I did however install the Java SDK and the Android SDK today..so, getting there)
At this point, I'm not sure what to do.
In the term emulator, I see a file named "busybox" under /system/bin, it's 0 kbytes. It's just an empty file, apparently. Weird.
I thought going to recovery mode and reapplying the su package might help, but it just says like invalid when I choose it.. (dammit, I forget exactly now, I'd have to retry it). It may be that I opened the zip file with WinRAR, which can change the checksum according to something I read on XDA; I might try that again, but I'm not sure it'd even matter.
Related questions:
* Did busybox come with the su package?
* Can you have more than one version of busybox installed? Titanium backup claims to use it's own "optimized" version of Busybox. Interestingly, when, in it's preferences, I tried setting it to use the my stock "system version", it could no longer get root access. Gah.. (I had to wipe it's application data to fix that, under settings | applications "clear data")