I don't have any faith this is repairable, but I thought I'd ask before I went on Craigslist and looked for a replacement. Here's the senario
bought a EVO and had it flashed to Boost Mobile, it worked fine but I wanted to put a better rom on it. When I bought it, it had Twopointtwo, which I really liked. After I got it flashed it was back to the stock Sprint rom. So I followed the TPT guide on here to a tee yesterday, I couldn't get the radio update to work, I got an error, but I decided I'd try installing the ROM any ways because if I have a problem I could just do a restore.
The phone was getting stuck on the EVO boot screen, I let it sit there for about an hour. So I went into recovery and wiped everything and tried again, When I installed TPT and rebooted I got the phone icon with the arrow and circle around it. I tried power and vol up or down, nothing. so I did a battery pull. Now when I press the power, nothing.
I did a battery pull, took the SD card out, when I hook it to a USB my Windows 7 isn't detecting anything. My gut's telling me it's bricked and there's nothing I can do. But maybe I'm wrong? One thing is, I can't remember if the radio update took or didn't take when I tried to re-flash it this morning.
Copy the contents of your SD card to your computer. Afterwards, using a card reader or your computer, format the SD card, removing all partitions. Afterwards, downloaded a fresh copy of the PC36IMG.zip file for amon_RA from HERE. After that, download a fresh copy of TwoPoint Two or whatever rom you want to use. Place both files on the root of your freshly formatted SD card. Now turn off your device. Simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text will flash across the screen. At the top of the screen, you should see "S-OFF". If you see "S-ON", you will have to re-root your device. Anyway, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. The installation will take about 10 seconds. Afterwards, reboot into your new recovery, and flash the radio. Afterwards, wipe cache & dalvik and then flash the PRI. After that, flash the NV, the WIMAX and HBOOT. Make sure you wipe cache & dalvik in between flashing. You can download the radio stuff from HERE. After that, wipe cache & dalvil ans then go to the flash zip menu and flash your rom. You *should* be good to go afterwards. Be patient during the initial bootup.
posting & replying via the XDA Premium app.
Thanks I'll try that when I get home, the phone doesn't even turn on now, not sure I made that clear in my OP. I tried with and without the SD card in and either way it does nothing when power (and vol up or down) is pressed.
jbird951 said:
Thanks I'll try that when I get home, the phone doesn't even turn on now, not sure I made that clear in my OP. I tried with and without the SD card in and either way it does nothing when power (and vol up or down) is pressed.
Click to expand...
Click to collapse
No, I was unaware that it doesn't power up. Just in case, however, plug it in to the charger, wait about 15 minutes and then see if it turns on. Also, see if the charging LED lights up.
posting & replying via the XDA Premium app.
dougjamal said:
No, I was unaware that it doesn't power up. Just in case, however, plug it in to the charger, wait about 15 minutes and then see if it turns on. Also, see if the charging LED lights up.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I left it hooked to a wall charger for about an hour to a wall charger.
jbird951 said:
I left it hooked to a wall charger for about an hour to a wall charger.
Click to expand...
Click to collapse
Hopefully, it'll power on for you. If it does, follow my instructions. Of it doesn't, try everything again. Take out the battery and SD card and then reinsert them. Try to get to the bootloader screen by simultaneously pressing the power and DOWN volume button. Try connecting via USB to your computer and then try to power it up. Do everything you can before getting rid of it. Let is know what happens either way....Good luck
posting & replying via the XDA Premium app.
Hope it works out for you but if not check out what you can sell it for on e-bay. A bricked Evo with zero damage and a clean ESN goes for some pretty decent $$$
Did you pull the battery right after flashing a radio? I don't know if I followed you correctly, but if that's what happened, the radio was still flashing (the screen with the phone and arrow in a circle is what you get when you flash a radio update, you're supposed to wait and it'll send you back to recovery). Your phone is most likely bricked forever if you did in fact pull the battery during the radio update.
If not, there still may be hope
(from... Evo/MIUI/Tapatalk)
That was my impression too, that he did the battery pull in the middle of the radio update.
HipKat said:
That was my impression too, that he did the battery pull in the middle of the radio update.
Click to expand...
Click to collapse
+1 If I followed correctly, he pulled the battery when it was at the screen with the arrow, which would indicate that the phone was flashing something very important (radio). The battery pull during that phase bricked it, without a doubt. Time for a new Evo, for sure.
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 was switching from Skyraider 3.3 to CM and I accidentally hit Restart Recovery while in Clockwork.
The phone vibrated 5 times then black screen and flashing green light.
Every time i try to get into recovery I get 5 vibrations, a black screen, and a flashing green light. Sometimes I can see the recovery screen for a split second.
I can do a battery pull and get into Hboot from optical, but that's it.
I cant flash any PB31IMG's for some reason.
I tried flashing both a Clockwork recovery and a RUU, but no go.
I tried using the RUU exe and it game me a error about not connecting to phone even though I was in Hboot with usb connected.
Also, today Rom Manager notified me about an update to Clockwork and I told it to update, but this was only supposed to take effect when i boot into Clockwork from Rom Manager.
What should I do? (besides call Verizon for a refurb)
K... so i tried using unrevoked to push a new recovery and it wont run from hboot.
but, i can get into recovery now IF the phone is plugged into usb and unrevoked is at "waiting for device."
if i unplug usb then it does the 5 vibrations w/ black screen and flashing green blinker.
problem is the phone wont mount sdcard.
i saw other people having problems with new CW, but mine still says 2.5.0.5
Bad SD Card?
RMarkwald said:
Bad SD Card?
Click to expand...
Click to collapse
Tried three.
daftlush said:
Tried three.
Click to expand...
Click to collapse
the vibrations/green light typically are Qualcomms diagnostic signal and comes from pressing vol UP/ power.........what cures this for me is a battery pull and making sure my fat fingers press vol DOWN / power to get into recovery properly. not sure if this is a fix for your problem, but worth checking.
wwjdd44 said:
the vibrations/green light typically are Qualcomms diagnostic signal and comes from pressing vol UP/ power.........what cures this for me is a battery pull and making sure my fat fingers press vol DOWN / power to get into recovery properly. not sure if this is a fix for your problem, but worth checking.
Click to expand...
Click to collapse
It's a Qualcomm mode or error code for sure since the phone comes up as "Qualcomm something something" in device manager. Still, dont know what happened to it but I'm damn sure it's fkkked.
I already have another refurb on the way. So my new question is...
If I had the "dev hboot" that i think allows fastboot, would I have been able to fix this phone by flashing a rom from my comp instead of sdcard.
If so, what are the down sides of having a dev hboot?
Same problem here. Rooted fine, then tried to load CM7 on it and it wouldn't boot afterwards.
I can get it to boot while the USB cable is plugged in but as soon as I pull the cable the phone vibrates and shuts off. Tried everything I could find to fix it, no luck. Going to have to go back to verizon.
The phone shouldn't be broken but there seems to be no way to bring it back
daftlush said:
It's a Qualcomm mode or error code for sure since the phone comes up as "Qualcomm something something" in device manager. Still, dont know what happened to it but I'm damn sure it's fkkked.
I already have another refurb on the way. So my new question is...
If I had the "dev hboot" that i think allows fastboot, would I have been able to fix this phone by flashing a rom from my comp instead of sdcard.
If so, what are the down sides of having a dev hboot?
Click to expand...
Click to collapse
FinalBoss said:
Same problem here. Rooted fine, then tried to load CM7 on it and it wouldn't boot afterwards.
I can get it to boot while the USB cable is plugged in but as soon as I pull the cable the phone vibrates and shuts off. Tried everything I could find to fix it, no luck. Going to have to go back to verizon.
The phone shouldn't be broken but there seems to be no way to bring it back
Click to expand...
Click to collapse
Literally just got the green light of death last weekend, it's most likely toast. YOu can turn your phone on and flash a rom when the phone is plugged in to the computer. For me, SD was unreadable (phone defect, sd is fine), and emmc wouldn't mount via usb, and adb wouldn't work either.
They refurbed me no questions asked.
BTW, the .77 fastboot-enabled hboot is only for AMOLED Incredibles. You'll really have a brick if you flash to an SLCD phone. I don't think fastboot would help anyway, as it's most likely a hardware malfunction.
wdfowty said:
Literally just got the green light of death last weekend, it's most likely toast. YOu can turn your phone on and flash a rom when the phone is plugged in to the computer. For me, SD was unreadable (phone defect, sd is fine), and emmc wouldn't mount via usb, and adb wouldn't work either.
They refurbed me no questions asked.
BTW, the .77 fastboot-enabled hboot is only for AMOLED Incredibles. You'll really have a brick if you flash to an SLCD phone. I don't think fastboot would help anyway, as it's most likely a hardware malfunction.
Click to expand...
Click to collapse
I don't know about that...I have an SLCD handset and I flashed .92 with no issues whatsoever.
daftlush said:
I was switching from Skyraider 3.3 to CM and I accidentally hit Restart Recovery while in Clockwork.
The phone vibrated 5 times then black screen and flashing green light.
Every time i try to get into recovery I get 5 vibrations, a black screen, and a flashing green light. Sometimes I can see the recovery screen for a split second.
I can do a battery pull and get into Hboot from optical, but that's it.
I cant flash any PB31IMG's for some reason.
I tried flashing both a Clockwork recovery and a RUU, but no go.
I tried using the RUU exe and it game me a error about not connecting to phone even though I was in Hboot with usb connected.
Also, today Rom Manager notified me about an update to Clockwork and I told it to update, but this was only supposed to take effect when i boot into Clockwork from Rom Manager.
What should I do? (besides call Verizon for a refurb)
Click to expand...
Click to collapse
Sounds like your SD card isn't formatted fat32..... it has to be or hboot won't read the PB31IMG.zip try reformatting
Sent from my Incredible using XDA App
I have hboot 0.92 on there now, I think I have the SLCD version (about a month old). Not home right now, will check when I get there.
I tried running urevoked while it's plugged in and functional but it says "communication issue" so I can't flash a custom rom or restore a backup. There has to be a way to bring it back, it's quite unlikely that it's damaged in any way.
As a last resort I'm going to try the RUU with HTC Sync Found steps in this thread.
http://forum.xda-developers.com/showthread.php?t=864858&page=2
FinalBoss said:
I have hboot 0.92 on there now, I think I have the SLCD version (about a month old). Not home right now, will check when I get there.
I tried running urevoked while it's plugged in and functional but it says "communication issue" so I can't flash a custom rom or restore a backup. There has to be a way to bring it back, it's quite unlikely that it's damaged in any way.
As a last resort I'm going to try the RUU with HTC Sync Found steps in this thread.
http://forum.xda-developers.com/showthread.php?t=864858&page=2
Click to expand...
Click to collapse
I have an ruu that I know works because I had to use it once if you want it just make sure you are formatted right....
http://db.tt/8YWjgVF
Here you go.....
Sent from my Incredible using XDA App
I have the five vibrate + green led problem as well.
Sounds like I'm super lucky though, I can boot into everything fine afterwards.
Running CM7, 9.01, .92, AMOLED.
-CM7 ADR6300
newtoroot said:
I have an ruu that I know works because I had to use it once if you want it just make sure you are formatted right....
http://db.tt/8YWjgVF
Here you go.....
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
No go.
I can boot the phone if the USB cable remains plugged in or if I unplug it during boot (at HTC logo). I can use it, call *228, etc. Once I plug in the USB cable, if I unplug it the phone vibrates x5/green light. I cannot mount it as USB drive on my PC, cannot run unrevoked, cannot run RUU.
I can flash it using a PB31IMG.zip through hboot. It's S-ON. It boots into default OS (2.2), it booted into CM7 before I flashed it but only with the USB cable plugged in. As soon as I unplug the cable it vibrates x5 + green light.
RUU is reporting a connection issue (error 170 USB) so I can't flash it through there.
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
FinalBoss said:
No go.
I can boot the phone if the USB cable remains plugged in or if I unplug it during boot (at HTC logo). I can use it, call *228, etc. Once I plug in the USB cable, if I unplug it the phone vibrates x5/green light. I cannot mount it as USB drive on my PC, cannot run unrevoked, cannot run RUU.
I can flash it using a PB31IMG.zip through hboot. It's S-ON. It boots into default OS (2.2), it booted into CM7 before I flashed it but only with the USB cable plugged in. As soon as I unplug the cable it vibrates x5 + green light.
RUU is reporting a connection issue (error 170 USB) so I can't flash it through there.
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
Click to expand...
Click to collapse
I hate to say it but it sounds toast bro.... if the ruu didn't fix it then it had to be a hardware problem sorry I couldn't help.....
Sent from my Incredible using XDA App
Had this happen to 3 INCs already, call for a refurb.
I'm going to get another one from VZW. Is there any way to make sure this doesn't happen again? I'll start off by not flashing CM7 in the mean time. Anybody have any suspicions on what could cause this?
I just had the same thing happen to mine this morning after flashing the HeyItsLou #9. I can only access ClockworkMod Recovery when I'm plugged in but can't access the sdcard. I've scoured multiple forums for hours and nothing seems to work. I just tried the RUU and it says "wrong image". There seems to be no reason why this happens and there's no one thing that causes it, I've read that it happens to both rooted and non-rooted users.
I filed a claim with Asurion and my new one will be here on Tuesday. It worries me a little that I can't get CWM off of it.
dpwhitty11 said:
I have the five vibrate + green led problem as well.
Sounds like I'm super lucky though, I can boot into everything fine afterwards.
Running CM7, 9.01, .92, AMOLED.
-CM7 ADR6300
Click to expand...
Click to collapse
Same here.
I just pulled the battery, rebooted into recovery then did a recovery from one of my backups.
Now I'm worried there might be a issue with CWM 3.0.0.8 or something causing this to happen to people....? I just read that CWM 3.0.0.8 is known to have issues clearing data or something when installing new ROMs ..
FinalBoss said:
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
Click to expand...
Click to collapse
It would appear that it's for sure bricked if you've tried this.
My Gmail emails weren't coming into my HTC EVO 4G so I tried to power cycled it (my non-Gmail emails were coming in just fine). When I powered it back it on nothing came on the screen, nothing happened. It is rooted (Unrevoked) so I tried holding the power button and volume up button, but it just vibrated three times, nothing came on the screen and nothing happen. I tried power button and volume down button and it boots in HBOOT. Seconds later it runs something and there's a message saying something about wrong image. I stopped here as I haven't used HBOOT before.
What's going on here? How do I get my phone to boot normally again?
P.S. - it's not the battery, because its been charging all night.
DiGiTY said:
My Gmail emails weren't coming into my HTC EVO 4G so I tried to power cycled it (my non-Gmail emails were coming in just fine). When I powered it back it on nothing came on the screen, nothing happened. It is rooted (Unrevoked) so I tried holding the power button and volume up button, but it just vibrated three times, nothing came on the screen and nothing happen. I tried power button and volume down button and it boots in HBOOT. Seconds later it runs something and there's a message saying something about wrong image. I stopped here as I haven't used HBOOT before.
What's going on here? How do I get my phone to boot normally again?
P.S. - it's not the battery, because its been charging all night.
Click to expand...
Click to collapse
It is normal for it to scan and give you that 'wrong image' message. If you had a PC36IMG on your sd card, that's when the bootloader would find it, and ask you to update. Since you dont have a PC36IMG on your card, it scans and finds nothing, so it says 'no image or wrong image'. No worries. What were you trying to accomplish by holding power and volume up? Its power and volume down that puts you to the bootloader. What were your intentions once you got to the bootloader? Were you trying to get to recovery, to clear cache or reflash a rom or something? If you want to reboot your phone without really doing anything, from where you're at in the bootloader, you'll see an option that says 'fastboot'. Select that. Once at the fastboot screen, you'll now see an option to reboot phone, and to power phone off. Select reboot, and see if she powers up for you. Shouldn't be any issues
Weird. So in HBOOT I chose "reboot" from the FASTBOOT main menu and the phone restarted and got back to the desktop/launcher successfully. Everything looks normal.
My Gmail inbox just now began updating from yesterday (even though the phone was on up until a couple of hours ago). Also the apps I set up to install yesterday from market.android.com just started to download and install too.
What's going on here? Is the internal storage/memory/ROM dying or something (come to think of it I did have this Gmail issue last week too, but that power cycle was successful)?
DiGiTY said:
Weird. So in HBOOT I chose "reboot" from the FASTBOOT main menu and the phone restarted and got back to the desktop/launcher successfully. Everything looks normal.
My Gmail inbox just now began updating from yesterday (even though the phone was on up until a couple of hours ago). Also the apps I set up to install yesterday from market.android.com just started to download and install too.
What's going on here? Is the internal storage/memory/ROM dying or something (come to think of it I did have this Gmail issue last week too, but that power cycle was successful)?
Click to expand...
Click to collapse
I'm not sure what would cause the problems you're describing. What ROM are you currently on? Have you tried wiping cache and dalvik cache? Perhaps it's an issue with the Gmail app itself. In any case, I'd first try wiping cache and dalvik. If that works, great. If it fails, I'd probably do a complete wipe and fresh install. That usually solves any issues for me.
Sorry, I saw your initial post after my second post.
I just realize what the confusion may have been. When I powered off the phone I figured I might as well take the opportunity and do a full backup with nandroid. So I proceeded to get into clockworkmod recovery with power + vol. up button (this is when it vibrates 3 times and does nothing). The confusion, I think, is that I've been installing/flashing various ROMs for my new Viewsonic G Tablet for the past 2 days straight (with very lil' sleep) and thought the recovery method (power + vol. up) for the G Tablet was also the method for the EVO.
Anyhoo, at this point I'm very confused. I could of sworn I installed clockworkmod recovery on my EVO and I used power + vol. up to get to it when rooting. I even see the clockworkmod folder on my EVO's microSD card. Weirdness.
My EVO is working now so I guess I shouldn't stress it. I'll just figure out how to do a full backup later.
Thanks!
DiGiTY said:
Sorry, I saw your initial post after my second post.
I just realize what the confusion may have been. When I powered off the phone I figured I might as well take the opportunity and do a full backup with nandroid. So I proceeded to get into clockworkmod recovery with power + vol. up button (this is when it vibrates 3 times and does nothing). The confusion, I think, is that I've been installing/flashing various ROMs for my new Viewsonic G Tablet for the past 2 days straight (with very lil' sleep) and thought the recovery method (power + vol. up) for the G Tablet was also the method for the EVO.
Anyhoo, at this point I'm very confused. I could of sworn I installed clockworkmod recovery on my EVO and I used power + vol. up to get to it when rooting. I even see the clockworkmod folder on my EVO's microSD card. Weirdness.
My EVO is working now so I guess I shouldn't stress it. I'll just figure out how to do a full backup later.
Thanks!
Click to expand...
Click to collapse
Yea, its power down and volume that takes you to the bootloader. You wont get directly to recovery unless your rom has the 4 option quickboot, then u can select recovery. Anyways, so once youre at the bootloader, you just need to select recovery. Then youll boot to clockwork. From there, you can make a new backup, flash a new rom, wipe caches etc.
Sent from my PC36100 using XDA App
Oh, okay. Thanks again!
DiGiTY said:
Oh, okay. Thanks again!
Click to expand...
Click to collapse
You're welcome. I'm glad to help out
I opened up CWM and told it to do a backup, I gave it a name and then it immediately shut off and wont come back on. I removed the battery and tried turning it back on and nothing. Did CWM just brick my phone and if so how?
Can you get into download mode?
Sent from the pink Unicorn from the Darkside.
DarkStarr said:
I opened up CWM and told it to do a backup, I gave it a name and then it immediately shut off and wont come back on. I removed the battery and tried turning it back on and nothing. Did CWM just brick my phone and if so how?
Click to expand...
Click to collapse
Hold volume up + volume down + power button and when your phone switched on after 10 seconds its starts to vibrate release the power button but keep holding the Vol up + Vol down buttons till CWM appears... Do wipe cache then wipe dalvick then reboot your device...
The buttons do nothing, it doesn't respond to being plugged in. I let it sit a bit with no battery still no luck, I let it sit plugged in. Its looking very much like somehow it bricked it.
Try this:
Go to galaxys2root.com find your device and look up how to unroot t mobile galaxy s 2. Gives you a step by step guide and also the files you will need to put your device back to stock.
This is how I done it over 5 times and not once has there been an issue. Make sure Odin is open and you have followed the directions given. Make sure Kies is not open. If Kies is open it will not work.
1) power off device( DO NOT plug in USB.)
2) take out battery.
3) hold power ,volume up and down at the same time. Best way to do this is holding the phone upside down. ( frees your other hand - thumb in power button)
4) put battery back in.
5) plug in USB.
6) as soon as you feel vibration let go of power button.
7) your device will load up in download mode. Press volume up.
8) in Odin, if tar file is loaded you should see com6 in yellow. And device will show mounted.
9) press start and find something to do. Clip your nails, shave , shower , take a dog for a walk. The process takes about 10 mins. DO NOT touch anything.
10) after phone reboots go into settings/backup and reset/ factory reset. PS. This will reset everything on your internal to factory. You WILL lose all you had in your phone.
Your phone should be in stock and completely factory. Please read read read and re read. I'm not responsible for your device.
Sent from my SAMSUNG-SGH-T989 using Xparent ICS Tapatalk 2
Yea, its already toast, a jig does nothing, its not charging and on top of that its not responding to buttons or usb cables. I called samsung and its going in to be fixed, what a PITA all because Rom Manager/Clockwork mod screwed up a simple backup.
People have all ways said using ROM manger app on our phone was a bad ideal
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Yea...... Now I know, and why isn't this information (Rom Manager on the T989 is a probably gonna break stuff) not in the info thread?
DarkStarr said:
Yea...... Now I know, and why isn't this information (Rom Manager on the T989 is a probably gonna break stuff) not in the info thread?
Click to expand...
Click to collapse
Because 99% of users never experienced a problem. Truth is, for our phones at least there aren't too many options.
TWRP is a good different recovery. However its still probably less stable than clockwork mod. If you are creating s backup, never do it from the app. Use recovery.
Sent from my SGH-T989 using xda premium
Well, its on its way back, they replaced the PBA (Phone Board Assembly) so it truly bricked it.
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.