Database Users

Burning ROM - phone not working

Hi, I'm hoping to get some help with cooking and burning ROMs to my o2 XDA.
My original product specs are:
ROM Version: 3.20.06 ENG
Radio version: 4.21.01
I cooked and then downloaded 4.01.00 ENG from Lumpi Stefan's site, then ran the rom.exe file that it produced for me. Everything worked fine, and then I rebooted my XDA. Upon first boot the phone appeared to work, but after performing a soft-reset because the XDA froze, all of the phone functionality appears to be not working.
When I do a hard-reset I get: Wallaby Bootloader v6.22 - GSM OK which I think looks good as far as the phone functionality is concerned. Looks like it's the OS that's on the XDA which is causing the phone difficulties.
I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started!
I don't have an SD card, and am in dire straits about getting my phone to work. Is it possible at all to get this to work, or perhaps to go back to my original ROM (I backed it up to orig.nb1) using XDAtools. Anytime I try to burn the .nb1 file back to my XDA it fails. Or is the ONLY way to get an SD card and use the Bootloader technique? I even tried downloading the 3.17.03 ROM upgrade directly from the o2 sitebut it fails.
Any help will be GREATLY appreciated.
Thank you.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![/qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![\qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.

Thanks, I will try. ActiveSync still works...
I notice you are running the same ROM version as me - sis your radio still work?

Can you verify that I am trying to Flash the ROM correctly?
1. Confirm that I have orig.nb1 - yes, it's there - backup of original ROM before I started this whole dilemma.
2. Ensure that XDA is Activesync'd - yes, as "Pocket_PC" - all working okay.
3. Right click on orig.nb1 and select "burn"
4. OSImageTool.exe then pops up and copies orig.nb1 to Programme A.
5. A DOS box then appears saying "ERROR: GetConnectionType - A
ote host. error getting connectiontype".
6. Programme A then runs and after pressing "next" a couple of times, I get an error - "Error 011: Cannot execute the remote communication program. Pleace make sure that the USB cable is properly connected."
And that's basically it.
I have tried different variances of this, but all without success.
Help!
BTW, I'm logged in to MSN Messenger now, could you let me know when you're online - or anyone else, for that matter. My address is [email protected]

This message means that the current ROM in your XDA can't be flashed through Program A ... not a big issue, for unknown reason it happened with me few times ... but now you have to use SD card to flash your ROM.

Here is an update...
I have played around some more with the XDA with no success. I have now bought a 64MB SD card and am unsure as to how the ROM image on my PC gets onto the SD card. This is how I have been doing it:
1) Insert SD card into XDA
2) Place XDA into cradle
3) XDA then ActiveSync’s to the PC
4) Run OSImageTool.exe and select the following –
a. Source: “C:\Documents and Settings\Paul\Desktop\orig.nb1”
b. Destination: “XDA SD card slot – unknown size”
5) Then I press “copy” and I see the progress bar go across to 100%. After this appears to finish, the program just sits there not telling me it’s finished. I assume that it’s all okay and I then close the program
6) Take XDA off cradle and hold power button down whilst doing a warm-reset
7) The following appears: “Wallaby Bootloader v6.22 – GSM OK” – nothing else happens, and from what I have read it is supposed to ask if I want to perform a ROM upgrade. However, I can get into the diagnostic and flash tools by pressing the action button etc, but nothing is in there to upgrade the ROM.
Does the fact the OSImageTool destination says “XDA SD card slot – unknown size” matter? I’m assuming not because when I have transferred the ROM using the above steps, the XDA asks if I want to format the card; meaning that the transfer worked okay. Do I have to have an SD card reader/writer on my PC to get the ROM onto the SD card?
I have read a little about a Bootloader patch – do I need to run this, and how do I get it onto the XDA – using the same method?
I would be very appreciative of any help that can fix this, as all I want to do is get my three-day old XDA working again!
Any other comments and help in relation to solving this hair-challenging issue would be great!
Thanks,
Paul…

Ok ... from what you wrote it seems your doing it correctly. However, I have doubts on the file orig.nb1 you are using ... maybe it wasn't copied properly.
Try to cook any ROM (TMO 4.01.00 is good) at Stefan kitchen and you can cook it as .nbf or EXE then extract the .nbf file using winzip or winrar.
Follow the same steps and let me know.
Good luck ...

Is bootloader v6.222 okay - will it allow me to overwrite my current ROM with this new ROM that you are suggesting? I have read that I may have to downgrade my bootloader to do the SD ROM writing thing.

