Read-Only file system error when trying to push via adb - Xperia Z3 Compact Q&A, Help & Troubleshooting

I've tried running a script for TA partition restoration (I had it backed up) but ended up with "Permission denied" error while it tried pushing a file into my internal sdcard.
Code:
=======================================
PUSH BACKUP TO SDCARD
=======================================
failed to copy 'tmpbak\TA.img' to 'sdcard/restoreTA.img': Permission denied
*** Restore unsuccessful. ***
So I opened up adb myself to see if I am able to push manually but it fails despite what destination I choose with "error: Read-Only file system".
Code:
android-sdk-windows\platform-tools>adb
push C:\yo.txt root\sdcard
adb: error: failed to copy 'C:\yo.txt' to 'root\sdcard': Read-only file system
Any thoughts?

Related

Clockwork FRF83

Flashing from CM 5.0.8 using Rom Managers FRF83. It downloads three files, ERE27, FRF50, and FRF83. I get this error when installing part two
Code:
Installing: SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
Opening update package...
I:Update file path: /sdcard/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
Installing update...
I:Trying update-binary.
installing HTC updater extensions
Failed to mount /dev/block/mtdblock3 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
Verifying current system...
mtd read matched size 2101248 sha e7f20e513e5bd5c30e20670e992092296ee731a0
0 bytes free on /cache (6762912 needed)
error opening /cache/recovery/otatest: No such file or directory
0 regular files in deletable directories
no files can be deleted to free space on /cache
unable to make 6762912 bytes available on /cache
script aborted: assert failed: apply_patch_space(6762912)
assert failed: apply_patch_space(6762912)
E:Error in /sdcard/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
(Status 7)
Installation aborted.
Failure at line 7:
install_zip SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
From what I'm reading, this means that the updater script from Rommanager doesn't release the mount on system after the first flash, because I can easily navigate to the directory after I receive this error and install it manually. I figure the way it works is after install it umounts.
Just as an FYI, if others are trying this, this is what I did to overcome. 1.Using clockwork recovery
2.mount SD
3.find FRF83fromFRF50
4. copy to /sdcard/update.zip
5. manually install ERE27toFRF50
6. let it boot
7. reboot into stock recovery
8. install update.zip through stock recovery
BOOM FRF83
Ooops, sorry MODs. It originated as a question, but I figured it out mid writing this. Please move to general. Sorry

permission denied on /sdcard

Hi,
I cannot copy update.zip to my device using adb.
from my comman prompt:
C:\asdk\tools>adb devices
List of devices attached
9000b0c52740 device
=> connected
C:\asdk\tools>adb push root.zip /sdcard/update.zip
failed to copy 'root.zip' to '/sdcard/update.zip': Permission denied
=> the problem
C:\asdk\tools>adb shell
$ su
su
# ^C
=> popup on phone, access granted
C:\asdk\tools>adb push root.zip /sdcard/update.zip
failed to copy 'root.zip' to '/sdcard/update.zip': Permission denied
=> nothing changed
I have JM5, SamSet 1.9d. Busybox installer is installed.
busybox installer says that phone is rooted, but when I try to install busybox it says error. nand is not unlocked or remount is not possible.
If I use windows explorer I can copy an update.zip to /sdcard but then recovery mode says "cannot open".
What wrong?
How can this be fixed?
Thanks in advance
HolyFreak

[Q] OTA Update failed to install correctly. Recovery missing...

