Cynagogen mod 6 rls 5.1 wont install - Tilt, TyTN II, MDA Vario III Android Development

I use a 1gb sd with a fat32 and a ext2 partition.
It doesn't want to install, tried also the eclair version. Same problem.
Please help me .
This is my bootlog
** /dev/block/mmcblk0p1
** Phase 1 - Read and Compare FATs
Attempting to allocate 988 KB for FAT
Attempting to allocate 988 KB for FAT
** Phase 2 - Check Cluster Chains
** Phase 3 - Checking Directories
** Phase 4 - Checking for Lost Files
Free space in FSInfo block (201623) not correct (201622)
Fix? yes
Next free cluster in FSInfo block (50390) not free
Fix? yes
9 files, 403244 free (201622 clusters)
sh: 1: unknown operand
Using partitioned system
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/mmcblk0p2 is mounted
ext2: clean, 11/120832 files, 15402/481950 begin_of_the_skype_highlighting**************15402/481950******end_of_the_skype_highlighting blocks
Creating a new Data store
256+0 records in
256+0 records out
mke2fs 1.38 (30-Jun-2005)
mke2fs: cannot determine if /sdcard/andboot/data.img is mounted
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
65536 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=1
32 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185
Writing inode tables: 0/32 1/32 2/32 3/32 4/32 5/32 6/32 7/32 8/32 9/3210/3211/3212/3213/3214/3215/3216/3217/3218/3219/3220/3221/3222/3223/3224/3225/3226/3227/3228/3229/3230/3231/32done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0: clean, 11/65536 files, 8286/262144 blocks
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
Click to expand...
Click to collapse
Also adding a third partition as linuxswap makes this install not even see the ext2 partition, thats why I did not add a linuxswap, do I need to?

Try installing it without an ext2 partition, there really is no benefit from using an ext2 partition on a haret install, in fact it may be the cause of your problems, a swap partition may help however, around 64-96 MB is usually more than enough.
The error messages may indicate that the Fat32 partition is not the first partition on the SD card, it depends what you used to partition the SD, some utilities are no good for android SD partitioning, since they may create the partition wrongly, ( as far as android is concerned).

Related

[Q] [Help] 32GB SD Card Error

I have a 32GB uSD Card Class 6. I partition in Recovery (RA) with 512 Swap, 1920 ext2 (or 3 or 4 tried all) and remaining FAT32. If I use the old 8GB Class 4 card with 100MB Swap, 512MB EXT4 and remainder FAT32, it works fine.
I get the error "Bad magic number in super-block while trying to open /dev/block/mmcblk0p2" when I try to upgrade from EXT2 to 4 and when I wipe DALVIK Cache. I tried mini partition with the same results. I have formatted card with NTFS and copied a 17GB movie file and it plays ok. Reformat it as above and back to same old error. Can copy files into FAT32 partition (<2gb files that is) and see them. Here is a RECOVERY.log of the partition, upgrade and then Dalvik cache wipe. Please help
- RECOVERY.log------------------------------
Model: SD 33333 (sd/mmc)
Disk /dev/block/mmcblk0: 32.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 30.3GB 30.3GB primary fat32 lba
2 30.3GB 32.2GB 1920MB primary
3 32.2GB 32.7GB 512MB primary
script log is located @ /data/sdparted.log
Partitioning complete!
I:Set boot command ""
Upgrade ext2 to ext3
Press Trackball to confirm,
any other key to abort.
Upgrading ext2 to ext3 : .e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Ext upgrade complete!
I:Set boot command ""
Upgrade ext3 to ext4
Press Trackball to confirm,
any other key to abort.
Upgrading ext3 to ext4 : .tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p2
/dev/block/mmcblk0p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Ext upgrade complete!
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Wipe Dalvik-cache
Press Trackball to confirm,
any other key to abort.
Formatting DATA:dalvik-cache...
Formatting CACHE:dalvik-cache...
Formatting SDEXT:dalvik-cache...
E:Can't mount /dev/block/mmcblk0p2 (or /dev/block/mmcblk0)
(Invalid argument)
Error mounting /sd-ext/dalvik-cache!
Skipping format...
Dalvik-cache wipe complete!
-end-----------------------------------------------
when i run this command
/ # e2fsck -p /dev/block/mmcblk0p2
e2fsck -p /dev/block/mmcblk0p2
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcb
2
/dev/block/mmcblk0p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
What does this all mean. I had a dream of a 32 GB storage with plenty of songs and media on my HTC Desire
__________________
HTC Desire PVT4
SD Card: 32GB Class 6
Espresso Sense HD RCS Touch v2.1 A2SD+
Recovery: RA AMON Recovery 2.0.0
Radio: 32.54.00.32U_5.14.05.17
HBOOT : 0.93.0001 S-OFF
Try formatting it with no swap. Set it to 0.
Ok, tried that same error. 0MB Swap, 512MB Ext2 and remainder FAT32. Partition FAT32 is first (viewable and RW in Windows) followed by 512MB EXT2.
I guess the question should be asked, does anyone run a HTC Desire GSM with a 32GB microSD Card, and if so what/how did the partitions set up. I suspect that the HTC Desire does not support 32GB cards. (I put the card in a HTC Desire HD and formatted under Clockworks 3.0.0.5). Formats ok, but get same error. Put a 16 GB card in CLASS 10 and get same errors. Put an 8GB microSD CLASS 4 and everything works fine.
-thanks anyway for the suggetion !

