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!
Related
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!!!!!
ok...I'm really new to all this so please show a little patience towards me!
I was trying to load the XDA-developers-SER-v12 on my phone and just when it started with the progress bar moving at the top of the PPC screen, when it said "Do not Remove Device..." I accidently lifted the phone out of the cradle as dumb as I am...! After that I tried to hard start it by shoving a pin on the hole in the right side under the battery icon with the cross (hard-reset) and got the Bootloader 5.17 screen with the three colors and GSM (OK) there when I pressed the soft-reset and power buttons simultaneously.
But since I was the idiot and could not understand what was going on, as I was not in this forum nor even behind a computer, I reset it again and again a couple of more times. Now present situation; I have the same "Do not Remove..." screen everytime I do a hard or soft reset even if I keep the power on/off button pressed alongwith pressing the hot or cold boot buttons on the left and right corners respectively. In fact the screen has gotten badly distorted but the same "Do not Remove..." comes up in the totally distorted state on the screen and the Bootloader or the colors, nothing comes up anymore.
When I try to put the phone on the charger, the light goes orange just as if it is charging, in fact, after an hour or so, just as it normally would in the correct phone state, it turns green.
Is my phone toast or can I still do something about it?
Munz.
I'm no expert, but it seems to me that if there is a complication with the software when loading, one should try using the sd method of rom flashign. Cook or dl a rom, use XDA tools to load it to an SD, put the SD into the device, and then use the bootloader to load off of SD. Other than that, I know little to nothing.
Good luck!
Search in the forum after SD Card flashing for the Wallaby.
This would fix your device...
HTH
Stefan
Re: Dead SX-56
You guys are good and quick....but!!! As I mentioned, I can't even see the Bootloader even after a reset and power button combo...nothing comes up or happens...the screen just blinks and then goes blank...should I open it up and disconnect the battery or something...? Right now I am just seeing the screen saying "Do not Remove...." and that even in a totally distorted form....
Try pushing a pin in the hard reset, push once only, leave it overnight, I think that is good as removing battery as it disconnects the connection between battery and mainboard as fas as I know. Next morning push once with oin again, you never know your luck. Its weird that the bootloader should be affected however the good thing is that your gsm seems ok and the xda is charging.
XDA Dead!
Thanks for the reply...I have just pushed the pin and am leaving the XDA in that state for the whole day...hope it revives back...its presently just giving me a garbled screen and nothing else...even when I press the power and hard reset together, it comes back to the garbled screen and nothing else...I'll take your advice and not touch it after the above for the day and let you know what happens, if there is any other advice I would highly appreciate it...
Bootloader Malfunction
You mentioned that your bootloader seems to be screwed up. Download the full version of XDA tools WITH the bootloader and Programme A. Grab yourself a new ROM of your choosing, lumpistefan's kitchen, etc. Then use the XDA tools to write the bootloader and the rom to your SD card. After that hard booting the device with the SD card installed should ask you if you want to flash the device.
I noticed that if you have XDA tools without the bootloader file it will write the rom to your SD and you will NOT be able to get to the flash your device screen.
This is the only way to do it since your device will not boot to a rom. Upgrades from manufactures and roms prepared with Programme A all require MS Active Synch AND a good working connection.
If you have a SD card prepared with the ROM and the bootloader the right way, it should almost be foolproof from what I understand.
Hope this helps, I was in much the same situation
XDA Dead!
Yups! I tried to boot it from an SD Card, its not exactly an SD Card but an MMC Card (128MB). It still comes up to the same garbled screen which is more garbled than ever before! Does not ask me for anything; or even confirms anything...It does not do anything else besides the screen even after a soft reset/hard reset or a combo hard/soft power button reset.
I'm really totally stuck...Any ideas will be much appreciated!
Thanks.
Your XDA is completely dead; you screwed OS ROM and bootloader.
Forget SD or Details method, it won't work for you!
Re: Dead SX-56
Can you help me fix it please? What do I need to do?
Bootloader
The more experienced members of this forum can correct me on this, but I have been under the impression that the SD method of flashing does not require an intact OS ROM or bootloader on the device.
If you created the SD correctly, it should contain its own bootloader. Just putting it in the unit and then reseting it should come up with the screen to flash the device.
Did you create the SD card with XDAtools? Did you also have the bootloader file in the /bin directory when you did it?
If a properly created SD "flash" card cannot fix your problem, then you really might have no choice to but to get it professionally repaired where the remove the chips themselves and replace them.
I think you may even be in luck. www.pocketpctechs.com probably can do this and they are located in Fountain Valley, CA about 4 hours away from you. They can also put in bigger memory and batteries at the same time at a discount if you are getting it repaired
Re:
Thank you so much for the reply...I will try it once more; although, yes I have tried the same thing before and made the MMC Card through the XDATools, but never hurts to try again...I'll double check on the bootloader again too this time...
If you can, please send me the contact information for the people who fix the XDA's professionally as you mentioned in the USA somewhere near me preferably, I am in San Jose, CA...I'll try to contact them also...
Best Regards.
Contact Information
Their website is www.pocketpctechs.com.
You can find all the contact information right there. As far as I know fountain valley is about 4-5 hours away from San Jose.
Similar problem:
I have a XDA I here, which has a similar problem:
It boots with the welcome to T-Mobile screen, and
it shows at the bottom of the screen 4.01.16 after a while R4.06 and after a while G32S54. The machine locks-up and does not respond to anything except the touch screen. If i tap the screen, the backlight turns on, and a
rotating 'wait' icon appears. That's it. I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD.
I guess the former user has tried to reflash the unit, and had put the OS overwriting the bootloader, OTOH, the unit seems to run *some* code, since it responds to taps on the screen, by turning on the backlight.
Any guru have any clue on this one? I could not find anything in the forums, while the forums are VERY helpful in the past.
GreetingZ,
Richard
Bootloader
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Re: Bootloader
ed207_us said:
<<I am not able to put it in Bootloader mode by pressing power - > reset, so i cannot reflash the unit using SD>>
I really do not understand that. I am not a Guru by any means, and I hope one does make a comment on this.
Click to expand...
Click to collapse
I also have a good working unit, and testing my SD card, created with XDARIT in this unit tells me i need to press power -> reset to be able to
flash the unit. if i do'nt hold the power button, the unit boots normally.
ed207_us said:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card.
Click to expand...
Click to collapse
It is there. 'press action to download ROM, or press record to exit'
ed207_us said:
<<
Only methods to backup the rom to the sd card. So I am really really confused to hear you guys say that.
I have successfully flashed XDA's with 2 methods. Programme A by which the XDA is connected to Active Synch 3.7 and by an SD card created by XDAtools.
Click to expand...
Click to collapse
I cannot connect the unit to activesync.
ed207_us said:
<<
Programme A only seems to work when there are NO problems at all and you just want to upgrade or try something else.
The SD card method seems to be the choice for repair.
Creating the SD card with XDAtools *WITH* the bootloader file in the /bin directory does work. The SD card I created with this method DID not, i repeat, DID not need the Bootloader (power-reset). It only needed to be powered on with the SD Card in the XDA.
Click to expand...
Click to collapse
I don' know the contents of the SD, since i created it a long time ago, but i really would appreciate is if you can email me a image of yours. Hope you are right and i can use the bootloader on your card to start this unit.
email size is no problem upto 100Mb
ed207_us said:
<<
If there are any Gurus moderating this post, I would sincerely appreciate having this cleared up
Click to expand...
Click to collapse
<<ed207_us wrote:
As far as a I can tell by my own experiences, you do not need to put it in Bootloader mode by presseing power-reset. That is totally unneccessary to flash the unit. In fact, in Bootloader mode I have never found any command or method to flash the unit from the sd card. >>
<<<RichardRosenberger wrote:
It is there. 'press action to download ROM, or press record to exit' >>>
It is only there when you have the SD card in the device, otherwise you cannot find it by moving around through the different menus.
XDAArit is completely outdated. You need to get their new tool.
XDATools can be downloaded from the website here. The best thread that talks about the tool is:
http://forum.xda-developers.com/viewtopic.php?t=2189&highlight=xdatools
The exact link to get the tool and all the supporting files, including the bootloader is:
http://cuba.calyx.nl/~jsummers/XDA/XDAtools-Jeff.exe
When you install this version of XDAtools you will find a directory called binaries. Under it there should be a file called "bootloader_v5_15.nb0"
Use the tool to create your SD card with a .nb1 file of your choice. After that it should only be a matter of powering on the device with the SD card inside the unit.
I have 2 XDAs. 1 good en 1 have problem with bootloader and rom.
I can't access Wallaby bootloader en the OS don't start.
I backup it from good XDA in the bootloader (ce+Boot) and i pushed my SD in the XDA where problems are..
He don't work. How can I fix my problem..
Please Help...
I am not aware of what the (ce+boot) actually creates on the SD card. If that is the exact ROM that you want, I would suggest downloading the full version of XDA tools, and I think you can use it to copy the ROM from the SD card to a .nb1 file on your computer. Then follow the instructions I have already posted to make the working SD card that will flash the XDA.
When it comes to the SD card, the only time I have ever been successfull is when creating it with XDAtools with a .nb1 file and the bootloader .nb0 file inside the binaries directory.
That's it. I have never been able to do it any other way. Programme A does not count since it requires an active and working OS and connection to the PC and most people that are in trouble don't have that.
I'm a newb in the sense that I'm new to the whole Windows Mobile Devices. As my location of this thread, I have a T-Mobile Wing.
I'm a current web designer and I'm learning to program/code. Especially for mobile devices first. So I am computer literate just a newb using roms, windows mobile in general. I believe I can follow on very easily.
I will edit this post to add the answers and explain them in more details, etc. as I learn them for future cookers/newbies/etc.
I have searched around the forums, learned a lot but still have questions hopefully some pro cookers could answer and maybe use this as a ref for all beginner newbs. I have the link to the wing/herald xda wiki/atlas, etc.
BUT STILL....
I'm on Windows Vista 64 bit. Maybe this is my problems? I take that into possibility. Within a week I'll have XP back on this computer as well.
[1]
I understand if your SPL/IPL is above 4.0+ you can hardspl your device. (DO NOT ATTEMPT TO HARDSPL YOUR DEVICE IF IT IS UNDER 4.0! IT WILL BRICK IT!)
I aslo heard of a uspl method where it hardspls your deivce JUST FOR THE NEW ROM YOU"RE INSTALLING.
I read that hardspl will hardspl your device forever but since then it's now reversable correct? Just curious about this, not a big deal either way.
NEWBS IF YOU WANT TO CHECK YOUR IPL/SPL VERSIONS : take your stylus out and soft reset your device by pushing your stylus into the small hole just under the volume slider on the left side of your phone and hold the camera button as it boots up until you see 3 grad colors. red blue, etc. it will then display your version numbers.
[2]
I wanted to learn how to cook, since I felt it wouldn't be too hard since I have a good background with computers, etc.
So.... I started following this thread:
http://forum.xda-developers.com/showthread.php?t=341243
I found a few others including the ones displayed with the hypercore download thread. But I stuck with this one as a first attempt and have not tried any others yet. I know I should but this one just bugged me, haha.
I did all steps accurately and did them again to double check...... but when I go to BuildOS.exe the top of the screen displays:
"the system cannot find the batch label specified"
Is this bad? I remember reading a long time ago about the format being unix and not dos, yatta yatta it would bring this error up but that can NOT be the possibility since everyone else has used this guys thread to create custom roms. Any ideas?
[3] (Cont'd from Question [2])
I also get some error trying to do step 2 in the BuildOS.exe menu, which is.... build OS.nb from SYS and Oem..... that error is file not specified... so i believe it has something to do with the batch error at the top, maybe? Ive tried this step 2 several times and actually got it to work and displayed new os.nb is saved in hypercore/build.... which i went there and didnt see it, but i see one inside the ROM folder... I assume this is the one I want? Perhaps?
[4] (Cont'd from Question [2])
When I try option number 3 in the BuildOS.exe menu I get this message
Save to desktop as........ as what? lol. I assumed the same name, leave it the same.... well the OS.nb was not at the location it specified. (hypercore/tools/convert) lol.
Again tho the save as problem.... I believe it all has to do with the batch file, it's like not fetching/displaying the file name.... if not it meant to leave it the same name? Anyway why is it not in the location specified?
[5]
This is what it displays after clicking enter, of course again no RUU folder found, I figured this with the previous errors. But heres what the flash option in the BuildOS.exe menu does err.... rather displays......
Again Place the _____ here..... still all the batch file problem?
[6]
Again dealing with this screen, is it ok that after Device: its blank? aka not displaying the propper htc model for the wing 3450 or whatever it is, I forget.
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.
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.