Database Info

Flashable Filesystem Check and Repair Tool

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 ?

[Q] Status 7 Error Pacman Rom

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

[Q] Freescale Tablet Problem

Hi,
I have a Zenithink C-94 tablet running ICS on it. I have compiled a JB rom and a KK rom for it, but have not been able to get the tablet to even come on. I contacted Zenithink and requested the kernel source since it is under GPL, but have had no luck. I managed to come up with the proprietaries (ex. cameras, codecs, etc.) and either obtain or write drivers for them. I have compiled the kernel, but this tablet has two kernels. Yes, two kernels; one for the boot.img and one for the "uImage_update". This writes to the vendor partition (mmcblk0p8). The kernel I have compiled is for the boot.img. I am now working on the uImage_update kernel. This one the CPIO is customized big time. See the ICS_CPIO.zip (attached). I am working on the scripts in this to update them to JB /KK. These scripts involve the partitions and recovery.fstab, etc. The partitions have changed from ICS to JB / KK. ICS was like this:
Code:
mmcblk0p1 ------- BOOT
mmcblk0p2 ------- RECOVERY
mmcblk0p4 ------- MEDIA
mmcblk0p5 ------- SYSTEM
mmcblk0p6 ------- CACHE
mmcblk0p7 ------- DATA
mmcblk0p8 ------- Vender
mmcblk0p9 ------- MISC
JB / KK are like this:
Code:
mmcblk0p1 ------- BOOT
mmcblk0p2 ------- RECOVERY
mmcblk0p4 ------- DATA
mmcblk0p5 ------- SYSTEM
mmcblk0p6 ------- CACHE
mmcblk0p7 ------- DEVICE (AKA Vender)
mmcblk0p8 ------- MISC
Boot, recovery, system, and cache have not changed. Data which was on mmcblk0p7 is now on mmcblk0p4. Device, which was known as vender, was on mmcblk0p8 is now on mmcblk0p7. Misc which was on mmcblk0p9 is now on mmcblk0p8. ICS had Media and Data separate, now they are together on the same partition. I know to change the partitions in the scripts, but I am having trouble with the recovery.fstab part. ISC is like this:
Code:
/boot emmc /dev/block/mmcblk0p1
/recovery emmc /dev/block/mmcblk0p2
/system ext4 /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p6
/data ext4 /dev/block/mmcblk0p7
## /misc emmc /dev/block/mmcblk0p9
# UBI support is under below:
#/system ubifs /dev/ubi1_0
#/data ubifs /dev/ubi1_2
#/cache ubifs /dev/ubi1_1
/sdcard vfat /dev/block/mmcblk0p4
JB / KK are like this:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/devices/platform/sdhci-esdhc-imx.2/mmc_host/mmc1 /mnt/extsd vfat defaults voldmanaged=sdcard:auto
/devices/platform/fsl-ehci /mnt/udisk vfat defaults voldmanaged=sdcard:auto
/dev/block/mmcblk0p5 /system ext4 ro wait
/dev/block/mmcblk0p4 /data ext4 nosuid,nodev,nodiratime,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic wait,encryptable=footer
/dev/block/mmcblk0p6 /cache ext4 nosuid,nodev,nomblk_io_submit wait
/dev/block/mmcblk0p7 /device ext4 ro,nosuid,nodev wait
/dev/block/mmcblk0p1 /boot emmc defaults defaults
/dev/block/mmcblk0p2 /recovery emmc defaults defaults
/dev/block/mmcblk0p8 /misc emmc defaults defaults
In the sbin folder of the CPIO is the "product_tool.sh". It has this line:
Code:
if mount -t vfat /dev/block/mmcblk1p1 /sdcard
How would I rewrite this for JB / KK according to the recovery.fstab? Would this stay the same? Please help.

[Q] Spontaneously /data and /cache unable to mount

