Okay, so I just got my Hermes on Monday. No less than 4 days later, I accidentally brushed it from my couch to a cup of tea I had sitting on the floor (what luck!). So, I waited a few hours, then tried charging it and turning it on. I then read in several places that you're not supposed to try to turn on a device after water damage because you run the risk of shorting it. I had little hope for it at this point, so I decided to take it apart to give it all a good cleaning with electronics cleaner. So, after taking it completely apart, and giving it a good aeresol spray down with electronics cleaner, I let it dry for 2 days. Today, I put it all back together and tried to turn it on, low and behold it actually turns on! Problem is, its on what appears to be bootloader mode (tri-color screen, dislpays IPL and SPL and just says Serial at the bottom). So at this point, I get slightly happy thinking I may just be able to flash it with the official WM6 RUU. So, I run the RUU, and the Hermes starts showing the progress, it gets all the way to 100% and the RUU says its finished. But, upon Hermes restart, it just goes back to bootloader mode. I tried to hard reset after 'successful' flash, but still restarts back to bootloader screen. Is there any other steps anyone recommends trying to try to bring my baby back to life?
Yoy MAY just need to give it longer to dry out in the nooks and crannies. There may be moisture trapped in micro switches causing bootloader mode to be entered. Possibly try a hair dryer or a fan oven on a very low setting - But be careful obviously. You could also try leaving the m/board on a radiator. (Take all the usual anti-static precautions).
Mike
eek
I had a stupid cat knock over a glass of water on to my 8525 one day.
I immediately pulled the battery, took every thing out of it and set it out in the hot sun all day long (was summer then). By the ned of the day I put it back together and all was fine (thank god).
Haven't had a problem with it related to that incident.
So, I'm reading a lot about mitty.exe fixing problems like these (stuck in bootloader mode), but I can't seem to find out exactly what mitty is, or its purpose. I figure it may be worth a try, although it probably won't work. Can anyone point me in the right direction for mitty info? I've searched, can't find much of a description.
Edit: Okay, from a little more reading, I understand what mtty.exe is, and I see that some non-water-damage-related-stuck-bootloader issues are resolved by using the commands "SET 14 0" and "TASK 8". It seems that the former command is basically like a hard-reset, but I'm not sure what the latter command does. I'll update after I try this later today.
Okay, so did the mtty command and reset, still stuck in bootloader. Tried flashing with official htc at&t wm6. The phone however wasn't shipped with windows mobile 6, could it be that I need to flash it with the original windows mobile 5 that it was shipped to me with? Or is this thing toast.
Related
Before I start I know how touchy people are about searching forums and the wiki etc... but I already have!
Ok so, I tried to flash a new ROM to my phone last night, I have done it before without problems however this time I was having trouble getting the phone to connect to my laptop (I run Windows 7). Both USPL and HSPL wouldn't work (in fact active sync wouldn't even recognise it).
So I went to bed, woke up and... My phone didn't work at all
I spent ages trying to get it too work, I tried putting it into bootloader, but nothing happened, I tried getting it to Hard reset, but nothing happened. (By nothing happens i mean the screen doesn't turn on).
The only sign of life i get from it is the little vibration that usually occurs after the 'smart mobility' screen appears. Except this is delayed by about 10 seconds from after pressing the Power button.
The delay makes me think that there is something else wrong with the phone other then the screen...
Please help!!
Oh and I am sorry for the essay... I only just realised how long and rambling it is haaa.
UPDATE: right it just connected to activesync but still nothing on the screen, is there any way of checking for definite that the screen is broke before I fork out for a new one? There is astill the massive delay between turning the phone on and getting the little vibration...
Try removing battery overnight, then re-inserting. Then try to get to bootloader or hard reset
how exactly did you manage to brick it? did you flash the rom in question with uspl, or do u generally have hard spl installed? i dont know but it looks like the bootloader is somehow broken ...
Ok I will try doing that, thank you for helping
And no, I didnt get as far as flashing the ROM because active sync never recognised the phone in Bootlaoder. I usually use USPL.
Did you fix it? and if so how?
I have very similar issues with my HD right now. Screen went black, bought a new LCD and still the same problem. Oddly enough the only way I can get the screen to come on is to take the battery out and set both battery and phone body in my window sill for half an hour or so. It is cold here right now and they are both pretty cool to the touch when I take them out. Put it back together and tada! Screen comes on. I dunno what the deal is also, don't know if its the battery or phone being cold that makes it work again??? I am going to try and figure it out.. Try it on yours it may help
Hi,
A coworker of mine dropped her Diamond 2 in the toilet. True story!
Anyway, since it was brand new she dried it up and if you switch it on now you get to the tricolor screen. I tried attaching it to my pc, and the text at the bottom changed from serial to USB. I now thought I might have a chance to salvage the phone by trying to flash the original rom. owever, even if everything seems to have worked out fine during flashing, the screen (when ready flashing) turned blank only to go back to the tricolor screen again.
Any one have any idea on what to try next? Is it bricked for good?
The screen shows no sign of water damage whatsoever.
Regards -
/Ballista
BallistaSlim said:
Hi,
A coworker of mine dropped her Diamond 2 in the toilet. True story!
Anyway, since it was brand new she dried it up and if you switch it on now you get to the tricolor screen. I tried attaching it to my pc, and the text at the bottom changed from serial to USB. I now thought I might have a chance to salvage the phone by trying to flash the original rom. owever, even if everything seems to have worked out fine during flashing, the screen (when ready flashing) turned blank only to go back to the tricolor screen again.
Any one have any idea on what to try next? Is it bricked for good?
The screen shows no sign of water damage whatsoever.
Regards -
/Ballista
Click to expand...
Click to collapse
The best thing to do in these situations is to immediately pull the battery and put into a bag of rice to absorb all of the moisture before putting power to the unit thus risking a short circuit.
You may still have water shorting out your hardware keys and its putting the phone into bootloader mode.
My wife put her phone on the kitchen counter, well, it got completely wet. In addition to using rice, I put the rice and the phone in one of the vacuum bags and pulled vacuum, left it in for 2 or 3 days and the phone worked and functioned 100%. 6 months later, still up and running.
Thanks for the answers. I think it is as dried up as it can be though. She have dried it with rice etc. Is there any tip on what to do from the tricolour screen?
Hi,
I maybe didn't understand when the screen goes blank, but since the situation looks pretty desperate why not try to install latest HSPL, it's still a flashing procedure and should end up succesfully if you don't have any hardware damage. If HSPL flashing works, you'll be able to flash any ROM you like, official ones included. Since the device is not yours sorry for the silly question: you have WMDC installed on your pc ,don't you?
The screen goes blank after the bar goes up to 100% on the telephone. I have WMDC installed, but I cant get it to connect to the phone, so installing HSPL will be a problem or?
Edit: Doublepost
If you can't connect to WMDC you can't flash anything,I'm afraid...Any chance to flash by putting the ROM image into the SDcard? Problem is that official ROMs come in .exe format while flash procedure via SDcard needs the ROM image to be in .nbh format..I'm sorry, I'm stuck.
You most probably have a hardware problem, probably a button stuck. Try pressing volume up down repeatedly for example 30 times then try to turn on the device. If that doesn't work you will have to disassemble and dry off your device and check for a shortcircuit or some resistivity in the volume down area. Even if you dry your device on the outside, some water still remains on the inside (I know since I'm an electrician).
Sorry for posting in here - my issue is with an opal but it sounds like a very similar issue.
I tried to clean out the stylus holder on my opal with some washing up liquid on a cotton tip bud. Nothing happened at the time, but some washing up liquid must have got into the phone, as the next time I went back to it seemed to be bricked. I didn't know how to deal with washing up liquid so I disassembled the phone and put it into the freezer to see if that would get me anywhere. I didn't think rice would be much use at absorbing washing up liquid. Anyway, a few cycles in the freezer followed by a cold blast with the hair dyer seemed to have the phone able to get to the bootloader, and able to hard reset.
This is where I am now. Hard resets only get as far as displaying:
ONBL 1.27.000
SPL 1.27.000
GSM 03.29.90
with the 'smart mobility' splash below. That's it - after about 5 seconds the phone turns off. I can keep performing hard resets in this loop, and I can also get the phone into the bootloader 'tri-colour' screen where it shows
ONBL 1.27.000
SPL 1.27.000 (all in the red bar)
and then 'F256' in the green bar
the white bar will change from USB to SERIAL as appropriate.
I thought I'd cracked it when I downloaded the stock ROM from htc, and it seemed to run succesfully. However, once it got to 100% it turned itself off again and I was still only able to either unsuccessfully hard reset, or get to the bootloader screen. I've tried installing the stock ROM through an SD card too, and it seems to work again, but same result. I suspect the phone is a brick now, and there must be hardware damage somewhere important. Any ideas appreciated though.
BallistaSlim said:
A coworker of mine dropped her Diamond 2 in the toilet. True story!
Click to expand...
Click to collapse
It might need re-flushing. hahah
I have a developer unlocked Focus that is currently running 7004. It was dropped in water and I assumed it did not work as all it would give on boot is the connect to PC icon.
Earlier today I was thinking "Hey I should get a second battery" Well I remembered that other 'broken' Focus and I plugged it in. Mistakenly I was holding the camera button as it took a picture and brought me to the camera screen. This allowed me to exit and browse through the phone as normal. Everything worked as normal (Aside from there being no SIM) I could even browse the marketplace.
I decided to test the apps to see if they'd work first Facebook (no good couldn't update stuff even though I was on WiFi) and twitter. After writing a tweet the phone locked up and reverted to the connect to PC screen. Now the hardware buttons do not respond (Back, Home, Search, Camera will focus but won't take picture)
Short version:Now whenever I boot up it goes to the connect to PC screen. If I connect the phone to a PC it just keeps rebooting itself. The hardware buttons do not respond if I do the reset command. (Back, Home, Search, Camera will focus but won't take picture)
Question: Is it possible to fix this issue of infinite boot and have a normal phone again?
Phone specs
Unlocked
ATT Focus
No MicroSD
Version is 7004
If the hardware hasn't been affected you can try a reflash with one of these ROMs. If you can still do that. Plus a hard reset.
From what you have described, I can't tell for sure what is wrong (soft, hard or both). Hopefully none.
The fact that the phone worked, suggests that part of the software is working. The hardware seems ok, so if you're lucky enough the phone might work with a reflash.
What I recommend, before you reflash, considering it was dropped in water, is make really sure it's dry. I hope you removed the battery quick enough as that usually damages the phone if left in, afterwards.
I've heard various methods, and I know 2 that work:
- remove the battery and the cover and find a warm/hotter and dry place (not too hot) and put the phone there, over a towel and in between the phone and the towel, kitchen towel. The idea is to heat the phone slightly. DO NOT use a microwave or a blow dryer or fire. A good example is over an electric blanket, at lowest power (+towel, +paper towel).
- dry rice. immerse the phone completely in dry rice (batt/cover removed) and leave for 24h
So when I flash the device it comes up with a connect to PC screen. However the flash does complete the entire process. Zune then starts running but says restoration fails.
EDIT: I don't think this phone is good to work anymore.
Picture of Zune error: http://imageshack.us/photo/my-images/98/erroron.jpg
Mister Locke said:
So when I flash the device it comes up with a connect to PC screen. However the flash does complete the entire process. Zune then starts running but says restoration fails.
EDIT: I don't think this phone is good to work anymore.
Picture of Zune error: http://imageshack.us/photo/my-images/98/erroron.jpg
Click to expand...
Click to collapse
Did you re-flash the firmware or you only tried to restore from Zune?
The flash process doesn't involve Zune...
I reflashed the phone and then it reboots itself. First with the screen with the red arrow. Which is supposed to happen. Then it reboots itself again and Zune boots up, giving me that error. It then returns to the connect to PC screen once again no matter how many times it is rebooted.
EDIT: Would it matter which AT&T ROM I used to flash it with?
Mister Locke said:
I reflashed the phone and then it reboots itself. First with the screen with the red arrow. Which is supposed to happen. Then it reboots itself again and Zune boots up, giving me that error. It then returns to the connect to PC screen once again no matter how many times it is rebooted.
EDIT: Would it matter which AT&T ROM I used to flash it with?
Click to expand...
Click to collapse
Hmmm.
Here's an Omnia 7 guide, but should apply to the Focus as well (evidently, with Focus ROM/binaries from Samsung-i917-Focus-firmware-UCJK2-ATT-USA.exe)
I suppose you followed it. If that's the case then your hw might be affected...
Yeah I followed that exactly. I'm guessing the hardware is affected and can't be used anymore. Guess the one time I used it was a fluke. XD Oh well. So much for having two Samsung Focuses.
Mister Locke said:
Yeah I followed that exactly. I'm guessing the hardware is affected and can't be used anymore. Guess the one time I used it was a fluke. XD Oh well. So much for having two Samsung Focuses.
Click to expand...
Click to collapse
I think you should ask Heathcliff74 (PM him), maybe the problem is that one of the steps just doesn't complete and maybe there's a way to force that, or there might be more you can try.
Hi everyone,
I would really appreciate it if you could give me an advice for my TMOUS HD2 P81120, that won't turn on.
I bought it with some firmware problems, spent plenty of time flashing it and finally managed to install a stock ROM from SDCARD using a fridge (it couldn't install w/o such cooling).
After that, it booted to white splashscreen with pink logo (smth like "Bringing happinness", don't remember the text) and stuck on it. I rebooted, flashed HSPL 2.08 successfully.
After that the device won't turn on at all. When I hold the Power button, all I get a barely sensible short vibration, but the screen stays completely black, no signs of life. I kept it on AC charger overnight — nothing has changed. When I hook it to the charger w/o the battery, and put the battery in, HD2 powers on itself (same short vibration, no other signs of life). Tried removing the sdcard, different combinations of power-ons, still nothing. Tried freezing it again for 5-10 mins — still no luck.
Please let me know what else I can try.
and one more thing — when I plug the USB, the PC doesn't detect any device.
It seems that a JTAG is my last resort, still I'm not sure I can find the hardware for that.
kitjarik said:
and one more thing — when I plug the USB, the PC doesn't detect any device.
It seems that a JTAG is my last resort, still I'm not sure I can find the hardware for that.
Click to expand...
Click to collapse
same sh*t her pall
the problem is that your HD2 are overheating so the only thing thats left in your case is to replace motherboard
BobbyManifesto said:
the problem is that your HD2 are overheating so the only thing thats left in your case is to replace motherboard
Click to expand...
Click to collapse
Good point!
Make sure that none of the three pins on the phone that touch the battery are bent. One of the causes of constant reboot is when one of those pins are not touching the battery. Please let me know if it worked for you...
meb786 said:
Make sure that none of the three pins on the phone that touch the battery are bent. One of the causes of constant reboot is when one of those pins are not touching the battery. Please let me know if it worked for you...
Click to expand...
Click to collapse
That were definitely not the battery pins.
If anyone cares - here's how it ended (or not yet )
I found a JTAG service in my city, they wanted 50$ to restore the device to a working condition. I agreed, they took the phone. After that they've called me and said they have restored the bootloader, but can't make HD2 actually boot (they flashed stock ROM directly through JTAG, but it always got stuck on "Stick Together Screen". Now I understand I have probably flashed the wrong rom/radio — that's what has bricked it. I paid them 7$ for "diagnostics" and got back a phone with a working bootloader.
After that, I used the "fridge" method to flash latest radio for HD2 and some custom Win6.5.3 ROM (10 mins of fridge before each step). Then I cooled it again and put the cold phone on a frozen chicken (still laughing on that). Guess what — it booted into WM6.5, I even managed to make a call, though it rebooted in 3-5 mins. Overheating problems confirmed, at least it's not a complete brick.
What I've done now is found a guy that will try to "reball" the CPU's BGA - sort of "reheat" the chip to get a firm contact of it with the motherboard, and solve the heat problems. He'll call me today and let me know how it went — i'll update this topic.
As a conclusion, I can only say: "Check three times what you're flashing before you actually are flashing". Otherwise, JTAG is a wonderful "resurrection" solution, although a bit pricey (my case is pure luck).
Greetings everyone,
As the title of the thread states, I have in my possession a M1A1 that is stuck on a Bootloop.
First of all, let me explain the situation a bit. This phone was accidentally put inside a washing machine, lasting inside there for what may have been a good 20 minutes until it was noticed there and promptly removed.
Upon removal it was still showing some signs of life, such as the LED lights going off. My first decision was to quickly open the phone and remove the battery in order to avoid further possible damage. I then decided to disassemble the phone while at the same time removing the water and letting the components dry up in a lit location. Once they dried up, I proceeded to wash them with alcohol, fully bathing the motherboard while giving a slight rinse to the other components, and used a soft brush to very gently clean the slight corrosion that formed in some places. I repeated this process up to 4 times, each time letting the components dry before giving it another go. It is worth mentioning that i was not able to remove the electromagnetic shielding due to the lack of tools.
Upon seeing no more corrosion, I decided to reassemble the phone and test if it was still alive. To my surprise, it did actually turn on. However, once it got to loading the OS, the loading bar got frozen and the phone restarted, resulting in a bootloop. I argued that maybe, somehow, the OS may have been corrupted, and I decided to try to flash a new ROM. I don't exactly remember whether I first tried via Fastboot or if I went straight to unlocking the phone in order to use TWRP, but long story short, I ended up unlocking the phone and therefore wiping all the data, however allowing me to freely use TWRP to flash new ROMs.
In retrospective, that may have been an extremely foolish decision, as no matter which ROM I tried, the result was the same as it previously was: The phone shows the Mi logo, it then starts loading the OS, the loading animation freezes up, and then restarts. So not only did I end up wiping all the data, but I am still stuck with the same problem.
This is my main issue. I do not know how to identify what is causing this Bootloop. The phone is at least somewhat working, seeing as how I am able to fully use TWRP. Is there maybe some component that may have been fried that is preventing the booting sequence? I would really appreciate some pointers. Thanks.
Something similar happened to me using the adriane tool , I resolved it by unpluging the phone from the PC and the forcing the phone off and rebooting into fastboot mode, and when I got it to boot the first boot was slow, A couple minutes maybe ?. I don't know if this can be helpful, I wish I could do more bro.
lionr2 said:
Something similar happened to me using the adriane tool , I resolved it by unpluging the phone from the PC and the forcing the phone off and rebooting into fastboot mode, and when I got it to boot the first boot was slow, A couple minutes maybe ?. I don't know if this can be helpful, I wish I could do more bro.
Click to expand...
Click to collapse
Hmmm, I don't think this approach would work for me. I have tried every possible rebooting combination to no result, but I really appreciate the help man.