Develop Bugs

[Q] Unable to restore Incredible to stock 2.2

After messing with a custom ROM downloaded from ROM Manager, I wanted to go back to my original stock 2.2. However, when I went to do the restore of my most recent backup (done before I flashed this most recent ROM) it tells me that the MD5 sum has a mismatch and won't do the restore.
So after doing some research, I try and do a clean restore of the stock 2.2 RUU .zip, but HBOOT tells me that the PB31IMG.zip is out of date and won't do the update.
I have no other backups on my SD card or anywhere else, and I've flashed the phone to a different ROM that was downloaded to my SD card so I at least have a functioning phone. However I want to bring it back to stock in case I have to send the phone to Verizon at some point.
Security is set to S-ON for those who need to know.
Any assistance on this is greatly appreciated. Thanks in advance.

http://forum.xda-developers.com/showthread.php?t=714114

That worked! Restoring my backup now! Thank you!

Ok, after fixing the MD5 error and restoring my backup (and clearing the cache/data/etc) It shows the "HTC Incredible" screen, but then goes black and shows nothing at all. All buttons are unresponsive and a battery pull is necessary to get back into recovery.
What might be happening here?

I've been having the same exact problem. My phone is almost unusable right now after loading a 2.3 ROM onto to it just to see how it worked. I backupped my files and clear my cache before hand, but when I load into HB Boot and click recovery, the phone vibrates, displays the HTC logo, then goes to a black screen with two white bars on the sides. It is unresponsive and requires a battery pull.
I can reboot the phone and get into the 2.3 ROM, but it is slow and buggy. No android market, lots of force closes, and won't load my google account.
I assume the problem has something to do with Clockwork MOD recovery. Any ideas out there?

kaptain120 said:
I've been having the same exact problem. My phone is almost unusable right now after loading a 2.3 ROM onto to it just to see how it worked. I backupped my files and clear my cache before hand, but when I load into HB Boot and click recovery, the phone vibrates, displays the HTC logo, then goes to a black screen with two white bars on the sides. It is unresponsive and requires a battery pull.
I can reboot the phone and get into the 2.3 ROM, but it is slow and buggy. No android market, lots of force closes, and won't load my google account.
I assume the problem has something to do with Clockwork MOD recovery. Any ideas out there?
Click to expand...
Click to collapse
Actually it does sound like CMR, check the lastest unrevoked rooting thread to get the image and how to install it. This usuallly occurs with the slcd screens. If i'm wrong someone else let me know.

You can go here to get the SLCD recovery: http://www.incredibleforum.com/foru...nly-see-black-screen-white-bars-recovery.html

worked liked a charm. Thanks.

[Q] Dinc stuck on white "htc Incredible" screen

I installed a new rom that I ended up not liking as much as I thought I would so I restored to the nandroid backup I had previously made. Now when I turn the phone on it gets stuck at the white "htc Incredible" screen. I have pulled the battery and can get into recovery but when I try to turn it on normally it does not work. Anybody know how I can fix this?

Go into recovery, which you say you can do, and try your nandroid restore again. If that fails, it may be a corrupt nandroid. Worst case, wipe clean and flash the previous ROM that you know works and rebuild your apps and data.
vbrana24 said:
I installed a new rom that I ended up not liking as much as I thought I would so I restored to the nandroid backup I had previously made. Now when I turn the phone on it gets stuck at the white "htc Incredible" screen. I have pulled the battery and can get into recovery but when I try to turn it on normally it does not work. Anybody know how I can fix this?
Click to expand...
Click to collapse

Thank you very much. I could not restore to the backup I had made and I never thought to just go back to the rom I had on the SD card. Thank you.

Not trying to threadjack here but I have mostly the same problem so I thought I would just add it here. I was flashed Ruby 2.02 ROM and was just setting things up when my phone rebooted it would not get past the htc incredible splash screen so I read to pull the battery and try to reboot into recovery. When I tried to reboot into recovery my phone just vibrated 3 times then went dead. Did my phone just get bricked or what? ANY help would be awesome!

