Related
Hi all,
I've the following problem. A friend told me he found a new AKU 3.5 rom of Helmi and he sent it to me.
I unzipped it, checked the files who lookeed good and flashed my universal.
Once finished, tried reboot and got black screen.
After spending 2 hours to go back in bootloader mode (no success) and after looking in the files, seems he sent me a Blue Angel rom and no Universal.
Phone refuse to go in bootloader mode. Black screen. :s but when I put it in usb, windows says unrecognized USB device.
Any one can help please :$
Think Xanaxer needs his account deleted...sorry I can't help with the OP's problem
gloom said:
Hi all,
I've the following problem. A friend told me he found a new AKU 3.5 rom of Helmi and he sent it to me.
I unzipped it, checked the files who lookeed good and flashed my universal.
Once finished, tried reboot and got black screen.
After spending 2 hours to go back in bootloader mode (no success) and after looking in the files, seems he sent me a Blue Angel rom and no Universal.
Phone refuse to go in bootloader mode. Black screen. :s but when I put it in usb, windows says unrecognized USB device.
Any one can help please :$
Click to expand...
Click to collapse
I just tried several previous official and un-official upgrades but none detected the universal.
Tried mtty methode too but nothing detected on USB port. (Killed active sync modules with task manager)
Tried several times to enter in bootloader mode but nothing displays on screen like before. Screen stays black.
I hope it isn't broken cause seems windows detected something pluged on the usb
gloom said:
Hi all,
I've the following problem. A friend told me he found a new AKU 3.5 rom of Helmi and he sent it to me.
I unzipped it, checked the files who lookeed good and flashed my universal.
Once finished, tried reboot and got black screen.
After spending 2 hours to go back in bootloader mode (no success) and after looking in the files, seems he sent me a Blue Angel rom and no Universal.
Phone refuse to go in bootloader mode. Black screen. :s but when I put it in usb, windows says unrecognized USB device.
Any one can help please :$
Click to expand...
Click to collapse
your best bet with be take it back to your mobile phone vendor, because the motherboard is messed, and nothing can be done apart from replacing the motherboard
coolbeans252 said:
your best bet with be take it back to your mobile phone vendor, because the motherboard is messed, and nothing can be done apart from replacing the motherboard
Click to expand...
Click to collapse
No other way to get it back in bootloader mode ?
since the bootloader is also overwritten with something from the BA ROM, it is improbable.
Hi !
I had a similar problem, but I am in bootloader mode, but I can't reflash my board. Does anyone knows how should I do ?
Thanks
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".
Hi guys,
Can anyone help me here ?
When I try to start up my Phone, it always loads the bootloader ...
I tried running reflashing a rom and task29, but no help there :s
Does anyone have an idea what to try ?
Tnx
Nick
Some people with the same problem said that their batterie was broken. Can you try another batterie?
I'll give it a try
Will let you know ...
Lennyz1988 said:
Some people with the same problem said that their batterie was broken. Can you try another batterie?
Click to expand...
Click to collapse
Nope, doesnt help.
Tried with a friend's battery, and have the same result.
Also tried using his phone with my battery and worked perfectly.
Any other ideas?
Trickass said:
Nope, doesnt help.
Tried with a friend's battery, and have the same result.
Also tried using his phone with my battery and worked perfectly.
Any other ideas?
Click to expand...
Click to collapse
Just to ask: You're not (accidentally) holding down the volume key when you press the power key (or reset) to turn on, are you? That puts it into bootloader.
MCbrian said:
Just to ask: You're not (accidentally) holding down the volume key when you press the power key (or reset) to turn on, are you? That puts it into bootloader.
Click to expand...
Click to collapse
No, I'm not doing that
I thought maybe it got stuck though, something like that :s but when I do press it, I hear a pretty clear "click", so I guess it's not broken at all...
Also, I noticed that when I try to reflash a ROM, the "current image" (or whatever it's called) is blank ...
(I mean the thing that sais the version number of the currently installed rom)
Okay, sounds dumb I know, but did you flash a new rom after flashing Task29?
It is used to wipe the OS out completely BUT you then have to re-install a new OS...
Just thought I'd ask.....
Same issues.
Same issues on my touch pro 2.
The only solution i find in order to make it boot is with mtty on a Windows xp pc with no activesync.
Perform a
set 14 0
task 8
then the phone boot on the os but on the next reset stay in bootloader !
ultramag69 said:
Okay, sounds dumb I know, but did you flash a new rom after flashing Task29?
It is used to wipe the OS out completely BUT you then have to re-install a new OS...
Just thought I'd ask.....
Click to expand...
Click to collapse
Lol yeah I know that
Thanks anyway
Frederic.james said:
Same issues on my touch pro 2.
The only solution i find in order to make it boot is with mtty on a Windows xp pc with no activesync.
Perform a
set 14 0
task 8
then the phone boot on the os but on the next reset stay in bootloader !
Click to expand...
Click to collapse
Hm, I'll see if I can find a Windows XP pc somewhere and try ... MTTY doesn't seem to work with Win7 x64
Trickass said:
Lol yeah I know that
Thanks anyway
Hm, I'll see if I can find a Windows XP pc somewhere and try ... MTTY doesn't seem to work with Win7 x64
Click to expand...
Click to collapse
Hummm i have see somwhere a howto for mtty on W7... but i'm a little lazy i have choose to do this on a old windows xp
But this command are just temporary i'm searching for something more stable !
Some news from my Rhodium Stuck in bootloader
I have try to Hardspl it (Olinex 0.85)
The good news is i have manage to do it, the bad news is after that even the
set 14 0
don't manage to make it boot.
After a while searching, (thanks wiki of another phone) i have find those command :
password BsaD5SeoA
set 14 0 # Maybe it's usless now but in fact i don't know
set 1 0
task 8
And now i'm back to my start....
I tried using the MTTY commands, and when I did it the first time, the phone booted and performed its "first run setup" thing.
After rebooting though, it went back to the tricolor screen, and I can't get past it anymore, even with the same MTTY commands ...
Any other ideas ? :/
mtty, a lot of post on the internet...
hi,
I think we are a the same point !
I have find a way to start a boot with the HTC screen but the phone tel me that a txt file is missing on the sd card ???!!!???
with mtty :
boot
yes it's quite simple why i haven't think of that befor i don't know... but that didn't solve my problem at all.
I have send a mail to HTC in order to have a diferent point of view but all they said to me is doing a hard reset (who didn't do anything...)
I will post the avancement of my test but i feel a little stuck.
Note : After searchin on the internet, the set 14 0 tel to the phone to boot on the os after a flash (sometime the phone don't reconize the end of flash)
the set 16 0 (or set 16 1) disable (or enable) the RUUNBH tag on boot loader.
More Infos...
I have find a post on a other forum whos said that a defective battery could result to an unstable beaviour of the phone.
I have let it without battery for a day and, today it has directly boot on the OS.
I have ordered a battery on ebay and waiting for it maybe the solution ?
Frederic.james said:
I have find a post on a other forum whos said that a defective battery could result to an unstable beaviour of the phone.
I have let it without battery for a day and, today it has directly boot on the OS.
I have ordered a battery on ebay and waiting for it maybe the solution ?
Click to expand...
Click to collapse
Oke, I will try to take out the battery tomorrow as well ... Although, I tried using a different battery and it didn't help ...
Right now, I managed to boot using mtty set 14 0 > task 8, which seems to work
(sometimes, I need to do the task 8 twice in a row ...)
So as of now, I managed to flash a stock rom onto the phone, and only have to try and reset hardspl back to stock as well.
Waranty here I come ...
lol mine is out of waranty, and it's the solution i ve find everywhere !
did you try hard reset by holding the call and hang up button together when you power up the phone.
last time I remove a program and tha cause me to boot ot a black screen after teh bootloader. Hard reset fix the issue as it return teh phone to the sotck setting of the rom.
PUTALE said:
did you try hard reset by holding the call and hang up button together when you power up the phone.
last time I remove a program and tha cause me to boot ot a black screen after teh bootloader. Hard reset fix the issue as it return teh phone to the sotck setting of the rom.
Click to expand...
Click to collapse
yes, i've try it (HTC has send me the same advise) and... same issue !
In order to done the hard reset (who didn't execute when the phone is to boot in bootloader) i have do a set 14 0 and reset with power and holding the two call hang and power.
But thanks for the advise !
Frederic.james said:
lol mine is out of waranty, and it's the solution i ve find everywhere !
Click to expand...
Click to collapse
Out of warranty ?
How old is it then ?
Mine is just under 1 year old, so I'm lucky I guess ... and I hope
Trickass said:
Out of warranty ?
How old is it then ?
Mine is just under 1 year old, so I'm lucky I guess ... and I hope
Click to expand...
Click to collapse
Hum it's the phone of a firend who give it to me... and he has buy it on e-bay.... for the waranty sound difficult to retreive a bill and... I will search till i find something to do
hello guys,
after a long research i landed to this forum at last.
today morning i had a client who wanted to have new rom on his tp2 with russian language. but unfortunatly i flashed the tp2 with a wrong flasher! first time hapening something like this... i was pretty sleepy that i didnt even recognised that it was the wrong one... and now the client wants his phone back but the phone dosnt even turn on and not going in the boot menu... only when i plug the usb cable to the pc with the tp2, the pc recognises that there is a usb connected.. but only this.. im really stuck in a bad situation i would be very appreciative if someone can help me with this out the client will come tomorrow again, i hope there is some options to get the tp2 back alive
Try to flash back with stock, but depending on what you've flashed, it might very well be bricked.
This is why you should always be careful as to pay attention to what you are flashing.
Did you apply the wrong hSPL, or the wrong ROM? Did you flash something meant for a CDMA device on a GSM device...? Please, explain exactly what you have done.
Firstly thank you very much for your answer. I apply the wrong hSPL. HardSPLWrapper_Blackstone i used, the hSPL from blackstone >.< ..my device is htc touch pro 2 Sprint . It much be CDMA but with Gsm radio as far i know. actually the progress didnt start.. there were not a loading bar and no boot mode on phone screen (green-blue-red). suddenly phone turned off and red service light turned on.now when i connect it to pc,i hear usb connected sound and the pc reads the phone as ''qualcomm cdma tecnologies msm'' and requests driver for it.
Does anyone have a clue if there is a solution or what i can do ? or even if there is no way to fix it, except with Jtag ? :S
yildizgsm said:
Does anyone have a clue if there is a solution or what i can do ? or even if there is no way to fix it, except with Jtag ? :S
Click to expand...
Click to collapse
You flashed a RHOD with hSPL for BLAC. That's pretty blatant mistake dude.
I'm not sure if there's a way back. Try flashing stock like I already suggested. Try relocking too, I don't know.
You might have to go into mtty, erase everything, flash the radio, then flash stock. Next time, be more careful.
I would flash it back to stock but the problem is that i need to get activesync with the phone.. my pc dosnt connect to the phone with activesync because i cant open the phone :S do you think with mtty it could work mate ? im gonna search for that now.. thanks
yildizgsm said:
I would flash it back to stock but the problem is that i need to get activesync with the phone.. my pc dosnt connect to the phone with activesync because i cant open the phone :S do you think with mtty it could work mate ? im gonna search for that now.. thanks
Click to expand...
Click to collapse
Try flashing via SD?
yildizgsm said:
Firstly thank you very much for your answer. I apply the wrong hSPL. HardSPLWrapper_Blackstone i used, the hSPL from blackstone >.< ..my device is htc touch pro 2 Sprint . It much be CDMA but with Gsm radio as far i know. actually the progress didnt start.. there were not a loading bar and no boot mode on phone screen (green-blue-red). suddenly phone turned off and red service light turned on.now when i connect it to pc,i hear usb connected sound and the pc reads the phone as ''qualcomm cdma tecnologies msm'' and requests driver for it.
Click to expand...
Click to collapse
HardSpl doesn't show a progress bar when flashed. Can you manually put the phone in bootloader mode (Press volume down button and power it up)?
If you can get it into bootloader what does it show on the screen? You may be able to flash the shipped rom after you are in bootloader if when you connect to your PC it says USB toward the bottom of the bootloader screen and then click on the exe for the shipped rom on your PC. Or maybe try flashing the re-locker as suggested earlier to see if you can install the correct SPL.
i cant get bootloader mode(volum-,power up).im gonna try flash via sd if no succes then gonna try relocker ...i'll post result..
i cant get bootloader mode(volum-,power up).im gonna try flash via sd if no succes then gonna try relocker ...i'll post result..
Click to expand...
Click to collapse
If you flashed the wrong HSPL then you have bricked the device. There is no recovery outside of a jtag box. I don't know of anyone who has made one of those fora Rhodium anyway. It sounds like you owe your client some money.
By the way, if you can't get into the bootloader, then you can't flash via SD.
cajunflavoredbob said:
If you flashed the wrong HSPL then you have bricked the device. There is no recovery outside of a jtag box. I don't know of anyone who has made one of those fora Rhodium anyway. It sounds like you owe your client some money.
By the way, if you can't get into the bootloader, then you can't flash via SD.
Click to expand...
Click to collapse
Indeed, and a great way to end the thread.
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