A friend of mine has a Desire and got it a little wet the other day. He was really impressed that it continued to work and everything seemed fine for a few days.
He let the battery go flat and then discovered that it is booting into the screen before recovery (as though he was pressing the back key and powering on). When it gets to the screen, neither the up , down or power button will do anything.
Any ideas how to get it to boot?
Cheers
Maybe the water has damaged it. Since your friend can't do anything with the hboot screen then I suggest either getting it to HTC or your carrier or if they have a custom rom, use an RUU (ALL data will be lost).
I suggest getting the phone cleaned somehow... What I did in a case like this BUT DO NOT RECOMMEND TO OTHERS was go under the shower with the case off wash it a little and dry it for 3 days (with the phone turned off of course) and worked like a charm
It was running a stock ROM. It is recognised as an Android 1.0 device when plugged in. I have installed the driver from the SDK so now 'Android ADB Device'.
Is there any way in which to re-write the stock ROM? I have downloaded the UK vodafone ROM however it cannot find the device...
Cheers
Aidan
Related
Hello everybody,
I seem to have a major problem with my XDA Orbit: Not only it shuts down with no apparent reason so that I have to reset it, but it shows sometimes the dreaded "white screen of death" - from now on "WHISOD". The screen all of the sudden slowly goes white and sometimes shows dark vertical bands. After that - if I am lucky - I can reset the device, however a couple of times I already had to hard reset end even reflash it.
I have already checked software and plugin problems and would rather say that it seems to be a hardware problem. Any ideas out there. They would be highly appreciated.
Best regards,
Smack
i had the same problem and as at now my phone is dead becuase i did not flash it with the original rom. look for the rom it came with and flash it to the phone ,like how u first got the phone or u will loos ur phone very soon
I am not at all sure if it has to do with the ROM. I have tried different ROMs to check the error but it appeared with all of them. However the next time I will try again with the latest official ROM.
Thanks for the comment and your help. BTW Did you send your Orbit in for repair?
Regards,
Smack
Hi, do you use the uspl before every new rom install? Try it.
I have the same problem, my htc3300 is almost dead I think. No way I can even turn it on, allways end in the windows screen, and it was because I didn`t use the uspl before last rom install.
Give it a try, and let us know.
See ya.
Thanks. No flashing problem. I have flashed a couple of devices (always unlocking them before ;-) )and have had no problems whatsoever.
The problem I mentioned is not connected to any earlier flashing. The device works a couple of hours perfectly. However suddenly it starts to behave like crazy.
Now to your problem: If you can get into boot loader modus you will most probably be able to unlock your item. Search for uspl and download it. Then get into boot loader mode (press voice recorder button and power button while resetting the device) and you will get a three colored screen. Then connect the USB cable. You will see "usb" in small fonts on the screen of the device. Now you can run uspl. With a little luck the device starts again. However you can flash it again with a fresh ROM the same way (after unlocking it). This may (!) work.
Regards,
Smack
Hello,
I have the same problem, I already hard reset end even reflash my p3300 many times with different ROM.
I even tried running it for some time with and without the micro SD, ending with the same result: the screen of death.
Any ideas , tips, anyone ?
Thanks,
Roundi
Ok, I tried the following: Just take the battery out for six or seven hours and insert it again. The device seems to run smoother. Will keep you posted. Tell me if it works out for you.
Regards,
Smack
Ok, just removed the battery, I will leave till tomorrow morning.
I will keep you updated.
Thanks,
Roundi.
I have same problem here - though mine is the second phone and the fifth motherboard I've had. HTC just don't seem to able to fix it. I'm now trying to get a refund.
Hi, Jem.
Yes that's something I have thought about too. Did you you use the original ROM? However right now the system seems to be more stable. I have had only one blank screen after removing the battery (and one shut down).
Regards,
Smack
I have just put in the battery and switched on the phone after almost 24h.
So far so good.... I will try to use it for a while and will let you know.
Regards,
Roundi
Had the same problem again, when using Mortplayer. I have Mortplayer installed on the SD card. Could it be that the problems arise, when there is heavy usage of the SD Card?
Any ideas are welcome.
Regards,
Smack
Again it went SOD shortly after turning it on. I didn't launch any applications.
I am stuck here.....
Hi eveyone,
I have a HTC desire, originally bought unbranded and unlocked. About two months ago I rooted with unrevoked (after downgrading the HBOOT as I had installed the OTA vanilla Froyo). I have been running OpenDesire and was until recently using v.4.0.34.
Everything has been working fine until yesterday, when it was in my pocket and I got caught in a rainstorm. It got damp, but not super-wet, and was still working fine at the time. Inside the back case and under the battery was dry. Several hours later I updated to 4.0.36. Immediately after update, it was fine and acting normally. In the morning when I woke up and ever since then, the phone has not been vibrating at all. I first noticed it in Swiftkey entering text and thought it must be a setting, but it doesn't vibrate on texts, phonecalls, turning on, turning into vibrate mode, anything.
I thought I might as well reflash from scratch in case something had gone wrong with 4.0.36 so I went to do a wipe, reflash the radio and the rom, and see if this fixed it.
At this point I got back to ClockworkMod recovery and couldn't use the trackpad. It doesn't scroll, it doesn't press, nothing. It also doesn't do anything when booted. Every other bit of my phone works perfectly - charger, headphones, touchscreen, volume and power buttons, the lot.
I am *assuming* these problems are related to the damp rather than anything software-related, but other than the update to 4.0.36 I haven't done anything different or installed any new software. I would also be surprised if it was due to the water, cos it really wasn't that damp.
Any help would be appreciated. I am *this* close to stripping it down and taking it to bits to clean all the contacts of any deposits or anything, but just in case that's a bit OTT, I thought I'd ask you guys on here, because, well, you know everything
Cheers,
Dan
I have this on very rare occasions. Softly hitting the phone on the back helps. If you unsure what I mean. Just drop the phone on your bed once and it'll fix. (Atleast for me it does then)
My friend is running CM 7 on his Tmobile G2.
He was describing that yesterday was acting weird with market downloads.
Here is what he he emailed me on what happened.
the phone was acting normal throughout my day until the evening towards the night, i noticed it failed to finish downloading the update for google earth along with google maps. the phone was fine, and then i pulled it out of my pocket a few times and saw multiple times that it was randomly turned off. i would turn it back on and it would still give me the same issue. when i got home and plugged it in to charge, it would boot and then get to the main home screen telling me that google maps is downloading to update. however the update would be frozen, and a few seconds later the phone would freeze altogether, forcing me to turn it off by pulling out the battery. this happened about 4 times, and now has reached the point that it has become a brick and refuses to turn on or show the charging light
any suggestions on what might be wrong with the phone? Thanks in advance. Im running Cm7 on my phone and never experienced this issue.
same happend to me 3days ago, phone running then freezed... bootloop after batterypull... recovery worked for 2 times but had problems with flashing new rom/backing up -> errors with cache partition...
after 4hours of letting it stay off -> it wont turn on again und wont charge (no LED)
tried it with another dz battery+charger... no change... i wrote htc and they answered within 1hr that i have to send it in without battery...
i guess its a known problem (or why wouldnt they want to have me sending in charger+battery .. if its a power-on problem..)
there are semibrick threads here and in other forums.. but they all don't suffer from the power on problem... so i guess i did the right thing sending it in
edit: never had heat issues, never had random reboots, no overclock, no indication of an update from any app did any harm to my phone, running cm7 for 3 weeks without any problems, no hboot flash, no radio flash ... nothing that would indicate a risk of brick (according to guides & forum threads)... first htc that ever failed for me ;(
Thanks for the reply. I will forward it to my friend. I think he is going to try to exchange it at the store and if it all fails we are going to try HTC.
have any of you tried to boot into recovery? did you have eng-hboot on your devices? go to #g2root
its complete dead as in dead... no LED light, no turn on, no hboot mode (or what its called when you press vol+power key).... i dont have a g2 but a unbranded european dz.. hboot and radio was never touched by me
Similar thing happened to me. My phone kept frozing on me running cm7..was fine for a week though.
So I booted into recovery..wiped cache,factory reset flashed another rom got bunch of erros recovery thing rebooted stuck i n htc logo for like 20min yanked out battery rebooted and it never rebooted back. No hboot,no nothing.
My light indicator still worked though but no hboot or anything.. got a new one now have to send the old one back to tmobile but I'm scared that they're gonna charge me for removing void stickers.
Even though I checked twice that removing void sticker won't avoid warranty according to tmobile customer chat sevice..
So I'm thinking about swiping out the sticker that contains serial number and such on back of our phone with the old one and tell them the new one came without a void sticker lolol
Sorry I got way off topic rofl..
Sent from my HTC Vision using Tapatalk
We went to the store today and exchanged it for another g2. The guy didnt ask any questions and exchanged it happily for a new one.
This very same thing happened to me today. Updated to CM 7.0.3 from 7.0.1 and the phone was freezing when installing items from the market. Pulled the battery and the phone was stuck on the boot animation. Pulled the battery again, and now it will not start at all. No charging light, no nothing. Had more than 50% charge, and now it seems entirely unresponsive. I can't use the power w/ volume button technique either, because the phone does not respond.
Seems like somehow I have bricked the phone, or the phone just coincidentally died just after updating to CM 7.0.3? (seems unlikely)
just a short update on my case:
i got the mobile back from HTC repairs.
they exchanged my "mainboard" (changed IMEI) under warranty.
i don't know what emmc chip i had before cause it died so fast, but my usb deviceIDs changed completely and are now simmilar to the ones in the cm wiki.
my current emmc is now:
$ cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
SEM04G
Click to expand...
Click to collapse
might help ppl.
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
My Verizon GNex is rooted, running BAKED Black Bean. A couple months ago I dropped my phone in water, I saved it with a bag of rice though and it operated fine for the following months. One day the volume up button stopped working. Volume down still works fine. Shortly after my phone ran out of juice one day while I was at work and when I went to power it back on later that day it wouldn't boot into Android. It just stays on the Android splash screen.
Hoping to fix the volume button I bought a new flex ribbon cable and swapped it out, but my volume up button still doesn't work (volume down still works fine w/ the new ribbon). So it's apparently a more serious issue than just the ribbon cable. I've read numerous guides on how to restore through Odin but I can't get any of them to work. No matter what I do or which computer I try it on my phone is never detected by Windows. I've tried re-installing drivers but nothing is working.
Hopefully somebody can help me out. All I want to do is be able to get back into recovery mode, even just one time, to revert it back to stock so I can get it booting!
mosquitoman said:
My Verizon GNex is rooted, running BAKED Black Bean. A couple months ago I dropped my phone in water, I saved it with a bag of rice though and it operated fine for the following months. One day the volume up button stopped working. Volume down still works fine. Shortly after my phone ran out of juice one day while I was at work and when I went to power it back on later that day it wouldn't boot into Android. It just stays on the Android splash screen.
Hoping to fix the volume button I bought a new flex ribbon cable and swapped it out, but my volume up button still doesn't work (volume down still works fine w/ the new ribbon). So it's apparently a more serious issue than just the ribbon cable. I've read numerous guides on how to restore through Odin but I can't get any of them to work. No matter what I do or which computer I try it on my phone is never detected by Windows. I've tried re-installing drivers but nothing is working.
Hopefully somebody can help me out. All I want to do is be able to get back into recovery mode, even just one time, to revert it back to stock so I can get it booting!
Click to expand...
Click to collapse
Did you follow this guide? http://forum.xda-developers.com/showthread.php?t=2065470
How is your phone detected by windows right now? Take a screenshot of Device Manager.