Develop Bugs

HELP!!! hBOOT .92 in bootloop

I just installed HBOOT .92 on the root of SD card. It installed because it is listed at the top of recovery. But when I try to reboot, it keeps coming back to the bootscreen. I've tried powering down, but still comes back to bootscreen. What have I done and how can I get out of this? First time I've ever had what seems to be a potentially serious problem.

PeanutTM said:
I just installed HBOOT .92 on the root of SD card. It installed because it is listed at the top of recovery. But when I try to reboot, it keeps coming back to the bootscreen. I've tried powering down, but still comes back to bootscreen. What have I done and how can I get out of this? First time I've ever had what seems to be a potentially serious problem.
Click to expand...
Click to collapse
just restore through recovery... you got a back up right!?!
after you restore, it should be fine. updating HBOOT wipes your kernel which is why this happens.

PeanutTM said:
I just installed HBOOT .92 on the root of SD card. It installed because it is listed at the top of recovery. But when I try to reboot, it keeps coming back to the bootscreen. I've tried powering down, but still comes back to bootscreen. What have I done and how can I get out of this? First time I've ever had what seems to be a potentially serious problem.
Click to expand...
Click to collapse
If you are in recovery nandroid back. You will retain .92 hboot.

PhillyCheez said:
just restore through recovery... you got a back up right!?!
after you restore, it should be fine.
Click to expand...
Click to collapse
this
10 chars

Okay, not real sure what I did, but seems that I got out. Was finally able to get back to recovery screen and in the process of doing a nandroid restore.
Regardless, curious as to what I did wrong? Almost scared to attempt again. I guess I don't really need it, just feel like I need to have the latest and greatest of everything. Thanks for any input.

So, do you install the kernel right after flashing the new HBOOT, but before rebooting to avoid the problem again?

PeanutTM said:
Okay, not real sure what I did, but seems that I got out. Was finally able to get back to recovery screen and in the process of doing a nandroid restore.
Regardless, curious as to what I did wrong? Almost scared to attempt again. I guess I don't really need it, just feel like I need to have the latest and greatest of everything. Thanks for any input.
Click to expand...
Click to collapse
PhillyCheez said:
updating HBOOT wipes your kernel which is why this happens.
Click to expand...
Click to collapse
this
10 char

PeanutTM said:
So, do you install the kernel right after flashing the new HBOOT, but before rebooting to avoid the problem again?
Click to expand...
Click to collapse
it's honestly not really a problem. just nandroid before you update HBOOt next time.
OR
not sure if this works but have a kernel backed up on your sdcard before hand. just flash the kernel from recovery and in theory you should be good to go with a nandroid restore.

Phone hangs after new ROM install

