hello, guyz!
this is a full story of mine after wp7.8 by H2OWNER FLASH AND BATTERY GOT DEAD:
"HD2Owner, dear,
it's not to abuse as we know all the risks we take testing roms, just asking for your advice:
1. I did install your latest rom
2. after some time it stopped charging at all
3. the problem is the phone got unable to charge under sd android as well.
4. at the end of story battery got dead - can't load magldr.
5. managed to direct power on it via red/black cables of usb to +/-
6.but the problem still the same - I can't charge battery via phone
7. and even more - can't enable usb via bootloader (tricolor) - serial only:
- usb flasher works only with wp7 rom install;
- magldr, hspl, task29 flash via usb flasher fails with critical error 0000001;
- naturally, can't flash winmo;
- usb storage works well.
I'm completely lost what to do
h2owner, dear, I made grand research over google and xda.
can add only, that in addition I've already tried:
1. nbh of the default os flashed fine
2. pins in phone battery slot are properly aligned
3. I did try to clean both usb cable and usb port
and issue is still here - no charge under any os/no usb in bootloader/usb mass storage works fine/can flash only any wp7 build/the rest "flashes" lead to no usb connected
and what I can say is only that this is almost definitely connected to the usb power management of the phone by your wp7.8 build.
thus, that would be great if you know what to do and how to fix it. probably, reflash your wp7.8 updated with this fix?"
as for the moment I've managed to flash original wm3.14 rom via sd.
still no usb in bootloader, no charge.
don't know what to do yet.
don't even say usb is broken -
THE MAIN POINTS ARE THAT
1. I STILL CAN FLASH WP7/7.8 VIA USB FLASHER
2. I STILL CAN FLASH MAGLDR VIA USB FLASHER
3. BUT NOTHING MORE
4. AND USB MASS STORAGE WORKS AS WELL
5. UNDER WP7/7.8 STILL NO USB/NO CHARGE
the couple of thoughts to take in attention:
1. I did close zune while it's starting first time with wp7.8 by HD2OWNER under admin account
2. I did try another pc (win7, mine is w7 as well - same results, no usb)
please, post your suggestions, but remember - I CAN FLASH WP7/7.8 VIA USB FLASHER, WHICH MEANS HARDWARE IS OK.
okay, first news on the subject:
HD2Owner Today, 02:54 PM #3079
Recognized Developer - OP
Thanks Meter 1459
Posts: 1,947
Join Date: Oct 2009
Location: Neuhausen am Rheinfall
MORE INFO >
DONATE TO ME
important info related to usb2video:
usb mode is not changed back to zune/charge mode with a simple reboot.
you have to click usb2video appicon again and switch back to normal zune mode (with needed reboot).
otherwise, performance will stay choppy and device will never charge/connect to zune again.
WILL KEEP YOU UPDATED
this is going to be my personal blog alike..
okay, speaking with myself..
in order to have wp7.8 back, I need hspl and magldr..
then how to flash hspl now from spl 1.42 and without usb???
omfg.
hi dimdimdim !
this Thread & post for you only
i think must usb
try with this tool
http://forum.xda-developers.com/showthread.php?t=1090783
maybe can help you
boxmax said:
hi dimdimdim !
this Thread & post for you only
i think must usb
try with this tool
http://forum.xda-developers.com/showthread.php?t=1090783
maybe can help you
Click to expand...
Click to collapse
yes, I tried...but this is not more than interface for same magldr, hspl, recovery...method is not changed..
but thanks for suggestion!
Maybe is problem with usb drivers on your pc,try to reinstall them,tricolor screen won't recognize usb if you dont have drivers proper installed....
zexmunze said:
Maybe is problem with usb drivers on your pc,try to reinstall them,tricolor screen won't recognize usb if you dont have drivers proper installed....
Click to expand...
Click to collapse
I did try it on another pc...still no usb
This does sound like a hardware issue to me. I know you dont think it is an hardware issue, because some of the communications still work.
But the active driver determines the hardware id's that broadcasted. The drivers are mainly on OS level. Booting another OS would definitely solve problems in the problematic OS.
I think the one of the power-pins on your USB jack is broken.
The only other possibility that I can think of, but it is unlikely, is that Magldr somehow screwed up and interferes with the USB-power-management.
The Video-to-USB is unlikely the cause, because AFAIK it does not influence the power-management of the USB.
Heathcliff74
Heathcliff74 said:
This does sound like a hardware issue to me. I know you dont think it is an hardware issue, because some of the communications still work.
But the active driver determines the hardware id's that broadcasted. The drivers are mainly on OS level. Booting another OS would definitely solve problems in the problematic OS.
I think the one of the power-pins on your USB jack is broken.
The only other possibility that I can think of, but it is unlikely, is that Magldr somehow screwed up and interferes with the USB-power-management.
The Video-to-USB is unlikely the cause, because AFAIK it does not influence the power-management of the USB.
Heathcliff74
Click to expand...
Click to collapse
okay, if jack is broken, then I have only chance to send the phone to the service.
the point is that I'd like to know whether there is a way to go deeper, than OS level.
is that possible with tools, available at home? with cab for wm6.5 or nbh with drivers?
h2owner wrote it is not possible to charge the phone anymore if apply usb2video and not enable normal mode back again.
I can't say 100% I do not push usb2video once. I'd rather say I did it once and no more. and after that my battery got dead during a call.
thus, usb2video may get stuck on it's half way...
just to be sure - is there any option to apply some tool, which can go that deep into a hardcoded drivers?
if that was possible to get somehow wp7.8 back and apply usb2video again...but - no usb means no hspl..
by the way, JIC, isn't it possible to use usb2video cab on wm65?
dimdimdim said:
okay, if jack is broken, then I have only chance to send the phone to the service.
the point is that I'd like to know whether there is a way to go deeper, than OS level.
is that possible with tools, available at home? with cab for wm6.5 or nbh with drivers?
h2owner wrote it is not possible to charge the phone anymore if apply usb2video and not enable normal mode back again.
I can't say 100% I do not push usb2video once. I'd rather say I did it once and no more. and after that my battery got dead during a call.
thus, usb2video may get stuck on it's half way...
just to be sure - is there any option to apply some tool, which can go that deep into a hardcoded drivers?
if that was possible to get somehow wp7.8 back and apply usb2video again...but - no usb means no hspl..
by the way, JIC, isn't it possible to use usb2video cab on wm65?
Click to expand...
Click to collapse
Just tested for you: The phone DOES charge when USB Video Out driver is selected. I just switched back and forth and it charges always. Using HTC HD2 with exact same ROM as you used.
There are no such low level tools to look into drivers. At least, not for WP7 that I know of. But what do you expect to see? If you are booting Android, it uses Android drivers, with Android power-schemes. Completely different, but same problem. That proves for me, the problem is at hardware level. Any ROM flash or Hard Reset should always reset the USB mode/driver.
Maybe you can try to flash MagLdr on it (again). That is the only software-solution that I can think of.
Good luck,
Heathcliff74
Heathcliff74 said:
Just tested for you: The phone DOES charge when USB Video Out driver is selected. I just switched back and forth and it charges always. Using HTC HD2 with exact same ROM as you used.
There are no such low level tools to look into drivers. At least, not for WP7 that I know of. But what do you expect to see? If you are booting Android, it uses Android drivers, with Android power-schemes. Completely different, but same problem. That proves for me, the problem is at hardware level. Any ROM flash or Hard Reset should always reset the USB mode/driver.
Maybe you can try to flash MagLdr on it (again). That is the only software-solution that I can think of.
Good luck,
Heathcliff74
Click to expand...
Click to collapse
okay, this is that kind of proof I'd want to have before I send the phone for repair.
thank you, Heathcliff74.
dimdimdim said:
okay, this is that kind of proof I'd want to have before I send the phone for repair.
thank you, Heathcliff74.
Click to expand...
Click to collapse
You can try to reinstall Magldr, although I don't think it will help.
Just to be clear: Information I gave is the best of my knowledge, but it is provided "as is". I don't take responsibility of any costs that arise from using the provided information, even when that information proves to be incorrect afterwards.
That said, I hope they can fix it for you. But I guess a good repair man can easily determine if the usb jack is indeed broken.
Good luck,
Heathcliff74
Heathcliff74 said:
You can try to reinstall Magldr, although I don't think it will help.
Just to be clear: Information I gave is the best of my knowledge, but it is provided "as is". I don't take responsibility of any costs that arise from using the provided information, even when that information proves to be incorrect afterwards.
That said, I hope they can fix it for you. But I guess a good repair man can easily determine if the usb jack is indeed broken.
Good luck,
Heathcliff74
Click to expand...
Click to collapse
I did reinstall magldr when still had hspl 2.08...but now I'm on spl...
thus..happy repairing!
I did already replace usb socket half of year ago, that's why I did struggle so much for not hardware issue
Related
I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
I have also tried to use ActiveSync to version 3.8 (I found this suggestion from this web site) but bad luck it can't detect my BA device at all. I have also tried to revert back to WM2003SE but still get the same problem. My system is WinXP SP2 & O2 IIs. So Please help I am in the dark right now.
Same problem here...
su2003 said:
I have upgraded from WM2003SE to WM6 (the first released from XPlode version OS 5.2.1620 build 18125.0.4.2) without any problem. Now I want to upgrade from that version to the current release, but the ActiveSync (I am using 4.5) always disconnect after MaUpgradeUT_noID has detected the previous installed OS. So I got an error message like "cannot to the device" or so. It happens everytime even I just try to upgrade the Radio rom.
Click to expand...
Click to collapse
get into boot loader mode,then try
(press record button + power button and reset at same time)
addan said:
get into boot loader mode,then try
(press record button + power button and reset at same time)
Click to expand...
Click to collapse
Have tried that already but still get the same error. I have even reformatted my PC and reinstalled WinXP and ActiveSync 4.5 just in case there are viruses or so but also get no luck.
Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Did you soft (or hard) reset your BA and reboot your PC after failure? (Try clean upgrade, and in bootloader).
Yes, at this time you asked me. Nothing changed.
Did you (succesfully) establish an ActiveSync partnership before upgrading?
Yes.
Did you try unchecking Enable advance network functionality in USB to PC (under settings, connections)?
Yes. I did it.
More over, if I started BootLoader mode before execute MaUpgradeUt_noID.exe the program get struck while performs device information checking, I have to pull it out from Sync station the program then continue running but without any information (like the existing OS version etc.)
how long did you wait for the program to respond before you find that its stuck ?
Here it takes about 2 min to find the device
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
2. place it to cradle
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
4. start upgrade utility and follow the onscreen instructions
5. perform hard reset (the three options thing)
thats all
Xplode's new cube cab
deleted... off topic
how long did you wait for the program to respond before you find that its stuck ?
It was about 5 min and the program still had no responses. I then have to pull it out and the program continue running but without any information (like I had mentioned it before).
Here it takes about 2 min to find the device
Unfortunately not with mine.
Proper upgrading procedure, as it was said 10000's of times
1.put your device in bootloader mode
Yes. I did it.
2. place it to cradle
Yes. I did it.
3. kill activesync (optional - if you dont do it the upgrade utility will do it for you, but sometimes activesync stays on and fail the upgrade process)
I have tried it both with and without killing the activesync.
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
su2003 said:
4. start upgrade utility and follow the onscreen instructions
Yes, but once I started the upgrade I have noticed that the activesynce has disconnected my device.
5. perform hard reset (the three options thing)
I didn't have chance to go to this point.
thats all
I think the main problem is the activesync has disconnected my device suddenly when started the utility. I have also tried to take out anythings that using USB port like mouse, ext. DVD, printer, scanner just in case the upgrade utility may conflicts with those devices.
I think I shall try to change the PC to upgrade my device to make sure that it wasn't caused from hardware defection.
Click to expand...
Click to collapse
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
Good luck!
With regard to your last remark: you stated earlier you did a fresh reinstall of XP. Now, why would you install and connect all these peripherals if you only want to upgrade your BA rom??? All you need is a fresh WinXP and ActiveSync...
Did you really do a fresh install and follow the wiki and the tips mentioned again (and again)?
You are getting me (and probably all of us) confused.
First of all, Sorry if I make you and other confused. I have began to unsuccessfully upgrade my device since Friday. So I decided to help myself at first by try to do everything I can do by myself. I have formatted PC HDD and also reinstalled activesync because I thought the utility may conflict with other program on my PC or from Viruses. I have also tried many ways with hard reset and cold reset etc. to upgrade my device but have no luck. That was with very fresh new installed WinXP PC. Unfortunately, I have to use this computer for my job also. So that's why I have to install printer & scanner driver including MS Office, AutoCAD and other necessary program to serve my job . I have falled with upgrading but I do not want to have problem with my job. Hope you understand my essential.
Your answers to especially points 4 and 5 of xplode tips to me clearly indicate that you do not really take (enough) time to understand the procedures (or what you are doing) and want to have WM6 running asap with no effort at all...
Since I began to upgrading and everytime I have executed the utility I have always wait & wait but I just never look at the clock to see how long I have waited. Xplode has just warned me to take enough time so I started to upgrading but with clock at this time. I have already mentioned that I have successfully upgrade from WM2003SE to the WM6 (previous version) so as a user I have enough experience and know what I am doing.
Your remark "I think the main problem is the activesync has disconnected my device suddenly when started the utility" only confirms this as this is the whole point of boatloader and was furthermore indicated it would do exactly so by xplode earlier on.
This is just my opinion to let you guy see and understand the problem. That's it.
Please do take time and hence show consideration to all of us that are trying to help you in preparing yourself properly before trying to attempt any further upgrade.
I think I have already put a lot of effort about upgradind my device. I have reformatted and reinstalled all necessary programs. It took me out almost half a day to do this. And not only with my PC I have also reinstalled all programs on my device with an old OS version since I have lost them all from hard reset. Other than that I have also tried & tested upgrading the device during the time. The only word I can say that It was not funny to do all of this. It was not really a hard job but it took almost my weekend time.
Good luck!
Yes I do need it barely. Actually I have already felt a little lucky got from all of you that try help me solving the problem. Thanks.
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
April 1 said:
su2003, nice answer.
His main problem is that he does not understand that activSync will work if the device is in a normal state but when device goes to bootlogger mode, its only USB connection that will help a PC to talk to Device and not activSync.
Click to expand...
Click to collapse
Thanks for your additional.
I have also tried using different PC to upgrade the OS but got the same result.
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
I am quite sure that the screen has displayed USB but the number is 2.07 not 2.06. I am not sure about the meaning of the number, it could be the version.
I have also brought a new USB-XDA IIs cable yesterday, just in case the cardle was defected but it doesn't work also, I have got the same result.
khanem said:
you have to be sure that your BA when cradled display USB (after getting into bootloader mode) instead of serial 2.06 than run the upgrade utility
Click to expand...
Click to collapse
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Conclusion:
Bad Hardware(Flash ROM)?
Your Bootloader is toasted or had it's LAST flash of it's lifetime???
We can say that... but hopefully not for your sake.
Because as you have said you've done EVERYTHING that was posted.
and though our Senior's "inputs" didnt worked out the way it SHOULD work.
I cant say it's a waste of time to answer your questions.
But there are no more questions to ASK
and there are no more questions to ANSWER
They're all been said here.
All you have to do is PRAY HARD leave the BA rest for a day...
remove the battery...
think things out, clear your mind... sleep...
then execute Xplode's Walkthrough from Step 1 the next day.
but be sure to have the battery fully charged.
Your BA is not dead and your bootloader is not toast. The only problem you have is probably you are impatient. Go to the Wiki and follow the procedure exactly as it is written. It will work. By the way, if you kill Activesync (ie disable USB connection in activesync connection setting), put your device in bootloader mode and connect your usb cable (in that order), run the upgrade and it will work. Forget about activesync.
su2003 said:
I am quite sure that the screen shown USB 2.07 (should be differ version than your).
I have also brought a new USB-XDA IIs sync cable but getting the same result.
Click to expand...
Click to collapse
I use xda IIs and the bootloader mode shows ver 2.07, and i dont have any probs installing. I dont think the version 2.07 has got something to do with your problem.
You said that you tried other pc and it doesnt work, and it worked before when you upgraded previously. I think you know enuf about upgrading if you have done it before....
did you have problem with sync connection before? I was just thinking maybe there is something wrong with your BA....like actual hardware problem with the cable connection??
what about firewall? would it affect it - I doubt it cause its not in sync mode.... but at this stage, maybe just try all possibilities to try to get it working.
Good luck
Mhm. I'm not sure I've really followed all the intricacies of this case ... But whatever, here's my two cents for a safe upgrading procecedure:
1) use a cradle, not a USB cable, and make sure the cradle's
power supply is plugged into a wall outlet. It also helps to make
sure the cradle is plugged directly into the PC, not via any kind of
USB hub. No other devices should be connected to that same USB
channel. I suppose temporarily disconnecting other (unneeded) USB
devices from the computer can't hurt, either.
2) I guess "kill ActiveSync" can mean various things ...
however, here's the best way to do it I think: as sofene mentioned,
disable USB connections (what the hell - disable ALL connections) in
ActiveSync settings. Then reboot the PC. No need to look for ActiveSync
processes and kill them manually -- disabling the connections will take
care of that. Rebooting ensures that ActiveSync's driver code is really
unloaded.
3) remove SD card and, for good measure, SIM card from the BA.
4) perhaps soft (or even hard) reset your device
5) put device in Bootloader mode
6) insert device in cradle, start upgrade utility, off you go ...
By the way, ActiveSync has got nothing to do with the ROM upgrade utility, and it should therefore not have been necessary to re-install ActiveSync, etc. You just have to make sure it does not get in the way of the upgrade process. As far as I understand the process, the ROM upgrade should work equally well on a PC that does not even have ActiveSync installed.
Long story short my phone worked fine for months. Went to a 1.56 Rom active sync stopped working. I have already tried everything associated with AS problem, everything. Went to get it repaired at HTC America in Houston, TX there gay and dont support T8285. I have tried flashing via memory card but I seem to be retarded doing it that way. Engineer said mini usb slot works fine, cooked rom may have corrupted AS. Customer service would not let him fix my phone because it was an "aussie version". I just want the phone to sync is that too much to ask? Anyway $100 bucks to anyone that can make it work paid via paypal immediately.
moved out of development
Personally I think your mad offering $100. I'm sure most people would have hepled you for free, including myself. I'm not after your money but offer my assistance.
Have you tried doing a hard reset? uninstalling activesync & reinstalling it?
Flashing different rom. If you can't flash through SD Card, have you tried flashing again via usb. You don't need phone sync'd
Put your phone into bootloader and then connect to pc via usb. At bottom of screen the text should change from 'serial' to 'usb'. Now flash phone by running rom (cooked or stock etc) you downloaded. Put .nbh and ruu file into same folder and then open ruu file and follow instructions.
I severely doubt cooked rom affected activesync.
EDIT
As bonesy said below, you'll need either USPL or HSPL to flash 1.56+ based rom.
Full tutorial or dummies guide to flashing 1.56+ based roms can be found in cRaCKwHoRe's guide. See my signature
Turn off your phone, Take out your memory card, Plug the miniUSB in then power on (Hold volume down press power holding volume down still) This will bring up a coloured screen. Run the ROM Wrapper package exe (BlackstoneRUUWrapper) This SHOULD now install the right ROM.
Please make sure you are using a 1.56 rom with the HSPL or i think it has problems with GFX.
When windows loads go to start>settings>connections>USBtoPC
this is on 6.5 rom not sure about 6.1 :/
Untick Enable faster data synchronizaion, I had to do all this on works computer to update a ROM god knows why but this was my fix.
ROM Should load as should activesync now.
Please let me know if this helps
Tried to post in ure original threads but mods were moving to trash each time BAH!
Thanks to both of you guys for your suggestions. I thought I was not a noob when it came to flashing roms but once I could not do it via usb I was a whole different story. Yeah I am offering the $100 just to get people to help. I know you get slammed if you ask a question so I figured I would make it worth someone's time. I am going right now to pick it up from the repair center so I will try during my lunch in about an hour.
Fallen Spartan said:
Personally I think your mad offering $100. I'm sure most people would have hepled you for free, including myself. I'm not after your money but offer my assistance.
Have you tried doing a hard reset? uninstalling activesync & reinstalling it?
Flashing different rom. If you can't flash through SD Card, have you tried flashing again via usb. You don't need phone sync'd
Put your phone into bootloader and then connect to pc via usb. At bottom of screen the text should change from 'serial' to 'usb'. Now flash phone by running rom (cooked or stock etc) you downloaded. Put .nbh and ruu file into same folder and then open ruu file and follow instructions.
I severely doubt cooked rom affected activesync.
Click to expand...
Click to collapse
I tried uninstalling and reinstalling active sync. Different cables, different computers, xp and vista, everything, checked usb enhanced, etc ,etc.
bonesy said:
Turn off your phone, Take out your memory card, Plug the miniUSB in then power on (Hold volume down press power holding volume down still) This will bring up a coloured screen. Run the ROM Wrapper package exe (BlackstoneRUUWrapper) This SHOULD now install the right ROM.
Please make sure you are using a 1.56 rom with the HSPL or i think it has problems with GFX.
When windows loads go to start>settings>connections>USBtoPC
this is on 6.5 rom not sure about 6.1 :/
Untick Enable faster data synchronizaion, I had to do all this on works computer to update a ROM god knows why but this was my fix.
ROM Should load as should activesync now.
Please let me know if this helps
Tried to post in ure original threads but mods were moving to trash each time BAH!
Click to expand...
Click to collapse
Thanks for breaking it down barney style for me. I will try this very soon. If it works my friend you got $100 smackers.
no worries, Glad to help (if it does lol)
bonesy said:
Turn off your phone, Take out your memory card, Plug the miniUSB in then power on (Hold volume down press power holding volume down still) This will bring up a coloured screen. Run the ROM Wrapper package exe (BlackstoneRUUWrapper) This SHOULD now install the right ROM.
Please make sure you are using a 1.56 rom with the HSPL or i think it has problems with GFX.
When windows loads go to start>settings>connections>USBtoPC
this is on 6.5 rom not sure about 6.1 :/
Untick Enable faster data synchronizaion, I had to do all this on works computer to update a ROM god knows why but this was my fix.
ROM Should load as should activesync now.
Please let me know if this helps
Tried to post in ure original threads but mods were moving to trash each time BAH!
Click to expand...
Click to collapse
So I got my phone and this is what it says.
BLAC120 32M
SPL-1.56.01Olinex
MicroP-Blackstone (LED) v6
and it's just red green blue and white no word on the bottom. Ran BlackstoneRUUWrapper with the nbh file that I wanted and it gave me a connection error. Now it says Seiral in the white.
Fallen Spartan said:
Personally I think your mad offering $100. I'm sure most people would have hepled you for free, including myself. I'm not after your money but offer my assistance.
Have you tried doing a hard reset? uninstalling activesync & reinstalling it?
Flashing different rom. If you can't flash through SD Card, have you tried flashing again via usb. You don't need phone sync'd
Put your phone into bootloader and then connect to pc via usb. At bottom of screen the text should change from 'serial' to 'usb'. Now flash phone by running rom (cooked or stock etc) you downloaded. Put .nbh and ruu file into same folder and then open ruu file and follow instructions.
I severely doubt cooked rom affected activesync.
EDIT
As bonesy said below, you'll need either USPL or HSPL to flash 1.56+ based rom.
Full tutorial or dummies guide to flashing 1.56+ based roms can be found in cRaCKwHoRe's guide. See my signature
Click to expand...
Click to collapse
Well I get it into bootloader no problem but then plug in the usb cable and nada, it says serial. So then I tried starting bootloader mode with the cabe and still nada, it does not even say serial. If I unplug it then it says serial. I have tried both ways to run the RUU Wrapper and I keep getting the usb conncetion error
serial?
Hi, please can you post a screen shot of where it says serial at boot screen?
stoolzo said:
Hi, please can you post a screen shot of where it says serial at boot screen?
Click to expand...
Click to collapse
I cant because I cant use my software that would do that since it wont sync to my computer.
snap shot
just take a snap shot with a webcam or digital camera if you have one.
stoolzo said:
just take a snap shot with a webcam or digital camera if you have one.
Click to expand...
Click to collapse
let me see if this comes thru ok.
turcomora said:
let me see if this comes thru ok.
Click to expand...
Click to collapse
Here yo go. This picture is with me having the device plugged in it charging fine. Then entering bootloader mode. If I unplug then it will say serial. If I dont plug in before then enter bootloader it will say serial still.
thanks
ok, that looks pretty normal,so to recap you fully powerdown the phone by taking the battery out, put the cable into both the phone and pc and the turn on holding volume down and it just sits there?, what happens when you press volume up at this point?
stoolzo said:
ok, that looks pretty normal,so to recap you fully powerdown the phone by taking the battery out, put the cable into both the phone and pc and the turn on holding volume down and it just sits there?, what happens when you press volume up at this point?
Click to expand...
Click to collapse
Only thing I was not doing was taking out the battery. Just tried that and still same screen. Nothing happens when I press the volume up button just stays there.
pc
do you have another pc to try this on to rule out an actual active sync problem?
stoolzo said:
do you have another pc to try this on to rule out an actual active sync problem?
Click to expand...
Click to collapse
Yeah I have been trying on my latop, home pc, and work pc and nothing same result. I have tried different usb cables, os, reinstalling, everything. Only thing I have not tried is flashing via sd card yet.
brick
its sounds like you have a corrupt spl, it is definately worth trying the sd card as it may allow you to activesync but it may then fallover when it reboots and goes into boot mode. This i where user viperbjk (see android dev thread) may be able to help as he has successfully managed to unbrick a phone.
I had this same problem but powering down and simply triggering the and spl reflash resolved it. your problem sounds different though.
Hey, small problem here. I was charging my HD2 earlier today with no problems at all, I flashed the 1.72 stock ROM back onto my phone, and it seemed to be charging fine for a small while after that. But now, after I tried charging my phone, it doesn't seem to recognise there's a USB connection at all. The LED at the speaker-grille isn't doing anything, and the the phone tells me it isn't connected by USB when it's plugged into a computer.
I tried a tonne of things, checked the cable and switched it, soft-reset it, took the battery out, hard reset it, and even blown inside the socket to try and get rid of anything that might be blocking it, but it just isn't showing it's plugged in AT ALL any more... and now the battery is dead, so I can't do anything with it now to try and help it. :/
The only sign I have that the phone realises it has any sort of USB connection, is when I tried to hard reset the device, (I used the hold volUp+volDown+Power method) and it shows the message 'press volUp to hard reset,' usually when I do this, pressing volume up doesn't do anything when the phone is connected by USB for some weird reason - and I have to disconnect USB for the phone to hard reset. I figured this wouldn't happen if the phone doesn't realise it has a USB connection, but when the cable was plugged in, it still wouldn't hard reset until I took it out. So it shows there must be some way the phone knows it's connected.
I'm running the WWE 1.72 ROM with radio 2.10. 50.08_2 if it helps.
Any suggestions?
*Bump*
Sorry for the bump, but it would really help if anyone could help explain this.
I think a bit of trial and error would be best here to establish whats at fault.
phone, cable, or usb port.
-try plugging into a different usb port
-try a different cable (if you have one)
appologies if you have tried these allready.
Tried another cable again just incase, still nothing though. My iPods connected via that USB port I tried using, and that's working fine, so it doesn't seem like that's it, either...
Hi:
I'm having a similar problem. I had plugged in a new retractable usb cable, and when I did, the phone shut off. I rebooted, and tried my original cable, but the phone doesn't charge or sync. I've also tried hard/soft reset, wall charger, usb charger, and none of that seems to work.
Any suggestions?
Thanks.
No idea if this is related or not but my USB connection stopped working after I got the "bttrayce.exe is not a valid pocket pc application" problem (Thanks TomTom! ) so it would appear the USB port has some weird dependencies!
Fixed it by renaming the windows\btsdkce30.dll file (added "[temp]" to the name just in case!) and soft-resetting.
Might be worth a try?
r u using activsync or windows mobile centre ???
USB Issue
I've got exactly the same issue, running HyperROM 3.01.405.T1 and Radio 2.06.51.07.
Suddenly USB isn't working, tried various cables and I suspect it's a software issue somewhere.
Charging isn't a problem at the moment, I have a charging station (ebay from Hong Kong) so I can access the phone and try and resovle this.
I'm going to go back to the stock rom (I assume I'll find that somewhere on XDA) and upddate the Radio version and see if that sorts it.
If anyone has worked out what's casuing this generally let me know as I can imagine this will take a lot of trial and error to solve!
Thanks
have you fixed it?
i am having a similar issue:
I have recently updated my HTC HD2 rom to version 3.14.410.2.
After that i have installed tomtom navigator, but when i turn on the device it returned a message 'BTTRAYCE' is not a valid Pocket PC application'.
I looked at the forums and it was recommended to delete files Windows\BtSdkCE30.dll and
\Windows\BtCoreIf.dll, so i did.
Unfortunately my usb connection is now not working, and i think it could be related to the deletion of those 2 files.
I made a hard reset, but the problem still persists.
can anyone help me please?
My problem solved
Hi i got the same problem , i use ARTEMIS 48 rom 3.14. so my phone suddenly droped to the ground last night but i was charging after that .... next days morning i wanted to connect it to my pc via activesync but it dose not connect .... even disk drive did not work and i could not charge it via AC CHARGER and PC , i toyed around with it here is what i did
1- tried on another pc (result wass the same it did not worked)
2-i hard reseted it (result = the problem was not solved )
3-i went to setting>>>>system>>>power>>>battery and unchecked the option "when phone is on , do not charge ...."
4- i connected it to pc it was not recognozed by pc but it was charging !!!!!!
5-after that i connected it to AC ADAPTOR and it was charging !!!!!!
6- i decided to flash my rom and do a HSPL so my phone will not brick so i connected it to activesync via bluetooth and it was as sucess
7-mean while i was searching this forums
8- i checked my SPL ver
9- i soft-reset and stuning it was recognized by pc and everything was back to normal
in my XP i think it was due to BAD ASS ANDROID ROM and some custom roms bugs....
fpcraveiro said:
have you fixed it?
i am having a similar issue:
I have recently updated my HTC HD2 rom to version 3.14.410.2.
After that i have installed tomtom navigator, but when i turn on the device it returned a message 'BTTRAYCE' is not a valid Pocket PC application'.
I looked at the forums and it was recommended to delete files Windows\BtSdkCE30.dll and
\Windows\BtCoreIf.dll, so i did.
Unfortunately my usb connection is now not working, and i think it could be related to the deletion of those 2 files.
I made a hard reset, but the problem still persists.
can anyone help me please?
Click to expand...
Click to collapse
Uninstall TomTom and the problem goes away.
You can download versions on TomTom Navigator 7 with the Bluetooth files removed - like * HERE *
I don't have an OS installed...
This is due to aMAGLDR being installed and when I had the device open.. I created a 'temp' folder and my next task was to create a 'create_to_sd_root', well I renamed the temp folder to that... bad move? I think so. My system acknowledges the device, however I'm unable to access it. I.e. my computer(no icon), windows mobile center(not connected), etc. Please help! I need my phone!
MrHellas said:
This is due to aMAGLDR being installed and when I had the device open.. I created a 'temp' folder and my next task was to create a 'create_to_sd_root', well I renamed the temp folder to that... bad move? I think so. My system acknowledges the device, however I'm unable to access it. I.e. my computer(no icon), windows mobile center(not connected), etc. Please help! I need my phone!
Click to expand...
Click to collapse
I you were trying to flash Android you just need to flash Clock Work Mod (CWM) and then place the .zip file for the Android ROM on your SD card and use CWM to flash the Android ROM. It is links to Youtube videos in the OP of the thread showing you how to flash CWM and the ROM.
Are you could flash back to Win MO through USB and bootloader or SD card and bootloaderr.. If you go for USB and bootloader make sure you see USB in the white bar of bootloader befor tryng to flash the ROM. Also thew SD card metrhod will remove HSPL if you use a Official and not a custom ROM.
Well I've figured out how to get the android os on there, however I'm unable to locate the drivers for AD8? I'm still unsure about what folder/files need to be on my microSD if I'm running the Desire HD Froyo(current) I cannot access any internal/external(microSD). Help?
MrHellas said:
Well I've figured out how to get the android os on there, however I'm unable to locate the drivers for AD8? I'm still unsure about what folder/files need to be on my microSD if I'm running the Desire HD Froyo(current) I cannot access any internal/external(microSD). Help?
Click to expand...
Click to collapse
You have to use MAGLDR's mass storage option to get access to your SD card, or use the mount storage option in Clock Work Mod. I recomemd usingvthecnass storagecin MAGLDR though as I have had trouble gettingvthecdrivers for mount storage in CWM to install but have never had a problem with the mass storage option in MAGLDR.
T-Macgnolia said:
You have to use MAGLDR's mass storage option to get access to your SD card, or use the mount storage option in Clock Work Mod. I recomemd usingvthecnass storagecin MAGLDR though as I have had trouble gettingvthecdrivers for mount storage in CWM to install but have never had a problem with the mass storage option in MAGLDR.
Click to expand...
Click to collapse
How do I get back the loader without booting up? Obviously haven't been able to copy the rar files. Could this be why my GPS and other functions could not be working properly?
imanh said:
3-i went to setting>>>>system>>>power>>>battery and unchecked the option "when phone is on , do not charge ...."
Click to expand...
Click to collapse
Thanks this sorted my problem!
imanh said:
Hi i got the same problem , i use ARTEMIS 48 rom 3.14. so my phone suddenly droped to the ground last night but i was charging after that .... next days morning i wanted to connect it to my pc via activesync but it dose not connect .... even disk drive did not work and i could not charge it via AC CHARGER and PC , i toyed around with it here is what i did
1- tried on another pc (result wass the same it did not worked)
2-i hard reseted it (result = the problem was not solved )
3-i went to setting>>>>system>>>power>>>battery and unchecked the option "when phone is on , do not charge ...."
4- i connected it to pc it was not recognozed by pc but it was charging !!!!!!
5-after that i connected it to AC ADAPTOR and it was charging !!!!!!
6- i decided to flash my rom and do a HSPL so my phone will not brick so i connected it to activesync via bluetooth and it was as sucess
7-mean while i was searching this forums
8- i checked my SPL ver
9- i soft-reset and stuning it was recognized by pc and everything was back to normal
in my XP i think it was due to BAD ASS ANDROID ROM and some custom roms bugs....
Click to expand...
Click to collapse
I did the same but no work. I have issue #USB not recognized# after installed Android Transformer SD ver.
In three color screen I have USB connection working fine. I could install HSPL4, update Radio, but Win 6.5 has a USB problem.
I don't think this is a hardware issue or I am wrong?
Still confused. Should I take my phone to service?
Hi,
I have the similar problem with my hd2, but worse. Out of 3 different comouters I tried none can see the phone connected and gives me the error saying one of the USB device connected to this computer has malfunctioned and cannot be recognized. I have tried two different cables. I cannot connect my phone through latest magldr using USB flasher or USB mass storage modes. Moreover, when I connect my phone in rainbow screen (hspl screen where you install magldr), it should change to USB from serial but even that does not happen. ANy solutions?? I think its my phone.... Is there any way to revert this back to normal. I don't want a brick.
mcdoc said:
I did the same but no work. I have issue #USB not recognized# after installed Android Transformer SD ver.
In three color screen I have USB connection working fine. I could install HSPL4, update Radio, but Win 6.5 has a USB problem.
I don't think this is a hardware issue or I am wrong?
Still confused. Should I take my phone to service?
Click to expand...
Click to collapse
Your USB drivers for the defualt bootloader (multicolor screen) seem to be working fine, so no you do not have a hardware problem. You might want to uninstall Windows Mobile Device Center or Active Sync, which ever one your computer uses. Then re install it. Also go to device manager in your comtrol panel while you have hour HD2 booted up and connected via USB and clck on update drivers for hour phone, it should be listed in device manager.
kushki said:
Hi,
I have the similar problem with my hd2, but worse. Out of 3 different comouters I tried none can see the phone connected and gives me the error saying one of the USB device connected to this computer has malfunctioned and cannot be recognized. I have tried two different cables. I cannot connect my phone through latest magldr using USB flasher or USB mass storage modes. Moreover, when I connect my phone in rainbow screen (hspl screen where you install magldr), it should change to USB from serial but even that does not happen. ANy solutions?? I think its my phone.... Is there any way to revert this back to normal. I don't want a brick.
Click to expand...
Click to collapse
When you say your Serial in boorloader does not change to USB this tells me you are having driver issues or hardware issues with your micro USB port on your HD2. My bet is it is just driver issues. I sugest you uninstall and rei nstall Wimdows Mobile Device Center or Active Sync which ever one your computer uses. These programs contain the USB drivers for the HD2 and MAGLDR partialy relies on those drivers to. So maybe that will solve your problem.
Hello,
here is the situation.
i have a hd2 with magldr 1.13
android in nand
android in sd
both are working fine.
im trying to flash wp7 but my pc wont even pick up the connection (device not listed in devmgmt) however the phone is charging no problem.
i have installed, uninstalled and re-installed:
android sdk tools
windows mobile device center
windows phone sdk
i have manually removed each drivers after uninstalling all these through devmgmt.msc
i have also tried all this on 2 other PCs, with the same results so far.
i will try on a 4th PC later tonight.
i havent had the opportunity to try another cable yet.
what is causing this?
Thanks,
In wmdc did you untick "allow USB connections"?
That doesn't make any sense. If you flashed Android to NAND it should Flash WP7 to NAND with the same ease.
Make sure you hate .net 4.0 installed too, I know that helped me.
on the phone do you have it set to charge only from USB?
menu button - settings - Connect to pc - Default connection type
yep "allow USB" is unticked
i have .NET 4.0 installed...
i dont even have that in android:
"menu button - settings - Connect to pc - Default connection type"
do i have a faulty phone? the last time i flashed was about 2.5 weeks ago
willrider said:
yep "allow USB" is unticked
i have .NET 4.0 installed...
i dont even have that in android:
"menu button - settings - Connect to pc - Default connection type"
do i have a faulty phone? the last time i flashed was about 2.5 weeks ago
Click to expand...
Click to collapse
I don't understand what the problem is exactly:
You connect your HD2 to your PC, load up MAGLDR and select usb flash mode.
then you're running the DAF WP7 flasher and then it fails to connect or what?
orangekid said:
I don't understand what the problem is exactly:
You connect your HD2 to your PC, load up MAGLDR and select usb flash mode.
then you're running the DAF WP7 flasher and then it fails to connect or what?
Click to expand...
Click to collapse
on the phone, nothing happens.
on pc flasher fails after a while.
also on the tri-colour HSLP boot, i can see "serial"
but i cant seem to put in "USB" mode.
i tried booting into HSPL with the USB connected but then it wont display "serial" or "USB"... it stays blank
willrider said:
on the phone, nothing happens.
on pc flasher fails after a while.
also on the tri-colour HSLP boot, i can see "serial"
but i cant seem to put in "USB" mode.
i tried booting into HSPL with the USB connected but then it wont display "serial" or "USB"... it stays blank
Click to expand...
Click to collapse
oh well if bootloader stays on serial its almost certainly hardware, cos it should switch to USB regardless of whether flashing works and drivers and what not. You say you can charge so I would suspect a broken data pin inthe socket,perhaps dirty, perhaps bad solder, perhaps faulty cable.
samsamuel said:
oh well if bootloader stays on serial its almost certainly hardware, cos it should switch to USB regardless of whether flashing works and drivers and what not. You say you can charge so I would suspect a broken data pin inthe socket,perhaps dirty, perhaps bad solder, perhaps faulty cable.
Click to expand...
Click to collapse
He's saying it doesn't say serial or USB, so it might be some software issue, "it stays blank"
I would flash stock via SD, then flash HSPL, task29, then flash magldr, then try again.
yea, but since it does say serial when usb isn't connected, means it is detecting something, because it can tell the difference. You may be right in a corrupted bootloader, but id bet its more likely hardware, shorted data pins, or a break on either the phone or the cable. (all just guesswork, of course, , , hurry up and find out, OP! minds with nothing better to do need to know! hehe)
orangekid said:
I would flash stock via SD, then flash HSPL, task29, then flash magldr, then try again.
Click to expand...
Click to collapse
@OP
+1 on that, but of course it will all stop at "stock via SD" if that doesnt fix it,because hspl gone, no usb to reapply it, no radio flashing, so no more android, just stock winmo roms,, so think carefully what you want, if you can live with what you have, id be tempted to leave it alone until you need to.
samsamuel said:
yea, but since it does say serial when usb isn't connected, means it is detecting something, because it can tell the difference. You may be right in a corrupted bootloader, but id bet its more likely hardware, shorted data pins, or a break on either the phone or the cable. (all just guesswork, of course, , , hurry up and find out, OP! minds with nothing better to do need to know! hehe)
@OP
+1 on that, but of course it will all stop at "stock via SD" if that doesnt fix it,because hspl gone, no usb to reapply it, no radio flashing, so no more android, so think carefullyu what you want.
Click to expand...
Click to collapse
That's true, if you flash stock via sd then you're back to SPL 3.03, but reflashing HSPL might be what you need to do, so it's hit or miss.
If it's hardware then you will find out this way and since you'll hopefully be back to stock SPL you could do warranty on it.
I hate to say it but that's most likely a dead physical USB port. I work on the HD2's daily and have seen this problem several times and it was 100% not software related which I have verified after a fully memory sweep and write of a JTAG dump from a working phone to the defective one. In these case the phone would also charge but had no PC connectivity either. You can however flash all the WinMO ROM's you would like over the SD-Card and definitely still benefit from the SD-Card style of booting Android ROM's so the phone is not a total wash. You can also still hope that Cotulla or some DEV will come up with a way to flash CWM Recovery from the SD-Card to the NAND. Then you could even still have NAND based Android ROM's as the CWM step is the only part of MAGLDR to Android that involves PC > Phone flashing.
The port is cheap at about $6.00 USD but the skill required to put one on is high. I don't offer it as a service yet but I'm planning on it soon as I solder frequently on JTAG ports smaller than the usb ports themselves and have the skill to do this.
EDIT: I'm also not 100% sure it's the port to blame but most likely it is. However, it could still be something inline with the USB data bus on the phone to blame.
connexion2005 said:
I hate to say it but that's most likely a dead physical USB port. I work on the HD2's daily and have seen this problem several times and it was 100% not software related which I have verified after a fully memory sweep and write of a JTAG dump from a working phone to the defective one. In these case the phone would also charge but had no PC connectivity either. You can however flash all the WinMO ROM's you would like over the SD-Card and definitely still benefit from the SD-Card style of booting Android ROM's so the phone is not a total wash. You can also still hope that Cotulla or some DEV will come up with a way to flash CWM Recovery from the SD-Card to the NAND. Then you could even still have NAND based Android ROM's as the CWM step is the only part of MAGLDR to Android that involves PC > Phone flashing.
The port is cheap at about $6.00 USD but the skill required to put one on is high. I don't offer it as a service yet but I'm planning on it soon as I solder frequently on JTAG ports smaller than the usb ports themselves and have the skill to do this.
EDIT: I'm also not 100% sure it's the port to blame but most likely it is. However, it could still be something inline with the USB data bus on the phone to blame.
Click to expand...
Click to collapse
If this is the case I wouldn't flash stock via SD since you have no way to flash HSPL after that.
Just bought a used HD2 (TMOUS). I checked the bootloader and it already had HSPL installed. However, I wanted to flash stock ROM and do task29 prior to installing HSPL again myself.
I flashed the stock ROM v3.14.531.1 via microSD card method. Then I tried to run task29 and it failed. Bootloader wouldn't detected the USB connection. I also try to install HSPL but it doesn't work. I get an error: USB COnnect Failed!
When I connect to PC or wall charger, the phone charges perfectly fine. I even see the icon that says its connected.
When I am on the bootloader and connect the phone to my PC via USB, the white background area says "Serial" and it doesn't change to "USB".
I tried using different USB cables and also different PC, but still no luck.
What is wrong? Why can't I connect via USB? Help please.
Have you tried droidexployer? Doubt that'll work but worth a shot. What might be wrong is you don't have the proper drivers installed.
Sent from my Desire HD-2 using XDA App
htccraze said:
Have you tried droidexployer? Doubt that'll work but worth a shot. What might be wrong is you don't have the proper drivers installed.
Sent from my Desire HD-2 using XDA App
Click to expand...
Click to collapse
Droidexployer is for devices running rooted android. mine is still stuck on windows, i can't install hspl in order to run android...
i am sure its not a driver problem because i have another hd2 which connects perfectly fine.
Have you tried it on a different usb port on the pc? Sometimes one will work while another won't for some reason. Also remember to check the options in ActiveSync or WMDC to ensure usb connections are allowed, seems a stupid mistake, but one I have made myself before. If all that fails, maybe try on a different pc or with a different usb cable. Sorry for the super simple answers, I see you're not a brand new user, but its often these simple little things that hang us up
Change the battery
Change the battery ?
I seen your comment that said you already had hspl so I just assumed it was on android, sorry. Yea the different usb ports is a great idea if it wasn't for the fact that you even tried it on a different computer as well. Since you said you bought it used would you mind saying where from? I've known people who have problems with they're phone & can't find out how to fix it so they try and sell it on ebay. If you did get it from there the best thing to do is contact the seller and explain your problem. Ask if it had this problem before and say you don't want this phone if it's not repairable. With ebay you only have a short time to file a complaint if it leads to that.
Sent from my Desire HD using XDA App
another "simple" thing..
check for dirt or fluff in usb port
same here but I have EU version of HTC HD2...
also i Have MIUI 1.8.5. Gibgerbread 2.3.5 and same thing with bootloader...when start phone everything works fine !!!
If you find any solutions please write it to me so i can solve problem! Thanks
Are you able to charge the phone? if not, it's possible the microusb port is broken.
yes able to charge phone....i think its manufacture something cause tryed to connect to other PC with other USB and still same prob.
sportman123 said:
yes able to charge phone....i think its manufacture something cause tryed to connect to other PC with other USB and still same prob.
Click to expand...
Click to collapse
Have you installed windows mobile device center?
I am having the same issue. It worked a couple weeks ago. Now I can not get USB connection in MAGLDR or Bootloader...
Any help?
Yeah, me too.
Get your self a new sparkly xoom and wanna put android on my hd2. Oh well no mobile internet for my xoom. Unless any one knows of any wm6.5 app/prog that'll do it?
Arty U.K.