My Slide went to an endless blackscreen while booting, however, the computer pics it up completely. Is my Slide bricked?
Nope, if your able to get into HBOOT or Recovery, then no, your flex-ribbon might have gone out if your cant see anything though, like, in you cant see your HBOOT or recovery
Everything works except the lights, but I don't know how to exactly check the flex cable.
idk then, if the screen works, than our not bricked and i dont think its the flex ribbon
Out of nowhere, I pressed the power button and it booted up normally, but then, the next boot was black.
Now, it boots into recovery no matter which rom I flash.
Luckily, I got it working by flashing Esprimg.zip. Mod, close please.
Related
SOLVED
So, I did a silly thing
I rooted my new Incredible using Unrevoked 3.21 and it worked like a dream. Super impressed with how easy it was compared to when I rooted my original Droid. I decided I wanted to run Cyanogen Mod, since I loved it on the Droid.
The mistake I made was thinking I could install like I did on my Droid - I juts downloaded Rom Manager and downloaded and told it to install the latest version. Now I know that was bad.
My phone now boots only to the white HTC Incredible splash screen and sticks. The only way to power down is to pull the battery. If I pull the battery, and boot using the volume + power button, it vibrates 3 times and the screen goes black.
If I plug it into my computer while it's stuck on the white splash screen Unrevoked will pick it up and start the push. I thought awesome, because it rebooted it back to the hboot screen -- but then it restarted again and stuck on the white splash.
Then I tried stoping unrevoked at the hboot screen and trying clear storage and i tried recovery when that didn't work. Pushing the power button to select the option makes the phone vibrate once and go back to the white splash.
Am I doomed? I tried a Froyo RUU and it can't find it via USB. I'm feeing antsy with no phone and a little nervous I wrecked my Incredible.
Hmm, I've heard there are ways to manually recover via USB, but I'm not sure of how to do it. Also, how long have you let it sit at the HTC screen. Many roms take about 7-10 mins on the first boot and may seem like they are frozen.
If I try booting using power + volume it pulses (vibrates) 3 times and the screen stays black.
Maybe take a look at this.
androidforums.com/incredible-support-troubleshooting/187107-3-vibrates-no-recovery.html
Thanks, so now I can get into hboot - when I volume down to select 'recovery' it vibrates one and goes to the white splash screen again. Then, it goes black with white bars on the right and left sides
jensenist said:
If I try booting using power + volume it pulses (vibrates) 3 times and the screen stays black.
Click to expand...
Click to collapse
Holding volume up and power enables Qualcomm diagnostics (vibrates three times). Pull the battery and put it back in then hold volume down and power. That should get you to hboot.
Sent from my ADR6300 using XDA App
Yea I've made it into hboot now, but it doesn't seem to do anything? It goes to the white HTC Incredible screen, or a black screen with two white bars.
Are the some zip files I should have on my SD Card?
Ok, I found this thread: http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=806734
But the recovery file linked is a dead link?
EDIT: Think I found the file needed: http://www.dougpiston.com/files/Recovery/
in there. Trying to put that on the card now.
Update: I used the file from the thread I found and this time it actually came up withs ome prompts. once I opted yes, though, it went back to the white HTC Incredible screen.
Am I missing anything else? That recovery file is the only thing I've put on the SD card. Do I need any other images?
Call *611 and get a refurb. something happened. same thing happened to me. I flashed shadowrom(not blaming this rom) and instead of booting up i hear 3 beep, black screen flashing green notification light. only way to pull batt. then i try turn on, 3 beep same ****.. weird enough, i could plug it in, get a red light turn it on, and use it fine, i was s-off, this turned me to s-on somehow, and when i had the phone booted finally from having it plugged in, once rebooted, samed 3 beep, and if i tried turning it on while plugged in and pulling the cord before fully booting, it would do the 3 beep, i just got a refurb for this, just flash the signed PB31IMG.zip file to set it back to s-on and stock recovery...
I've got recovery working. Now I just need a backup file to restore to or a stock image or something, I think.
If you have recovery working you're good to go
jensenist said:
I've got recovery working. Now I just need a backup file to restore to or a stock image or something, I think.
Click to expand...
Click to collapse
Step 1: Download this file: http://www.mediafire.com/?n3bmd2bkz55k1b9
Step 2: Connect your phone to your computer.
Step 3: Save all of the files on your sdcard to a folder on your computer.
Step 4: Format your sdcard to fat32.
Step 5: Place the "PB31IMG.zip" file that you downloaded onto the sdcard in the bottom directory.
Step 6: Power down the phone.
Step 7: Hold the volume button down while pressing the power on button. (This will place you in HBOOT)
Step 8: HBOOT will find the file on the sdcard named "PB31IMG.zip" and ask if you wish to update with it. Answer yes. (It will start to load and restart HBOOT and scan for the file again, don't panic, let it do it's thing.)
Step 9: When it is finished it will ask you to reboot the device, press volume up to reboot.
Step 10: Remove "PB31IMG.zip" from the sdcard.
Courtesy of dadicus at http://forum.xda-developers.com/showthread.php?t=760306
I just cleaned it up a bit and made sure it works. This will revert your phone to complete stock 2.1 to include the recovery, radio, splash, etc, ready to receive the 2.2 OTA. After this, just run unrevoked again. Any problems/questions, let me know.
Well. Doomed I think.
It was going through the install like you described, I left the room. Came back to a black screen. Let it sit for a bit. After awhile I decided to go ahead and try a restart. Now, joy of joys, the buttons on the bottom light up but the screen stays black like it's booted up but unresponsive. Can't use the volume + power reboot at all now, I don't think. I'll keep trying.
jensenist said:
Well. Doomed I think.
It was going through the install like you described, I left the room. Came back to a black screen. Let it sit for a bit. After awhile I decided to go ahead and try a restart. Now, joy of joys, the buttons on the bottom light up but the screen stays black like it's booted up but unresponsive. Can't use the volume + power reboot at all now, I don't think. I'll keep trying.
Click to expand...
Click to collapse
Since you already did a restart, tried a battery pull? Detected in adb?
I read a quote once (forget from where), it's not doomed till it doesn't power on.
I haven't tried adb -- I'll have to wait til I get home. battery pull doesn't seem to make a difference. Buttons at the bottom vibrate as I run my finger over them and are responsive - just can't see anything on the screen :\
Ha, I like that quote. And while it sucks breaking stuff, I always learn the most when I've wrecked something to the point I don't think I'll be able to ever recover lol
Not sure how I'm going to try ADB though. Looking at this post: http://forum.xda-developers.com/showthread.php?t=709220
I need access to my phone, and I can't get it. I might actually be doomed now. I'll keep researching. If anyone has tips, they're appreciated.
jensenist said:
Ha, I like that quote. And while it sucks breaking stuff, I always learn the most when I've wrecked something to the point I don't think I'll be able to ever recover lol
Not sure how I'm going to try ADB though. Looking at this post: http://forum.xda-developers.com/showthread.php?t=709220
I need access to my phone, and I can't get it. I might actually be doomed now. I'll keep researching. If anyone has tips, they're appreciated.
Click to expand...
Click to collapse
adb is good to know. It'll let you edit your phone and manipulate it when it's connected to the computer. Very good if your screens broke, and it's quicker than just typing in commands on your phone. Assuming your device is detected, at least. Once you get it up and running, try the command
Code:
adb devices
Well it looks like it's detected. I'm at work, and while they block the USB ports so I can't do anything with the device it is saying "Hey you've connected something, it'll charge but you can't use it"
So hopefully when I get home I can ADB in and fix this nonsense.
I am a little confused why volume+power doesn't do anything, but oh well. Onward!
So I'm not super certain what I did. But I pushed volume and power until it booted, I now appear to be back to stock 2.2 thanks to the img PonsAsinorem linked -- but when I try and make a call it says verizon can't validate my phone.
They give a #8899 number to dial, but I want to ask here what's up before I call it and get an operator that's like "YOU ROOTED AND MESSED UP YOUR PHONE, DIE!" or something less or more severe
EDIT: Nevermind, I called anyway and it took 2 seconds for them to get it back on. I am back at stock 2.2 and working!
I am using a rooted EVO 4G gingerbread with clockworkmod
Current symptoms are as follows:
Boots into a blank screen (backlight is on, but nothing on the screen at all)
Vibrates once you turn it on, but nothing after that.
Stays there until I pull the battery.
Occasionally vibrates twice and a green light will start to blink above the screen.
Tapping power still toggles the screen and backlit buttons when in this state.
Throughout today it's gone through several different symptoms.
At first it was stuck on the quickboot screen doing nothing, but the buttons were completely unresponsive. It would sometimes also constantly vibrate. I took out the battery for awhile and it would just show the screen again when I put it back in and tried to boot.
When I got home later that day, it stopped doing that, but just would refuse to boot at all. It would sometimes show the white screen and just be stuck there unless i pulled the battery out. Now it's doing the symptoms I posted in the beginning.
Any ideas on what's going on and how to fix this?
Can you get into Hboot? If you can you can RUU and hopefully that will do something.
Sent from my PC36100 using XDA Premium App
tropicalbrit said:
Can you get into Hboot? If you can you can RUU and hopefully that will do something.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Thank you for the reply
No I cannot get into HBoot, it literally just boots up (whether or not I'm holding the volume down button or not) into the blank screen I described.
Reioumu said:
Thank you for the reply
No I cannot get into HBoot, it literally just boots up (whether or not I'm holding the volume down button or not) into the blank screen I described.
Click to expand...
Click to collapse
Turn off your device and then remove the battery AND the SD card. Wait about 30 seconds and then re-insert the card and battery. Now simultaneously press the DOWN volume button and the power button until the device starts. You *should* be taken to the HBOOT screen. If so, select 'recovery' from the menu and then go from there. I suggest a re-wipe and re-flash of your rom.
If you still cannot get to the HBOOT screen or recovery, download one of the RUUs from my signature, specifically one with an .exe extension and run it from within Windows while your device is connected to your PC via USB.
Still nothing. Thanks though.
I think I have to just return and get another phone... I haven't seen this error anywhere. I removed the microSD card for about a minute, put everything back in, still tried to boot in recovery (vol- and power) didn't work. I tried one of the RUU .exe and no good, when the phone was on, the program didn't recognize that my phone was there or something. Afterward, I tried the other RUU link where you have to drag files, coudln't see anything when I tried to boot in recovery still.
This is looking like i have to get a new phone
new symptom. Just vibrated 5 times. Longer than normal too.
HELP
Reioumu, what did you do?
i have this exact same problem and im freaking out. any suggestions?
same symptoms...with 5 vibrations and need for a battery pull.
EVO 4G
CYANOGEN MOD 7.1 RC
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.10.0001
I can get into hboot (by pressing vol-down + power)
I cannot get into recovery.
It splashes to the white htc evo screen, then flicker of the LED, 5 vibrates, and a black screen.
i was backuping my system using ROM MANAGER. When i turned on the phone, it couldnt detect the SD card. When i rebooted all the issues you described started to happen.
I'm at wit's end. I did a bunch of googling on the issue. "vibrate 5 times black screen evo" and there seems to be some sort of fix but i dont understand how to implement any of it. I got as far as installing the Android SDK but cant get fastboot to work. The issue seems to be with the USB port AND the SD card detection.
I was planning to just give up and give it to Sprint to fix but the rep said i need to unroot it before i send it to them. [email protected]#[email protected]#. I cant do that without recovery!
hey xda
my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?
try a factory reset.
hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices
Same problem
tekweezle said:
try a factory reset.
hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices
Click to expand...
Click to collapse
My incredible started doing this yesterday, Ive tried this option it doesn't work for me. I can get the menu but it when I choose factory reset or any of the other options it flashes the htc incredible screen and starts the loop again, any more suggestions would be appreciated.
Is your phone unlocked and rooted/s-off?
It will say so on that menu screen.
Sent from my SCH-I500 using Tapatalk 2
Htc loop
wanted167 said:
hey xda
my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?
Click to expand...
Click to collapse
tekweezle said:
Is your phone unlocked and rooted/s-off?
It will say so on that menu screen.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
No I was getting ready to root it the day this started. Will rooting help this problem?
having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.
whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.
i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.
if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.
Htc loop
tekweezle said:
having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.
whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.
i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.
if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.
Click to expand...
Click to collapse
I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol
SuzyQangel said:
I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol
Click to expand...
Click to collapse
This sounds quite a bit like an Inc I have lying on my shelf. It was a friend's and he gave it to me to see if I could fix it. As far as I can tell, the phone's emmc storage simply failed. These phones are aging and that happens sometimes. Anyway, I tried all the usual stuff, including running RUU's (flashing signed PB31IMG.zip's since the thing had never been rooted and was still s-on), and yeah, just boot looped.
I did get the phone working, but it was complicated and messy. Here's more or less what I did: I was able to successfully run the RUU that updates HBOOT to 1.02 (or 1.07, either one works), which allowed me to unlock the bootloader via HTCdev. (see one of the root / s-off guides if this doesn't make sense.) This made it possible to flash ClockworkMod recovery using fastboot, and boot into recovery. From there, I was able to get to a root shell through adb (plugged into my computer) and proceeded to downgrade and get s-off, following the guide. It now works, though it's running Froyo and there is hardly any space for apps due to the messed up storage. I've been wanting to try this hack on it but I haven't gotten around to it yet.
stuck in boot loop, keys dead
I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?
spappy said:
I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?
Click to expand...
Click to collapse
Sounds hosed to me. You could try to flash an RUU zip but that'd require use of the keys in HBOOT. If there is an RUU option that does not involve touching the phone, it's possible. Otherwise, no. I guess you could open the phone and check the button connections are there but it may be locking up at the HBOOT screen. Give it a chance to charge up a bit. However, I believe this phone is a lost cause. I seem to be seeing more frequent bootloop phone reports lately.
So, I tried to restore a backup from TWRP. During the process, the system and cache were restored fine, but couldn't restore the data (for some reason, it said failed), so I figured it's alright, I'll just have to install all the apps again, no big deal. But, after I clicked the "reboot system", the screen went off and never turn back on.
I can't get in bootloader screen in any way, I haven't tried the Vol up + power button for 10s, and the vol down + power button, and the 3 button all together... Nothing works.
When I press the power button normally, nothing happens, not even the Htc logo screen.
When I plug it in, it only shows the battery charging icon. So I tried the buttons combination again (coz I thought at least the screen turns on now), but still, nothing happens, just the screen switch between black and the charging icon.
So, I left it charging overnight, and tried the buttons combination again, nothing works still.
Now I have no idea what to do, can anyone please help me?
Htc one m8 international
Rooted, TWRP recovery, S-ON
It sounds like you hard bricked your phone. Try using this guide youtu . be/ rpA71FXddyU[/ but Im not sure it will work.
Only thing what you need is that computer recognize your phone, because when It doesnt then you should take your phone to local phone repair.
Okay so here's what happened. I unlocked my device just fine, and attempted to install a ROM, didn't work, So i decide I'm going to try to install cyanogenmod. I go this (wikiDOTcyanogenmodDOTORG/w/Install_CM_for_a5 )wiki tutorial [/URL] and I attempt to flash clockworkmod recovery via this link (builderDOTunstableappsDOTCOM/#/latest/clockworkmodrecovery/a5) When i flash, it installs. But then upon booting I get the app for developement only screen, and it's stuck showing my battery charge screen, with the orange charge light. Anyways I can't boot using the power down volume combo. I'm currently waiting on the battery to die so I can reflash the stock recovery, because fastboot won't recognize the device when I plug it in, even though my computer makes the device connected tone. So should I just wait until the battery dies? Or is there something else I can do?
Any help will be appreciated, thanks
Solved
I actually solved my problem. I waited for the phone to die, powered it on normally. Then to reset the device and held the power and up button as soon as the screen went black hit down on the volume and got into my bootloader.