Important information concerning Leo flashing algorithm:

Leo is manufactured with 2 different NAND-Flash ROM chipset types. You can detect the type entering tri-color boot mode.
If you see
PB81120 SS-B3 in the first line - that means NAND-Flash ROM from Samsung - KBY00U00VM
If you have
PB1120 HX-B3 in the first line - that means NAND-Flash ROM from Hynix - h8BFS0WU0MCR

After one year usage Samsung chipset usually has a dozen of bad clusters. Hynix normally has none of them or just a couple.

So for devices with SS-B3 and Samsung chipset recommended flashing algorithm is the following:
1. Task29
2. Task32

For devices with HX-B(3/С) and Hynix chipset - Task28 is totally acceptable.

The chipset information is provided by haccker

Awesome post from minhduong11 on other thread.. fortunately i have hynix chipset but i dont know how to do task28 ..can somebody shed some light on this 2 tasks or difference between them .

Originally Posted by vallcho

How can i check how many MB left in System ?

I use this - Safe Partitioning - How to Confirm. There are of course other ways to do it without needing a computer, but I go by this.

Originally Posted by ph03n!x

It should be "LS - L" in lower case
The output would something like this:
Attachment 1109158
Note: This image is not for this ROM!!!

What I wanted to check was the sizes and permissions the files have.

Problem seem to be that there no .dex files in the dalvik-cache that represents the /system/framework/* - without which the OS of course cannot boot.

Are you sure the MD5 checksums match? Are you sure you do not have any bad blocks in your /data? Can you try including the 40ad2sdx script or the this script which I use in the zip file of the ROM - in the /system/etc/init.d directory and flash afresh? You seem to be having a SD-EXT partition, did you format it too?

Okay here is what I get



From what I understand this is proof of no bad blocks



Indeed at one time I made the EXT partition, after many repartitions.
But I'm not going to do any difficult things(scripts etc.) until I get this rom working.
Yes checksum matched om sd card and pc.
I don't know if I am smart enough to do your script lol
Note: I can get the Gingerbread nexushd2 rom working, and another gb one also.
Even tried another usb cable...

Originally Posted by mmarkk

Okay here is what I get



From what I understand this is proof of no bad blocks



Indeed at one time I made the EXT partition, after many repartitions.
But I'm not going to do any difficult things(scripts etc.) until I get this rom working.
Yes checksum matched om sd card and pc.
I don't know if I am smart enough to do your script lol
Note: I can get the Gingerbread nexushd2 rom working, and another gb one also.
Even tried another usb cable...

Umm.. easiest way to check bad blocks - format all partition in ClockWorkMod and see the recovery log (after formatting, go to advanced in ClockWorkMod and choose report error, this will save a log in your sdcard/clockworkmod directory).

For the script - pretty simple. Open the zip file for the 40ad2sdx script and navigate to /system/etc/init.d and drag and drop the file (40ad2sdx) to desktop (assuming Windows). (Or download the script I had linked and save it to desktop - remove the .txt extension if you want to). Open v2.2 ROM's zip file in WinRAR, navigate to /system/etc/init.d and drag n drop the script file from the desktop to the init.d directory. Copy the ROM's zip file to SD Card and flash as usual. This WILL change the MD5 checksum though, because you are modifying the .zip file.

Right now I am trying to figure where the problem lies - why the framework is not getting dex'ed to dalvik-cache, and these are plain shooting in the dark steps. Have you tried any other ICS ROMs, did they work?

Originally Posted by ph03n!x

Umm.. easiest way to check bad blocks - format all partition in ClockWorkMod and see the recovery log (after formatting, go to advanced in ClockWorkMod and choose report error, this will save a log in your sdcard/clockworkmod directory).

For the script - pretty simple. Open the zip file for the 40ad2sdx script and navigate to /system/etc/init.d and drag and drop the file (40ad2sdx) to desktop (assuming Windows). (Or download the script I had linked and save it to desktop - remove the .txt extension if you want to). Open v2.2 ROM's zip file in WinRAR, navigate to /system/etc/init.d and drag n drop the script file from the desktop to the init.d directory. Copy the ROM's zip file to SD Card and flash as usual. This WILL change the MD5 checksum though, because you are modifying the .zip file.

Right now I am trying to figure where the problem lies - why the framework is not getting dex'ed to dalvik-cache, and these are plain shooting in the dark steps. Have you tried any other ICS ROMs, did they work?

Thank you!
Going to check for the bad blocks now.
And going to work on your script.
I have not tried another ICS rom, in fact the GBnexushd2 rom was the first rom I ever had on my hd2 for many months before trying to go to ICS now.

Edit:



Erase failures??

Originally Posted by Charmacas

I have a question: Is it normal that it lasts some time (short to middle lag) until apps are going to start? After the apps started they are working so nice and without any lag.

I asked because that's what I am experiencing. I am using a class 10 sd card and a2sd. I have installed about 105 user apps and I am using the go launcher.

Any advice?

Gesendet von meinem NexusHD2 mit Tapatalk 2

Originally Posted by J.Soko

Try a Class 6 card. Should be faster.

Ciao,
Joachim

Actually, the higher class number the faster card it is.

Actually, after 6 it's pointless.

Class 10 or 10mbyte/second can only be reached on sequencial writing. Random writing is still a class 6, and Android is pretty random

True,but you cannot point to class 6 as a faster one than class 10...

Originally Posted by abdealiv

Important information concerning Leo flashing algorithm:

Leo is manufactured with 2 different NAND-Flash ROM chipset types. You can detect the type entering tri-color boot mode.
If you see
PB81120 SS-B3 in the first line - that means NAND-Flash ROM from Samsung - KBY00U00VM
If you have
PB1120 HX-B3 in the first line - that means NAND-Flash ROM from Hynix - h8BFS0WU0MCR

After one year usage Samsung chipset usually has a dozen of bad clusters. Hynix normally has none of them or just a couple.

.

mine says PB81110 HX-BC ??

Originally Posted by alimorshid

mine says PB81110 HX-BC ??

Hynix.