Nook Touch Partition Hacking

Folks are starting to look at the ST partition table and the file layout on the ST. This post is intended for other folks with power tools to think about.
My goals:
- expose the BN content (so I can read the New Yorker on my NC, mostly, but also so I can manage the library on my ST with Calibre as I do on the NC)
- understand how much room I have on the internal memory
- increase the amount of memory available for sideloading.
I got in well over my head during a conference call last week, but my ST is reborn and now able to do cool things.
However: I did not start from a factory fresh partitioning scheme, sadly. My first backup of the device went permanently offline (the disk and linux install containing it) and I was unable to return to it after I'd borked the ST pretty badly on the call. All I really was sure of was the partition order.
The tools:
- "noogie." Available and discussed at http://nookdevs.com/NookTouch_Rooting
- the rooting disk from http://forum.xda-developers.com/showthread.php?t=1132693 (currently at 1-6-24 - mad props to the folks who put that together!)
- a working Linux installation with USB support. Vmware player in Windows works just fine for this.
Note: currently, that third element is key; this is not intended as a walkthrough that tons of people could follow today, but to spark awareness of the technique - it seems possible that something very much like the DeanG scripts for redoing the NC partitions could emerge. Hint Hint.
First: the noogie disk is super cool. You boot from it and it mounts all of your ST partitions. So you can get a complete backup in linux (or Mac) by :
#dd if=/dev/sdX of=virigin.ST.img bs=1M
A true disk image backup.
You could (if you were patient) get the individual partitions as well - there is value in doing that, because within the first three partitions your serial number is stored. It's possible to restore this image to a different ST -- but then you've also transferred your serial number. whoops.
You can mount the partitions in linux and copy all the files from each of them as well.
After you have a backup, power off, insert the simple touch root disk, and power up. It will boot to a screen that reads "rooted forever" (as does Noogie) and after a pause, will continue booting as it does some setup.
You will wind up with ADB enabled over wifi by default and google apps installed.
You may also need to restart immediately -- I've found that sometimes after rooting, my s/n is all zeroes. Restarting clears that.
I also find that in order to get the Android marketplace working, I need to hunt down a copy of Vending.apk that is 2 meg (2,125,824 bytes on disk) in size and install it over the copy that touchnooter installs. I believe this one is the one that folks use for cm7?
The command to install it is:
#adb install -r Vending.apk
The -r is needed to avoid getting told the signature's bad. It's a reinstall flag.
So , once rooted, you have access to ADB and to fdisk for examining and changing disk layout.
The layout is interesting. Here's the issue: I know the order of the layout, but I screwed up my partition boundaries before I started, so the actual values here are from AFTER I finished:
(these values are from the fdisk display; they are not commands)
/dev/block/mmcblk0p1 c Win95 FAT 1-38
/dev/block/mmcblk0p2 c Win95 FAT 39-46
/dev/block/mmcblk0p3 83 Linux 47-141
/dev/block/mmcblk0p4 5 Extended 142-926
/dev/block/mmcblk0p5 83 Linux 142-285
/dev/block/mmcblk0p6 6 FAT16 406-807
/dev/block/mmcblk0p7 83 Linux 808-926
/dev/block/mmcblk0p8 83 Linux 286-405
It's partitions 5-8 that are interesting.
5 is /system, and I leave it untouched.
6 is /media - the area you can copy files to. 6 is -- on my device -- the SECOND to last PHYSICAL partition.
7 is /cache. It is the LAST physical partition.
8 is /data - and it is the 6th PHYSICAL partition.
The device restore scripts from BN don't care how big the partitions are, but they do care what ORDER they're in.
I will give my current partition table at the end - I want to avoid posting a (wrong) copy of what I thought I started with, because I screwed it up.
A stock ST writes your purchases to /data, not to /media.
It writes them to /data/media, in fact.
So, first question: what happens if you do an
#rm -r
inside /data/media, then
#cd ..
#rmdir media
then do
#ln -s media /media to so you wind up with
lrwxrwxrwx root root 2011-08-29 20:19 media -> /media
in your /data partition?
1) It works
2) restart, grab stuff from BN - and you see it from your desktop system. Your content is visible.
Win!
Ok, so the next thing is: bugger . I only have 240 M or so of room for stuff now? Eh?
shell back in and use fdisk to delete the partitions and rebuild them.
The order is key here. They are named as they're made, but you need them laid out out of physical order.
The following worked for me:
#fdisk /dev/block/mmcblk0
d6
d6
d6
Partitions 6, 7 and 8 are gone now.
Next, to create partitions of a useful size in the correct order
n
(creates p6)
406 807
n
(creates p7)
808
926
n
(creates p8)
286 405
write your changes from fdisk.
reboot.
But - now you've picked stuff and moved it around. It's a Really Good Idea to reformat the partitions before use.
The best way is probably to use the mkfs tools on the device.
Best way, schmest way. I booted to Noogie and used qtparted in linux so I had a gui to doublecheck my partition layout.
formatted these as ext3 for the Linux partitions at 7 and 8, and as fat16 for the win partition at 6.
It's entirely possible that you could format that as fat32, but it comes from the factory at fat16 so I stuck with that.
Power down, remove noogie, power up.
I got a "failed to install" followed by a reboot followed by being back in the OS.
I did not have to reroot to get my apps, but I did need to reroot to fix the marketplace - the /data partition being blown out meant that the Android market was crashing.
Now, to finish:
go back in via adb and reestablish the symlink (you just blew it out when you resized /data)
So:
shell in
#cd /data/media
#rm -r
(only inside /data/media, it WILL tear out any files it sees.) then
#cd ..
#rmdir media
then do
#ln -s media /media
And your stuff is put on the /media directory and can be managed properly.
I think this stuff may well be scriptable.
There's a great thread on the repartitioning that I found last night, making use of sfdisk rather than fdisk:
http://forum.xda-developers.com/showthread.php?t=1225196
As far as I know, swapping /data/media out to /media is new, but if it's not I apologize for being unaware of it.
So, here's the layout I finished with:
Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 38 77808 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 39 46 16384 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 47 141 194560 83 Linux
/dev/block/mmcblk0p4 142 926 1607680 5 Extended
/dev/block/mmcblk0p5 142 285 294896 83 Linux
/dev/block/mmcblk0p6 406 807 823296 6 FAT16
/dev/block/mmcblk0p7 808 926 243696 83 Linux
/dev/block/mmcblk0p8 286 405 245728 83 Linux
Partition table entries are not in disk order
Can you please format your commands in such a way that they look correctly? Current formatting in the post with your commands seem strange and incorrect.
I think all are OK except the fdisk commands.
Unfortuantely, the fdisk commands are given inside of an ascii gui of sorts, to there's really no 'great' way to represent them, I don't think.
I've prepend the others with # so it's obvious they're shell commands.
How's about symlinking various things to a 2nd partition (ext4?) on the sdcard then?
gparted?
Has anybody tried gparted to resize the partitions? If it works it could be useful.
Have any one tried doing it on windows and using which software? I'm thinking of mini tool's partition manager. But i'm not sure. Anyone?
roustabout said:
#cd /data/media
#rm -r
(only inside /data/media, it WILL tear out any files it sees.) then
#cd ..
#rmdir media
then do
#ln -s media /media
And your stuff is put on the /media directory and can be managed properly.
Click to expand...
Click to collapse
Thanks a lot for this, but the second and last lines are wrong:
rm -r should be rm -r *
ln -s media /media should be ln -s /media media
Still, thanks for the idea!
I wonder if symlinking to the sdcard could fix the whole 'shelves don't work for sideloaded books on sdcards' problem.

