Through a comical accident, my FUZE was trhown agaisnt a wall and landed on a computer keyboard, which then Bluescreened. Why ..I don't know. But the phone came apart. When I put it back together, it started with a error message....
It boots into the Tri colored screen and says ROM loading error, please try again.
I originally had OlipPro spl on the device. After reading for about an hour, I tried to reinstall the hard spl. that didn't work. I found a stock spl from the forum here and tried raphimg.nbh. That boots but goes into a Loading... screen with no other action.
I can't imagine what caused this...I was in the dentist office when the accident occured. I would expect this to occur if I was flashing or something.....
Any one have any thoughts...or is this bricked
alodar1 said:
Through a comical accident, my FUZE was trhown agaisnt a wall and landed on a computer keyboard, which then Bluescreened. Why ..I don't know. But the phone came apart. When I put it back together, it started with a error message....
It boots into the Tri colored screen and says ROM loading error, please try again.
I originally had OlipPro spl on the device. After reading for about an hour, I tried to reinstall the hard spl. that didn't work. I found a stock spl from the forum here and tried raphimg.nbh. That boots but goes into a Loading... screen with no other action.
I can't imagine what caused this...I was in the dentist office when the accident occured. I would expect this to occur if I was flashing or something.....
Any one have any thoughts...or is this bricked
Click to expand...
Click to collapse
A brick it is not. After reading the notes in the Disaster Recovery thread, I found a stock ROM in the WIKI and tried to flash it. Because I could get a USB connection, the ROM loaded. And, after a couple of hard resets, I now have my FUZE functional again. Thanks for the WIKI and all the experts here that contribute.
alodar1 said:
I can't imagine what caused this...
Click to expand...
Click to collapse
Something to do with the wall?
I expected this to be something like "What does error 206 meanzorz111!!1?"
Quite refreshed to see that that was not the case. I am glad you fixed your error. I have had issues like that with my kaiser before, and since I got windows 7, the comp recognizes the device even from bootloader. Congrats on solving your issue, best of luck in the future, and dentists are bad
I've never had a cavity, ever. Brush once a day and haven't seen a dentist in 3 or so years $$
Related
Obviously I'm a n00b I just got my 8525 yesterday, right away I upgraded to WM6 went all day today with it working fine, I installed a PockMSN and Windows Live anyways to keep it short I FIGURED I WOULD just RE-INSTALL Windows Mobile 6 to get a fresh phone (didnt know hard reset did the same) Actually it was the 3rd time I flashed the OS and RE-UPGRADED to WM6 to get a fresh phone!!!!
~heres the trouble~
In the middle of the reinstalling WM6 I accidentally reset my computer, didnt realize it right away and, got ERROR 260 I believe, anyways I followed the directions, took out the battery and reset, plugged the USB back and RAN the Offical WM6 Rom of HTC site again and it keeps getting stuck EVERYTIME at 11%, I have tried it like 10 times and it gets stuck at 11%, and I get the same ERROR. Says Communication error 260. I have tried everything I know reset the computer, changed USB cords, and Nothing, everytime it gets stuck at 11%!!!!!!
Any Ideas about how to get my 2 day old Hermes back??
(I know i did a n00bish thing and I am sorry)
same place everytime!!
I tried to reinstall Active Sync, changed USB cables, switched USB ports, nothing!! I keep getting ERROR 262 (thought it was 260 at 1st) and wont get past 11% says no connection. I do notice everytime i try this process, Active Sync isnt connected, but the Hermes is connected to the computer! Cause if it cant read the hermes it wouldnt be able to even start the update process. But 11% everytime its stops
nicknowsky said:
I tried to reinstall Active Sync, changed USB cables, switched USB ports, nothing!! I keep getting ERROR 262 (thought it was 260 at 1st) and wont get past 11% says no connection. I do notice everytime i try this process, Active Sync isnt connected, but the Hermes is connected to the computer! Cause if it cant read the hermes it wouldnt be able to even start the update process. But 11% everytime its stops
Click to expand...
Click to collapse
Perhaps you could try to flash using the sdcard method. So you would not be connected to a pc anymore. Who knows, it could solve your problem. I know one case where installing an official rom cured also a similar problem.
Quick summary of the sdcard method:
Use an empty sdcard formatted in FAT32
Copy the RUU_Signed.nbh file containing the OS to the card and rename it: hermimg.nbh
Enter bootloader mode (OK + POWER + Softreset). Normally, after the 3colors screen, you will get "Loading" followed by a description of what is on the card.
When ready, press power and... wait...
Good luck (The phone is NOT connected to the pc)
sounds good but I dont have a MicroSD card reader to do that. And I am using an Offical HTC WM6 ROM, thats all I ever used was the offical WM6 Rom from the AT&T site. Like I said, I was able to install WM6 already, but me being a complete idiot was Flashing the upgrade ROM to get the Hermes back to fresh phone factory settings. But I accidentally reset the computer in the middle of Flshing and since then I have never been able to get it to install again, everytime I turn on the phone I am stuck at the Tri-Color Screen, I am able to restart the upgrade process, but it stops at 11% says ERROR 262 and no connectivity!!
please anybody knows anything, this is the only thing I got, my mom got it for me! We cant afford to get a new one, or even fix it, it was a special present!
nicknowsky said:
please anybody knows anything, this is the only thing I got, my mom got it for me! We cant afford to get a new one, or even fix it, it was a special present!
Click to expand...
Click to collapse
Ok. I am a bit annoyed if you cannot try the sdflash method (BTW you can ask somebody having a PC to prepare the card for you.)
There are different things you can flash on your hermes. Radio, OS, Splash screens, Extended Rom,.... The most tricky thing is the radio rom as a failure there has a higher probability to brick your pda.
This is why i believe it is very dangerous to flash right away without some readings and understanding about what you do. i hope you had some experience here.
Did you first install hardspl (olipro 2.10 )? This is not mandatory but is a very good protection against bricking. (here the excellent guide of mrvanx: http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=30&Itemid=27 )
Did you flash also a radio rom? (Was it included in the "package" you wanted to flash?) If yes, i am a bit anxious that a stop at 11% is a problem... BUT, if you flashed a radio rom, it goes very, very, very... slowly. And gives the feeling that it freezes. For the "radio" part it is normal . I hope you did not stop the process too soon.
Once again, try the sdcard method. Or try to flash an official rom (most of the time containing a radio part...) and be patient. Can take till 25 minutes.
If this does not work, do not panic yet. Others had also problems before you: go there and start reading : http://forum.xda-developers.com/showthread.php?t=286755 and here http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
There is a hope to solve your problem. Good luck
Try to flash a radio ROM, turn the device on and if it stays at the bootloader screen (the tri colour screen) make a note of the version displayed. Hook up the device with USB cable, dont worry about activesync.
Download and unzip a radio ROM upgrade (try this one), run the exe, select your bootloader version on the screen....follow the screens through and see if it works.....radio roms take ages to flash so DO NOT disconnect your device.....if it doesnt work you most likely have a corrupted radio bootloader.............which is likely since the radio flash takes the longest ammount of time the reset probably occurred halfway through this.................unlucky
Give it a try though.
The lesson to learn here is to READ THRICE and flash once.....never ever disconnect your device out of impatience (which i suspect has happened many times on a radio flash) and be carefull these devices are expensive
mrvanx said:
The lesson to learn here is to READ THRICE and flash once.....never ever disconnect your device out of impatience (which i suspect has happened many times on a radio flash) and be carefull these devices are expensive
Click to expand...
Click to collapse
I could not say better
I know, the MicroSD method is nice, but when I got the phone the guy gave me a MicroSD card, but not the regular SD card to read it on computers ( i do have a card reader) Guys a super appreciate the replies> I am gonna try everything rite now, but real quick is my Hermes FUCT??? or is this error fixable??? It is just losing communication everytime at the exact same place, it just seems like something is fixable, but my sorry luck i cant get over the hump!! I will let ya'll know ASAP
okay, here is the thing, Every Hermes ROM update utility I have downloaded wont work, i start it and the VERIFY INFO ON HERMS windows appears about 2 minutes late I get ERROR 260 and it exits! Now when I use the OFFICAL WM6 upgrade ROM from the ATT/HTC site it seems to read the HERMES and wanna start the upgrade process, but thats where it ends at 11% No other RUU I have used or tried has even gotten that far, I just get ERROR 260 before it starts and I have to exit.
What it looks like is I cant communicate with my HERMES at ALL!! Active Sync wont see, only when I reset my computer and reset the HERMES and I plug it in a different USB port, it says Installing New Hardware and HTC USB something and then Hardware has installed and is now ready to use. But Active Sync wont recogniZe it
I'm sorry to tell you that but i think you ****ed up your phone and it is as useless as my ****ing jasjam.
please give us some detailed info s about your hermes like IPL SPL GSM STATUS....
When I am in Tri Color Mode I see.......
HERM100
IPL-1.04
HERM100
SPL-2.03
and SERIAL at bottom, then USB when I plug it in to my computer
I had upgraded to WM6 before on it, but me being a impulsive FOOL, i flashed it again to get me back to Factory Setting (didnt know HARD RESET did the same) and I accidentally RESET my computer in the middle of ROM Upgrading and ever since I cant get past 11% when I try to do it again (using the OFFICAL WM6 ROM from HTC)
and I cant get any communication with mtty although I dont know much about that app, I get a CANT load screen appear
is your phone KITL enabled.
hold the COMM manager button + POWER button + OK button (the one on the left side under the jog wheel) and reset with stylus.
if you see KITL dialogue then it is KITL enabled (MY bricked jasjam is KITL disabled)
if it is KITL enabled then read : http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES and your phone will be just fine.
if it is not then your phone is ****ed up just like mine
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
nicknowsky said:
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
Click to expand...
Click to collapse
Hey dude!
Would you kindly provide me the sulotion.
I would appreciate it.
nicknowsky said:
HA HA, me and my phone guy (well the guy who I bought my Hermes from) HAVE FOUND A FIX to get the phone outta Bootloader Mode and back into OS!! in my case WM6!! I have to do it 1 more time to fully confirm the method!!!!!!!! My friend is calling "SHOCKING THE PHONE" but not really shocking anything!! I am reluctant to share the method, but this site needs more people to actually HELP out others
Click to expand...
Click to collapse
Mmm... do i understand correctly your post? Are you hesitating to help others because your method is risky, or because you express some exasperation about people on this site? In this case, do not forget that all people here are exchanging ideas, questions etc on a totally free base without any obligation. In the limits of there knowledge. Encountering a problem after flashing a device is the only responsability of the user. We just try to help. But i prefer to believe that you found a method, still risky, that you need still to test
That said, it seems that there are an increasing number of hermes encountering a problem with the radio part. It seems that stopping a flash at 11% is a symptom of that. See some consolidation of those problems here: http://forum.xda-developers.com/showthread.php?t=349461
I hope you will find a solution for your problem and moreover i hope that none of you bought a hermes second hand with an already radio part problem. If so try always to get your money back...
I AM trying to confirm my method BEFORE i share it, because it might work on mine, and I dont wanna screw anyones hermes up more
nicknowsky said:
I AM trying to confirm my method BEFORE i share it, because it might work on mine, and I dont wanna screw anyones hermes up more
Click to expand...
Click to collapse
Why don't you answer my PMs????
Please tell me your sulotion and let me try that if you have any
I posted this in the Titan forum by mistake. Sorry for the duplication
I need some help...I'm freaking out...
I cooked a ROM with dcd's version 1.6.9 for BELL a few days ago and it was wonderful and worked great.
Today, I tried to upgrade to version 1.6.10 and I f___ed something up.
It starts the htc boot up screen as usual, then the Bell screen comes up as usual, then a Sprint screen comes up briefly and then the Windows Mobile screen comes on and HANGS........
I have tried cold reboots, and nothing. I cant connect to it with USB.
I can kick myself for making an error because I was rushing......
Can anyone please help............................
Edit/Delete Message
koilmaker said:
I posted this in the Titan forum by mistake. Sorry for the duplication
I need some help...I'm freaking out...
I cooked a ROM with dcd's version 1.6.9 for BELL a few days ago and it was wonderful and worked great.
Today, I tried to upgrade to version 1.6.10 and I f___ed something up.
It starts the htc boot up screen as usual, then the Bell screen comes up as usual, then a Sprint screen comes up briefly and then the Windows Mobile screen comes on and HANGS........
I have tried cold reboots, and nothing. I cant connect to it with USB.
I can kick myself for making an error because I was rushing......
Can anyone please help............................
Edit/Delete Message
Click to expand...
Click to collapse
Try the hard reset.
If that doesn't work then try the bootloader mode and reflash it.
Hard reset
Hard reset did not help, it hangs on windows mobile screen.
Can u give me a bit more detail on how to get into the bootloader mode?
I figured it out. You have to but it into bootloader mode by pressing the POWER and CAMERA buttons at the same time and then reboot.
Then load ROM as usual'
Thankyou
You are the fing master. OMG mine was in the EXACT situation and i was freaking out. its currently reloading the ROM back on. Thank you soooooo much.
it probably happenned because modules overlapped, run g'reloc before building to avoid this.
Hello,
Ive been tring to access the wiki page for the past few hours. and Im unable to to get to it, just gives me a tcp time out.
But Im kinda stuck, I loaded the ROM
HTC_Hermes_S64_WM_6.1_HTC_WWE_v2_30.3.2008
Worked great for about 12 hours. and now its locked on the Windows Logo Screen. Ive tried Soft re-set via the button on the bottom of the phone and ive also tried removing the battery. ive read in some threads there is a button combination that can get me to a bootloader screen so i can load another rom? is this true?
And it hangs each time on the windows logo screen. Can someone point me in the correct direction. Ive searched on and off the forums. and im not finding a solution really other than goto the wiki pages but i cant seem to access those.
Any help at all would be appreciated.
** I got it to boot. I found a thread that suggested Pressing Both Soft Keys at the same time and pressing the reset. Once there Press R on the Keyboard to Confirm. and it seems to be working fine now. I Just need to Load a Stable ROM on there.
That would be called a "HARD RESET". It puts the hermes back to factory standard.... Please note though that it reloads the last os you installed, HTC_Hermes_S64_WM_6.1_HTC_WWE_v2_30.3.2008.
If t keeps causing problems, my advice would be to go back to a wm6 rom until you know about the quirks of this little device and the issues caused by flashing wm6.1(not known to be totally stable)... Cheers...
ultramag69 said:
If t keeps causing problems, my advice would be to go back to a wm6 rom until you know about the quirks of this little device and the issues caused by flashing wm6.1(not known to be totally stable)... Cheers...
Click to expand...
Click to collapse
Definitely.
On the other hand, if you are inclined to help with debugging, and understand what mtty is, and the phone is still causing troubles, you might try reading the rest of this thread, trying the proposed "task 28" solution, then reporting back in there.
Hi,
Sorry to stat a thread on this but can't find anything similar.
I've flashed a lot of ROM's prior. Thought I was fairly comfortable with it.
Currently, I have EnergyROM 6.5 and wanted to try another.
I can establish the connection with phone/computer (1st beep), then the second beep happens (activesync). Then I run the AthenaWrapper and it starts. It restarts the phone. I hear the first beep but never the second. The progress bar stays at 0% and eventually there is a communication error.
This happens with NATF's 6.5 ROM as well as the stock ATT rom.
Any suggestions on fixing this problem?
PS - the 'contacts' button at the bottom of the home screen... are those remapable? I have a mandatory program (Good Messaging) which has its own contacts program. Once I've installed it, the contacts button goes to it instead of the built-in contacts. That's not what I want.
Chris
txemsdoc said:
Hi,
Sorry to stat a thread on this but can't find anything similar.
I've flashed a lot of ROM's prior. Thought I was fairly comfortable with it.
Currently, I have EnergyROM 6.5 and wanted to try another.
I can establish the connection with phone/computer (1st beep), then the second beep happens (activesync). Then I run the AthenaWrapper and it starts. It restarts the phone. I hear the first beep but never the second. The progress bar stays at 0% and eventually there is a communication error.
This happens with NATF's 6.5 ROM as well as the stock ATT rom.
Any suggestions on fixing this problem?
PS - the 'contacts' button at the bottom of the home screen... are those remapable? I have a mandatory program (Good Messaging) which has its own contacts program. Once I've installed it, the contacts button goes to it instead of the built-in contacts. That's not what I want.
Chris
Click to expand...
Click to collapse
I had no idea what "Athenawrapper" was until I Googled Athena. The good news is I've solved your problem. The bad news is that you have a PEBCAK
error.
"Athena" is an entirely different piece of hardware from a Raphael , so it's RUU WILL NOT WORK with a Raphael. Frankly, I think you're lucky you didn't succeed in bricking the phone completely. You need to use the RaphaelWrapper to flash a Raphael.
On the off chance that you actually have an Athena, and are trying to flash it with a Raphael ROM, then you're still begging to have your hardware bricked. Most ROMs are not compatible outside of the hardware for which they are written.
You need to:
Figure out what hardware you have.
Go to that bulletin board.
Read the sticky threads there to learn how to flash properly.
Get to work.
Hi,
Well your explanation makes sense... however, the stock ATT ROM I downloaded from the raphael ROM development section and have successfully flashed a prior Fuze with before (I had to return it for warranty). It is the same file that worked then, that is not now.
But it is not working now AFTER I tried the NATF ROM which I'm pretty darn sure I directly downloaded from a link in the Raphael section. Perhaps it was a misguided link or something, and then it damaged the phone such that previously working ROM's now won't flash?
Chris
addendum...I know for sure it was the NATF ROM from Raphael section...
it is here http://forum.xda-developers.com/showthread.php?t=539513
If you did a HardSPL to load NATF's ROM, then you cannot flash back to the OEM ROM without first removing HardSPL.
So (and this is the second time in as many days ), here's my recommendation:
Myrddin Wyllt said:
Here's my recommended procedure:
Back up your PIM data, if needed.
Remove HardSPL.
Run your service provider's ROM installation.
Install HardSPL.
Download the NATF ROM (YES...DO IT AGAIN)
Flash the ROM.
Hard reset when you get to the screen alignment.
Yes, I know I'm yelling, but that's because you don't appear to be paying attention.
It would also be helpful if you'd put your device info in your user signature.
Click to expand...
Click to collapse
Re-downloading the NATF ROM ensures that you don't have a corrupted copy.
Myrddin,
Interesting name, how do you pronounce that?
1) I learned from you today about the HardSPL having to be removed. That I did not know, so thank you.
2) Back on the computer I flash with, I confirmed the wrapper files... first line does say Raphael Wrapper, under that it says Athenawrapper, then under that it says LSD creations.
3) I'll assume since you quoted your previous advice, the yelling and not paying attention comments were not directed at me
4) I'll do what you instruct master!
That's why we like the wise sages of the forum!
chris
It's Welsh, and it's pronounced Merlin, most of the time (Merthin is more accurate, though).
No, the yelling was not exactly directed at you, just at newbies everywhere. Take no offense, I merely wanted to place a great deal of emphasis on certain aspects of the process. It helps us help you.
M
Hi,
Well, somehow I managed to get back to the stock ATT Rom. I'm not sure how to remove HardSPL specifically as searching that topic doesn't bring up any specific threads (at least in the Raphael forum).
I thought since I had got the ATT rom to work, I coul ddo a 6.5 ROM, but I'm running into the same communication error I had before.
Very specifically, everything starts up fine. It causes my phone to restart.
The USB connection noise happens, but then I never get the activesync alert noise, so the download indicator stays at 0% and I get a communication error.
If I just plug my phone into the computer, it starts up activesync just fine.
Any suggestions? And if it is HardSPL, where's the instructions to remove that?
Thanks again,
Chris
Well shoot,
It must be my lucky day.. I did find some instructions for hardspl, did that.. and I think things are about to be working...
Nevermind on the last post for now!
chris
Hey everybody,
My phone is stuck in an infinite restart loop when i tried to revert back to the original rom without replacing the hardspl. Is there anything that can be done for that?
glz88 said:
Hey everybody,
My phone is stuck in an infinite restart loop when i tried to revert back to the original rom without replacing the hardspl. Is there anything that can be done for that?
Click to expand...
Click to collapse
Most often this is the result of a bad flash or a corrupt ROM. Try putting the phone in Bootloader mode (see the wiki for instruction), and download the ROM again (delete your old copy to avoid confusion). Try the flash once more, and don't forget to do a hard reset when you get to the screen calibration the first time.
Hi guys,
I successfully flashed Android to my HD2 a few months back. I used what I believe is Cotulla's rom(?). However the other day my phone sorta died and whenever I plugged it into the charger it would vibrate go through the boot screen and reset at the "1234 go go go" stage. I read some reading on the forum and flashed it back to "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship" from the HTC website, using the SD card. Windows mobile restored the phone and I started using it again.
I tried to put android back on it and I think I unsuccessfully tried to update the radio after which the phone sorta died again. So I thought ok, no problem, lets get back to windows again. So I installed the HTC rom again through the SD card, which the screen told me was successful. But now I can't get the phone to boot or go into bootloader or anything. When I plug the charger in, I get a vibrate and HTC bootscreen, with the red writing at the bottom left and then dead to only do this again and again. If i pull out the charger, the phone just dies. Battery charge was about 50% when it died.
Any ideas or help on how to resurrect my beloved HD2 would be greatly appreciated!
*quick update*
I stuck the phone in the fridge for a while and managed to get it into the bootloader just once and flashed the official winmo rom again, which was successful but still dead phone!
What made you decide to stick the phone in the fridge??
What is your SPL version??
mentalityx said:
What made you decide to stick the phone in the fridge??
Click to expand...
Click to collapse
Probably the dozens of threads that talk about successfully flashing only when the phone has been cooled.
@op it doesn't look good. Usually the fridge trick working implies hardware overheating issues.
Just confirm please, its not a tmous right?
Samsamuel is right, i just read about it and thought hey, why not! plus it got a priceless look from the mrs! lol
It's definitely not TMOUS, its UK Virgin and the SPL was 3.03.0000 if I recall correctly.
When I cool it, I can get it into bootloader, but only once.
well, i still suspect its hardware and unfixable, but there have been cases where for whatever reason a rom suddenly seems to fix it. Try all the versions of the correct stock Rom.
Try the 1.43 the 1,66 and again the 3.14, wwe ones, chilling the phone well before each flash, a good 20 mins.