Database Users

The Dangerous Lines

Hi,
I have been looking at these post around and I have noticed some unlocky guys with "bad" experiences upgrading their ROM(s) ...
I have thought of I way of documenting their mistakes as "Dangerous Lines" so others will not make the same mistake ..
I will start with my own "bad" experience when trying to upgrade my Radio Stack using Othman's previouse posts ..
I had the problem when the system was expecting the PIN number but it has hang , I reseted it and I lost my QTEK sice that .
I took it to the supplier and they claim changing the main board.
"SO WE SHOULD NOT HAVE PIN ASSIGNED BEFORE UPGRADING OUR RADIO STACK"
There other mistake madeby one of the guys is that they have choosen to load the boot using the XDArit with the wrong file and they have lost their bootloader ..
"SO WE SHOULD NOT CHOOSE TO LOAD THE BOOLLOADER WHILE BURNING THE SD CARD WITH A ROM using the XDArit tool"
That is it form me ... let have more Dangerous lines ..

About bootloader....
IMHO: "so we should not choose to load the bootloader while burning the sd card with a rom using the XDArit tool, TILL YOU DON'T HAVE RIGHT BOOTLOADER IMAGE..." It's a real way to change version of bootloader...

What about using Jeff's exe file- any "not-to-do"
HI
What about some tips for simple non computer literate guys like me upgrading my 3.16.32 Eng rom? Running exe file from Jeff is all I thot of doing and are there any steps to note to avoid danger?
Any advice on what to do and what not to do ?
Cheers
Vic

I disagree, I've flashed many different devices with different versions of OS and Radio without problems - most problems are caused by people trying to charge their XDA while updating (there's a bug in the flash programme btw, it says "unplug me", then it screams it is not 70% charged - if you keep it in charger and pres OK you're doomed), or by trying to flash version for different region (900/1800 on 900/1900 device for instance). Or disobbeying another rules (NO USB HUB, disabling USB deviced which may interfere).
I think it's mostly peoples fault... but accidents sometimes DO happen by themselves

Oh, go easy on the kids Zviratko look at me I was a lowly dumb pretty boy :mrgreen: Actor before this site and now I'm flashing like the pro's 8) ok I did have some Cell phone tech background but know nothing about writing code. Most of your heavy hitters here are programmers 8)
But you are right about user errors more than device errors so that's how we learn sometimes :lol:

my xda is locked and a GID code is required - Help

I have upgraded my XDA with a rom from the kitchen and now the phone will not work it keeps asking me for a GID: code. the sim is not locked as it works fine in a differant phone and i have tryed a differant sim in the xda and still get the GID: code window. can anyone tell me what is this and how do i get past it.
rom ver: 3.17.03 eng
date 05/15/03
radio ver: 4.21.00
protoco ver: 32s54
Well ive read most of the other chains and there is lots about unlocking sim and using XDAunlock but they also say if you have the special edition rom you dont need XDAunlock as itis included which i have.
If i click the sim unlock it tells me the sims is unlocked but when i enable the phone i still get the GID code window.
Any help would be good as i am now without a phone.

This is weird: the ordinary SIMlock used is some phones is technically called SID-lock. As I understand, the GIDlock feature is used to lock to a specific SIM. Why your phone would suddenly have a GIDlock enabled after upgrading your PDA ROM is beyond me. Are you sure upgrading the ROM is only thing that's different? Is it a 900/1800 or a 900/1900 phone? What RSU version is in there? What ROM did you have before? What ROM did you base your new kitchen ROM on? Do you have a serial cable or cradle?
Questions, questions, questions...