[Q] SD Card write speed dropped!

Well, I got a new Class 10 SD card, Transcend, from an online shop.
First few days it gave me great speeds. ~15mbps. Now, I'm getting not more than 4mbps!
I guess this happened mostly after using Data2SD or Partitioning the SD card
Anyone has any clue?
Hi,
I'd suggest formatting your memory card, then re-partitioning/re-doing whatever you've done to it.
Sent from my very dumb HTC Wildfire S (Stock Euro 2.3.5)
Did that a couple of times already
Well then I really don't know, sorry ...
Sent from my very dumb HTC Wildfire S (Marvel - Stock Euro 2.3.5)
Try using an SD Card reader and check its speed on your PC so that you know whether it's the card or the phone.
Then try a fresh ROM without Data2SD and check the speed.
Do each of the tests more than once cause sometimes there can be anomalies.
Same problem here
Bout a Samsung class 10 ,16gb sdhc and transfered some files to test the speed on my computer
I got 21mb write and 24mb read speed just as it said on the box
made partitions with Minitool to creat ext4 at a 32 cluster size
next thing you know even in windows my speed went down to 1mb/ and 2mb/sec
Anyone know whats going on here ?
Partition Alignment
SharpKami said:
Bout a Samsung class 10 ,16gb sdhc and transfered some files to test the speed on my computer
I got 21mb write and 24mb read speed just as it said on the box
made partitions with Minitool to creat ext4 at a 32 cluster size
next thing you know even in windows my speed went down to 1mb/ and 2mb/sec
Anyone know whats going on here ?
Click to expand...
Click to collapse
There are several factors that could play into it here.
How are you accessing the microSDHC? USB cable to phone / plugged with card reader?
Can you test with a more reliable tool, like CrystalDiskMark?
Windows may be buffering the transfer and giving wrong numbers.
It could be that Minitool did not align the partition(s) properly, as it would have done for built-in SSDs.
Did you shrink the (first) FAT32 partition and create the ext4 at 'the end' of the available space?
On my WFS + SanDisk 16GB, Class 10, I created the partitions with CWM, and DATA2SD (Data2sdV2withA2sdremover_by_jikantaru) had to recreate the ext3 partition, because it was improperly aligned. This is from the data2whateverlog.txt:
Code:
=============================
Fri Nov 2 10:44:17 PDT 2012
=============================
+++ Your Partition(s) are NOT aligned and data2whatever modified them:
----------------------------------------------------------------------
+++ Your SD-Ext Partition started at sector: 29617188
=> your SD-ext partition was NOT 1024k aligned
and it should start at following sector: 29618176
+++ Your Swap Partition started at sector: 30617188
=> your Swap partition was NOT 1024k aligned
and it should start at following sector: 30617600
+++ OLD Partition table of your SD-Card:
----------------------------------------
__________________________fdisk_Partition_table_____________________________
Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 29617187 14808593+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 29617188 30617187 500000 83 Linux
/dev/block/mmcblk0p3 30617188 31116287 249550 82 Linux swap
____________________________________________________________________________
+++ The Partitiontable has been modified
----------------------------------------
__________________________fdisk_Partition_table_____________________________
Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 29617187 14808593+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 29618176 30617599 499712 83 Linux
/dev/block/mmcblk0p3 30617600 31116287 249344 83 Linux
____________________________________________________________________________
+++ The SD-ext partition got formated with EXT3 afterwards:
-----------------------------------------------------------
_________________________mke2fs+tune2fs_output______________________________
Filesystem label=userdata
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
124928 inodes, 499712 blocks
0 blocks (0%) reserved for the super user
First data block=1
Maximum filesystem blocks=524288
61 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.6 (30-May-2009)
Filesystem volume name: userdata
Last mounted on: <not available>
Filesystem UUID: 5e4066d3-bb6c-4ef9-8081-03c03cecfce7
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal dir_index filetype sparse_super
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 124928
Block count: 499712
Reserved block count: 0
Free blocks: 475708
Free inodes: 124917
First block: 1
Block size: 1024
Fragment size: 1024
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 2048
Inode blocks per group: 256
Filesystem created: Fri Nov 2 17:44:20 2012
Last mount time: n/a
Last write time: Fri Nov 2 17:44:44 2012
Mount count: 0
Maximum mount count: 31
Last checked: Fri Nov 2 17:44:20 2012
Check interval: 15552000 (6 months)
Next check after: Wed May 1 17:44:20 2013
Reserved blocks uid: 0 (user unknown)
Reserved blocks gid: 0 (group unknown)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 611421e5-1bfd-44b8-95d8-8af4c40c053b
Journal backup: inode blocks
____________________________________________________________________________
+++ Filesystem check found no errors - no log attached
-------------------------------------------------------
I checked the speed with RoboCopy over USB to the WFS, it was about 4MB/s.
CrystalDiskMark reports 4.5MB/s write speed over the same connection (with 5 runs of 100MB data).
Try using SD-Booster app
You're right litemaster ! my windows was showing the wrong figures while transferring files .
i tried the sd tester and booster ,speed results weren't all that bad , 10mb read /10mb write.
and in windows it shows 2mb but file transfers at a much higher rate some times 30mb/sec.
Appreciate your your help buddy and Eduardo
P.S... By the way , given the results , this samsung class 10 isnn't that bad. Bought it for £12.00 from amazon.

