[Help] Black Screen, Bricked? - Droid Incredible Q&A, Help & Troubleshooting

Yesterday I rooted my HTC Droid Incredible (AMOLED). Following that I installed Cyanogen Mod 7, Build 30. The rom was running perfectly until earlier today. Half way through the day, at a point at which I'm sure I still had battery power, the screen no longer functions. Restarting is responsive, but still leaves a blank screen. The same goes with the method of holding the volume down key and the power button.
How may I restore function to my phone, whether it be unrooting or however else? Whatever the method, how can it be done without a visual onscreen?
Less important but still of interest, what is the likely cause that transformed the phone from one working to bricked so randomly?
Thank you.

Did you drop it or get it wet?
Sent from my Incredible using XDA App

Were you ever able to use ADB before this happened? If so, then can you try it now. If you can at least see something, you could give that a try and try some trouble-shooting from within. I'd guess that if something serious happened to the actual screen or interface to it, that it might show up as a hardware error in the log. (#logcat, dmesg, ).
Have you yanked the sdcard and mounted it on a PC? (if you can, you might be able to save the content, reformat 'fat32' and maybe for starters just try to restart it with the blank reformatted card. If that works, well, you're OK.
Do you think it is booting fully, but just not able to output to the LCD or do you think it is only doing the first stage and dropping into the recovery screen? Was this thing overclocked? If so, have you tried a 'safe boot' yet (which disables anything past a vanilla startup like setcpu type things)? (instructions are around XDA somewhere).
Without seeing.. I suppose you can put a standard image on the phone (as in RMA) if you get the 'timing' down for when to push buttons, (assuming that is still doable).

Related

[Q] Evo Buttons Stopped Working

I've seen a lot of these threads on random android forums, never with much resolution, which is frustrating.
My power button has stopped working entirely. I took it into the Sprint shop, they spent an hour with it, came back out and said they could find no reason it shouldn't be working. It's an obnoxious fix, but I downloaded "No Lock" from the marketplace and set the screen to shut off after 15 seconds. Now I press a volume key to turn on my screen...
Now, when it gets annoying is when I went to install Cyanogenmod 7 tonight. The power button obviously doesn't work. Widgetsoid's reboot button is ignored entirely if I do Shut Down, Reboot, Bootloader, or Recovery. It's A-OK with Hot Reboot. So the only way I've gotten into the bootloader to wipe/install CM7 is to pop out the battery, hold VolDown, and put the battery in. Peachy. But once I'm into the bootloader, now not only does power (which is now my "enter" button) now work, but the volume buttons are unresponsive as well. So no scrolling.
I'd love to call up HTC or Spring and see what I can do about a replacement (which might not even happen, I don't have a warranty), but I can't un-root the device to send it in.
Any insight you guys have would be greatly appreciated...
Is there an SDK or something that would allow me to remote control the phone using my computer via USB? I'm completely at a loss here.
END_OF_FLESH said:
Is there an SDK or something that would allow me to remote control the phone using my computer via USB? I'm completely at a loss here.
Click to expand...
Click to collapse
I believe you are referring to adb?
and you can unroot via adb, just search around, I'm sure you'll find something on it.
btw, does Sprint know you rooted your phone? if they didn't find out, then you still have a warranty
Samzebian said:
I believe you are referring to adb?
and you can unroot via adb, just search around, I'm sure you'll find something on it.
btw, does Sprint know you rooted your phone? if they didn't find out, then you still have a warranty
Click to expand...
Click to collapse
Yeah, I'm just not as familiar with ADB as I'd like to be.
Not so much looking to unroot, as reload HTC Sense so they don't think to look haha. And yeah, when I brought the phone in today it was very obviously modded. They restarted it and the Cyanogenmod 6 flash screen came up. The guy looked a little confused. He was more than willing to help out, but I'm not so sure it would be the same if I sent it in. They definitely wouldn't replace it.
Alright, so I have ADB up and running with no issue. Got it to give me my device's serial #. At this point, how do I hijack the phone's bootloader and force it to wipe and install the ZIP of CM7 that's on the SD card?

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

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.

[Q] inc 2 with dead screen

