Related
Hi there,
I tried to run the ATT/Siemens release and it locked up. Per some advice I tried to use the tool provided here to burn the ROM from a SD card, but after I do this I just get a white screen, and my only options is to format the SD card if I insert it.
Is this a lost cause, has the PDA been damaged beyond repair?
Thanks for any help!
t00f
t00f said:
Is this a lost cause, has the PDA been damaged beyond repair?
Click to expand...
Click to collapse
No, it is not. If your device still wants to talk to ActiveSync, you can just get Jeff's .exe file and run it on your PC. If it doesn't talk to ActiveSync, you need a PC SD-card reader/writer, which I think I understand you already have. Just find a ROM image you'd like to flash, either in .nbf format (as supplied with the upgrades) or in .nb1 (as saved by the XDArit tool) format, and follow the instructions on our page.
Good luck...
I tried your tool with the SX56 ROM and get the same results some other people posted here in the past: PDA boots up to a white screen and if you press or hold down the volume botton, the welcome screen partially comes up, but it's not functional.
Also I got ahold of one of your modified ROMs and tried to use that and got the exact results.
t00f
Hmmm, looks like a hardware problem at first glance...
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.
Ok, i konw there's already been several threads here about downgrading from the wm2003 rom (4.01.16ENG from the rom kitchen to be precise) but i can't seem to get this thing anywhere... as i said i upgraded the rom to the one specified above and found it far slower and unstable than the ppc2002; I wanted to flash the xda with the old rom but there's this strange communicate saying that the connection has been suddenly closed and the "programme a" stops. i tried to flash the old rom directly to the device using the xdatools but also with no success... it keeps on saying that it couln't communicate with the remote application... well then i thought about this bootloader fix (still unsure what bootloadre i have because i can't get the info anywhere) and it said that the memory on the device is write protected.... :/ well, and as for now i am waiting for a sd card to try that, but.... tell me, will the xdatools prepare the card if i insert it into the device? (i have no card reader for my pc) i am woried because each action i take (except normal device usage - activesync, copying and moving files, installing appz) that messes with the roms, shuts down the connection and i have to unplug the device from my pc and plug it again... please help me, i'm in dire need!
I am having a similar problem with the same rom version. I wish i never used that version! I did an update to wm2003 earlier and i could go back and forth with no problems, but this one is a real nasty one!!
the message i get when using osimagetool:
ERROR: GetConnectionType - An existing connection was forcibly closed by the rem
ote host.
error getting connectiontype
I am having the same problem ..
and when i power on/off the device it says (Unrecognized Card)
Enter the name of the device for this card. For information, see the card manufacturer's documentation.
and there is a place where i can write something (Unknown card in socket 1)
m112a said:
I am having the same problem ..
and when i power on/off the device it says (Unrecognized Card)
Enter the name of the device for this card. For information, see the card manufacturer's documentation.
and there is a place where i can write something (Unknown card in socket 1)
Click to expand...
Click to collapse
YES!!! Same here!!
How about the phone? I cannot seem to turn it on. When the pin screen comes up it says i should turn on the phone, but i cant dothat anywhere..
Hi All,
The best option for ROM upgrade is always the SD method ... it's much easier and safer. XDAtools doesn't work with some ROMs because of the boot loader version not the ROM itself.
So what do you say guys? will i be able to downgrade it from the sd card? - and first of all, prepare the card having it inserted into the xda itself and using xdatools? i also wish i had never used it, the newest ppc2002 rom from o2 is just soo cool comparing to the wm2003 one i'm stuck with right now...
hi there, my mates xda mini on t-mobile was lost on his device as he tried to install a version that wasnt meant for his device, now he dont have any OS as it removed the rom and couldnt install the other, so its a clean device, i have downloaded the rom from the FTP site and i find the file is
tmobile.nb1
how do i get this installed on his device???
im new to this myself and no idea how to do it, i have heard this and that among the forums and i am assuming that you transfer this to an SD card and install it from there, if this is what you do then how do you do it??? is it simple, or is there an extractor i can use to turn it into an installer????
PLEASE HELP,
its not a process for the light hearted, however is it a xda mini your friend has or the mda compact, without the clarification we cant really progress.
All he needs if it is the mini is to install the xda mini rom files, however if it is the compact you will need to do a bit more.
Reply if further assistance is needed
jim
it is the mda compact, what he did was 9as he is new to this stuff0 tried to install an xda2s software to it, and it took his old rom off the device, it then tried to install then he got the error message and would not go any further, now as mentioned earlier, i have the file from the ftp site which im guessing more and more now that i just put that file on an sd card, and flash it, only thing is, it mentions something somewhere i read that you need to copy files from the old rom which he dont have and i dont have access to. what do i do, as he is going to india for 6 months in 4 weeks and if he sends it away for repair he wont get it back in time... and im his only hope as it happened to me, only thing, i have xda 2s and im on o2, so i just got the rom from here, which was an installer from the pc through the usb connection...
please help!!!!
So I can assume that the screen just says serial on top and v1.00 at the bottom, ie the bootloder screen, if this is the case there is some hope however you will need a few tools and some patience
ntrw
romupdate utility
SD card reader / writer
at least 256MB SD card
once you have that, just follow the instructions for the ananasky ROM update, however the rom that you will be patching is the tmobile.nb1 one on the ftp site, or you could go ahead and try the anansky patch itself
as before let me konw how u are progressing
jim
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.