[Q&A]HTC HD2 Help thread

1. Think a help thread is needed? 2. Would you support/participate? 3. Add anything?

  • 1: Oh yes!

    Votes: 18 94.7%
  • 1: Oh hell no!

    Votes: 0 0.0%
  • 2: Yes - PMing you now!

    Votes: 3 15.8%
  • 2: I'd rather see how it goes first

    Votes: 3 15.8%
  • 2: Not likely

    Votes: 0 0.0%
  • 3: Nope - it's good how it is!

    Votes: 3 15.8%
  • 3: Yeah - suggestions in new post please

    Votes: 2 10.5%

  • Total voters
    19
Search This thread

lukes91

Senior Member
Aug 20, 2013
2,052
1,217
32
Somewhere Over The Rainbow
i would like to help too :)
i've tried many hd2 android roms, but i've never developed one...
i've also helped some users in other threads...
moreover my hd2 is not my "main" phone, so i can try different configurations if required :)
 
  • Like
Reactions: Kandyegirl

Photoelectric

Senior Member
Sep 21, 2011
92
5
It could be bad blocks causing Photoelectric's problems, it would be good to find out where they are in nand and increasing the size of the partition they reside in.
if using clk see second post here http://xdaforums.com/showthread.php?t=2279582
if using mgldr, after switching off android, go to magldr menu/services/dmesg to sd and look at file dmesg.txt on sdcard. Somewhere in there there may be reference to bad blocks and what partition they are in, post dmesg.txt here if in doubt.

Thank you very much. Here's a relevant portion of the log up to the installation of the new ROM. Looks like this phone has some bad blocks. The other phone must be worse off. The current partition is 350M in size, I believe.

Starting recovery on Thu Feb 27 21:13:46 2014
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v3.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot yaffs2 boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery yaffs2 recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext auto /dev/block/mmcblk0p2 (null)

I:Completed outputting fstab.
I:processing arguments.
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=FRF91
ro.build.display.id=GRH78
ro.build.version.incremental=eng.aaron.20110107.002533
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.1
ro.build.date=Fri Jan 7 00:26:07 GMT 2011
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=aaron
ro.build.host=aaron-iMac
ro.build.tags=release-keys
ro.product.model=HTC Desire
ro.product.brand=htc_wwe
ro.product.name=htc_bravo
ro.product.device=bravo
ro.product.board=bravo
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=bravo
ro.build.description=2.10.405.2 CL226611 release-keys
ro.build.fingerprint=htc_wwe/htc_bravo/bravo/bravo:2.2/FRF91/226611:user/release-keys
ro.sf.lcd_density=240
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.ecc.HTC-WWE=999
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=5
ro.ril.hsxpa=2
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.telephony.default_network=0
ro.ril.enable.prl.recognition=1
ro.ril.def.agps.mode=2
ro.opengles.version=131072
dalvik.vm.heapsize=32m
ro.media.dec.jpeg.memcap=20000000
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=DonMessWivIt.ogg
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,113,115,117,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
ro.modversion=CyanogenMod-7.0.0-RC0-Desire-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=htcleo
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at 0
I:Set boot command ""

-- Wiping data...
Formatting /data...
mtd: erase failure at 0x00e80000
mtd: not erasing bad block at 0x04440000
mtd: erase failure at 0x0be20000
mtd: erase failure at 0x185c0000
mtd: erase failure at 0x1a960000
mtd: erase failure at 0x1b300000
Formatting /cache...
Formatting /sd-ext...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
mtd: successfully wrote block at 0
I:Set boot command ""

-- Wiping cache...
Formatting /cache...
Cache wipe complete.
mtd: successfully wrote block at 0
I:Set boot command ""
rm: can't remove '/data/dalvik-cache': No such file or directory
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
mtd: successfully wrote block at 0
I:Set boot command ""

-- Installing: /sdcard/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip
Opening update package...
Installing update...
about to run program [/sbin/umount] with 2 args
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/erase_image] with 2 args

====================
DARKSIDE.SUPER.WIPE
SGSII SGH-T989
====================

..A DARKSIDE DEVELOPMENT..

[*] Preparing Device...

