Develop Bugs

Ridiculous Boot Loop - Two bricked DINCs

Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Both phones are completely useless, not sure what to do at this point and CM6's owner was leaving town.
Any ideas? Ultimate way to unbrick a DINC? If you know of anything, please help.

A boot loop is not a brick. I would nandroid back to stock(you did this right?) or use an RUU.

grnmons said:
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Click to expand...
Click to collapse
Does this mean you can get into hboot?
If yes, you should be able to ruu an official release..
Sent from my ADR6300 using XDA App

I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.

ziggymanILT said:
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
Click to expand...
Click to collapse
UD is an AOSP Rom, King's kernel does not support it at this time.
I would try a fresh install of the 8-26 leak. Do wipe first, then do dalvik wipe under advanced settings. Get deodexed version of rom Here
If that does not work let's get some information
Did you run unrevoked forever and get S-off status?
What radio version are you using?
You should not be borked if you are getting into recovery you should be fine.

@ToyTank
BOTH phones are - 2.05.00.6.11 S-ON, Neither are unrevoked forever.
Problem with phone 1 (UD) is that the SD card is completely messed up now. It's an 8GB that has nothing on it, the compuiter is reading it at 758MB. Any function of Recovery leads to errors mounting, so flashing stuff isn't working, nandroid as well.
Phone 2 (CM6) let's me flash stuff onto it, "Install from sdcard complete." but will continue into a bootloop when I restart the phone.
I attempted RUU last night and maybe I'm doing it wrong but the software is giving me an error connecting to USB. How should I go about installing the 8-26 leak? Just wipe > throw in PB31IMG and install?

I assume I don't need unrevoked forever for this, I tried 8-26 and flashed PB31IMG.zip, Device 2 Starts dancing until it says "Main Version is older! Update Fail". Anybody know a workaround?

Try formating the sd card to FAT32 using a computer. That might help with phone #1. Error with usb can be solved using these steps.
1. Try the RUU executable. it will give you that usb error, taking you to the black htc screen.
2. Exit the ruu program (leaving phone in that state) and run it again. This worked for me when I RUU'd mine.
Who knows though. It may have been a one shot deal.

sounds like you are trying a bunch of stuff without READING about what you are doing. you flashed kernels with a rom that CLEARLY states that they will not work and then you tried to flash unsigned roms through hboot which will not work without s-off and then you try to downgrade when you have the ota leak (radio 2.05) which will not work.
you either need to get the ruu working, get s-off applied or follow the steps to go back to stock hboot.
time for you to start doing your homework to get yourself out of this mess.

Neither are bricked. Ruu back to stock.

yeah bro not good practice

@Fretless, @Lafester, @GermanBrat. Thanks for the comments - going to try RUU 3.21.605 and report back.

Hey guys RUU worked for Phone 2 (CM6) but is not playing nice with Phone 1. USB connection error. I appreciate the help so far, any more ideas for this phone?
It's basically stuck in white htc inc screen and will go no further. It's completely wiped and nothing will mount in recovery. RUU can't detect a usb connection but the PC beeps when I connect via usb

Continuous Boot loop, Cant load Recovery, NEED HELP!

