Database Users

Remove CityID after root and recovery flash

So I've rooted and installed the new recovery on my incredible. I want to remove CityID now, forgot to after root. When I launch recovery and run adb devices it shows my device. I then run adb shell, immediately getting the # for su (instead of the $ prompt for non su access). I execute /system/bin/rm /system/app/CityID.apk as instructed by the wiki and get /sbin/sh: /system/bin/rm: not found. I browse to /system/bin and do a listing and see nothing. So am I doing something wrong?
**EDIT**
Forgive my ignorance, but I forgot to mount system in the partitions menu of recovery. Doubtful this would be of any help to anyone, but there ya go.

Also in the How To:
StirCwazy said:
So I've rooted and installed the new recovery on my incredible. I want to remove CityID now, forgot to after root. When I launch recovery and run adb devices it shows my device. I then run adb shell, immediately getting the # for su (instead of the $ prompt for non su access). I execute /system/bin/rm /system/app/CityID.apk as instructed by the wiki and get /sbin/sh: /system/bin/rm: not found. I browse to /system/bin and do a listing and see nothing. So am I doing something wrong?
**EDIT**
Forgive my ignorance, but I forgot to mount system in the partitions menu of recovery. Doubtful this would be of any help to anyone, but there ya go.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=709220 - It's a few posts down, but will update first post later today.

help me get my vibrant to stock

I previously received my vibrant rooted and using this method on the thread http://forum.xda-developers.com/showthread.php?t=734475 and i used the unrooted file on page two. everything worked great but i still have root. I have the superuser permission show up on my app list, i also tested to see if i have root by installing a root only app, and it worked. so can anybody help get to stock?

Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.

ttabbal said:
Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.
Click to expand...
Click to collapse
yes i used the nandroid. can you point me to the odin flash? and is the odin more dangerous to use than nandroid? thanks for the help.

look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you

vdub804 said:
look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you
Click to expand...
Click to collapse
listen, im new to this and ive already searched the devolpment section and theres a couple similar threads. so, since i dont really know what im doing, i asked for help. all i asked was to point me to the thread that someone who is experienced in this thinks i should use. thanks for the help.

http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.

ttabbal said:
http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.
Click to expand...
Click to collapse
thank you for the help. i was just confused as to which one to use. hopefully, when im more experienced in this, i wont post stupid questions like this.

You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.

mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?

stepinmyworld said:
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?
Click to expand...
Click to collapse
did u type "su" before typing every other else?
it should be like:
# whatever you type
not $ whatever you type.

If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

From the sticky at the top of the page (that says to read before asking). If you want to use the links, go to the sticky.
HOW TO UN-ROOT *ie, sending your phone in for warranty work
The following code can be keyed in Terminal Emulator (could also be done in ADB or deleting the files using Root Explorer). If you do use Terminal, change the keyboard to the stock Android KB prior to opening Terminal. Apparently the backspace on swype does not work in Terminal. Each line should be entered separately. bahnburner gave the instructions in this thread, which you should review first.
Quote:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
* Alternate Method *
TGA_Gunnman in this thread created a one click root/unroot program. Thank him for his effort.

mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
mrxela said:
If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?

It is in the sticky.

JEEBUS (10....)

mrxela said:
It is in the sticky.
Click to expand...
Click to collapse
aww shux. smh
thanks

I used root explorer and deleted those files, so that means I'm on stock and I can get warranty service? Thanks a lot guys, you have saved a noob

stepinmyworld said:
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?
Click to expand...
Click to collapse
Haha rooting won't keep you from getting OTA updates.

(Q) Root with Super User

So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?

Have they asked for superuser?
Via EVO on 4G with XDA App

awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device

krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.

richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...

krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su

Please delete

krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.

richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.

rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?

richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.

rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.

followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"

spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?

richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!

spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.

if you flash noobnl's latest kernel, it includes superuser and it works perfectly.

rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.

richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.

I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?

s-off but not super user acces!? help please :)