[*] Running DARKSIDE.SUPER.WIPE...
> Wiping SYSTEM partition
mtd: erase failure at 0x0b8e0000
mtd: erase failure at 0x0c160000
mtd: not erasing bad block at 0x0e300000
Need size of filesystem
format: make_ext4fs failed (1) on /dev/block/mmcblk0p24about to run program [/sbin/umount] with 2 args
> Wiping DATA partitionumount: can't umount /data: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/erase_image] with 2 args

mtd: erase failure at 0x00e80000
mtd: not erasing bad block at 0x04440000
mtd: erase failure at 0x0be20000
mtd: erase failure at 0x185c0000
mtd: erase failure at 0x1a960000
mtd: erase failure at 0x1b300000
Need size of filesystem
format: make_ext4fs failed (1) on /dev/block/mmcblk0p25about to run program [/sbin/umount] with 2 args
> Wiping CACHE partitionabout to run program [/sbin/erase_image] with 2 args

Need size of filesystem
format: make_ext4fs failed (1) on /dev/block/mmcblk0p26> Aligning disksminzip: Extracted file "/tmp/superwipe/e2fsck"
minzip: Extracted file "/tmp/superwipe/mkfs.ext4"
minzip: Extracted file "/tmp/superwipe/superwipe.sh"

minzip: Extracted file "/tmp/superwipe/tune2fs"
minzip: Extracted file "/tmp/superwipe/wipe.sh"
about to run program [/tmp/superwipe/superwipe.sh] with 1 args
umount: can't umount /system: Invalid argument
umount: can't umount /data: Invalid argument
umount: can't umount /cache: Invalid argument
mke2fs 1.41.14 (22-Dec-2010)
mkfs.ext4: No such file or directory while trying to determine filesystem size
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p24
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p24
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p24
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: need terminal for interactive repairs
e2fsck 1.41.14 (22-Dec-2010)
/tmp/superwipe/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p24
Possibly non-existent device?
mke2fs 1.41.14 (22-Dec-2010)
mkfs.ext4: No such file or directory while trying to determine filesystem size
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p25
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p25
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p25
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: need terminal for interactive repairs
e2fsck 1.41.14 (22-Dec-2010)
/tmp/superwipe/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p25
Possibly non-existent device?
mke2fs 1.41.14 (22-Dec-2010)
mkfs.ext4: No such file or directory while trying to determine filesystem size
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p26
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p26
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
/tmp/superwipe/tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p26
Couldn't find valid filesystem superblock.
tune2fs 1.41.14 (22-Dec-2010)
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: need terminal for interactive repairs
e2fsck 1.41.14 (22-Dec-2010)
/tmp/superwipe/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p26
Possibly non-existent device?
about to run program [/sbin/e2fsck] with 3 args
> Checking filesystems/sbin/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p24
/dev/block/mmcblk0p24:
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>

run_program: child exited with status 8
about to run program [/sbin/e2fsck] with 3 args
/sbin/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p25
/dev/block/mmcblk0p25:
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>

run_program: child exited with status 8
about to run program [/sbin/e2fsck] with 3 args
/sbin/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p26
/dev/block/mmcblk0p26:
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>

run_program: child exited with status 8
about to run program [/sbin/busybox] with 4 args
script result was [0.000000]

[*] Cleaning leftovers...

Done!

:: DARKSIDE ::

Install from sdcard complete.
mtd: successfully wrote block at 0
I:Set boot command ""
mtd: successfully wrote block at 0
I:Set boot command ""

-- Installing: /sdcard/HD2_NDT_MIUI_GINGER_2.3.7_STABLE_V6.0_MAGLDR.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/HD2_NDT_MIUI_GINGER_2.3.7_STABLE_V6.0_MAGLDR.zip
Opening update package...
Installing update...

The latest I've read is that I should try adding an EXT4 partition to my SD card for swap / app data to help with stability?
 
Last edited:

Robbie P

Senior Member
Feb 8, 2011
5,116
4,017
London
Thank you very much. Here's a relevant portion of the log up to the installation of the new ROM. Looks like this phone has some bad blocks. The other phone must be worse off. The current partition is 350M in size, I believe.


The latest I've read is that I should try adding an EXT4 partition to my SD card for swap / app data to help with stability?

