Database Users

BA Disconnects as Update Starts

Hi,
Apologies in advance if I'm covering old ground.
I'm trying to re-flash a WM6 rom after my previous attempt just left me with the 4 colour screen permanently and as the links to mtty1.42.rar seem to be broken at the moment I decided to re-flash with a different rom.
the problem is that even though I can get the unit into boot-loader mode and the update software appears to see the BA when it checks versions etc. as soon as I hit the upgrade button the BA screen blanks and I get Error 112: CE ROM UPDATE ERROR.
I've tried different roms, different usb ports and different versions of activesync all with the same result.
Any help on this would be great and hopefully I haven't 'bricked' the unit.
Cheers
Duncan

Do you have PH20A2 or PH20B device?
mtty utility can be found using search button

It's a PH20B.
I've now found mtty after a fair bit of searching on other forums..now to see if I can make some sense of it's commands.
A further update: it seems that I've managed to corrupt just the OS part of the ROM. I managed a radio update successfully which means all the USB connection is fine for updating. It just can't access the OS part of the ROM.
Is there anyway to manually format that area of ROM so I can in effect install over clean unit? Infortunately I can't make sense of the mtty commands and don't know what memory address and for how log I should perform the format.
Cheers Duncan

try reflashing

You should know how to use search - however here is the link
http://forum.xda-developers.com/showthread.php?t=348030&highlight=mtty
(Is that hard to put "mtty" in the search field and set BA section only? )

Further update:
Now I don't even get the 4 colour screen. After soft and hard reset I get a dead device. I can put the device into bootloader mode (serial/usb) but as soon as the update software attempts to copy the rom across the screen blanks and I get the ROM Update Error.
Now my thought is to try and flash with the original rom for the device as I have another unit available but using the link from the BA wiki for dumping the ROM doesn't work. I have also tried searching for 'ROM Dump' within the BA section of the forum but there don't seem to be any definitive instructions for this, everyone just keeps asking why not use the wiki or search funtion....
I have used the wiki and the search funstion and I seem to be the first with this situation.
Soft Reset - Nothing
Hard Reset - Nothing
Bootloader - Able to flash the radio rom but as sson as i try to flash the OS rom the screen blanks and I get Error 112: CE ROM Update Error. When I take the device out of the cradle the screen comes back on with the Serial 2.xx screen and I'm back to square one.
I've tried to use the wiki to dump an exisiting working rom but the link on the wiki is broken. I have also searched the BA forum for these intructions but they're not covered as they're already in the wiki..... or not as the case is.
I appreciate you regular users get fed up with noobs coming on and expexting you to do all the work for them but so far I've spent 3 days searching both this site and others to try and resurect my device. I'm not dumb or lazy and would love to be able to do all this myself but without instructions I'm flying somewhat blind.
Any help would be great..... please??

[off topic]
no need for apologies...
we started once like you... some are far worse...
knowing one part and boasting with air on their heads...
since you managed to explain yourself on your first post.
knowing what to search (E.G. MTTY 1.42.rar)
you definitely searched the forum before you posted AND
you stated that the links are not working... that proves it.
we are the one who is sorry because some others think
that they are high and mighty, it sometimes blurs the opinion making.
i dont like opinionated people because i admit that am one too... sometimes...
but that doesnt mean i hate them...
[on-topic]
you never told us what happened when you tried the mtty procedure.
is your last post the result of your mtty experience?
please elaborate how did you end up with that... what did you do before you soft-reset and hard-reset?