packerjd04 said:
Not trying to threadjack here but I have mostly the same problem so I thought I would just add it here. I was flashed Ruby 2.02 ROM and was just setting things up when my phone rebooted it would not get past the htc incredible splash screen so I read to pull the battery and try to reboot into recovery. When I tried to reboot into recovery my phone just vibrated 3 times then went dead. Did my phone just get bricked or what? ANY help would be awesome!
Click to expand...
Click to collapse
Can you still get to recovery now? If so, you are probably ok.

I am able to get into recovery but if I try to reboot from there it is still stuck at the splash screen. I think my sd card is not working right now, so I am not able to flash anything. Is my only solution a factory reset?

packerjd04 said:
I am able to get into recovery but if I try to reboot from there it is still stuck at the splash screen. I think my sd card is not working right now, so I am not able to flash anything. Is my only solution a factory reset?
Click to expand...
Click to collapse
You need to boot recovery, wipe and flash a known working rom and start completely over. You really need to get a working card.

Well I flashed one and the problem didn't change so I am now flashing an older one of a different ROM that I hope will work.

packerjd04 said:
Well I flashed one and the problem didn't change so I am now flashing an older one of a different ROM that I hope will work.
Click to expand...
Click to collapse
complete wipe???

Good news!! The second backup I flashed worked! I think I should be okay for now, thanks for the help userjf.

[Q] Help Please

I got this screen today on my htc evo 4g and cant get past it. I dont know if I killed my phone or what so i am hoping someone can help me. the picture isnt the greatest but is an android with a white box and an arrow. it just keeps looping.

Were you flashing something before this happened?
A radio update maybe?
(from... Evo/MIUI/Tapatalk)

i flast mikfroyo 4.62 and it was fine, then under titanium backup i accidently, restored andriod keyboard(which kept force closing it was from a different rom) so i did something and it asked to uninstall i said yes and now it goes to that screeen

You should just reflash
We're comin from a pure power source.

when i try to do anything in recovery it goes to that screen

When the screen finishes installing whatever it is installing, turn off your device. Now simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text should scroll across the screen. At the top, you should see either S-ON or S-OFF. Hopefully, it will display S-OFF. if it does not, you need to re-root. If it displays S-ON, go to the options on the left side of the screen and select recovery. Your phone will then boot into recovery. Once in recovery, restore a nandroid backup, if you've made any. If not, go to the wipe menu and wipe EVERYTHING except the SD card and then reflash whatever rom you want to flash. If you continue to return to the screen you posted, you may need to re-flash a recovery. I suggest amon_RA. You can flash its PC36IMG.zip from file from the bootloader screen (The screen I directed you to at the beginning of my reply).

Yes it does say S-off, the screen that i took a picture of the status bar at the bottom goes about half way across and then starts over again, it will go to the bootloader screen but will not engage to recovery, i do have backups i always run one before i change anything

Okay, then download the PC36IMG.zip file for amon_RA recovery by clicking on "amon_RA" in my previous post. When the download is finished, place the file on the root of your SD card (not in any folder) and then shutdown your device. Boot back into the bootloader screen. The bootloader should autodetect the file and prompt you to install. Follow the easy prompts to install. Installation should be less than 10 seconds. When you're finished, reboot into your new recovery. From there, you should be able to flash roms again. If you used amon_RA to make your backups, you *should* be able to restore them, but if you used clockworkMod, then do not attempt to restore using amon_RA.

all of my recoveries are clockworkmod, so after i change to amon ra flash a rom that i have saved and the other recoveries dont use?

Yes, the main thing is to get you up and running with a working rom. After that, I suggest you make a backup using amon_RA, however, if you want to use the backups you made with CWM, then after you've successfully flashed a rom, download the ROM Manager app and have it install ClockworkMod for you. Afterwards, you should be able to restore your previous backups.

I agree with the getting up and running part, i have heard amon ra is alot better than clockworkmod, but just hadnt tried it yet, keeping my fingers crossed that this will work, just guessing here that since i have gotten some great feedback, that i didnt brick my phone?

