Okay, it will be kinda noob-ish but I searched but couldn't find anything. I have latest liberated rom rooted with unrevoked and I cant push anything to /system/customize or wherever on the phone storage. Cant adb push, when I try to remount with write access phone restarts. Any suggestions?
Code:
C:\Users\Evan\Desktop\New folder\sdk\tools>adb remount
remount succeeded
C:\Users\Evan\Desktop\New folder\sdk\tools>adb push widget.txt /system/customize
failed to copy 'widget.txt' to '/system/customize/widget.txt': Out of memory
There is memory!
all i can say is try booting into clockworkmod and mount system there.
joachim123 said:
all i can say is try booting into clockworkmod and mount system there.
Click to expand...
Click to collapse
Correct. Since our phone is nand locked, to edit/push/etc the phone would have to be booted into clockwork (without usb cable attached) - mount /system partition - and then attach cable. From there, remount in adb and push / pull / explode (explode isn't really a command... lol)
Oh yeah. Thanks for the answers, clockwork worked lol. Stupid me
Related
My phone keeps booting into recovery mode.
Power on -> Blank -> Reboot -> Recovery
I had the new SPL (the saphire ported one), JF's recovery (i still have it on) and JF1.51.
This happened since i tried to flash the HTC ADP update.zip.
I have tried using the hardSPL, reflashing the saphire SPL, tried flashing back to JF1.5, Rodgers but nothing seems to work
Any ideas?
EDIT: I just checked and it didnt flash the saphireSPL! i dont think adb shell push is copying the update.zip's to the SD card.
EDIT:
SOLUTION:
I was right in that it wasn't copying the updates to the sd card, i borrowed a friends G1, used it to put on the saphireSPL, flashed (and it worked this time), got into fastboot (the hardSPL fastboot didnt seem to work), and restored my nandroid backups! yey! now to try JAC's build
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
Thank you, that'll come in really handy for when i dont have a spare Dream or card reader about!
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
Oh my god... this (hopefully) has fixed the problem I've had for the past two days - I've spent so long reading every thread on here about the SPL problems, etc. I had a feeling the problem was the update wasn't working correctly, but I had no idea why. (It didn't complain, but just went very quickly - much to quick to be doing a full os upgrade).
Thanks!!!
umm how would i even run that script?cuz i keep bootlooping
Jerzdre said:
umm how would i even run that script?cuz i keep bootlooping
Click to expand...
Click to collapse
On Phone:
Recovery -> ALT+X -> Console
On PC
Command prompt
"cd <directory where you have update.zip>"
"adb shell mount /sdcard"
"adb push update.zip /sdcard/update.zip"
On Phone
Hold 'Home' and then:
On PC:
"adb shell reboot"
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
but you can abd push to the ext2 portion of the sd card without mounting while in recovery, correct?
i have my phone updated to 2.1 and rooted. Want to overclock it now but not sure what im supposed to do with the kernel-overclock-update-v3.zip. I have the original PB00IMG.zip i updated and rooted my phone with, am i supposed to use it somehow?? New to this would appreciate any help.
Just use this, Flash it and it will make ur life easyier.
http://forum.xda-developers.com/showthread.php?t=685581
so phone will be stock again right? have to re dload apps and sync contacts and **** again right?
hmm... or u can try to flash the kernel-overclock-update-v3.zip to the one you have
be sure to nand backup first
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
did you flash recovery?
duckingzebra said:
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
Click to expand...
Click to collapse
Hey man,
When you rooted did you flash the Amon-Ra recovery image? If so put the update zip on the root of your sd. Power down your handset. hold the volume UP and the power on will bring you to the recovery menu. Here you have options for back up,flash from zip etc...once there you can select whatever rom/update you want to flash. Remember nandroid is your friend always back up. Also as far as apps etc...check out Titanium back up or one of the other free back up apps in market. I hope this helps you out.
volume up + end button = Recovery
ok, im following the steps to III: Flashing a Custom Recovery. and when i get to the step :adb push recovery.img /sdcard it says :cannot start recovery.img: No such file or directory...is the recovery.img also supposed to gon on the root of my sd card? or just the tools folder, cause its there?
yes its suppose to be on the root of the sdcard too
still says cannot stat 'recovery.img': no such fire or directory
am i supposed to replace /sdcard with /J (which is what my phone comes up as in my computer) -tried that still didn't work...
can u link me to the tut u are using?
http://forum.xda-developers.com/showthread.php?t=647707
QUOTE=TopazAaron]
duckingzebra said:
did you see the tutorial i linked? still cant figure it out.
Click to expand...
Click to collapse
ok
put the Recovery image in the tools/ in the sdk
after that plug ur phone into the comp
now being there in cmd navigate to the /tools/ folder
then type or copy and paste
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
---
now if you still have issues, let me know, sorry i didnt reply, i got busy with other things.
thanks for ur pm tho[/QUOTE]
ok now instead of saying :cannot start recovery.img: No such file or directory
it says error: device not found, when i open my computer my sdcard in my phone shows up and i can open it...
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
TopazAaron said:
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sorry newser here, irc??
Is your phone actually rooted? To check, turn on your phone, then turn on USB debugging through Settings/Applications/Development/USB debugging. Plug your phone into the computer via the USB cable.
In the run box of your computer, type cmd, then enter.
When the command window shows up, changed you your SDK tools directory. On my system it would be:
cd c:\android-sdk-windows\tools
Then run the following command
adb shell
You're rooted if it comes back with
#
If it comes back with
$
try the typing
SU
if it does not change from $ to # then you might want to try rooting again, and be sure to install the Amon_RA recovery
typing exit multiple times will back you out of adb, and the cmd window.
Hope that helps.
Edit: Of course that works for 2.1 leak 3 users as well.
Easier way for you tho, if you boot to hboot with the send and end buttons, you should see hboot with S off if you're rooted. If it's S On you're not.
So i rooted my vibrant with the hopes of removing some of the bloatware. i rooted with the one click root method, loaded clockwork recovery, i know i am rooted but every time i try adb remount i get remount failed: no such file or directory.
so i tried going into clockwork recovery in the partition menu and mounting system there and trying adb remount and got remount failed: operation not permited. i ran adb root and got root can not run on factory builds (or something close to that)
in adb shell ive tried mounting every which way i can think of and nothing works.
ive searched all over and havent been able to find a fix, please help
root explorer didnt work either
also i tried deleting the system apps with root explorer and it would mount either
adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how
cojonesx said:
adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how
Click to expand...
Click to collapse
like i said in my post, i tried shell and couldnt get it to mount. maybe i did it wrong
Ok. So im touching up on my ADB. Messing around trying to transfer files and what not. Now when I try and push and file from my pc to my sdcard it errors me out saying Read-Only File System.
Command im doing is
adb push C:\Android\android.jpg /sdcard/android.jpg
Any ideas where im going wrong here? I have full root access, When I:
adb shell
su
I do not get permission denied... So dont get why this is happening.
Edit: Just looked more into it. I can push to the phone. Just not to the sdcard. I pushed to /data/local for giggles and it worked. Only gives me read only when pushing to the /sdcard.
Thanks for any info.
just tried mine and it worked fine. I first tried it with pushing a file from my sdk dir, and tried it with pushing a file from another directory on the drive. worked both times, not sure what to tell you.
p.s. I'm running the desire z rom
Yeah for some reason its only on the sdcard I cant write to.. USB Debugging is checked. Anyone have the slightest idea as to why I'm unable to write to my sdcard with this Read-only File system error?
Anyone know the shell command to mount the sd card as rw? Been trying to figure this thing out but it has me in a puzzle.
[G2/HTC Vision]
luis86dr said:
Anyone know the shell command to mount the sd card as rw? Been trying to figure this thing out but it has me in a puzzle.
[G2/HTC Vision]
Click to expand...
Click to collapse
Are you making sure that you don't have media mounted? That would screw up /sdcard. For me, it's "umount /media/*; eject /dev/sde" then on the G2 disable USB storage, wait for it to remount the SD card.
If that still doesn't work, what does "adb shell mount" tell you?
Normally, like with /system, it's "busybox mount -o remount,rw /system", but I've never seen /sdcard mounted readonly, unless there are I/O errors (it's mounted to remount ro on failure). Have you tried rebooting your phone?
luis86dr said:
Ok. So im touching up on my ADB. Messing around trying to transfer files and what not. Now when I try and push and file from my pc to my sdcard it errors me out saying Read-Only File System.
Command im doing is
adb push C:\Android\android.jpg /sdcard/android.jpg
Any ideas where im going wrong here? I have full root access, When I:
adb shell
su
I do not get permission denied... So dont get why this is happening.
Edit: Just looked more into it. I can push to the phone. Just not to the sdcard. I pushed to /data/local for giggles and it worked. Only gives me read only when pushing to the /sdcard.
Thanks for any info.
Click to expand...
Click to collapse
Is it possible that you are writing the command wrong? I noticed the slash is opposite on the second half of your command code.
C:\Android\android.jpg /sdcard/android.jpg
Click to expand...
Click to collapse
Figured it out. Had usb storage on. So it wouldn't push turned it off and I was able to push. Thx foe the info
[G2/HTC Vision]
the subject says it all. I've been trying to push apps to my encrypted xoom all afternoon without any luck...
I'll go ahead and admit upfront that I am a noob when it comes to using the sdk... so that could also be a major factor.
adb install (insert exact location+ filename.apk for the app you want to install)
I just tested it out
for example
adb install C:/abc.apk
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
scsa20 said:
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
Click to expand...
Click to collapse
I just tried to execute adb remount (I had not until you mentioned it), but I get a "remount failed: operation not permitted".
Code:
Hannibal:platform-tools dmoore$ ./adb install /Users/dmoore/Documents/android-sdk/platform-tools/AsusReader.apk
1259 KB/s (7747001 bytes in 6.007s)
pkg: /data/local/tmp/AsusReader.apk
Failure [INSTALL_FAILED_DEXOPT]
Additional information: I am on a MacBook Pro using the latest version of the SDK (downloaded it yesterday).
try typing "adb devices" if it does not list your xoom try installing or re-installing the motorola usb drivers
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Sic123 said:
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Click to expand...
Click to collapse
I've already installed the Android File Transfer app... it only allows me to browse the SD card - not the root fs... unless there's something I'm missing...
dmoore44 said:
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Click to expand...
Click to collapse
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Sic123 said:
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Click to expand...
Click to collapse
I have the odex file, so i'm not terribly worried about that.
My major question would be this though... Do I need to go full blown root, or can I just unlock the device?