SilverSamurai,
Thanks for the quick response.
After my last 'apparently' successful re-flash with Helmi's latest WM6 rom when I hard reset the device I had nothing but a blank black screen, no power LED or anything. Soft-reset was the same. I can reset into bootloader and the PC detects the device when I place it in the cradle. The first part of the update seems to work although it never detects the current OS installed, it always says upgrade from ' ' to 'ver 6.0.0' which is wierd because it always used to say the previous OS version. When I then hit next the progress bar shows on the PC but the BA screen immediately blanks and eventually the PC gives the ROM update error.
I have managed to re-flash the radio rom in this state which proved that I still have access tho the device from the PC.
Using mtty I can run through all the commands to recover from the 4 colour lines screen (even though I'm beyond that point).
USB>set 14 0
HTCST ÚÈÒHTCEUSB>task 28
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
USB>
It's almost as if the last flash didn't complete and has left the area for the OS 'dirty' with what ever it did manage to flash. What I was hoping to try was to re-format the entire OS section of memory and then try to re-flash again. Using mtty it says you can format sections of memory by stating a start address and the length you want to format but I don't have clue what these should be.
I've tried flashing with WM6, WM5 and a compatible version of 2003 with the same result every time. I would like to dump a rom from another BA I have and try with that but as mentioned earlier the link for that is down at the moment.
I think that's about it. If you need any more info let me know.
Many thanks
Duncan.

let's relist the things you did.
USB>set 14 0
Click to expand...
Click to collapse
1. start OS after a reset
result:
HTCST ÚÈÒHTCE
USB>task 28
Click to expand...
Click to collapse
2. format doc (Disc-On-Chip)
result:
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
Click to expand...
Click to collapse
3. do hardware clear boot.
Click to expand...
Click to collapse
since i dont want to experiment with my sole BA...
i tried to search for solution...
and with some of my computer instincts i came up with this suggestion...
try this command before "task 28"
"task 7 0" <-- this is the "Do flash ROM lock/unlock" command
"task 2a" <-- fix bad blocks on MFG bootloader and Storage
then try to reflash your BA.
my sources one | two
although it's not BA but i think mtty commands are generic.
it's worth a try.

SS,
Still no joy, it's exactly as it was before.
Just reading through some more posts for bootloader ant it seems at least one other person has the same problem - http://forum.xda-developers.com/showthread.php?t=345181&highlight=bootloader and no resolution posted for that either.
I think I may have got it beyond the point of return.
I've just tried to flash from the blank screen I end up with from the initial attempt and it still detects the device but fails in exactly the same way.

awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains

SilverSamurai said:
awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains
Click to expand...
Click to collapse
These steps are from my notes. Follow these steps. It worked for me last time i tried (3 months back)
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run mtty (from downloaded) Choose WCEUSBSH001
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.

i think he did all of those already,
that's why i posted this in response to his mtty experience.
wouldnt hurt to try it again though.

A bit more info:
I tried the mtty solution again but still the same result.
I finally managed to find the instructions for dumping and exisiting rom to SD card and pulled one from a working unit. I put the card into the faulty BA and booted into bootloader. Pressed 'Power Button' to flash from card and it appeared it was going to work........ until it got to 12% then it failed with the message 'Download Fail'. So still no better off.
What I'm going to try now as it seems anything is worth a try is use the address ranges used to dump the rom to try and format all 3 sections. See if that will give me a clean base to try and re-flash from the sd card. My only worry is if it will format the section of ROM used to store the bootloader info.
I'll post my results shortly.

Now I need to know how to get the bootloader password to enable me to use the 'erase' command through mtty.
The hunt coninues....

Yet more developments.
As the update from SD failed I thought I'd see if it was possible to dump the current contents of the rom to SD using the following
“d2s 80000000 02000000“
“d2s 60000000 00300000 sd a“
“d2s 70000000 01080000 sd a“
The first 2 commands completed fine and checksum was OK. On the 3r command 'd2s 70000000 01080000 sd a' it errored with the following result
USB>d2s 70000000 01080000 sd a
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SDetected one card
SD:ready for transfer OK
pc->drive.total_lba=1E8000
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=B368
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=3D000000
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
DOC_ReadBinary is fail: dwStartAddress=0,dwReadSize=40000.
DOC_ReadBinary is fail: dwStartAddress=0,dwTempReadLength=40000.
*DOC_ReadBinary is fail: dwStartAddress=40000,dwTempReadLength=40000.
*****************************************************************dwCheckSum of Storage=95609D16
cSectionNum=2
psImageSectionInfo[cSectionNum].dwCheckSum=0
psImageSectionInfo[cSectionNum].dwLength=1080000
Stored image of SD/MMC card checksum error!
Now my guess is the Doc_Read_Fail bits are the corrupt part of the rom. If I can find a way to repair these I could then try re-flashing the rom.

what was "task 2a"'s result?
i think that's the chkdsk option of mtty.
we're dissecting the innards of the bootloader.
little by little as we go along the way...
im learning something, i hope you can find the fix for your problem.

SilverSamurai,
Thanks for the help you gave but the unit has finally had enough and totally locked. No power or anything no matter how I try to reset it. I've tried charging for hours, discharging for hours, left the battery out for hours but to no avail. It seemed to take exception to me dumping the rom contents to the SD card. Maybe there was a hardware problem ?? Not sure.
I'll have to see if I can wangle another unit from the company I work for as we're currently selling a bunch that were purchased for a failed IT project on ebay.

it was sad to hear/read that.
anyways. at least we tried to revive it. but dont throw it away.
maybe someday there will be ways how to ressurect your BA.
Happy Computing! err... Mobile Computing!

[Problem] Can´t install anything

I´ve got really big problems now -.- ****ing HD2^^
So here it is:
I used v2.4 as daily and changed for testing to WP7 =) This really worked great but in case of the leak of apps in store I wanted to change back to android, especially to Futurshocks Miui!
So now starts the problems. I formated and partitioned the SD Card ( to fat32 ) and tried to flash the new v3.
It doesn´t work.
Even the clockwork installation don´t work. After now 3 hours of getting freaky, I said to myself, reinstall wp7 ... this works at least -.-
But ... now nothing works!
Clockworks does install, but after that I can´t start it ... always sais "SD Kernel failure"
The Android Build ( every build ) gets a failure while installing, on the htc screen it´s making the partitions -.-
Same happens now if i want to install WP7, it stops while making partitions... theres the failure code "Error Description: flash write failed. Info: .\RSPL\RSPL.cpp (710)"
I am sleepy now, but I NEED A WORKING PHONE TOMORROW and this is **** !
Sry for some words, but actually my HD2 pisses me off"!
PS: MAGLDR 11 or 12 or or or doesn´t change the situation!
Have Vista installed...and run everything as administrator!

