Database Users

T-Mobile Rom.... Can't do anything else... Help

Since updating to the T-Mobile Rom for my XDA, nearly everythiung has gone wrong.
And when I tried to downgrade it.... Nothing happens.
I used to use a modified Program A to upload it to my phone but it continues to say that the USB devide gets remotely stopped. the only thing that I can think is that my phone is cancelling the upgrade/downgrade.
I have also tried using a copy of the XDATools program to try and:
Upload another Rom.
Copy the rom to an SD card so I can use the bootloader method.
Change the Bootloader so I can use the SD card method.
None of there are working.
Help :-(
I really want to go back to the ATT rom, it might have the annoying thing with the sound but at least it doesn't mess up as much, doesn't format my SD/MMC cards and lets the alarms actually work for me.

if i'm not wrong, it seems you upgraded using the TMO exe file which updated both ROM & RSU.
check ur boot loader version, if it's 5.22 or higher, i think you need to dowgrade to 5.15 ... use the exe file that comes with the XDAtools in the binaries directory .. its name is fixbootloader.exe .. it should update ur boot loader to 5.15 by which you can use XDAtools or the SD method.

Tried that. I do have XDA tools on my machine and used that program but my CDA still has the bootleader of 5.22
And both of my machines don't like trying to update my XDA :-(
This Rom is the most annoying one I have tried mainly becaise now I can't go back to even my original one that I backed from the XDA when I got it.
Am I stuck with this ROM?

omg, i think i am having the same problem. In my case, since ive installed the new rom, i cannot sync with activesync, well very slow anyway. Activesync on my pc stops responding for a while and suddenly it says connected. However when i then run the executable created by the kitchen, it just flashes a command line window for a second.
When I try XDA-toolz with an nbf file, i get the following message:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
Click to expand...
Click to collapse
Please someone help, because i am really stuck now.

I checked, my bootloader is 5.14, so that shouldnt be the problem, perhaps i need to reinstall activesync, or perhaps lumpistefans kitchen cooks up bad roms. :?:

Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!

Biso007 said:
Nothing wrong with any kitchen ROMs so far ... when ActiveSynce can't recognize the XDA then it's either a PC problem which uninstall/reinstall will solve it ... or it's a wrong RSU update.
The best option so far in case it's a wrong RSU is to copy the proper RSU upgrade (4 files) to the SD card ... insert the SD card into the XDA and copy those 4 files to the \windows\startup directory ... then soft rest.
If the RSU flash works fine the ActiveSync will recognize the XDA again then you can preform a new ROM update
Note: RSU flashing is risky ... do this action on your own responsibility!!
Click to expand...
Click to collapse
I dont understand how i can have a wrong rsu? I didnt update it , as far as i know , i just updated the pda part. I only saw programme A.
Activesync does recognise my xda, because i can synchronize and explore my device. It does however take a long time before activesync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling activesync, this didnt help.

prowling said:
ActiveSync does recognise my XDA, because i can synchronize and explore my device. It does however take a long time before ActiveSync sees the device after its connected. It also stops responding when its connecting, for a few minutes. I tried reinstalling ActiveSync, this didnt help.
Click to expand...
Click to collapse
If there is something wrong with the RSU it will defeinitly slow the USB performance, not neceassary by wrong RSU flashing ... otherwise, check the pins of your cradle or the 22-pin connector of the XDA ... maybe one or more pins are bent or weared.

Tried upgrading the radiop stack and although the reception is slightly better... It still won't let me upload,
and its a new cable too :-(
Oh well looks like I am stuck with it.

Another way to upgrade firmware
Are there other ways to upgrade the bootloader from SD card from within the device or even to upgrade the OS from within the phone itself?
You know... as a last alternative?

You can use SD reader/writer from the PC using XDAtools ... once the .nbf file is on the SD card, use the normal SD flashing method.
Or you can use another XDA device from a friend to copy the file to your SD card

I am having the same problem. I have TMO 4.01.16 and since I installed I can't down/upgrade my ROM through EXE or XDA tools, it says my device isn't connected, but I can still connect with Active Sync and all that jazz

ha ha
I can fix all your problems!

How?

Finally got it to work, Although it was a little bit of effort to do so.
I went back to the kitchen and downloaded a NB1 cooked rom with the "B" Signature. Then I basically ran the TMobile Setup again...
Once the setup files were on my computer I overwrote their .NB1 file with the one I just cooked.
But.... I forgot to change the file for the Radio Stack.
The machine worked except for the phone and as something is still stopping me. *it was my first reboot* It wouldn't let me use a new radio stack.
Ended up that i kept on going in to the bootloader and eventually turned my radio off altoghether before trying an update.
Now I am back to a decent rom... (Cooked and modded version of the ATT Wireless rom) and I am almost really happy.
Now to figure out how to stop the annoying sounds starting off really low.
But til then... I'm 90% happy

Thespus2002 said:
How?
Click to expand...
Click to collapse
Use the Sd Method flashing!!
Tmobile roms won't let you upgrade from the usb, here's the link and it will guide you how to flash your device from the SD good luck
http://forum.xda-developers.com/viewtopic.php?t=3274

The way I described.. I had to use the USB method.
my current bootloader (6.22) will not allow me to boot from an SD card.
And XDATools will not allow me to downgrade it... Yet

on ur PC at \xdatools\binaries run this command: pnewbootloader.exe bootloader_5_15.nb0

Wish it was that easy. The phone still appears to be locked in the rom so I can't update the Bootloader. I keep getting a message that says.
Unable to flash in to offset, cannotg disable bootloader write protect.

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.

Artemis: USB-Connection not working - Up-/Downgrade by SD-Card not possible

Hi there,
I have a MDA Compact III from T-Mobile, but I upgraded it to WM6 from o2 in former times.
Now the USB-Connection is broken (don´t ask me why - I don´t know) and I want to send the Artemis to my provider for repairing or changing (btw loading is working by USB, but Windows Vista, XP etc. wont identified the Artemis - tested on serveral PCs).
Because of the guarantee I have first to downgrade the o2-OS to the original T-Mobile-OS. I´ve tried it by SD-Card, but I doesn´t work.
The bootloader shows IPL 3.04.0001 and SPL 3.04.0000. As I understand it, I have to use first Artemis_USPL, but without a working USB-Connection it wont work.
Can someone help me?
Many thanks in advance.

I have still the same problem. Any ideas yet?

Just an idea.but have you tried to activesync your device thru bluetooth and installing the Artemis uspl and then flashing your rom via SD card?
Edit .
Sorry mate, tested it on my Artemis and doesn't work.

I'm having the same problem here.
When i connect it to my pc it starts charging but there is no connection with the pc
Someone knows a fix?

sammis said:
Just an idea.but have you tried to activesync your device thru bluetooth and installing the Artemis uspl and then flashing your rom via SD card?
Edit .
Sorry mate, tested it on my Artemis and doesn't work.
Click to expand...
Click to collapse
Thanx for Testing...

By the way ,did you try to activesync thru bluetooth?

Yes mate. The Artemis was connected but didn´t synchronize.

And bluetooth can't be used to flash

RikP said:
And bluetooth can't be used to flash
Click to expand...
Click to collapse
No,it can't ,but,what i had in mind was this:
What if you extracted the ruu-signed.nbh from the USPL app renamed it to arteimg.nbh and put it in the root of your sd card which you then put in your Artemis.
Now create a bluetooth activesync connection with your PC "It's a ***** but it can be done" ,run the USPL app and once it reaches the point where the Dos window "Black screen" exits you manually enter bootloader and run the arteimg.nbh.
Do you think it might work?
Edit:
If this works then you will have a CID unlocked Artemis and you'll be able to flash any rom thru the SD card.

With "ruu-signed.nbh" you mean an original t-mobile-rom?

rumms said:
With "ruu-signed.nbh" you mean an original t-mobile-rom?
Click to expand...
Click to collapse
No, i mean the one that is inside the USPL app released by Pof.

sammis said:
No,it can't ,but,what i had in mind was this:
Do you think it might work?
Click to expand...
Click to collapse
Doesn´t work.

Problem upgrading to Artemis

Hi, I tried to install the Artemis Touch 4.02 Full with 4 sided cube ROM on my HTC 3301 (same that 3300) but when I try to install the mobile has restarted when the bar progress stay on 3% and don't work... please help me, my mobile don't work more, and I don't know what to do!
Thanks

3% is a classic... did you use uspl first? In this case it means that you have to perform step1.bat first, then step2.bat. Make sure step 1 went well, then try step2 again.

Gwystyl said:
3% is a classic... did you use uspl first? In this case it means that you have to perform step1.bat first, then step2.bat. Make sure step 1 went well, then try step2 again.
Click to expand...
Click to collapse
But when I execute STEP 1 I see this message:
"No Device Connected" -> "Would you like to try copying again?"
And don't work... My mobile only enter in bootload (Red, Green and Blue Screen).
The Active Sync don't connect in mobile on bootload screen =(
What I do?

Do you have a SD Card >2GB in your Slot?
Then removed it and try it again ... There is a known problem with flashing while a sd card >2GB is connected (you have to install the sdhc driver after install in order to use your sd card ... maybe its included in the rom)

Uncle_CM said:
Do you have a SD Card >2GB in your Slot?
Then removed it and try it again ... There is a known problem with flashing while a sd card >2GB is connected (you have to install the sdhc driver after install in order to use your sd card ... maybe its included in the rom)
Click to expand...
Click to collapse
No, I removed the memory card before install... I trying to use the mtty, but I don't have successfull too =(
I read on web that I can put a ELF0IMG.nbh file on memory card and power up on bootload with the card to install the ROM... it works?
Thanks

hmm, i dont know ... but if theres a tutorial give it a try
which USPL Version is shown when you try to start your phone?

Uncle_CM said:
hmm, i dont know ... but if theres a tutorial give it a try
which USPL Version is shown when you try to start your phone?
Click to expand...
Click to collapse
IPL 3.16.0001
SLP 3.16.0000
GSM 03.06.90
OS 10.0.0.10

Okay, than you could try this "by hand":
http://forum.xda-developers.com/showthread.php?t=311403
This worked for my O2 XDA Orbit (HTC Artemis) ... it could be, that youre device isnt supported ... it could be different as a P3300?!

Uncle_CM said:
Okay, than you could try this "by hand":
http://forum.xda-developers.com/showthread.php?t=311403
This worked for my O2 XDA Orbit (HTC Artemis) ... it could be, that youre device isnt supported ... it could be different as a P3300?!
Click to expand...
Click to collapse
Thanks, but I can't sync my phone because I can only enter in bootload mode =/
I tried puting the ARTEIMG.nbh file into memory card, but only give the message: "Invalid Certificate".
Thank you for try to help me, but I don't know what I can to do! I think that my mobile is dead forever =/

So, you can't turn on your device anymore?
Did you tried a Hardreset?

Uncle_CM said:
So, you can't turn on your device anymore?
Did you tried a Hardreset?
Click to expand...
Click to collapse
Yes, I can turn on the device, but don't start the OS, stay on SPL/IPL... screen, and I can enter in BootLoad screen too (Red/Green/Blue screen).

This sounds bad .... the last thing i know is to do a hardreset:
when device is switched on
1. press left and right softkey together and hold ... then stick the stylus in the RESET hole and remove it (but still press the keys)
2. after a short reboot you should see a message with further instruction ... now you can release the softkeys and follow the instructions ...
So, thats the last thing i get in mind ... sorry ...

people!
read wiki sometimes...

english rom

my unit come with ru rom and is cid lock
try to un lock with hard-spl but it did not work
how can i do it were can i dowmload unlock and good english rom
thanks

same problem here.
I read nearly all the treads and tried many ways to flash my pharos which is french that comes with default versions. From what I read I understood that I need to install hardSPL because the phone is CID locked. I have windows Vista (not tnat I like it but I have to stick with that because I need licensed software), anyway I understood that there is a problem with flashing on vistas. It always gives me the same error 270. I tried to flash the device with the original rom from htc and it says "invalid vender id". the htc website doesn't even support my phone. they say that my device isn't appropriate for their roms (using my serial number). the only thing that works is the Jump SPL that gives me the grey wallpaper, after starting the flash, the phone goes to bootloader and then starts but as described on other posts it stops on 1% or 2% and reboots to windows. I tryed with uploading .nbh and renamed it to HERMIMG.nbh and some other names to 1GB microSD with fat32 just formated and the bootloader doesn't find it. I don't know if the pharos have some special name like PHARIMG or s.th. like that. I worked here with my imaginations. I tryed on XP and same result. For vista there is some suggestion that it will work by changing the drivers to xp ones but the tread reffers to some other website and the url is not responding so I moved to XP and same result... If someone reads this and have to say something other than rtfm or read the wiki please don't hesitate to help