hey well i got to this point :
# # /data/local/tmp/root
Click to expand...
Click to collapse
anyhow when i run this it says:
cp: can't stat '/sdcard/superuser.apk': no such file or directory
then is the same but with su
Click to expand...
Click to collapse
i went ahead and put sync anyhow and when i restart and run 'su' but is says: unknown user root
any ideas what i did wrong? :/
oh and btw somehow i have S-off...
i followed each step, but i just notices this... for some reason it wont let me push superuser.apk or su, all of the other files can be pushed... any ideas?

no one?

http://www.youtube.com/watch?v=tU9zn_BEth4 i did that way and it works for me.

but i have s-off i supposed to be rooted already but i do not have super user powers... what do i do

Did you copy the Superuser.apk file to the root of your SDcard?

yes i did, and su too and now when i put su on my phone it says unknown user root :/
i can get temporal rooting tough.

Use visionary r13 ... had same issue... worked for me
Get it from pauls visionary thread on Modaco.
Sent from my HTC Vision using XDA App

i had the same situation with u few days ago. just follow http://forum.xda-developers.com/showthread.php?t=834228 and u only need do the temp root part.
Delete visionary and superuser first, install terminal emulator from market.
on you pc:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Then on you G2, open a terminal emulator
Launch Terminal Emulator---/data/local/tmp/rage----Wait for the message: "Forked #### childs."------Menu > Reset Term - Terminal Emulator will exit.-----Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell----- run the /data/local/tmp/root script here.---sync.
In the last step, u can find the origin thread dose not let u do this. but, if you've got s-off, trust me, just do the last step "/data/local/tmp/root", and when u see a feedback "****files exist",then "sync",

I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions

u can also do what i suggested in the 8th floor.

o>c said:
I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions
Click to expand...
Click to collapse
r u rspt in Gfan? since u can read chinese, just look at here. http://www.hiapk.com/thread-631413-1-3.html
I made this thread to help solve such problem.

After I got S-off, I didn't have root either. I just jumped on visionary (made sure run on boot wasn't checked), clicked root now. And boom, that was it. Then I deleted visionary and I've had root ever since...

Guys need help adb is driving me crazy!!!

Right guys,
Im trying to list the apk's in /data/app through adb so i can pull one of them!
I keep getting an error opendir failed permission denied!
BUT!!! I can get into /system/app fine with no problems.
Im running darkyy's 9.5 with his new kernel. Could this be a problem?
Its strange how i can get in system/app but not data/app
I have never had this problem in the past.
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
opendir failed, Permission denied
c:\AndroidSDK\platform-tools>

zolah said:
Right guys,
Im trying to list the apk's in /data/app through adb so i can pull one of them!
I keep getting an error opendir failed permission denied!
BUT!!! I can get into /system/app fine with no problems.
Im running darkyy's 9.5 with his new kernel. Could this be a problem?
Its strange how i can get in system/app but not data/app
I have never had this problem in the past.
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
opendir failed, Permission denied
c:\AndroidSDK\platform-tools>
Click to expand...
Click to collapse
Either :
adb root
adb shell ls /data/app
or
adb shell
su
ls /data/app
Reason /system is accessible is because system is ro by default. So they allow you to browse it knowing u won't be able to do anything w/o root. Whereas /data is rw and hence they restrict you, unless you have root.
Fyi : Wrong section to ask questions.

Daneshm90 said:
Either :
adb root
adb shell ls /data/app
or
adb shell
su
ls /data/app
Reason /system is accessible is because system is ro by default. So they allow you to browse it knowing u won't be able to do anything w/o root. Whereas /data is rw and hence they restrict you, unless you have root.
Fyi : Wrong section to ask questions.
Click to expand...
Click to collapse
I am rooted with superuser...

zolah said:
I am rooted with superuser...
Click to expand...
Click to collapse
The default superuser timeout is 10 secs, either increase it or keep looking at your screen.
PS : Have you tried a an app called Mount R/W? works great.

zolah said:
I am rooted with superuser...
Click to expand...
Click to collapse
Im confused, what are you implying by that response ?
To me that statement was equivalent to "The sky is blue"

Daneshm90 said:
Im confused, what are you implying by that response ?
To me that statement was equivalent to "The sky is blue"
Click to expand...
Click to collapse
..... sigh
You was telling me that i have to have root and su to be able to poke around in /data... i said i am rooted with su obviously as im on custom rom...

