You need to use the special NVflash zip file to reset the system partition to 250M before you can flash any of the ICS roms. It will also put 5504 version of the CWM on the tablet.
http://teamdrh.com/DRH-Downloads/Full_Stock_NVFlash_CWM_5504_Touch.zip
I want to know am i the only one having this multiply flashes of the viewsonic 3 bird screen when you try to boot into the rom? I did everything right as i was to do even to extent of NV flashing but i still get this and the start up into the Rom takes like ages for me.Don't know what i did wrong along the line and this a clean Install. Any Ideas? Have being on this for the past 4hrs and still getting same result
I downloaded a "leaked" version several days ago. I flashed over top. Performance is AWESOME. No random "waits" or hangs, no force closes, etc. Couldnt ask for better.
So.. my question is.. why is this a full wipe? Did something change in the last several days? I'd like to get to the "official" build, but really am not interested in doing a full wipe.
Thoughts?
That's unrelated to whatever slowdowns you're experiencing. But, to clean up /cache, just boot into CWM and "format /cache".
Yeah. The performance is pretty bad and I'm not sure exactly where the problem lies. Most people point to the paucity of memory being the culprit, and while it may contribute quite a bit, I don't think that's all there is to it: For one thing, there are phones with just 512 MB of RAM comfortably running ICS on them. For another, I see a lot of ANRs and processes being sent SIGQUITs (SIG 3 in the logs) to generate those ANRs. For yet another, the CPU load looks very high when there's lag.it seems very slow now running 1.3, prior to this I was running CM7 and the tablet was much faster.
It's the battery. Don't know what triggers it, though, or how to fix it. I'm trying to look into it.the other issue I have on my Gtab... not sure if this is related to the ROM or not.. is that my battery indicator ALWAYS shows 100%. I tried wiping battery stats multiple times in Clockwork but not luck. I also let the tablet's battery drain down to power off. Then plugged it in, booted into clockwork and did another battery stats wipe. Still not luck.
$ [B]sha1sum `find system data -type f` | tee ROM-files.sha1[/B]
gTablet$ [B]su[/B]
gTablet# [B]cd /[/B]
gTablet# [B]sha1sum -c system/etc/ROM-files.sha1 2>&1 | fgrep -v OK[/B]
gTablet# [I]No news is good news[/I]
Nope. No such "clearing out" happens with that kind of double/triple/... partitioning. It's simply a waste of time and a distraction from real troubleshooting. An explanation of what happens when you repartition an SD card might help:I think the main reason to format 4g first then 2g is to make sure the sd card part is cleared out byond the 2g region.
~ # [B]fdisk -l /dev/block/mmcblk2[/B]
Disk /dev/block/mmcblk2: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk2p1 1 1581 12699351 c Win95 FAT32 (LBA)
/dev/block/mmcblk2p2 1582 1825 1959930 83 Linux
/dev/block/mmcblk2p3 1826 1862 297202+ 83 Linux
/dev/block/mmcblk2p4 1863 1936 [B]594405[/B] 83 Linux
~ # [B]/root/mke2fs -j -m0 /dev/block/mmcblk2p4[/B]
mke2fs 1.42.4 (12-June-2012)
Filesystem label=
OS type: Linux
Block size=[B]4096[/B] (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
37200 inodes, [B]148601[/B] blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=155189248
5 block groups
32768 blocks per group, 32768 fragments per group
7440 inodes per group
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
~ # [B]mount /dev/block/mmcblk2p4 /root/[/B]
~ # [B]df[/B]
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 224188 32 224156 0% /dev
/dev/block/mtdblock4 222208 1296 220912 1% /cache
/dev/block/mmcblk2p4 [B]585040[/B] 16860 568180 3% /root
~ #
~ # [B]time dd if=/dev/zero of=/dev/block/mmcblk3[/B]
See the description above. I can guarantee you that unless there are ghastly bugs in CWM, the parted/e2fsprogs code or in the HW, a single repartition operation will get rid of all (user-visible) data on the SD cards.
Looking at the logs, I see that the ROM installation script is still cheerfully corrupting the /cache filesystem for no good reason. It also seems to be trying to remove the dalvik-cache from non-existent devices. Somebody should really scrutinize that install script.Sadly I tried everything I could think of, still no luck. Hopefully now that someone has sent their "stuck at the birds" device in for analysis there will be a fix. I have the CWM install log if that would be helpful. [Update: log attached]
Nope.I was just wondering if you were sure you had the 250mb partition would it be necessary to nvflash.
Only a "wipe data/factory reset" is needed. You'll see that it does the other 2 (wiping cache and dalvik-cache) if you look at the messages the operation prints.If you could just do a wipe/factory reset, wipe cache, wipe davilk cache and the flash the 1.3 rom.