NexusHD2 Android Forum

I experience very strange behavior on first start up of this ROM!
I installed using NAND method using clock work reocvery V1.3.
I made sure I copied the partition table into the flash.cfg of the clockwork recovery flasher tool before flashing clockwork recovery.
I am running a Telstra HTC HD2 (I'm in Australia) which happens to have the 1024MB NAND chip.
I then booted into clockwork mod recovery from aMAGLDR and used clockwork recovery to transfer the ROM zip from my laptop to the root of the blank SD card which I formatted to FAT32 format using Debian Linux on a different machine.
Once the ROM was transferred, I used clockwork recovery's install from sdcard zip function to install the ROM.
The installation went very smoothly, but on start up after the green htc logo, I would just get a lit up blank screen, the hard buttons would light up if I pressed one of them, but no CyanogenMod animated logo. It would not even respond to the reset button at the back of the phone!
So I redid the installation, this time doing a custom install with all the boxes unchecked
This time I got the CyanogenMod logo, and the phone started up and got to the set up screen, but everything would keep crashing! Something like android com core, trebuchet, Google Services, etc... I could not even skip past the WiFi screen, I would simply return to it after going past the Google location tick boxes.
So I restarted the phone, and it would just stay on the CyanogenMod animated logo.
Restarted again, taking the SD card out in case that would make a difference. But it seems to still be stuck on the CyanogenMod animated logo.
Any hint to what the solution might be? I don't really want to try data on EXT4 SD card method as I want to use the 32gb sd card for my helmet cam.

Kernel wrote:I experience very strange behavior on first start up of this ROM!
I installed using NAND method using clock work reocvery V1.3.
I made sure I copied the partition table into the flash.cfg of the clockwork recovery flasher tool before flashing clockwork recovery.
I am running a Telstra HTC HD2 (I'm in Australia) which happens to have the 1024MB NAND chip.
I then booted into clockwork mod recovery from aMAGLDR and used clockwork recovery to transfer the ROM zip from my laptop to the root of the blank SD card which I formatted to FAT32 format using Debian Linux on a different machine.
Once the ROM was transferred, I used clockwork recovery's install from sdcard zip function to install the ROM.
The installation went very smoothly, but on start up after the green htc logo, I would just get a lit up blank screen, the hard buttons would light up if I pressed one of them, but no CyanogenMod animated logo. It would not even respond to the reset button at the back of the phone!
So I redid the installation, this time doing a custom install with all the boxes unchecked
This time I got the CyanogenMod logo, and the phone started up and got to the set up screen, but everything would keep crashing! Something like android com core, trebuchet, Google Services, etc... I could not even skip past the WiFi screen, I would simply return to it after going past the Google location tick boxes.
So I restarted the phone, and it would just stay on the CyanogenMod animated logo.
Restarted again, taking the SD card out in case that would make a difference. But it seems to still be stuck on the CyanogenMod animated logo.
Any hint to what the solution might be? I don't really want to try data on EXT4 SD card method as I want to use the 32gb sd card for my helmet cam.

A couple of probabilities come to mind.

First, have you confirmed that the zip file on your card is not corrupt? Copying files over USB to the card has been known to create file corruption at times. You should confirm the file's md5 or simply move the card to a reader connected directly to your computer and copy the file there.

Second, please check your nand memory for bad blocks. If the device has bad blocks some parts of the installation could have become damaged during the install process. You may also have created a system partition which is too small, inadvertently or due to bad blocks. Try increasing the system partition size and reinstalling from a known good zip file. If it fails to boot, increase the partition size again by a nominal amount.

Although other problems may also create your symptoms these are the two more likely probabilities.



---
Any clod can have the facts, but having an opinion is an art.

NYLimited wrote:
A couple of probabilities come to mind.

First, have you confirmed that the zip file on your card is not corrupt? Copying files over USB to the card has been known to create file corruption at times. You should confirm the file's md5 or simply move the card to a reader connected directly to your computer and copy the file there.

Second, please check your nand memory for bad blocks. If the device has bad blocks some parts of the installation could have become damaged during the install process. You may also have created a system partition which is too small, inadvertently or due to bad blocks. Try increasing the system partition size and reinstalling from a known good zip file. If it fails to boot, increase the partition size again by a nominal amount.

Although other problems may also create your symptoms these are the two more likely probabilities.



---
Any clod can have the facts, but having an opinion is an art.

Maybe but I just installed the HD2 Xperia Z rom without a hitch and it's working just fine though not as quick as tytung's roms.
I think it's most likely that I have a corrupt download from the crappy download website it's hosted on, maybe if someone can do a direct connection transfer to me via IRC or something, that would be great, as I would like my phone to be fast and smooth.
There's no easy way of checking for bad blocks on the NAND chip from aMAGLDR so I may just install LC Black or whatever it's called which has the functionality inbuilt, unless you can suggest of an out-of-the-box utility I could use.

Good day!
I am russian-language user, so the quality of English do not abuse)

use your firmware for a long time, better than them no one has devised, thank you for your work!
There is only one negative - the maximum volume of the earpiece in an outgoing call, and this applies to all firmware gathered at your core. Can anything be done about it?


with respect, Stanislav

Kernel wrote:Maybe but I just installed the HD2 Xperia Z rom without a hitch and it's working just fine though not as quick as tytung's roms.
I think it's most likely that I have a corrupt download from the crappy download website it's hosted on, maybe if someone can do a direct connection transfer to me via IRC or something, that would be great, as I would like my phone to be fast and smooth.
There's no easy way of checking for bad blocks on the NAND chip from aMAGLDR so I may just install LC Black or whatever it's called which has the functionality inbuilt, unless you can suggest of an out-of-the-box utility I could use.

If the download is corrupt you should really be able to tell by the published md5.

There are simple ways to check for bad blocks which I and others have documented numerous times. Even easier is to try a larger system partition as already suggested.

It seems to me that you are a tad bit too busy to use search and find your answers. Fortunately for me my device is already fine so I will stop this nonsense. Perhaps we shall continue when you have more time and you don't wish me to do your research for you.


---
Any clod can have the facts, but having an opinion is an art.

Kernel wrote:Maybe but I just installed the HD2 Xperia Z rom without a hitch and it's working just fine though not as quick as tytung's roms.
I think it's most likely that I have a corrupt download from the crappy download website it's hosted on, maybe if someone can do a direct connection transfer to me via IRC or something, that would be great, as I would like my phone to be fast and smooth.
There's no easy way of checking for bad blocks on the NAND chip from aMAGLDR so I may just install LC Black or whatever it's called which has the functionality inbuilt, unless you can suggest of an out-of-the-box utility I could use.

1.Xperia Z rom is based on tytung's rom AFAIK, so should be similar speed, ymmv.
2.Use "hashcalc" or similar on pc, or some recoveries can do it too, to calculate md5sum of your download, and check with that in tytung's first post in the rom thread, simple and no need to re-download if it is the same.
3.From running rom, reboot phone to magldr menu (do not pull battery, power off or use reset button under battery cover), choose 10.services then 2.dmesg to sd, look on sdcard for dmesg.txt file, look in it for bad block messages. So it can be done easily from magldr. dmesg.txt is also useful to post sometimes for devs to debug their kernels/roms
There you go, saved you a little bit of research, now you can hopefully enjoy the rom.

stas_symba wrote:Good day!
I am russian-language user, so the quality of English do not abuse)