Hi people, we really appreciate all you do for us. I have a question. I have a first seen problem here. Many of us have faced the /data cannot mount problem. HOWEVER I am in a slightly worst position. The reason is that I had corrupted /Data AND /Cache. I know that this thread http://forum.xda-developers.com/showthread.php?t=2683787 is ALMOST the same but trust me, everything I do is not enough as this thread is about the first part of my problem.
I own an HTC Sensation, I use TWRP ver 2.8.6, unlocked, S-off, Firmware 3.33, HBOT-1.27.1100, RADIO-11.24A.3504.31_M, OpenADSP-v05.6.0.2226.00.0418 and I use my pc terminal.
Accidentaly the battery dropped out while I was trying to clear Dalvik and cache to flash a new ROM as my last one was a bit heavy for me.
I have already tried this (with this difference "mmcblk0p23" ):
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p23
reboot
with this result:
~ # ←[6nmake_ext4fs /dev/block/mmcblk0p23
make_ext4fs /dev/block/mmcblk0p23
Creating filesystem with parameters:
Size: 1252769792
Block size: 4096
Blocks per group: 32768
Inodes per group: 7648
Inode size: 256
Journal blocks: 4778
Label:
Blocks: 305852
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/76480 inodes and 10067/305852 blocks
But after that, (because I already had my ROM deleted) I cant proceed as any ROM I try to flash gives me an Error at /cache.
I mount manually /data through the recovery and that's all... Everything stucks at /cache...
I even tried that just in case:
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p23
which practically (I think) gives me the same result. However when I try to:
mount /data
mkdir -p /data/media/0
exit
adb push myrom.zip /data/media/0
nothing happens as it says I do not have the permission to write (its read-only and I don't know how to fix the permissions)
Sorry for the length but I already read all the thread and (as you can understand) my problem remains... Any help would be appreciated!
I just noticed that /SD-Ext and System too are not Mounted. The only 2 mounted options in my TWRP are sdcard and Data (which I manually mounted as I described above).
I can manually tick on System too when I do all this stuff I mentioned. However, if I try to tick /cache too, EVERYTHING roll back and I can't tick Data either...

[Kali NetHunter] Chroot won't start

Hello, I have a problem using Kali with my Nexus 5 (Android 6.0.1). I have installed Kali NetHunter and Magisk using TWRP. Every time I try to start chroot in the Kali Chroot Manager, everything goes well until it gives me this error and stops:
[-] sdcard /lib/modules/3.4.0-8.14-Re4son-3.5 doesn't exist or isn't mounted. .
What should I do?

I have the same problem,,,
[+] seems you have kali chroot installed already!
[+] proc was mounted already.
[+] sys was mounted already.
[+] dev was mounted already.
[+] dev/pts was mounted already.
[+] system was mounted already.
[+] ssdcard was mounted already.
[-] sdcard /lib/modules/3.4.0-8.14-Re4son-3.5 doesn't exist or isn't mounted.
<<<< End of Script >>>>
So i think that the problem is with free space,,, you need to have at least 8gb for minimal installation,,,

xNPx3 said:
Hello, I have a problem using Kali with my Nexus 5 (Android 6.0.1). I have installed Kali NetHunter and Magisk using TWRP. Every time I try to start chroot in the Kali Chroot Manager, everything goes well until it gives me this error and stops:
[-] sdcard /lib/modules/3.4.0-8.14-Re4son-3.5 doesn't exist or isn't mounted. .
What should I do?
Click to expand...
Click to collapse
You have to update nethunter.apk through the f-droid store.
If you encounter problems while installing nethunter, download the app from the web store.The url is at the end of the site in the nethunter store under references to find.

Hi guys, I have a Nexus 5 and It wasn't imposible to chroot too, I guess the problem is to not have enough free space in /system, so I decided to reparttition disk with gparted and adb shell command. I set to 8GB /system and it didn't resolve anything because it caused other issues, I think messing with partitions is a gamble.
I attach to you the bash script that resizes Nexus 5, you can modify it like you want. Then only:
1. "adb push repartition.sh /"
2. "adb push parted /"
3. "adb shell"
4. "chmod +x repartition.sh"
5. "./repartition.sh" or "sh repartition.sh"
Reboot and flash the kali rom you like.
WARNING: IT DOESN'T WORKED FOR ME, I THINK I CHOOSE BAD PARTITION SIZES, AND LATER I HAD TO RECOVER THE PHONE WITH STOCK ROM.
# repartition.sh ###############################################
#!/bin/sh
chmod +x parted
./parted /dev/block/mmcblk0 p
umount /data
umount /sdcard
umount /cache
umount /system
./parted /dev/block/mmcblk0 rm 25
./parted /dev/block/mmcblk0 rm 26
./parted /dev/block/mmcblk0 rm 27
./parted /dev/block/mmcblk0 rm 28
./parted /dev/block/mmcblk0 mkpart primary 193MB 10193MB
./parted /dev/block/mmcblk0 mkpart extended 10193MB 10224MB
./parted /dev/block/mmcblk0 mkpart primary 10224MB 11268‬MB
./parted /dev/block/mmcblk0 mkpart primary 11268MB 15.8GB
./parted /dev/block/mmcblk0 p
./parted /dev/block/mmcblk0 name 25 system
./parted /dev/block/mmcblk0 name 26 crypto
./parted /dev/block/mmcblk0 name 27 cache
./parted /dev/block/mmcblk0 name 28 userdata
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p27
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p28
./parted /dev/block/mmcblk0 p
mount -a
exit
# EOF #####################################################
Good luck mates.