Recent content by melch8805

so what exactly (name by name) did you remove?

Congrats! No offense meant to Cory Streater, but I personally would rather have everyone learn this little bit of adb than jump straight into a gui-based option. Now, on the other hand Cory Streater did put together an awesome tutorial! Mad Props!!! (yeah i'm bringing back early 90's phrases :P)...

i'm not sure what is up with your busybox.... which cannot find it, but you can call it directly? *scratches head* so, are all the apps you wanted to move actually moved successfully? I haven't been able to figure out why sometimes I will get the can't preserve ownership and other times i...

So 755 is "changing mode" to executable. If you need/want more info on chmod, I suggest looking it up, cuz there is a huge amount of info on it. anywho, adb shell su next you are going to cd to /sdcard then run: ./tboltappmover.sh it might spit a bunch of blah at you, but after it is done...

are you saying you are having force close issues with those apps?

first off, odd that you can't su in usb charge only (thats all i do) second: you can't use adb once you are in adb :) third: confirm busybox is installed (through root checker) fourth: in regular cmd prompt (after you cd to the dir that has adb) you type: adb push tboltappmover.sh /sdcard/...

So we have been through quite the journey... :P Lets try this: adb shell su which busybox (this will tell us busy is there and good) mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system busybox ls -lrt /system/app/VZW_* (did this to check permissions) busybox chmod 777...

I "request support" for this 2 times a day :) I always get the 90-120 days answer everytime though :(

So based off of the cat of the emmc: dev: size erasesize name mmcblk0p17: 00040000 00000200 "misc" mmcblk0p21: 0087f400 00000200 "recovery" mmcblk0p22: 00400000 00000200 "boot" mmcblk0p25: 35dffe00 00000200 "system" mmcblk0p28: 001ffe00 00000200 "local" mmcblk0p27: 1b4ffc00 00000200 "cache"...

try: adb shell su chmod 755 /sdcard/tboltappmover.sh if that doesn't work try: adb shell su /system/xbin/busybox chmod 755 /sdcard/tboltappmover.sh let me know

try: adb shell chmod 755 /sdcard/tboltappmover.sh (chmod not cmod)

Update For people who didn't want to read the whole thread and skipped right to the end: I updated the info a little bit on my original post Link: http://forum.androidcentral.com/showthread.php?p=747764#post747764 Again, if there are any questions: ask!

Make sure the script is renamed to have .sh at the end (not .txt) to use adb: (make sure script is in the same dir as adb) (starting with the text file tboltappmover.txt: adb push tboltappmover.txt /sdcard/ adb shell mv /sdcard/tboltappmover.txt...

Are you using the script? If not and are trying to run through this line-by-line, make sure you chmod 777 /sdcard/Bloatware I'm not sure if that will solve your issues or not (i'm at work and can't test it)

Same as here, melch8805.