use your firmware for a long time, better than them no one has devised, thank you for your work!
There is only one negative - the maximum volume of the earpiece in an outgoing call, and this applies to all firmware gathered at your core. Can anything be done about it?


with respect, Stanislav

Yeah, I know what you're talking about. Out going or incoming call volume is sometimes very low through the earpiece, but this has been the case with every Android ROM for the HD2 I've tried. Even the default Windows ROM had poor in-call volume. With older ROMs before ICS there were apps available at the market that helped to resolve this, and with Windows there were several registry hacks that helped. Unfortunately, Ice Cream Sandwich changed some of the underlying code which allowed the apps from the Market to work. So I personally don't know of a current solution.

What I do as a workaround is place the call on speaker and turn the volume down when I can't hear clearly through the earpiece. It's not an ideal solution, but since low volume only affect some of my calls, I live with it. Sorry I couldn't help more. Maybe someone else has a better solution.

Ciao

Hi:

is anyone able to fix permissions with this ROM?

I can't get it to work, neither calling it from RomManager, nor from Recovery.
(And yes, I did assign SU to RomManager. SU works fine in Titanium Backup.)

Any ideas? -- Thank you!

malkovich wrote:Hi:

is anyone able to fix permissions with this ROM?

I can't get it to work, neither calling it from RomManager, nor from Recovery.
(And yes, I did assign SU to RomManager. SU works fine in Titanium Backup.)

Any ideas? -- Thank you!

I don't use ROM Manager so I cannot help you there.

Which install option did you select? If you used DataOnEXT the only recovery that will help you (as far as I know) is TWRP Extended since none of the others would know where your /data partition is located.

You might also want to try ROM Toolbox and like utilities which may help.

Kernel wrote:I experience very strange behavior on first start up of this ROM!
I installed using NAND method using clock work reocvery V1.3.
I made sure I copied the partition table into the flash.cfg of the clockwork recovery flasher tool before flashing clockwork recovery.
I am running a Telstra HTC HD2 (I'm in Australia) which happens to have the 1024MB NAND chip.
I then booted into clockwork mod recovery from aMAGLDR and used clockwork recovery to transfer the ROM zip from my laptop to the root of the blank SD card which I formatted to FAT32 format using Debian Linux on a different machine.
Once the ROM was transferred, I used clockwork recovery's install from sdcard zip function to install the ROM.
The installation went very smoothly, but on start up after the green htc logo, I would just get a lit up blank screen, the hard buttons would light up if I pressed one of them, but no CyanogenMod animated logo. It would not even respond to the reset button at the back of the phone!
So I redid the installation, this time doing a custom install with all the boxes unchecked
This time I got the CyanogenMod logo, and the phone started up and got to the set up screen, but everything would keep crashing! Something like android com core, trebuchet, Google Services, etc... I could not even skip past the WiFi screen, I would simply return to it after going past the Google location tick boxes.
So I restarted the phone, and it would just stay on the CyanogenMod animated logo.
Restarted again, taking the SD card out in case that would make a difference. But it seems to still be stuck on the CyanogenMod animated logo.
Any hint to what the solution might be? I don't really want to try data on EXT4 SD card method as I want to use the 32gb sd card for my helmet cam.

I think NYLimited was on the right track. It sounds like you have a corrupted download or there's a problem with your NAND. Either you have bad blocks getting in the way or your system partition is too small which would be the case if there were several bad blocks residing there. Follow the bad block tutorial symbuzzer wrote here how-to-mark-your-bad-nand-blocks-t48.html and see if this helps. I personally have over 2 dozen bad blocks on my NAND, which is why I'm using a data-on-ext install.

Good luck