Hello all!
Yesterday I decided I wanted to try the latest RCMix ROM (v2.2b). Usually I do the update from ROM Manager, but it informed me there was a new version to download so I downloaded it.
Anyway, I proceeded with it and installed the ROM and everything went fine, until it rebooted, which it then just hung on the s-off boot screen. I waited for an hour but to no avail so had to take out the battery.
So, I tried to do it again manually by doing a factory wipe/clear cache/clear dalvik cache and flashed again, but again, same thing happened even though it said it had installed ok. I tried doing this 5 times before I gave up (although leaving 20 minutes on the boot screen before giving up each time)
Next I decided that maybe it was the new version of the ROM, so I downloaded the v2.1 of it, but still got the same problem, so then I decided to try my original one (v2.0) because it worked fine previously, but this also didn't work!
Finally, I decided I best try a different ROM altogether, so I tried the LeeDroid ROM (which I've used in the past,albeit a previous version), but this also has the same problem.
So, I'm a bit stuck what to do, hence why I've had to post on here. I've read that the latest clockworkmod recovery has some issues, does this still apply? Could this be the cause of my problem? I've tried finding a previous version of clockworkmod to install via sd card to test it out, but had no luck finding one.
Does anyone else have any suggestions on what I can do? Please bare in mind that I'm not very good with all the technical side of this so please try keep it as simple as possible for me!
My phone recovery says the following:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNW0101
RADIO-5.10.05.23
ClockworkMod Recovery v5.0.2.0
Thanks in advance for your help

hi there, do the roms you are trying require an ext partition on the sd card?

elliottg61 said:
hi there, do the roms you are trying require an ext partition on the sd card?
Click to expand...
Click to collapse
I believe they do yes. I did forget to mention I do have my SD card partitioned with 1GB~ ext partition

go to mounts and storage
format:
-boot
-system
-data
-cache
-sd-ext
-NOT SD-CARD!!!!!!!!!!!!!!!
Try to flash the rom again

bortak said:
go to mounts and storage
format:
-boot
-system
-data
-cache
-sd-ext
-NOT SD-CARD!!!!!!!!!!!!!!!
Try to flash the rom again
Click to expand...
Click to collapse
Out of curiosity, what would happen if I did SD-Card?
I shall try it now anyway and let you know

smhouston said:
Out of curiosity, what would happen if I did SD-Card?
I shall try it now anyway and let you know
Click to expand...
Click to collapse
I wonder what would formatting my Sd-Card do, possibly delete anything and everything off of it?

bortak said:
I wonder what would formatting my Sd-Card do, possibly delete anything and everything off of it?
Click to expand...
Click to collapse
lol I mean would it have any affect on the ROM installation process? Obviously I'd lose all my personal data but I have it all backed up anyway
Waiting to see if it'll load atm, still on the same screen, but only been 5 minutes so far. What's the next option if this doesn't work? I was thinking about just trying to go back to stock and start it all form scratch again.

As suspected, it still did the same thing :-(

Are the roms you are installing for specific use with the CM7 Hboot?

You mentioned Rom manager at the start, are you downloading your roms through there or from your pc?
Sent from my HTC Desire

Try EVERYTHING without ROM manager....

rootSU said:
Are the roms you are installing for specific use with the CM7 Hboot?
Click to expand...
Click to collapse
I think the RCMiX used to be
mistaliu said:
You mentioned Rom manager at the start, are you downloading your roms through there or from your pc?
Sent from my HTC Desire
Click to expand...
Click to collapse
I usually download the ROMs manually, place on the SD card, then do the install by selecting the option in ROM Manager
rootSU said:
Try EVERYTHING without ROM manager....
Click to expand...
Click to collapse
I'm going to remember this for the future!
After me being impatient (you'll probably be disheartened to hear) I've decided to go the stock way to try get me back to the beginning. After a lot of messing around (reformatting sd-card and placing files on it via a laptop which had the files put on there via USB flash drive!) I think I've managed to get it down to stock again. The bootloader screen thingy says:
BRAVO UNKNOWN SHIP S-ON
HBOOT-0.75.0000
MICROP-031d
TOUCH PANEL-SYNW0101
RADIO-4.05.00.11
and when I try select the RECOVERY option it just displays the red triangle (I believe this is because it's not rooted or something (can't currently remember how got it working last time)?)
The problem now though is I would have though I should be able to boot normally now? What happens is when I press the power button it just goes straight into the bootlader screen.

At the triangle, you press vol UP + Power to get to stock recovery. Cant do much there but factory reset though.
did you fastboot flash the downgrader.img from Alpharev before running the RUU?

rootSU said:
At the triangle, you press vol UP + Power to get to stock recovery. Cant do much there but factory reset though.
did you fastboot flash the downgrader.img from Alpharev before running the RUU?
Click to expand...
Click to collapse
I've just tried the up + power but when I do it displays the menu options i.e. Apply sdcard:update.zip and wipe data/factory reset; however, it has a yellow message below saying E:Can't open /cache/recovery/command ..... should I be concerned?
Yes I flashed the bravo_downgrade.img located at http://alpharev.nl/ by doing it via the SD card. Currently I can't connect to my phone via adb

smhouston said:
I've just tried the up + power but when I do it displays the menu options i.e. Apply sdcard:update.zip and wipe data/factory reset; however, it has a yellow message below saying E:Can't open /cache/recovery/command ..... should I be concerned?
Yes I flashed the bravo_downgrade.img located at http://alpharev.nl/ by doing it via the SD card. Currently I can't connect to my phone via adb
Click to expand...
Click to collapse
That error always comes up on stock recovery I think. It always did for me anyway.
I'd be tempted to factory reset then run an RUU again.

rootSU said:
That error always comes up on stock recovery I think. It always did for me anyway.
I'd be tempted to factory reset then run an RUU again.
Click to expand...
Click to collapse
That's ok then. Do you have any recommended RUUs? My phone was bought unbranded and unlocked

If truly unbranded 2.29.405.5
Sent from my HTC Desire using XDA App

smhouston said:
That's ok then. Do you have any recommended RUUs? My phone was bought unbranded and unlocked
Click to expand...
Click to collapse
I've just tried the following RUU after doing a factory reset:
RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865
However when going through the instructions it said that my current image is:
2.29.405.5
I proceeded anyway by pressing Update, and it ended up with the following error:
ERROR[140]: BOOTLOADER VERSION ERROR
From what I've quickly googled, it sounds like I got that error because the RUU I was trying to install was less than the one currently installed? If so then how can I get one that is newer as I can't see any newer ones than that!
EDIT: I'll try using the one you suggested again

If it starts with a 1 its android 2.1. You do not want that. It must start with a 2 at least
Sent from my HTC Desire using XDA App

rootSU said:
If it starts with a 1 its android 2.1. You do not want that. It must start with a 2 at least
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Wahey, you'll be pleased to know it's worked! Thank you all for your time and patience with me. Got to admit I thought I was doomed!

[Q] Back to Gingerbread after going ICS?

If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?

davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I would recommend tracking down calkulins format zip for the evo

1brainsurgeon said:
I would recommend tracking down calkulins format zip for the evo
Click to expand...
Click to collapse
Yeah... tried that already... Didn't fix it...

davidnjessicacruz said:
If this has been asked before then please forgive me...
I can not go back to any backup I had of CM7 or Gingerbread Sense ROM since upgrading to some Alpha ICS roms. I've tried wiping everything & started from scratch on these roms but I always get stuck at "failed to write boot partition from /tmp/boot.img" It doesn't matter what Gingerbread ROM I choose with the exception of MIUI rom (don't know why). I thought maybe I could use that as a stepping stone to go back from there but nogo. I've used RA's recovery & CWM with no success. Any ideas?
Click to expand...
Click to collapse
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?

Captain_Throwback said:
I can say with certainty that I don't have this problem. I've flashed every ROM from here to Timbuktu, AOKP, Deck's, Evervolv, and have had no problem restoring a nandroid of, or flashing MikG, Mik3D, MikRunny, The Express, or any other ROM I may have forgotten.
That boot partition error doesn't sound good, though. What HBOOT version do you use?
Click to expand...
Click to collapse
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?

davidnjessicacruz said:
HBOOT 0.97 is what I'm still using... never upgraded... should I & how do you recommend that I do so?
Click to expand...
Click to collapse
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.

Captain_Throwback said:
No reason to upgrade - just wondering.
I'd recommend you flash a stock ROM in the bootloader - that should normalize everything, and then try those other ROMs again.
Click to expand...
Click to collapse
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.

davidnjessicacruz said:
I assume your talking about in the recovery (aka amon ra/ clockworkmod), if so then I've tried that as well. Same issue.... This is not sounding good for me.
Click to expand...
Click to collapse
I believe he's talking about a RUU
Sent from my PC36100 using XDA App

evo4gnoob said:
I believe he's talking about a RUU
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well

davidnjessicacruz said:
The stock one? Wow... don't even know how to flash that back.... hmm... I'll see if I can find it here, if not then I'll google it. I'll keep you informed.... hopefully bricking does not ensue.... any help here would be great as well
Click to expand...
Click to collapse
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).

Captain_Throwback said:
In the first "My Links" link in my sig, there are 3 of them.
They're PC36IMG files - you rename the file to exactly that - PC36IMG.zip - and put the file on the root of your sd card. Then you reboot your device into bootloader (HBOOT) mode. From a powered off state, hold the Volume down button and then press and hold the power button until you see the HBOOT screen. The file should be recognized and loaded, and after a minute or so it will ask you to update. Press Volume Up to accept, and then wait for a while.
NOTE: This will upgrade your HBOOT, but that's no big deal. The phone will reboot into the bootloader once near the beginning of the process by itself - that is also okay. Don't touch anything while it's updating.
At the end of the process, you'll need to find a PC36IMG for your preferred recovery (RA-supersonic-v2.3 recommended), which you will flash the same way as the ROM (in fact, you can replace the ROM file with the recovery file - unless you want to hold on to it, then you can just move or rename it).
Click to expand...
Click to collapse
Failed on #4 Boot.... it stated "failed - PU" "Partition failed" Fun times.... Now the phone is a brick (stuck at the white screen).... Where there is a will then there is a way so I'll find a way.... any help would be appreciated though....

Sooo... I was able to flash back my alternate recovery using a PC36IMG version of it. Thank god for the rooted community.... Restoring back my last backup. Funny though, that I still could not restore a rooted stock backup I had or a new upgraded .zip that I wanted to use. Common denominator in all this (even when trying to use the 4.24.651.1 version of the stock software PC36IMG), it can not write the boot.img Any one else had this problem? Next I will try to RUU which will technically make me lose root but I should be able to get it back, assuming I'm successful, since I still have S-OFF.
PS: My HBOOT now, btw, is 2.16.0001 so I know that the original attempt to get back to gingerbread was succesful

Is it fixable?

Hello,
There is this Droid Incredible 2 that I have that is kinda broken...
I cannot flash anything on it...
The phone is S-off and rooted. I have tried flashing new ROMs, and new Recoveries, but after it says install completed and what not, it just loads the one that was previously loaded. It has some outdated recovery (Revolutionary 4.0.0.4? or something) and an outdated ROM (One of the early "Skyrader" ROMs).
Every time I flash a new ROM, it will go through the installation process and complete, but it will boot back to the previous ROM.
Every time I flash a new Recovery, it will go through the installation process and complete, but it will go back to the previous recovery.
I have also tried flashing through ADB without success.
If anyone knows a solution to fix this problem, please help me.
Thanks!

yuya1030 said:
Hello,
There is this Droid Incredible 2 that I have that is kinda broken...
I cannot flash anything on it...
The phone is S-off and rooted. I have tried flashing new ROMs, and new Recoveries, but after it says install completed and what not, it just loads the one that was previously loaded. It has some outdated recovery (Revolutionary 4.0.0.4? or something) and an outdated ROM (One of the early "Skyrader" ROMs).
Every time I flash a new ROM, it will go through the installation process and complete, but it will boot back to the previous ROM.
Every time I flash a new Recovery, it will go through the installation process and complete, but it will go back to the previous recovery.
I have also tried flashing through ADB without success.
If anyone knows a solution to fix this problem, please help me.
Thanks!
Click to expand...
Click to collapse
Did you wipe data, cache and dalvik before flashing?

brymaster5000 said:
Did you wipe data, cache and dalvik before flashing?
Click to expand...
Click to collapse
Thanks for the reply!
Yes, I have wiped everything possible... I have even wiped multiple times on each just to make sure... with no luck

Did you try 4ext recovery?
Maybe try returning to stock...
Sent from my ViperDinc

brymaster5000 said:
Did you try 4ext recovery?
Maybe try returning to stock...
Sent from my ViperDinc
Click to expand...
Click to collapse
Thanks for the reply!
I have flashed the phone with the stock images numerous times... but actually didn't go back somehow...
I have not tried the 4ext recovery; I will try that later tonight.
Thanks you!

I'd say format the SD card on its own and try transferring only a single rom and going from there. I don't know what formatting system mem would do but someone here might know.

kwick85 said:
I'd say format the SD card on its own and try transferring only a single rom and going from there. I don't know what formatting system mem would do but someone here might know.
Click to expand...
Click to collapse
Yeah, sometimes the SD card gets screwed. I don't know how or why, it just happens. And if you formatted the card, try flashing a ROM and maybe tell the phone where the boot.IMG is VIA Fastboot. If that didn't work, then try going back to a stock PMGIMG32. I don't have a S-OFF myself, but I hear you can go back to stock and it will still be rooted. If I am wrong, then someone please correct me.
Sent from my Incredible 2 using xda premium

EVoorhees said:
Yeah, sometimes the SD card gets screwed. I don't know how or why, it just happens. And if you formatted the card, try flashing a ROM and maybe tell the phone where the boot.IMG is VIA Fastboot. If that didn't work, then try going back to a stock PMGIMG32. I don't have a S-OFF myself, but I hear you can go back to stock and it will still be rooted. If I am wrong, then someone please correct me.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
You are correct. I did it.
sent from my paranoid android

depending on your recovery version, most new ICS or JELLYbean ROMs won't flash on older versions of recovery.

[Q] Can't reboot or get to recovery, can get hboot

I've searched the forums and can't find for my specific problem. I was running CM7 and heard that the Tiamat kernel worked great with it so I flashed it. Something apparently went wrong and now I can't boot, it just get stuck on the white HTCIncredible screen. When I go to hboot and try to boot into recovery, it just gives me the black screen with white bars. I also can't get my computer to recognize it as storage. No idea how to proceed. Here is what it says in bootloader. Please help!!!!
Incredible XD Ship S-off
Hboot-0.92.0000
microp-0417
touch panel-atmelco3_16ac
radio-2.15.00.07.28
jul 23 2010 18:06:51

deathvalley1981 said:
I've searched the forums and can't find for my specific problem. I was running CM7 and heard that the Tiamat kernel worked great with it so I flashed it. Something apparently went wrong and now I can't boot, it just get stuck on the white HTCIncredible screen. When I go to hboot and try to boot into recovery, it just gives me the black screen with white bars. I also can't get my computer to recognize it as storage. No idea how to proceed. Here is what it says in bootloader. Please help!!!!
Incredible XD Ship S-off
Hboot-0.92.0000
microp-0417
touch panel-atmelco3_16ac
radio-2.15.00.07.28
jul 23 2010 18:06:51
Click to expand...
Click to collapse
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!

nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
How do I check the md5? I'm not sure what that is... Thank you for your help, I'm going through this process right now.

nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
Also, after putting the PB31IMG of CWM recovery on the root of my sd card, I booted into hboot and it says:
Parsing... [sd zip]
[1] Recovery
do you want to start update
<volume up> yes
<volume down> no
I clicked yes because i assumed this is what you were talking about when you said if would ask if you wish to flash it. it just did the little update thing and asked me if I wanted to reboot and I again said yes and it went back into the HTCIncredible white screen.

nschiwy said:
I've heard of this problem before but I don't remember the way that it was fixed in the past so this is how I would proceed. You're going to need to find a way to access your sd card without using your phone such as an SD card adapter or something like that. When you do that, place this file on to the root of your sd card http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip it is a PB31IMG of CWM recovery, which you can flash through hboot because you have s-off. Just boot into hboot and it should find the file and ask you if you wish to flash it and you should say yes. A word of advice: check the md5 of the file before you flash it as well: there are several md5 sum checkers online that you can download for free and I highly recommend it. It might be why you're in this mess to begin with and flashing bad files through hboot can brick your phone permanently. the correct md5 for the file is here: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.md5
Once you have CWM flashed, you should be able to restore any backups you have made and go on with life. if you still have issues I would recommend flashing your favorite RUU though hboot. since you have s-off it won't be very difficult to regain root and return to the settings/rom you had before but an RUU is sometimes necessary to restore the file system before you can proceed with other things. Good luck!
Click to expand...
Click to collapse
ok sorry for the frantic multiple responses. You got me to where i can now boot into recovery! Thanks!!! Here is where I am. I tried to restore a backup I did before flashing the (apparently corrupt) kernel. it says:
Checking MD5 Sums....
MD5 Mismatch!
What do I need to do from here just to get back to the previous backup I did. I don't want to screw anything up more than I already have, so I will await your guidance because you obviously know exactly what you're talking about!
Thanks again

deathvalley1981 said:
ok sorry for the frantic multiple responses. You got me to where i can now boot into recovery! Thanks!!! Here is where I am. I tried to restore a backup I did before flashing the (apparently corrupt) kernel. it says:
Checking MD5 Sums....
MD5 Mismatch!
What do I need to do from here just to get back to the previous backup I did. I don't want to screw anything up more than I already have, so I will await your guidance because you obviously know exactly what you're talking about!
Thanks again
Click to expand...
Click to collapse
Okay, The only thing is, this may not have been your fault at all and the recovery may have just gotten funky and essentially self-destructed. I'm worried that may be the case and that the backup you created before flashing the kernel may also actually be corrupt. However, if you're feeling lucky we can go ahead and do this but keep in mind that it will probably get us back where we started and it can cause permanent damage to your phone. Out of curiosity, did you go back into your ROM and rename the folder that you created the backup in before going back into recovery and flashing the kernel?

nschiwy said:
Okay, The only thing is, this may not have been your fault at all and the recovery may have just gotten funky and essentially self-destructed. I'm worried that may be the case and that the backup you created before flashing the kernel may also actually be corrupt. However, if you're feeling lucky we can go ahead and do this but keep in mind that it will probably get us back where we started and it can cause permanent damage to your phone. Out of curiosity, did you go back into your ROM and rename the folder that you created the backup in before going back into recovery and flashing the kernel?
Click to expand...
Click to collapse
I did not rename it because I know that throws everything off. Also, I tend to forget things in these processes so please feel free to ask any question no matter how obvious it seems... Thank you, I have to get this thing running.
As a sidenote, I have 2 older backups that I haven't tried to restore yet due to not wanting to screw it up further. I would try those if you suggested it.

deathvalley1981 said:
I did not rename it because I know that throws everything off. Also, I tend to forget things in these processes so please feel free to ask any question no matter how obvious it seems... Thank you, I have to get this thing running.
As a sidenote, I have 2 older backups that I haven't tried to restore yet due to not wanting to screw it up further. I would try those if you suggested it.
Click to expand...
Click to collapse
yeah, try one of those.

nschiwy said:
yeah, try one of those.
Click to expand...
Click to collapse
got through a lot of it, at least the md5 sums but then got:
Error while restoring /sdcard/.android_secure!

deathvalley1981 said:
got through a lot of it, at least the md5 sums but then got:
Error while restoring /sdcard/.android_secure!
Click to expand...
Click to collapse
If your main concern is just to get the phone working again, then you can just flash CM from scratch like you did originally. Wipe/factory reset > flash CM > flash GApps > reboot and rejoice
or any other ROM for that matter, like mine http://forum.xda-developers.com/showthread.php?t=1788393
I can't really blame you if you prefer CM over sense though

nschiwy said:
If your main concern is just to get the phone working again, then you can just flash CM from scratch like you did originally. Wipe/factory reset > flash CM > flash GApps > reboot and rejoice
or any other ROM for that matter, like mine http://forum.xda-developers.com/showthread.php?t=1788393
I can't really blame you if you prefer CM over sense though
Click to expand...
Click to collapse
I'm actually going to try yours, but can you re-educate me on flashing gapps?

deathvalley1981 said:
I'm actually going to try yours, but can you re-educate me on flashing gapps?
Click to expand...
Click to collapse
if you are using mine then you don't need to flash GApps, it's included in the ROM. but if you go back to CM at some point you will need to go to this page: http://goo.im/gapps and find the appropriate file for your version of CM and then just flash it like you do the ROM right after you flash the ROM and then reboot into android.

nschiwy said:
if you are using mine then you don't need to flash GApps, it's included in the ROM. but if you go back to CM at some point you will need to go to this page: http://goo.im/gapps and find the appropriate file for your version of CM and then just flash it like you do the ROM right after you flash the ROM and then reboot into android.
Click to expand...
Click to collapse
thank you so much for all your help and I like your rom already! It's super quick.

deathvalley1981 said:
thank you so much for all your help and I like your rom already! It's super quick.
Click to expand...
Click to collapse
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!

deathvalley1981 said:
Also, after putting the PB31IMG of CWM recovery on the root of my sd card, I booted into hboot and it says:
Parsing... [sd zip]
[1] Recovery
do you want to start update
<volume up> yes
<volume down> no
I clicked yes because i assumed this is what you were talking about when you said if would ask if you wish to flash it. it just did the little update thing and asked me if I wanted to reboot and I again said yes and it went back into the HTCIncredible white screen.
Click to expand...
Click to collapse
Now see if you can access recovery. If you can wipe everything in the mounts and storage menu except emmc and sdcard, and then restore a known good backup or flash a rom fresh.

deathvalley1981 said:
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!
Click to expand...
Click to collapse
No, I've not heard this before. Let me test on my phone and I will get back to you.

deathvalley1981 said:
I've been running it since and love the ROM... not sure how you got it so responsive but it's smooth like butter. One question, for whatever reason, it's not recognizing my sd card and i've never had any problems with this card, tried it in my wife's phone and it worked there. Have you heard this before and if so, any fixes?
Thanks again!
Click to expand...
Click to collapse
Use fastboot and type this command:
fastboot oem enableqxdm 0
That may fix it. If not use a file explorer and go to /etc and open for editing vold.fstab and copy and paste its contents here.

cmlusco said:
Use fastboot and type this command:
fastboot oem enableqxdm 0
That may fix it. If not use a file explorer and go to /etc and open for editing vold.fstab and copy and paste its contents here.
Click to expand...
Click to collapse
do you think his file system got borked somehow?

nschiwy said:
do you think his file system got borked somehow?
Click to expand...
Click to collapse
Could be, have to see what he reports back.