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
Related
Sorry about Hekp Caps. I am stuck and cant install Debian =\ Heres what happens:
Code:
# cd /sdcard/debian
cd /sdcard/debian
# sh ./installer.sh
sh ./installer.sh
# exit
exit
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Jchmod: bootdeb: Operation not permitted
chmod: debian.img: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: installer.sh: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Custom Debian Bootloader is now installed! Quick huh?
This process does NO damage to your Android underlying OS!
Courtesy of http://www.androidfanatic.com
Installer by Mark Walker (ghostwalker)
To enter the Debian Linux console just type 'bootdeb'
PS: Be sure to run /scripts/onetime.sh as root from the shell after your FIRST '
boot'.
# sh bootdeb
sh bootdeb
←[H←[JAndroid Filesytem remounted as read/write
insmod: can't read 'ext2': No such file or directory
mknod: /dev/loop2: File exists
←[H←[J
a888a
d888888b
8P YP Y88
8|o||o|88
8. .88
8 ._. Y8.
d/ 8b.
.dP . Y8b.
d8: ::88b.
d8 Y88b
:8P :888
8a. : _a88P
._/ Yaa_ : .| 88P|
\ YP | 8P \.
/ \._____.d| .|
--..__)888888P ._.|
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or direct
ory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
Custom Linux Pseudo Bootstrapper V1.0 - by Mark Walker
WEB: http://www.androidfanatic.com
EML: [email protected]
Starting init process
INIT: Debian booting.....
Running Linux Kernel
net.ipv4.ip_forward = 1
AutoMounter started
Type EXIT to end session
Make sure you do a proper EXIT for a clean kill of Debian!
chroot: can't execute '/bin/bash': No such file or directory
umount: can't forcibly umount /data/local/mnt/dev/pts: No such file or directory
umount: can't forcibly umount /data/local/mnt/proc: No such file or directory
umount: can't forcibly umount /data/local/mnt/sys: No such file or directory
umount: can't forcibly umount /data/local/mnt: Invalid argument
Filesystems have unmounted
losetup: /dev/block/loop2: No such device or address
Loopback device shutdown - success
Debian down
Coded by Mark Walker
http://www.androidfanatic.com
admin.androidfanatic.com
Reverted back to Android console
# sleep 1
sleep 1
# sleep 1
sleep 1
# bootdeb
bootdeb
←[H←[JAndroid Filesytem remounted as read/write
insmod: can't read 'ext2': No such file or directory
mknod: /dev/loop2: File exists
←[H←[J
a888a
d888888b
8P YP Y88
8|o||o|88
8. .88
8 ._. Y8.
d/ 8b.
.dP . Y8b.
d8: ::88b.
d8 Y88b
:8P :888
8a. : _a88P
._/ Yaa_ : .| 88P|
\ YP | 8P \.
/ \._____.d| .|
--..__)888888P ._.|
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or direct
ory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
Custom Linux Pseudo Bootstrapper V1.0 - by Mark Walker
WEB: http://www.androidfanatic.com
EML: [email protected]
Starting init process
INIT: Debian booting.....
Running Linux Kernel
net.ipv4.ip_forward = 1
AutoMounter started
Type EXIT to end session
Make sure you do a proper EXIT for a clean kill of Debian!
chroot: can't execute '/bin/bash': No such file or directory
umount: can't forcibly umount /data/local/mnt/dev/pts: No such file or directory
umount: can't forcibly umount /data/local/mnt/proc: No such file or directory
umount: can't forcibly umount /data/local/mnt/sys: No such file or directory
umount: can't forcibly umount /data/local/mnt: Invalid argument
Filesystems have unmounted
losetup: /dev/block/loop2: No such device or address
Loopback device shutdown - success
Debian down
Coded by Mark Walker
http://www.androidfanatic.com
admin.androidfanatic.com
Reverted back to Android console
Im on SuperBad Eclair...
SilentRazor said:
Sorry about Hekp Caps. I am stuck and cant install Debian =\ Heres what happens:
Code:
# cd /sdcard/debian
cd /sdcard/debian
# sh ./installer.sh
sh ./installer.sh
# exit
exit
←[H←[Jmkdir failed for /data/local/mnt, File exists
←[H←[Jchmod: bootdeb: Operation not permitted
chmod: debian.img: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: installer.sh: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Custom Debian Bootloader is now installed! Quick huh?
This process does NO damage to your Android underlying OS!
Courtesy of http://www.androidfanatic.com
Installer by Mark Walker (ghostwalker)
To enter the Debian Linux console just type 'bootdeb'
PS: Be sure to run /scripts/onetime.sh as root from the shell after your FIRST '
boot'.
# sh bootdeb
sh bootdeb
←[H←[JAndroid Filesytem remounted as read/write
insmod: can't read 'ext2': No such file or directory
mknod: /dev/loop2: File exists
←[H←[J
a888a
d888888b
8P YP Y88
8|o||o|88
8. .88
8 ._. Y8.
d/ 8b.
.dP . Y8b.
d8: ::88b.
d8 Y88b
:8P :888
8a. : _a88P
._/ Yaa_ : .| 88P|
\ YP | 8P \.
/ \._____.d| .|
--..__)888888P ._.|
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or direct
ory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
Custom Linux Pseudo Bootstrapper V1.0 - by Mark Walker
WEB: http://www.androidfanatic.com
EML: [email protected]
Starting init process
INIT: Debian booting.....
Running Linux Kernel
net.ipv4.ip_forward = 1
AutoMounter started
Type EXIT to end session
Make sure you do a proper EXIT for a clean kill of Debian!
chroot: can't execute '/bin/bash': No such file or directory
umount: can't forcibly umount /data/local/mnt/dev/pts: No such file or directory
umount: can't forcibly umount /data/local/mnt/proc: No such file or directory
umount: can't forcibly umount /data/local/mnt/sys: No such file or directory
umount: can't forcibly umount /data/local/mnt: Invalid argument
Filesystems have unmounted
losetup: /dev/block/loop2: No such device or address
Loopback device shutdown - success
Debian down
Coded by Mark Walker
http://www.androidfanatic.com
admin.androidfanatic.com
Reverted back to Android console
# sleep 1
sleep 1
# sleep 1
sleep 1
# bootdeb
bootdeb
←[H←[JAndroid Filesytem remounted as read/write
insmod: can't read 'ext2': No such file or directory
mknod: /dev/loop2: File exists
←[H←[J
a888a
d888888b
8P YP Y88
8|o||o|88
8. .88
8 ._. Y8.
d/ 8b.
.dP . Y8b.
d8: ::88b.
d8 Y88b
:8P :888
8a. : _a88P
._/ Yaa_ : .| 88P|
\ YP | 8P \.
/ \._____.d| .|
--..__)888888P ._.|
mount: can't setup loop device: No such file or directory
mount: mounting devpts on /data/local/mnt/dev/pts failed: No such file or direct
ory
mount: mounting proc on /data/local/mnt/proc failed: No such file or directory
mount: mounting sysfs on /data/local/mnt/sys failed: No such file or directory
Custom Linux Pseudo Bootstrapper V1.0 - by Mark Walker
WEB: http://www.androidfanatic.com
EML: [email protected]
Starting init process
INIT: Debian booting.....
Running Linux Kernel
net.ipv4.ip_forward = 1
AutoMounter started
Type EXIT to end session
Make sure you do a proper EXIT for a clean kill of Debian!
chroot: can't execute '/bin/bash': No such file or directory
umount: can't forcibly umount /data/local/mnt/dev/pts: No such file or directory
umount: can't forcibly umount /data/local/mnt/proc: No such file or directory
umount: can't forcibly umount /data/local/mnt/sys: No such file or directory
umount: can't forcibly umount /data/local/mnt: Invalid argument
Filesystems have unmounted
losetup: /dev/block/loop2: No such device or address
Loopback device shutdown - success
Debian down
Coded by Mark Walker
http://www.androidfanatic.com
admin.androidfanatic.com
Reverted back to Android console
Im on SuperBad Eclair...
Click to expand...
Click to collapse
I get the same error sadly but what are the benefits of installing debian
Umm you can install a GUI like Gnome and have apps like Firefox etc run... VNC etc
having trouble installing kineto bundle. Nexus one cm6.1.0, using intersectraven's kernel, and 5.12 radio. I have looked through several pages of this thread with not really any similar issues. here is the clockwork recovery report on why it won't install. any suggestions? phone storage is at 105 mb left and 1 gig on sd card don't understand why it says no space left on device?
Copying files...
minzip: Extracted file "/system/build.prop"
minzip: Extracted file "/system/etc/init.d/04modules"
minzip: Extracted file "/system/lib/libganril.so"
minzip: Extracted file "/system/lib/libhtc_ril.so"
minzip: Error writing 4096 bytes from zip file from 0xbec51ae4: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/lib/libkineto.so"
calling command set_perm_recursive
calling command set_perm
calling command set_perm
calling command set_perm
calling command set_perm
E:Can't chown/mod /system/lib/librilswitch.so
(No such file or directory)
E:Failure at line 7:
set_perm 0 2000 0644 SYSTEM:lib/librilswitch.so
Installation aborted.
Failure at line 3:
install_zip SDCARD:/download/kineto-n1-bundle-v1.0-signed.zip
Hi Everyone.
I am currently trying to flash a custom rom onto my Htc one, However everytime i try to do this, it is giving me multiple errors.
Things I have done
*Unlocked Bootloader
*Rooted Phone (Using Superuser) - I have also updated the su scripts via Clockworkmod
*Fastboot Disabled
*S-Off
*Stock rom Installed
I am a noob in regards to the htc one, I have tried installing Viperone v5.0.0 and also Miui v5 both have failed. The phone does not have a sd card slot so I am not sure if it has anything to do with that. I have tried flashing via twrp-2.6.3.3-m7.img below is the error log.
AROMA INSTALLER version 2.70B6
(c) 2013 by amarullz xda-developers
ROM Name : ViperOne
ROM Version : 5.0.0
ROM Author : Team Venom
Device : HTC One
Start at : Wed Feb 19 06:48:30 2014
===========================================
ViperOne 5.0.0 By Team Venom
Be patient - 1st boot may take a while
===========================================
Extracting tools
Installing Venom Tools
Extract: /sdcard/Venom/Tools/BuildPropUpdate.sh
Extract: /sdcard/Venom/Tools/ConfigureSettings.sh
Extract: /sdcard/Venom/Tools/CopyLogFile.sh
Extract: /sdcard/Venom/Tools/DeleteDataWithoutMedia.sh
Extract: /sdcard/Venom/Tools/DeleteSystemApp.sh
Extract: /sdcard/Venom/Tools/DeleteUserApp.sh
Extract: /sdcard/Venom/Tools/EnableOTA.sh
Extract: /sdcard/Venom/Tools/ExtraTweaks
Extract: /sdcard/Venom/Tools/FileSystemCheck.sh
Extract: /sdcard/Venom/Tools/SetPropSetting.sh
Extract: /sdcard/Venom/Tools/SetSetting.sh
Extract: /sdcard/Venom/Tools/UpdateDefaultXml.sh
Extract: /sdcard/Venom/Tools/VenomCheck.sh
Extract: /sdcard/Venom/Tools/VenomMod.sh
Extract: /sdcard/Venom/Tools/VenomThemeTweaksBackup.sh
Extract: /sdcard/Venom/Tools/VenomTweaksBackup.sh
Extract: /sdcard/Venom/Tools/VenomUpdate.sh
Extract: /sdcard/Venom/Tools/fsck.ext4
Extract: /sdcard/Venom/Tools/sqlite3
Extract: /sdcard/Venom/Tools/zip
Extract: /sdcard/Venom/Tools/zipalign
Extracting Build Tools
about to run program [/sbin/busybox] with 3 args
Extract: /temp/fsck.ext4
Extract: /temp/mkfs.ext4
Extract: /temp/tune2fs.ext4
Setting permissions
about to run program [/sbin/busybox] with 7 args
Setting ConfigExists to 1 in /tmp/VenomSettings.prop
Formatting Partitions
Formatting /system
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
Formatting /cache
Creating filesystem with parameters:
Size: 671084544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2559
Label:
Blocks: 163839
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/40960 inodes and 5255/163839 blocks
about to run program [/sbin/sleep] with 2 args
Extracting Files
Writing System
about to run program [/sbin/busybox] with 3 args
about to run program [/sbin/busybox] with 3 args
Extract: /system/app/BasicDreams.apk
Extract: /system/app/Bluetooth.apk
Extract: /system/app/CIMEXT9.apk
Extract: /system/app/Calculator.apk
Extract: /system/app/CalculatorWidget.apk
Extract: /system/app/Camera.apk
Extract: /system/app/CertInstaller.apk
Extract: /system/app/ChromeWithBrowser.apk
Extract: /system/app/CloudPrint.apk
Extract: /system/app/DemoFLOPackageInstaller.apk
Extract: /system/app/DeviceManagement.apk
Extract: /system/app/DocumentsUI.apk
Extract: /system/app/FMRadioService.apk
Extract: /system/app/FaceLock.apk
Extract: /system/app/FacebookEngine.apk
Extract: /system/app/Flashlight.apk
Extract: /system/app/FlickrEngine.apk
Extract: /system/app/GoogleCalendarSyncAdapter.apk
Extract: /system/app/GoogleContactsSyncAdapter.apk
Extract: /system/app/GoogleTTS.apk
Extract: /system/app/HTCBackup.apk
Extract: /system/app/HTCSetupWizard.apk
Extract: /system/app/HTC_CIR.apk
Extract: /system/app/HTC_Widget_App_and_Shortcut.apk
Extract: /system/app/HTMLViewer.apk
Extract: /system/app/HoloSpiralWallpaper.apk
Writing Data
Extract: /data/app/com.adobe.flashplayer-1.apk
Extract: /data/app/com.adobe.reader-1.apk
Extract: /data/app/com.dropbox.android-1.apk
Extract: /data/app/com.estrongs.android.pop-1.apk
Extract: /data/app/com.facebook.katana-1.apk
Extract: /data/app/com.google.android.apps.maps-1.apk
Installing Mods
about to run program [/sbin/busybox] with 7 args
Setting CustomizePropExists to 1 in /tmp/VenomSettings.prop
about to run program [/sbin/busybox] with 7 args
Setting CustomizePropExists to 1 in /tmp/VenomSettings.prop
about to run program [/sbin/busybox] with 7 args
Setting CarrierPropExists to 1 in /tmp/VenomSettings.prop
Flashing Carrier Tweaks
Generic
about to run program [/sbin/busybox] with 7 args
Setting MergeBuildProp to 0 in /tmp/VenomSettings.prop
about to run program [/sbin/busybox] with 7 args
Setting CarrierIconExists to 0 in /tmp/VenomSettings.prop
Extract: /data/system/carrier_icon.png
about to run program [/sbin/busybox] with 7 args
Setting LauncherPropExists to 1 in /tmp/VenomSettings.prop
about to run program [/sbin/busybox] with 7 args
Setting RemovePropExists to 1 in /tmp/VenomSettings.prop
Removing User Apps
Removing Flickr
about to run program [/sbin/busybox] with 4 args
rm: can't remove '/system/app/Flickr.apk': No such file or directory
rm: can't remove '/system/priv-app/Flickr.apk': No such file or directory
run_program: child exited with status 1
about to run program [/sbin/busybox] with 4 args
rm: can't remove '/system/priv-app/FlickrEngine.apk': No such file or directory
run_program: child exited with status 1
about to run program [/sbin/busybox] with 7 args
Setting ConfigExists to 1 in /tmp/VenomSettings.prop
Extracting Stock Config
Extract: /system/customize/default.prop
about to run program [/sbin/busybox] with 5 args
/sdcard/Venom/Tools/SetSetting.sh: line 2: /system/xbin/sqlite3: not found
run_program: child exited with status 127
about to run program [/sbin/busybox] with 7 args
Setting VenomMods to 0 in /tmp/VenomSettings.prop
Resetting Minfree Settings to Stock
about to run program [/sbin/busybox] with 5 args
/sdcard/Venom/Tools/SetSetting.sh: line 2: /system/xbin/sqlite3: not found
run_program: child exited with status 127
Installing Kernel
about to run program [/sbin/busybox] with 7 args
Setting KernelExists to 0 in /tmp/VenomSettings.prop
about to run program [/sbin/dd] with 3 args
13156+0 records in
13156+0 records out
6735872 bytes (6.4MB) copied, 1.028048 seconds, 6.2MB/s
Finalizing Install
Creating toolbox symlinks
symlink(): created [/system/bin]
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Feb 19 06:48:47 2014
Please help I am desparate to get this issue resolved.
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
Is this my problem ?
P.s Custom rom zip file contains busybox file "/system/xbin/busybox"
Are you sure you flashed the correct TWRP recovery for your device? There is also a version for Sprint USA.
Besides how did you flash the recovery? Via fastboot?
And are you sure that your download of Viper 5.0.0 wasnt corrupt?^^
MrCrunch said:
Are you sure you flashed the correct TWRP recovery for your device? There is also a version for Sprint USA.
Besides how did you flash the recovery? Via fastboot?
And are you sure that your download of Viper 5.0.0 wasnt corrupt?^^
Click to expand...
Click to collapse
Hi Thank you very much for your reply !!! =D
*I flashed the recovery via Fastboot.
*I have also re downloaded the rom twice incase the zip file was corrupt
*And I have also tried to flash it via Clockwork recovery
I have also installed busybox into system\bin\ and system\xbin\ just incase but one i wipe data etc in preparation for the flash, it is like it is being removed or something.
What's your model? Post a fastboot getvar all excluding IMEI and serial number
Sent from my HTC One using Tapatalk
nkk71 said:
What's your model? Post a fastboot getvar all excluding IMEI and serial number
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA*************
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
Sorry for the delay and thank you
dannybbb said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
Click to expand...
Click to collapse
download TWRP:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure MD5 is correct, then flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery and install the ROM
nkk71 said:
download TWRP:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
make sure MD5 is correct, then flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery and install the ROM
Click to expand...
Click to collapse
Ok I have redownloaded recovery file and also the custom rom I have also checked md5's match
Recovery (openrecovery-twrp-2.6.3.4-m7ul.img)
Custom Rom (ViperOne 5.0.0)
Images attached
I have followed these steps
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
entered recovery
select install
Viperone 5.0.0
Then I selected Full wipe and everything is working fine now
Thank you so much for all your support it is greatly appreciated =D !!!!
Do you think it was because i was wiping the data manually through twrp, instead of doing the wipe through the install wizard?
dannybbb said:
Ok I have redownloaded recovery file and also the custom rom I have also checked md5's match
Recovery (recovery-clockwork-touch-6.0.4.6-m7.img)
Custom Rom (ViperOne 5.0.0)
Images attached
I have followed these steps
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
entered recovery
select install
Viperone 5.0.0
Then I selected Full wipe and everything is working fine now
Thank you so much for all your support it is greatly appreciated =D !!!!
Do you think it was because i was wiping the data manually through twrp, instead of doing the wipe through the install wizard?
Click to expand...
Click to collapse
I think it's because of an outdated/incompatible recovery version; 4.4 ROMs are best installed with TWRP 2.6.3.3 or .4 at the moment, something about selinux support.
PS: you can always hit the Thanks button if i've helped.
Can not update Custom Rom
Maybe someone can help me here. I was trying to update my custom ROM with a zip file and got this error.
installing from zip file
---creating toolbox symlinks
---creating additional symlinks
Installing busybox
set_perm: some changes failed.
Here is the log file.
AROMA INSTALLER version 2.70B6
(c) 2013 by amarullz xda-developers
ROM Name : RENOVATE
ROM Version : SVN build
ROM Author : mwilky
Device : HTC One (M7)
Start at : Wed Feb 19 21:36:31 2014
Installing from zip file
Extract: /tmp/FullWipe.sh
Extract: /tmp/fsck.ext4
Extract: /tmp/mkfs.ext4
Extract: /tmp/preflash.sh
Extract: /tmp/tune2fs.ext4
about to run program [/tmp/preflash.sh] with 1 args
kernel.prop found
Extract: /sdcard/vrtheme/cleanup.sh
Extract: /sdcard/vrtheme/installtheme.sh
Extract: /sdcard/vrtheme/zip
Extract: /sdcard/vrtheme/zipalign
about to run program [/sdcard/vrtheme/installtheme.sh] with 1 args
Processing /system/app/
/sdcard/vrtheme/installtheme.sh: cd: line 11: can't cd to /sdcard/vrtheme/system/app/
Processing boot
cp: can't stat '/system/app/boot': No such file or directory
cp: can't stat '/system/app/boot': No such file or directory
Processing cache
cp: can't stat '/system/app/cache': No such file or directory
cp: can't stat '/system/app/cache': No such file or directory
Processing charger
cp: can't stat '/system/app/charger': No such file or directory
cp: can't stat '/system/app/charger': No such file or directory
Processing data
cp: can't stat '/system/app/data': No such file or directory
cp: can't stat '/system/app/data': No such file or directory
Processing default.prop
cp: can't stat '/system/app/default.prop': No such file or directory
cp: can't stat '/system/app/default.prop': No such file or directory
Processing dev
cp: can't stat '/system/app/dev': No such file or directory
cp: can't stat '/system/app/dev': No such file or directory
Processing etc
cp: can't stat '/system/app/etc': No such file or directory
cp: can't stat '/system/app/etc': No such file or directory
Processing file_contexts
cp: can't stat '/system/app/file_contexts': No such file or directory
cp: can't stat '/system/app/file_contexts': No such file or directory
Processing fstab.goldfish
cp: can't stat '/system/app/fstab.goldfish': No such file or directory
cp: can't stat '/system/app/fstab.goldfish': No such file or directory
Processing fstab.qcom
cp: can't stat '/system/app/fstab.qcom': No such file or directory
cp: can't stat '/system/app/fstab.qcom': No such file or directory
Processing init
cp: can't stat '/system/app/init': No such file or directory
cp: can't stat '/system/app/init': No such file or directory
Processing init.qcom.firmware_links.sh
cp: can't stat '/system/app/init.qcom.firmware_links.sh': No such file or directory
cp: can't stat '/system/app/init.qcom.firmware_links.sh': No such file or directory
Processing init.rc
cp: can't stat '/system/app/init.rc': No such file or directory
cp: can't stat '/system/app/init.rc': No such file or directory
Processing license
cp: can't stat '/system/app/license': No such file or directory
cp: can't stat '/system/app/license': No such file or directory
Processing lpm.rc
cp: can't stat '/system/app/lpm.rc': No such file or directory
cp: can't stat '/system/app/lpm.rc': No such file or directory
Processing proc
cp: can't stat '/system/app/proc': No such file or directory
cp: can't stat '/system/app/proc': No such file or directory
Processing property_contexts
cp: can't stat '/system/app/property_contexts': No such file or directory
cp: can't stat '/system/app/property_contexts': No such file or directory
Processing recovery
cp: can't stat '/system/app/recovery': No such file or directory
cp: can't stat '/system/app/recovery': No such file or directory
Processing remount.qcom
cp: can't stat '/system/app/remount.qcom': No such file or directory
cp: can't stat '/system/app/remount.qcom': No such file or directory
Processing res
cp: can't stat '/system/app/res': No such file or directory
cp: can't stat '/system/app/res': No such file or directory
Processing root
cp: can't stat '/system/app/root': No such file or directory
cp: can't stat '/system/app/root': No such file or directory
Processing sbin
cp: can't stat '/system/app/sbin': No such file or directory
cp: can't stat '/system/app/sbin': No such file or directory
Processing sdcard
cp: can't stat '/system/app/sdcard': No such file or directory
cp: can't stat '/system/app/sdcard': No such file or directory
Processing seapp_contexts
cp: can't stat '/system/app/seapp_contexts': No such file or directory
cp: can't stat '/system/app/seapp_contexts': No such file or directory
Processing sepolicy
cp: can't stat '/system/app/sepolicy': No such file or directory
cp: can't stat '/system/app/sepolicy': No such file or directory
Processing supersu
cp: can't stat '/system/app/supersu': No such file or directory
cp: can't stat '/system/app/supersu': No such file or directory
Processing sys
cp: can't stat '/system/app/sys': No such file or directory
cp: can't stat '/system/app/sys': No such file or directory
Processing system
cp: can't stat '/system/app/system': No such file or directory
cp: can't stat '/system/app/system': No such file or directory
Processing tmp
cp: can't stat '/system/app/tmp': No such file or directory
cp: can't stat '/system/app/tmp': No such file or directory
Processing ueventd.goldfish.rc
cp: can't stat '/system/app/ueventd.goldfish.rc': No such file or directory
cp: can't stat '/system/app/ueventd.goldfish.rc': No such file or directory
Processing ueventd.qcom.rc
cp: can't stat '/system/app/ueventd.qcom.rc': No such file or directory
cp: can't stat '/system/app/ueventd.qcom.rc': No such file or directory
Processing ueventd.rc
cp: can't stat '/system/app/ueventd.rc': No such file or directory
cp: can't stat '/system/app/ueventd.rc': No such file or directory
Processing usb-otg
cp: can't stat '/system/app/usb-otg': No such file or directory
cp: can't stat '/system/app/usb-otg': No such file or directory
Backups done for system apps
Patched system app files
Zipaligning aligned
Unable to open 'aligned' as zip archive
cp: can't stat '*': No such file or directory
chmod: /system/app/*: No such file or directory
VillainTheme is done
about to run program [/sdcard/vrtheme/cleanup.sh] with 1 args
Cleanup complete
-- Creating toolbox symlinks
-- Creating additional symlinks
symlink(): created [/system/fonts]
symlink(): created [/system/lib]
symlink(): created [/system/lib/modules]
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Feb 19 21:36:31 2014
What recovery do you have?
sent from my mobile device
SaHiLzZ said:
What recovery do you have?
sent from my mobile device
Click to expand...
Click to collapse
Twerp 2.6.3.3
worldfamous said:
Maybe someone can help me here. I was trying to update my custom ROM with a zip file and got this error.
installing from zip file
---creating toolbox symlinks
---creating additional symlinks
Installing busybox
set_perm: some changes failed.
<snip>
Click to expand...
Click to collapse
Looks like the zip file you downloaded has errors in the install script.
It appears to be a Renovate ROM svn update. Have you tried posting this issue in the Renovate thread? The dev and folks there would probably be better suited to help you than in the general Q&A section. Just a thought...
trjlive said:
Looks like the zip file you downloaded has errors in the install script.
It appears to be a Renovate ROM svn update. Have you tried posting this issue in the Renovate thread? The dev and folks there would probably be better suited to help you than in the general Q&A section. Just a thought...
Click to expand...
Click to collapse
Yes i have posted it but was seeing here also about it.
failed status 7
Hi I'm new with flashing my HTC one developer edition. I just tried to install venom 5.8 however I got error status 7
Extract: /system/xbin/rlog.sh
Extract: /system/xbin/sqlite3
Extract: /system/xbin/su
Extract: /system/xbin/sysro
Extract: /system/xbin/sysrw
Extract: /system/xbin/tcpdump
Extract: /system/xbin/unrar
Extract: /system/xbin/venom_functions.sh
Extract: /system/xbin/vim
Extract: /system/xbin/zip
Writing Data
Extract: /data/app/MIUI-N7/127--t.apk
Extract: /data/app/MIUI-N7/8--t.apk
Extract: /data/app/com.adobe.flashplayer-1.apk
Extract: /data/app/com.adobe.reader-1.apk
Extract: /data/app/com.android.chrome-1.apk
Extract: /data/app/com.dropbox.android-1.apk
Extract: /data/app/com.estrongs.android.pop-1.apk
Extract: /data/app/com.facebook.katana-1.apk
Extract: /data/app/com.google.android.apps.maps-1.apk
Extract: /data/app/com.google.android.apps.plus-1.apk
Extract: /data/app/com.google.android.gm-1.apk
Extract: /data/app/com.google.android.marvin.talkback-1.apk
Extract: /data/app/com.google.android.street-1.apk
Extract: /data/app/com.google.android.talk-1.apk
Extract: /data/app/com.google.android.youtube-1.apk
Extract: /data/app/com.htc.backup-1.apk
Extract: /data/app/com.infraware.docmaster-1.apk
Extract: /data/app/com.keramidas.TitaniumBackup-1.apk
Extract: /data/app/com.melodis.midomiMusicIdentifier.freemium-1.apk
Extract: /data/app/com.twitter.android-1.apk
Extract: /data/app/com.zoodles.kidmode-1.apk
Extract: /data/app/mobi.mgeek.TunnyBrowser-1.apk
Extract: /data/app/org.adaway-1.apk
Extract: /data/app/tunein.player-1.apk
Installing Mods
about to run program [/sbin/busybox] with 7 args
Setting CustomizePropExists to 1 in /tmp/VenomSettings.prop
Installing Exchange Mod
Extract: /system/priv-app/Mail.apk
Installing Viper Boot
Extract: /system/customize/resource/bootanimation.zip
Extract: /system/customize/resource/downanimation.zip
about to run program [/sbin/busybox] with 7 args
Setting CustomizePropExists to 1 in /tmp/VenomSettings.prop
Removing HTC Sense
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/Htc3DRichNotesWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/app/HtcAutoRotateWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/app/HtcBackgroundDataWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/HtcCalendarWidgets.apk
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/HtcContactWidgets.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/HtcDataRoamingWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/HtcDataStripWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/HtcFMRadioWidget.apk
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/HtcMailWidgets.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/HtcMsgWidgets.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/HtcPhotoWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/app/HtcPowerStripWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/app/HtcProfilesWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/app/HtcScreenBrightnessWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/app/HtcScreenTimeoutWidget.apk
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
Deleting /system/app/HtcSyncWidget.apk
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/MyTaskWidget.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/priv-app/Prism.apk
about to run program [/sbin/busybox] with 4 args
Deleting /system/app/StockWidget.apk
about to run program [/sbin/busybox] with 4 args
about to run program [/sbin/busybox] with 7 args
Setting CarrierPropExists to 1 in /tmp/VenomSettings.prop
Flashing Carrier Tweaks
Generic
about to run program [/sbin/busybox] with 7 args
Setting MergeBuildProp to 0 in /tmp/VenomSettings.prop
about to run program [/sbin/busybox] with 7 args
Setting CarrierIconExists to 0 in /tmp/VenomSettings.prop
Extract: /data/system/carrier_icon.png
about to run program [/sbin/busybox] with 7 args
Setting LauncherPropExists to 1 in /tmp/VenomSettings.prop
Adding Nova Launcher
Extract: /data/app/com.teslacoilsw.launcher-1.apk
about to run program [/sbin/busybox] with 7 args
Setting RemoveAppsPropExists to 1 in /tmp/VenomSettings.prop
Removing User Apps
Removing Google Apps
Removing Venom Apps
Removing System Apps
about to run program [/sbin/busybox] with 7 args
Setting RemoveMediaPropExists to 1 in /tmp/VenomSettings.prop
Removing Media
about to run program [/sbin/busybox] with 7 args
Setting KeyboardsPropExists to 1 in /tmp/VenomSettings.prop
Installing Keyboards
about to run program [/sbin/busybox] with 7 args
Setting ConfigExists to 1 in /tmp/VenomSettings.prop
Extracting Stock Config
Extract: /system/customize/default.prop
about to run program [/sbin/busybox] with 5 args
/sdcard/Venom/Tools/SetSetting.sh: line 2: /system/xbin/sqlite3: Permission denied
run_program: child exited with status 126
about to run program [/sbin/busybox] with 7 args
Setting VenomMods to 0 in /tmp/VenomSettings.prop
Installing Kernel
about to run program [/sbin/busybox] with 7 args
Setting KernelExists to 0 in /tmp/VenomSettings.prop
about to run program [/sbin/dd] with 3 args
13156+0 records in
13156+0 records out
6735872 bytes (6.4MB) copied, 2.168442 seconds, 3.0MB/s
Kernel Flashed.
Finalizing Install
Creating toolbox symlinks
Installing busybox
about to run program [/system/xbin/busybox] with 4 args
Creating additional symlinks
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Installer Error (Status 7)
End at : Mon Mar 31 00:57:27 2014
>>>>>
I AM TRYING TO UPDATE MY TWRP HOWEVER I DON'T HAVE ANY OS INSTALLED ON A PHONE. I CAN'T USE GOO OR ANY APPS, I CAN ONLY GO TO RECOVERY, HOW CAN I UPDATE MY TWRP TO 2.7.0 USING TWRP RECOVERY??
hec2rhym3 said:
Hi I'm new with flashing my HTC one developer edition. I just tried to install venom 5.8 however I got error status 7
>>>>>
I AM TRYING TO UPDATE MY TWRP HOWEVER I DON'T HAVE ANY OS INSTALLED ON A PHONE. I CAN'T USE GOO OR ANY APPS, I CAN ONLY GO TO RECOVERY, HOW CAN I UPDATE MY TWRP TO 2.7.0 USING TWRP RECOVERY??
Click to expand...
Click to collapse
no need to scream mate, you update recovery using fastboot in bootloader:
if your device is an m7_u or m7_ul: get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then install the rom
Error status 7
>>
Hello, Not sure on how to do it.
I tried to go to fastboot
open recovery ( when i tried to open 2.6.3.4-m7.img saved on my USB otg using twrp 2.5.0.0 it only shows the file do i need to move it or rename it?)
Sorry If I'm not really familiar on what to do.
Please help me.
Error status 7
By the way I followed the instruction on how to flash the recovery. But i can't connect my phone to computer it doesn't recognized it. It didn't go to Fastboot USB. I tried to download ADB drivers nothing seems to work. My phone is S-ON and I believe that my USB debugging is enabled I don't have a way of opening the settings of the phone since there is no OS installed. I really don't know what to do. My TWRP. is 2.5.0.0.. hope to get some help from you guys.
I do not have an os too install a rom to, i have tried many different roms, installing through adb sideload as my phone got completely wiped, all with same errors "cannot mount ..."
hec2rhym3 said:
By the way I followed the instruction on how to flash the recovery. But i can't connect my phone to computer it doesn't recognized it. It didn't go to Fastboot USB. I tried to download ADB drivers nothing seems to work. My phone is S-ON and I believe that my USB debugging is enabled I don't have a way of opening the settings of the phone since there is no OS installed. I really don't know what to do. My TWRP. is 2.5.0.0.. hope to get some help from you guys.
Click to expand...
Click to collapse
get adb+fastboot files from: http://www.androidfilehost.com/?fid=23329332407580571
put them in a simple folder, something like C:\ADB
update drivers from: http://forum.xda-developers.com/showthread.php?t=2089508
Check Windows Device Manager if you get "Android USB Devices -> My HTC"
you can look at FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082
then update your recovery to 2.6.3.3 as mentioned above
I have an HTC One M8, and I installed Cyanogenmod 12.1 (I followed their guide and did HTCdev Unlock). For a little while, LTE was working fine with my phone, but then about a couple of weeks ago, my LTE connection stopped working, and it hasn't worked since. So ultimately that's the problem I'm looking to solve.
I had backed up my HTC factory ROM and restored that to see if LTE would work there. That's when I found that it wants me to do an update, but the update reboots me into TWRP and doesn't work. My thought is that to solve this, I will need to apply the update somehow, and if that's the case, then I could use some help figuring out how to do that. (I'm trying to run "Update Profile".)
If you have other ideas of what I can do to fix LTE, then I'm open to hearing them as well.
Thanks!
You need to install stock recovery to enable the update to install.
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
komi_9 said:
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
Click to expand...
Click to collapse
Yup sounds correct except being you are on 2.16 there will be a few updates you will need to do to get current.
I went through the process, and each step went fine (you were right about having to update a few times), but LTE is still not working in CM when I switched back over. It is working on the Stock ROM side of things; that's how I did my OTA update. (At least it says LTE in the status bar, so I assume that's what it's using, as opposed to just defaulting to LTE but switching to 3G when LTE is not present.)
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Thanks for the help again!
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
Click to expand...
Click to collapse
I don't use CM so can't answer but yeah your best bet would be to ask in their forum.
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Click to expand...
Click to collapse
If you took all the update to make you current you should have the latest stock recovery. You can always pull the stock recovery from the latest Full Firmware zip.
HK = Harmon Kardon Edition
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
komi_9 said:
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
Click to expand...
Click to collapse
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Sloth said:
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Click to expand...
Click to collapse
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
komi_9 said:
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
Click to expand...
Click to collapse
Have you updated your twrp recently?
I have 2.8.7.0 downloaded from here: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
komi_9 said:
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
Click to expand...
Click to collapse
Yes that might be the problem. A full wipe shouldn't wipe anything important.
If you have a backup and you need to use it you will be back to the ROM you made the backup of.
Sent from a Glade Plugin.
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
komi_9 said:
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
Click to expand...
Click to collapse
V7.4.2 is not the latest version...try the latest and see if it makes a difference. Usually status 7 error means the updater script is out of date (if I remember correctly).
When I do a full wipe I choose Advance Wipe then check the boxes next to cache/dal cache/data/system. From my experience wiping in twrp and then wiping again in Aroma usually causes problems. I prefer the twrp method myself.
I also put anything I'm going to flash on the EXT sdcard.
The 7.4.3 version is only available as a patch to 7.4.2 as far as I can tell. The full download is only available in 7.4.2. Or at least that's all I see.
Anyway, the point is moot now since I seem to have gotten LTE working. I went into APN settings and the option CDMA 0 was selected. Any of the other options pop me over to the Sprint LTE Internet option, but that one will just sit there and not work. I'm not quite sure how I got stuck on that APN. But oh well, since it's working now.
I really appreciate all the help! One day I might embark on trying out different ROMs again, but for now I'm happy that CM is working out OK.
Cool glad you got it sorted.
I have a `system.img.ext4.lz4` file that is compatible with my Samsung S10 5G(Qualcomm) device. I have extracted `system.img.ext4` file from the `system.img.ext4.lz4` using `unlz4 system.img.ext4.lz4` command.
I want to play with its content. So I have decided it in two steps:
1. Flash `system.img.ext4` without modification:
- Using `tar -cvf AP.tar system.img.ext4` command, I have created a AP.tar file.
- Flashed `AP.tar` file using Odin3 v3.13.
- It flashed successfully.
2. Flash `system.img.ext4` with modification:
a) Modifying
- With `simg2img system.img.ext4 system.img`, you will get a raw image file named `system.img`
- With `mkdir system`, create directory to mount system.img
- With `sudo mount -t ext4 -o loop system.img system/` you will get all files of `system.img` in `system` folder
- With `ls -l system/init.rc` note permissions: 750
- With `sudo chmod 777 system/init.rc` give write permissions
- With `sudo echo "#MODIFICATION " >> system/init.rc` done some modification in `init.rc`
- With `sudo chmod 750 init.rc` reset `init.rc` to the noted permissions
b) Calculate system sector size
- With `tune2fs -l system.img | grep "Block size\|Block count"` you will get block size and count
- With `echo $((1553064 * 4096))` multiply both results. I got 6361350144
c) Packing
- With `sudo make_ext4fs -s -l 6361350144 -a system system_new.img sys/` you will get `system_new.img` “Android Sparse Image” that has all changes
- With `sudo umount system` unmount the system directory
- With `rm -fr system` delete the system directory
d) Tar Compression
- With `rm system.img.ext4` remove original system.img.ext4, Don’t worry you should have a backup of it in lz4 file
- With `mv system_new.img system.img.ext4` rename system_new.img to system.img.ext4 for flashing with Odin3 v3.13
- With `tar -cvf AP.tar system.img.ext4` you will get AP.tar that you can flash with Odin3 v3.13.
- It failed to flash with FAIL! (Auth) error.
Please suggest how can I resolve this issue?
I will be very thankful to you for any little to big suggestion.:angel:
Vats12 said:
I have a `system.img.ext4.lz4` file that is compatible with my Samsung S10 5G(Qualcomm) device. I have extracted `system.img.ext4` file from the `system.img.ext4.lz4` using `unlz4 system.img.ext4.lz4` command.
I want to play with its content. So I have decided it in two steps:
1. Flash `system.img.ext4` without modification:
- Using `tar -cvf AP.tar system.img.ext4` command, I have created a AP.tar file.
- Flashed `AP.tar` file using Odin3 v3.13.
- It flashed successfully.
2. Flash `system.img.ext4` with modification:
a) Modifying
- With `simg2img system.img.ext4 system.img`, you will get a raw image file named `system.img`
- With `mkdir system`, create directory to mount system.img
- With `sudo mount -t ext4 -o loop system.img system/` you will get all files of `system.img` in `system` folder
- With `ls -l system/init.rc` note permissions: 750
- With `sudo chmod 777 system/init.rc` give write permissions
- With `sudo echo "#MODIFICATION " >> system/init.rc` done some modification in `init.rc`
- With `sudo chmod 750 init.rc` reset `init.rc` to the noted permissions
b) Calculate system sector size
- With `tune2fs -l system.img | grep "Block size\|Block count"` you will get block size and count
- With `echo $((1553064 * 4096))` multiply both results. I got 6361350144
c) Packing
- With `sudo make_ext4fs -s -l 6361350144 -a system system_new.img sys/` you will get `system_new.img` “Android Sparse Image” that has all changes
- With `sudo umount system` unmount the system directory
- With `rm -fr system` delete the system directory
d) Tar Compression
- With `rm system.img.ext4` remove original system.img.ext4, Don’t worry you should have a backup of it in lz4 file
- With `mv system_new.img system.img.ext4` rename system_new.img to system.img.ext4 for flashing with Odin3 v3.13
- With `tar -cvf AP.tar system.img.ext4` you will get AP.tar that you can flash with Odin3 v3.13.
- It failed to flash with FAIL! (Auth) error.
Please suggest how can I resolve this issue?
I will be very thankful to you for any little to big suggestion.:angel:
Click to expand...
Click to collapse
you need to unlock your bl and/or flash in twrp.
if you are trying this on a locked bl it will not work since when u modify the system partition you break the sig and hashes etc etc
elliwigy said:
you need to unlock your bl and/or flash in twrp.
if you are trying this on a locked bl it will not work since when u modify the system partition you break the sig and hashes etc etc
Click to expand...
Click to collapse
The bootloader is already unlocked and after that I am getting this issue. Twrp is not available for this model of Samsung S10.
hi, what next about this problem?
i have same issue
Vats12 said:
The bootloader is already unlocked and after that I am getting this issue. Twrp is not available for this model of Samsung S10.
Click to expand...
Click to collapse