Hello,hello,
Anyway without going into it too much i have my phone with imcokeman's 2.31 and all ready to go with a new screen. I'm trying to use mtty.exe on windows 7 and with usb turned off on wmdc and i keep getting "usb can not open" error
i tried administrator,xp compatibility,Eugenia project, nothing seems to be working.
If anybody has any idea how to fix this....then that would be coooool. otherwise i think i'm going to have to get a new phone. (htc of course!)
spuzzum said:
Hello,hello,
Anyway without going into it too much i have my phone with imcokeman's 2.31 and all ready to go with a new screen. I'm trying to use mtty.exe on windows 7 and with usb turned off on wmdc and i keep getting "usb can not open" error
i tried administrator,xp compatibility,Eugenia project, nothing seems to be working.
If anybody has any idea how to fix this....then that would be coooool. otherwise i think i'm going to have to get a new phone. (htc of course!)
Click to expand...
Click to collapse
Have you tried Virtual XP? Also, you did put your device in bootloader, right?
Windows 7 32 bit doesn't have that many issues, but 64 bit does... Try to get a machine with XP if at all possible. It will solve a lot (if not all) your issues (current and future )
yeah , i had it in bootloader 2.31, tricolor screen,with custom rom, never had too many problems doing this stuff with xp. I'll see what i can do in the next couple of days after that.....new or used phone. thanks for the reply.
Related
My friend's jamin when he tried upgrading with smart1 wm6
after the flashing process finished it gives the 3 colors of boot loader
the screen flickers continously with the 3 colors
no way to hard reset the device
and activesync doesn't feel it
I searched all the forum for a problem like this but I didn't find any
any suggestion please, or any help?
Flash NVID Rom and try Smart again. Read WM6 upgrade Manuel and readme for the ROM.
NetrunnerAT said:
Flash NVID Rom and try Smart again. Read WM6 upgrade Manuel and readme for the ROM.
Click to expand...
Click to collapse
Please how can i flash with the activesync doesn't notice my device and where's NVID Rom
Ok. I'll search for it but please help how can I flash it to the device which doesn't recognized or felt by PC
If your device is in bootloader mode, activesync cannot recognize it but this is normal. Jamin is recognize only as a usb device and you can downgrade it to NVID rom easly.
Then you could upgrade your favorite rom, I suggest PDAVIET 4.0.0.1
Bye for now
divxmaniak said:
If your device is in bootloader mode, activesync cannot recognize it but this is normal. Jamin is recognize only as a usb device and you can downgrade it to NVID rom easly.
Then you could upgrade your favorite rom, I suggest PDAVIET 4.0.0.1
Bye for now
Click to expand...
Click to collapse
I think I didn't discuss the problem well
The Problem is when I start to flashing a rom a message tells that check if the usb is connected and if the device is connected .
This is happen with the device is connected to the cable and the tricolor screen is flicking . and the device doesn't open doesn't flashing.
must use NVID rom. maybe qtek nvid one from here? http://wiki.xda-developers.com/index.php?pagename=Prophet_ROMs
hasanemara said:
I think I didn't discuss the problem well
The Problem is when I start to flashing a rom a message tells that check if the usb is connected and if the device is connected .
This is happen with the device is connected to the cable and the tricolor screen is flicking . and the device doesn't open doesn't flashing.
Click to expand...
Click to collapse
If the problem still there, Try to release the battery for 1-3 hours and put it again to the device, go to the boot loader and pray. Hopefully it could work. Actually, this way worked on my Himalaya and Prophet.
Just run the "Step 1" component of the PDAViet ROM (http://rapidshare.com/files/32728615/Prophet_PDAViet_Step1.zip), which is just a plain AKU 2.20 NVID. This will find your device even if its in bootloader mode (it doesnt depend on activesync). Just flash it with that sucker and you should have a working phone on WM5, then you can safely upgrade it to WM6 (or leave it if you like).
ekto said:
Just run the "Step 1" component of the PDAViet ROM (http://rapidshare.com/files/32728615/Prophet_PDAViet_Step1.zip), which is just a plain AKU 2.20 NVID. This will find your device even if its in bootloader mode (it doesnt depend on activesync). Just flash it with that sucker and you should have a working phone on WM5, then you can safely upgrade it to WM6 (or leave it if you like).
Click to expand...
Click to collapse
I shall try and tell you the result
error 260 this is the result
i have a slight variation problem like this...
1. i was upgrading my O2 Neo to the latest WM05 & the phone went to bootloader mode & the upgrade started searching for the phone as normal..then some error & it stopped upgrading while the phone was in bootloader mode..
2. at that time,i got an urgent call & had to leave the phone in bootloader mode...
3. when i came back..the phone was dead & now it wont startup at all.. not even in the bootloader mode.
4. Maybe the batteries dead...so i charged it (Over night)..nothing happened in the morning..
5. kept the battery removed for about 5-6hours & still nothing happens..it simply does not startup.
6.I've tried holding the camera button & resetting, but it wont go into bootloader mode.
7. i;ve tried holding the connections button + camera button _ reset but it wont hard reset...
can anyone help me here...
what can i do???
hasanemara said:
error 260 this is the result
Click to expand...
Click to collapse
Error 260... If i remember correctly that's "cant find device" or something.
Few things to check:
Is the PC you are upgrading on running windows vista?
If so, use a different PC running windows XP.
Have you tried a different USB cable?
If not, do so, this tends to be the cause of problems like this.
Have you checked device manager?
Go to control panel, Administrative tools, computer management, device manager and see if you can find your device. If it has a yellow ! icon on it or is listed as "Unknown device" or anything like that then you may need to reinstall the drivers (int hsi case the easiest way to do that is to reinstall activesync). If everyhting is working properly it should show up as "HTC USB Sync", "PocketPC USB Sync" or something like that under the heading "Mobile Devices".
Have you just plain tried another computer, regardless of the OS?
I found that I could never get my phone to flash on my laptop, but it worked without a problem on my desktop. This is not to say laptop's cant do it, it simply means some computers just have problems like (in my case i believe) no USB 2.0, or too low-powered USB ports.
ekto said:
Error 260... If i remember correctly that's "cant find device" or something.
Few things to check:
Is the PC you are upgrading on running windows vista?
If so, use a different PC running windows XP.
Have you tried a different USB cable?
If not, do so, this tends to be the cause of problems like this.
Have you checked device manager?
Go to control panel, Administrative tools, computer management, device manager and see if you can find your device. If it has a yellow ! icon on it or is listed as "Unknown device" or anything like that then you may need to reinstall the drivers (int hsi case the easiest way to do that is to reinstall activesync). If everyhting is working properly it should show up as "HTC USB Sync", "PocketPC USB Sync" or something like that under the heading "Mobile Devices".
Have you just plain tried another computer, regardless of the OS?
I found that I could never get my phone to flash on my laptop, but it worked without a problem on my desktop. This is not to say laptop's cant do it, it simply means some computers just have problems like (in my case i believe) no USB 2.0, or too low-powered USB ports.
Click to expand...
Click to collapse
No I didn't change any and I can connect my o2 xda mini to the same cable
I want to ask few technical question
HOW CAN A SOFTWARE DAMAGE THE DEVICE?
CAN A SOFTWARE FOR EXAMPLE BURNS A PROCESSOR OR SOMETHING LIKE THIS?
If So there will be a big problem with those types of devices
a virus for example can destroy my device's board or processor!!
Yesterday My friend went to an I-mate customer service who tel him that
the board had been destroyed by the bad software !!!!!!!!!
Please Give me technical advice about this problem
and is there a web site for him to buy this board (i-mate jamin)?
I've tried everything... even tried it on my desktop... but my phone just wont turn on now. i've kept the battery removed for more than 8hrs now... i've even charged it for more than 8hrs non-stop..nothing happens..
maybe i should get hold of a charged battery & try it with that battery...?
Any clue how to get my phone started??
got it working !!! PHEW... i used my HP battery which was charged & put it into it..now i've got my bootloader & i'm installing the new OS as we speak... 15% done.... keeping my fingers crossed
done.. got my HP Ipaq battery , which was charged & my new started up in bootloader more.. PHEW !!!
66% done... keeping my fingers crossed
ok, installed...now, one more problem..my touch screen's not working...???
Any idea what to do?
i installed "Prophet_PDAViet_Step1"
Well... I've been without a phone for close to 3 weeks now (because the phone is bricked) and have been reading and reading and reading..
anyway.. the point being is I think i have came close (I've tried the SD method and it hasn't worked) is there any way at all, to be able to connect the phone on activesync, even when bricked, because thats the only way i can flash the rom!!
respond please!
Not sure what exactly your specific issue is but, having just recovered my, Hermes from "Brick-Hell". I'll try to help.
First, do you have access to an XP machine and AS4.5? This would make things easier... if not have you read MrVanx's guide to syncing on Vista?
But try this anyway:
In WMDC de-select connect via USB (or whatever it says, I forget as I dumped Vista for Linux).
Remove the battery from your device for several minutes. In the meantime reboot your Vista machine. When it comes back up, make sure allowing USB connections is still un-checked.
Go here and download the T-Mobile ROM (2nd Link) to your desktop.
Return the battery to your phone and connect via USB cable. Then run the T-Mobile ROM app from your desktop. If it doesn't work, at first, keep trying until you get by the "Erasing" part. The ROM update will eventually return an error but after that you should be able to flash any ROM to your phone. But first I would Hard SSPL upgrade.
I just did this under XP (in a virtual machine, no less) and it worked like a charm.
Good luck.
OK....I've followed all the tutorials, searched, and still I can't figure out how to get Hard HSPL2 on my tmous HD2 so that I can then begin the process of installing custom ROMs. When I run the HSPL2 from the zip, I follow the on-screen instructions, select 2.08hspl, and select next. After that my phone does the tri-colour thing and then it just sits there with a green bar moving back and fourth on the screen. It doesn't give me a percentage amount to let me know how far along I am!
I let it sit for 30 mins....and still nothing. And also....activesync disconnects once HSPL2 is ran. If anyone knows whats going on please help me. I really need a custom ROM. Thanks in advance.
EDIT: Just so you guys know....I am running Windows XP SP3, I have Activesync 4.5 installed, HSPL will load and got thru the process, but nothing after that. The green bar will just go back and fourth for a long time.
I'm a noobie to WinMo. I don't know if my advice will help, but I'll share. I had a similar problem when I tried installing HSPL2. For some reason, when my HD2 was in bootloader mode, it would disconnect from the USB connection and reconnect. But HSPL wouldn't finish the installation and I kept getting a fatal error message that connection was lost. All I did was was run HSPL2 again after I got the error message and it worked fine. If you're getting the same error message, it should work.
I'm not getting the error msg, It's just that the HSPL installer is stuck on the installation screen and just sits there. The green bar will go back and fourth for like 20-30 mins. IDK what I can do to fix it.
i'd say try every usb port,especially try to use one round the back.and don't forget to run as administrator,
I've downloaded the HSPL_1024. What happens is I'll run it, it'll go thru the process, but in won't install. There's a green bar that goes back and fourth forever. My phone will sit on the tri-colour screen and nothing else will happen. I let it sit that way for a long time and still nothing. Shold I do a hard reset or what?
Watch This!
http://www.youtube.com/watch?v=a6Bt0S7dCmM
It's funny, I just watched that video. Followed exactly what that guy did. His finished in under 2 minutes or so. After about 15 minutes...mines still has the green bar going back and fourth. I am getting so frustrated. I love this phone but I can't stand having to deal with things like this in order to get to it's full potential.
its a long shot but try taking out the sd and sim, and i repeat what i said about usb ports. hspl is far more picky about it than regular flashing.
try starting already in bootloader, if the word serial doesn't change to usb then there is your problem.
Im getting an error msg now. ughhh! And the error msg comes after letting the program run for about 10 mins. I'm going to try and take the sim and SD card out and then try again. IDK what I'll do after that.
samsamuel...I've tried everything you said. Now I'm getting a "Critical Error". I'm on a Macbook running Windows XP SP3 in VMWARE. I have activesync 4.5 (not WMDC) Does this make a difference at all? If none of this helps I'll just have to do a hard reset and try it again.
tylawtheboss said:
samsamuel...I've tried everything you said. Now I'm getting a "Critical Error". I'm on a Macbook running Windows XP SP3 in VMWARE. I have activesync 4.5 (not WMDC) Does this make a difference at all? If none of this helps I'll just have to do a hard reset and try it again.
Click to expand...
Click to collapse
ohhhh well there you are then. when the phone is running propperly, the mac can happily pass the usb signal through, but when it boots to bootloader, the mac fails to propperly pass through the signal. (Based on stuff that i have read , , i dont have a mac)
Got a friend with a PC? use that to flash HSPL, and then on your own machine give bootcamp a try to actually run xp rather than vmware for flashing.
tylawtheboss said:
samsamuel...I've tried everything you said. Now I'm getting a "Critical Error". I'm on a Macbook running Windows XP SP3 in VMWARE. I have activesync 4.5 (not WMDC) Does this make a difference at all? If none of this helps I'll just have to do a hard reset and try it again.
Click to expand...
Click to collapse
Use a PC...that'll work
just loaded Windows 7 on my laptop and went to flash to the latest energy rom. Im not familiar with WMDC but when it goes to flash, it gives me the RGB screen when rebooting my tp2 then my pc reports cannot complete update due to lost connection... wtf... why? win7 not compatible? am I a retard?
Not at all
XITruthiX said:
just loaded Windows 7 on my laptop and went to flash to the latest energy rom. Im not familiar with WMDC but when it goes to flash, it gives me the RGB screen when rebooting my tp2 then my pc reports cannot complete update due to lost connection... wtf... why? win7 not compatible? am I a retard?
Click to expand...
Click to collapse
I have Windows 7 and flash my ROM. It's not a Windows 7 issue more than likely. It sounds like you have not connected with Activesync before you tried to flash your ROM. The reason I say, you haven't established a communication port with your pc and it therefore cannot enter a usb connection in bootloader. I have had this happen when I didn't wait for activesync to sync with my computer. I got an ERROR: screen, so I know what you're talking about.
Just sync your device with Mobile Device Center and as soon as activesync completes, run the ROM install.
Let me know if this doesn't work. We'll proceed from there.
XITruthiX said:
just loaded Windows 7 on my laptop and went to flash to the latest energy rom. Im not familiar with WMDC but when it goes to flash, it gives me the RGB screen when rebooting my tp2 then my pc reports cannot complete update due to lost connection... wtf... why? win7 not compatible? am I a retard?
Click to expand...
Click to collapse
Its compatible but it can be rly retarded if you dont do it like it wants
1st install wmdc and let it connect to you phone
2nd disable usb connections on wmdc
3rd and so forth go onto flash your device
if it still says that then connect to the internent and boot your phone into the tri color screen WHILE still connected to computer and try flashing from there
I have flashed roms and done Task29 several/many times from my W7-32-bit laptop and my W7-64-bit desktop, and both work fine -- no issues. I didn't do any special procedures or settings (none on purpose, anyway)...it just worked.
I know this doesn't solve your problem...but it might help to know that W7 should work.
I guess by now this should be solved. If not, try getting into bootloader mode (turn your phone off, and turn on by holding power+volume up button). Then connect the USB cable and try flashing.
I also use Windows 7 64b, sometimes when flashing roms got the same problem, and had to reset the phone from the color screen using the button. This has never happed after I started using Task29, because I have to get into bootloader mode manually.
Ok... Id like to continue this post for only one reason, I am in fact a retard...
Simply reading the stickys is always crucial in your quest to not appear far more retarded than you actually are. Apparently windows 7 update DOESNT update WMDC to 6.1. I Re-Read the "For Noobs" sticky and realized hm, maybe I should check to update WMDC and WHAM, no problem.
The moral of the story, read the previous posts. Asking questions in text based form on the forum when perfectly good answers already float about right in front of your eyes is just a complete waste of precious bandwidth, so dont do it.
I apologize.
Sometimes I post things and feel like a complete idiot, I actually just had a lot of trouble flashing my tp2 to a cooked rom for the first time, but I've had HTC phones since the wing and still run into problems. This last bout of problems I had was fixed by simply reseting my phone to factory default :O
Well, it's been almost a year since I've had the upgrade bug. I have been running the 8107 (unlocked, I think it was a YUKI/XBOXMOD ROM) version of Windows Phone 7.5 for a while now. I finally saw there's a new version, and I want to flash it.
Perhaps it is because it has been so long since I've done this, but I cannot get the USB connection I need when running DWI.exe.
I've tried all the fixes on my Windows 7 x64 bit computer and I'm stumped.
Tried running customRUU.exe while running DWI.exe...didn't work
Tried making sure DWI.exe was being run as Administrator...didn't work
Can anyone help? I'm just trying to get from one WP7 ROM to another...I already have HSPL 2.08 and Mag 1.13.
Is this a problem with the phone or the USB drivers on my PC?
Sorry for this, I used to remember all this stuff but my HD2 has been rock solid (except for touch tones not registering on calls...which means I can't call any customer service centers that require you to enter selections via touch tones) for so long I can't figure this out...
Do I need to do a hard reset? Go back to WM 6.5 and start all over?
Is it the USB drivers? Where are the ones you need for this?
Any help is appreciated. LONG LIVE THE HD2!!
UDPATE: Nevermind, re-installing the WMDC for WM 6.5 did the trick.