Idk much about all this but try downloading wp7 or android on a different sd card
Sent from my HD4.5 using Board Express

ok for now got android working!
I just reinstalled everything you could^^
From task 29, over orig. wm, radio, other wm6.5, mgldr -> android...
but this was the third time I did this steps all!
Oh hell man^^ But anyway for first it works again

Help!! Phone keeps acting possessed!!!

Ok, so i have a friends HD2 right now because she was having issues with it. After using it with the stock OS i immediately found the phone doing random tasks that i didnt initiate. For example, i would be in messages or email and it would just start calling the last dialed number over and over again. Id end the call and it would just start another. It would also just open voice commands without ever even touching the phone.
So i decided it was probably a OS bug or something, so i Installed a custom WINMO ROM and put android on it. It ran great for 2 days and it seemed i had fixed it. WRONG!! The bug is still there! What could be causing this issue?
I thought maybe it was the radio, but i flashed like 4 of them and it is still possessed!!
Anyone have any ideas???
Thanks

JohnnyVolcom5 said:
Ok, so i have a friends HD2 right now because she was having issues with it. After using it with the stock OS i immediately found the phone doing random tasks that i didnt initiate. For example, i would be in messages or email and it would just start calling the last dialed number over and over again. Id end the call and it would just start another. It would also just open voice commands without ever even touching the phone.
So i decided it was probably a OS bug or something, so i Installed a custom WINMO ROM and put android on it. It ran great for 2 days and it seemed i had fixed it. WRONG!! The bug is still there! What could be causing this issue?
I thought maybe it was the radio, but i flashed like 4 of them and it is still possessed!!
Anyone have any ideas???
Thanks
Click to expand...
Click to collapse
I would suggest flash to one radio, 2.15.50.14, do a task 29(very important to get rid of any traces of old files/data in your internal rom partition) then depending which way you're going, winmmo or android, flash that.

Just had to read the thread with a title like that
Roloracer has hit it on the nail, just follow his instructions, and don't forget to format the sd card on the PC before putting it back in the phone
In my house its only the wife that acts possessed, lol

johnerz said:
Just had to read the thread with a title like that
Roloracer has hit it on the nail, just follow his instructions, and don't forget to format the sd card on the PC before putting it back in the phone
In my house its only the wife that acts possessed, lol
Click to expand...
Click to collapse
feel you in the wife part! lol
I would recommend him to format the sd card in CWM since it's way easier to do over the pc way.
In CWM go to format card and select 1024 mb with a 0 swap.

roloracer said:
I would suggest flash to one radio, 2.15.50.14, do a task 29(very important to get rid of any traces of old files/data in your internal rom partition) then depending which way you're going, winmmo or android, flash that.
Click to expand...
Click to collapse
Well thats what radio i initially flashed and is the radio that is on there now.
What is task 29? (sorry, im fairly new to this)
As to formatting SD card, i did that on MY HD2 and it is running NAND DL Desire by Dandiest. I formatted in Gnome Parition. Made a 1536 partition ext4, then broke that up into another ext4 partition at 512.
Is this what i should do on her phone? She likes having both WINMO and Android.
Thanks for all the replies and help!!

JohnnyVolcom5 said:
Well thats what radio i initially flashed and is the radio that is on there now.
What is task 29? (sorry, im fairly new to this)
As to formatting SD card, i did that on MY HD2 and it is running NAND DL Desire by Dandiest. I formatted in Gnome Parition. Made a 1536 partition ext4, then broke that up into another ext4 partition at 512.
Is this what i should do on her phone? She likes having both WINMO and Android.
Thanks for all the replies and help!!
Click to expand...
Click to collapse
Task 29 HERE
I suggest you run the attached Task 29 .exe together in a folder with the
.nbh file of Radio 2.15.50.14
procedure: (HSPL a prerequisite)
1. take the Task 29.exe and the .nbh file of Radio 2.15.50.14 put these two in a folder
2. Enter bootlloader (with device off, long press volume down while briefly pressing power button)
3. connect device to pc via usb
4. run Task 29 as administrator (or just double click it)
5. dont panic if your screen goes completely while, just remove battery
6. put back battery, enter bootloader again and flash any custom winmo ROM

