Related
When I try and use the file explorer in DDMS for my device it just comes up as blank. I am am running JF ADP1.5 on the device and the 1.5SDK on Mac OS X.
Can someone please confirm that DDMS file explorer works for JF ADP1.5 (preferably on Mac).
Anyone have any other suggestions?
it never worked on 1.5 for me...
This is because you are using a modified firmware.
You have to replace the busybox ls file with the toolbox ls file.
but my ls is linked to toolbox ?
just had another go, it appears you have to close the file explorer and open it again
Ah ok thanks. I didn't know that. What is the easiest way for me to get a file out of an application directory then. I want to get the sqlite database from an app I am writing off the phone.
I'm using apps2sd so I thought the application data should reside in /system/sd/app but if I navigate there in linda or astro it is blank. /data/app is also blank.
BGH80 said:
I'm using apps2sd so I thought the application data should reside in /system/sd/app but if I navigate there in linda or astro it is blank. /data/app is also blank.
Click to expand...
Click to collapse
/data/data
jashsu said:
/data/data
Click to expand...
Click to collapse
/data is also empty
Have you tried opening it with Term Emu or adb instead of a file manager?
Well I'm a bit stuck now.
I got thinking my apps 2 sd wasn't working so I just decided to switch to the unionfs method.
Now my phone is looping. I don't want to do a wipe and I don't have access to ADB here at work so I can't copy a new update.zip ROM to my phone.
So I can't check anything until I get home and can reflash my phone which will hopefully fix the problem.
Ah what a nightmare. The unionfs apps2sd didn't work on the first attempt so I ended up having to reformat, wipe, reinstall etc. I'm back up and running now and was able to get the file I wanted via adb pull.
How come file managers don't show the contents of folders such as /data/data/ ?
BGH80 said:
Ah what a nightmare.
Click to expand...
Click to collapse
Welcome to A2SD.
I accidentally Deleted my Launcher using Titanium Backup. Now as you can image my phone is very limited. Can someone please upload a launcher.apk that i can install?
roberto188 said:
I accidentally Deleted my Launcher using Titanium Backup. Now as you can image my phone is very limited. Can someone please upload a launcher.apk that i can install?
Click to expand...
Click to collapse
pull it out of the rom that you flashed) and push it to your phone (/system/app)
Ok
Ok I have the rom...how do I extract the data from the rom?
open the zip file and extract it maybe?
open the rom zip, find the launcher2.apk and extract it somewhere (sdk tools folder usually best)
if in windows, hit shift+right click in a blank area of that explorer window/directory the apk now resides
in console window type:
adb remount
adb push Launcher2.apk /system/apps/
Just reflash your ROM, much easier for someone who may not know what they are doing.
daveid said:
Just reflash your ROM, much easier for someone who may not know what they are doing.
Click to expand...
Click to collapse
+1 agree
daveid said:
Just reflash your ROM, much easier for someone who may not know what they are doing.
Click to expand...
Click to collapse
On the flip side, he's got to learn somewhere and this would be a pretty easy task in the grand scheme of things.
Gang, I've searched and couldn't find. I rooted the Sprint Nexus S 4G and installed CW recovery.
Would some one please be kind enough to point me on how to unroot and return to stock recovery for a return.
Thank you!
Why do you want to return it?
dmora01 said:
Why do you want to return it?
Click to expand...
Click to collapse
Exchanging for another, I appear to have a defective screen which flickers when phone is shaken.
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
r80ies said:
Yeah this would be good to know, as when you unlock it there is now a big unlocked icon when booting. I could see a sprint rep throwing the phone in my face saying they can't support it.
Click to expand...
Click to collapse
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
What about the custom CWM recovery?
oldblue910 said:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
a2k said:
What about the custom CWM recovery?
Click to expand...
Click to collapse
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
oldblue910 said:
Oh, my bad. Before deleting root, go to /system/etc and find whatever you renamed the install-recovery.sh file to, and rename it back to install-recovery.sh. Then follow my instructions to delete root, and once you reboot back into the ROM, it will erase ClockworkMod and install the stock recovery. That said, here is a set of updated instructions:
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Many thanks!!!!
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
a2k said:
Titanium Backup did install busybox, how do I delete it along with all the symlinks that it created?
Click to expand...
Click to collapse
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
oldblue910 said:
Did Titanium Backup install busybox into /system/xbin? If so, (I assume you have a nandroid backup just in case), I would delete absolutely everything in that folder except dexdump. If it installed busybox somewhere other than /system/xbin, then we'll cross that bridge when we get there.
Click to expand...
Click to collapse
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
a2k said:
I don't believe it to be installed in /system/xbin/ as the only two items showing there are:
dexdump
su
Click to expand...
Click to collapse
OK check /system/bin then. Is BusyBox in there?
oldblue910 said:
OK check /system/bin then. Is BusyBox in there?
Click to expand...
Click to collapse
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
a2k said:
OldBlue, I really appreciate your assistance!
I feel really stupid, there are numerous files inside /system/bin, heck I stopped counting at 40!! I do not see a "BusyBox" file there, what should I look for?
Click to expand...
Click to collapse
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
oldblue910 said:
Yeah there will be a bunch. Do you have a terminal emulator installed? If so, go into the terminal emulator:
Type "su" (without quotes)
Type "busybox which busybox" (without quotes)
Tell me what it says.
Click to expand...
Click to collapse
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
a2k said:
I installed Terminal Emulator:
Typed: su
Typed: busybox which busybox
Response: busybox: not found
Although TB says:
Root Access: OK (BusyBox 1.16.0 from app)
Click to expand...
Click to collapse
Oh no wonder! You're all set then. BusyBox is located within Titanium Backup's data folder. You don't need to worry. BusyBox will go away when you uninstall Titanium. So just follow my updated instructions and you're good. Let me know if you have any problems. Make sure you have a nandroid backup of your ROM before you delete root, just in case! You can never be too careful!
Use a file manager like Root Explorer or SuperManager (any file manager that can run with root access)
Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
If you installed busybox, you'll have to delete it along with all the symlinks that it created.
Delete /system/app/Superuser.apk
Delete /system/xbin/su
Delete /system/bin/su
Reboot the phone into the bootloader.
Plug the phone into USB.
Type "fastboot oem lock"
Good to go.
Click to expand...
Click to collapse
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
spdwiz18 said:
Quote: Go into /system/etc and find the install-recovery.sh file that you renamed originally, and rename it back to install-recovery.sh. (This will ensure that the stock recovery will be restored on first boot)
what if there is no install-recovery.sh file!!!!!! under system/etc?
i didnt delete it!!!!!!! i was woundering way everybody was talking about renameing it? i dont have that file..
Click to expand...
Click to collapse
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
oldblue910 said:
Hmmm....try just /etc. Is it in there? Every stock Android build since 2.3.1/GRH78 has had that file in there. It checks the MD5 hash of the current recovery and if it doesn't match up, it flashes the stock one over it. That's really strange.
Click to expand...
Click to collapse
Nope .... no such file. I even did a search for it with root explorer and it does not come up. If worse come to worse ill pull it from someone's Tom just so I have it on my phone. But I know I did not delete it.
Sent from my Nexus S 4G using XDA Premium App
That is very strange indeed. I wonder if Google didn't install it on the Nexus S 4G. Can any other NS4G owners verify if /etc/install-recovery.sh exists on your phone?
Hi I was wondering if it were possible to run adb on my infinity so I can hook my phone up to it.
I'm getting real tired of firing my old laptop to use adb for my phone.
shaggydiamond said:
Hi I was wondering if it were possible to run adb on my infinity so I can hook my phone up to it.
I'm getting real tired of firing my old laptop to use adb for my phone.
Click to expand...
Click to collapse
I found this a while ago, but never tried it:
http://forum.xda-developers.com/showthread.php?t=2033722
_that said:
I found this a while ago, but never tried it:
http://forum.xda-developers.com/showthread.php?t=2033722
Click to expand...
Click to collapse
Thanks, but this won't work for me, it's a flashable zip and I don't want to unlock my bootloader(yet)
shaggydiamond said:
Thanks, but this won't work for me, it's a flashable zip and I don't want to unlock my bootloader(yet)
Click to expand...
Click to collapse
Shouldn't need to flash anything. Just download the zip file, extract the contents, copy the `kadb' file to /system/bin (or /system/xbin), and finally set permissions (chmod 0755 /system/bin/kadb). To use, just open a terminal emulator and run the binary.
Haven't tried it myself, but it looks like what you're looking for.
becomingx said:
Shouldn't need to flash anything. Just download the zip file, extract the contents, copy the `kadb' file to /system/bin (or /system/xbin), and finally set permissions (chmod 0755 /system/bin/kadb). To use, just open a terminal emulator and run the binary.
Haven't tried it myself, but it looks like what you're looking for.
Click to expand...
Click to collapse
Oh i might have misread it then. i'll give it a go this weekend
Anybody know how to change the destination folder when installing the modified apk?
wileout said:
Anybody know how to change the destination folder when installing the modified apk?
Click to expand...
Click to collapse
What do you mean exactly?
Are you installing using a flashable zip or the application?
A flashable zip is the easiest way so you can edit the installer script to place it in whatever directory you wish.
I never use the apk tools themselves for installing.
You can also boot to recovery and mount system.
Then from terminal, EX:
Code:
adb push MyCoolMod.apk /system/app
Let me know if that helps, or if you need more info, or are deadset on using that app to install and we can go from there.
santod040 said:
What do you mean exactly?
Are you installing using a flashable zip or the application?
A flashable zip is the easiest way so you can edit the installer script to place it in whatever directory you wish.
I never use the apk tools themselves for installing.
You can also boot to recovery and mount system.
Then from terminal, EX:
Code:
adb push MyCoolMod.apk /system/app
Let me know if that helps, or if you need more info, or are deadset on using that app to install and we can go from there.
Click to expand...
Click to collapse
I was trying to use the tool to push iy becaude i cant get adb to push it at all...but the tool keeps trying to push it to data/app or something like that and i need it to go to system/priv-app
ok tried adb pushing it again and no go even doing it with your command. any ideas?
wileout said:
ok tried adb pushing it again and no go even doing it with your command. any ideas?
Click to expand...
Click to collapse
My bad, forgot a slash, try it again.
Code:
adb push MyCoolMod.apk /system/priv-app/
santod040 said:
My bad, forgot a slash, try it again.
Code:
adb push MyCoolMod.apk /system/priv-app/
Click to expand...
Click to collapse
I did that man it just restarts adb like i put in a bad command or it says cannot stat blah blah blah file or directory not found
Ive had tigerstown tryin to help me out too and he has no idea whats going on
well got adb to push it but I lost my clock widget all together lol
wileout said:
well got adb to push it but I lost my clock widget all together lol
Click to expand...
Click to collapse
Using stock data cable? Had that be a problem on other devices when pushing files.
Sent from my HTC6525LVW using Tapatalk
wileout said:
well got adb to push it but I lost my clock widget all together lol
Click to expand...
Click to collapse
You need to do:
adb remount /system rw
adb push test.apk /system/priv-app
jsaxon2 said:
You need to do:
adb remount /system rw
adb push test.apk /system/priv-app
Click to expand...
Click to collapse
Do i replace test with the name of the file?
wileout said:
Do i replace test with the name of the file?
Click to expand...
Click to collapse
Yes sir.
You also need to have the file in your adb directory and start the command prompt from there.
There are other ways to do it, but this should work for you.
jsaxon2 said:
Yes sir.
You also need to have the file in your adb directory and start the command prompt from there.
There are other ways to do it, but this should work for you.
Click to expand...
Click to collapse
I got the widget back by going into the priv-app folder and clicking it and installing it but now it force closes so im assuming its something on my end with how it was signed and stuff
wileout said:
I got the widget back by going into the priv-app folder and clicking it and installing it but now it force closes so im assuming its something on my end with how it was signed and stuff
Click to expand...
Click to collapse
After you push to the /system/priv-app folder, did you reboot? That should have installed it for you. Might also be a permissions problem. Make sure the permissions on your file are the same as the permissions on the rest of the files in that folder.
jsaxon2 said:
After you push to the /system/priv-app folder, did you reboot? That should have installed it for you. Might also be a permissions problem. Make sure the permissions on your file are the same as the permissions on the rest of the files in that folder.
Click to expand...
Click to collapse
Ok ill try that...thanks for your help ill report back
jsaxon2 said:
After you push to the /system/priv-app folder, did you reboot? That should have installed it for you. Might also be a permissions problem. Make sure the permissions on your file are the same as the permissions on the rest of the files in that folder.
Click to expand...
Click to collapse
Tried that and im still getting force closes so its something on my end im assuming