I can't confirm that my self ... I used SD with 5.17 and 6.22 without problems but maybe it's my luck
Cook the 4.01.00 as EXE and try it as is or extract the .nbf file and use the SD method.

Okay I'll give that a go now... Will let you know how I go...

Nope - didn't work. I'm not getting a screen in the bootloader to update the ROM via SD - if I press the action button I get into dignostics...
Is this a bootloader issue, and if so, how do I downgrade?

Also just tried the following:
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
And got the following error message:
Unable to find flash info offset, cannot disable bootloader writeprotect
Any ideas?

I don't get it ... you cooked and downloaded and tried a new nbf file for TMO 4.01.00 in less than 15 minutes ??!!!!
what is the nbf file size ??

Yes, I used Winzip to extract NK.nbf. It is 31,745kb.
I am now cooking on Lumpi's site a zipped NK.nbf file and will try that too...

ROMs and getting it onto the PPC

OK I have the tmo PPC its already got 2003 on it and I know the loader is 5.15, other info that might be needed.
ROM 4.01.16 ENG
Radio 6.25.02
OK I want to get my own cooked ROM onto this, I know I know use the SD card method, well I don't have one and after getting this thing can't get one for a while either. I have the cradle that it comes with and have put software into etc, I have tried some unlock ROM software to find it didn't work etc etc. after cooking ROM and running it it tells me in a DOS window:
Error getconntiontype - An Existing connecitonwas forcibly closed by the remote host.
error getting connectiontype
so basicly I need to find a way to get this into my PPC via activesync or something. sorry for bad post a little tired but I think people will understand and be able to help me or tell me I need SD card and wait until I get one.

I think you can use xdatools to flash the rom direct from xda memory, choose the nbf file as source then choose the xda device memory as destination from the drop down box in destination section.

OK tried that but can't access the PPC with xdatools so that won't work. thats for trying though.

TMO ROMs are known to resist exe flashing ... use the SD method and you are lucky to have the boo loader 5.15

Well glad to know that my boot loader is a good one, now to find a SD card I can borrow to do this with, should I use a 32 or 64 or does it really matter as long as it holds the file.

64 megabytes is needed really, I have had a problem with 32 meg, it looks like it is programmed but when i flash it there is always a problem.

macgyver33 talked about having a 2003 version. Can anyone tell me where to get it? I mean european one (900-1800 MHz). Or at least the PDA part of it? And yet haven't found quiet an exact explanation of "SD method" - any suggestions? Thanx a lot!

Bootloader v.5.17 locked
BL v.5.17 + TMO ROM. I am not able to downgrade the bootloader or change ROM.
I've tried using:
Cooked ROM.EXE - No way
(Error: GetConnectionType - An existing connection was forcibly closed by the remote host. Error getting connectiontype)
XDA OS Image Tool - No way
(Error: Same as above)
ITSTools - pnewbootloader - No way
(Error: Unable to find flash info offset, cannot disable bootloader writeprotect)
SD Method - No way
In bootloader mode (soft-reset while pressing on/off button), I have no options: Even with an SD card with OS image inside, there's no way to start ROM download as there is no option to choose...
Any idea?
Thx

Check this thread