zolah said:
..... sigh
You was telling me that i have to have root and su to be able to poke around in /data... i said i am rooted with su obviously as im on custom rom...
Click to expand...
Click to collapse
Yes, but by default, if u dont run
adb root....ur not running the shell in root mode
Also on most roms if u run :
adb shel
u'll see $......
when u type su
u see #
So to enter # mode u need root but still need to execute either adb root or adb shell n then su.
Hope that clears it.

install android commander and forget about command line for simple listing and coping tasks
Sent from my GT-I9000 using Tapatalk

This is what i get ...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb root
adbd cannot run as root in production builds
c:\AndroidSDK\platform-tools>adb shell
/ $ su
su
ls /data/app
ls /data/app
Permission denied
/ $ ls /data/app
opendir failed, Permission denied
/ $

zolah said:
This is what i get ...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb root
adbd cannot run as root in production builds
c:\AndroidSDK\platform-tools>adb shell
/ $ su
su
ls /data/app
ls /data/app
Permission denied
/ $ ls /data/app
opendir failed, Permission denied
/ $
Click to expand...
Click to collapse
I dont see a # anywhere in there...
Are u accepting the dialog on ur phone when u type su ?
There shud b a popup on ur phone once u do that.

Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App

woolf clubs said:
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Maybe he's trying to learn how to navigate using adb. Very useful skillset to acquire imho.
But yes for general purpose, a gui is better.

the plot thickens...
Ill fill you guys in from the start in a short story..
Updated to darkyy v9.5 from v9.3
I thought the phone went a bit funny when it loaded the first boot as on the boot animation it vibrated like crazy and the animation started again as it was going to loop but then the phone loaded...
Been using the phone a few days and everything fine and wanted to pull an app from /data/app
All the above stuff happened and it wouldnt let me.
I thought something wasnt right so i took out the battery for a few minutes and put it back in and went into download mode and plugged my phone into computer to see of odin would still recognise it ok...
My windows vista computer started installing device drivers???? ive had this phone 7 months and plugged in about 100,000,000 times lol
Odin recognised my phone so i rebooted and tried again and now it works fine...
Something weird going on there which is concerning me with it installing new drivers...
This is what i get now and used to get before when i used adb...
Code:
C:\Users\Paul>cd c:\AndroidSDK\platform-tools
c:\AndroidSDK\platform-tools>adb shell ls /data/app
FasterFix.apk
Vending.apk
com.adobe.flashplayer-1.apk
com.android.wallpapersetandsave-1.apk
com.darkyrom.darkyconfig-1.apk
com.ebproductions.android.launcher-1.apk
com.google.maps.apk
com.google.youtube.apk
org.projectvoodoo.controlapp-1.apk
circular_battery_indicator.apk
com.androidapps.spareparts.apk
com.haxor-1.apk
com.sgsinfo.apk
com.sgstoolbox.apk
de.Fr4gg0r.SGS.Tools-1.apk
neldar.bln.control.free-1.apk
ymst.android.homeswitcherfroyo-1.apk
com.android.vending-1.apk
com.handcent.nextsms-1.apk
com.keramidas.TitaniumBackup-1.apk
com.pants.sc.lite-1.apk
com.navigon.navigator_select-1.apk
org.adwfreak.launcher-1.apk
com.speedsoftware.rootexplorer-1.apk
com.anddoes.fancywidget.pro-1.apk
adw.creativethemez.gingerbread-1.apk
com.quoord.tapatalkxda.activity-1.apk
c:\AndroidSDK\platform-tools>
Thank you for all the responses by the way...
Any one have any idea what could have happened?

woolf clubs said:
Am I being daft or is root explorer 10 times easier than using adb for this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
For what i was doing no because i wanted to just quickly pull an apk, decompile it and edit something and compile it and push it back...
Daneshm90 said:
Maybe he's trying to learn how to navigate using adb. Very useful skillset to acquire imho.
But yes for general purpose, a gui is better.
Click to expand...
Click to collapse
I know how to navigate with adb very well. I just couldnt figure out why i was being blocked from entering /data/app...
I even have a video tutorial in my sig that i made showing how to use adb and its commands...
Seems a quick battery pull did the trick although i still now dont know why new drivers where auto installed on reboot to my pc