Hi guys i been running 4th bar ics S-on for a few months now and today i decided to change roms.
im used to running DS full wipe scripts in between flashing anything new, but for some reason this time i get error and aborting messages same with flashing kernels and radios.
I relocked bootloader and followed unlocking procedure all over again, tried TWRP and 4ext recoveries with no luck, re partitioned my sd card and still no luck.
Anyhow this is the error i keep getting hopefully someone might be able to interpret it for me. thanks in advance
Mounting '/emmc'
I:Mounting /sdcard using: 'mount /emmc /sdcard'
Error flashing zip '/sdcard/darkside-wipe-cache-only.zip'
I:Set page: 'flash_done'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
I:Mounting '/emmc'
I:Mounting /sdcard using: 'mount /emmc /sdcard'
-- Verify md5 for /sdcard/darkside-wipe-cache-only.zip
-- No md5 file found, ignoring
-- Install /sdcard/darkside-wipe-cache-only.zip ...
I:Mounting '/emmc'
I:Mounting /sdcard using: 'mount /emmc /sdcard'
I:Unmounting /sdcard (dual storage path code)
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
Installing update...
[*] Running DARKSIDE.SUPER.WIPE on /cache only...
> Erasing & Formatting CACHE Partition
about to run program [/sbin/umount] with 2 args
umount: can't umount /cache: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/erase_image] with 2 args
Creating filesystem with parameters:
Size: 4194304
Block size: 4096
Blocks per group: 32768
Inodes per group: 256
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 1024
Block groups: 1
Reserved block group size: 7
error: do_inode_allocate_extents: Failed to allocate 1025 blocks
E:Error in /tmp/sideload/package.zip
(Status 1)
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
E:Unable to mount /data
Try ruu and reflash 4ext
Sent from my HTC_Amaze_4G using xda premium
dadogintown said:
Hi guys i been running 4th bar ics S-on for a few months now and today i decided to change roms.
im used to running DS full wipe scripts in between flashing anything new, but for some reason this time i get error and aborting messages same with flashing kernels and radios.
I relocked bootloader and followed unlocking procedure all over again, tried TWRP and 4ext recoveries with no luck, re partitioned my sd card and still no luck.
Anyhow this is the error i keep getting hopefully someone might be able to interpret it for me. thanks in advance
Mounting '/emmc'
I:Mounting /sdcard using: 'mount /emmc /sdcard'
Error flashing zip '/sdcard/darkside-wipe-cache-only.zip'
I:Set page: 'flash_done'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
I:Mounting '/emmc'
I:Mounting /sdcard using: 'mount /emmc /sdcard'
-- Verify md5 for /sdcard/darkside-wipe-cache-only.zip
-- No md5 file found, ignoring
-- Install /sdcard/darkside-wipe-cache-only.zip ...
I:Mounting '/emmc'
I:Mounting /sdcard using: 'mount /emmc /sdcard'
I:Unmounting /sdcard (dual storage path code)
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
Installing update...
[*] Running DARKSIDE.SUPER.WIPE on /cache only...
> Erasing & Formatting CACHE Partition
about to run program [/sbin/umount] with 2 args
umount: can't umount /cache: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/erase_image] with 2 args
Creating filesystem with parameters:
Size: 4194304
Block size: 4096
Blocks per group: 32768
Inodes per group: 256
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 1024
Block groups: 1
Reserved block group size: 7
error: do_inode_allocate_extents: Failed to allocate 1025 blocks
E:Error in /tmp/sideload/package.zip
(Status 1)
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
E:Unable to mount /data
Click to expand...
Click to collapse
If I remember correctly, DarkSide wipe is only designed for Samsung Galaxy SII. It probably fails due to different partition structures. The tool may be attempting to wipe the wrong partitions, which leads to errors. There is an option in 4Ext recovery that allows you to do a full wipe, and it is recommended to use that option compared to using superwipe scripts, as such scripts are usually only designed for one device.
Related
I can't make backups! I have plenty of space on my sd card. The problem is Data will not back up. System and I think the Boot or whatever the other one is does but when I try to back up Data it immediately says error and backs up 0 bytes or close to it.
Ive tried reinstalling several times and have tried both the latest version and the last version and no dice. Please help. I'm running Sense 5 r141 and have backed it up in the past with no problems.
Sent from my EVO using xda app-developers app
Try this TWRP I built from source with several fixes, including the one that should fix your problem: http://tinyurl.com/TWRP-Recovery-2-6-0-1
Captain_Throwback said:
Try this TWRP I built from source with several fixes, including the one that should fix your problem: http://tinyurl.com/TWRP-Recovery-2-6-0-1
Click to expand...
Click to collapse
Still won't work. = ( As soon as it tries to backup "Data" it fails. I wonder if there is something on my phone blocking the recovery from accessing Data or something?
Do you think Avast anti theft or mobile security could be the problem? I tried to deactivate it and I tried uninstalling and still can't backup Data in recovery 2.6.0.1.
Sent from my EVO using xda app-developers app
Starzboy77 said:
Do you think Avast anti theft or mobile security could be the problem? I tried to deactivate it and I tried uninstalling and still can't backup Data in recovery 2.6.0.1.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Is compression enabled? What error does the recovery log give you?
Captain_Throwback said:
Is compression enabled? What error does the recovery log give you?
Click to expand...
Click to collapse
Yes, compression is enabled. Looks to be error 255. I can't find what that means?
Log:
persist.rild.nitz_long_ons_2=""
persist.rild.nitz_long_ons_3=""
persist.rild.nitz_short_ons_0=""
persist.rild.nitz_short_ons_1=""
persist.rild.nitz_short_ons_2=""
persist.rild.nitz_short_ons_3=""
debug.nfc.fw_download=true
debug.nfc.fw_boot_download=false
debug.nfc.se=true
ro.nfc.port=I2C
persist.timed.enable=true
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130816-UNOFFICIAL-jewel
ro.modversion=10.1-20130816-UNOFFICIAL-jewel
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
com.qc.hardware=true
debug.composition.type=dyn
debug.egl.hw=1
debug.mdpcomp.logs=0
debug.sf.hw=1
dev.pm.dyn_samplingrate=1
lpa.decode=true
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
persist.audio.speaker.location=high
persist.hwc.mdpcomp.enable=true
persist.thermal.monitor=true
ro.opengles.version=131072
ro.qc.sdk.audio.fluencetype=fluence
wifi.interface=wlan0
persist.gps.qmienabled=true
ro.baseband.arch=msm
ro.product.wireless=WCN3660
ro.qualcomm.bt.hci_transport=smd
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.choice_fn=stopped
init.svc.dmesg=stopped
init.svc.adbd=restarting
service.adb.root=1
init.svc.recovery=running
Running boot script...
Finished running boot script.
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/sdcard/TWRP/.twrps'.
I:Backup folder set to '/sdcard/TWRP/BACKUPS/HT25AS401570'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'backup'
I:Set page: 'backup_run'
Updating partition details...
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Backup Name is: '2013-08-24--18-55-15'
I:Full_Backup_Path is: '/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-15/'
I:Calculating backup details...
* Total number of partitions to back up: 1
* Total size of all data: 1511MB
* Available space: 2804MB
[BACKUP STARTED]
* Backup Folder: /sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-15/
I:Estimated Total time: 2 Estimated remaining time: 2
Backing up Data...
I:Using compression...
I:tar_append_tree '/data/misc' as '/misc'
==> tar_append_tree(0x44c90190, "/data/misc", "/misc")
==> tar_append_tree(0x44c90190, "/data/misc/dhcp", "/misc/dhcp")
==> tar_append_tree(0x44c90190, "/data/misc/keystore", "/misc/keystore")
==> tar_append_tree(0x44c90190, "/data/misc/location", "/misc/location")
==> tar_append_tree(0x44c90190, "/data/misc/location/mq", "/misc/location/mq")
==> tar_append_tree(0x44c90190, "/data/misc/keychain", "/misc/keychain")
==> tar_append_tree(0x44c90190, "/data/misc/bluetooth", "/misc/bluetooth")
==> tar_append_tree(0x44c90190, "/data/misc/vpn", "/misc/vpn")
==> tar_append_tree(0x44c90190, "/data/misc/wifi", "/misc/wifi")
==> tar_append_tree(0x44c90190, "/data/misc/wifi/hostapd", "/misc/wifi/hostapd")
==> tar_append_tree(0x44c90190, "/data/misc/wifi/wpa_supplicant", "/misc/wifi/wpa_supplicant")
==> tar_append_tree(0x44c90190, "/data/misc/wifi/sockets", "/misc/wifi/sockets")
E:Error appending '/data/misc' to tar archive '/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-15//data.ext4.win'
I:createTarFork() process ended with ERROR=255
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'backup'
I:Set page: 'backup_run'
Updating partition details...
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Backup Name is: '2013-08-24--18-55-23'
I:Full_Backup_Path is: '/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-23/'
I:Calculating backup details...
* Total number of partitions to back up: 3
* Total size of all data: 2389MB
* Available space: 2804MB
[BACKUP STARTED]
* Backup Folder: /sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-23/
I:Estimated Total time: 5 Estimated remaining time: 5
Backing up Boot...
I:Backup command: 'dd if=/dev/block/mmcblk0p21 of='/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-23//boot.emmc.win' bs=16777216c count=1'
I:1+0 records in
1+0 records out
I:16777216 bytes (16.0MB) copied, I:0.488478 seconds, 32.8MB/s
Iartition Backup time: 0
* Generating md5...
* MD5 Created.
I:Estimated Total time: 5 Estimated remaining time: 3
Backing up Data...
I:Using compression...
I:tar_append_tree '/data/misc' as '/misc'
==> tar_append_tree(0x44c914e0, "/data/misc", "/misc")
==> tar_append_tree(0x44c914e0, "/data/misc/dhcp", "/misc/dhcp")
==> tar_append_tree(0x44c914e0, "/data/misc/keystore", "/misc/keystore")
==> tar_append_tree(0x44c914e0, "/data/misc/location", "/misc/location")
==> tar_append_tree(0x44c914e0, "/data/misc/location/mq", "/misc/location/mq")
==> tar_append_tree(0x44c914e0, "/data/misc/keychain", "/misc/keychain")
==> tar_append_tree(0x44c914e0, "/data/misc/bluetooth", "/misc/bluetooth")
==> tar_append_tree(0x44c914e0, "/data/misc/vpn", "/misc/vpn")
==> tar_append_tree(0x44c914e0, "/data/misc/wifi", "/misc/wifi")
==> tar_append_tree(0x44c914e0, "/data/misc/wifi/hostapd", "/misc/wifi/hostapd")
==> tar_append_tree(0x44c914e0, "/data/misc/wifi/wpa_supplicant", "/misc/wifi/wpa_supplicant")
==> tar_append_tree(0x44c914e0, "/data/misc/wifi/sockets", "/misc/wifi/sockets")
E:Error appending '/data/misc' to tar archive '/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-23//data.ext4.win'
I:createTarFork() process ended with ERROR=255
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'backup'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log
disable compression
Tried that, no effect. I really appreciate your help so please let me know if you have any ideas.
Sent from my EVO using xda app-developers app
Go to IRC #TWRP and tell them your issue and share your recovery log.
Thanks I'll try.
Sent from my EVO using xda app-developers app
This also worked on my M8_ul
I can't make backups on TWRP anymore and I think the clockmod recovery could be a reason why. How do I remove it? I assume use terminal emulator but what are the commands?
Sent from my EVO using xda app-developers app
You can NOT possibly have 2 coexistent recoveries, the recovery partition is just one
Sent from my liquid glowing bomb shell
Then I don't know why TWRP keeps failing when it tries to access the data partition when I run a back up. I've tried flashing multiple versions and nothing works. It used to work fine and now it doesn't. I fist thought it was AVG anti theft I had installed but I removed it and no change.
Sent from my EVO using xda app-developers app
Weird, have you tried to reflash twrp?
And does your phone work as it should when in Android?
Sent from my liquid glowing bomb shell
Also, what version of TWRP? Some users have reported issues with some of the newer versions.
Sent from my EVO using XDA Premium 4 mobile app
Also are S-Off?
Sent from my EVO using Tapatalk 4
Also if you are flashing 4.2.2 roms you probably have a few /data/media/0 every time you flash a 4.2.2 rom another 0 folder is added so if you flashed four 4.2.2 roms it will look like this /data/media/0/0/0/0 meaning you may be low on storage.
Look here for a better understanding
http://forum.xda-developers.com/showthread.php?t=2304138
I am on Sense 5 port r141 which is 4.1.2. I am S-off. Have tried TWRP 2.5.0.0, 2.6.0.0, 2.6.0.1 both new version and capts modified. I get error 255 in the recovery log every time it tries to access the data partition. I don't have a data/media folder as I reviewed that thread posted. I don't think it's a memory issue as I still show more than 2.7gb of free internal space within the TWRP recovery.
Sent from my EVO using xda app-developers app
Here is my recovery log. This is TWRP.
persist.rild.nitz_long_ons_2=""
persist.rild.nitz_long_ons_3=""
persist.rild.nitz_short_ons_0=""
persist.rild.nitz_short_ons_1=""
persist.rild.nitz_short_ons_2=""
persist.rild.nitz_short_ons_3=""
debug.nfc.fw_download=true
debug.nfc.fw_boot_download=false
debug.nfc.se=true
ro.nfc.port=I2C
persist.timed.enable=true
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130816-UNOFFICIAL-jewel
ro.modversion=10.1-20130816-UNOFFICIAL-jewel
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
com.qc.hardware=true
debug.composition.type=dyn
debug.egl.hw=1
debug.mdpcomp.logs=0
debug.sf.hw=1
dev.pm.dyn_samplingrate=1
lpa.decode=true
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
persist.audio.speaker.location=high
persist.hwc.mdpcomp.enable=true
persist.thermal.monitor=true
ro.opengles.version=131072
ro.qc.sdk.audio.fluencetype=fluence
wifi.interface=wlan0
persist.gps.qmienabled=true
ro.baseband.arch=msm
ro.product.wireless=WCN3660
ro.qualcomm.bt.hci_transport=smd
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.choice_fn=stopped
init.svc.dmesg=stopped
init.svc.adbd=restarting
service.adb.root=1
init.svc.recovery=running
Running boot script...
Finished running boot script.
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/sdcard/TWRP/.twrps'.
I:Backup folder set to '/sdcard/TWRP/BACKUPS/HT25AS401570'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'backup'
I:Set page: 'backup_run'
Updating partition details...
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Backup Name is: '2013-08-24--18-55-15'
I:Full_Backup_Path is: '/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-15/'
I:Calculating backup details...
* Total number of partitions to back up: 1
* Total size of all data: 1511MB
* Available space: 2804MB
[BACKUP STARTED]
* Backup Folder: /sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-15/
I:Estimated Total time: 2 Estimated remaining time: 2
Backing up Data...
I:Using compression...
I:tar_append_tree '/data/misc' as '/misc'
==> tar_append_tree(0x44c90190, "/data/misc", "/misc"
==> tar_append_tree(0x44c90190, "/data/misc/dhcp", "/misc/dhcp"
==> tar_append_tree(0x44c90190, "/data/misc/keystore", "/misc/keystore"
==> tar_append_tree(0x44c90190, "/data/misc/location", "/misc/location"
==> tar_append_tree(0x44c90190, "/data/misc/location/mq", "/misc/location/mq"
==> tar_append_tree(0x44c90190, "/data/misc/keychain", "/misc/keychain"
==> tar_append_tree(0x44c90190, "/data/misc/bluetooth", "/misc/bluetooth"
==> tar_append_tree(0x44c90190, "/data/misc/vpn", "/misc/vpn"
==> tar_append_tree(0x44c90190, "/data/misc/wifi", "/misc/wifi"
==> tar_append_tree(0x44c90190, "/data/misc/wifi/hostapd", "/misc/wifi/hostapd"
==> tar_append_tree(0x44c90190, "/data/misc/wifi/wpa_supplicant", "/misc/wifi/wpa_supplicant"
==> tar_append_tree(0x44c90190, "/data/misc/wifi/sockets", "/misc/wifi/sockets"
E:Error appending '/data/misc' to tar archive '/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-15//data.ext4.win'
I:createTarFork() process ended with ERROR=255
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'backup'
I:Set page: 'backup_run'
Updating partition details...
I:Unable to mount '/sd-ext'
I:Actual block device: '', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Backup Name is: '2013-08-24--18-55-23'
I:Full_Backup_Path is: '/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-23/'
I:Calculating backup details...
* Total number of partitions to back up: 3
* Total size of all data: 2389MB
* Available space: 2804MB
[BACKUP STARTED]
* Backup Folder: /sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-23/
I:Estimated Total time: 5 Estimated remaining time: 5
Backing up Boot...
I:Backup command: 'dd if=/dev/block/mmcblk0p21 of='/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-23//boot.emmc.win' bs=16777216c count=1'
I:1+0 records in
1+0 records out
I:16777216 bytes (16.0MB) copied, I:0.488478 seconds, 32.8MB/s
Iartition Backup time: 0
* Generating md5...
* MD5 Created.
I:Estimated Total time: 5 Estimated remaining time: 3
Backing up Data...
I:Using compression...
I:tar_append_tree '/data/misc' as '/misc'
==> tar_append_tree(0x44c914e0, "/data/misc", "/misc"
==> tar_append_tree(0x44c914e0, "/data/misc/dhcp", "/misc/dhcp"
==> tar_append_tree(0x44c914e0, "/data/misc/keystore", "/misc/keystore"
==> tar_append_tree(0x44c914e0, "/data/misc/location", "/misc/location"
==> tar_append_tree(0x44c914e0, "/data/misc/location/mq", "/misc/location/mq"
==> tar_append_tree(0x44c914e0, "/data/misc/keychain", "/misc/keychain"
==> tar_append_tree(0x44c914e0, "/data/misc/bluetooth", "/misc/bluetooth"
==> tar_append_tree(0x44c914e0, "/data/misc/vpn", "/misc/vpn"
==> tar_append_tree(0x44c914e0, "/data/misc/wifi", "/misc/wifi"
==> tar_append_tree(0x44c914e0, "/data/misc/wifi/hostapd", "/misc/wifi/hostapd"
==> tar_append_tree(0x44c914e0, "/data/misc/wifi/wpa_supplicant", "/misc/wifi/wpa_supplicant"
==> tar_append_tree(0x44c914e0, "/data/misc/wifi/sockets", "/misc/wifi/sockets"
E:Error appending '/data/misc' to tar archive '/sdcard/TWRP/BACKUPS/HT25AS401570/2013-08-24--18-55-23//data.ext4.win'
I:createTarFork() process ended with ERROR=255
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'backup'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log
Sent from my EVO using xda app-developers app
so /data/misc is the problem, there might be something wrong with it's permissions
Okay I think I have a bad misc partition because I ran the strings command and got just FNOC. I need the p23_dump file so I can fix the partition but the link on goo manager is no longer good. Can anyone help me with this?
Sent from my EVO using xda app-developers app
I fixed misc partition but no affect on my problem. Can't make a back up. Error 255 every time it tries to access the data partition.
Sent from my EVO using xda app-developers app
Starzboy77 said:
I fixed misc partition but no affect on my problem. Can't make a back up. Error 255 every time it tries to access the data partition.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
i had the same issue with twrp 2.6.0.0 .just wouldnt make a backup. after installing it and bouncing back and forth between 2.5 and 2.6 finally 2.6 took correctly. only advise i can give you. i did that and a full wipe all sd and internal then installed fresh rom. has worked correctly since.
kaos420 said:
i had the same issue with twrp 2.6.0.0 .just wouldnt make a backup. after installing it and bouncing back and forth between 2.5 and 2.6 finally 2.6 took correctly. only advise i can give you. i did that and a full wipe all sd and internal then installed fresh rom. has worked correctly since.
Click to expand...
Click to collapse
He RUU'd and fixed the issue.
Sent from my EVO using XDA Premium 4 mobile app
FinZ28 said:
He RUU'd and fixed the issue.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks was nice of him to update the thread. lol
kaos420 said:
thanks was nice of him to update the thread. lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2428222
Sent from my EVO using XDA Premium 4 mobile app
Yes I fixed my problem. Thanks again. I RUU and then unlocked the bootloader again. I ended up only losing my texts as I have titanium backup so it worked out well. In case people are wondering, I used Viperuu.
Sent from my EVO using xda app-developers app
Hello, xda!
I need a help!
I want to port stock rom via Android kitchen, so I dumped system.img and boot.img from my phone and then I have tried to cook it in the kitchen.
But when I flash it, it says "Updater process ended with signal: 11"
Is there error in my rom or in the updater-script?
How to fix that?
Could be anyone here so kind to tell me, please?
recovery log while flashing:
Code:
I:operation_start: 'Flashing'
Installing zip file '/external_sd/VF-895N_signed_040116_202039.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Updater process ended with signal: 11
I:Legacy property environment disabled.
Error installing zip file '/external_sd/VF-895N_signed_040116_202039.zip'
Updating partition details...
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Data backup size is 0MB, free: 3498MB.
I:sending message to remove 65537
I:Message sent, remove storage ID: 65537
mtppipe remove storage 65537
...done
I:Set page: 'flash_done'
I:operation_end - status=1
P.S. there is no stock rom (zip) for my phone yet, that's the reason I need to make it.
All we have is Sugar program that downloads the stock rom but when it downloads the rom, there are just .mbn files.
Is there any method to make the flashable stock rom from these .mbn files ?
Thank you so much for advices.
Hello, xda!
I need a help!
I want to port stock rom via Android kitchen, so I dumped system.img and boot.img from my phone and then I have tried to cook it in the kitchen.
But when I flash it, it says "Updater process ended with signal: 11"
Is there error in my rom or in the updater-script?
How to fix that?
Could be anyone here so kind to tell me, please?
recovery log while flashing:
Code:
I:operation_start: 'Flashing'
Installing zip file '/external_sd/VF-895N_signed_040116_202039.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Updater process ended with signal: 11
I:Legacy property environment disabled.
Error installing zip file '/external_sd/VF-895N_signed_040116_202039.zip'
Updating partition details...
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Data backup size is 0MB, free: 3498MB.
I:sending message to remove 65537
I:Message sent, remove storage ID: 65537
mtppipe remove storage 65537
...done
I:Set page: 'flash_done'
I:operation_end - status=1
P.S. there is no stock rom (zip) for my phone yet, that's the reason I need to make it.
All we have is Sugar program that downloads the stock rom but when it downloads the rom, there are just .mbn files.
Is there any method to make the flashable stock rom from these .mbn files ?
Thank you so much for advices.
Same prop
I already unrooted and setup custom os on a couple of Motorola G7 play phones. But on this one, I thought I would try a different way to install twrp permanently.
which was to boot into twrp, then "install recovery ramdisk" pointing it to the recovery.img that I know works correctly with this phone.
I got these messages....
I:Switching slots to flash ramdisk to both partitions
I:Setting active slot B
Updating partition details...
Iata backup size is 867MB, free: 14022MB.
I:checking for twrp app
I:Can't probe device /dev/block/bootdevice/by-name/vendor_b
Failed to mount '/vendor' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/vendor_b', current file system: 'ext4'
I:Can't probe device /dev/block/bootdevice/by-name/modem_b
Failed to mount '/firmware' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/modem_b', current file system: 'ext4'
I:Can't probe device /dev/block/bootdevice/by-name/dsp_b
Failed to mount '/dsp' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/dsp_b', current file system: 'ext4'
...done
Backing up Boot...
I:Reading '/dev/block/bootdevice/by-name/boot_b', writing '/tmp/repackorig//boot.emmc.win'
I:Restored default metadata for /tmp/repackorig//boot.emmc.win
I:Error unpacking /tmp/repackorig/boot.img, ret: 256!
Error unpacking image.
I:Set page: 'action_complete'
Iperation_end - status=1
At this point, I realized I didn't previously flash dtbo.img. I suspected if I reboot I would brick the phone. I decided to reboot to bootloader anyway. because to start flashing over the top of this seemed like a bad idea.
Which I in fact bricked the phone.
What should I have done at this point? Gone ahead and flashed dtbo from the PC while in twrp? flashed a copy of the boot.img (from my PC?). before I rebooted?
I actually have found NO info on why I am reflashing dtbo, or whats in these modified dtbo's, or how to tell I need to flash the dtbo. Or if it's even correct "before" commiting to unpacking/repacking the boot image.
And there are multiple links to different modified dtbo's and different instructions sometimes leave out no-verity-opt-encrypt.zip For the record I didn't do this no verity step on the last couple phones and worked fine.
What is the procedure to fix the boot before I reboot out of twrp. And how do I know I have a good copy of a modified dtbo
How can I tell I have (or not) already flashed dtbo?
So since this phone seems to have borked Slot B. Can I unbrick it somehow by going to Slot A? It does not respond to anymore to VolumeDown-Power button so it really bricked for good or not?
Sorry for all the questions, but I think this would save a ton of people wrecking phones.