Not sure that ext4 will help with the rom you are using (i think it is this one http://xdaforums.com/showthread.php?t=1013852), and am confused as to why you would need 350Mb system partition for a gingerbread rom (OP says minimum 150Mb so i suggest 160Mb is ok)
Also, i think you posted the recovery log, not the dmesg.txt, but it does show bad blocks in system and in data partitions.
I assume you are using magldr, try getting the dmesg as i mentioned earlier.
 
  • Like
Reactions: Photoelectric

Photoelectric

Senior Member
Sep 21, 2011
92
5
Oops, just looked at dmsg. 4 bad blocks on this "worse" phone.

The larger partition size was from testing other ROMs in the past, 4.0+. I'm going to try a Cyanogen 4.4 ROM now, which was relatively smooth and stable on the other phone for a while--that one supports Ext4 and Swap partitions.
 
  • Like
Reactions: Robbie P

Robbie P

Senior Member
Feb 8, 2011
5,116
4,017
London
What is the best course of action here? I'm thinking complete wipe and reinstall of everything from scratch. Does that mean I need to reflash HSPL and start from there? It's been a while since I've done that, so I'm trying to remember all the steps. Any general suggestions or ideas about what might be causing the increasingly aberrant behavior?
I would be wary of reflashing HSPL for now
first thing is to find and possibly mark your bad blocks, and adjust sizes of partitions.
Or try NativeSD/DataonEXT as you suggested with an ext4 sdcard partition.
Good luck
 
  • Like
Reactions: Photoelectric

Photoelectric

Senior Member
Sep 21, 2011
92
5
I would be wary of reflashing HSPL for now
first thing is to find and possibly mark your bad blocks, and adjust sizes of partitions.
Or try NativeSD/DataonEXT as you suggested with an ext4 sdcard partition.
Good luck

I have the block numbers, but how does one mark and not use them? From what I've read so far, only Windows installation removes bad blocks from use--not current Android installations.
 

Robbie P

Senior Member
Feb 8, 2011
5,116
4,017
London
I have the block numbers, but how does one mark and not use them? From what I've read so far, only Windows installation removes bad blocks from use--not current Android installations.
I admit i am a bit confused by this, I thought android dealt with bad blocks. Will have to read up on it again, tomorrow;)
Goodnight Photoelectric, and happy flashing.:)
 
  • Like
Reactions: Photoelectric

Photoelectric

Senior Member
Sep 21, 2011
92
5
I admit i am a bit confused by this, I thought android dealt with bad blocks. Will have to read up on it again, tomorrow;)
Goodnight Photoelectric, and happy flashing.:)

Just what I've read here:

http://xdaforums.com/showpost.php?p=25284969&postcount=285

I've done a task 29 and reflashed a 350M/45M Magldr recovery partition--the bad blocks are still all present and have the same numbers after installing a Cyanogen ROM now with data on EXT4. Hopefully I don't have to move entirely to SD.
 

hitman1376

Senior Member
Jan 7, 2013
667
432
26
zanjan
Well ...

Thank you for this thread.

I own and maintain 2 HTC HD2s (T-Mo edition), and both have been using custom Android NAND-based ROMs ever since I got the phones. The issue is that with time, there are more and more random bugs and reboots. Like a ROM suddenly crashing and rebooting, and upon reboot some programs are missing (needs a reboot or a reboot + Dalvik clear to fix), or other strange stuff happens such as available internal memory suddenly jumps to zero (that one only happened once). I feel like despite my best attempts to do clean installs, something's been accumulating and messing things up.

For reference, I have been using SuperWipe as of late, but while it does free up more internal space, it still does not help. My go-to ROM has been Gingerbread MIUI, which has been smooth and stable, but even with that ROM my phones have been crashing a lot lately and exhibiting various bad behavior. I've tried Gingerbread ROMs as well as 4.0, 4.1, 4.2, and 4.4 variants so far over time and have changed internal partition sizes accordingly.

What is the best course of action here? I'm thinking complete wipe and reinstall of everything from scratch. Does that mean I need to reflash HSPL and start from there? It's been a while since I've done that, so I'm trying to remember all the steps. Any general suggestions or ideas about what might be causing the increasingly aberrant behavior?
My Dear friend ... I'm not an expert ... but as I know this thread's first post can help you ( He is an expert :laugh: ) ... Exactly the things you said ( Bootloops - random reboots ,... ) ... So good luck ...


With Best Wishes
Hitman1376​
 

Robbie P

Senior Member
Feb 8, 2011
5,116
4,017
London
I'm not really experienced in the HD2, but isn't there a way to wipe everything like in fastboot using "fastboot wipe" commands?

