Guest Nebulous Posted June 1, 2010 Report Posted June 1, 2010 Whenever I navigate through the file system, I get loads of strange characters which make it very hard to understand what is happening. I get it through ADB and using a terminall application on the phone its self. c:\android>adb-windows.exe shell ls -l /data drwxrwxrwx 1 0 0 2048 May 30 18:40 ←[1;34mDxDrm←[0m drwxrwx--x 1 1000 1000 2048 May 30 18:41 ←[1;34manr←[0m lrwxrwxrwx 1 0 0 14 May 30 18:40 ←[1;36mapp←[0m -> ←[1;3 4m/system/sd/app←[0m drwxrwx--x 1 1000 1000 2048 May 30 18:40 ←[1;34mapp-cache←[0m lrwxrwxrwx 1 0 0 22 May 30 18:40 ←[1;36mapp-private←[0m -> ←[1;34m/system/sd/app-private←[0m drwx------ 1 1000 1000 2048 Jun 1 09:07 ←[1;34mbackup←[0m lrwxrwxrwx 1 0 0 23 Jun 1 09:07 ←[1;36mdalvik-cache←[0m -> ←[1;34m/system/sd/dalvik-cache←[0m drwxrwxrwx 1 0 0 2048 May 30 18:34 ←[1;34mdata←[0m drwxr-x--- 1 0 1007 2048 May 30 18:40 ←[1;34mdontpanic←[0m lrwxrwxrwx 1 0 0 11 May 30 18:40 ←[1;36mdrm←[0m -> ←[1;3 4m/data/local←[0m drwxr-xr-x 1 0 0 2048 Aug 1 2008 ←[1;34mdropbear←[0m prw-r--r-- 1 1000 1000 2048 May 30 23:28 ←[0;35mgps_nmea_fifo←[0 m drwxr-xr-x 1 2000 2000 2048 May 30 18:40 ←[1;34mlocal←[0m drwxrwx--- 1 0 0 2048 May 30 18:40 ←[1;34mlost+found←[0m
Guest Kali- Posted June 1, 2010 Report Posted June 1, 2010 some time ago i got the same problem (never bricked my phone) on win7 x64
Guest KaMeLe0n Posted June 1, 2010 Report Posted June 1, 2010 c:\android>adb-windows.exe shell ls -l /data try running: c:\android>adb-windows.exe shell & (<---- remember about the "&" sign at the end!) and then in the shell: ls -l /data see if anything changes
Guest Nebulous Posted June 1, 2010 Report Posted June 1, 2010 try running: c:\android>adb-windows.exe shell & (<---- remember about the "&" sign at the end!) and then in the shell: ls -l /data see if anything changes Nope, its still the same!
Guest Silvarbullit Posted June 1, 2010 Report Posted June 1, 2010 try running: c:\android>adb-windows.exe shell & (<---- remember about the "&" sign at the end!) and then in the shell: ls -l /data see if anything changes Mine does the same since putting r3 on, I've done a recovery reflash too but it didnt change anything. Everything seems to work fine however and the paths do work as /system or /data etc.... its just weird looking and annoying try to find file names and paths through ADB. Putting & doesn't make any difference. Using win7-64 - haven't tried linux or mac.
Guest Nebulous Posted June 1, 2010 Report Posted June 1, 2010 Mine does the same since putting r3 on, I've done a recovery reflash too but it didnt change anything. Everything seems to work fine however and the paths do work as /system or /data etc.... its just weird looking and annoying try to find file names and paths through ADB. Putting & doesn't make any difference. Using win7-64 - haven't tried linux or mac. I am using Windows 7, although had the same problem on XP
Guest encrypt Posted June 1, 2010 Report Posted June 1, 2010 Have the same issue on Win7 X64... Used the tinycore method for root.
Guest KaMeLe0n Posted June 1, 2010 Report Posted June 1, 2010 (edited) do you have usb-debugging turned on? have you tried running those commands from recovery? as per: run in recovery (red triangle page) and then adb-windows push files / (<----- files from Pauls rooting guide) adb-windows shell busybox --install /sbin adb-windows shell mount /system adb-windows shell & see what happens Edited June 1, 2010 by KaMeLe0n
Guest afiorillo Posted June 1, 2010 Report Posted June 1, 2010 That isn't a device issue, nor a ROM one: those "strange" characters are escape sequences to color the console output that aren't properly parsed by your command prompt / console window.
Guest WolfspiritM Posted June 1, 2010 Report Posted June 1, 2010 (edited) Just type: alias ls='ls --color=never' and the color sequenzes are gone for this shell session. For use in one line ls code: adb.exe shell ls --color=never -l /data Edited June 1, 2010 by WolfspiritM
Guest Matchstick Posted June 1, 2010 Report Posted June 1, 2010 Just type: alias ls='ls --color=never' and the color sequenzes are gone for this shell session. For use in one line ls code: adb.exe shell ls --color=never -l /data Alternatively you can use the freeware program ANSICON to enable the colours in the windows shell. http://adoxa.110mb.com/ansicon/index.html You can automate running ANSICON with the -i option which works fine in Windows XP. However on Windows -i option doesn't work with cmd but it you use Console instead of cmd the colours work fine. http://sourceforge.net/projects/console/
Guest Silvarbullit Posted June 1, 2010 Report Posted June 1, 2010 Just type: alias ls='ls --color=never' and the color sequenzes are gone for this shell session. For use in one line ls code: adb.exe shell ls --color=never -l /data Cheers Wolf. Suspected it was escape codes but didn't know why they had turned on all of a sudden after r3. Turning color off fixed it. If only I can find which .profile file or other shell config file I can add the alias into to switch them off permanently.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now