As the title says, I'm having trouble pushing the busybox binary to my T-mobile G1.
I have ADB running, and have it successfully connected to my phone and can start a shell and everything. The problem is, when I type
Code:
adb push C:\busybox /data/local/busybox
All I get is
Code:
1092 KB/s (0 bytes in 1782264.001s)
and nothing writes. Any help would be greatly appreciated. Thank you.
**Edit**
If it helps to know, I've tried pushing other files, as well as pulling some, but it hasn't worked. The same "0 bytes in 1782264.001s" thing just pops up and nothing happens.
I hope someone can help.
Related
Ok, so I'm pulling apks from the device and here's what happens.
Various commands I've tried:
adb pull /system/sd/app/com.p1.chompsms.apk /Desktop/apks/messaging.apk
adb pull /system/sd/app/com.p1.chompsms.apk /Desktop/apks/
adb pull /system/sd/app/com.p1.chompsms.apk /Desktop/apks/com.p1.chompsms.apk
adb pull /data/app/com.p1.chompsms.apk /Desktop/******
My results:
**** kb/s (0 bytes transferred in **** s)
^random kb/s and different time intervals
Wtf...
I'm running my apps of the sd card... but the device is on, the ext2 partition is mounted.
Jf 1.41 Rc30
P.S. Just one time, I had it where the cmd prompt said the same thing, but the image of the file showed up in the destination, but it was still 0 bytes, so it was an empty file.
did you remount first?
Yep.
Remount succeeded. <_<
This is bugging me a lot.
just ignore the kb/s and bytes transfered and whatnot. it isn't accurate.
I know it isn't.
The thing is though, the cmd prompt seems to think it pulled the file, but it didn't.
The file doesn't show up in the destination folder at all. I tried pulling them to the full address and the shortcut and nothing happens, but the prompt says it was done.
command prompt? are you on windows? last I checked /Desktop/<whatever> isn't a valid path on windows (if you're on mac/linux, sorry, "command prompt" is windows speak )
Yeah, it's windows. I'll eventually convert to linux once I get more comfortable with it.
I've tried the full path C:/..../apks, and I used the shortcut, which is /desktop, because the current directory in command prompt is C:/Users/Admin/, but that isn't the problem.
The damned apks won't transfer.
If it was an invalid directory, it would give me that error, but alas it isn't.
I am not in adb shell command either.
i think that you should try ./desktop/<whatever> instead of /desktop/<whatever>
EDIT: the regular old /data/app/<whatever>.apk and /system/app/<whatever>.apk should work, too. No need to use /system/sd/<whatever> since you symlinked it to /data/app/ when you moved your apps to your SD card.
i used all of it.
I just gave up on using this computer with w7 x64 and used a 32 Xp, and it worked just fine. Might be the driver. Idk.
So yeah, I pulled them. Throwing out my little proggy tonight. Assuming all the testing is functional.
By default, if you dont specify a directory to pull it to, it should end up being pulled to the same folder as adb.
APrinceAmongMen said:
Ok, so I'm pulling apks from the device and here's what happens.
Various commands I've tried:
adb pull /system/sd/app/com.p1.chompsms.apk /Desktop/apks/messaging.apk
adb pull /system/sd/app/com.p1.chompsms.apk /Desktop/apks/
adb pull /system/sd/app/com.p1.chompsms.apk /Desktop/apks/com.p1.chompsms.apk
adb pull /data/app/com.p1.chompsms.apk /Desktop/******
My results:
**** kb/s (0 bytes transferred in **** s)
^random kb/s and different time intervals
Wtf...
I'm running my apps of the sd card... but the device is on, the ext2 partition is mounted.
Jf 1.41 Rc30
P.S. Just one time, I had it where the cmd prompt said the same thing, but the image of the file showed up in the destination, but it was still 0 bytes, so it was an empty file.
Click to expand...
Click to collapse
Are you using Vista?
Have tried just moving your "apks" folder to the C: drive and using: adb pull /system/sd/app/com.p1.chompsms.apk c:\apks (making sure you use the correct slash)
I was using windows 7.
Idk. There was some kind of issue. I just threw it on xp and did it there. No biggie.
Hey All,
Whenever I do a pull from ADB, it appears to work, but the file never gets copied.
Code:
C:\>adb pull /system/build.prop
272 KB/s (2786 bytes in 0.010s)
But there is no build.prop file in my C:\. Do I need new drivers? I can connect to adb shell just fine and su just fine. Is this a permissions issue? My phone is rooted, but I am guessing that ADB doesn't have root permissions. Any ideas?
I'm too new of a member to be able to post my issue in that forum so I will post it here.
I got to the point where It checked for updates on the phone, then starts to reboot, and during the reboot the program continues and starts giving more errors. I didn't see a similar issue in the thread that pertained to my particular issue. Here is the error I'm getting :
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
46 KB/s (334 bytes in 0.007s)
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was created, looking good.
remount succeeded
3905 KB/s (91980 bytes in 0.023s)
5023 KB/s (1116332 bytes in 0.217s)
rm failed for /system/app/Superuser.apk, No such file or directory
4918 KB/s (574184 bytes in 0.114s)
Error: Could not access the Package Manager. Is the system running?
Unable to chmod /system/app/Superuser.apk: No such file or directory
Done! Rebooting...
Press any key to continue . . .
I'm assuming the root didn't work. How would I know? Any ideas?
Thanks
Znichols513 said:
I'm too new of a member to be able to post my issue in that forum so I will post it here.
I got to the point where It checked for updates on the phone, then starts to reboot, and during the reboot the program continues and starts giving more errors. I didn't see a similar issue in the thread that pertained to my particular issue. Here is the error I'm getting :
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
46 KB/s (334 bytes in 0.007s)
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was created, looking good.
remount succeeded
3905 KB/s (91980 bytes in 0.023s)
5023 KB/s (1116332 bytes in 0.217s)
rm failed for /system/app/Superuser.apk, No such file or directory
4918 KB/s (574184 bytes in 0.114s)
Error: Could not access the Package Manager. Is the system running?
Unable to chmod /system/app/Superuser.apk: No such file or directory
Done! Rebooting...
Press any key to continue . . .
I'm assuming the root didn't work. How would I know? Any ideas?
Thanks
Click to expand...
Click to collapse
Check your app drawer for SuperSU. If it's there click it and see if you can update the binary. If you can, you're rooted. If you can't or if it's not there than you need to repeat the process until it works.
_MetalHead_ said:
Check your app drawer for SuperSU. If it's there click it and see if you can update the binary. If you can, you're rooted. If you can't or if it's not there than you need to repeat the process until it works.
Click to expand...
Click to collapse
Ok. It is there and it asked me to update, and that part worked. So... I guess I'm rooted then? I can move on to the bootloader unlocking then?
Znichols513 said:
Ok. It is there and it asked me to update, and that part worked. So... I guess I'm rooted then? I can move on to the bootloader unlocking then?
Click to expand...
Click to collapse
Yep, youre rooted. Now go and get that bootloader unlocked and flash CleanROM!
Okay so I rooted and unlocked BL. I also used fastboot to flash CWM, but when I try to boot into recovery, it just gets stuck on the "HTC Quietly Brilliant" page and a message in red text underneath.
I've tried reflashing it a few times and no results.
Hello,
Try downloading Goomanager in Google Play and going to "options" install recovery script, it isn't CWM but I actually like it much more. Good Luck
ryan9316 said:
Hello,
Try downloading Goomanager in Google Play and going to "options" install recovery script, it isn't CWM but I actually like it much more. Good Luck
Click to expand...
Click to collapse
This worked. Thanks a lot!
I welcome all and please help me.
I have HTC ONE X AT&T 1.85.502.3
USB debugging - enabled
fastboot - disable
HTCDriver3.0.0.007 -installed
HTC sync - disable
I tried this method "[ROOT] 1.85 One Click Root! - ACT NOW, MAY NOT LAST FOREVER!" http://forum.xda-developers.com/showthread.php?t=1709424
After starting the root.bat i see only:
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
10 KB/s (334 bytes in 0.031s)
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
Next, nothing happens.
"If you are stuck at "waiting for device to reboot" for a long time or you get "/data/local.prop was not created, exit the script, try again." followed by lots of junk, reboot your phone and push your clock forward two days, reboot, and try again."
I made as written here many times, but it did not help.
I tried this method "[ROOT] 1.85 - New, working method - ACT NOW, MAY NOT LAST FOREVER!" http://forum.xda-developers.com/showthread.php?t=1709296
I did everything by the instruction. But after entering
"adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so"
I see
C:\root>adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
C:\root>adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdms
como.so
link failed File exists
Kerp setting the clock forward and retrying. It should take.
18th.abn said:
Kerp setting the clock forward and retrying. It should take.
Click to expand...
Click to collapse
Put clock on phone and the computer at 2 o'clock forward, and from the second attempt it was possible. Thanks)
Right,
I've got this Q-Ware 9.7" tablet which has the Allwinner A10 / Mali setup.
Yesterday I tried to install CM9 on this tablet, but since I'm writing this post it did not work out as intended.
I know there was an issue with the Touchpad not working - which I encountered myself as well. I then installed the "fix" and some compatibility package which was supposed to fix that, but it didn't.
A guy on another forum pointed me towards another compatibility fix that I might have to install as well (was for momo8), but after installing that one the tablet just is not showing anything anymore ........ at all.
It does seem to work as I can connect to it with ADB and DroidExplorer, but that is where it ends.
What I've tried so far is:
- Fix_permissions (it says that it is not allowed to fix permissions in the /system/ folders;
- Clear Dalvik_Cache and /data/;
- Tried to reinstall CWM via ADB;
- Tried to run this command someone else gave me:
adb shell "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
Returns this:
[email protected]:/ $ echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1
conv=sync; sync; reboot
x dd of=/dev/block/nandf count=1 conv=sync; sync; reboot <
0+1 records in
1+0 records out
512 bytes (512B) copied, 0.001510 seconds, 331.1KB/s
reboot: Operation not permitted
Click to expand...
Click to collapse
- I also created a logfile with logcat, please see here: pastebin suffix: dWWXGnPA (cannot post links yet).
- Tried wiping the 'system' folder, does not work as it gives these errors:
unlink() error on '/system/xbin/uudecode' 'Read-only file system'
- It has enough battery (100%) according to the /capacity command in ADB;
- I am able to push/pull things over via ADB or with external SDcard;
Also I noticed the daemon connection seems to drop very often, it just kicks me out on a regular basis.
DroidExplorer works and finds the tablet, but is not showing any folders. I also see the 'boot' folder for example is 0bytes (not sure whether this can also we caused by rights?).
Any help would be appreciated a lot
Before I forget to add ... it is only giving me a blank/black screen. Occasionally I see the backlight change a bit in power, but that's it.