Related
I follow instruction in http://forum.xda-developers.com/showthread.php?t=313486 but after hardreset.
My p800w is stuck in T-Mobile logo and version number. It can't continue booting up to windows mobile.
Question: How to flash ROM without ActiveSync?
How to recovery my Artemis?
Welcome any advice,
Thanks in advance.
Yea me to, mine is now a brick after that upgrade? No active sync connection possible and all I get now is the blue O2 start screen after the hard reset with the red writing and numbers in the top left hand corner..
Phone is an UK XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 02.67.90
OS 3.4.0.0
HELP!!!!!!!
yeah, I had the same problem and have created a thread for it already. unfortunately I got no useful replies, and it seems that I am stuck waiting for an official o2 ROM so that I can recover my Orbit.
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
motomob said:
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
Click to expand...
Click to collapse
I read in here that you hold the voice button and soft reset.
Decaf said:
I read in here that you hold the voice button and soft reset.
Click to expand...
Click to collapse
Correct and use mtty
Already see in the forum ....
Thanks guys and apologies for the spelling..I ran the Artemis_USPL before I tried upgrading to WM6 and again have been able to run it after with my new brick now with the phone in bootloader mode but still when I try and run the german ROM update a) it will only work with the german file which freezes @ 3%? This seems to be a known problem reading around and b )when I replace it with the smaller ROM file, 54MB the german one is 66MB, I originally tried to use it doesn't read the ROM file or the update utility doesn't want to read it. I reckon I might be able to get it back if I can get one of the ROM update utilities to read a good ROm file and send it to the phone.
I can;t find this MTTY program to sniff the USB port and return the code of if the USPL util wokred as I think that could be key to all of this.
Can anyone post a quick how to here for
1) install MTTY from somewhere
2) what command to run agaist the phoen to see if the USPL util worked and what values I should be looking for
3) another WM6 ROM version (that the update utils can read) download location I can download from to try and send to the phone using the German update util
Not asking for much am I but I desperately need my phone back WM5 or 6 in the next day or so so really can't send it off.
Thanks
Error message I recive at the 3% stage when using the German ROM and english update util.
use the file attach and read that :
http://forum.xda-developers.com/showthread.php?t=285112
Thanks but I'm not that cleud up on what commands I'm meant to be sending. It works in Bootloader mode I ge a response from the phone by send it a command. But even if I get a response telling me what the CID status is its not much help as I think ti shoudl have tekane BEBEs ROM by now as I've got the german ROMUpdateUtility sending that 54,272KB file to the phone but it stops after 3%. What are my options?
motomob said:
But even if I get a response telling me what the CID status is its not much help as I think
Click to expand...
Click to collapse
That's right. On older models MTTY was quite useful, but not on the Artemis. You cannot use it to read the CID status anyway. If you are not sure about the status, run the USPL tool, just to make sure.
I've already re run the USPL ROMUpdateUtility and it completes 100% okay in bootloader mode. But after I hard reset and then try and flash the WM6 BEBE ROM or any ROM German etc back onto it it either fails with the error code I posted up earlier or gets to 3% and fails.
What are my options at this stage? Does anyone have a link to another ROM I can try like the original WM5 O2 ROM or any other WM6 ROm that might work. I'm willing to give them all a try as it's just a useless phone right now and I haven;t sent it off as 1) I need it before the weekend and 2) As I can flash some ROMs with the USPL and others have done this no problem I really feel there must be a solution as I can still falsh the phone.
What can I say RTFM... I did it all right and I didn't have a brick, I missed out one small detail... loading on the ROM with the extended ROM. All now running and it does seem a little faster than WM5.
Thank you to all those that tried to help out. To the others that are still having probs.. Don't try and run the update in the middle of a busy day in the office whilst trying to manage 100 other things meaning you are probably missing out a line like me...
One question though how do I get back my O2 power and storage meters on the today screen back as I liked them and the WiFi seems to have a bug where when it is enabled and you click on the WiFi symbol up the top it only allows you to switch it on, when it is already on.. so you have to open up the COMM manager to switch it off.
So how did you fix it exactly? I have read this thread thoroughly and can't find out what you did!
ERROR[206] occurs while trying to update ROM to WM6
While tring to update ROM to WM6 on O2 XDA Orbit i encounter ERROR[206].
I wanted to attach the screen shot but dont know how to do that, but anyway what i am doing is i attached my pda to my pc via activesync using supplied usb cord. Everything goes well till i reach a screen where it says "You are now ready to update your ROM image...." and once i click next a progress bar apperas and my pda shuts and activesync exit's automatically and my pda tries to restart with RBG band and some text:RUU, IPL 1.25.0001, SPL 1.25.0000 and USB. And thats it after few seconds or a min i get the ERROR[206] and my pda hangs.
I dont know why Activesysn shutsdown ???
Just an additional in i want to tell that without installing activesync i am not able to connect/pair my pda with my pc. So do i need to install the drivers and then try or it doen't matter cause once i install Active sync i can connect the device.
Please help me with this....
Thanks
unable to load bootloader!!!!!!!!!!!!
HELP!!!!!!!!
I have HTC3300, tried to update rom, now its bricked. I tried to start bootloader by pressing the voicebutton and softreset but loads in t-mobile screen and hangs, im unable to start the bootloader.
Is this end of story or are there any other options to get the bootloader to start????
please help
Bootloader
I had a problem with my phone loaded touch flow 4 and cid unlocking, everything was fine then after a while it froze at boot up.
I look put the battery and did a hard reset, put it into bootloadeder mode, reflashed with a t-mobile rom does not need to be cid unlocked to do that.
Once origonal rom was working, cid unlock again, flashed back to touchflow 4.0 - sorted
Where did you got an tmobile rom from can you tell me. Mine is also freezing on booting almost once every day or so after I've upgraded to 4.0
HI all,
yesterday my Orbit crashed. Whenever i try to turn it on, it gets stuck, and only shows the first 2 lines when loading, and does not show the GSM version and OS version, I tried to do a hard reset, nothing helps, it just keep stucking on the 1st screen with the first 2 red lines.
Anyone any ideas ???
Thanks
Worth a Try
You might just have a go at putting it into bootloader mode and flashing with a new or the same ROM.
I wouldn't like to suggest it would definitely work, but it'd be worth a go.
How do i do that ?
When in doesnt recognize a connection ?
igal said:
When in doesnt recognize a connection ?
Click to expand...
Click to collapse
It may be able to make a connection in bootloader mode. Like I say, it may not work, but have you tried it? Have you got a better idea?
igal instructions how to go into bootloader mode are in the first thread of the forum. You dont need an activesync connection just connect via usb.
As Mark has said above Activesync connection is not required for "connection" Bootloader mode activates a USB connection which allow ROM flashing.
Use an official O2 Rom or similar, which AFAIK does not require USPL'd ?
Check this thread, which succesfully fixed my bricked Orbit, Remember your on your own though, but if it is knackered now it can't get worse....
My instructions use the official German Rom to get it back up and running, as the English version had not been released. Once you get back up and running you can use any of the other cooked ROMS that are about.
http://forum.xda-developers.com/showthread.php?t=312495
DISREGARD the bit about WINRAR, just get an official ROM, stick your handset in bootloader mode and run ROMupdateUtility.exe
Report back on how you get on.....
I went in to..
Bootloader mode. and got the RGB screen with usb connection, but when i try to flash ( both the rom im using now B&B 4.1 and also an official ROM by O2 ), it quits after 3% altough i have a CID unlcoked by imei-check, and i flashed like 10 times before...
any ideas ??
Thanks!
You must use the factory rom specific to your device including language - did you?
Yes i did.
Not working....
Hi Igal,
which rom eaxctly did you try to flash with to rescue your Artemis from the bootloader?
Rgs
Cyber
I used O2's rom
I downloaded the official rom of O2 ( Windows Mobile 6 ). Once it told me "Invalid Vendor" and the other time " Image corrupted " ( I have O2 XDA ORBIT ).
Are you in the uk using a rom from 02 UK?
I had a similar problem like you are having and managed to rescue using the HTC WM5 standard rom.
Im not in the UK, But
The phone is a UK one, and i tried to rescue it with wm6 official rom, Do you think i should try with wm5 ? Where do i get it ?
igal said:
The phone is a UK one, and i tried to rescue it with wm6 official rom, Do you think i should try with wm5 ? Where do i get it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=318696&highlight=mobile+5
Since Diamond is not available in russia yet we are all waiting for a working russian rom. Finally someone has uploaded it, but also said that Hard SPL for WWE Roms will not work with it for some reason. Can please someone test it and see what is the matter with it. May be it is the newer rom and you will get the same HSPL problem with next wwe roms too.
http://rapidshare.com/files/1243845...Diamond_52.26a.25.09_1.00.25.03_Ship.exe.html
Thanks!
This rom is mainly important for me `cause I need a russian dialer. I have tried pretty much everything i know but still have not managed to put russian letters in the dialer.
HTC apparently introduced a new region protection. Roms from some particular regions (Russian rom and maybe others) apparently won't run on devices imported from another region.
Do me a favor and enter tricolor bootloader. Then connect with MTTY, press return twice until you see the Cmd prompt and then type the command "readregionalid" (w/o quotation marks). Copy & paste the output here.
I have not tried to run this new rom yet 'cause do not want to brick a device. Diamond was bought for me in Hong kong.
Now I am on 137.456.2 Signed for Middle East
To further research the issue I would like to see the reply of the "readregionalid" command of Diamonds sold in different regions.
Thx in advance.
I can do it, but...
I have Diamond from NL, and Russian ROM not work too.
But you know europe code, i think...
Cmd>readregionalid
ReadRegionalID: GPIO value:0
iourioul said:
I have Diamond from NL, and Russian ROM not work too.
But you know europe code, i think...
Cmd>readregionalid
ReadRegionalID: GPIO value:0
Click to expand...
Click to collapse
Thanks.
What happens? Does it not run at all, do you get an error message?
I have flashed with this rom my diamond. And now, it's reboots every time after writing TOUCH DIAMON and version numbers (radio, rom,...)
I have tried to hard reset device - but the same.
And I cann't flash with a new rom because it doesn't sync to my pc.
Is it possible to flash it with a good rom? Or my diamond is broken at all?
acipat said:
I have flashed with this rom my diamond. And now, it's reboots every time after writing TOUCH DIAMON and version numbers (radio, rom,...)
I have tried to hard reset device - but the same.
And I cann't flash with a new rom because it doesn't sync to my pc.
Is it possible to flash it with a good rom? Or my diamond is broken at all?
Click to expand...
Click to collapse
Hold power button and volume down and after that press reset.You will enter to Bootloader mode next step connect device to PC and flash other rom like 1.37.707.1 WWE
Football said:
Hold power button and volume down and after that press reset.You will enter to Bootloader mode next step connect device to PC and flash other rom like 1.37.707.1 WWE
Click to expand...
Click to collapse
Thanks a lot!
May be somebody have started diamond withs this rom?
jockyw2001 said:
Thanks.
What happens? Does it not run at all, do you get an error message?
Click to expand...
Click to collapse
Reboot after splash screen.
Down+Reset -> 1.37.405.1 WWE...
this isn't a hardspl problem...
the rom has to be patched
cmonex said:
this isn't a hardspl problem...
the rom has to be patched
Click to expand...
Click to collapse
hi there cmonex,
you are right, or what i like better is to sec unlock the device
All will b soon
jockyw2001 said:
hi there cmonex,
you are right, or what i like better is to sec unlock the device
Click to expand...
Click to collapse
you are right too long term that's better solution..
btw can we talk on MSN?
try: http://rapidshare.com/files/124846060/RUU_HTC_RUS.exe
this is patched and worked when I tested it.
cmonex said:
this is patched and worked when I tested it.
Click to expand...
Click to collapse
Sorry, unfortunately it doesn't work.
Flashing was ok, now WM6.1 Russian loading, but GSM module can't be started. No way to switch it on using both Settings an CommManager.
Tried twice, the same results.
DmMc said:
Sorry, unfortunately it doesn't work.
Flashing was ok, now WM6.1 Russian loading, but GSM module can't be started. No way to switch it on using both Settings an CommManager.
Tried twice, the same results.
Click to expand...
Click to collapse
our apologies, i didnt test that part as i assumed it would work as the phone booted.
back to the drawing board.
after russian rom, I have flashed 1.37.456.2 - and my phone becomes to restart, after entering pin code. if I didn't enter pin code- device is working (without gsm). But each time it restarts after I'm entering pin.
I have flashed old rom 1.37.405.1 - the same problem.
acipat said:
after russian rom, I have flashed 1.37.456.2 - and my phone becomes to restart, after entering pin code. if I didn't enter pin code- device is working (without gsm). But each time it restarts after I'm entering pin.
I have flashed old rom 1.37.405.1 - the same problem.
Click to expand...
Click to collapse
and you reflashed radio and everything?
DmMc said:
Sorry, unfortunately it doesn't work.
Flashing was ok, now WM6.1 Russian loading, but GSM module can't be started. No way to switch it on using both Settings an CommManager.
Tried twice, the same results.
Click to expand...
Click to collapse
sorry, indeed forgot to check - we are not really familiar with the rom's default language
that is very interesting & will look into this today
Hiya XDA
I've been trying all evening to get any HardSPL onto my Diamond without success, everytime I try I get to 0% and after a few minutes "error [260] connection" and the phone keeps its' black screen until I soft-reset it.
Can anyone help me get a hardspl onto my phone? I would really like to try WM6.5. I've read many SPL-guides already, so you don't have to point me to them
(even that on modmydiamond.info)
Thanks in advance!
esset said:
Hiya XDA
I've been trying all evening to get any HardSPL onto my Diamond without success, everytime I try I get to 0% and after a few minutes "error [260] connection" and the phone keeps its' black screen until I soft-reset it.
Can anyone help me get a hardspl onto my phone? I would really like to try WM6.5. I've read many SPL-guides already, so you don't have to point me to them
(even that on modmydiamond.info)
Thanks in advance!
Click to expand...
Click to collapse
Here's the Tutorial and here's the Troubleshooter. They're both stickies. Please search and read before posting.
Thanks for the quick response, but as I said. I've read all stickies and guides, and it's still stuck at 0%.
esset said:
Thanks for the quick response, but as I said. I've read all stickies and guides, and it's still stuck at 0%.
Click to expand...
Click to collapse
Did you let your device sync with Activesync/Windows Mobile Device Center?
Try recreating the sync pairing.
Try uninstalling the device from PC's Device Manager and reinstalling it and then try recreating the sync partnership.
Try another USB port.
Yes, yes, yes and yes. I even tried doing it on my laptop.
Edit: I even tried flashing down to 1.93 with HTCs official stuff, no success there either
esset said:
Yes, yes, yes and yes. I even tried doing it on my laptop.
Edit: I even tried flashing down to 1.93 with HTCs official stuff, no success there either
Click to expand...
Click to collapse
Another USB cable?
Try manually entering bootloader and connect to PC. The label should say USB not Serial and try from there.
esset,
May I ask what branding/model of the Diamond you own?
I own a pure AT&T model just purchased a week or two ago. And, so far I've also had almost zero luck flashing it. I'm moving from an AT&T Tilt which I've flashed so many times, the USB port is starting to wear down. I've also got a lot of experience with many small computing devices with all types of weird programming and flashing routines, so I'm not a newbie. But the AT&T Fuze just seems to be locked in a way that has yet to be covered by the good XDA folks here. Heck, I can't even dump the shipped ROM off the device to send it here for checking out by the developers. All I've been able to do is flash an odd 1.90 HardSPL that seems to have locked the phone even tighter than before. YUCK!
If you're in this same scenario, I'd suggest patience. Eventually someone with enough knowledge of these devices will be able to help out. It is frustrating though, after flashing the other phone so many times with so many different configurations to be held back on the new one.
tnyynt said:
Try manually entering bootloader and connect to PC. The label should say USB not Serial and try from there.
Click to expand...
Click to collapse
You might find this odd. The down-volume + back arrow key combo doesn't seem to work with some of the new versions of the Diamond. I've tried on two of them, and neither respond to this key combo at startup.
Many times entering the bootloader is not a problem though. The routine does cause the phone to go there. And, I can get it there by other means. Just not via the boot up sequence. This tells me there is something very different about these models....
I tried starting and flashing directly from the bootloader (showing USB), and the phone got to show a percentage field (the one when you are flashing) but same here, is constantly at 0% until the flashing utility times out and tells me to reboot my phone and guides me through steps if it has been semi-bricked (bootloader is the volume down + softreset, right?)
I bought my phone in the first shipment to Sweden, it's not locked to any company, bought it without subscription
Else I just flashed it up to latest ROM from htc.com (still no success with HardSPL ) to 2.03.413.2 SVE (02/06/09)
Radio: 1.09.25.23
Version: 52.51.25.26H
ninjaedit: (In the four-colored bootloader thing it says DIAM100 64M SPL-2.03.0000 MicroP-Diam (LED) v11)
Tell me if you need any other info :]
Here's another indication that the new phones are different. I've copied a DIAMIMG.nbh file to both a flash card inside the phone, and to it's internal memory. (sorry, but the thread on that location is confusing on what memory. I assume like most phones of the past that it's supposed to be the flash card, but "internal memory" is not a flash card.) But, the loader screen always responds with "no image file" when it's called up. So, is there a different name expected now?
put manual hardspl into your device, and click to it from your device..
zerocool81 said:
put manual hardspl into your device, and click to it from your device..
Click to expand...
Click to collapse
Tried that with every Hard-SPL linked to from this thread: http://forum.xda-developers.com/showthread.php?t=415191
Didn't work
Something's changed.
zerocool81 said:
put manual hardspl into your device, and click to it from your device..
Click to expand...
Click to collapse
Hi uhm, was that answer aimed for me or to scottwilkins?
If it was for me, is it possible to flash the mobile directly from the memory-card (or internal flash card)? Else if you mean the "manual make-the-screen-black-and-go-to-bootloader" my screen just goes blank, as when you do it with the RUU, and just stops there. Also seems like it looses the connection via USB doing so too. And flashing through the bootloader directly (volume down at softreset) shows the progressbar on the phone, but steadily at 0% (when trying to flash).
search and download
a) SDA_ApplicationUnlock.exe (Desktopprogram)
b) EnterBootloader.exe (ATTENTION: it must be that for diamond, normaly find by flashing-tools)
connect with active sync and copy EnterBootloader.exe to pda-root.
start SDA_ApplicationUnlock.exe on desktop and follow all but reset (DONT RESET)
start EnterBootloader.exe on pda
if bootloader-Mode and USB-Label than start flashing
wait for response
scottwilkins said:
Tried that with every Hard-SPL linked to from this thread: http://forum.xda-developers.com/showthread.php?t=415191
Didn't work
Something's changed.
Click to expand...
Click to collapse
try this.. put this file into internal storage and lounch this from ppc
http://rapidshare.com/files/207721836/SSPL-Manual.rar
okokur said:
search and download
a) SDA_ApplicationUnlock.exe (Desktopprogram)
b) EnterBootloader.exe (ATTENTION: it must be that for diamond, normaly find by flashing-tools)
connect with active sync and copy EnterBootloader.exe to pda-root.
start SDA_ApplicationUnlock.exe on desktop and follow all but reset (DONT RESET)
start EnterBootloader.exe on pda
if bootloader-Mode and USB-Label than start flashing
wait for response
Click to expand...
Click to collapse
I tried what you suggested, I successfully unlocked the phone (and did Not reboot it). Ran the bootloader; and the screen just went black, as usually, and nothing more happens
zerocool81 said:
try this.. put this file into internal storage and lounch this from ppc
http://rapidshare.com/files/207721836/SSPL-Manual.rar
Click to expand...
Click to collapse
That program makes the Fuze screen just turn black and do nothing. Cool, huh
Seems that the newer stock ROMS might be blocking something... hmmmm....
Well, crap!
I just figure out where my whole problem is...
The Fuze (my phone) = The Raphael
NOT the Diamond.
I just scrolled down the forum list, saw a phone that looked like mine and went there. DOH!
I feel like a total dumb-ass.
If I'd scrolled just a bit farther down the XDA forum, then I'd seen the Raphael phone.
Holy Cow! Go ahead, say it, I deserve it...
Thanks for all the help otherwise. It was a learning experience for me....
esset said:
I tried what you suggested, I successfully unlocked the phone (and did Not reboot it). Ran the bootloader; and the screen just went black, as usually, and nothing more happens
Click to expand...
Click to collapse
hi,
i think, you have the wrong bootloader.
i find this and try it by me self. this brings your fone definitly to bootloader.
than you can start manualy the hard spl by normal description way.
http://rapidshare.com/files/208123046/EnterBootloader.exe.html
okokur said:
hi,
i think, you have the wrong bootloader.
i find this and try it by me self. this brings your fone definitly to bootloader.
than you can start manualy the hard spl by normal description way.
http://rapidshare.com/files/208123046/EnterBootloader.exe.html
Click to expand...
Click to collapse
Thanks, but that file takes me into the bootloader, and when I start flashing the percentage is still at 0% until the software times out. Same as before, just the usual "going-into-the-bootloader".
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
JiGSaW_HTC said:
Hello everyone!
I'm new at these forums, so excuse me if I'm being a "noob". I've searched all over the forums and found some instructions for my problem, but none of them helped.
My story is:
I have a T-Mobile MDA III device (I think it's also called HTC BlueAngel). It had the stock ROM, without any modifications. It was WM2003 I suppose.
I wanted to upgrade it to WM6, using this. In that thread it was recommended to use the updater given there, so I downloaded everything and tried to flash. After about 30 seconds of verifying information on the PDA, I got to a screen where it was supposed to say From and To version numbers, but everything was blank. I also have successfully flashed a HTC Trinity P3600 and those fields were blank there too, so I thought it's OK and pressed Continue. The program started to process, but after a while it said isn't designed for my device. I have tried numerous ROMs and RUUs to update it, but all of them gave some sort of error, some said "Congratulations, update complete" even if it didn't do anything.
The problem is, that my PDA is now stuck at the bootloader (?) screen. The backlight is off, the top of the screen says Serial (USB when cradled) and on the bottom I can see a version number (v2.05). I have read about key combinations (Camera, power, reset, record, etc) which are used to exit this state, but none of them worked. If I cradle my device, Windows (Windows 7, 64bit) recognizes the device as "Microsoft USB Sync", but WMDC doesn't see my device at all. On the forums I've read that in this state the device allows ROM updating, but I haven't found anything that could work, and the RUUs don't seem to recognize my device.
So if anyone has a ROM and updater that can work with this device, please link it to me, it's very important. I don't want to lose my PDA. If you haven't got a WM6 ROM, it can be even WM5, or even the stock ROM of this device, I just want to somehow revive it. Really, any ROM will do, just give me the proper updater and ROM. Or if you think the ROM wasn't erased from the device, please help me getting back to it.
Click to expand...
Click to collapse
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
d-two said:
Remove the battery and look which model you have....
something like PH20B or the FCCID: xxxBLUEANGEL...
Click to expand...
Click to collapse
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
JiGSaW_HTC said:
It says:
PH20B MDA III
FCCID: NM8BLUEANGEL
Click to expand...
Click to collapse
Please look here for install the right driver for windows 7 64x
d-two said:
Please look here for install the right driver for windows 7 64x
Click to expand...
Click to collapse
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
You have not read the tutorial right... you must install the driver manual!!!!
JiGSaW_HTC said:
Thanks, I've downloaded the PDFs and tried to follow the steps, but there were some problems.
The first strange thing I noticed was that the driver said it was already installed to my computer. I think that's not a problem, but still worthy to mention.
I have completed the driver installation, so I moved on to the ExtROM tutorial. Unfortunately this step failed completely, because it needs a working BA, and as I've said I'm stuck on the bootloader screen. Also I've tried to reflash the WM2003 that was in the tutorial, but it said that the Updater is not designed for my device. So I moved on to the final step, flashing - I downloaded the Updater and tried to flash the WM2003 you provided. I kept pressing Continue - but after getting to the last page, and pressing Continue for the last time, after about 10 seconds, the updater said Congratulations! The ROM have been updated successfully. But that was just a message, my BA acted like nothing happened. I'm still in the Bootloader and can't do anything. What am I doing wrong?
Click to expand...
Click to collapse
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
B-44 said:
Can't you exit bootloader screen by simultaneously pressing power and reset?
Did you disable USB-Connection in activesync? Is important to do.
If update runs till "congratulations" in very short time (update usually takes about 10 minutes - estimated ), it seems like updater didn't see the nk.nbf file, which should be 32.769KB.
Please don't throw bricked phones at me, but- is the file unzipped? (note: i don't mean opened)
And: though d-two has given you the drivers for Win7 (and he's the one you can really trust he's got the right stuff) you may just try
another PC. Many people have trouble when trying to update with Win7. I still use XP.
Click to expand...
Click to collapse
If I press power and reset simultaneously, the screen goes dead for a second, then bootloader comes up again.
Tried disabling USB connection in WMDC (No activesync for Win 7), it changed nothing.
The nk.nbf is EXACTLY 32.769KB, so I don't know why it won't see it. With some versions it sees it but gives me an error 150 (RUU not designed for this device).
If by unzipped you mean extracted, yes, all the files (EnterBL.EXE, nk.nbf, MaUpgradeUt_noID.exe, etc.) are extracted to a folder, it looks the same as in D-Two's tutorial.
Unfortunately I don't have an XP PC. Will using a Vista laptop do any better, or should I use some kind of emulator of XP and update from there? If so, can you link me to one of those?
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
B-44 said:
Sh*t.
Take out the battery for at least three days.
Then retry.
I lately had an VPA3 revived by this.
Always stuck in first step of bootscreen, already wanted to abandon it,
then after some days retried just out of some mood.
Worked.
XP emulator may be a good idea, but i'd have to google it the same way like you.
Because of my Siemens phones i haven't yet left original XP.
Click to expand...
Click to collapse
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
d-two said:
he is not stuck at the 4 color screen he stuck in the bootloader mode..
If the bootloader mode active with software is he not wakeup after 3 days without battery or something else...
the BLENTER.EXE erase at adress 0x40000 the first 4 bytes and this will active the bootloader mode!!!
you must install the driver like in the PDF!!!
and than you can flash it with any rom!!
if you have install the driver correct it must like this...
sorry for my bad english
Click to expand...
Click to collapse
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
JiGSaW_HTC said:
No problem about your english, mine isn't perfect too
I realized what is the problem. When installing the driver manually, it says that the driver is not signed, and therefore I can't install it. I do everything the same as you did, but I fail at this step. I can't get it to install. Any solutions for this? :\ I'm starting to worry about this.
Click to expand...
Click to collapse
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
d-two said:
Reboot your PC and press before windows start "F8" and select the option "Start without driver signature" or something else...
I don't know what is the exactly word spelling in English i use my windows in German :laugh:
Click to expand...
Click to collapse
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
JiGSaW_HTC said:
Found this option and I could install the driver You sent to me.
But the RUU still doesn't see my device. It acts the same as I was running it without my device.
Click to expand...
Click to collapse
have you use my updater?
d-two said:
have you use my updater?
Click to expand...
Click to collapse
Ignore my previous message. I just needed to reboot the computer. It updates now!! Thank you VERY VERY MUCH!! Finally I can use my PDA again Pressing Thanks button