After upgrading my HTC diamond with any ROM based on win.mobile 6.5 when i softreset the device, the device is doing hardreset and starting completly fresh installation. What might be the problem.
here is your solution
http://forum.xda-developers.com/showthread.php?t=490182&highlight=strange+problem
I hava windows Vista. I tryed MTTY with USB connection, but every time i get "USB port cannot be opened"?????? And what will I get wit this procedure? What actually is the problem?
Funny I started having that problem this morning. I did a reset about 30 mins ago and now my device won't even boot up. I think it's bricked... Just hangs at the Rogers start up screen.
*sigh*
read this
Related
My DOPD - bought in China was running a chinese version of WM5.0 and I wanted to install a english version.
After upgrading my DOPOD 900 with the upgrade : Universal_Upgrade_v1.30.68_radio_1.09.0.zip I have problem.
It is really DEAD. soft reset does nothing and a hard reset only gives the option of "0" and "X" which do nothing.
the USB is no longer recognised and nothing seems to want to communicate with the Dopod. It seems the USB loader program is no longer running on the Dopod.
Has anybody any idea how I can attach to the device an install a new bootloader, or something.
I had the same issue and I have a solution. But, let me tell you my process that got me where you are.
I tried performing the update using the No_ID (or whatever) method and kept getting errors. I rebooted my PC and changed the Operator ID using the HTC64 Extended ROM Tool.
After this, I was able to use the typical installer. The flash went fine and I hard reset as instructed. From that point on, I had your exact problem.
A dead screen. I was able to redo the hard reset after pulling the battery but I would just end up with the dead (blank) screen again. ONCE, I did get it into boot loader mode where I could actually read the screen. But, of course I reset and again had a dead screen.
My solution was to revert back to a true O2 ROM. Even though I couldn't see the screen (still can't), the ROM update is proceeding as I type this. I'm at 44% of the radio ROM installed.
Hope this gives you hope!
Well, good news. I just finished the ROM update and I'm looking at the O2 boot image.
Is there any indication that the QTek ROM looks for the Carrier info to be QTek or it will fail once installed? Just wondering why I had this problem.
ARG! Reflashing with QTek ROM did the same thing. :evil:
Blank screen and all.
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Thanks and another question
Well thanks for the hope. but I have tried this already with no luck, however after this message I will try again. My biggest problem is that I cant regain communication over the usb.
I would like to know how your system behaved when you plugged in your apparantely dead device. My system just says device un recognised and I cant begin a download with or without active sync.
So I cant get another rom image to download.
regards
Nick
dolebole said:
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Click to expand...
Click to collapse
This was the first thing I did.
The problem is that I cannot get any communication over the USB.
The device is unrecognised on USB and after starting any ROM download it just timesout after "checking information from device" message .
Ever seen a dead USB interface like this ?
The USB PnP mgr sees the hardware but cannot establish the device type !!
Nick
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
ta_mobile said:
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
Click to expand...
Click to collapse
Why don't you guys take it to your respective service centres and get it fixed?
Even if you have to pay something, it will certainly be better than these bricks occupying table space.
Have you tried going back to an original O2 ROM? I went to 1.13.139 WWE and all is fine now.
Just to share my experience with you guys here:
I posted my problem way back during the Radio Upgrade from 1.04 to 1.06. My Dopod 900 got stuck on the splashscreen. I couldn't get my device to pass the splashscreen even after upgrading/downgrading the radio ROM back and forth two times.
Finally, I just forced my device into bootloader mode (Backlight+Reset+Power). Even after doing this, the dopod screen was completely blank (no indication of serial/usb letter on the screen). I downloaded the official O2 exec ROM and plug my device (in bootloader mode) back to the USB port. It said unrecognized port on my PC. Despite that, I reflashed my Dopod back with the NoID tool the complete O2 ROM (Radio, Main ROM & The extended). Once completed, my device regained its consciousness.
I managed to flashed back the 1.06 radio after that. And has since been upgraded 4 times (two i-mate, one Orange and the latest QTek ROM) with no problem whatsoever.
I had the exact same problem as you to guys, i tried to update it, and it wouldn't budge...
It constantly, without fail timed out... I tried everything...
As my hope started to wain, i gave it one last shot...
I took out everything, sim and sd and battery, then connect the battery back and from the bootloader menu, connected it to the pc, with usb cable...
Finally it worked!! Like normal, i was able to load any and all rom and radio updates...
Wouldn't work, from the normal working screen (which was working for a while, i later tested this out, and found out ) and also wouldn't work, from the bootloader (power+backlight+reset) with sim+flash in there....
Hope you guys have some luck.. I htink you should, because i was in the exact same boots as you guys...
It worked for me
My O2 Exec did exactly the same thing, and I spent (on and off) 24 hours trying to get the damn thing to go again - wouldnt charge either....
I too finally took out everything, SIM and sd and battery, then connect the battery back and from the bootloader menu (which I only found about from this site), connected it to the pc, with usb cable...
It worked as well - bloody brilliant. I now have the latest 02Exec Upgrade (Version 1.30.162 AKU2 Release) and all is great.
Cant believe that 2 days after logging email with O2 site, they have not responded...
Would almost kiss you guys.....
Solution for getting stuck in bootloader
http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen
Im trying to flash my rom but i cannot establish a proper conexion between my diamond and the pc.
When i reset i goes to the windows mobile green screen and thats it, since it cant continue it nevers syncs properly with my computer.
I have tried to instal several hard-Spl but it gives me 0% error and 262.
I think is a conncection promblem, any other way so the Diamond could be properly detected?
i had same problem on cruise once,hard reset was the only solution 4me..
thanks.. did end up finally doing hard reset and since I had to install new rom I took the opportunity to install a better one (natxoCC Buffet 2), in spanish. I recomend it. fast and stable.
http://www.htcmania.com/showthread.php?t=14410
after installing a rom update my diamond reboots before windows mobile even appears. I see HTC diamond, seconds pass....vibrate....reboot.
is there anyway to break the cycle....i hope i haven't bricked it.....
please help..... i dont want a $280 crime deterrent device
I had this same problem when I flashed to 1.93, i got pissed and just set my phone aside and let it do its thing then it eventually booted up after like 10 minutes of rebooting. but now my phone is even more messed up because now my phone is not even picking up my t mobile network signal, so ya 1.93 does have some big problems, well at least to me it did. so now im looking to take my phone back to HTC for repairs as I have tried everything I could have myself.
Hard Reset
My friend had the same problem... He let it reboot for a while, ventually i it paused the rebooting and he had the chance to do a har reset. Has been running smoothe ever since.
Remember to do a hard reset everytime you install a new rom...
hello,
i solved this problem by going to bootloader-modus and flash it
with an other rom.
my problem was that i used my own cooked rom by cooking again ...
okokur
Guys I need your help..
3 days ago I upgrade my ROM from VIC ROM to DIB ROM but now my diamond goes weird...
If I soft reset the device it became a hard reset..Or if my diamond more than 7-8 hours standby it suddenly "hang" and if I soft reset then became a hard reset again...I think it's because a new ROM then I change to my old ROM (that before it's normal), but I didn't see any different, my diamond keep hard reset and hang..
Any one have suggestion or solution?What happening to my diamond?
Oh I almost forget same times if it hang and I soft reset the device it appears message like "Your device can't boot because it didn't turn off correctly or you install untrusted application..bla...bla.."
PLEASE HELP ME....
kumis_merah said:
Guys I need your help..
3 days ago I upgrade my ROM from VIC ROM to DIB ROM but now my diamond goes weird...
If I soft reset the device it became a hard reset..Or if my diamond more than 7-8 hours standby it suddenly "hang" and if I soft reset then became a hard reset again...I think it's because a new ROM then I change to my old ROM (that before it's normal), but I didn't see any different, my diamond keep hard reset and hang..
Any one have suggestion or solution?What happening to my diamond?
Oh I almost forget same times if it hang and I soft reset the device it appears message like "Your device can't boot because it didn't turn off correctly or you install untrusted application..bla...bla.."
PLEASE HELP ME....
Click to expand...
Click to collapse
Problem mimics this thread ......http://forum.xda-developers.com/showthread.php?t=490182.....might be caused by a bloated ROM
I had the same problem and for me this way works:
I flashed a new HardSPL (1.93 by Olinex)
Then made a Hard-Reset.
After the new HardSPL i installed the original 2.03 Rom from HTC
and made also a Hard-Reset.
Now my device works without any problems.
So I think, after my last step it is possible to install any cooked Rom,
but at the moment i don't know which one causes the crashes and it seems that a few others here have also problems so i will wait and see what happens in the next time...
(Im sorry for the English but I hope you can understand what I wants to say!)
hey, I'm only 1.40 Olinex unsigned;
when i first boot up I have this:
R 52.2.25.12h
G 1.00.25.05
D 1.93.0.0.0
My phone shuts down by itself, after i see the HTC logo and i hear the shut down sound.
why is that happening, is it software or hardware?
PS: RUU_Diamond_HTC_Europe_1.93.401.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
I am flashing with this ROM, and with some other ROMs it is not even booting up
try this mate
try running mtty then reflash your rom, mtty formats your nand chip and repairs any erroes read THE DEFFINATIVE MTTY THREAD all explained there got to be worth a try hope this helps
trying this now will report on results thank you mate
still having problems, now phone wont boot up at all
i think i can make it boot
(I got USB error after i pressed <- and Vol Down to flash ROM )
is there a problem in my SPL? is my phone bricked?
i can boot into WinMo after i have left the phone for a few hours
but now 5-20 minutes after booting (depending on each time), suddenly i see the HTC logo, and here the shut down beep
any help ?
could it be a bad battery issue?
because when i turn it on i see an exclamation mark next to the battery icon in the bar on top
any suggestions? plzplzplz !!
MTTY Thread
Reflash your phone doing EXACTLY what it says in that thread and you should be good to go.
mzaouar said:
could it be a bad battery issue?
because when i turn it on i see an exclamation mark next to the battery icon in the bar on top
any suggestions? plzplzplz !!
Click to expand...
Click to collapse
Buy another battery, It looks like battery problem.
Good luck
now the battery looks like it's working fine, i've flashed a new radio ROM, but it's getting turned off again :S
should i upgrade to the 1.93 HSPL? because i have a 1.93 ROM
can the problem be from the radio?
Same thing here,
Been flashing the diamond to the bone.
After flashing the (22 jul) verion of the NRG warhawk rom
I have been experiencing some glitches.
As it was my first step from wm 6.1 to 6.5 and I dont want to go back.
The errors ive experienced are not related to rom issues.
Because i got em almost with every rom.
- random restarts
- loss of contacts
- no responding of the device
And ive been reading about the MTTY sollution I go and try that one.
Enonoid, so you didnt find a soltuion to your problem?
and if not, what do you suspect the culprit is?
Been flashing the diamond to the bone.
After flashing the (22 jul) verion of the NRG warhawk rom
I have been experiencing some glitches.
As it was my first step from wm 6.1 to 6.5 and I dont want to go back.
The errors ive experienced are not related to rom issues.
Because i got em almost with every rom.
- random restarts
- loss of contacts
- no responding of the device
And ive been reading about the MTTY sollution I go and try that one.
Reply With Quote
the problem isn't rom related running MTTY formats the chip where the rom resides its like reloading windows on your computer when you know there are bad sectors on your hard drive. it just wont happen follow the THE DEFINATIVE MTTY THREAD and honestly all should be fine it sounds quite tricky at first, but I use mtty everytime i reflash now saves whishing you'd done it once you've reinstalled everything and believe me its so easy if you just follow the guide.