Thanks Biso007.
No way. My XDA doesn't load the bootloader in a proper way:
1. Inserted th SD card in his slot
2. Answered "No" to format the card
3. Soft-reset while pressing on/off button (so to enter in bootloader mode)
4. Display turns off
5. No Wallaby Bootloader screen, so no action to take...
6. Wait... Nothing.
7. I've also tried to press the "Action" button so to start the SD downloading... Nothing
8. Wait... Nothing.
6. It needs another soft-reset to exit this state (a not working bootloader mode, I suppose)
7. It turns on "normally".
Any further idea? :-(
Thanks

if I'm not wrong, I couldn't see that you ran the 5.17 patch first ... without it your device will never detect the SD file ... chech the thread again

Ther must be a way for UNBRICKING

Hi, I searched a lot on forum and found a way for flashing from sdcard in Hermes forum.
There for i took a RUU_signed.nbh file copied to the fromated SDcard
- renamed it to HERAIMG.nbh (similar to HERMIMG.nbh on hermes forum)
--> and put the phone in bootloader
--> it starts searching sdcard
AND THEN
--> a processbar appears and it says "Checking SD contents"
BUT
--> "Invalid Certificate" - press any key.
So there must be a way to flash from SD card.
I will try different RUU and tell more.
Someone wanne help?

It must be named
"HERAIMG.nbh"
then it stops on white screen saying: Checking SD contents
But i got
Invalid Certificate

AND when it is an official .nbh extracted from RUU_xxxxx
it stops for 5sec on
"Checking SD content"
but the processbar doesn´t change and then it goes to bootloader without changing anything.
????????????????????????????

I will test this method too, i saw some flash of SD hen going into bootloader mode, did'nt know there was an option like this i will post my experiences

I tried these two RUU nbh's:
- RUU_Herald_HTC_WWE_5.4.405.1_4.1.13.34_02.79.90_Ship
- RUU_Herald_HTC_WWE_1.8.405.1_02.71.90_Ship
I've firtstly formatted my SD card, then copied NBH file's to my SD and named them HERAIMG.nbh.
Both times there was only a statusbar that did not proceed loading, and my continues in bootloader after 3 seconds...
Also got the Invalid Certificate error when I copied the WM6 nb of ASerg and renamed it to HEARIMG.nbh.. what is this certificate? and can it be edited in a way so we can flash??
Talking about unbricking anyway, can Herald users use Platform Builder?? i read in a thread that you're phone has to have KITL, but i don't think the Herald has KITL.. Can anyone who knows for sure please tell?

The Dutchman said:
I tried these two RUU nbh's:
- RUU_Herald_HTC_WWE_5.4.405.1_4.1.13.34_02.79.90_Ship
- RUU_Herald_HTC_WWE_1.8.405.1_02.71.90_Ship
I've firtstly formatted my SD card, then copied NBH file's to my SD and named them HERAIMG.nbh.
Both times there was only a statusbar that did not proceed loading, and my continues in bootloader after 3 seconds...
Also got the Invalid Certificate error when I copied the WM6 nb of ASerg and renamed it to HEARIMG.nbh.. what is this certificate? and can it be edited in a way so we can flash??
Talking about unbricking anyway, can Herald users use Platform Builder?? i read in a thread that you're phone has to have KITL, but i don't think the Herald has KITL.. Can anyone who knows for sure please tell?
Click to expand...
Click to collapse
The .nbh are "signed" os files. you can generate these fiels by "nbhgen.exe" but i didn´t get it to work with an RUU - it allways says "image is corrupted" because it only contains OS.nb
when you extract an RUU_signed.nbh out of the RUU_xxx.exe it contaisn splash.nb, os.nb, extrom.nb, spl.nb etc.
That´s the certificate = the singend nbh

So that won't be an option I guess... too bad
but does the Herald have KITL in bootloader mode? if so, you could use Platform Builder to unbrick your phone.. that would be very very sweet.
And what is this mtty thing? should be some funky stuff to

The Dutchman said:
So that won't be an option I guess... too bad
but does the Herald have KITL in bootloader mode? if so, you could use Platform Builder to unbrick your phone.. that would be very very sweet.
And what is this mtty thing? should be some funky stuff to
Click to expand...
Click to collapse
MTTY never worked for me - but that could be my system. And KITL - i don´t know what this is. sorry.
I sent it to O2 and hope they will repair some minor bugs and also the booting problem.

Little thready about unbricking a Hermes with KITL + Platform Builder:
http://forum.xda-developers.com/showthread.php?p=1162054#post1162054
Hmm i'll have a look around to find out what this mtty thing does..
btw: KITL = Kernel Independent Transport Layer, it is the windows ce kernel debugger interface

Is there anyone continueing papamopps' solution to unbrick Herald?

^^no need anymore, you can just use an official WM6 RUU

blackout203 said:
^^no need anymore, you can just use an official WM6 RUU
Click to expand...
Click to collapse
That´s not right. For unbricking a XDA Terra we still need a soulution.
The Terra IS NOT the P4350!!!!!
And the RUU updates are for P4350 (and in some cases for VPA compact)
But not for terra - we have to wait for an O2 update....

Vendor Id
I have a Vodafone CID(?) locked bricked HTC P4350.
Using the HTC updates I cannot unbrick my phone, because it keeps saying "Invalid Vender Id".
This unbricking with flashcard could be a solution for me.

I already try with official rom, but my herald is still brick, i can not syncronize the herald with pc to run the official rom.
It is freeze in inicial boot with HTC logo.
help, please anyone....

You can't simply place the rom file to the card and hope the device will read it in this way. In my time working for pda service, we used WINHex to format the card (to RAW-unformatted) and then we wrote the rom file in RAW format to the card. Your card looks like an endless stream of hexazecimal values. Only winhex recognises this format, if you insert the card to the computer, it will simply ask you to format it. After inserting this card into the pda, it will start the upgrade . The order of this operation was, as I remember, to fill the card with 0000 values (there is an option in WINHex, a kind of format) then write the rom file to the card in RAW mode. Then insert the card to the device.
Another way was to use MTTY, connect the pda to the computer (PDA should be in bootloader), open MTTY and connect with the device. ActiveSync should be killed before this. In MTTY in the terminal window write "set 14 0" then remove the data cable, then close MTTY, reconnect data cable then run the RUU.
These methods worked on HP Ipaq's wich we were repairing in our service center some time ago. I don't know if it works for herald or htc products because their RUU has a different way to register with the device.

Stuck on bootloader menu after error upgrading ROM

Help,
Is there a way to get the OS and boot img for my o2 XDA to put on my SD card so i can recover it?
I'm stuck on the boot-loader screen (version 5.22) i can not use active sync as it comes up as unrecognized device, im at my wits end, i just want to get my phone working again. is there any place i can get the O2 ROM file from? or anything that can be done, or do i have a useless brick now?
i tried upgrading with the developers ROM using the auto install, it got to the "it will take 5 mins to upgrade" screen then active sync lost connection, there was nothing showing in the progress bar, when i tried to restart, active sync could not connect. now im stuck with the boot-loader menu after a soft reset.

Sorry for the double post,
Right sorted the problem out, got a cooked ROM from a different site as no link i clicked on here was still active.
I found out that if you Format the SD card to Fat32 when in bootloader it doesn't recognize the ROM, so a format to just FAT under windows XP sorted it out, and now I'm back up and running again, though now i cant get my phone unlocked to Vodafone as the XDAunlock returns "error getting code" message. here are my Device info
Rom version 3.17.03
Radio version 4.21.X1
Protcal version 32S54

problem resolved by updating the Radio stack to 6.24 (placing the files onto the device and upgrading from there) once that had done, i had no signal, so downgraded it back to 4.21 and now I'm fully functional

Where did you get the ROM?
I have a similar problem with an XDA which failed whilst being flashed via active sync and now will not start apart from via bootloader. Where did you get the ROM that you mention please?
Thanks
Geezer

use this ROM from http://www.romkitchen.de/ choose one that u will use to cook, PC2002 or WM2003/SE, (WM2003SE cannot use SD Card, only can use activesyn) then downgrade bootloader from v5.22 to v5.15,
using MMC (flash SD) continue to special rom 1.2, Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button if when you get to the bootloader screen you see nothing more than some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader. Bring up XDArit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'Wallaby' in the hex codes at the bottom of the XDArit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT). Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.' Type 'pnewbootflash_40116 nbl515.nb0' to write the Wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0' you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
for the complete, read this web :
http://www.romkitchen.de/
http://www.romkitchen.de/tools/
http://www.romkitchen.de/tools/manual_unlock.htm
*read careffuly and try it, you can read my post, almost similiar problem but i can solve it by read one by one,hehehhe.. never give-up, ok ^_^V

