[Galaxy S II Q&A, Help & Troubleshooting] jeanclaudevandamme:
it's not working. I think it's because the twlauncher error has somehow caused my phone to be unrooted, or at least making all applications requring superuser access disabled. because the adb install command fails because it says an folder (/data/local/tmp/) is read / only and when I go into Root Explorer to try making it r/w, the first message i get is the Superuser application stopping unexpectedly.

but when i check for root access using adb, ie "adb shell", I get "#", which means I still have root access?

I don't understand.

-------------------------------

Upon further investigation, it seems that the entire /data folder and subfolders are locked to r/o by the twlauncher failure (logprovider as well as every other crash loop error) caused initially by Swiftkey 3 when i pressed the home key while typing in Skyfire.

I have managed to regain some minor amount of utility by following a series of frustrated attempts,

*when there are 10 different crash loop errors, try pressing as fast as I can go to into task manager, the crash loop errors will now be reduced to about 3, then clear ram. This takes something like 25 attemps

*when there 2 crash loop errors remaining, try pressing as fast as i can "force close -> options (button left of home key) -> setting in the pop up panel. This will take something like 50 attempts to get the timing right so I am able to fast press everything in sequence before the next force error makes me start again.

*once into settings, there is just one crash loop error (logprovider), go into applications, all, twlauncher and press force end (obviously there'll be crash loop errors so you have to be quick in pressing keys)

*now there are no crash loop errors until you press the homekey or try and access all your applications (twlauncher error remains, logprovider will come up again and i have to repeat all these steps if i try to use contact/message function)

What the above has essentially enabled me to do is to access a few applications that was on my 1st or 2nd homescreen by chance (not all will work) , i still can't access any on my app screen as twlauncher crashes too fast.

This is how I have been able to simultaenously mess around with Root Explorer and ADB on my PC in USB debugging mode.

This is how i have discovered that when I use Rootexplorer, initially it says Superuser application has stopped and I have to force close it.

However, I am still able to use Rootexplorer to mount r/w or r/o on a few folders, such as /system , so this implies that I do still have root access. However, there is no options to make /data r/w, even in root explorer, attempts using adb to make /data r/w also fails.

What this means is that I can't clear the cache / dalvik-cache as they are sub folders of /data. It means that adb install launcher.apk fails because /data/local/tmp, the folder where you're copying the apk to is r/o. It means that I can't install or uninstall any applications because /data/apps is read only.

For eg, I have used adb push launcher.apk successfully to put go ex launcher in the /system/apps folder, but it just stays there as an apk file (from previous experiences, putting an apk in the /system/apps file doesn't make that apk install on boot, because you need an odex file for that apk). So when I manually select to install that apk, phone crashes and reboots because /data/apps is r/o. This is also how I can't uninstall or clear the cache of the application that caused this in the first place (swiftkey 3)