Yesterday, the OTA update was pushed to my D3 by verizon. It appearred to install correctly, but I noticed issues with a couple apps. I tried to enter recovery, but it's not there! I checked /system and it is full. 0 free space. I need to reinstall the recovery. Any help would be appreciated.
UPDATE: I rooted my D3, and then pushed the recovery to the phone. I then ran the install .sh and was able to boot into recovery.
AXi0N420 said:
Yesterday, the OTA update was pushed to my D3 by verizon. It appearred to install correctly, but I noticed issues with a couple apps. I tried to enter recovery, but it's not there! I checked /system and it is full. 0 free space. I need to reinstall the recovery. Any help would be appreciated.
Click to expand...
Click to collapse
I have the same issue. Update installs (Thanks to Petes tools for bloatware recovery) but camera app is not working. Try to boot into recovery and get this message:
Code:
AP Fastboot Flash Mode (S) (Boot Failure)
0A.53
BAttery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG:recovery)
Based on suggestions here I used Titanium Backup to backup and remove a few verizon bloatware apps and got up to 54MB free on recovery partition, but still can't boot into recovery. Tried doing an adb push of the install-recover.sh from the update to /system/etc and still can't boot into recovery. When I run sh /etc/install-recovery.sh I get this:
Code:
[email protected]_solana:/# sh /etc/install-recovery.sh
sh /etc/install-recovery.sh
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
contents of partition "recovery" didn't match MTD:recovery:2048:ed2ac38df0bab0b2
382dc3330707ff884981f335
file "MTD:recovery:2048:ed2ac38df0bab0b2382dc3330707ff884981f335" doesn't have a
ny of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
applying patch to MTD:boot:8388608:c2c527aa31b9e529de6c6a574e4e589f1d2965d9
LoadPartitionContents called with bad filename (MTD:recovery)
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
contents of partition "recovery" didn't match MTD:recovery
partition read matched size 8388608 sha c2c527aa31b9e529de6c6a574e4e589f1d2965d9
544096256 bytes free on /cache (8388608 needed)
Unknown patch file format
I do not really know where to go from here. Because I haven't yet posted ten times, I can't respond directly to the thread where they were discussing this solution. Any help would be greatly appreciated.
I pushed recovery-from-boot.p and install-recovery.sh files from an update I downloaded from another thread. I ran the .sh from terminal on the phone, and it installed the recovery partition. Did you push both files?
recovery-from-boot.p is located at /system/recovery-from-boot.p
AXi0N420 said:
I pushed recovery-from-boot.p and install-recovery.sh files from an update I downloaded from another thread. I ran the .sh from terminal on the phone, and it installed the recovery partition. Did you push both files?
recovery-from-boot.p is located at /system/recovery-from-boot.p
Click to expand...
Click to collapse
Thanks a lot! This seems to have worked. I ran the install-recovery.sh from an adb shell and am able to boot into recovery again. Now I just have to reinstall all the bloatware and run the patch again.

V8 rooted but no CWM

I was on v8 non-rooted.
I followed the instructions here to the letter:
http://forum.xda-developers.com/showthread.php?t=1566729&page=4
didn't have any issues at all, no errors.
I'm confirmed on V8 and do have root but can't access CWM. Attempting to run the new AIO again gives the following:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: Read-only file system
7781 KB/s (5345280 bytes in 0.670s)
Unable to chmod /system/xbin/busybox: Read-only file system
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Press any key to continue . . .
Any ideas how to get to CWM?
Looks like you need to root again after your upgrade. Run MT's Root&RecoveryAIO.bat again and select the "Root ZV8" option.
[EDIT]
My bad. That's what you are trying to do! I've been up all night and am tired. Did you get any errors when you ran the "Prepare for Update" option before you upgraded? That option actually pushes the superuser files back to your phone and the "Root ZV8" option just goes back and set's the permissions. You can try manually running these commands with adb first.
Files\adb push Files\zergrush /data/local/tmp/zergrush
Files\adb shell "chmod 755 /data/local/tmp/zergrush"

MTP broken, ADB sideload and push don't work

I installed TWRP and am trying to transfer the xiaomi.eu MIUI10 rom to the device to flash it, but I keep getting errors.
Trying to drag and drop through explorer always results in the same error:
(Cannot copy rom.zip. The device has either stopped responding or has been disconnected.)
Trying to sideload gives the error:
(Total xfer: 0.00x)
Trying to push gives the error:
(adb: error: failed to copy 'rom.zip' to '/sdcard/rom.zip': remote couldn't create file: Required key not available
rom.zip: 0 files pushed. 49.2 MB/s (262112 bytes in 0.005s)
Edit:
I realize I wasn't in sideload when trying to push. Now it gives a different error:
(adb: error: connect failed: closed)

Categories

Resources