Related
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...
I have a nice new image for a i-mate sp5m , I used the bootloader to copy it to a sd card, I then pluged that sd card into another i-mate phone and when asked to flash said yes, the flash went ok, but when the phone starts I get "device authentification error". I have looked and people have mentioned a hex edit , but this was from 2003 to wm5 and not from this nice new image. I also read about a patch1.exe but again this was for a wm5 image.
toxicated101 said:
I have a nice new image for a i-mate sp5m , I used the bootloader to copy it to a sd card, I then pluged that sd card into another i-mate phone and when asked to flash said yes, the flash went ok, but when the phone starts I get "device authentification error". I have looked and people have mentioned a hex edit , but this was from 2003 to wm5 and not from this nice new image. I also read about a patch1.exe but again this was for a wm5 image.
Click to expand...
Click to collapse
Hi. that seems to be a very nice rom you have. please check this thread: http://forum.xda-developers.com/showthread.php?t=296419 there you will see how to dump the rom to a file to the computer and share it with the experts. the will be able to help you and the rest of the people waitting for that fine rom
I put the file ARTEIMG.nbh to SD Card (FAT32), the ROM that I'm using is "Artemis 4.02", but on manual (http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing) says that I need to extract the NBH, but when I try to extract I have a error, then I've copied the file to SD Card, but when I enter on bootload in screen show me "Invalid Certificate" and I don't know what I do! Please help me... my mobile is dead
exact same problem..... has any one got any solution for this ?
Same problem also for me... have anyone found a solution for that???
Thank you all
Same problem with a number of ROM's. The only ROM I have been able to flash is an old wm5 (ART_HTCDAN_11240301_026790_DAN_SHIP). And I think it is an older version than the one installed when I bourght the device
My p3300 refuses to do any flash from win7, sometimes it can't see the device and sometimnes it reaches 2-3% of the transfer before it stops.
mortuis said:
Same problem with a number of ROM's. The only ROM I have been able to flash is an old wm5 (ART_HTCDAN_11240301_026790_DAN_SHIP). And I think it is an older version than the one installed when I bourght the device
My p3300 refuses to do any flash from win7, sometimes it can't see the device and sometimnes it reaches 2-3% of the transfer before it stops.
Click to expand...
Click to collapse
Hi!
Flash USPL first,after that you can flash any ROM into your device.
BR
Szig
probably error 260
mortuis said:
Same problem with a number of ROM's. The only ROM I have been able to flash is an old wm5 (ART_HTCDAN_11240301_026790_DAN_SHIP). And I think it is an older version than the one installed when I bourght the device
My p3300 refuses to do any flash from win7, sometimes it can't see the device and sometimnes it reaches 2-3% of the transfer before it stops.
Click to expand...
Click to collapse
type error 260 in search you will be directed to pages where the sollution is, you must change something in your pc in windows mobile center
show invalid certificate me on
SPL 1.25.0001
Hi everyone,
I offer you a safe way to recover your bricked ipaq or just change language into English.
I use the lastest official english ROM download on Hp website.
I saw some members have the ideal to patch the ROMupdate.dll to bypass the check the language of the phone ipaq 61x.
It means that we can update the phone with any languages.
I do exactly the same with Ipaq 91x.
So I upload the file for you.
Just download, extract and run hpRUU.exe
Follow the instruction and after about 20m.
You have the phone
P.S: I used this method to change my phone language from Italian to English successful. And recovery my friend's bricked phone.
But notice that I'm NOT responsibility for any damage with your phone.
Good luck
Download the rom here
http://www.mediafire.com/download.php?jyzy00y2yal
Good job, thanks!
Will try it out later!
is it still compatible even though my device SKU IDs is not compatible with the update?
Last time i tried i almost bricked my device.
In theory, yes
Actually, like I wrote above.
My ipaq 914c is Italian version.
It means that the SKU IDs of the phone is not not compatible with the update. ( I mean the official update!)
But we all know that there is no difference in the hardware between the ipaq 91x.
So any language ROM versions can be used on the another ipaq 91x phone.
=> WWE ROM can be used on any Ipaq 91x phone.
My Ipaq now is in English. But the SKU IDs still show that it's in Italian.
By the way, I forget to thank: Z!L0G80.
i just tried to update my 912c using HP update utility that i downloaded from mediafire.
but it failed it gave me Code 402 : Cannot Communicate with device. and the device stuck at boot screen with RUU... on top of the screen.
- i already Hardreset the device
- i'm using Benjaminries Motherload ROM
- i'm using Windows XP
please tell is there somethings wrong?
i really want to try the update. should i try using SDbootloader? can you helping find some solution?
many thx
AbsolutBenz said:
i just tried to update my 912c using HP update utility that i downloaded from mediafire.
but it failed it gave me Code 402 : Cannot Communicate with device. and the device stuck at boot screen with RUU... on top of the screen.
- i already Hardreset the device
- i'm using Benjaminries Motherload ROM
- i'm using Windows XP
please tell is there somethings wrong?
i really want to try the update. should i try using SDbootloader? can you helping find some solution?
many thx
Click to expand...
Click to collapse
Hi,
As it was given like that, I think you should check the usb cable. Sometimes the cable is not working well. I use the original cable, because the last time I use another there was an error when it was flashing. (I'm not sure if the active syn is necessary. In my case, I have the active syn on my laptop. XP enviroment.)
If you want to try the SDBootloader you can find in this forums some instructions about cutting some bytes to obtain the flashdio.nb0
But I really don't recommend that way. Because the last time when I find the way to change the language by flashing the english Rom following those instruction. My phone was bricked. So I tried to find another way.
And this is it.
I think this method is the safest way for newbie. As I wrote above. The first time I bricked my phone. But I did the same procedure again. And it worked.
Just check the procedure again.
Good luck,
For the SDloader update (Which works very very well on my German 914c):
download the file below (I already cut the first 3432 bytes from it), put it on a newly formatted SD-card (not SDHC!) and hold down volumeup+OK button (the one on the right side) while pushing the reset button, hold the mentioned sidebuttons until you see SDloader. Then wait for a few minutes, and the update will finish!
If the updater does not find the file, you have to re-format the SD-card to either FAT or FAT32!
Rename the file to FLASH.DIO when you copy it onto the SD-card!
http://rapidshare.com/files/236053650/FLASH.DIO.html
vragon said:
Hi everyone,
I offer you a safe way to recover your bricked ipaq or just change language into English.
I use the lastest official english ROM download on Hp website.
I saw some members have the ideal to patch the ROMupdate.dll to bypass the check the language of the phone ipaq 61x.
It means that we can update the phone with any languages.
I do exactly the same with Ipaq 91x.
So I upload the file for you.
Just download, extract and run hpRUU.exe
Follow the instruction and after about 20m.
You have the phone
P.S: I used this method to change my phone language from Italian to English successful. And recovery my friend's bricked phone.
But notice that I'm NOT responsibility for any damage with your phone.
Good luck
Download the rom here
http://www.mediafire.com/download.php?jyzy00y2yal
Click to expand...
Click to collapse
Hi Everybody,
@vdragon
1- what a great job, guy!
2- in reality, i have already flashed your ROM successfully for my ipaq 914c, which is a native italian version. Since the incompatibilites of different versions were resolved perfectly.
3-Grazie tanto di nuovo
I'm pretty new with this and I've been trying to update my 910 with original ROM but for some reason it gets stuck and the only way to bring it back is with a SDLoader I downloaded from here but that one is very simple and I'd like one with all the programs.
Is there a way to load yours on it through the SD card?
you can follow the instruction to cut the 3432 bytes and flash your phone with SD card.
I see that many people prefer to use the sdloader method than this one.
But the positive point of this method is that it updates all your firmwares include OS, WAN, Radio... to new version. Not only OS.
vragon said:
...
But the positive point of this method is that it updates all your firmwares include OS, WAN, Radio... to new version. Not only OS.
Click to expand...
Click to collapse
Hi all,
Are you really sure that the method of using SDloader has NOT updated Modem, Radio ...so on ?
Anybody has idea on the contrary?
congtiger said:
Hi all,
Are you really sure that the method of using SDloader has NOT updated Modem, Radio ...so on ?
Anybody has idea on the contrary?
Click to expand...
Click to collapse
sure
congtiger said:
Are you really sure that the method of using SDloader has NOT updated Modem, Radio ...so on ?
Click to expand...
Click to collapse
Yes it is true!
Using vragon's patched Updater the following is updated:
OS (=ROM)
Bootloader
Pre-Bootloader
Radio&Modem
This update takes about 20minutes, so be patient, do not remove any cables during update!
The flashing of FLASH.DIO with an SD-card "only" updates the OS (=ROM) and is done within less than 10minutes.
Thanks vrago for patching the Romupdate.dll!
You can also see it in the bootsplash screen. Before the update (even after SDloader updates) it always showed FW 1.04.
Now it is 1.09 - and yeah, it works GREAT and quick!
I can recommend it!! (I do not take responsibility though)
Should be a sticky!!
I've been trying this file, and I get an error at 51% of update. Any ideas?
I think it's about your cable. Be sure that you use the original cable with the anti-noise hub.
If you didn't success the first time. Try it again.
Do as you did the first time.
And just be patient. Don't move anything.
The first time I used this method, at the middle of flashing, I kicked my cable and it just stopped. And I did it again carefully.
So that's it
Actually, I think I figured it out. It seems that Vista treats USB partnerships differently than XP, so after a certain amount of time, it "refreshes" the relationship with the USB device. If you are trying to flash your phone, that stops the flash/update.
I just used my XP system, and it worked fine. After a few registry tweaks for ring volume and battery life, it's working fine.
Are you really sure that the method of using SDloader has NOT updated Modem, Radio ...so on ?
Click to expand...
Click to collapse
I'm positive the SD Loader method isn't as thorough as this method. This method takes 20 minutes or so, and you can see that it's updating the pre-loader, modem/radio, etc. The SD method only updates software.
Problem using HP 614c from original ITA rom
I am a stupd guy
I am a stupd guy
I am a stupd guy
Hy vragon, i have used your method to upgrade my device 614c (and not 914) from an original Italian ROM. All process is ended correctly, all upgrade are finished without errors.
The update utility has made the update of that:
Software - From Version - To Version
Bootloader - 1.00.07 - 1.01.01
Windows Mobile 6.1 Professional - 1.00.07 - 1.01.01
Pre-Bootloader - 1.00.07 - 1.01.01
iPAQ WAN Radio Firmware - 0.81.00 - 1.09.00
But after the upgrade, at the end the display was black(not really black i can see the leds of the entire display are ON but das not appear nothing), and after some minutes abouth 20, i removed the battery and restart the device but nothing has changed. The led over the screen and the sound working.
I have try also to do a hard reset with a flash.dio on an SD card inserted to replace the Rom, but dose not work!
The device after that will work properly, and das not appear to have any problem.
CAN SOMWONE HELP ME !!!
@ilconte81:
just go to hp site.
find a ROM update for 614c.
download it.
using winrar to extract everything in the exe file.
copy the ROMupdate.dll from my file to replace the file in the folder which is extracted from exe file.
run the rom update again.
Tanks for reply vragon,
i have tryed to do what you wrote, but the device will not be right recognized from the OS (will appear USB device not recognized) and the update utlity after a long time in "Plese wait while the device state is verified" give the comunication error Code 402, Cannot comunicate with device.
I use the original cable and try these on different OS like Win XP and Win 7.