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
Hallo,
I use since some months the ROM CROMi-X 6.1 on my tablet.
Yesterday suddenly became a black screen and if would restart he stuck on the ASUS bootlogo, a ****ing boot loop.
I try to restart the old ROM and the new CROMi-X, but nothing. The installation comleted, but i can't see any change.
And if I start in recovery he write something like could not mount /...cache ... or ... data
Could any one pls help me?
Thanks
:crying:
I can't flash a other recovery or something else.
This is my log from the installation.
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMBi-kk
ROM Version : CM11-KitKat-4.4.4-20140714-DEODEX
ROM Author : sbdags/lj50036
Device : Asus Transformer TF701T
Start at : Wed Jul 16 09:41:55 2014
Thank you for installing CROMBi-kk KitKat 4.4.4!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System.....
Extract: /tmp/fsck.ext4
Extract: /tmp/mkfs.ext4
Extract: /tmp/tune2fs.ext4
Backing up CM11 Addons.....
mount: failed to mount /dev/block/mmcblk0p1 at /system: Invalid argument
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 11
run_program: child exited with status 127
about to run program [/sbin/umount] with 2 args
about to run program [/sbin/umount] with 2 args
umount: can't umount /data: Invalid argument
run_program: child exited with status 1
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed
Tuning System.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA at /data: Invalid argument
Wiping Dalvik-cache.....
Wiping Cache.....
Installing Core System.....
Extract: /system/addon.d/50-cm.sh
Extract: /system/addon.d/blacklist
Extract: /system/app/Apollo.apk
Extract: /system/app/BasicDreams.apk
Extract: /system/app/Bluetooth.apk
Extract: /system/app/BluetoothExt.apk
Extract: /system/app/Browser.apk
Extract: /system/app/CMFileManager.apk
Extract: /system/app/CMWallpapers.apk
Extract: /system/app/Calculator.apk
Extract: /system/app/Camera2.apk
Extract: /system/app/CertInstaller.apk
Extract: /system/app/DSPManager.apk
Extract: /system/app/DeskClock.apk
Extract: /system/app/Development.apk
Extract: /system/app/DocumentsUI.apk
Extract: /system/app/DownloadProviderUi.apk
Extract: /system/app/Email.apk
Extract: /system/app/Exchange2.apk
Extract: /system/app/Galaxy4.apk
Extract: /system/app/Gallery2.apk
Extract: /system/app/HTMLViewer.apk
Extract: /system/app/HoloSpiralWallpaper.apk
Extract: /system/app/KeyChain.apk
Extract: /system/app/LatinIME.apk
Extract: /system/app/LiveWallpapers.apk
Extract: /system/app/LiveWallpapersPicker.apk
Extract: /system/app/LockClock.apk
Extract: /system/app/MagicSmokeWallpapers.apk
Extract: /system/app/NoiseField.apk
Extract: /system/app/PacProcessor.apk
Extract: /system/app/PackageInstaller.apk
Extract: /system/app/PhaseBeam.apk
Extract: /system/app/PhotoPhase.apk
Extract: /system/app/PhotoTable.apk
Installing Options.....
Kernel Preparation
- 10.26.1.18 CM11 Kernel
DPI Preparation
- 320 DPI
Extract: /tmp/upd-build-prop.sh
Resolution Preparation
- 2560x1600 res
Extract: /tmp/res-build-prop.sh
Boot Animations
- CROMBi-kk BLUE
Launcher
- Apex Launcher
Google Apps
- Google Core Libraries and Play Store
- Google Calendar
- Google Now and Voice Search
- Google Music
- YouTube
- Google Maps
- Google Mail
- Google Hangouts
- Google Plus
- Google TTS
- Google Ears
Misc Apps
- ES File Explorer
- AdAway installed
- Terminal Emulator
- Titanium Backup
Extract: /data/app/com.keramidas.TitaniumBackup-1.apk
- DropBox
Extract: /data/app/com.dropbox.android-1.apk
- CM11 Inverted BetterBean Blue Theme
Extract: /data/app/com.blackout1911.theme.BetterbeanThemeFree-1.apk
Installing CROMBi-kk System Tweaks.....
Extract: /tmp/crombikk-build-prop.sh
about to run program [/tmp/crombikk-build-prop.sh] with 1 args
sed: can't create temp file '/system/build.propMisvwq': Read-only file system
sed: can't create temp file '/system/build.propITfIQ1': Read-only file system
sed: can't create temp file '/system/build.propOmKZV2': Read-only file system
/tmp/crombikk-build-prop.sh: line 6: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 7: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 8: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 9: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 10: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 11: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 12: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 13: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 14: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 15: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 16: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 17: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 18: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 19: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 20: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 21: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 22: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 23: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 24: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 25: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 26: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 27: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 28: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 29: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 30: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 31: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 32: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 33: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 34: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 35: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 36: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 37: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 38: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 39: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 40: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 41: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 42: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 43: can't create /system/build.prop: Read-only file system
run_program: child exited with status 1
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Xposed App installed
Extract: /data/app/com.ceco.kitkat.gravitybox-1.apk
Extract: /data/app/com.e_vertise.dopa.phab7-1.apk
Installing build.prop
about to run program [/tmp/upd-build-prop.sh] with 1 args
/tmp/upd-build-prop.sh: line 2: can't create /system/build.prop: Read-only file system
/tmp/upd-build-prop.sh: line 3: can't create /system/build.prop: Read-only file system
/tmp/upd-build-prop.sh: line 4: can't create /system/build.prop: Read-only file system
run_program: child exited with status 1
about to run program [/tmp/res-build-prop.sh] with 1 args
sed: can't create temp file '/system/build.prop6OKOeU': Read-only file system
sed: can't create temp file '/system/build.proppx4cD3': Read-only file system
sed: can't create temp file '/system/build.propShUKmO': Read-only file system
sed: can't create temp file '/system/build.propzZny5M': Read-only file system
sed: can't create temp file '/system/build.propGeSQmg': Read-only file system
run_program: child exited with status 1
Building symlinks.....
symlink: failed to symlink /system/bin/dump.f2fs to ../bin/fsck.f2fs: Read-only file system
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
Installer Error (Status 7)
End at : Wed Jul 16 09:42:26 2014
In your first post you talk about CROMi-X 6.1 (which is 4.3), but in your 2nd post you try to flash 4.4.4 which is CROMBi-kk I guess.
I think you need a full wipe going from the one to the other.
Yes this is a other try, the reinstall from 4.3 was the same problem.
And if i try a full wipe a get a message with no mount error.
For whatever reason CWM is not allowing you to mount your /system as rw and /data is not getting mounted.
Have you tried formatting /data? Not just wiping it. You will lose everything on the internal sdcard - be warned.
Failing that install the latest CWM 6.0.5.0 from droid basement and try again.
I'm a little desperate.
I made a fullwipe and factory reset in recovery.
But somehow it is not so pretty.
Because the data I'm not worried, the main thing is it goes again.
How do I make a complete formatting in recovery?
I try to install some different recoverys and the fastboot say all ok, but if i boot in recovery i see the old one.
Pls I don't have 450€ again.
nero0345 said:
I'm a little desperate.
I made a fullwipe and factory reset in recovery.
But somehow it is not so pretty.
Because the data I'm not worried, the main thing is it goes again.
How do I make a complete formatting in recovery?
I try to install some different recoverys and the fastboot say all ok, but if i boot in recovery i see the old one.
Pls I don't have 450€ again.
Click to expand...
Click to collapse
Type out the commands you are using to install the recovery please.
To format /data
Go to CWM
mounts and storage
format /data
format /data and /data/media (/sdcard)
Probably the second one that you want.
I use
fastboot recovery recovery.img
And i get a positiv message
nero0345 said:
I use
fastboot recovery recovery.img
And i get a positiv message
Click to expand...
Click to collapse
You should be using this command:
Code:
fastboot flash recovery recovery.img
Sry, I write it wronge, I have tried to install the recovery with this command you write, but in the terminal i get the message all ok and done. But if I would boot, the old one ist loading and starting, not this one I try to install.
Sry for the longe time, I was at work.
What should I make after format /data?
sbdags said:
You should be using this command:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Sry, I write it wronge, I have tried to install the recovery with this command you write, but in the terminal i get the message all ok and done. But if I would boot, the old one ist loading and starting, not this one I try to install.
Sry for the longe time, I was at work.
What should I make after format /data?
nero0345 said:
Sry, I write it wronge, I have tried to install the recovery with this command you write, but in the terminal i get the message all ok and done. But if I would boot, the old one ist loading and starting, not this one I try to install.
Sry for the longe time, I was at work.
What should I make after format /data?
Click to expand...
Click to collapse
Are you sure the renamed recovery.img is the file you intend to flash? Happened to me... had an old version still in my fastboot folder and forgot to delete it.
How do you reboot?
Do you see a brief blue progress bar on the boot screen?
Post the output of your cmd window as a screen shot.
After formatting data just reboot.
berndblb said:
Are you sure the renamed recovery.img is the file you intend to flash? Happened to me... had an old version still in my fastboot folder and forgot to delete it.
How do you reboot?
Do you see a brief blue progress bar on the boot screen?
Post the output of your cmd window as a screen shot.
After formatting data just reboot.
Click to expand...
Click to collapse
Yes if I would install a recovery i name the file in recovery.img and yes ist is the only file in the folder.
How should I reboot? Normal
If i start my device i see at first the ASUS Logo and on the top left corner the leter "Device Unlocked" or something else and after 2-4 secends I see the Asus bootlogo and the circle of points that rotat around the circle.
I belive the format is finished, but if I reboot, same problem. I am stuck on the boot screen.
I hope you would like see this?
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.119s]
booting...
OKAY [ 0.028s]
finished. total time: 1.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8192 KB)...
OKAY [ 1.120s]
writing 'recovery'...
OKAY [ 0.279s]
finished. total time: 1.403s
nero0345 said:
Yes if I would install a recovery i name the file in recovery.img and yes ist is the only file in the folder.
How should I reboot? Normal
If i start my device i see at first the ASUS Logo and on the top left corner the leter "Device Unlocked" or something else and after 2-4 secends I see the Asus bootlogo and the circle of points that rotat around the circle.
I belive the format is finished, but if I reboot, same problem. I am stuck on the boot screen.
I hope you would like see this?
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.119s]
booting...
OKAY [ 0.028s]
finished. total time: 1.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (8192 KB)...
OKAY [ 1.120s]
writing 'recovery'...
OKAY [ 0.279s]
finished. total time: 1.403s
Click to expand...
Click to collapse
Why are you doing this first?
Code:
fastboot boot recovery.img
You don't need to and this is probably causing the issue.
sbdags said:
Why are you doing this first?
Code:
fastboot boot recovery.img
You don't need to and this is probably causing the issue.
Click to expand...
Click to collapse
I make it to test it
I try again to install a ROM after format /date and /cache, but nothing.
I can cry.
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMBi-kk
ROM Version : CM11-KitKat-4.4.4-20140714-DEODEX
ROM Author : sbdags/lj50036
Device : Asus Transformer TF701T
Start at : Thu Jul 17 11:05:33 2014
Thank you for installing CROMBi-kk KitKat 4.4.4!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System.....
Extract: /tmp/fsck.ext4
Extract: /tmp/mkfs.ext4
Extract: /tmp/tune2fs.ext4
Backing up CM11 Addons.....
mount: failed to mount /dev/block/mmcblk0p1 at /system: Invalid argument
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 11
run_program: child exited with status 127
about to run program [/sbin/umount] with 2 args
about to run program [/sbin/umount] with 2 args
umount: can't umount /data: Invalid argument
run_program: child exited with status 1
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed
Tuning System.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA at /data: Invalid argument
Wiping Dalvik-cache.....
Wiping Cache.....
Installing Core System.....
Extract: /system/addon.d/50-cm.sh
Extract: /system/addon.d/blacklist
Extract: /system/app/Apollo.apk
Extract: /system/app/BasicDreams.apk
Extract: /system/app/Bluetooth.apk
Extract: /system/app/BluetoothExt.apk
Extract: /system/app/Browser.apk
Extract: /system/app/CMFileManager.apk
Extract: /system/app/CMWallpapers.apk
Extract: /system/app/Calculator.apk
Extract: /system/app/Camera2.apk
Extract: /system/app/CertInstaller.apk
Extract: /system/app/DSPManager.apk
Extract: /system/app/DeskClock.apk
Extract: /system/app/Development.apk
Extract: /system/app/DocumentsUI.apk
Extract: /system/app/DownloadProviderUi.apk
Extract: /system/app/Email.apk
Extract: /system/app/Exchange2.apk
Extract: /system/app/Galaxy4.apk
Extract: /system/app/Gallery2.apk
Extract: /system/app/HTMLViewer.apk
Extract: /system/app/HoloSpiralWallpaper.apk
Extract: /system/app/KeyChain.apk
Extract: /system/app/LatinIME.apk
Extract: /system/app/LiveWallpapers.apk
Extract: /system/app/LiveWallpapersPicker.apk
Installing Options.....
Kernel Preparation
- 10.26.1.18 CM11 Kernel
DPI Preparation
- 320 DPI
Extract: /tmp/upd-build-prop.sh
Resolution Preparation
- 2560x1600 res
Extract: /tmp/res-build-prop.sh
Boot Animations
- CROMBi-kk BLUE
Launcher
- Apex Launcher
Google Apps
- Google Core Libraries and Play Store
- Google Calendar
- Google Now and Voice Search
- Google Music
- YouTube
- Google Maps
- Google Mail
- Google Hangouts
- Google Plus
- Google TTS
- Google Ears
Misc Apps
- ES File Explorer
- AdAway installed
- Terminal Emulator
- Titanium Backup
Extract: /data/app/com.keramidas.TitaniumBackup-1.apk
- DropBox
Extract: /data/app/com.dropbox.android-1.apk
- CM11 Inverted BetterBean Blue Theme
Extract: /data/app/com.blackout1911.theme.BetterbeanThemeFree-1.apk
Installing CROMBi-kk System Tweaks.....
Extract: /tmp/crombikk-build-prop.sh
about to run program [/tmp/crombikk-build-prop.sh] with 1 args
sed: can't create temp file '/system/build.prop4U8QGE': Read-only file system
sed: can't create temp file '/system/build.propzpYgtD': Read-only file system
sed: can't create temp file '/system/build.propWIExOQ': Read-only file system
/tmp/crombikk-build-prop.sh: line 6: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 7: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 8: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 9: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 10: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 11: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 12: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 13: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 14: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 15: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 16: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 17: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 18: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 19: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 20: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 21: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 22: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 23: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 24: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 25: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 26: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 27: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 28: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 29: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 30: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 31: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 32: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 33: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 34: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 35: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 36: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 37: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 38: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 39: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 40: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 41: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 42: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 43: can't create /system/build.prop: Read-only file system
run_program: child exited with status 1
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Xposed App installed
Extract: /data/app/com.ceco.kitkat.gravitybox-1.apk
Extract: /data/app/com.e_vertise.dopa.phab7-1.apk
Installing build.prop
about to run program [/tmp/upd-build-prop.sh] with 1 args
/tmp/upd-build-prop.sh: line 2: can't create /system/build.prop: Read-only file system
/tmp/upd-build-prop.sh: line 3: can't create /system/build.prop: Read-only file system
/tmp/upd-build-prop.sh: line 4: can't create /system/build.prop: Read-only file system
run_program: child exited with status 1
about to run program [/tmp/res-build-prop.sh] with 1 args
sed: can't create temp file '/system/build.propRlJcH6': Read-only file system
sed: can't create temp file '/system/build.propbiValf': Read-only file system
sed: can't create temp file '/system/build.propwZST3P': Read-only file system
sed: can't create temp file '/system/build.propypRuEJ': Read-only file system
sed: can't create temp file '/system/build.propVIfJGb': Read-only file system
run_program: child exited with status 1
Building symlinks.....
symlink: failed to symlink /system/bin/dump.f2fs to ../bin/fsck.f2fs: Read-only file system
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
Installer Error (Status 7)
End at : Thu Jul 17 11:06:00 2014
nero0345 said:
I try again to install a ROM after format /date and /cache, but nothing.
I can cry.
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMBi-kk
ROM Version : CM11-KitKat-4.4.4-20140714-DEODEX
ROM Author : sbdags/lj50036
Device : Asus Transformer TF701T
Start at : Thu Jul 17 11:05:33 2014
Thank you for installing CROMBi-kk KitKat 4.4.4!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System.....
Extract: /tmp/fsck.ext4
Extract: /tmp/mkfs.ext4
Extract: /tmp/tune2fs.ext4
Backing up CM11 Addons.....
mount: failed to mount /dev/block/mmcblk0p1 at /system: Invalid argument
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 11
run_program: child exited with status 127
about to run program [/sbin/umount] with 2 args
about to run program [/sbin/umount] with 2 args
umount: can't umount /data: Invalid argument
run_program: child exited with status 1
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
warning: wipe_block_device: Discard failed
Tuning System.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA at /data: Invalid argument
Wiping Dalvik-cache.....
Wiping Cache.....
Installing Core System.....
Extract: /system/addon.d/50-cm.sh
Extract: /system/addon.d/blacklist
Extract: /system/app/Apollo.apk
Extract: /system/app/BasicDreams.apk
Extract: /system/app/Bluetooth.apk
Extract: /system/app/BluetoothExt.apk
Extract: /system/app/Browser.apk
Extract: /system/app/CMFileManager.apk
Extract: /system/app/CMWallpapers.apk
Extract: /system/app/Calculator.apk
Extract: /system/app/Camera2.apk
Extract: /system/app/CertInstaller.apk
Extract: /system/app/DSPManager.apk
Extract: /system/app/DeskClock.apk
Extract: /system/app/Development.apk
Extract: /system/app/DocumentsUI.apk
Extract: /system/app/DownloadProviderUi.apk
Extract: /system/app/Email.apk
Extract: /system/app/Exchange2.apk
Extract: /system/app/Galaxy4.apk
Extract: /system/app/Gallery2.apk
Extract: /system/app/HTMLViewer.apk
Extract: /system/app/HoloSpiralWallpaper.apk
Extract: /system/app/KeyChain.apk
Extract: /system/app/LatinIME.apk
Extract: /system/app/LiveWallpapers.apk
Extract: /system/app/LiveWallpapersPicker.apk
Installing Options.....
Kernel Preparation
- 10.26.1.18 CM11 Kernel
DPI Preparation
- 320 DPI
Extract: /tmp/upd-build-prop.sh
Resolution Preparation
- 2560x1600 res
Extract: /tmp/res-build-prop.sh
Boot Animations
- CROMBi-kk BLUE
Launcher
- Apex Launcher
Google Apps
- Google Core Libraries and Play Store
- Google Calendar
- Google Now and Voice Search
- Google Music
- YouTube
- Google Maps
- Google Mail
- Google Hangouts
- Google Plus
- Google TTS
- Google Ears
Misc Apps
- ES File Explorer
- AdAway installed
- Terminal Emulator
- Titanium Backup
Extract: /data/app/com.keramidas.TitaniumBackup-1.apk
- DropBox
Extract: /data/app/com.dropbox.android-1.apk
- CM11 Inverted BetterBean Blue Theme
Extract: /data/app/com.blackout1911.theme.BetterbeanThemeFree-1.apk
Installing CROMBi-kk System Tweaks.....
Extract: /tmp/crombikk-build-prop.sh
about to run program [/tmp/crombikk-build-prop.sh] with 1 args
sed: can't create temp file '/system/build.prop4U8QGE': Read-only file system
sed: can't create temp file '/system/build.propzpYgtD': Read-only file system
sed: can't create temp file '/system/build.propWIExOQ': Read-only file system
/tmp/crombikk-build-prop.sh: line 6: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 7: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 8: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 9: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 10: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 11: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 12: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 13: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 14: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 15: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 16: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 17: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 18: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 19: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 20: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 21: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 22: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 23: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 24: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 25: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 26: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 27: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 28: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 29: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 30: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 31: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 32: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 33: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 34: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 35: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 36: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 37: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 38: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 39: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 40: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 41: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 42: can't create /system/build.prop: Read-only file system
/tmp/crombikk-build-prop.sh: line 43: can't create /system/build.prop: Read-only file system
run_program: child exited with status 1
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Xposed App installed
Extract: /data/app/com.ceco.kitkat.gravitybox-1.apk
Extract: /data/app/com.e_vertise.dopa.phab7-1.apk
Installing build.prop
about to run program [/tmp/upd-build-prop.sh] with 1 args
/tmp/upd-build-prop.sh: line 2: can't create /system/build.prop: Read-only file system
/tmp/upd-build-prop.sh: line 3: can't create /system/build.prop: Read-only file system
/tmp/upd-build-prop.sh: line 4: can't create /system/build.prop: Read-only file system
run_program: child exited with status 1
about to run program [/tmp/res-build-prop.sh] with 1 args
sed: can't create temp file '/system/build.propRlJcH6': Read-only file system
sed: can't create temp file '/system/build.propbiValf': Read-only file system
sed: can't create temp file '/system/build.propwZST3P': Read-only file system
sed: can't create temp file '/system/build.propypRuEJ': Read-only file system
sed: can't create temp file '/system/build.propVIfJGb': Read-only file system
run_program: child exited with status 1
Building symlinks.....
symlink: failed to symlink /system/bin/dump.f2fs to ../bin/fsck.f2fs: Read-only file system
script aborted: symlink: some symlinks failed
symlink: some symlinks failed
Installer Error (Status 7)
End at : Thu Jul 17 11:06:00 2014
Click to expand...
Click to collapse
Download the file again or try another Rom ( cm for example)
Rikodu said:
Download the file again or try another Rom ( cm for example)
Click to expand...
Click to collapse
I have tried it with Stock Rom and the two CROMBi ROMs.
nero0345 said:
I have tried it with Stock Rom and the two CROMBi ROMs.
Click to expand...
Click to collapse
Try Cyanogenmod
It's not the rom - it's your device - for some reason it can't mount data and system - you need to fix that. Normally a job for recovery. Bt seing as you can't install a recovery that makes me even more concerned - that means other partitions are corrupted.
There is a post somewhere on how to fix from fastboot or adb - let me see if I can dig it up.
EDIT:
Ok you need to read this post very carefully and follow the instructions exactly if possible. I suspect this is the only way to get it back.
http://forum.xda-developers.com/showthread.php?t=2546941
I have the sprint n6. I am unlocked and rooted. The phone is decrypted. I have twrp for recovery. Everytime i try to flash this through twrp, it errors out. Do i have to sideload this? Ive tried looking through the board but didnt see anything. Thanks in advance for the help
What's the error for starts
What error? Is the rom downloaded fully and not corrupted?
Sent from my Nexus 6 using Tapatalk
Installing '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 1
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'
Error flashing zip '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'
Updating partition details...
Iata backup size is 1164MB, free: 21687MB.
That was the log from twrp
toast333 said:
Installing '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 1
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'
Error flashing zip '/sdcard/Download/LS-LP-v4.0-2014-12-21-liquid_shamu.zip'
Updating partition details...
Iata backup size is 1164MB, free: 21687MB.
That was the log from twrp
Click to expand...
Click to collapse
Before installing, did you wipe the system partition?
I thought I had. Lemme try that again.
There's a Q&A for LS right here http://forum.xda-developers.com/showthread.php?t=2977149
I've tried installing various custom roms (and versions) and they all seems to fail. The only successful flashes I've managed have been stock roms from this page. This is the log from when I attempted to install CM 10.2 in TWRP 2.6.6.3:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
I:Cannot find file /data/media/0/sideload.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: assert failed: getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" || getprop("ro.product.device") == "m7ul" || getprop("ro.build.product") =="m7ul"
assert failed: getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" || getprop("ro.product.device") == "m7ul" || getprop("ro.build.product") == "m7ul"
E:Error executing updater binary in zip '/data/media/0/sideload.zip'
Anyone recognise these errors?
robtherobot101 said:
I've tried installing various custom roms (and versions) and they all seems to fail. The only successful flashes I've managed have been stock roms from this page. This is the log from when I attempted to install CM 10.2 in TWRP 2.6.6.3:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Anyone recognise these errors?[/QUOTE]
CM10 is really old are you sure that's what you want ? and it may require a special version of recovery .. check the developers thread
[QUOTE]First time installing CyanogenMod 10.2 to your HTC One (GSM), or coming from another ROM:
- Read the official wiki
- Unlock your device via http://www.htcdev.com
- [COLOR="Red"]Flash the latest official ClockworkMod-Recovery via Fastboot[/COLOR]
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
[/QUOTE]
Click to expand...
Click to collapse
Here's the result of flashing CM 11:
Code:
Starting ADB sideload feature...
failed to open driver control: No such file or directory
failed to open driver control: No such file or directory
sideload_service invoked
adbd exiting after successful sideload
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
I:Cannot find file /data/media/0/sideload.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
mount: failed to mount /dev/block/mmcblk0p35 at /system: Device or resource busy
about to run program [/tmp/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 11
run_program: child exited with status 127
Creating filesystem with parameters:
Size: 1946152960
Block size: 4096
Blocks per group: 32768
Inodes per group: 7920
Inode size: 256
Journal blocks: 7423
Label:
Blocks: 475135
Block groups: 15
Reserved block group size: 119
Created filesystem with 11/118800 inodes and 15607/475135 blocks
minzip: Extracted file "/system/addon.d/50-cm.sh"
minzip: Extracted file "/system/addon.d/blacklist"
minzip: Extracted file "/system/app/Apollo.apk"
...
minzip: Extracted file "/system/xbin/strace"
minzip: Extracted file "/system/xbin/su"
minzip: Extracted file "/system/xbin/vim"
about to run program [/tmp/backuptool.sh] with 2 args
/tmp/backuptool.sh: cd: line 99: can't cd to /tmp/addon.d/
md5sum: can't open '*sh': No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
find: /tmp/addon.d/: No such file or directory
cp: can't stat '/tmp/addon.d/*': No such file or directory
script result was [/system]
On reboot TWRP reports that no OS is installed and the phone boots to a black screen
robtherobot101 said:
On reboot TWRP reports that no OS is installed and the phone boots to a black screen
Click to expand...
Click to collapse
Here is how to flash CM on the M7
just in case...
http://wiki.cyanogenmod.org/w/Install_CM_for_m7
What would cause the stock roms flash without a problem but all custom roms install improperly?
robtherobot101 said:
What would cause the stock roms flash without a problem but all custom roms install improperly?
Click to expand...
Click to collapse
Using the wrong custom recovery
TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working
robtherobot101 said:
TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working
Click to expand...
Click to collapse
Yeah, I'm not sure what's up with that. But it's for sure the reason why the other roms aren't working
When I bought the phone(supposedly brand new) the bootloader was locked but it was already S-OFF and had CID:11111111. The writing on the box is in German(I live in New Zealand) so I guess whoever I bought it off had fixed that for me...
Just in case anyone ever stumbles upon this thread in the distant future, let it be known that I managed to install this rom successfully and it's got all the useful features you'd expect from Cyanogenmod (and a few more).
robtherobot101 said:
Just in case anyone ever stumbles upon this thread in the distant future, let it be known that I managed to install this rom successfully and it's got all the useful features you'd expect from Cyanogenmod (and a few more).
Click to expand...
Click to collapse
or you just install maximus HD 50.0.0. this rom is super !
robtherobot101 said:
TWRP 2.6.3.3 and Philz Recovery 6.25.0 are the only recoveries I've managed to get working
Click to expand...
Click to collapse
This is the exact same problem I have only the 2 recoveries you mentioned work for me too, I've tried updating to newer versions of TWRP but it gets stuck on the HTC Logo with "entering recovery" at the top, I have the international version I also had to replace the screen because it smashed maybe that has something to do with it.
#fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support SINGLE-SKU
File-Based OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/attiqi_ATT'(No such file or directory)
can't open directory '/system/omc/SUP/etc/sysconfig'(No such file or directory)
can't open directory '/system/omc/SUP/etc/cid/sysconfig'(No such file or directory)
can't open directory '/system/omc/SUP/etc/cid/sysconfig'(No such file or directory)
can't open directory '/system/omc/SUP/etc/permissions'(No such file or directory)
can't open directory '/system/omc/SUP/etc/cid/permission'(No such file or directory)
can't open directory '/system/omc/SUP/etc/cid/permission'(No such file or directory)
E:[Libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/
android/compatible : No such file or directory