any help with magician rom?

OK I found this thread and this is what I need to do but I don't follow any of this. what is the ROm image and how do I cook? I'm totally lost and My phone is wrecked or bricked as you say???

Htc 0300 in tri colour

I have a HTC ELF 0300 it is stucking in the tri colour screen with the following
IPL: 2.26.0002
SPL:2.28.0000
i have followed the advice i found on this forum of flashing the ROM but when i try the rom update utility it comes up with error 270 about the image also i tried the mtty process but it wont open the usb port
i tried flashing the SD Card but it then says "Invalid Certificate"
i'm a total loss and totally stuck..
any help appricated

Have you really read this sticky thread http://forum.xda-developers.com/showthread.php?t=406721 before flashing ?
Have you used "search" function with f.e. "stuck in bootloader" before posting ?
If not, please do and you'll find very useful solutions

i have read the theads over and over again and finally worked out mtty and worked out my phone is
elf0300
tmob050
it's still in tri colour mode yet i cant find a rom for it...
i tried the nbh file flashing to the memory card
but no luck....
heelllp

Do you know if you have Elf or Elfin?
It is essential for flashing original Rom Elf: http://forum.xda-developers.com/showpost.php?p=2045325&postcount=2
Elfin: http://forum.xda-developers.com/showpost.php?p=2045051&postcount=1

i haave an elf (p3450) well thats what it says on my box
i cant find the orginal rom for this and i'm totally stuck
any help is greatrully recived
also i have tried CID unlocking it so i can put custom roms on it but my computer wont active sync when the phone is connected through the USB port...

Also, what did you do to get your phone stuck in bootloader in the first place?

my brother did it to my phone before i'd even had chance to use it , and i don't know what he did.....sorry x

Try this and follow the instructions exactly http://forum.xda-developers.com/showthread.php?t=347700 and report pls