If your phone starts and you can get to the bootloader or recovery, you ARE NOT BRICKED!...lol

dougjamal thank you so much it got past the screen and it is acting like nothing ever happened, this is a prime reason why these forums are great, thank you everyone for reading and responding

You're very welcome, my friend. I'm glad I was able to help. Take care and enjoy the rest of your day...

Stuck on Google Screen after JB Update

Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..

bevnet said:
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
Click to expand...
Click to collapse
1.) Your phone is far from bricked at all. You have access to the boot loader (i.e. the screen with the options). The recovery you're seeing is stock recovery. All you need to do is go into boot loader and fastboot flash recovername (CWM) and you will have your custom recovery back to wipe data and reinstall a rom or restore a nandroid backup

Mine is doing the same thing, weird thing is, it was working since yesterday on jellybean, it just randomly froze this morning and and now won't boot..
im currently at work so i don't have admin rights to do a fastboot flash..
any idea why it would randomly stop working when i havn't flashed anything on it besides the jb rom?

Sorted..
Thanks for the comments.. yeah i was over-reacting a bit there..
I downloaded the Galaxy Nexus Toolkit, got a stock rom form gopogle, flashed it.. back to normal, well, it will be after i restore the CWM backup i took.. phew..
Thanks again
Ian.

Still stuck
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!

this has happened twice today and i think it from using volume+

Steelbully said:
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
Click to expand...
Click to collapse
Boot into recovery, wipe cache, Reboot

s3 t999l unable to flash any rom with twrp 3.1.1-0

I did a search and maybe not correctly but I did not find my particular problem.
So I have stock root66 rom flashed with odin 3.11 on my phone goes into boot loop.
I flashed twrp 3.1.1-0 with odin and I can go into recovery but as soon as I select any rom (OCT-N-WEEKLY-20170811-1427-d2tmo) it starts to do something and just reboots the phone and back into the boot loop. I reboots to fast for me to even figure out what it says on the phone.
Has anyone else experienced this? Battery is charged to 80%+
edit: tried CWM same symptoms reboots right away. Only thing I can flash with is odin otherwise with any recovery reboots right away. I was able to flash a modem with twrp and that works but no roms work.
update 2: I finally was able to get root66 installed. Gets to the set up part. Once I finish the setup the phone turned off on its own. It never turns on on its own so leads me to believe the power button isnot stuck but why does it turn off on its own? I turned back on and goes into bootloop.

The power button may be stuck in the "pressed" position.
Have you tried TWRP 2.87? You're sure you are flashing the correct TWRP version for the phone?

audit13 said:
The power button may be stuck in the "pressed" position.
Have you tried TWRP 2.87? You're sure you are flashing the correct TWRP version for the phone?
Click to expand...
Click to collapse
Thanks for the reply. I have tried 6.0.1.2_CWM_Touch-recovery-image & twrp-3.0.2-0-d2tmo.img but not 2.87.
However, as I stated above I was able to flash a modem but just not flash any roms which is weird.
If the power button pressed and the phone reboots when i pull the battery and put back in wouldn't the phone turn back on? I'm just finding it odd the phone keeps rebooting but when I pull the battery and put back in it doesnt turn on automatically.
update: So 2.8.6 twrp worked which is odd installing as we speak phone has not rebooted yet so lets see how it does once rom is flashed. I did odin root66 and after that installed it kept rebooting so fingers crossed this works. Using OCT-N-WEEKLY-20170811-1427-d2tmo hopefully this works

so after the flash seems to just back to the bootloop. I'm still not convinced my power button is stuck since it doesnt auto turn on and during the whole process of flashing it didnt reboot on its own only after the flash. Any ideas?
Literally gets to the samsung galaxy siii logo and reboots right away.

Try flashing the latest stock ROM, not a rooted stock ROM.

audit13 said:
Try flashing the latest stock ROM, not a rooted stock ROM.
Click to expand...
Click to collapse
same bootloop. Gets to the tmobile animation and then reboots.

It's possible that the memory chip is damaged. You could take it to a repair shop and have it flashed via jtag.