alright so about 5 days ago my inspire's battery died I got home charged it over night and I went to turn it on and I got 7 vibrations and stuck at splash screen and I tried wiping and restoreing and such but nothing worked so i figured my motherboard was fried ( emmc) so I took apart my old inspire that had a cracked screen changed the mother board and now I just get a black screen but you can see it has a back light. also it shows up on my pc as "my htc" in device manager. also during the replacement my volume switch kinda got damaged so i dont think that it would work to get me to hboot but it worked on the cracked screen. if any body could give me any insight on this it would be nice
UPDATE: I just looked in my device manager again it says it is using the adb driver so i loaded up adb and ran adb devices and it came back as my serial and then to the right it said recovery but yet the phone still has a black screen does any body know any commands I could you to possibly flash a new rom or something of that nature.
Do 'adb reboot bootloader' and tell me what happens.
Sent from my Desire HD using xda premium
Related
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
Hi all
I have changed the screen of my HTC Desire (so had to opened it)
I replaced it, re assembly all the phone without doing it fast to avoid to kill some piece of other stuff.
When everything is done, the Desire can be put ON, i got the HTC white screen with the vibration
The phone took 2 minutes to show me a black screen with a phone into a green circle.
I flashed it with the RUU, (fastboot USB works) he rebooted after installation.
Same white screen, and after a few minutes, the HTC quietly brilliant screen appears, but the letters were very very very laggy.
Now, it is stuck on this image and i dont know what to do
I suppose if i had damaged something, he couldnt works no? usb is ok, fastboot, installation of RUU...
I'm scared having killed my Desire (the operation was risky but a really payed a good attention when disassembling and assembling.)
Thx for help
Did u make nandroid- backup before? If, go into recovery and flash this.
Sent from my HTC Desire using XDA App
thx for your help
as i thought, it was material, not software problem
2 pieces were in touch whereas they shouldn't be, i repeared it and the phone has booted well
This thread can be closed, thx!
On Friday night, My phone was in the breast pocket of a blazer that got very damp in an unexpected downpour. The phone continued to work on Friday night as far as I recall (I wasn't using it much, but I'm pretty sure I did use it some). When I woke up on Saturday morning, it appeared to be off and wouldn't turn on. I pulled and replaced the battery and still got nothing. I put it on the charger, but I had to run out, and I ended up being gone all day.
When I came home, the power button still wouldn't turn on the device. I pulled the battery and replaced it, and the Google screen came on, then the CM10 boot animation. When it got to the pin screen, however, the screen wouldn't respond to me entering my pin. Then, after a minute, the screen turned off, and the power button wouldn't turn it back on. I did a battery pull. Again, replacing the battery brought up the google screen, the CM10 boot animation, and the pin screen. But, again, the screen was unresponsive, and the power button did nothing when the screen went off.
I took it apart and left it alone all day Sunday. On Monday morning, I tried again and got the same results. I went and picked up a bag of white rice yesterday and left it in there last night and all of today. Still, I've got the same outcome. Buttons and screen are unresponsive.
So I'm left with a couple of questions:
First, is there anything else that can be done? This seems to me to be water damage. Does anyone have any suggestions for possible solutions?
And second, I keep getting text messages. Is there any way to pull those messages using the Toolkit or adb or anything (I'm pretty inexperienced with adb)?
Any help would be great. I'm stuck in China without a phone right now, which is a pain in the butt. I'd like to revive this, and I don't want to go track down a new phone until I know this one is sunk. Thanks for your help.
install android-sdk
run adb server on the host
connect your device to pc (feed it naked drivers manually found on dev section, if you're on windows and device manager shows unknown device)
type: adb devices
q: do you see your device listed? (should be lots of numbers and letters)
if it doesnt even recognizes that it has been plugged in, then your usb connection went down the drain, nothing else you can do
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
ejchis said:
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
bk201doesntexist said:
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
Click to expand...
Click to collapse
And you would expect this to resolve the screen and buttons being unresponsive? This is interesting. Is it possible to pull my messages beforehand?
Sent from my Nexus 7 using Tapatalk 2
Hi all.
I have a seemingly unique problem with my nexus, one day it got stuck in the boot logo. I gave the phone to a friend to fix, he used the galaxy nexus tool kit and halfway through solving the problem the phone crashed and now wont boot. At all. I am locked out of fastboot nothing at all is displayed on the screen, the tool kit wont detect the handset. There is no response when I push any of the buttons. I tried opening the phone and shorted out the power button. the only response I get from the phone it when I plug it in to windows 8 it get the sound on my pc to know it found hardware, then immediately followed by the disconnecting sound, and a little notification flashes from the system tray, If I am fast enough I can click on it and I get this message:
(I cant post a link as this is a new account) i.imgur.com/fmkE9Ki.png
I found on another thread that someone had a similar problem, they fixed it by getting a new battery, I did this and it still didn't work. i checked with a multimeter and they're both fine anyway. I am about to use my last resort and send it in to a paid service. Is there anything else i can try? or do you think a repair shop would have a better chance?
Thanks in advance for your time.
You're internal memory might be fried, happened to my first GN, was downloading something via a torrent app and all of a sudden the screen went black, had to pull battery and restart, first time it nearly got through the boot sequence but then froze up again, pull battery again to reboot but the second time it just started with major graphic errors and did not leave to Google logo screen.. Had to be replaced, good thing was that there was no way for service center to tell it was rooted ;P
Sent from my Galaxy Nexus using xda premium
Have you tried omap flash?
Beamed from my Grouper
I JUST got my LG G2 from sprint less than 4 hours ago and as soon as i got home i rooted it using ioroot25 that i found somewhere online (if its important i can dig up the link but figure its probably irrelevant) and installed TWRP recovery, made a backup, not a single issue, then all of a sudden half hour later i pick it up and turn it on and the screen is mostly white with yellow lines (that move/respond to touch and whats supposed to be going on on the screen) and it will not show any sort of picture just kinda yellow fuzz lines...it looks just like some phones ive seen with cracked/ faulty LCDs but if i hold the power button and up or down to hard reset it, the LCD starts working again upon boot, and continues to work untill the LCD turns off for the first time after booting and i try to wake the phone again, every time i turn the screen on when its on it goes back to fuzzy lines with no way to make it start working other than restarting the phone with the buttons on the back.
anybody ever seen anything like this before? it cant be a broken or cracked lcd cuz when it first boots it shows a crystal clear screen and everything works fine untill the first time the screen turns off...im guessing i am more than likely going to end up making a trip back out to the sprint store tomorrow for a manufacturer defect replacement? any insight into this strange problem would be greatly appreciated!
Check out this thread
http://forum.xda-developers.com/showthread.php?t=2680948
[KERNEL] Stock KitKat kernels & White Lines issue fix
Sent from my LG-LS980 using Tapatalk
Here's the fix
http://forum.xda-developers.com/showthread.php?t=2727616
Sent from my LG-LS980 using Tapatalk
Faced similar problem with LS980
I am also facing similar problem with LS980.
Only additional mistake i have made is -
I have installed TWRP recovery for D802 instead of LS980(Seller labeled it as D802). After reboot into recovery mode, My lcd showing only lines.
Any suggestion/help ?