Read-only file system on microSD

Hi everybody..
I have a strange and boring issue with my micro SD card that I use with my smartphone.. Today, while I was reading a PDF book the phone freezes it self: the only solution was to reboot it!
But.. WOW; 'till that moment the phone doesn't recognize my micro-SD any more!! It doesn't give warnings or messages.. nothing.. the only problem is that my SD card is inserted but the phone won't read it..
I mount the micro sd into my Slackware laptop and it still have partitions but they are all read-only! Every thing I try to do (copy files, move, delete etc) fails with a read-only warning!
So I try to format all from the scratch.. but it is not possible!! It doesn't let me format my SD for the same reason: read-only file system!!
WOW!! It's absurd!!
What can I do? is there a solution for that?
I tried to use fsck, badblocks, mkfs but nothing helped!
fdisk -l output
Code:
Disk /dev/sdb: 15.9 GB, 15918432256 bytes
255 heads, 63 sectors/track, 1935 cylinders, total 31090688 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00031a4f
Device Boot Start End Blocks Id System
/dev/sdb1 1 29027343 14513671+ c W95 FAT32 (LBA)
/dev/sdb2 29027344 31027343 1000000 83 Linux
/dev/sdb3 31027344 31090687 31672 82 Linux swap
I have a FAT partition for data, a ext2 one used with Link2sd and a swap one.
This is the result I got when trying to format the second partition..
Code:
# mkfs.ext2 /dev/sdb2
mke2fs 1.41.14 (22-Dec-2010)
/dev/sdb2: Read-only file system while setting up superblock
The same to me. Wish a help!! Thanks

