NexusHD2 Android Forum

sameer wrote:

Hi Tytung,

i used is rmnet,installation to nand and i installed the rom and kept on the charge and when to sleep,when i woke up,i restarted the phone and from that moment it shows cynogen mods revolving for ages,it does not go ahead than that.

I installed many times but the same out come.

Is there other way to get u the logcat since the phone is stuck in cynogen mod revolving.

Together with it i noticed it freezes in lock screen after some time,hav to try pressing the home button and try to move the slider to unlock.



thanks, waiting for ur response..

sameer

Increase your system partition size more - you probably have some bad blocks. Try 300 or more. If that leaves too little room for data and apps you may have to try using DataOnExt method.

NYLimited wrote:
Increase your system partition size more - you probably have some bad blocks. Try 300 or more. If that leaves too little room for data and apps you may have to try using DataOnExt method.

hi, thanks for the response, i high appreciated ur help.

I wanted to ask if there are bad blocks why do other version of roms like 2.5,2.6 work excellently there is no trouble like this.This is the first time i face this problem when i installed 4.3 version. Any idea y is that happening except from the reply u gave me.

sameer wrote:

hi, thanks for the response, i high appreciated ur help.

I wanted to ask if there are bad blocks why do other version of roms like 2.5,2.6 work excellently there is no trouble like this.This is the first time i face this problem when i installed 4.3 version. Any idea y is that happening except from the reply u gave me.

An interesting question.. A bad block could be anywhere in NAND memory. It may have been flagged bad or if could be new and unknown. If we are installing a ROM and a bad block is accessed in the system partition the results will be simply unpredictable. The read or write could fail or a totally invalid instruction could be attempted.

Why would it surface while installing a new ROM? One of the reasons is the size of the new ROM or system apps - the old one may have luckily skipped over the bad spot or more likely, it didn't use space as far, having been smaller. There is also less working space with a new, larger ROM and yet less if the bad blocks need to be navigated around.

The are not the only possibilities but they are the more likely answers.

NYLimited wrote:
An interesting question.. A bad block could be anywhere in NAND memory. It may have been flagged bad or if could be new and unknown. If we are installing a ROM and a bad block is accessed in the system partition the results will be simply unpredictable. The read or write could fail or a totally invalid instruction could be attempted.

Why would it surface while installing a new ROM? One of the reasons is the size of the new ROM or system apps - the old one may have luckily skipped over the bad spot or more likely, it didn't use space as far, having been smaller. There is also less working space with a new, larger ROM and yet less if the bad blocks need to be navigated around.

The are not the only possibilities but they are the more likely answers.

hi i did some research and found out something.please have a look at it and tell me.

Log Report Before =ad recovery->wipe data/factory reset

Code: Select all

http://speedy.sh/U8gBV/recovery.log

After Wipe data/Factory rest

Code: Select all

http://speedy.sh/Tys6R/recovery1.log

Hope i get some good advice..thanks sameer

sameer wrote:
hi i did some research and found out something.please have a look at it and tell me.

Log Report Before =ad recovery->wipe data/factory reset

Code: Select all

http://speedy.sh/U8gBV/recovery.log

After Wipe data/Factory rest

Code: Select all

http://speedy.sh/Tys6R/recovery1.log

Hope i get some good advice..thanks sameer

Not sure what the question is.. In any event, your device definitely has some bad blocks so increasing the system partition size is more than likely required:

Code: Select all

Formatting /data...
mtd: erase failure at 0x03640000
mtd: not erasing bad block at 0x0af40000
mtd: not erasing bad block at 0x0af60000
mtd: not erasing bad block at 0x0d640000
mtd: not erasing bad block at 0x1c500000

These blocks are showing up in the /data partition but I do not see a format of the /system partition in your log so we simply don't know what may be there. The HD2 is manufactured with 2 different NAND-Flash ROM chipset types. You can determine the type used in yours while in the 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 a year or so use the Samsung chipset usually has a dozen bad clusters, maybe more. Hynix normally has none of them or just a couple.



The other problem showing in the log is the fact that you do not have an sd-ext partition.

Code: Select all

mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
Formatting /sd-ext...
I:Formatting unknown device.
Skipping format of /sd-ext.

Now, I don't know if you wanted to have one or not but it is required if you want to use the DataOnEXT installation method. If you need help creating and formatting the ext4 partition take a look at this post. You can use Minitool or Paragon or a number of other programs, many linked in my thread for you.

Hi Tytung, how do I set the wifi region code in this rom, can't find it?

regards

Lirff

lirff wrote:Hi Tytung, how do I set the wifi region code in this rom, can't find it?

regards

Lirff

Go to Settings->Wi-Fi then click the three vertical dots in the lower right corner. Then select Advanced and the Wi-Fi region code will be on the next menu.

Hi,

I Changed my SD Card and used a spare one i had, tried installing the 4.2 version installation successfully stable no problem used for a day

I tried to install 4.3 freshly,after installation completed and it took me to choose a language selection for your phone when i chose english it took me back to cynogen mod loading for some hours,Don't know y?

After ad hard reset i restarted my phone and i saw the phone successful opened. till that time it works well but it freezes on lock screen until i press call button and wait for it to respond.

any idea y it freezes?

I wanted to know also how do u get bad blocks or how to avoid getting bad blocks?

you help is really appreciated,

thanks,sameer

NYLimited wrote:
Not sure what the question is.. In any event, your device definitely has some bad blocks so increasing the system partition size is more than likely required:

Code: Select all

Formatting /data...
mtd: erase failure at 0x03640000
mtd: not erasing bad block at 0x0af40000
mtd: not erasing bad block at 0x0af60000
mtd: not erasing bad block at 0x0d640000
mtd: not erasing bad block at 0x1c500000

These blocks are showing up in the /data partition but I do not see a format of the /system partition in your log so we simply don't know what may be there. The HD2 is manufactured with 2 different NAND-Flash ROM chipset types. You can determine the type used in yours while in the 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 a year or so use the Samsung chipset usually has a dozen bad clusters, maybe more. Hynix normally has none of them or just a couple.



The other problem showing in the log is the fact that you do not have an sd-ext partition.

Code: Select all

mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
Formatting /sd-ext...
I:Formatting unknown device.
Skipping format of /sd-ext.

Now, I don't know if you wanted to have one or not but it is required if you want to use the DataOnEXT installation method. If you need help creating and formatting the ext4 partition take a look at this post. You can use Minitool or Paragon or a number of other programs, many linked in my thread for you.

hi, Brother,

I checked and found i have PB81120 HX-B3

Hi Tytung,

Thanks and congratulations for your works on HD2.

I Installed this ROM and most of thing are OK. I'm face to two concerns , Bluetooth with my PC and viewing mp4/youtube V5 on HD2.

Bluetooth : my PC first recognizes and adds this "nexus HD2", but at the end of the process it says : "device driver not installed" and then no way to send files from HD2 to PC.

MP4 : Cannot read MP4 files. Neither with youtube last update V5, nor youtube V 4. And, when I'm on youtube site, with V5, could not read anything clip. Unisntall V5 and install V4, it's fine.


Any idea to fix these issues?

Thanks a lot.