So i recently got a free upgrade to a inc 2 by turning my og inc in under warranty for a blow speaker (for the third time) and i naturally rooted it and installed a nice miui rom. Now about a month later im out of town for work and the screen has died. The phone is still operational, but the screen is black.
I am wondering if this could possibly a firmware issue? i have tried pulling the battery and booting into recovery but the screen is 100% useless. the touchscreen still seems to work, i can unlock it and answer calls ect...
My hunch is that its a hardware problem, but i'd like to try and flash it back to stock if possible to eliminate the possibility of a rom issue.
Does anyone know a way to flash a rom onto it without the use of the screen?
Can i use the HTC sync tool to set it back to stock like i could with the OG incredible?
Any help is much appreciated, i'm pretty desperate here.
if it was me, I'd flash it back to stock using a ruu file, then do a warranty claim, cause then if it's a firmware/software issue the ruu will fix it. There's a thread somewhere around that has instructions to do that, give me a minute...
Edit -found it! Here ya go- http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/page__st__53
Sent from my Incredible 2 using xda premium
ok, so my new issue is that if i flash the ruu, and the screen still doesn't work, i'll be stuck at the setup wizard right? then i won't even be able to use google voice to make calls from my laptop. i guess ill have to wait till i get home, this would be so much easier if my pos nextel work phone had service out here in wyoming.
Yea, that's a tough one, I definitely wouldn't flash an RUU for the exact reason you bring up.
One option, although it isn't without it's own challenges, would be to try to install a VNC server on your phone, so you could then connect to and use it through a desktop computer. You could probably install it easy enough through the Android Market web site. Here's one: https://play.google.com/store/apps/details?id=org.onaips.vnc
If you download the Android SDK (http://developer.android.com/sdk/index.html), connect your phone to your computer, open a command prompt and run ddms, it'll bring up the Dalvic Debug Monitor. Here, you can go to Device>Screen Capture and it'll bring up a window showing the screen of your phone. There's a refresh button which will refresh the screenshot. It'll be a little hit or miss, but you should be able to reference the screenshot to tap on your blank screen to open the VNC app, hit the start server button, and then see what IP/port it's listening on.
Once you get the VNC server running and connect, you should be able to use the phone fairly easily, although if the screen is dead even during boot (no initial boot screen, no display in h-boot) it would seem like a hardware problem and there's probably not much you can do about it.
ChrisDDD said:
Yea, that's a tough one, I definitely wouldn't flash an RUU for the exact reason you bring up.
One option, although it isn't without it's own challenges, would be to try to install a VNC server on your phone, so you could then connect to and use it through a desktop computer. You could probably install it easy enough through the Android Market web site. Here's one: https://play.google.com/store/apps/details?id=org.onaips.vnc
If you download the Android SDK (http://developer.android.com/sdk/index.html), connect your phone to your computer, open a command prompt and run ddms, it'll bring up the Dalvic Debug Monitor. Here, you can go to Device>Screen Capture and it'll bring up a window showing the screen of your phone. There's a refresh button which will refresh the screenshot. It'll be a little hit or miss, but you should be able to reference the screenshot to tap on your blank screen to open the VNC app, hit the start server button, and then see what IP/port it's listening on.
Once you get the VNC server running and connect, you should be able to use the phone fairly easily, although if the screen is dead even during boot (no initial boot screen, no display in h-boot) it would seem like a hardware problem and there's probably not much you can do about it.
Click to expand...
Click to collapse
Yeah i think i'm hosed, i have no screen at all, i can't get the ruu to run, it comes back saying i have the wrong device. i guess im just gonna send it back and hope they don't notice.
captainlovesac said:
Yeah i think i'm hosed, i have no screen at all, i can't get the ruu to run, it comes back saying i have the wrong device. i guess im just gonna send it back and hope they don't notice.
Click to expand...
Click to collapse
Where is it indicating that it's the wrong device if you have no screen?
Please Delete Post
I ran into a similar problem with black screen over the weekend.
However my phone was not rooted.
This is how it happened.
I was using my phone then I saw the screen flicker once or twice, then it went black.
I pulled out the battery and powered up again.
The phone vibrated, and after a while the four bottom buttons light up.
The volume keys work and I could receive incoming calls, but the screen just stays black.
One thing to note is that my pocket was a little wet before I pulled out the phone to use.
Also that I did use my phone for a good 5-10 mins before it went black.
What I am trying to determine is if it is a software issue or hardware.
Are the bottom button lights separate from LCD screen, so that even if they light up it could still mean LCD is bad?
Any help would be appreciated, thanks!

a very strange hard brick

Hi!
First of all i got AOKP + Franco kernel for 2w without any problem and I didn't change any option since last week.
This morning i rebooted it, it switched off and it didn't start again.
I cannot switch one my nexus again since then. I have always a black screen, also if I try to enter in download mode or in the recovery.
I tried to connect to my computer and smt times my laptop see a omap4400 (i'm not sure about the name) but after few second it disappears.
Tomorrow I'm going to the service center... But I have a big doubt:
What the hell happened this morning?
Thanks
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f634...eeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
biscuitownz said:
Remove the battery for 5 minutes and try again.
If that doesn't work,
Follow this guide:
Click to expand...
Click to collapse
This, if OP can't reach fastboot.
Sent from my i9250
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****... I would be very curious as to an explanation as to WHY on earth this would happen. Very confusing.
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
owlieowl said:
I'm having the exact same problem. I saw my phone at maybe 10% battery in the AM, said screw it and let it die, woke up this morning and plugged the phone in and nothing. No LED light, black screen, completely unresponsive. I've tried every trick in the book, and the only one that seemed to work marginally even was using a different battery, which got my phone to boot to the encryption screen, but then shut off again. It did that twice, and now both batteries are useless.
I used Legija's program to try and bring some life back to my gnex, even though it's not the international version, just in hopes of getting some of my data back (I have already started the replacement process with Verizon since the phone was insured), but I got no luck there either.
It's extremely disappointing and annoying to me that this phone survived all sorts of ROM installations (I was also using AOKP on 4.1 if someone wants to start making connections), reformatting, tweaking, almost every setting on that phone was modified by me.
Not only that but almost any software or hardware problem I did run into I could solve in maybe an hour, but I let my charge run out and the phone just up and bricks itself? Now, that's just bull****...
Not to hijack the thread, but my interest here is not restoring the phone to working condition but just seeing if I can pull my data off of it. I wouldn't even be posting here had I been able to have an SD card with my gnex, which I figured was unnecessary at the time I bought it since I knew the space on their was enough for me already, and the added branding of "Nexus" brand which had me under the impression it was maybe stable enough by itself. Not a mistake I'll make again..
Is it at all possible to get the data off of my phone at this point? At least partially? I believe encryption makes it impossible but I'm rather stubborn. Any help would be greatly appreciated..
Click to expand...
Click to collapse
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
TomBall718 said:
So just to be clear... You've been able to get it to boot all the way up to the encryption screen, right? If so you should be able to get into fastboot (Holding down BOTH volume rockers and the power key.) From there you could relock/unlock the bootloader to do a full factory wipe which might solve your boot issue.
As far as the data loss from the wipe, you could then try this: http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
owlieowl said:
I was able to get it to the encryption screen with my old battery that had a little bit of charge left in it twice, but it shut itself down on me both times. So now both batteries are useless.. I took it to the Verizon store hoping they would maybe try one of their batteries, but they just called customer service and told me they're just going to replace it at this point.
I have a feeling the charging mechanism is somehow damaged, because when I did get it to the encryption screen I had it plugged into a wall outlet and it wasn't charging at all. So, I can't turn the phone on whatsoever anymore.. if I could turn it on I could solve this problem... but it simply refuses to boot. The closest I came to interfacing with it was the OMAP Flash script, which did work, but didn't fix the problem.
So maybe if I could get the phone working enough to use ADB with it I could get my data back, but not even that seems possible..
Click to expand...
Click to collapse
If the phone isn't charging then there's something wrong with the USB port. One way to test that would be to use a battery charger. Also, try a different cable. I've had issues with a few different cables that for whatever reason started to not fit properly in the phone.
If you're USB port has gone bad then you'll need to either A) Always use an external battery charger. B) Get a replacement. C) Fix it yourself (Good guide here: http://www.ifixit.com/Guide/Repairi...+LTE)+Micro+USB+Charge+Port+&+Main+Mic/9641/1 )

Screen not responding for unknown reason.

So I've searched here AND the entire net for a fix for this but I cannot find it anywhere. I'm decently experienced in the area of androids, flashing, and rooting and currently own a rooted Moto G Play running a debloated stock rom with Xposed installed as my main device (besides the point but just so you know my level of experience.)
I was recently given a HTC Desire 526 and was told by the giver that she couldn't turn it on. So obviously my first thought was to try to enter bootloader mode. I charged the device and held the volume up and power keys to enter bootloader, and it was successful, but still no image on the screen, mind you there is zero visible damage on the phone screen or water damage on the inside so I'm guessing it can't be that the screen is broken physically. I confirmed that it was in bootloader by running fastboot and it is listed under devices when I run "fastboot devices." Vibration works and it occasionally outputs sound so I know the phone turns on (at least). I'm completely new to HTC devices and when i try to do almost anything involving flashing with fastboot I get the s-on error. Adb isn't available as I know that developer options, and furthermore, usb debugging has not been enabled on this device at all in the past.
Can I hard reset with just hardware keys (vol up, vol down, and power)? Everything online says yes and then the instructions go on to explain how to reset via the on screen bootloader menu navigation, that of which I can't see nor navigate with a black screen (I know these "solutions" to this problem make no sense considering I asked about a device with a screen that won't turn on, very frustrating haha.) If not, does anyone have any suggestions on what I could do to get the screen to work? Not sure if this matters but it is a verizon phone. Any info is appreciated as I'm coming to my last leg trying to get this going. So annoying feeling it vibrate and hearing sounds because I feel like it is definitely fixable without replacing the screen but I'm not 100% sure. Thanks.
Edit: My only solution is to see if someone who owns this device (currently I know no one with this device) can direct me on what to push, when, to reset without my screen, so I can navigate through that phone or through pictures of it.
This post can be deleted. Still don't know the cause but it turned on and all is well now. Now I'm just searching for a proper root method!

Categories

Resources