[HELP] TWRP unable to flash custom roms (miglobe etc) after miflash restore

Hi all,
I recently restored my device from EDL mode using miflash. Its boots up fine to the official stock firmware rom that i recovered to (miui 9.6.4.0) using miflash but after re-installing TWRP i'm unable to install any custom roms.
The output from TWRP:
Code:
Installing MIUI update...
performing update
Installing MIUI update...package_extract_file took 00s.
package_extract_file took 00s.blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/2bdde8504898ccfcd2c59f20bb8c9c25f73bb524
254427136 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 181701 blocks
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
writing 512 blocks of new data
Decompression failed with BLOCK_LENGTH_2
missing 1222632 bytes of new data
failed to execute command [new 2,326044,326556]
Perform Block Image Update took 04s.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
device name: /dev/block/bootdevice/by-name/system
Filesystem volume name: system
Last mounted on: <not availabel>
Filesystem UUID: da594c53-9beb-f85c-85c5-cedf76546f7a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem flags: unsigned_directory_hash
Filesystem features: has_journal ext_attr resize_inode filetype extents sparse_super large_file gdt_csum
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem os type: Linux
Inode count: 193920
Block count: 774155
Reserved block count: 0
Free blocks: 106382
Free inodes: 189202
First block: 0
Block size: 4096
Reserved GDT blocks: 191
Blocks per group: 32768
Inodes per group: 8080
Inode blocks per group: 505
Last mount time: n/a
Last write time: Wed Dec 31 19:00:00 1969
Mount count: 0
Maximum mount count: 10
Last checked: Wed Dec 31 19:00:00 1969
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
Updater process ended with ERROR: 7
I:Install took 5 second(s).
Error installing zip file '/sdcard/Download/globeROM_v10_whyred_9.2.28_cfg-fmygvtpxbrw.zip'
Updating partition details...
I:Data backup size is 842MB, free: 49040MB.
I:Unable to mount '/usb_otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
Any ideas how to solve this one?
Resolve after updating MIUI to the latest version was able to flash custom roms again.

Categories

Resources