two days a go I tried to upgrade present WM5 to WM6! few moments after it appeared recovery error. I followed an instruction, but the device was crashed! next time when I tried to start device, on the screen appears HTC and then stops. So many times I attempt to repeat process of upgrading, but nothing. What have I to do! Please help me?
Related
two days a go I tried to upgrade present WM5 to WM6! few moments after it appeared recovery error. I followed an instruction, but the device was crashed! next time when I tried to start device, on the screen appears HTC and then stops. So many times I attempt to repeat process of upgrading, but nothing. What have I to do! Please help me?
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
I was attempting to change to ookba's 3VO ROM but the operation failed and the ROM did not install. I did get the recovery instructions screen and followed them but the phone did not reset to the previous ROM (NRGZ28's EnergyROM 52409). The phone hangs on the Windows Mobile screen. I have done the following -
1) Followed ookba's recovery instructions and gotten the tri-band screen. However whenever I try to flash back to the T-Mobile ROM (any version) I get Error 260.
2) Followed stylez hard reset instructions and gotten the reset screen but the phone hangs on the Windows Mobile boot screen. A hard reset does not occur.
3) Followed NRGZ28's "In Case Things Go Wrong" instructions and gotten the tri-band screen, however when I try to flash the EnergyROM (or any other non T-Mobile ROM) I get corrupted image errors.
4) I have used jockeyw2001's bootloader but get Error 260
Also, the power button does not turn the phone off. I have to remove the battery to get it to shut down. I think I have tried all the recovery steps I know if. If anyone has a suggestion or solution I would be most appreciative. Thanks.
The Rotagilla said:
I was attempting to change to ookba's 3VO ROM but the operation failed and the ROM did not install. I did get the recovery instructions screen and followed them but the phone did not reset to the previous ROM (NRGZ28's EnergyROM 52409). The phone hangs on the Windows Mobile screen. I have done the following -
1) Followed ookba's recovery instructions and gotten the tri-band screen. However whenever I try to flash back to the T-Mobile ROM (any version) I get Error 260.
2) Followed stylez hard reset instructions and gotten the reset screen but the phone hangs on the Windows Mobile boot screen. A hard reset does not occur.
3) Followed NRGZ28's "In Case Things Go Wrong" instructions and gotten the tri-band screen, however when I try to flash the EnergyROM (or any other non T-Mobile ROM) I get corrupted image errors.
4) I have used jockeyw2001's bootloader but get Error 260
Also, the power button does not turn the phone off. I have to remove the battery to get it to shut down. I think I have tried all the recovery steps I know if. If anyone has a suggestion or solution I would be most appreciative. Thanks.
Click to expand...
Click to collapse
Maybe its safe to assume you have a hardware issue? Since the initial flash and following consecutive flashes failed, maybe its a bad USB cable? I would try reflashing the shipped T-Mobile ROM from a different PC altogether using a different USB cable. Since your phone gets to the Bootloader (multicolor) screen means it's not bricked. Try different PC and cable hardware...
Will do. I did try another hard reset and the boot screen has sat for over 20 minutes without getting past it.
Or try flashin stock ROM via SD
you must flash to official rom to make any progress at this point. at least thats what i had to do when my computer auto-restarted in the middle of one of my flashes.
Fixed, thanks for the help.
bricked excalibur
how did you fix it cause i'm having the very same problem
Switched from a PC running Windows 7 to one running XP.
muga said:
how did you fix it cause i'm having the very same problem
Click to expand...
Click to collapse
Welcome to the forum
Also reading here would help http://forum.xda-developers.com/showthread.php?t=415225
Well that didn't work for me its stuck it the multi colour screen and pc not flashing it. When it does recognise and start to flash i see a count down screen like the one on pc but only stops at 3percent
muga said:
Well that didn't work for me its stuck it the multi colour screen and pc not flashing it. When it does recognise and start to flash i see a count down screen like the one on pc but only stops at 3percent
Click to expand...
Click to collapse
Muga, It's also happening to me. I had previous flashes with different roms Kavana's, rose, energy (6.1 release) and everything went well with no problems at all. But a few days ago, I tried to flash my excalibur with the latest release by NRGZ28 (energy rom 6.5) and what I think what happened was that I didn't run the unlock file aplications (since I didn't have to do it in the other flashes, because I already had unlock the phone with the first upgrade) that's the only explanation I can get. At the end, I came up with the frozen screen and I've tried the bootloader steps, original rom installation, hard reset with no succes at all. What I get is the same error you have.
Every time I try to update the hardspl on my phone it works up until its about to install. The progress goes 0 percent on my comp and stays there then the loading icon comes up on my diamond but then it just freezes and disconnects from my computer then gives me error 260. I'm on xp and I have followed all the instructions and its pissing me off.
Error 260
I've had this same problem too.
Plucked up the courage to install unsigned hard SPL Olinex 1.93, so I could just install the 2.03.405.3 official HTC ROM (Orange haven't bothered to release it...).
And then this error 260...
At first I thought I'd bricked my Diamond, but luckily a soft reset brought it back to life.
I've trawled this site, and it doesn't seem like anyone has any solutions to this issue.
So, at the moment, my upgrade process has stalled.
Any advice, gratefully received!
Dear xda-dev community!
Today I tried to flash a wm6.1 ROM on my Uni. In the first few percents of the flashing process everything went fine, however, at 9% it reported some error, and stopped flashing. Now I can't boot back to wm, but I can enter bootloader, though every time upgrading fails at around 9%. Have I bricked my uni? thanks in advice, andor
andor44 said:
Dear xda-dev community!
Today I tried to flash a wm6.1 ROM on my Uni. In the first few percents of the flashing process everything went fine, however, at 9% it reported some error, and stopped flashing. Now I can't boot back to wm, but I can enter bootloader, though every time upgrading fails at around 9%. Have I bricked my uni? thanks in advice, andor
Click to expand...
Click to collapse
Please forgive me for being inpatient, the DOC Format method solved the problem. Please delete/merge this topic to a ''general help'' topic.
Hi, i succesfully, after lots of tries and errors, completed this guide https://forum.xda-developers.com/ze...ed-phone-updating-to-mm-tips-t3452785/page111 after finishing flashing it with AFT, nothing changed, and im still on the bootloop.
I haven't found anything helpful after searching so im hoping this thread would give me something.
Issue: Phone starts normally and freezes on the loading screen. And i get this weird flashing green artifacts before it finally freezes.
This was the worst freeze i saw and took a pic: https://imgur.com/G5woXT0.
How it happened? some years ago it simply died while i was texting, and looped into this nightmare.
Bootloop seems to be working fine, but "adb devices" doesnt recognize the device when im on bootloader. AFT does.
I can get to the recovery, but when i try to ADB sideload, i get "E: footer is wrong" "E: signature verification" and i still haven't found and explanation to that.
This if my first time posting a thread so i hope i'm not breaking any rule, thanks in advance .