Thanks for your reply.
i have only upgraded the rom. its a 900/1800
not sure of the RSU device info is
rom ver: 3.17.03 eng
date 05/15/03
radio ver: 4.21.00
protoco ver: 32s54
this is a v-old XDA and the rom was so old it could not upgrade via usb /cradle (sorry forgot what the rom was but reading another chain who had the issue of not being able upgrade via usb i had the same rom as him. so i saved the ce+boot from a work mates xda to sd card and upgraded it. all was ok i then downloaded the rom from the kitchen and upgraded it via the cradel (usb).
I still have the sd card and have tryed reloading the ce+boot but when i boot up i still get the gGID: code window. so reloaded the kitchen rom and thats where i am now.

the rom i used i got from http://cuba.calyx.nl/~jsummers/ROMkitchen/
3.17.03 ENG O2-Euro .
here is all the info on my XDA i hope this helps some one.
model pw10a1
platform pocketpc
imei : 350312010009954
cpu : arm sa1110
speed 206 mhz
ram 32 mb
flash : 23 mb
flash chip : 28f128
data bus 23 bits
rom ver :3.17.03 eng
rom date : 05/15/03
radio vertion : 4.21.00
protocol ver : 32s54

We roughly know where the GIDlock code is stored in the phone ROM. And if you have a serial cable, we probably (maybe) have the AT command to extract the data. However: since 4.20 they obfuscated the other (SIDlock) code, and they may also have obfuscated this one. So no promises: It's a bit of a project, and as long as you're the only one with this problem it's kind of a waste: I'd rather spend the time on stuff that is useful to all of us.
Let's first try this: maybe it helps to reset the phone... Could you try resetting it using the menu from the bootloader? To do this, soft-reset the phone while keeping the power button pressed, and then (after "WAIT" is gone) press the top-right (calendar) button, select the fourth option from the menu using the rocker switch and then press the center of the switch.
I still need to know if you have (access to) an XDA serial cable.

I have tryed the soft reset no joy
i done have access to a serial cable only the usb.
please try to help,,,,
i i do get hold o a serial what do i need to do?

I'd like you to hook up a serial cable, start a terminal program at 115.200 bps, put the device in bootloader mode as described above, and then enter "dualser<enter>" followed by "AT%UREG?3FE004,FFFFFFFF<enter>", and then cut and paste the result here...

Ive got hold of a serial cable and connected it up. booted xda and see HTC botlader for (wallaby) etc.etc on screen.
but when i type the dualser i do not 1. see what i typed & 2. there is no responce from the device.
hyperT is set to
com 1
BPS = 115200
data b = 8
parity = none
stop b = 1
flow c = (tryed none, hardware, xon/xoff.
i know the typerT works as i have commected to a modem and can see at when i type it. tryed typing ate1 when connected to the xda (as this turns on echo but still no joy.. dose the xda have a differant echo on command.??
i do not beleve i have a duf cable as when i boot up i can see info from the xda come on the screen.. any comments would be good. ill see if i can find a differant cable for now and retry.

Ok i havegone a got a cable from 02 and connected it up.
i still have the same situation. i can see the xda boot on hyperT but my key strokes have not affect..
what now....

ok that was a game and some but here is the results.
i hope this means someting to you..
Code:
at%ureg?3fe004,ffffffff
+EXT_UREG
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFF000000000000
00000000000000000000FFFFFFFFFFFF
FFFF000000000000FFFFFFFF00000606
00000000
ok

nex_uk said:
i hope this means someting to you..
Click to expand...
Click to collapse
I would say your GIDlock is set to "00000000" (eight times zero). And your SIM pin is set to 0606 ?
(I'm glad it's all zeroes, because the obfuscation algorithm (I now know GIDlock also obfuscates) doesn't touch it that way, otherwise I would have to rip out the manipulator source.)
Try entering it normally first (i.e. through the box that asks for it). If that doesn't work, try entering "AT%LCKGID=0,00000000".
Hope this works...
Still have no clue why on earth your phone would have decided to turn it on...

Thanks Peter Poelman.
I have done that and now the window is gone. but my phone will not get a signal.
the At now looks like this.
AT-Command Interpreter ready
at%ureg?3fe004,ffffffff
Code:
+EXT_UREG
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFF000000000000
0000FFFFFFFFFFFFFFFFFFFFFFFFFFFF
FFFF0000FFFFFFFFFFFFFFFF02020606
00000000
OK.
ive tryed registering on network bit dose not find any.
ill reload the xda rom and try again and let you know.
thanks again for you helo so far...

nex_uk said:
I've tryed registering on network but does not find any.
Click to expand...
Click to collapse
I'd say the phone part in your device got very very confused at some point, possible not even connected with the new OS ROM. The dump already looks kind of funny, and I wouldn't be surprised if your phone has lost all of its configuration data, resulting in it being broken. You may (at your very own risk, I've never done this!!!), try the GSM Debug/Calibration mode from the bootloader. I've always been curious to see what it does, and in your case it may actually do some good.
Loading new ROMs will probably not help. You could try (again, at your own risk) doing an RSU upgrade before trying the calibration from the bootloader. But I'd say this device probably needs to go back in for repairs.

(And you might want to check, using the bootloader) that it's not inadvertently set to the wrong band or something)

Thanks..
we the reload of rom has started so ill wait for it to finish then ll try RSU upgrade (ill down load a new one from 02) thenif i still have no joy ill post the at string first so you can see if you see anything if not (what the hell) ill try GSM Debug/Calibration the xda is shagged so it cant break it..
as this is a second hand XDA do you know of anyone that can fix it in the UK.???
any ho ill let you what happens..

l chck the boo after the reload as this is 02 (uk) it should be 900/1800 right.

Just set the band manually via the bootloader (use calendar button in the bootloader).

You guys are great read the submerged post by my earlier on the result fixed mine also.
GID CODE 0000000
it think it must be the default.
just made a call
Thanks BTW Will try and leave my xda alone for a while
= SUBMERGED =
it it works, - leave it alone
it is doesnot ask

Hi Peter Poelman ...
You may (at your very own risk, I've never done this!!!), try the GSM Debug/Calibration mode from the bootloader. I've always been curious to see what it does, and in your case it may actually do some good
Click to expand...
Click to collapse
Actually, during doing RSU upgrade to a friend's XDA, since it didn't work from the first time, I selected this function from the bootloader. It kept the XDA veryyyy slow with a mark on the phone signal as if there is a continues call running. I couldn't stop it except by a hard reset, then applied TMO R6.24 and then it worked fine.
I 'm not sure it's just a coincedence or it was THE reason that made the new RSU works

WHY ME??

First of all, I'd like to say this is the most positive and progressive forum I've ever joined on the internet so far. You guys not only rock, but also inspire, for which I would like to add to the THANK YOU chorus!
I have spent days and sleepless nights browsing this forum, trying to unlock my T-mobile MDA.
The details are:
-T-Mobile (USA)
-ROM Version: 3.14.40 ENG
-ROM Date: 11/26/02
-Radio Version: 6.18
-Protocol version: 324e4
-Model No.: PW10B1
-IMEI: 35031400086966009
I'm using the USB via the cradle. The XDA unlock gives me an error reading, which is not uncommon elsewhere in this forum. I had to download the SER v 1.2.
Upon download and installation, I copied (via OSImage Tool)as per instuctions and ran programme A, only to get the "error message 007 ....No ROM image file".
At this point I'm pretty exhausted, especially when I see other posts of people who successfully unlocked theirs. I give up on foguring it out myself, so I please need help. Apparently, I'm a total rookie in this field . It would be highly appreciated if someone can be kind enough to please give me a step-by-step guide on the entire process either by replying to this post in this forum or by anyother means to contact me (e-mail, IM, etc) through my profile. I'll have a great sense of achievement and happiness gaining my freedom by eventually unlocking my device this weekend before my trip next week.
Thank You and I appologise to anyone that might be offended by the length of this post :wink:

You can run the file from your desktop, make sure you are synced with the xda, it will update the rom through the usb port. Before you do this it would be a good idea to back up your current rom using the sd bootloader method. Once the special edition rom has completed, just poke the unscrewed top half of the stylus in the hole on the bottom right of your xda, just poke once, wait one minute then poke again. You should tehn have an unlocked xda, you can then restore your original rom by inserting the sd card with your original rom, entering bootloader and pushing the action key when prompted.

Thanks for the response. OK, first, what ecxactly is the bootloader and the "bootloader method'?
Secondly, I tried running the S E ROM and keep getting the error message relating to its inability to find the ROM image.

Where did you download from, what size is the file? The bootloader method is accesssed by pushing the reset with the stylus while holding down the power button, then press the top left key on front of xda, you will see options there, you will not see these options when you restore a ron from sd, all you need do is enter bootloader, the xda will ask if you wish to program the rom, you press the centre of the 4 way jog button and away it go's.

I downloaded from:
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
It seems to be a 15.4MB file

The file size is correct, you should be able to sync your xda, click on the special edition rom .exe file and it should install to your xda using program a, there is need to use any other tools, as\long as you have a backup of\current rom you have a way back to your original configuration.

I have just downloaded and executed that same file, the first thing that comes up is winzip self extractor, once it has unzipped itself a dos box pops up, it then jumps to program a and commences the install, make sure you are running the file direct from the directory and not from a shortcut, it definitely works.

I did that and I keep getting that bewildering error code 7. Again, I tried unzipping the file first and then run prog A. It went fine until after step #3 then error code 12 pops up: "ROM image is not compatible with my device.............. download utility nd try again...."
This thing seems simple and works for everybody else but me :evil:

at this point, you should use winzip or winrar to extract a file named nk.nbf frim the exe you downloade. then to either use the XDAtools to copy it directly to your XDA ROM, or move the file to SD card using your xda then use the SD flashing method from the bootloader.
good luck ...

Good news & Bad news ...... I was able to run the SER prog. First, I ran the adaptrom file and then programme A. Everything was proceeding fine until it was about 50% and then my system (desktop) froze/crashed. I had no choice but to restart the system. Now the XDA screen has a display with a progress bar and the message: "Upgrading........ It will take about 5 mins.........."
It seems its a curse :twisted: but since I've made some progress, I cant give up now. So I'm determined to succeed by fixing this stuff. My question is Can someone please tell me where to go from here??????? As usual, your patient and kind response is highly appreciated.

Oh, I forgot to add that in addition, now ActiveSinc cannot establish communication with my device, even after restarting it several times and trying to get connected via its program

hey ... no big problem ... relax!
you have to get SD reader/writer and connect it to your PC. move the extracted nk.nbf file to the SD card then insert it into the XDA. goto the bootloader mode (power + soft reset) it should recognize the card content ... just press the middle of the rocker key (action) and you will see hex counter increasing from 000 to 200 ,.. at the end, press hard reset and after 60 sec press hard reset again.
note: make sure your XDA is > 80% charged before start!!
good luck.

Didnt Work
Did exactly as you suggested, but ending up with the same screen "uploading..... It will take about 5 minutes..." :?

Finally made it!!! Thanks guys for all your input. Device works fine, so far, I dont seem to have lost anything! I feel FREE, excited and victorious!!!! YEAHHH!!!!!

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!

First time flasher, ROM dump possible before flash?

First of all I feel obliged to say I'm sorry for creating a new thread just for these basic questions.
I have read the FAQs and searched through the forum, and it's a bit messy hence this thread.
First of all I want to have the security to be able to revert to the stock ROM in case something goes wrong.
1) I do not find any SWE-rom in the collection thread though. My question is, can I (or someone help me to) dump my 1.43 SWE rom?
Edit: Just found this link by chance in duttys signature:http://rapidshare.com/users/258XUJ
And the swedish rom is included here. I wonder why this is not included in the sticky thread (..........)
2) If I flash to a custom ROM with SSPL, can I flash a stock ROM back with SSPL or do I really need to go through all the hassle with the gold card etc? Is there no easy way to flash an official ROM?
3) If I use HSPL to upgrade my bootloader, my warranty will be affected if I'm not mistaken. Could HTC (or whoever who performs service) deny my phone because I've used HSPL from here? If so, is there any way to revert to the state before using the HSPL, that is to say load the previous stock bootloader?
Once again, if you find this thread unnecessary please just ignore it and let it die or delete it.
I did some searching and still had these questions left, and I'm in the middle of studying for an upcoming exam while my HD2 is pissing me off since my last (and first) hard reset (the WiFi is really bugging out).
So I hope this will save me some time (and maybe other newbies)

I'm not sure if there's a way to actually back it up, but u should be able to get the official one off the htc support website. htc.com/support
using sspl is only for custom roms, but hard spl is now available. it let's you flash anything.g..custom or official.

Thx for the reply,
The swedish rom is not available there unfortunately. Hence my problem.
Regarding the HSPL, I have another question:
3) If I use HSPL to upgrade my bootloader, my warranty will be affected if I'm not mistaken. Could HTC (or whoever who performs service) deny my phone because I've used HSPL from here? If so, is there any way to revert to the state before using the HSPL, that is to say load the previous stock bootloader?

I'm not really sure about hard spl yet..I've not had a chance to read about it..or needed it.
i think you can revert to original spl by using goldcard method...and with this, your warranty still intact... but just read about it in sticky to be sure.

tshizzle said:
I'm not really sure about hard spl yet..I've not had a chance to read about it..or needed it.
i think you can revert to original spl by using goldcard method...and with this, your warranty still intact... but just read about it in sticky to be sure.
Click to expand...
Click to collapse
You don't mean reverting SPL but flashing official ROMs right?
I did not read anything about the goldcard changing SPL?
Now that question 1 & 2 have been answered only question 3 is left.
A way to revert the SPL in case something happens and I have to send it for repair.

Only way to remove the HSPL is to flash an original SPL from SD card.
- Take any "RUU_signed.nbh" from a ship ROM and copy it to SD card.
- Rename it to "leoimg.nbh"
- Reset the device while pressing the volume down button.
Click to expand...
Click to collapse
you're right...it is flashing original rom...but that removes hspl.
i think you should just read http://forum.xda-developers.com/showthread.php?t=611433cuz i haven't...and don't think I'm qualified to give advice..

tshizzle said:
you're right...it is flashing original rom...but that removes hspl.
i think you should just read http://forum.xda-developers.com/showthread.php?t=611433cuz i haven't...and don't think I'm qualified to give advice..
Click to expand...
Click to collapse
I see, that one I had missed. So it should be realitvely easy to restore both the SPL (by following the steps you quoted, no gold card needed) and the stock rom if one has HSPL, as long as one has the stock ROM (which I'm downloading atm )
In that case this is great news, I'll be ready to start flashing in no time

I dont get it. I downloaded the stock ROM from the link provided above, it is an exe-file. Just like an official rom release from HTC.
Does this mean that I can install a custom ROM with SSPL and revert to the stock ROM simply by running the exe-file while the phone is in ActiveSync, without any need of using goldcard/HSPL?

umiss said:
I dont get it. I downloaded the stock ROM from the link provided above, it is an exe-file. Just like an official rom release from HTC.
Does this mean that I can install a custom ROM with SSPL and revert to the stock ROM simply by running the exe-file while the phone is in ActiveSync, without any need of using goldcard/HSPL?
Click to expand...
Click to collapse
You need to extract the exe to get the nbh-file that you use to flash with SSPL. Just right klick and extract it, put nbh ans SSPL in a folder and run SSPL. Simple as that

Thanks alot for the help. I am ready to flash away

Confused....
Rather than creating a new thread I thought I'd post in here about a rom dump - and the troubles I'm having. (hope that's ok)
I'm trying to dump my official stock HD2 rom but something's not going right.....
I want to do this to have a backup before I start flashing custom roms and to also share it as I noticed it is not on the list in the sticky thread.
I'm using "dump my phone" which I found here:
http://forum.xda-developers.com/showthread.php?t=509708
Everything seems to run ok, but when I run the final part I get the following errors:
CopyTFFSToFile(0x0, 0x520000, Part01.raw)
ERROR: ITReadDisk: outbuf==NULL
- The device is not ready for use
CopyTFFSToFile(0x0, 0xdd80000, Part02.raw)
ERROR: ITReadDisk: outbuf==NULL
- The device is not ready for use
I found another site with details on how to backup the stock rom:
http://www.planete-htc.com/index.php?mod=forum&ac=voir&ref=30&cat=282&id=22438&debut=0
(It's in french but I could understand most of it) but I continue to get the exact same error as before.
I've tried on 2 different computers (XP & vista) but no joy. Can anyone please provide some advice on what could be causing the problem?
I'd really love to be able to backup this rom.
Thanks.

aushtcuser said:
I've tried on 2 different computers (XP & vista) but no joy. Can anyone please provide some advice on what could be causing the problem?
I'd really love to be able to backup this rom.
Thanks.
Click to expand...
Click to collapse
Hi, I successfully dumped my raw rom using this
http://forum.xda-developers.com/showthread.php?t=427507
process.
the thread reffers to the raphael, so the numbers that are generated during the process (the coloured ones) are different, but take it slow, its an easy step by step.
Once the raw files are dumped, you will, then need to figure out how to rebuild them, but i 'think' kitchens can be used for that.

Why don't you guys just download the officially released stock ROM? In my case there was none to download (or so I thought) hence I started the thread. Later on I found link to the official ROM so I started flashing immediately =P

umiss said:
Why don't you guys just download the officially released stock ROM? In my case there was none to download (or so I thought) hence I started the thread. Later on I found link to the official ROM so I started flashing immediately =P
Click to expand...
Click to collapse
hehe, and thats why i never got around to figuring out the converting of teh raw dumps, I found my stock rom.

what if you need a stock rom that hasnt been uploaded to the website??
I'm still interested personally in converting the raw dump to a .nbh installable via hspl.

chris_ah1 said:
what if you need a stock rom that hasnt been uploaded to the website??
I'm still interested personally in converting the raw dump to a .nbh installable via hspl.
Click to expand...
Click to collapse
Go have a read of the thread i linked above, as i said, I dumped the raw files easy enough, and the rest of the process of reconstructing should be the same, although of course you will have to use leo source files and what not.

samsamuel said:
Hi, I successfully dumped my raw rom using this
http://forum.xda-developers.com/showthread.php?t=427507
process.
the thread reffers to the raphael, so the numbers that are generated during the process (the coloured ones) are different, but take it slow, its an easy step by step.
Once the raw files are dumped, you will, then need to figure out how to rebuild them, but i 'think' kitchens can be used for that.
Click to expand...
Click to collapse
Thanks for the help......the methods in that thread are very similar to the ones I've already tried. I have everything copied correctly to my device, found my address codes, but whenever I run this line:
“pdocread -w -d DSK1: -b 0x800 -p Part00 0 0x31f000 Part00.raw”
I get the same error as I mentioned previously - the device is not ready.
I've tried enabling/disabling faster activesync connection but still the error occurs.
umiss said:
Why don't you guys just download the officially released stock ROM? In my case there was none to download (or so I thought) hence I started the thread. Later on I found link to the official ROM so I started flashing immediately =P
Click to expand...
Click to collapse
If I could find this exact version I would've done that by now, but I can't find it anywhere ROM version - 1.48.421.2 WWE

Hmm, three things to check,
1, the number 0x31f000 are you sure thats the right one, give as teh output of the "procread.exe -l" command? (Just checking you arent just copy/pasting teh thread commands)
2, are you using am external usb slot? i've found hspl doesn't instal over my usb slot in eth case of my machine, but does when i plug it into one of the slots directly on the motherboard, , maybe this is teh same?
3, is itsutils.dll running? is there a popup on your mobile with 'allow this program?' or something similar?

1 - I just copied/pasted what was in the thread, but I just ran the pdocread.exe again and it is the same address.
2 - I'm using a laptop but I've never had any connection issues with it previously.
3 - Not sure if that process is running. Nothing appears on the phone to confirm it.
Here's a really stupid question but am I meant to be doing this after I install HSPL? I haven't done that yet as I thought I could backup the rom beforehand.....

aushtcuser said:
1 - I just copied/pasted what was in the thread, but I just ran the pdocread.exe again and it is the same address.
2 - I'm using a laptop but I've never had any connection issues with it previously.
3 - Not sure if that process is running. Nothing appears on the phone to confirm it.
Here's a really stupid question but am I meant to be doing this after I install HSPL? I haven't done that yet as I thought I could backup the rom beforehand.....
Click to expand...
Click to collapse
No, no need for hspl here.
OK, you changed the HKLM\Security\Policies\Policies setting, you soft reset. (Power propperly off and back on), you copied over itsutils.dll and moved it to /windows.
Next step is opening command prompt, did you open it as administrator?
oh wait, in your command
“pdocread -w -d DSK1: -b 0x800 -p Part00 0 0x31f000 Part00.raw”
are you sure it is DSK1:?
Cos im failry sure mine came out at DSK7 or something, pretty sure it wasn't 1...