Ok, I'll try to keep this simple and informative.
I have been rooted with unrEVOked for months. Last night I flashed CyanogenMod 7 RC2. (I've posted this there too on their forums) Today my Evo crashed while using the app QR Droid, and now goes into a boot loop after the "htc EVO 4g" white screen. It loads that screen, then goes black, reboots and does this cycle until I pull the battery.
I can get into hboot. (v 2.10.001, Clockworkmod), S-OFF, updated radio last night when I actually could before I flashed CM7 RC2 to 2.15.00.11.19.
Here is where the problem deepens, and is very similar to this thread; Bricked Evo, and cant factory wipe. Help please
When I try to select Recovery, the boot-loop starts over; so i actually cant get into recovery and flash anything from the sd card it also does not give me any triangle bull**** or whatever, just starts the boot loop.
I have a card reader for my micro sd card; I took everything off of it and put an RUU on it, renamed it PC36IMG.zip, got into hboot, tried to update it and it failed, goes back to the boot loop. I believe the ruu was outdated.
Can someone link me to the most recent recovery image? I should use to get back to stock? I think that is my problem, the ruu is out of date.
Or any other input would be greatly appreciated.
Thanks
I tried this recovery image to know effect, when i reboot after applying update it goes back into loop; CANT POST LINK YET!

mhport2 said:
Ok, I'll try to keep this simple and informative.
I have been rooted with unrEVOked for months. Last night I flashed CyanogenMod 7 RC2. (I've posted this there too on their forums) Today my Evo crashed while using the app QR Droid, and now goes into a boot loop after the "htc EVO 4g" white screen. It loads that screen, then goes black, reboots and does this cycle until I pull the battery.
I can get into hboot. (v 2.10.001, Clockworkmod), S-OFF, updated radio last night when I actually could before I flashed CM7 RC2 to 2.15.00.11.19.
Here is where the problem deepens, and is very similar to this thread; Bricked Evo, and cant factory wipe. Help please
When I try to select Recovery, the boot-loop starts over; so i actually cant get into recovery and flash anything from the sd card it also does not give me any triangle bull**** or whatever, just starts the boot loop.
I have a card reader for my micro sd card; I took everything off of it and put an RUU on it, renamed it PC36IMG.zip, got into hboot, tried to update it and it failed, goes back to the boot loop. I believe the ruu was outdated.
Can someone link me to the most recent recovery image? I should use to get back to stock? I think that is my problem, the ruu is out of date.
Or any other input would be greatly appreciated.
Thanks
I tried this recovery image to know effect, when i reboot after applying update it goes back into loop; CANT POST LINK YET!
Click to expand...
Click to collapse
I attatched a PC36IMG of Amon Ra recovery version 2.3. You can try flashing that from the bootloader. I will also provide a link to the most recent RUU's and PC36IMG's. This link actually has all of them, old and new. Hope you're able to recover the phone dude. Good luck.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu

thanks, I have clockworkmod from when i unrevoked and had it updated via the CM7 rom manger last night, does that matter?
I tried that img you attached, it did not work, Im not exactly sure how to use the RUU's could someone explain what else I should do?

mhport2 said:
thanks, I have clockworkmod from when i unrevoked and had it updated via the CM7 rom manger last night, does that matter?
Click to expand...
Click to collapse
should'nt make any difference at all. I'm not sure how your initial problem happened, but you are not the first I've seen this happen to. Most that I've seen were recent, and were running CM7. Not sure what's up with that, but if you search the q and a section, you'll find a few similar threads. Very strange. I hope you ge it working again.

Happened to me and a few others a week or 2 ago. There was no fix that we found. Pc36img wont work, ruu won't work. U won't be able to do anything to get s-off to s-on either (in my experience.) Even tho u can get to bootloader, if its like what happened to me and a few others, ur bricked. I got mine warranty replaced (but they're still gonna charge me $125 for returning an unrecoverable phone) another guy threw his out his car window and they charged him $100 to replace his "lost" phone. Those are the only options I know of.
Sent from my PC36100 using XDA App

Stuck on Loading Screen!

I have posted a question about this a wile backwhen it was a white loading screen and someone told me to download the P----.ZIP file and I did and fixed my problem.
Now, this problem has reoccurred and I want to know how to get rid of it.
My HTC Droid Incredible was rooted and when the battery dies, and I charge it, and then start the phone up again, it just loads the screen again (using SKYRAIDER) and it doesn't go past that. I have once again, wiped the phone, installed the P-----.ZIP file(forgot the exact name), and then te phone worked. Once I rooted the phone again use revoked and installed the sky raider theme again, it just loads the loading screen. This always happens whenever my phone dies. Help?

we sort of need more info to work with here.

cvbcbcmv said:
yeah. Please tell us, EXACTLY what you do to flash it. One little thing could do the problem, all details please, it's all important.
Click to expand...
Click to collapse
yep, same, like did you use rom manager, did you do a nandroid backup, what kernal did you flash? did you try to flash a radio?
is said rom made for your phone?

Sorry if my details wasn't enough. Before my phone had died, it had the latest 4.2 Sky raider Rom installed. When the phone had died, this is what I did. I went into the clockwork recovery and wiped the phone completely, then I installed that PB31IMG.zip file to get the phone to unroot it. When that was finished, the phone was fine, everything bak to the way as it was manufactured, not rooted. Then I rooted it with unrevoked and went into recovery and installed the skyraider rom from a zip. Once that was finished, the phone would load up the loading screen and just continue it.. if there's anymore information you need, let me know. Thanks.

Guahan said:
Sorry if my details wasn't enough. Before my phone had died, it had the latest 4.2 Sky raider Rom installed. When the phone had died, this is what I did. I went into the clockwork recovery and wiped the phone completely, then I installed that PB31IMG.zip file to get the phone to unroot it. When that was finished, the phone was fine, everything bak to the way as it was manufactured, not rooted. Then I rooted it with unrevoked and went into recovery and installed the skyraider rom from a zip. Once that was finished, the phone would load up the loading screen and just continue it.. if there's anymore information you need, let me know. Thanks.
Click to expand...
Click to collapse
most roms should already be rooted, that may be what you did wrong
my suggestion, go back to stock, if you made a backup, then use the unrevoked method. then go into recovery, wipe it, reset, that good stuff, then install zip from sd card, then leave it be.

all you pretty much said in that post, sorry if i mis-read it, was that you instaled skyraider after you went to stock, did you load it via rom manager or booted it manually with clockwork mod? and is your phone SLCD or AMOLED. if it is AMOLED you eed to use cwm 3.0.0.7 if SLCD, then use 3.0.0.8

@Kiboe - that is exactly what I did until I got the loading screen. How do I check if my phone is SLCD or AMOLED? How to check it with my problem?
@cvbcbcmv - I installed Skyraider through the CWM, installed it using .zip.

Guahan said:
@Kiboe - that is exactly what I did until I got the loading screen. How do I check if my phone is SLCD or AMOLED? How to check it with my problem?
Click to expand...
Click to collapse
under your phone battery, there should be a SKU number, if the number ends in "VW3" then it's SLCD
if it ends in "VW2" then it's AMOLED
so, AMOLED would be "ADR6300VW2"
and SLCD would be "ADR6300VW3"

I'm only seeing ADR6300VW, not 2 or 3.

Guahan said:
I'm only seeing ADR6300VW, not 2 or 3.
Click to expand...
Click to collapse
It may be AMOLED then, mine is just ADR6300VW. My guess is an SLCD would be ADR6300VW2.
And in a sense ROM hardware version is 002 for AMOLED and 003 for SLCD, if you're on an Incredible ROM anyway, a lot of the Gingersense ROMS based on other phones report my AMOLED as 003. It is not, as I got it on Launch day, and it was manufactured April 2, 2010.

Currently having this problem as well...
I've tried flashing a couple of ROMs--specifically, Synergy RLS1 and Optimized Shift 2.4.1. I tried both the original download and the mirror download for Synergy. I'm flashing through ROM Manager 4.3.0.1 and wiping data, cache, and dalvik. Each time, the ROM will seem to install in CWM, but will be stuck at the white HTC Incredible screen when trying to boot. I know it may stay there for a while when flashing new ROMs, but it will sit there for over five minutes, at which point I just take out the battery and try again. I still get stuck at the same screen, so I just go into recovery and restore my last backup, which works. So I'm not bricked; I can return to a backup, but can't flash a new ROM. What should I try? I've flashed plenty of times before successfully, always the same way, never had this problem unless the download was corrupted.

I'd recommend not using rom manager. Try manually flashing in recovery and see if that doesn't help. I'm also assuming you're on the .92 hboot and 3.x.x.x recovery?

k_nivesout said:
I'd recommend not using rom manager. Try manually flashing in recovery and see if that doesn't help. I'm also assuming you're on the .92 hboot and 3.x.x.x recovery?
Click to expand...
Click to collapse
Worked--thanks! Odd I'd never had a problem with ROM Manager until now.

[Q] Phone is stuck! Help please.

Hi, I am not a noob, but my phone seems to be malfunctioning. Specifically it is having this problem:
My Incredible is running CM7 with ClockwordMod and was having many force close problems and the only solution seemed to be to do a factory reset or try getting a backup from recovery. When I tried recovery however, the phone got stuck on the HTC Incredible white screen and never did anything else. I took out the battery and tried factory reset, this produced the same result. I tried starting up the phone at that point again and when it got to the skateboarding android splash screen, it kept freezing and starting the animation over again. I am fine just doing a wipe through the USB if that's possible but I don't know how that is done. Thanks in advance for any help.
I have tried to flash CWM Recovery using the SDK, but it unfortunately has been giving me a different error, and it won't let me. I am wondering if my phone is dead, and there is no chance of bringing it back.
Currently using an OG Droid that I had as a back-up and wait for the Galaxy Nexus to come out.
Anyone have any ideas?
Thank you.

Your phone is probably fine. Just the recovery needs reflashing.
Go to PvilleComp's site and download a recovery flashable from HBOOT (PB31IMG.zip method). Just boot into HBOOT with the file on the root of the SD card, and it recovery should work again.

Thank you very much! This worked perfectly.
Was able to get back into CM7. Am back up and running.
HUGE HELP!

Help Possible Brick

My buddy's incredible seems like it may be bricked. I can get into recovery, I actually installed the team win 2.0 recovery over top the cwm recovery he had before. I have tried a couple of roms after wiping everything and I cant get past the first splash screen. I have made sure that the radio is up to date, the recovery is good to go but it doesnt seem to want to get past that splash. Anyone got any ideas?
Hard to tell what rom he was running before, I think I installed some version of skyraider (froyo) for him about 9 months ago.
Im not new to android and know my way around fairly well.
I believe its SLCD. Would definitely appreciate any help.

I suggest downloading CWM recovery from "http://pvillecomp.com/?page_id=28" and installing either CWM 3x or 5x. Label the file "PB31IMG.zip" make sure it is NOT labeled "PB31IMG.zip.zip" I just took a look at the Twrp recovery thread and several others are having issues.

I don't think its bricked, just try flashing a new rom by using USB during recovery or updating a PB31IMG.zip over it
Sent from my ADR6300 using XDA App

After trying multiple things, the issue seems like it was from a corrupt ext3 system. It now works after repartitioning the sd card and the ext3 partition.

I hit another snag. After I got the phone booting, I flashed MikRunny and now all hell is breaking loose. The phone will not boot unless I trick it into turning on by plugging the USB cable in when I see the splash screen. MikRunny just loops the boot animation so I cant get into the android system. I can get to hboot and recovery but the phone is not recognizing the sdcard at all now. My PC does recognize it and I have formatted the card multiple times. I cannot get adb to recognize the phone. I dont know if this is a driver issue or an issue caused by the problem. I tried flashing a new recovery by using the PB31IMG method, but I can't because it doesnt recognize the sd card. I tried a different micro sd card and same issue.
I could follow this guide if I could get the SD Card to be noticed (the phone is giving the 5 vibrations when I try to turn it on without the USB cable):
http://www.incredibleforum.com/forum/htc-incredible-help/10309-5-vibs-fix.html
I tried installing an RUU while I was on the hboot screen (not sure if this is even possible from this screen) but the RUU keeps telling me the battery is less than 30% when the recovery shows about 75% and I just charged it recently.
Anyone have any insight on what else I could try? Thanks in advance.

It's a hardware problem unfortunately... You will have to send in for a refurb... I've had the same thing happen to me twice. Wish I had better news for ya, just make sure you flash back to stock through hboot before returning

Not sure how to flash to stock through hboot because it will not read the sd card. I have been able to get the pc to recognize it using fastboot.
If I could somehow get a rom flashed using fastboot I could fix it. Is there any way to flash a .zip update using fastboot? Or a way to force install the RUU exe without it checking battery level?

JLine05 said:
Not sure how to flash to stock through hboot because it will not read the sd card. I have been able to get the pc to recognize it using fastboot.
If I could somehow get a rom flashed using fastboot I could fix it. Is there any way to flash a .zip update using fastboot? Or a way to force install the RUU exe without it checking battery level?
Click to expand...
Click to collapse
Does ADB recognize your phone in CWR? If it does you might be able to get away with Mounting the /System and simply swapping out the Mik Bootanimation for the Stock HTC Bootanimation found in /System/Media? (Correct me if I am wrong). Then basically tricking whoever checks if the phone is rooted with a Stock Bootanimation that bootloops
Hope this helps.