Related
This flashable script will try to check and fix filesystem errors in your ext and fat32 partitions. The repair on fat32 may not be robust, but at least you will be alerted to any potential issues and can then run a dosfsck/chkdsk to fix issues,
This was created for my SuperNova Rom which uses Data2sd, but can be used for any Rom which uses an ext4 partition.
Potential candidates are phones with new issues of Force closes appearing, which usually signify a partition corruption..
Report on the file system check and repair will be output to /sdcard/repairlog.txt
This could be a "must-have" tool for every sdcard.
[*]Version History
FixFS 21-Sept-11
Initial script
FixFS 0.2 22-Sept-11
More checkpoints in logic
Verbose output
Any followups....
Nice one. If I had a partition to check, I'd definitely use this!
rootSU said:
Nice one. If I had a partition to check, I'd definitely use this!
Click to expand...
Click to collapse
Ha ha..
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 00:36:27 GMT 2011
Ext4 file system found...
e2fsck running
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
DosFsck running...
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
-----
Above is my result of your awsome tool(thank you so much), seems some errors occured or found problems on my sd, but not fixed during the patch's on.
Would you give me a tip for the next step?
Sent from my HTC Desire using XDA App
You will have to do a manual e2fsck from the shell, since that usually means it is waiting for user intervention due to some errors. Though the automatic options I specified should correct minor issues, some seem to still need intervention
Sent from my HTC Desire using Tapatalk
nice work as per usual matey
ran it once through ROM Manager and your screen in recovery was only visible for a split second, so I checked the repairlog and read this:
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 00:43:51 GMT 2011
Ext4 file system found...
e2fsck running
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
DosFsck running...
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
===================================
When I got home I checked the SD card through windows (no errors) then your script through Max's 4EXT app and no split second reading this time, it read:
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 04:57:43 GMT 2011
Ext4 file system found...
e2fsck running
Your ext4 file system was checked and was clean..No repair was necessary.
Sdcard found..
Attempting to unmount sdcard
DosFsck running...
Your Fat32 file system was checked and was clean..No repair was necessary.
Script has completed operations
So a very big thank you to you and Max
Great tool! Thanks very much, have been looking for something like this for ages.
Hi Droidzone,
something goes wrong for me, i explain it with log below:
recovery.log
Code:
-- Installing: /sdcard/FixFS.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/FixFS.zip
Opening update package...
Installing update...
about to run program [/tmp/pre.sh] with 1 args
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 10:38:42 GMT 2011
Ext4 file system found...
e2fsck running
/tmp/pre.sh: line 56: /tmp/e2fsck: not found
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
umount: can't umount /sdcard: Device or resource busy
DosFsck running...
/tmp/pre.sh: line 86: /tmp/fsck_msdos: not found
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
The log file has been copied to sdcard_repairlog.txt
script result was [|______________________________________________|]
minzip: Extracted file "/tmp/e2fsck"
minzip: Extracted file "/tmp/fsck_msdos"
minzip: Extracted file "/tmp/pre.sh"
________________________________________________
| |
| PARTITION CHECK & REPAIR TOOL |
| ================================== |
| - DROIDZONE - |
| |
| This is an On-Demand Partition Fix tool. |
| If you find too many force closes or freezes |
| on your phone, it may be the first indication|
| of increasing corruption on your ext4 partit-|
| ion. Running this tool will fix most of them.|
| |
| |
| [*]Checking and Fixing File system... |
| [*]Checking Fat32 File system... |
| [*]Checking ext4 File system... |
| [*]Done |
| [*]Repair log in sdcard/repairlog.txt |
|______________________________________________|
Install from sdcard complete.
So, without reboot i connected my adb shell and i'd try manually (with /sdcard alredy unmounted)
Code:
/tmp # ls -ail
ls -ail
213 drwxr-xr-x 2 root root 0 Sep 22 10:38 .
1 drwxr-xr-x 19 root root 0 Sep 22 10:03 ..
722 -rw-rw-rw- 1 root root 10 Sep 22 10:04 4ext_version
721 -rw-rw-rw- 1 root root 3 Sep 22 10:04 batt_level
756 -rwxrwxrwx 1 root root 111492 Aug 1 2008 e2fsck
730 -rw-rw-rw- 1 root root 5 Sep 22 10:04 free_space
757 -rwxr-xr-x 1 root root 22640 Aug 1 2008 fsck_msdos
758 -rwx------ 1 root root 2490 Aug 1 2008 pre.sh
692 -rw-rw-rw- 1 root root 8502 Sep 22 10:49 recovery.log
715 -rw-rw-rw- 1 root root 72 Sep 22 10:03 sd_fstypes
764 -rwxr-xr-x 1 root root 255904 Sep 22 10:38 update_binary
/tmp # /tmp/e2fsck -af /dev/block/mmcblk0p2
/tmp/e2fsck -af /dev/block/mmcblk0p2
/sbin/sh: /tmp/e2fsck: not found
/tmp # /tmp/fsck_msdos -pf /dev/block/mmcblk0p1
/tmp/fsck_msdos -pf /dev/block/mmcblk0p1
/sbin/sh: /tmp/fsck_msdos: not found
/tmp # pre.sh
pre.sh
/sbin/sh: pre.sh: not found
/tmp # ./pre.sh
./pre.sh
===================================
DROIDZONE'S FILESYSTEM FIXER SCRIPT
===================================
Script started at Thu Sep 22 10:58:36 GMT 2011
Ext4 file system found...
e2fsck running
./pre.sh: line 56: /tmp/e2fsck: not found
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
umount: can't umount /sdcard: Invalid argument
umount: can't forcibly umount /sdcard: Invalid argument
DosFsck running...
./pre.sh: line 86: /tmp/fsck_msdos: not found
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
The log file has been copied to sdcard_repairlog.txt
/tmp # ./tmp/fsck_msdos -pf /dev/block/mmcblk0p1
./tmp/fsck_msdos -pf /dev/block/mmcblk0p1
/sbin/sh: ./tmp/fsck_msdos: not found
i can't understand why ./pre.sh: line 56: /tmp/e2fsck: not found
recovery is kidding me!?
anyway all seems ok using e2fsck built in recovery 4EXT 2.1.3RC4 (i used verbose option):
Code:
~ # e2fsck -afv /dev/block/mmcblk0p2
e2fsck -afv /dev/block/mmcblk0p2
730 inodes used (0.56%)
25 non-contiguous files (3.4%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 720
259347 blocks used (49.47%)
0 bad blocks
0 large files
707 regular files
14 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
721 files
Weird indeed that the files in /tmp cant be accessed. Anyway, I'll add code to abort script if the binaries cant be found..it doesnt look good with the script saying everything's working.. I didnt add verbose early because of the output (confuses newbies?), but I'll add it too.
Edit: Forgot to mention that I use 4ext too, and no such issues here.
Droidzone said:
Weird indeed that the files in /tmp cant be accessed
Click to expand...
Click to collapse
nope, file can be accessed! with cat /tmp/e2fsck i see correct output
Droidzone said:
I'll add code to abort script if the binaries cant be found..it doesnt look good with the script saying everything's working..
Click to expand...
Click to collapse
+1 lol
did you try with 4EXT 2.1.3RC4 too?
Droidzone said:
You will have to do a manual e2fsck from the shell, since that usually means it is waiting for user intervention due to some errors. Though the automatic options I specified should correct minor issues, some seem to still need intervention
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Really appreciate for your kind explanation ^^;
Then, could somebody inform me how to to do a manual e2fsck from the shell or any links shows relative information? I've already questioned it at Q & A, but so far nobody has answered...
limscap1 said:
Really appreciate for your kind explanation ^^;
Then, could somebody inform me how to to do a manual e2fsck from the shell or any links shows relative information? I've already questioned it at Q & A, but so far nobody has answered...
Click to expand...
Click to collapse
It was there in Ultrakiller's quote.
Code:
e2fsck -afv /dev/block/mmcblk0p2
The command is found in /system/bin usually..My flasher also copies that file to /tmp. So:
Code:
chmod 755 /tmp/e2fsck
/tmp/e2fsck -afv /dev/block/mmcblk0p2
I would be linked in first post, for all that users who can't use the droidzone's script.
Reboot in Recovery, and connect adb shell.
EXT4 REPAIR/CHECK
Code:
e2fsck -afv /dev/block/mmcblk0p2
e2fsck will check and repair ext4 partition if needed.
an example:
Code:
e2fsck -afv /dev/block/mmcblk0p2
730 inodes used (0.56%)
25 non-contiguous files (3.4%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 720
259347 blocks used (49.47%)
0 bad blocks
0 large files
707 regular files
14 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
721 files
FAT32 REPAIR/CHECK
mount usb partition on pc using recovery menu.
Once connected usb cable and opened cmd on pc type:
Code:
chkdsk /R f:\
in my case fat32 partition is f:
chkdsk can take a while (around 20min)
an example of output here (sorry, italian OS, anyway in my case no errors found)
Code:
Il file system è di tipo FAT32.
Numero di serie del volume: B996-8582
Verifica dei file e delle cartelle in corso...
Verifica dei file e delle cartelle completata.
Verifica dello spazio disponibile in corso...
Verifica dello spazio disponibile completata.
Verifica del file system effettuata. Nessun problema rilevato.
13.525.072 KB di spazio totale su disco.
2.408 KB in 295 cartelle.
6.963.592 KB in 1.891 file.
6.559.064 KB disponibili.
8.192 byte in ogni unità di allocazione.
1.690.634 unità totali di allocazione su disco.
819.883 unità di allocazione disponibili su disco.
If i helped someone please hit thanks button!
First of all, thanks Droidzone for your work
I have run the tool and had this
e2fsck running
One or more errors were found in your ext4 partition
e2fsck has encountered technical errors and cannot continue. Script will ABORT
Sdcard found..
Attempting to unmount sdcard
DosFsck running...
One or more errors were found in your Fat32 partition
dosfsck has encountered technical errors and cannot continue. Script will ABORT
Script has completed operations
-----
Click to expand...
Click to collapse
When running e2fsck from adb doesn't find anything wrong:
(sorry can't copy/paste, I have attached an image)
And if I run a script (founded in a MIUI rom, a didn't remember what version) from gscript, called check sd it says:
Will be Check your SD Card from kernel message:
===============================================
[ 19.726623] mmcblk0: mmc1:b368 USD 7.46 GiB
[ 19.727478] mmcblk0: p1 p2 p3
[ 20.836303] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
[ 24.104003] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
[ 24.484558] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
[ 26.537750] EXT4-fs (mmcblk0p3): mounted filesystem without journal. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
===============================================
If you found error between two lines, then your SD card is broken.
Click to expand...
Click to collapse
The commands on that script are:
mkdir /sdcard/gscript/resources>/dev/null
clear
echo "echo Will be Check your SD Card from kernel message:" > /sdcard/gscript/resources/temp.sh
echo "echo ===============================================" >> /sdcard/gscript/resources/temp.sh
echo "dmesg|grep mmcblk0" >> /sdcard/gscript/resources/temp.sh
echo "echo ===============================================" >> /sdcard/gscript/resources/temp.sh
echo "echo If you found error between two lines, then your SD card is broken." >>/sdcard/gscript/resources/temp.sh
su</sdcard/gscript/resources/temp.sh
rm /sdcard/gscript/resources/temp.sh
Click to expand...
Click to collapse
If someone can help, I'll be really grateful. I have also tried repartitioning the whole SD card with gparted, but the problem still appears. I'm using Alex-V ROM d2ext with default kernel (snq-)
Thanks in advance
blackhawk_LA said:
First of all, thanks Droidzone for your work
I have run the tool and had this
When running e2fsck from adb doesn't find anything wrong:
(sorry can't copy/paste, I have attached an image)
And if I run a script (founded in a MIUI rom, a didn't remember what version) from gscript, called check sd it says:
The commands on that script are:
If someone can help, I'll be really grateful. I have also tried repartitioning the whole SD card with gparted, but the problem still appears. I'm using Alex-V ROM d2ext with default kernel (snq-)
Thanks in advance
Click to expand...
Click to collapse
That check in Miui seems to be at the kernel level..However imho I dont see an error...that line just seems to be the kernel output saying what ext4 options have been used for the mount (should be present for everyone ). Do you see any actual issues while using the card?
I haven't see any big issues, just noticed that the sdext restore from a nandroid seemed to take too much time (7-8 minutes for just 300mb) and that's why i used your tool and have a look at this post.
But everything is working fine (or it seems so), just wanted to know if my files could be starting to get corrupted or something.
Thanks
As far as my script is concerned..it depends on error code from e2fsck to report file system state. That particular error code means that a standard error level was not returned, so only a command line manual e2fsck will show exactly what was the system response. See Post #14 for how to do that.
Mmm this is what I did, I think. See the attached image in my other message; it seems there was no erros (0 bad blocks)
Hi, got an error in clockwork recovery : error in fixfsv0.2.zip ( status 0 ) installation aborted ..
any clues ?
Hi I am constantly getting a status 7 error when trying to install the rom from here
here is the log from the recovery
any help would be greatly appreciated
Starting recovery on Thu Mar 14 14:13:44 2013
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Tue Feb 5 19:22:42 CET 2013
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT18NT202090
ro.baseband=26.17.14.11_M
ro.carrier=ATT
ro.bootloader=0.85.2007
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=70
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 12h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35760 inodes and 4484/142847 blocks
warning: wipe_block_device: Discard failed
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: 11/75200 files (0.0% non-contiguous), 13377/300799 blocks
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/76912 files (0.0% non-contiguous), 20002/307196 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
About to install:
saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Continue install?
-- Installing: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Finding update package...
I:Update location: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
E:Error in /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
(Status 7)
Installation aborted.
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 540.5MiB
data ext3 1.1GiB 1.0GiB
cache ext3 290.5MiB 265.5MiB
sdcard fat32 1.8GiB 924.3MiB
Current Rom: IceColdSandwich-8.2.AOKP
Start fixing permissions?
Fixing permissions...
/sbin/fix_permissions 2.04 started at 03-14-2013 10:15:20
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.04 ended at 03-14-2013 10:15:20 (Runtime:0m0s)
Done!
Could anyone tell me what I am doing wrong or help me correct this problem?
EDIT: I want to note that PAC-man-v20.0.1-BLINDNDUMB.zip installs without error its just the nightlies and PAC-man-v21.0.0-BLINDNDUMB.zip that do not work for me
thekool11 said:
Hi I am constantly getting a status 7 error when trying to install the rom from here
here is the log from the recovery
any help would be greatly appreciated
Starting recovery on Thu Mar 14 14:13:44 2013
framebuffer: fd 3 (480 x 800)
Welcome to 4EXT Recovery Touch
by madmaxx82
Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 2recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext4 /dev/block/mmcblk0p25 (null)
I:end load volumes..
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
Command: "/sbin/recovery"
ro.build.date=Tue Feb 5 19:22:42 CET 2013
ro.build.date.utc=0
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=msm7x30
ro.build.product=ace
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT18NT202090
ro.baseband=26.17.14.11_M
ro.carrier=ATT
ro.bootloader=0.85.2007
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=70
ext.edition=ng
Ireparing..
Preparing boot.. 2Irep sys1: 0
Preparing boot.. 2Ireparing.. fin
Preparing boot.. 2 Configuring settings..
Your configuration settings:
Using button backlights level: 80
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Timezone: configured
Using 12h-hour time format
I:theme propok
Recovery is ready..
I:have tz_data
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
Creating filesystem with parameters:
Size: 585101312
Block size: 4096
Blocks per group: 32768
Inodes per group: 7152
Inode size: 256
Journal blocks: 2231
Label:
Blocks: 142847
Block groups: 5
Reserved block group size: 0
Created filesystem with 11/35760 inodes and 4484/142847 blocks
warning: wipe_block_device: Discard failed
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p26: 11/75200 files (0.0% non-contiguous), 13377/300799 blocks
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.12 (17-May-2010)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p27: 11/76912 files (0.0% non-contiguous), 20002/307196 blocks
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
About to install:
saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Continue install?
-- Installing: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Finding update package...
I:Update location: /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
assert failed: getprop("ro.product.device") == "saga" || getprop("ro.build.product") == "saga"
E:Error in /sdcard/saga_PAC_JB_4.2.2-v20.1.0_20130310.zip
(Status 7)
Installation aborted.
------------------ Info -------------------
mount point | fs | size | free
system ext4 549.2MiB 540.5MiB
data ext3 1.1GiB 1.0GiB
cache ext3 290.5MiB 265.5MiB
sdcard fat32 1.8GiB 924.3MiB
Current Rom: IceColdSandwich-8.2.AOKP
Start fixing permissions?
Fixing permissions...
/sbin/fix_permissions 2.04 started at 03-14-2013 10:15:20
cat: can't open '/data/system/packages.xml': No such file or directory
cat: can't open '/data/system/packages.xml': No such file or directory
/sbin/fix_permissions 2.04 ended at 03-14-2013 10:15:20 (Runtime:0m0s)
Done!
Could anyone tell me what I am doing wrong or help me correct this problem?
EDIT: I want to note that PAC-man-v20.0.1-BLINDNDUMB.zip installs without error its just the nightlies and PAC-man-v21.0.0-BLINDNDUMB.zip that do not work for me
Click to expand...
Click to collapse
Have you checked md5sum?
glevitan said:
Have you checked md5sum?
Click to expand...
Click to collapse
Did you really need to quote all of that just to say that?
Sent from a dream.
I believe you're trying to flash a Saga ROM.
bananagranola said:
I believe you're trying to flash a Saga ROM.
Click to expand...
Click to collapse
I couldnt have been a bigger idiot, thank you very much lol this shouldve been obvious to me if I were paying attention the nightly I downloaded
thekool11 said:
I couldnt have been a bigger idiot, thank you very much lol this shouldve been obvious to me if I were paying attention the nightly I downloaded
Click to expand...
Click to collapse
Sorry noob here. I'm getting the status 7 error too and I have no clue what a saga rom is :/ how do i fix it?
A ROM for a different device: the Desire S, codenamed Saga. We are the forum for the Desire HD/Inspire 4G, codenamed Ace.
williamrazmy said:
Sorry noob here. I'm getting the status 7 error too and I have no clue what a saga rom is :/ how do i fix it?
Click to expand...
Click to collapse
here is a noob fiendly way to solve it
http://forum.xda-developers.com/showthread.php?t=2302599
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
do you have access to the bootloader/recovery?
noutsos said:
Hi,it all started after i flashed TWRP in my HTC sensation xe(i had 4EXT recovery),then i wanted to flash a new rom but something happened and my htc freezed and then i pulled out the battery and inserted it,i turned it On but then it couldn't mount the system,cache,data.One of my friends managed to flash again the 4EXT recovery and told me that my partitions are corrupted.I tried some metjods with adb but nothing happened,
</tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37> but it says <no such file or directory>
and also tried this <parted /dev/block/mmcblk0 mkfs ext2> but it says <can't have overlapping partitions>
Click to expand...
Click to collapse
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
[email protected] said:
I have the same problem with you,,,I have not fix it at all,,,maybe we can ask @shantur for help,,,
which rom and the TWRP version do you use???
Click to expand...
Click to collapse
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
noutsos said:
i can access my 4est recovery but i dont have a rom,after flashing one my phone stucks in the logo
Click to expand...
Click to collapse
are you on S-ON?
post your bootloader details
rzr86 said:
are you on S-ON?
post your bootloader details
Click to expand...
Click to collapse
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
noutsos said:
i am S OFF
firmware 3.33
hboot 1.27.1100
radio 11.24A.3504.31_M
Click to expand...
Click to collapse
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
rzr86 said:
ok probably you need to update 4ext version to the latest
also redownload the rom
by the way which rom did you try to flash?
Click to expand...
Click to collapse
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
noutsos said:
i tried to flash viperS 5.1.0
i tried to flash the stock,when i do factory reset it says "E:formate_volume: make_extf4fs failed on /dev/block/mmcblk0p24"
and then i reboot and stucks in htc logo
Click to expand...
Click to collapse
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
rzr86 said:
use the option format all partitions except sdcard from 4ext
then reflash the rom
which version of 4ext do you have?
Click to expand...
Click to collapse
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
noutsos said:
version 1.0.0.5 RC5
but the same thing occurs,in system is blk0p22,in data number23,in cache number24
when i try to flash custo rom it says installation aborted
Click to expand...
Click to collapse
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
rzr86 said:
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
but probably your emmc is corrupted unfortunately
by the way did you try a ruu.exe?
Click to expand...
Click to collapse
tried ruu exe but nth happened,cant find the device,and cant fastboot
How does fastboot not work? Does usb not connect at all?
Hey guys, any news about fixing bug in TWRP which caused corrupting partitions and bricking phones?
Hi guys,
I have the same issue as OP, however only the /data won't get mounted. My phone got stuck while doing wipe of the data partition in TWRP 2.6.3.0 (it didn't freeze, but it was taking over 40 minutes already), so I had to take the battery out and put it back in.
First, I tried using TWRP 2.6.3.0 to perform the wipe again, but I got
Code:
E:Unable to mount '/data'
I got the same error when I tried to install any ROM, so the installation got aborted.
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'.
Here is my bootloader info:
S-OFF
Firmware 3.33
HBOOT 1.27.1100
Radio 11.24A.3504.31_M
I am pretty much desperate at this point. Is there any way or chance of fixing my partitions? I haven't tried fixing it using parted, because I was unable to find a good howto for Sensation. I would be happy for any advice.
MatesCZ said:
Then I flashed 4EXT Recovery Touch v1.0.0.6 RC3 through fastboot and did Format all partitions (except sdcard). The format went fine with no errors, however when I tried to flash any ROM (I tried CyanogenMod 11 with 3.0.16 kernel by sultanxda and Slimkat specifically), I get:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
Same happens with the CM11 ROM. I also tried performing the full format with 4EXT recovery, then flashing the ROMs with TWRP. Same problem as before, Unable to mount '/data'..
Click to expand...
Click to collapse
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
rzr86 said:
i think something is wrong with the rom zip or with sdcard
try to redownload the rom and flash it again with 4ext recovery
or try to flash a different rom
Click to expand...
Click to collapse
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
MatesCZ said:
Here is what I did:
- Formatted the SD card
- Put CM11, Slimkat and ViperS/C2 5.2.1 on it
- Checked MD5/SHA1 sums for each of them
- Went to 4EXT, performed full format
- Tried to flash Slimkat first, same result as before:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/Slim-pyramid-4.4.4.build.7.8-WEEKLY-6262.zip (Status 7)
Installation aborted.
- Tried to flash ViperS, the installer went through fine, no errors, however, after exiting the installer, 4EXT recovery window was showing:
Code:
Starting AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
E:Error in /sdcard/ViperSC2_5.2.1.zip
(Status 0)
Installation aborted.
Tried to reboot anyway, but phone is stuck on the Sensation logo
Click to expand...
Click to collapse
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
rzr86 said:
in both cases the issue is the sdcard as i see
i suggest to format your sdcard
backup first whatever you need
or if you have a different sdcard try to flash the rom with that one
Click to expand...
Click to collapse
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
...
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Click to expand...
Click to collapse
MatesCZ said:
As I mentioned, I did format the SD card before trying.
Also today I tried with different, definitely working SD card (also formatted before trying) - same results as mentioned before. Doesn't seem to be SD card-related.
I also tried flashing stock ROM from RUU by extracting the rom.zip and renaming it to P58IMG.zip - the process gets stuck at
Code:
[6] USERDATA -Updating
forever. This consequently locked my bootloader, but I was able to unlock it again using fastboot.
I managed to retrieve log from 4EXT, and this is what it says during format of everything:
Code:
About to format everything..
..except your fat32 partition
Format BOOT SYSTEM DATA CACHE SD-EXT..?
Formatting /boot...
I:Formatting unknown device.
Formatting /system...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
51296 inodes, 204799 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
7 block groups
32768 blocks per group, 32768 fragments per group
7328 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Allocating group tables: 0/7 done
Writing inode tables: 0/7 done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/7 done
-- Wiping data...
Formatting /data...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
76480 inodes, 305852 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
10 block groups
32768 blocks per group, 32768 fragments per group
7648 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/10 done
Writing inode tables: 0/10 done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: 0/10 done
Formatting /cache...
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=64 blocks, Stripe width=64 blocks
30720 inodes, 30709 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
30720 inodes per group
Allocating group tables: 0/1 done
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: 0/1 done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: 0/1 done
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p24 (Invalid argument)
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
Data wipe complete.
All internal partitions have been formatted.
This includes dalvik-cache and batt stats
since they are just files / directories.
Your sdcard(s) weren't touched
no worries.
These lines in particular are most likely related to the problem
Click to expand...
Click to collapse
yeah you are right
some partitions are broken probably from TWRP because a lot of users faced issues similar with yours
someone posted a solution few days ago how to boot a rom from sdcard
he had also broken partitions in internal memory caused from TWRP and he managed to boot a rom from sdcard
he created two partitions
one to be recognized as /data and one to be recognized as /system and mounted them successfully(if i remember well)
but i can't find that post
if i find it i will come with edit
i know there are a lot of threads out there having the same problem as mine, but i think my situation is different, so need help on this.
Here it goes:
After i flashed my unlocked S-On HTC Sensation 4G T-Mobile back to Stock, i experienced wifi problem so i decided to flash again a rom compatible with my handset. After flashing Android_Revolution_HD-Sensation_1.2.2_T-Mobile, it's stuck on HTC Logo, so i decided to flash the Rom again. Now it can't seem to find my system and data partition, it says E: Format_volume: make_extf4fs failed. I solved the problem by partitioning my external sd card as system and data and installing another rom with the updater-script configured. Now the installer says it is sucessful but after i reboot, it's still stuck in the HTC logo. What should i do? I'm really desperate for help. Hope you can rescue me in this situation.
HEre is the installation Log (i have to delete the extract logs since it's too long):
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:11:37 1970
Preparing partitions
Formatting cache partition
unmount of /cache failed; no such volume
[Creating filesystem with parameters]:---
Size: 125784064
Block size: 4096
Blocks per group: 32768
Inodes per group: 7680
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 30709
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/7680 inodes and 1518/30709 blocks
warning: wipe_block_device: Discard failed
error: file_write: write: I/O error
E:make_ext4fs failed (1) on /dev/block/mmcblk0p24format: Can not format_ext4 emmc partition named "/dev/block/mmcblk0p24"ui_print
Installing system
Mounting system on sd-ext
about to run program [/sbin/busybox] with 6 args
Mounting Data on sd-ext2
about to run program [/sbin/busybox] with 6 args
Copying files
Setting permissions
Installing kernel
Copying kernel modules
Mounting /system on sd-ext
about to run program [/sbin/busybox] with 6 args
Extract: /system/lib/modules/bcmdhd.ko
Extract: /system/lib/modules/cdc-acm.ko
Extract: /system/lib/modules/option.ko
Extract: /system/lib/modules/pl2303.ko
Extract: /system/lib/modules/usb_wwan.ko
Writing boot image
Flashing Boot.img...
Kernel imaged flashed...
Finished
script result was [@Finished]
Installer Sucessfull (Status 0)
End at : Fri Jan 2 00:16:12 1970
did u flash boot.img after u flashed the rom?
jmcclue said:
did u flash boot.img after u flashed the rom?
Click to expand...
Click to collapse
no, how do i do that? if from fastboot, i don't think that's posible, adb can't detect my device.
iameg said:
no, how do i do that? if from fastboot, i don't think that's posible, adb can't detect my device.
Click to expand...
Click to collapse
adb & fastboot setup
http://www.google.ie/url?q=http://f...Z1GBjE&usg=AFQjCNG5wlDp1B-QvlsXu3HOD2a01TSDgw
plenty of guides here on xda for u to read if not sure of fastboot commands.
and u can always flash latest 4ext recovery and enable smart flash in settings, it flashes boot.img for s-on users.
HELP!
jmcclue said:
adb & fastboot setup
http://www.google.ie/url?q=http://f...Z1GBjE&usg=AFQjCNG5wlDp1B-QvlsXu3HOD2a01TSDgw
plenty of guides here on xda for u to read if not sure of fastboot commands.
and u can always flash latest 4ext recovery and enable smart flash in settings, it flashes boot.img for s-on users.
Click to expand...
Click to collapse
hi, after a few days of not having been able to attend to my htc sensation, now it doesn't charge (no led light indicator) and doesn't power on nor go to bootloader. how do i fix this? please help me.
Here's the log from install. Symlink issue.
AROMA Installer version 2.70RC2 (c) 2013 by amarullz xda-developers ROM Name : TyrannusRom ROM Version : v8.1 ROM Author : frenkowski Device : Samsung Galaxy S6 G920/G925 Start at : Thu Oct 22 14:35:53 2015 ****************************** * TYRANNUS ROM by frenkowski * ****************************** - Start Update! - Mounting FileSystem Mounting Partitions... about to run program [/sbin/mount] with 4 args mount: mounting /dev/block/sda15 on /system failed: Device or resource busy run_program: child exited with status 255 about to run program [/sbin/mount] with 4 args mount: mounting /dev/block/sda17 on /data failed: Device or resource busy run_program: child exited with status 255 about to run program [/sbin/mount] with 4 args mount: mounting /dev/block/sda16 on /cache failed: Device or resource busy run_program: child exited with status 255 about to run program [/sbin/mount] with 4 args mount: can't find /preload in /etc/fstab run_program: child exited with status 1 - Wipe Cache and Dalvik-Cache Wipe Cache and Dalvik-Cache... - Format System Format System... - Restoring Applications Please Wait... Installing Touchwiz Note5 Deleting Touchwiz data Installing Statusbar 3Minit Center Clock Installing Xposed Framework about to run program [/tmp/flash-script.sh] with 1 args run_program: execv failed: Permission denied run_program: child exited with status 1 Installing Viper4Android and Dolby Surround Installing Volume Booster Installing Edge Features Installing Activity Zone Installing BootAnimation AndroidM - Symlinking Settings Symlinks... symlink: failed to remove /system/bin/app_process: Read-only file system symlink: failed to symlink /system/bin/app_process to app_process64: File exists script aborted: symlink: some symlinks failed symlink: some symlinks failed Installer Error (Status 7)
Any help appreciated.