i tried this yesterday at first when i pressed enter i didnt get >cmd (which is what happening now)
then when i do get it eventually after many tries it sasys
cmd55 or something failed
and stays on 0% on a gray screen
sorry if i sound stupiud.

Ok
First you connect your device, then right click on active sync icon on your computer, chose connection settings and change according to the instructions then continue with mtty.exe

i have done this
when i press enter i dont get anything come up....
yesterday i managed to get it up though and just stayed gray screen at 0%

Try again a few times making sure you didn't overlook any detail.
I just found this http://forum.xda-developers.com/showpost.php?p=3395787&postcount=155 possibly mtty version doesn't work
2- Another possibility is unbricker rom http://forum.xda-developers.com/showthread.php?t=446242
3- gold card method (the links are dead so you should pm Dsixda)
Flash from the SD card:
ELF0IMG.nbh on a FAT32 filesystem, complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
1. Format microSD card from your computer.
2. Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract.
3. Rename the .NBH file to ELF0IMG.nbh and copy it to the root folder of your microSD card.
4. With microSD card inserted in the phone, start the bootloader (the bootloader is invoked by hold down the camera button and reset device with the stylus).
5. Confirm flashing on screen by pressing the power button (or the volume slider down).
6. Flashing might hang after some time but this is normal. Just wait.

Will try now and keep u updated
manny thanks x

Follow the instructions until you get cmd only, then return to the tutorial to continue
Good luck

Just an update
i downloaded the nbh file you sugested and tried both
1) flashing from the SD card by renaming file - when i do this is says checking sd contents then goes back to my bootlooder screen
2) running the romupdateutility.exe with the nbh file in the same folder it goes through then i get error 294 incorrect vender
i am unable to pm Dsixda about the gold card
i have no idea what else to try
ps: when running mtty i still get a gray screen then the bootloader screen.

Sorry to hear this, I'm out of ideas. Just some details not to miss:
try a hard reset
writing "ELF0IMG.nbh" (elf zero img and not elf o img)
google for mtty and download a few versions
Wait for an answer from Dsixda for gold card if you can't find your original rom

Creating your GoldCard
I don't remember well the procedure but you can try the following:
If you have access to a working pda or a working GPS device - PNA which is powered by WM (even modified) then you have to follow these steps:
Download this package and save it in your C:\ drive.
Run it.
(it will extract all the necessary files in C:\itsutilsbin (folder) and it will start the setup of Perl)
When the Perl - installation is finished run Perl Package Manager from Windows Start Menu.
Add repositories.
Name: itsme
Location: http://www.xs4all.nl/~itsme/projects/perl/ppm
Name: theoryx
Location: http://theoryx5.uwinnipeg.ca/ppms/package.xml
(HowTo: run Preferences from the Perl Package Manager menu and switch to the repository tab)
After database synchronization install these packages:
Crypt-DES
XdaDevelopers-NbfUtils
(HowTo: at the main window of Perl Package manager find those packages, mark them for install (the icon with green plus, next to the search bar) and run marked action(green arrow icon))
Format the sd card(FAT32) and insert it in a working pda.
Connect the working pda to the pc , wait to sync and run psdread.bat from C:\itsutilsbin.
Find an official rom from here with a ModelID which matches your device's one
Example: If your pda is an Elfin and you have ModelID ELF030000 then get the below rom from that thread.
RUU_Elfin_TMO_NL_2.26.114.52_4.1.13.52_03.08.90_BL UE_Ship.exe (T-MOBILE)
Device: ELF030000
CID: T-MOB003
Version: 2.26.114.3
Language: NLD
Click to expand...
Click to collapse
Extract the RUU_Signed.nbh, rename it to ELF0IMG.nbh and copy it to the sd card.
Fully charge your battery, insert the sd card to your pda, enter bootloader and flash from memory card
(Confirm flashing on screen by pressing the power button (or the volume down button)).
If everything went ok then you can use a HardSPL or a USPL to CID Unlock your phone and update the rom with one of your choice.
If you don't have a working pda use a card reader - Ubuntu (even from a LiveCD) and QMAT are required
Regards!

i don't have a working pda to use :-( the only pda i have is my bricked one :-(

buncie2010 said:
i don't have a working pda to use :-( the only pda i have is my bricked one :-(
Click to expand...
Click to collapse
There is a way to use a card reader instead.
Using Ubuntu LiveCD and QMAT
ps:I wonder how did the wiki entry got erased?
Dsixda and all the members who worked on this had done a great job and it's really annoying that all their work was lost.