won't that fix it? I'm just guessing here though

Sent from my Nexus 4

It won't fix bad nand blocks, those mothers are bad to the bone.;)


Task 29, superwipe etc won't fix either. Some people never do a task 29, tytung for instance never has. -pixelfreak- advises using superwipe. It is sometimes difficult to know what to do.
 
  • Like
Reactions: Photoelectric

Photoelectric

Senior Member
Sep 21, 2011
92
5
It won't fix bad nand blocks, those mothers are bad to the bone.;)


Task 29, superwipe etc won't fix either. Some people never do a task 29, tytung for instance never has. -pixelfreak- advises using superwipe. It is sometimes difficult to know what to do.

I believe those are just to clean up any residual "stuff" that doesn't get deleted and can interfere with new installations. I've only done Task 29 to reinstall Magldr. Superwipe does clean more than manual deleting of Data/Cache/Dalvik Cache before installing a ROM--the numbers prove it, so I do use Superwipe.

In any event, my current install on the "worse" phone has been holding up very well since yesterday, though it's a short time frame. I've done a fresh 350M/45M partition in Magldr (via HD2 toolkit) and put on a Cyanogen ROM with data on EXT4 and the rest on NAND. Amazingly no errors of applications crashing so far, which is usually pretty uncommon--at least *something* suddenly stops after installation. The bad blocks are all still there, of course, but either re-partitioning or moving data to EXT4 seems to be helping at least a bit.
----

UPDATE: still trouble :( After a reboot, error messages from Google Play Services. Reboot into recovery, wipe Dalvik Cache-> everything resets completely and I have the "internal memory is full" error :( Now I'm trying to figure out how to make 2 EXT4 partitions to work on my SD card for DirectSD ROM installation, as partitioning on my computer does not make the second EXT4 visible to the phone. Trying this: http://xdaforums.com/showthread.php?p=47615553
but unsuccessfully (can't install 4EXT4 Recovery yet, been trying to).
 
Last edited:
  • Like
Reactions: Robbie P

lukes91

Senior Member
Aug 20, 2013
2,052
1,217
32
Somewhere Over The Rainbow
Now I'm trying to figure out how to make 2 EXT4 partitions to work on my SD card for DirectSD ROM installation, as partitioning on my computer does not make the second EXT4 visible to the phone.

i recently created 2 ext4 sd partitions with this tool and worked fine, both coumputer and phone saw them... give it a try if you are on windows :)
 
  • Like
Reactions: Photoelectric

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    HTC HD2 Help Thread


    Welcome to the HTC HD2 help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and will provide answers as soon as possible. For the list of supporters, see here;

    List of Supporters

    Robbie P (RC) All round knowledge of phone
    rirozizo (RC) Android battery guru & all-around-android guy
    kuzibri (RC) All round, Android and WM
    gilbert32 (SM) All round guru, Android and WM. HD24Ever team member
    lukes91 (SM) Experienced Android user
    hitman1376 (SM) Experienced Android user
    lolerpro8 (SM) Experienced Android user
    ...​
    <device> Help Thread


    Please read the FAQ found (here, insert FAQ link), before asking any questions.
    It is quite possible your question may have already been answered

    Welcome to the <device> help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and provide answers as soon as possible. To see a list of supporters, see here

    List of supporters
    ...
    ...
    ...​


    To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligable of posting there, you may post here. Thank you!

    Supporters:If you want to be put on or off the list, just make a request here in the thread!

    ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligable for posting in development section.

    To all of you: Remember the Rules and the Forum Etiquette
    3
    Useful links etc.

    NYLimited's info thread All about SDcards
    LNE Team's NativeSD for (new) WM users
    ksubedi's (and bzdemes') HD2 NAND toolkit
    gilbert32's guide to flashing android on "hopeless"devices

    More later, if you have any suggestions for this list, feel free to post them:)
    3
    nice idea, will be supporting all around this thread...

    also, this post will be reserved for something possibly useful :p
    3
    Hi my dear friend,

    Very good initiative!! see your PM box, I'm in!!:good:

    kindest regards, Kuzibri
    3
    @lukes91 and @hitman1376 welcome to the HD2 Supporters club, and thanks for your support. If you want your messages-next-to-names changed, feel free to post them here.
    We now have more supporters than questions;):D, though that may change soon.:fingers-crossed: