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
Related
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!
Hi,
I open this thread in the hope that this might help other people in the future (I found it quite time-consuming to find out the relevant information).
Motivation: My Polaris (actually from O2) had lately a servere graphics error which disappeared after a soft reset, but the day after it refused booting:
after pressing the power button, the provider-logo is shown (appearing with some minor graphics errors) and after 30 seconds the device reboots again. Before doing a hard reset or sending it to HTC, I wanted to backup the NAND-Memory, from which I can - hopefully - restore some data, especially Notes, Short Messages and some contacts.
I spent a lot of time finding out the possible ways of ROM dumping. To summarize what is not possible:
Dumping to MicroSD-card is not possible, since "r2sd" (or "d2s") is not available on the Polaris
Dumping via "itsutils" and "pdocread" is not possible, because it requires a properly running Windows Mobile on the Polaris
Please correct me, if I am wrong.
The only available method seems to be:
Start the Polaris in bootloader mode and connect it to the PC via USB
With HTCFlasher (great tool btw! Alternatively mtty/ttermpro) issue the commands
password BsaD5SeoA
set 1e 1
rbmc
I know that rbmc can be told a start-address and length, but I do not know these addresses. In the first moment this seems to work, even though it is quite slow (~8 KB/s, at the moment the dump is at 71 MB). However, after a first peek into the dump, I noticed that the dump might be partially corrupted, due to some seemingly randomly inserted bytes (mostly with value 0x00). For example: at offset 0x39110 there seems to be a Delivery Confirmation of a Short Message: Instead of "Systemadministrator" it reads "Sys.temadmin.i.rator" (the dots are 0x00, 0x82, 0x81). Or again at offset 0x3D1C0 it reads "Sy.stemadmi.ni.rator" (dots are 0x00, 0x04, 0x81).
I use the latest version of HTCFlasher on linux-2.4.32 with the usb-serial-source of linux-2.4.28.
My questions:
Is there something to keep in mind when using rbmc on the polaris?
...probably regarding usb host buffer sizes? In in this thread pof suggests to use two rbmc's to dump the splashscreen.
Is there another way to perform the dump?
Yeah me too
Yeah I wanted to do something similar with my Kaiser. I wanted to dump the various winCE partitions from bootloader.
I started two threads
http://forum.xda-developers.com/showthread.php?t=481964
and
http://forum.xda-developers.com/showthread.php?t=480410
As you will see the only advice I got was "try using QMAT".
Unfortunately, QMAT is an extremely complicated piece of software and only runs for ten minutes at a time unless you are willing to pay for it.
IMO there should be a simple answer to this but nobody cares enough to read our threads...
The SMT5600 is app unlocked and, I think, Super CID (via lokiwiz02_173 but how verify?) but no ROM changes as of yet as I want to make a backup of the original ROM before proceeding further.
After problems getting a term program to work (now using nueTTYConsole on Vista) I am able to get what appear to be complete ROM backups.
Procedure summary:
WinHex zero fill 64MB SD
USB bootloader SMT5600 with 64MB SD
r2sd all (via nueTTYConsole-12-v0.1-spackr)
SD back to PC [no to format query]
psdread E: 0 31328768 ipl.bin (using itsutl050119)
Status messages from the r2sd all command appear to be good and complete but no two backups, using the exact same procedure, are ever identical when binary compared with WinMerge. Size is, of course, the same but WinMerge always reports 'two' differences in what seems to be the same general area of the images: The first is very near the front of the image (WinMerge reports as 'lines', line 3) and the other at the very tail end.
Is that normal (maybe because TIME, or some other dynamic variable, changes or scratch storage?), is there a better backup procedure, and how can I verify the backups are good before I flash a new one and forever lose the original?
Thanks in advance for any enlightenment offered.
To check if it works - just restore the backups before doing anything else.
Follow the whole procedure (including psdread and - after reformatting the card - psdwrite again) to restore your device via the card. As a first try leave out the device external activities and restore immediately afterwards from the card just written.
For me it works well (on the SDA 2 - where no official update exists, a Hurricane device - but this generic handling is identical afaik) and the difference in the backups are normal.
Mind that the size of the read/write to card includes the bootsector, so don't miss the last 512 bytes. As far I remember there were two different size readings with two methods to verify the image size. The r2sd size is smaller than the size of bytes different to null on card.
To check for SuperCID enter "info 2" in the terminalprogram, it should report HTCSuperCID at the end.
tobbbie said:
To check if it works - just restore the backups before doing anything else.
Follow the whole procedure (including psdread and - after reformatting the card - psdwrite again) to restore your device via the card. As a first try leave out the device external activities and restore immediately afterwards from the card just written.
Click to expand...
Click to collapse
Thanks for the reply
Yes, I thought about doing a test restore, but, considering the problems I'd already had, wasn't sure if it might do something like not mention there being a 'problem' till it was half way through, leaving me with a scrambled ROM.
I take it you're saying it'll checksum first and no even start if things don't look good?
tobbbie said:
For me it works well (on the SDA 2 - where no official update exists, a Hurricane device - but this generic handling is identical afaik) and the difference in the backups are normal.
Mind that the size of the read/write to card includes the bootsector, so don't miss the last 512 bytes. As far I remember there were two different size readings with two methods to verify the image size. The r2sd size is smaller than the size of bytes different to null on card.
Click to expand...
Click to collapse
Hmm. I saw the confusion about SMT5600 image size but I'm not sure what you're saying here about the bootsector and "different to null."
Speaking of which, what would be wrong with just making a 64M save and, ok, you've save a pile of extraneous 0's along with it but, so what? Might be irritating if I were putting it on rapidshare but for a personal backup is there any down side to it?
tobbbie said:
To check for SuperCID enter "info 2" in the terminalprogram, it should report HTCSuperCID at the end.
Click to expand...
Click to collapse
Thanks. Good to know.
Something apparently went wrong somewhere because I didn't get that report but I'll try again.
The r2sd is a command that HTC has implemented in the SPL (Secondary Program Loader). I am not aware of checksums or other safety measures - it will as I noticed following the procedure detect if there is an image on the card, which type of image and if you want to restore.
The difference in size is that r2sd reports one size "x" after the image was taken, but if you count the bytes until when the card shows the zeros you will notice that this offset on card is 512 bytes larger than the r2sd reported size. So when using psdread you have to take the larger size. Indeed it is no problem to write more to the file and restore more as well with psdwrite. The restore procedure in the SPL will anyway know how much to restore - it just needs to find ALL bytes, including the last 512
I think there is no risk attached to the procedure, go ahead!
The only danger is if something goes wrong with the IPL (Initial Program Loader) or SPL because they open the door to the device handling.
Sadly you MUST deal with SPL to upgrade to WM5+ afaik, so be very sure to select the right IPL and SPL that matches your device HW (OMAP 730, 750 or 850) and intended OS Version. Also take care not to enter any command in the SPL except the ones you are supposed to enter - it may kill your device as well. Do never use "format all" or "doctest" - you have a brick then.
tobbbie said:
The r2sd is a command that HTC has implemented in the SPL (Secondary Program Loader). I am not aware of checksums or other safety measures - it will as I noticed following the procedure detect if there is an image on the card, which type of image and if you want to restore.
Click to expand...
Click to collapse
Well, I am certainly no expert on this thing but r2sd spits out a wealth of information, including checksums, and I was sort of guessing based on what I'd do if I'd made it. Just that, if you're going to calculate them, it seems a shame to not use them. But, hey, I've seen stranger things done.
tobbbie said:
The difference in size is that r2sd reports one size "x" after the image was taken, but if you count the bytes until when the card shows the zeros you will notice that this offset on card is 512 bytes larger than the r2sd reported size. So when using psdread you have to take the larger size. Indeed it is no problem to write more to the file and restore more as well with psdwrite. The restore procedure in the SPL will anyway know how much to restore - it just needs to find ALL bytes, including the last 512
Click to expand...
Click to collapse
Oh, OK. I wasn't going by r2sd. I opened it up in WinHex, found the end of data, and compared that to the size mentioned on "Backup your Typhoon ROM - WinMo @ MoDaCo." The 'corrected' number there matched well enough.
But now that I think of it, I did that because I *did* look at r2sd and it seemed too small. So you've explained it. Good.
tobbbie said:
I think there is no risk attached to the procedure, go ahead!
Click to expand...
Click to collapse
How can there be no risk if it doesn't check anything?
tobbbie said:
The only danger is if something goes wrong with the IPL (Initial Program Loader) or SPL because they open the door to the device handling.
Click to expand...
Click to collapse
Oh, I think I see what you mean. You're suggesting that if I've cut the ROM image short then only that part will fail but the loader should still be good so I could recover by burning another (good) ROM image.
Well, perhaps, but that would mean I don't have a valid backup and couldn't make one since it would be trashed in the bad flash. Or so it seems to me.
tobbbie said:
Sadly you MUST deal with SPL to upgrade to WM5+ afaik, so be very sure to select the right IPL and SPL that matches your device HW (OMAP 730, 750 or 850) and intended OS Version. Also take care not to enter any command in the SPL except the ones you are supposed to enter - it may kill your device as well. Do never use "format all" or "doctest" - you have a brick then.
Click to expand...
Click to collapse
I was thinking of going straight to WM6.x per
karhoe.net/guide-upgrading-htc-feelertyphoonamadeus-to-windows-mobile-6-update-september-06-2008.html
which involves changing the loader first via Patched_RUU
Do you think going to WM5 first is a safer procedure?
I said I was not aware of any checking - but as I have not written the SPL, I simply do not know it. You are right that reporting stuff like this makes it highly probable that upon restore a check on the image should be done before restoring. Try it out, if you like
WM5 or WM6 does not make a difference what the SPL is concerned. Afaik you have to use the same anyway. The device is tight in memory anyway, so don't expect miracles.
Go ahead, either dare it or leave it...
tobbbie said:
I said I was not aware of any checking - but as I have not written the SPL, I simply do not know it. You are right that reporting stuff like this makes it highly probable that upon restore a check on the image should be done before restoring. Try it out, if you like
Click to expand...
Click to collapse
Hehe. Yeah.
I was sort of hoping someone else had already stepped off that cliff and could tell me what the ground was like before I dove in
tobbbie said:
WM5 or WM6 does not make a difference what the SPL is concerned. Afaik you have to use the same anyway. The device is tight in memory anyway, so don't expect miracles.
Go ahead, either dare it or leave it...
Click to expand...
Click to collapse
The primary aim was to get bluetooth a2dp but the incentive may have diminshed, depending on how another project works out.
Thanks again for the help.
I would not bet on A2DP - I have it in the Tornado and the CPU use is much higher due to additional compression on the BT interface. Player + BT overhead is getting to average above 80% CPU (depending no the settings, but for good quality is like this) - it will also drain your battery much faster.
The Typhoon, Hurricane and Tornado have identical good analog Audio capabilities (I measured them with RMAA - see www.rightmark.org) and make a perfect music player as they are.
If your device is SuperCID you can take any other Typhoon ROM - you must just be sure that r2sd will save your bootloader + OS if you want to go back to WM2k3. I have done this already on my Amadeus (and went back to WM2k3) and this can still serve as a nice musicplayer.
tobbbie said:
I would not bet on A2DP - I have it in the Tornado and the CPU use is much higher due to additional compression on the BT interface. Player + BT overhead is getting to average above 80% CPU (depending no the settings, but for good quality is like this) - it will also drain your battery much faster.
The Typhoon, Hurricane and Tornado have identical good analog Audio capabilities (I measured them with RMAA - see www.rightmark.org) and make a perfect music player as they are.
If your device is SuperCID you can take any other Typhoon ROM - you must just be sure that r2sd will save your bootloader + OS if you want to go back to WM2k3. I have done this already on my Amadeus (and went back to WM2k3) and this can still serve as a nice musicplayer.
Click to expand...
Click to collapse
I admire people who can make these flash things work because it never does for me. I've now got an SMT5600 that will do nothing but display a rainbow boot screen and error out regardless of what ROM I try.
That's why I didn't try this till I had a new phone.
Hey that thread has a long history - what happened in the meantime?
3 colour screen does not mean the device is dead yet. You still have a bootloader that works and this is the thing to start from in any case.
What do the lines tell in the 3 color bars?
Did you already upload the changed SPL (I think it was 1.09) that allows to flash ROMs of WM5 or WM6 on that original WM2k3 device? If so, the you need to revert back to old SPL first before you can upload the original ROMs again.
tobbbie said:
Hey that thread has a long history - what happened in the meantime?
Click to expand...
Click to collapse
I put it on hold pending a new phone and other things cropped up.
Frankly, I had 2003 pretty well tricked out with SmartToolkit and gStart.
tobbbie said:
3 colour screen does not mean the device is dead yet. You still have a bootloader that works and this is the thing to start from in any case. What do the lines tell in the 3 color bars?
Click to expand...
Click to collapse
I swear it wasn't a troll but no sooner than I posted it wouldn't flash I managed a flash and I'm not sure why this worked when the others failed.
I was trying to verify the hard spl, getting info, etc. To make that easier I turned 'ui' on during boot and, just for chuckles expecting nothing, I tried flash again. You know, the definition of 'insanity'. Low and hold the dern thing flew.
As far as I know nothing was different other than 'ui' on. Same tools, same wm6.5 bin file, etc.
tobbbie said:
Did you already upload the changed SPL (I think it was 1.09) that allows to flash ROMs of WM5 or WM6 on that original WM2k3 device? If so, the you need to revert back to old SPL first before you can upload the original ROMs again.
Click to expand...
Click to collapse
You have no idea how helpful mentioning "1.09" is. The SPL flash program opines something like changing to v 5.000 but that number shows up no where and no where does it tell you to look for '1.09'. There are other confusions, like saying the existing device was 'Orlando' (I think it was), but I guess that's moot now.
Anyway, it's now running WM6.5 and I have a new toy to fiddle with inbetween playing with Android on my Tilt 2.
Thank you for the help.
Glad it worked now
The older (wm2k3) devices could only be updated with a binary transfer protocol (the .BIN file - which can be confused with other ".bin" in the scope of cooking in general). To enable the reception of the MTTY command "l" (for Load) and the execution of the related actions, the SPL must be in "UI" (User Interface) mode - this is the key for further flashing - and it must be mentioned in all such upgrade manuals. Also mind that other terminal programs (like TerraTerm) have not implemented that protocol. So only MTTY works for that purpose! As I am struggling currently with porting a Tornado ROM to the Hurricane I have come quite deep into that topic recently.
Are you having the WM65 from aleut now on the device? I think it is very tight on RAM now, so what are the memory key-data from settings->about after a reboot? You should repeat that with the standard home screen (Windows default) which is less memory greedy.
The way back to WM2k3 is not so easy as you must replace the SPL with the original one first before you can get back to the original OS. Whenever you mess with SPL it is a potentially dangerous action as failure doing that right will result in a bricked device.
tobbbie said:
Glad it worked now
The older (wm2k3) devices could only be updated with a binary transfer protocol (the .BIN file - which can be confused with other ".bin" in the scope of cooking in general). To enable the reception of the MTTY command "l" (for Load) and the execution of the related actions, the SPL must be in "UI" (User Interface) mode - this is the key for further flashing - and it must be mentioned in all such upgrade manuals. Also mind that other terminal programs (like TerraTerm) have not implemented that protocol. So only MTTY works for that purpose! As I am struggling currently with porting a Tornado ROM to the Hurricane I have come quite deep into that topic recently.
Click to expand...
Click to collapse
So I discovered after missing the little '0' in the instructions.
tobbbie said:
Are you having the WM65 from aleut now on the device? I think it is very tight on RAM now, so what are the memory key-data from settings->about after a reboot? You should repeat that with the standard home screen (Windows default) which is less memory greedy.
Click to expand...
Click to collapse
Yes, I originally flashed Aleuts 6.5 but I've since reflashed with his 6.1.
tobbbie said:
The way back to WM2k3 is not so easy as you must replace the SPL with the original one first before you can get back to the original OS. Whenever you mess with SPL it is a potentially dangerous action as failure doing that right will result in a bricked device.
Click to expand...
Click to collapse
Yep, flashing SPL is the most vulnerable but I don't think I'll be going back to 2003. Although, I might try WM5 if that has more free memory.
With most things I plan on using installed there's 8.5Meg free at boot and while that sounds laughable by today's standards there's only 22Meg total for a more impressive sounding '38% free' Although, as soon as you touch the thing almost half of that is gone.
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.
hi...i have a big problem...i cannot install an OS on my htc...especially a radio version...i receive an error at 100% saying that its not compatible or something like that....if i install a 6.5 Windows rom the phone won't start...so i'm guessing it is because of the radio....please someone help...tnx
Check if you phone gets hot... if yes then your phone has heating issues.
te be sure try this:
put you phone in fridge for 5-10 min ( take out battery, sim card, memory card and put phone in a bag to protect from water ), than try to install ( usb method or sd card method - i prefer last one)... probly everything will go ok but phone still wont boot up - if it does then its not heating issues.
I hope it works
PS: for heating issues visit link provided in my signature ( Solving the thermal problems of HD2 ) .
hi thx for the advice...but i do not think thats the problem now....maybe it was when it had an operating system and it kept restarting...but now i cant put on him a radio version...to install a os rom i can...but freezes in the logo screen...so i guees i need to install radio on it so the os will start..but i cant(....and i also tried to delete the memory with mtty and it failed also..at task 29 command or task 28 55aa says this:Cmd>set 14 0
crc=0xD2C8DA7F.
HTCST ÚÈÒHTCE
Cmd>task 28 55aa
Format start
Fill RSVD information for block 497 to 530
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>task 29
Format BINFS start
Fill RSVD information for block 497 to 530
CE start start block=530, total block=3566
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format BINFS end
Cmd>
so i do not know what to do...
in the mtty thread, post 1, it says to ignore those error messages, , they are normal. MTTY (and task29) doesnt touch teh area of NAND where the radio is located anyway.
You seem to have what is sometimes referred to as a stuck radio, which doesnt work and wont flash.
Sorry, there is no actual fix for this, and the consensus seems to be that it is corrupt / bad NAND blocks.
The only solution which occasionally seems to work (but only in some cases) is cooling the phone as mentioned above.
Prepare your CORRECT stock rom on an sd card, phone into a bag in the fridge/freezer for long enough for it to be cold, then quickly sd card in, into bootloader, start it flashing, hope it takes. Ive seen people say it took on the 5th/10th/20th attempt, but for many it never takes.
ok thx...ill try the cooling method....regarding the mtty post...i've read it too...but there wrote to ignore errors...in my case says tag not found!not clear storage....like some kind of memory error...
QUOTE from mtty thread post 1
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Click to expand...
Click to collapse
samsamuel said:
... and the consensus seems to be that it is corrupt / bad NAND blocks.
Click to expand...
Click to collapse
totally agree with " samsamuel ".
About fixing a i told visit that thread because we are trying to find a solution about it... in my case i think it worked... my hd2 had same problem always filed at 8% - 9%, i tried fridge method everything went ok BUT phone didnt boot up it - stock at htc ... i installed android it booted but if i watch a movie or played games it will freeze and restart... then i installed wp7 same as android... many times it had fatal hit and wont boot until it cooled down, but now im able to watch a video @480p 3 times - length 80 min. im unable to flash stock rom because my volume buttons and keypad buttons dont work.
rzvcool003 said:
hi...i have a big problem...i cannot install an OS on my htc...especially a radio version...i receive an error at 100% saying that its not compatible or something like that....if i install a 6.5 Windows rom the phone won't start...so i'm guessing it is because of the radio....please someone help...tnx
Click to expand...
Click to collapse
why....do...you...type...like...this??
Fridge trick does work!
Hey guys, I got one TMOUS HD2 which boots randomly and won't flash any radio.
I tried everything ...HD2 toolkit, mtty , stock rom etc...nothing.
Last put the darn thing in the freezer for 30 minutes (cannot tell the temp )
And yeeeeeeeeeeeeeesssssssssssssssssss
IT WORKS!
EVERYONE WITH A STUCK RADIO SHOULD TRY IT.