jigners said:
Task 29 HERE
I suggest you run the attached Task 29 .exe together in a folder with the
.nbh file of Radio 2.15.50.14
procedure: (HSPL a prerequisite)
1. take the Task 29.exe and the .nbh file of Radio 2.15.50.14 put these two in a folder
2. Enter bootlloader (with device off, long press volume down while briefly pressing power button)
3. connect device to pc via usb
4. run Task 29 as administrator (or just double click it)
5. dont panic if your screen goes completely while, just remove battery
6. put back battery, enter bootloader again and flash any custom winmo ROM
Click to expand...
Click to collapse
Thanks, i found a video and a thread here.
http://forum.xda-developers.com/showthread.php?t=644781
I will update everyone in a couple days. (for some reason after each new install it takes awhile for the phone to become "Possessed" again. Last one worked great for 2 days and then BOOM back to Exorcist BS!!!
Thanks again everyone!

jigners said:
6. put back battery, enter bootloader again and flash any custom winmo ROM
Click to expand...
Click to collapse
Couldnt I just run Task29 with radio, (it will still be HSPL right?) then flash MAGLDR and just flash a NAND android rom?
My guess is yes, but would like some verification before i do ir
NEVERMIND...I just read your NAND guide in your sig....(which i used to on MY hd2, awesome guide and thanks BTW)
I will explore a little more before i ask questions from now on.
Thanks again Guys. and i will still update as to if it works!

if you have the radio already flashed , you don't need to flash it ever again!!! even after task 29, you don't need to, task 29 doesn't touch where your radio is stored.
I flashed my phone to 2.15 radio back in last november and task 29 about 20 times since then and never had to mess with the radio.

[Q] Hd2-Tmo (android) freeze when end call & sometime no sound when received the call

[Q] Hd2-Tmo (android) freeze when end call & sometime no sound when received the call
I've been try many android rom for my HD2(both nand and sd) but still get the same problems like the title and frozen when using the application for a long time (when hd2 getting hot). This rom http://forum.xda-developers.com/showthread.php?t=1930240 perhaps best android rom ever for my HD2: more stable, long time battery use (love it :good. But still get the same problem in the next 2 -3 days.
I've heard about MTTY but not yet try it. Will it helpful for my hd2?
What should i do?
Thanks for any help and sorry about my language!
Best regard!

Please thumbs up to help my question!

Re: [Q] Hd2-Tmo (android) freeze when end call & sometime no sound when received the
doomme said:
I've been try many android rom for my HD2(both nand and sd) but still get the same problems like the title and frozen when using the application for a long time (when hd2 getting hot). This rom http://forum.xda-developers.com/showthread.php?t=1930240 perhaps best android rom ever for my HD2: more stable, long time battery use (love it :good. But still get the same problem in the next 2 -3 days.
I've heard about MTTY but not yet try it. Will it helpful for my hd2?
What should i do?
Click to expand...
Click to collapse
If by MTTY you mean something like a Task 29 to wipe the device it probably will not help. If your device is overheating and several roms exhibit the same problem you may have a hardware problem..
---
Be careful about reading health books, you may die of a misprint...

NYLimited said:
If by MTTY you mean something like a Task 29 to wipe the device it probably will not help. If your device is overheating and several roms exhibit the same problem you may have a hardware problem..
---
Be careful about reading health books, you may die of a misprint...
Click to expand...
Click to collapse
thanks!
I've searched the whole forum, there are so many similar questions but no answers or something like you wrote. I'm trying to flash that rom (v1.3a) on NAND with clk 1.4.1 boot and radio 2.14.50.04 (perform Task29 provided by doloop first).
Results:
My phone automatically restart 1 - 2 times when i'm trying to download app from G-play store. But now everything seems ok.
I dont know how it would be in the next 2 - 3 days, hope everything will be fine.

Re: [Q] Hd2-Tmo (android) freeze when end call & sometime no sound when received the
doomme said:
thanks!
I've searched the whole forum, there are so many similar questions but no answers or something like you wrote. I'm trying to flash that rom (v1.3a) on NAND with clk 1.4.1 boot and radio 2.14.50.04 (perform Task29 provided by doloop first).
Results:
My phone automatically restart 1 - 2 times when i'm trying to download app from G-play store. But now everything seems ok.
I dont know how it would be in the next 2 - 3 days, hope everything will be fine.
Click to expand...
Click to collapse
Restarts and lockups are very different from overheating. Do you know how many bad blocks your device has? What size partitions did you create and which install (1, 2 or 3)?
---
Be careful about reading health books, you may die of a misprint...

NYLimited said:
Restarts and lockups are very different from overheating. Do you know how many bad blocks your device has? What size partitions did you create and which install (1, 2 or 3)?
---
Be careful about reading health books, you may die of a misprint...
Click to expand...
Click to collapse
- My device doesn't has bad block, i have followed the instructions by AngelDeath in this thread: http://forum.xda-developers.com/showthread.php?t=1189544.
- I was partition 320mb NAND memory with 5mb cache and install on NAND with DataOnEXT (type 2). Everything still works normally until now, no more freeze, no more auto restart (only gps hangs when i use Gmap to access my location = hardware failure).
- I think, my device hang in call because i have installed RamManagerPro v4.1.2. before, perhaps it isn't compatible with my device.

Damn, It happened again when i take a call over 20 minutes. This is no hope, exactly hardware problem :crying:

[Q] All roms boot failure, mgldr works fine

Hello all,
I have a question regarding a HD2 of a friend of mine who asked to put Android on it. I did it before without problems, but on this phone something is not going right. I have spent at least 20 hours on trying to fix it (mainly flashing new roms, fixing clockworkmod over and over again etc.) and of those 20 hours I spent at least 5 of them reading the web. So I hope I did not miss the solution somewhere, if it is out there I really tried to find it.
2 Sections, 1 with the question(s) and 1 with phone outputs.
QUESTION SECTION
The phone is not bricked (as far as I know), it just won't boot any roms.
When the phone is booted (power button down) magldr boots fine (UPDATE: Flashed original ROM, so Magldr is gone now, can reflash if necessary)
Clockworkmod works, but only until I flash a ROM. After flashing a ROM clockworkmod is gone.
Now when I try to flash a rom (zip from SD card to NAND with Clockworkmod) it works fine. I get the installer most of the time (in general Aroma) and the installer indicates everything gets installed correctly. I did check, the 250 MB partition was enough for the Roms (most required only 200 MB). But when the system goes for a reboot I get to Magldr, it seems to boot allright, but when it says 'GO GO GO!' it just stops. I am now trying a last time by leaving it on for the next hour in the hope at some point something will happen, but ten minutes does not seem to be enough of a wait for anything to happen.
I tried six or seven roms (and a few months back like 5 or 6 too).
The funny thing, about 3 months ago I flashed this same phone. Back then it was already taking more time then I am used for a HD2, and lots of errors until I finally managed to get it working. Only the rom installed seemed to be instable, it rebooted a lot and that is why they asked me to put another one on it. But still, that android rom did boot. I believe the instability issues could have been caused by me choosing the wrong partitioning, I noticed there was hardly any room left on the system so I might have used the bigger half GB clockwork partition back then leaving no room for apps or whatever the phone needed (16 mb system memory was left).
After starting my original flash my friend told me Windows was not working correctly. Yes, after I did the more or less irreversible flashing
Does anyone have any idea regarding what I could be missing?
Thanks in advance.
<UPDATE, TRIED THE FOLLOWING>
Reflashing original ROM
I reflashed the original ROM (twice). The second time I did a 'task 29' before flashing.
The first time it booted to the 'first time use' part where I could put some settings like wifi etc and I could unlock the SIM so it registered to the network. But before it actually booted fully it started to reboot. It would generally reboot around the 'enter PIN' screen.
The second time (after the task 29) the system just hangs on the 'htc' welcome screen.
I used the original rom from the HTC website (RUU_Leo_S_HTC_NLD_3.14.404.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship).
PHONE READOUTS / DO NOT READ IT ALL, PICK THE INTERESTING STUFF
The phone
HTC HD2
EU model (half a GB NAND)
HSPL has been flashed
Radio has been flashed
Magldr has been installed (v 1.13, this is the newest version)
Clockworkmod has been installed (250MB variety) (here also the newer NAND version)
Bootloader screen readout
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x40
<UPDATE>
I did a info 8 on MTTY to check for bad blocks in NAND memory. As I was at it I did some other info queries. I hereby post the results. Maybe this means something to someone. All I know is there are no bad blocks (as far as this output is telling me).
--------------------INFO 0 OUTPUT
Platform Model IDB8110000
Platform HW Board ID:4, UNKNOWN
--------------------INFO 2 OUTPUT
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 LC card
4 bit mode
SD Init OK
crc=0xDCE9D41E.
HTCSSuperCIDHTCE
--------------------INFO 3 OUTPUT
crc=0xD0003C4A.
HTCS
--------------------INFO 4 OUTPUT
crc=0xDCE9D41E.
HTCSSuperCIDHTCE
--------------------INFO 6 OUTPUT
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
--------------------INFO 7 OUTPUT
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: LEO, Bootloader Version : 2.08.HSPL
Built at: Feb 8 2010 22:33:51
Copyright (c) 1998-2006 High Tech Computer Corporation
CPU ID=0x510F00F2
--------------------INFO 8 OUTPUT
--- 2K bytes sector version ---
DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 1030 (0x406) is reversed block
Partition[0], type=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0
CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000
--------------------INFO 9 OUTPUT
Storage Start Addr=0x30420000, length(with sectorinfo):0x0
Storage Start Addr=0x30420000, length(without sectorinfo):0x0
Ext ROM Start Addr=0x4AAA0000, length(without sectorinfo):0x0

I appreciate the amount of information you're providing, but you're just giving too much information (or should I say too much writing?)
I don't mean you should never provide lots of information, I am saying you should provide all the information which are relevant.
Anyway, since your friend said that the device was not functioning properly on windows mobile, it could indicate a hardware problem. I suggest you flash back windows mobile and see if the problem is hardware related. If it is, we won't have to troubleshoot Android, CWM, or MAGLDR.
Report back.

Hello Marvlesz,
Thanks for the suggestions.
I reflashed the original ROM, I used a ROM from the HTC website.
Unfortunately this does not make the phone usable, so I start to wonder if it indeed is a hardware error. The first time it was a successful flash, but it keeps resetting itself at about the 'enter PIN' field. After a task 28 I reflashed the same ROM and now it comes no further as the HTC screen.
As windows phone has loaded after the first flash I am assuming (H)SPL cannot do this, after loading Windows the secondary bootloader has already done it's work. And as the Radio is in the ROM this should be current (and functional) too.
Note: I did multiple task 28's the regular one but also the task 28 55aa.
I fear the phone will not be recoverable as it is more or less stock now and still not functional, I am almost certain it is a hardware error.
Regarding the big pile of text, I believe you are right. I posted a humongous amount of text.
I divided it in two sections, the actual question which is quickly readable and a phone output section out of which everybody can pick what he or she wants to see .

Pelskikker said:
Hello Marvlesz,
Thanks for the suggestions.
I reflashed the original ROM, I used a ROM from the HTC website.
Unfortunately this does not make the phone usable, so I start to wonder if it indeed is a hardware error. The first time it was a successful flash, but it keeps resetting itself at about the 'enter PIN' field. After a task 28 I reflashed the same ROM and now it comes no further as the HTC screen.
As windows phone has loaded after the first flash I am assuming (H)SPL cannot do this, after loading Windows the secondary bootloader has already done it's work. And as the Radio is in the ROM this should be current (and functional) too.
Note: I did multiple task 28's the regular one but also the task 28 55aa.
I fear the phone will not be recoverable as it is more or less stock now and still not functional, I am almost certain it is a hardware error.
Regarding the big pile of text, I believe you are right. I posted a humongous amount of text.
I divided it in two sections, the actual question which is quickly readable and a phone output section out of which everybody can pick what he or she wants to see .
Click to expand...
Click to collapse
What is task28? I have never heard of that.
...
*Does research*
...
Nope, couldn't find anything of interest. Could you please tell me what task28 is?
Maybe you mean task29? But task29 doesn't have a 55aa alternative.
Anyway, although I highly doubt it, it could be HSPL. Uninstall it, and install a stock ROM then see how it works.
Your problem is weird, and with no background of the device, it could be anything.
By the way, when the phone was "acting strange" in your friend's hands, was it overheating?
Since you said the device worked fine using the same setup a few months ago, I'd say it's hardware related.

Thanks for the suggestions once again. Though I really do not know why flashing HSPL back to stock SPL fixed the phone it now works again.
What did I do? I took the same rom that I flashed the last two times and did not work, but this time instead of doing it trough the pc I extracted the file and only used the leoimg file, put it on SD, booted in bootloader mode and this way not only the rom itself but also SPL was flashed.
And now the phone works again .
I however do think I am not going to put Android back on it for now. I will give him back a working windows phone or, if he no longer needs it (as he bought another phone this morning) I will use it for testing more fun mod stuff. Maybe it will start to fail again, but now I know how to make it work again (and it's actually rather easy trough SD). Though I am really curious now if it really was the SPL that was causing problems (it was the only non stock item left) and if flashing a new HSPL would fix the device for android use.
Regarding task28, I took that from the 'Hermes Bootloader Commands' doc file. By typing task28 in mtty it formats the NAND memory, by using the command task28 55aa it formats the nand memory and the "partion". I did notice that mtty gave a different output if I added 55aa, it included more blocks in the formatting process if I remember correctly.
Thanks again, the phone is working
Marvlesz said:
What is task28? I have never heard of that.
...
*Does research*
...
Nope, couldn't find anything of interest. Could you please tell me what task28 is?
Maybe you mean task29? But task29 doesn't have a 55aa alternative.
Anyway, although I highly doubt it, it could be HSPL. Uninstall it, and install a stock ROM then see how it works.
Your problem is weird, and with no background of the device, it could be anything.
By the way, when the phone was "acting strange" in your friend's hands, was it overheating?
Since you said the device worked fine using the same setup a few months ago, I'd say it's hardware related.
Click to expand...
Click to collapse