Related
I know there's a lot of forums for this topic! i have tried following the procedure given at most of the forums but to no help. The upgrades just don't happen as the connection error 101 keeps popping up after executing the rom upgrade exe. I don't know how to use the mtty.exe and host.exe to fix the problem. I'm using vista ultimate on my desktop and wm6 rom (jwright 2.02.00) on the jasjar. before i got stuck in the bootloader mode, i remember getting the KITL option on the blue imate boot screen and enabling it. I'm stuck in the bootloader since then. I appreciate this forum and the people here...need your help. Thanks in advance.
Got it Resurrected
crooner999 said:
I know there's a lot of forums for this topic! i have tried following the procedure given at most of the forums but to no help. The upgrades just don't happen as the connection error 101 keeps popping up after executing the rom upgrade exe. I don't know how to use the mtty.exe and host.exe to fix the problem. I'm using vista ultimate on my desktop and wm6 rom (jwright 2.02.00) on the jasjar. before i got stuck in the bootloader mode, i remember getting the KITL option on the blue imate boot screen and enabling it. I'm stuck in the bootloader since then. I appreciate this forum and the people here...need your help. Thanks in advance.
Click to expand...
Click to collapse
Hi people...here's an update on how I came out of my crisis..(for a moment i thought there's some defect caused on the mainboard!) anyways, i went to a lot of threads pertaining to the 'stuck in bootloader topic' and mixed and matched the solutions. here's what i did.
unsuccessful efforts :
used the combination keys with reset to come out of the bootloader in vain.
tried hard-reseting the device in vain.
tried weird key combos in vain.
tried to upgrade rom (on vista ultimate) got connection error 101.
tried to reflash radio rom but got the error even though device was listed in the device manager
------------------------------------------------------------------------
Successful Effort:
Just when i thought that i'd have to bring my baby to the service center...i said a prayer to Jesus asking Him to fix it for me. Really got desperate and prayed...I got a check from Him to try using another computer with XP which i did but the Rom wouldn't flash. Still stuck on the bootscreen, I tried the radio upgrade on the computer running XP SP2 with the maupgrade noid stuff and there it was, upgrading the radio rom! I thanked the Lord for helping me for XDA Developers forum and I'm a happy Jasjar user once again. I hope you will get some help from my testimonial which is why I'm posting this!
hey.
i wanted to upgrade my o2 Xda Exec to WM6, i am not a stranger to flashing, and enjoy modifying consoles and such.
however i am running windows vista, and got the connection error (yes, i read through the stickies first) I was now stuck on the bootloader screen, no matter what i could do, and none of the utitlities, including mtty would work.
upon deeper research i learned that vista was a problem for flashing.
So i took my xda to a windows xp machine that i had freshly set up the day before:
installed active sync,
installed drivers,
disconected xda,
unchecked activesync usb connections,
restarted,
Installed "XDA_EXEC_WWE_21200_21207_11500.exe"
It then appeared to succesfully work.
upon hard rebooting though, i now have no screen, no bootloader, and no connectivity, hard rebooting brings up the white screen, upon hitting 0, nothing happens... i fear it is now bricked....
Will not charge, no orange light comes on when plugged either directly into power, or directly into computer.
its now an "Unknown Device" in vista and a "device thats malfunctioned" in xp, i cant connect anything too it.
mtty wont give me any options other than COM, on vista or xp.
can anybody offer any oppinions?
This is the device in question:
http://www.my-xda.com/xdaexec.html
Vista doesn't have any problems! I have flashed my XDA so many times under Vista that I count them! You only need the right driver that have been posted several times here in the forums! It is not Vista's fault the the stupid flash utility is as old as the earth itself!
i tried updating the drivers before flashing, with the ones i downloaded from here, but it said i couldnt as the drivers i had were better, even after uninstalling and re installing...
as a side note i found this if its of interest to anybody:
offical xda upgrade
http://www.my-xda.com/downloads/Xda_Exec_Upgrade_v1.30.162.exe
I have updated them manualy! And everything is fine! You only need to kill Sync center and Mobile device Center from task manager before flashing!
ok, well can anybody help me understand whats happened?
are there any steps i can take to diagnose any further, or will i write it off as a brick/
i tried updating the drivers manually, and it didnt work, mobile device center was disabled as well. yet something went wrong, it wouldnt connect, but it got far enough to wipe my rom. i had no version numbers of anything, and just a bootloader screen, after trying to upgrade with windows xp, i now have no response at all from my xda, it wont charge or anything.
can anybody help me diagnose any further? or help me understand what went wrong, if its not a case of windows vista and old programs.
Same for me ...
Xiviliai said:
ok, well can anybody help me understand whats happened?
are there any steps i can take to diagnose any further, or will i write it off as a brick/
i tried updating the drivers manually, and it didnt work, mobile device center was disabled as well. yet something went wrong, it wouldnt connect, but it got far enough to wipe my rom. i had no version numbers of anything, and just a bootloader screen, after trying to upgrade with windows xp, i now have no response at all from my xda, it wont charge or anything.
can anybody help me diagnose any further? or help me understand what went wrong, if its not a case of windows vista and old programs.
Click to expand...
Click to collapse
If you have noy figured it out yet then i would say i have exactly the same problem with my xda exec and i proved to be installation problem, what i did was, reflashed with original wm5 ROM first, after setting it up completelyi then flashed again with wm6, problem resolved automatically... so good news is your xda is still very much alive.i used windows XP though... give it a try mate!!
Manual bootloader mode and then reflash with an original rom of your choice.
That'll do the trick.
Psi
diffrences ??
hey can anyone enlighten me on wats the difference between o2 cda exec and imate jasjar ?? coz both seems to have the same specification and same functionality?
DEAD XDA brought back to life
I recently upgraded my XDA Exec to WM6 with no problems so offered to do same for my sisters XDA Exec but part way through activesync crashed. Needless to say after that her XDA was dead wouldn't do anything at all and appeared to have no usb connection no charging nothing. After a hard reset I did get the reset screen but pressing "0" or "x" did nothing.
After much reading of many forums I couldn't find the answer to this and so I had to give my sister mine Boo Hoo!!
Anyway not one to give up this is how I fixed it
I happen to have the XDA plugged into a different usb port to what I normally use and done a hard reset on it then pressed "0" then the PC popped up saying found new hardware and it was installed and working so I looked hard at the unlit and what appeared to be blank screen of the XDA I noticed then it said "usb" at the top and "2.0" at the bottom so I ran http://www.my-xda.com/downloads/Xda_..._v1.30.162.exe which doesn't need activesync even though it say it does on the start screen just carry on it found it ok and now its all back and working ok.
This may not work for you but the usb thing is easy to miss if you use the same port all the time and the instructions tell you you need activesync to run the flash program is misleading. Just to note I did have activesycn 4.5 installed and running when I run the xda up date exec but I'm certain it played no part in the process.
Of course I wish I had found this before I spent £150 on a replacement
anyone need an XDA Exec for Xmas????
wohooo free xda?me!me!
please help
p24hrsmith said:
I recently upgraded my XDA Exec to WM6 with no problems so offered to do same for my sisters XDA Exec but part way through activesync crashed. Needless to say after that her XDA was dead wouldn't do anything at all and appeared to have no usb connection no charging nothing. After a hard reset I did get the reset screen but pressing "0" or "x" did nothing.
After much reading of many forums I couldn't find the answer to this and so I had to give my sister mine Boo Hoo!!
Anyway not one to give up this is how I fixed it
I happen to have the XDA plugged into a different usb port to what I normally use and done a hard reset on it then pressed "0" then the PC popped up saying found new hardware and it was installed and working so I looked hard at the unlit and what appeared to be blank screen of the XDA I noticed then it said "usb" at the top and "2.0" at the bottom so I ran http://www.my-xda.com/downloads/Xda_..._v1.30.162.exe which doesn't need activesync even though it say it does on the start screen just carry on it found it ok and now its all back and working ok.
This may not work for you but the usb thing is easy to miss if you use the same port all the time and the instructions tell you you need activesync to run the flash program is misleading. Just to note I did have activesycn 4.5 installed and running when I run the xda up date exec but I'm certain it played no part in the process.
Of course I wish I had found this before I spent £150 on a replacement
anyone need an XDA Exec for Xmas????
Click to expand...
Click to collapse
can u please give the link again ??
your download link is invalid....can you post the file?
my jasjar is stuck and the pc wont accept it as a usb device....
02 XDA Exec Bricked
Hi - I have the same problem - the links dead can you post the file pls?
Fixed now:
This issue has now been resolved, not sure if you need to do all the steps but they worked for me:
1. Remove SIM card and SD card
2. Reinstall Active Sync and reboot
3. Reapply ROM
For me it doesn't work :-(
I am searchin since one month to find a way to get my Mda Pro to work... - On the Display says "Serial" when it is plugged...
Xiviliai said:
hey.
i wanted to upgrade my o2 Xda Exec to WM6, i am not a stranger to flashing, and enjoy modifying consoles and such.
however i am running windows vista, and got the connection error (yes, i read through the stickies first) I was now stuck on the bootloader screen, no matter what i could do, and none of the utitlities, including mtty would work.
upon deeper research i learned that vista was a problem for flashing.
So i took my xda to a windows xp machine that i had freshly set up the day before:
installed active sync,
installed drivers,
disconected xda,
unchecked activesync usb connections,
restarted,
Installed "XDA_EXEC_WWE_21200_21207_11500.exe"
It then appeared to succesfully work.
upon hard rebooting though, i now have no screen, no bootloader, and no connectivity, hard rebooting brings up the white screen, upon hitting 0, nothing happens... i fear it is now bricked....
Will not charge, no orange light comes on when plugged either directly into power, or directly into computer.
its now an "Unknown Device" in vista and a "device thats malfunctioned" in xp, i cant connect anything too it.
mtty wont give me any options other than COM, on vista or xp.
can anybody offer any oppinions?
This is the device in question:
http://www.my-xda.com/xdaexec.html
Click to expand...
Click to collapse
I rather think that you should first check whether your phone is really bricked, to read the instructions regarding this and to see how to recover from the brick
After you have recovered you phone, I recommend that you use Windows Mobile 6.5!
Thanks!
Always glad to help!
Have you seen the post date above you
Most likely he already solved or got another device
Besides that link does not include HTC Universal
Hi, i have just bought a new imate jasjam and uploaded the windows mobile 6 as per your instructions. Everything was going ok, then active sync kept stuffing up, i reinstalled it 3 times and only sometimes works, i have limited to no connectivity in my LAN, and my imate takes 2hrs to do anything once i touch the screen. i have tried hard resetting etc nothing! i have searched and searched for everything and found nothing, i eally hope someone can help me, i am at my wits end!
PLEASE HELPPPPPPPPPPPPPPP
Try putting it into bootloader and flashing hard spl and flash a new rom after that.
thank you!
i just tried to do that and it said error please connect the usb to the phone etc..and it is..
if this helps anyone- ipl 1.04 and spl.2.10.0lipro?
ggrrrr
Can you tell us what ROM you are trying to flash, and what OS you are using to connect with?
ROM VERSION: 3.30.2.1
ROM DATE: 05/15/07
RADIO:1.38.30.10
PROTOCOL:32.71.7020.12H
I have a windows xp sp2
i am so grateful to everyones input. thanks
usb connectivityy
Goto to the usb settings under communication and remove the tick from advanced usb fuctionality. Maybe unplug from USB first before doing that.
Thanks, have just tried that but it didnt work, still got the red cross on the icon and limited to no connectivity thru the LAN. i am so lost, i should have just left the phone as is ;-(
have you tried loading into the bootloader and then connecting the jasjam to your pc?
How to get into the bootloader is described here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Resets
once connected just run the offical update from telstra (which is a damn good rom btw) and it should return your jasjam to normal. The latest Offical update can be found here - http://forum.xda-developers.com/showthread.php?t=348436&highlight=telstra
hope that helps
edit; should have read first post. hmmm. try uninstalling activesync and reinstalling it, or try on another computer. i had this problem awhile ago, can't remember exactly how i fixed it, but it was a combination of new activesync, bootloader and hardresetting
ok, i have reset it- is the bootloader screen the one with 3 colours with ipl etc on it?
i connected it and it then said usb on the screen, but activesync can't connect it?
When you get to the bootloader screen with the 3 colors you need to reflash with a new ROM
thanks to everyone, i am now back and running! god knows hoe but thanks!
Hi, hoping someone can help.
Getting the following. Can't get past it. Also what does the Diam100 stand for as I notice others have different.
A tri-colored screen that reads as follows:
Diam100 64M
SPL-1.37.0000
MicroP-Diam (LED) v.11
-----------------------
PSOC-Diam STAGE_PVT v0x30
Upgrade ROM code error
Please try again
Thanks for you help!
1: state the subject in the thread title, that's what it's for
2: search is your best friend; the issue you mention has been discussed in several threads
3: I'd recommend: get into bootloader mode (seems like you can); install hardSPL again, flash again with any ROM supported by hardspl.
4: insert [solved] in front of your thread title.
5: this is NOT a relevant subject for this forum (it's got nothing to do with rom development)
apologies, im new to this (only got the diamond today) and havent been able to use it yet and this forum was the closest thing i could find to getting it working.
Im unable to enter bootloader mode (volume down, reset?)
Also can't get my diamond to connect to pc and keep getting connection errors when trying to install Hard-SPL?
Thanks, your help is appreciated.
The tricolor screen IS bootloader mode.
Just run the HardSPL, then Rom upgrade utility from a rom, and that's it.
IF you got it in this state, you'd probably want to return it (you got warranty?)
Thanks for your help.
Is HardSPL going to install even though ActiveSync isn't recognising the device (ie not connected). When i run it it seems to work and then a grey screen with 0% shows. Then the install program comes back with a 'connection problem' message,i go through all the steps but just keeps happening. I read posts on this earlier today but it seems the install program is fixed and shouldnt do it any more????
...also ive done all the firewall changes to make sure it connects etc etc. Forgive me if im not doing something that has been posted already, but i couldnt find it.
Thanks.
I had the same problem make sure you install the HARD SPL but the unsigned version not the sign version.....it should work them.....
i think there's two issues people are describing here..
1) installing hard spl.. if you get the 0% error, then you need to follow the instructions in the thread and manually run SSPL from your phone and then start the RUU
2) if you keep getting errors while trying to install your rom AFTER installing hard-spl, then you probably are flashing an unsigned ROM on the signed hard-spl.. go to the sticky thread and download a signed version of the ROM you want..
Thanks guys. I dont see how i can do the manual install, as it requires me to copy a file onto the diamond and at this stage i cant even get activesync to connect to it. I dont beleive its a problem with activesync or the pc as ive tried many many things, but rather that the diamond isnt communicating properly.
Also i havent even got to installing the new ROM yet as i cant get past HARDSPL install.
Do you think installing the un-signed HARDSPL version will work? as in will it install when the signed version won't?
all your help is very much appreciated. I cant wait to actually turn my phone on for the first time!
you haven't turned it on yet
is that right?
you have not had it working yet?
or have you tried to update it even before using the phone???????
yeh unfortunatley thats right, yet to turn it on. hopefully will have it up and running shortly...
1) can you confirm exactly what happened to get you stuck in the bootloader screen? (it usually doesn't just happen by itself)
2) Have you tried to soft reset to get your device out of bootloader?
3) are you flashing in win xp or vista?
4) are you connected through a usb hub?
yes, tried soft rest but it just returns to bootloader screen.
using winXP SP3. Not using a USB hub. have tried different ports.
Have tried the signed and unsigned versions of HardSPL.
I keep getting to the 0% grey screen and then the communication error 262.
Maybe i should try and just flash the original ROM? Does anyone know where I can download it from and the HTC e-club doesnt have it? Or is this not the next step???
Thanks!
yeah try the original ROM..
but still i don't understand how you got to this point.. what were you trying to flash when it got stuck in bootloader?
I bought the phone like this.
Do you know where i can get the original ROM from? I tried e-club (both worldwide and SEA) no luck.
Appreciate your help on this.
?? that's quite strange... is there any reason why you're not just returning it for a new set?
try this thread for SEA ROM
I bought it whilst overseas last week in SEA. Im now back in australia and would like to try my best to fix it before going down the long and difficult warranty path.
Do you think its buggered? Or the fact that its in the bootloader screen and giving me this message quite common on failed ROM updates?
Do you think an orginal ROM install will fix it? if so where can i get it from?
Thank you.
well that's what i'm asking..
you got this screen when you pulled it out of the box, or tried to update the ROM and then hung on this screen. also, if you did try an update, was it a SEA update, or australian ROM
i wouldn't say its a common issue.. i also don't think your device is bricked, since its showing bootloader.. diamond is relatively new so i don't really know a lot about getting it out of this state.
trying to load original ROM is a good option.. one thing is for sure, before any further flashes (after you get out of this mess) you want hard-spl on your device.
If flashing original ROM doesn't work, i'd suggest PM'ing walshieau, olipro, or pof as they know a lot more about this type of stuff.. do post your results
Thanks for the link above. i'll give it a go. is it different from the one in the ROM list??
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