Database Users

[Solved] May have bricked my Z;(

Edit: "Rom Development" is only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here. Moved thread to "General." Please refer to "[REF] STOP! Read before posting!" ~TheRomMistress
Guys i think i may have bricked my Z
I did the following
I flashed the wpthis-Z.ko file
then i flashed the wpthis.PreOTA file
then i flashed the hboot, which worked fine.
But now i get lots and lots of force closes when sense boots,
Can anyone help please?
JD

Go back to stock using the RUU

EddyOS said:
Go back to stock using the RUU
Click to expand...
Click to collapse
Will give it a go mate,
Was that the right way to s-off?
JD

JupiterDroid said:
Guys i think i may have bricked my Z
I did the following
I flashed the wpthis-Z.ko file
then i flashed the wpthis.PreOTA file
then i flashed the hboot, which worked fine.
But now i get lots and lots of force closes when sense boots,
Can anyone help please?
JD
Click to expand...
Click to collapse
ok first of all that is not a brick! Bricks are when you cannot even power on the device, if you're getting all the way into the ROM that is NOT A BRICK.
Second. Learn what you're doing before you do it. wpthis-Z.ko is for the DZ wpthis-pre-OTA.ko is for the G2, both does not mean better.
Third. Which hboot did you flash? if you flashed the g2 hboot that means that your partitions are gonna be different in which case you should flash the roms from the g2 forum not this one.

Sphaerophoria said:
ok first of all that is not a brick! Bricks are when you cannot even power on the device, if you're getting all the way into the ROM that is NOT A BRICK.
Second. Learn what you're doing before you do it. wpthis-Z.ko is for the DZ wpthis-pre-OTA.ko is for the G2, both does not mean better.
Third. Which hboot did you flash? if you flashed the g2 hboot that means that your partitions are gonna be different in which case you should flash the roms from the g2 forum not this one.
Click to expand...
Click to collapse
I flashed the z hboot,
Im just getting errors with sense, lots of force closes;(
JD

JupiterDroid said:
I flashed the z hboot,
Im just getting errors with sense, lots of force closes;(
JD
Click to expand...
Click to collapse
My suggestion would be to re-flash the rom.
http://forum.xda-developers.com/showthread.php?t=832503 has a guide, since you're s-offed you *should* (not positive about this) be able to skip basically everything, grab the rom from RUU and flash it via hboot and you should be fine.

dont worry mate we will find a way,
I'm searching G2 fora right now, will report

Sphaerophoria said:
My suggestion would be to re-flash the rom.
http://forum.xda-developers.com/showthread.php?t=832503 has a guide, since you're s-offed you *should* (not positive about this) be able to skip basically everything, grab the rom from RUU and flash it via hboot and you should be fine.
Click to expand...
Click to collapse
So what is it I have actually done? I don't have clockwork mod installed so can i flash the RUU as normal?
JD

gtrab said:
dont worry mate we will find a way,
I'm searching G2 fora right now, will report
Click to expand...
Click to collapse
Your a diamond mate
Im not sure how to play it from here:/
JD

JupiterDroid said:
Guys i think i may have bricked my Z
...
But now i get lots and lots of force closes when sense boots,
Click to expand...
Click to collapse
I just remembered THIS SAME SHIZZ ALREADY HAPPENED TO ME
You are NOT bricked, just getting a lotof annoying FORCE CLOSE messages, ain't ???
If so, then this is what I did:
1.- remove the battery 30 secs
2.- hold vol down + power
3.- in bootlader, select "FACTORY RESET" (use vol keys to up-down)
Then my phone rebooted and everything was back to normal

gtrab said:
I just remembered THIS SAME SHIZZ ALREADY HAPPENED TO ME
You are NOT bricked, just getting a lotof annoying FORCE CLOSE messages, ain't ???
If so, then this is what I did:
1.- remove the battery 30 secs
2.- hold vol down + power
3.- in bootlader, select "FACTORY RESET" (use vol keys to up-down)
Then my phone rebooted and everything was back to normal
Click to expand...
Click to collapse
cool mate, so the accidental flashing of the OTA after the z.ko is not going to hurt anything?
JD

JupiterDroid said:
cool mate, so the accidental flashing of the OTA after the z.ko is not going to hurt anything?
JD
Click to expand...
Click to collapse
just do it
what else could go worst ??
when your phone turns stable, connect to PC and push wpthis-Z.ko again

gtrab said:
just do it
what else could go worst ??
when your phone turns stable, connect to PC and push wpthis-Z.ko again
Click to expand...
Click to collapse
Very true, will do that mate
Really appriciate your help
JD

Hi Friend,
I just had similar problem as you.
I rooted phone, flashed hboot s-off and..?
..first my Z was restarting in loop every 2-3 minutes.
I uninstalled VISIONARY+ and apps that force closed every boot.
But still there were many problems with my phone.
I couldn't install many apps from market,
and random ones just disappeared every reboot.
It wasn't nice.
Then I used Clockwork recovery, did clear cache, full wipe,
and the phone is in perfect condition, s-off, with clock-recovery,
after wipe my apps has been restored - including SuperUser,
and its rooted already, after wipe
No need to use VISIONARY+ again!
Try it
br,
condi

[Q] n00b bricks glacier with Rom Manager

So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?

lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899

Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App

Also, you need to flash CW at least twice for it to take.

CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.

lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
First thing's first. Pull the battery for about a minute. Reinstall it then plug in the phone but don't try to boot. If the orange light comes on that's good. If not you might be in trouble but all hope is not lost yet.
krohnjw said:
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899
Click to expand...
Click to collapse
This is your best bet. Re-image it completely and start over, this time READ THE ENTIRE TUTORIAL BEFORE TOUCHING IT!!
jjjackson56 said:
Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ADB probably won't be much help since he's not perm-rooted; it won't let him do anything. Just re-image the sucker.
CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
In order to perform a nandroid backup you need:
1. Perm root, NOT temp root, PERM ROOT.
2. S-OFF so you can successfully flash clockwork recovery.
Not trying to be harsh just want to be perfectly clear.
TeeJay3800 said:
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.
Click to expand...
Click to collapse
Yup.

Possible Brick I Dunno what I did

So I'm fairly new to rooting but I have had android since the day it came out and I am good with the system. I have a g2 running a root of Visionary. I wanted to install a custom rom, so i was in Rom manager and i flashed in Clockwork Recovery, that went fine, and then i clicked back up current rom. I changed the name to original Rom, then the phone went blank then it had a g2 with a red triangle with an exclamation point in it. Does that mean the phone was bricked or what mode was that in? I pulled the battery and powered the phone on while holding the volume down. I think clicked the recovery option and the phone produced the same black screen with a G2 with a red triangle with an exclamation point in it. I then pulled the battery again, powered it up with the volume down button and did a factory reset and now my phone is back to how it was out the box running regular software.
Any idea what I did wrong? Or what went wrong? I would like to throw visionary back on and do a temp root and throw in a custom rom. My end goal is to do it once and have the phone run flawlessly and fast and never mess with any settings again. Help please!

Just for your information use the root method in wiki thats on this forum its easy. I think the visionary is outdated.
Sent from my HTC Vision using XDA App.

jjp023 said:
red triangle with an exclamation point in it.
Click to expand...
Click to collapse
The red triangle is the pre-screen to the stock recovery. At that screen if you press Vol + and Power (IIRC), it will take you to the recovery. I am not sure why you got this screen if you flashed clockwork recovery from ROM manager.
If the phone is not properly rooted, it probably cannot flash a custom recovery. Make sure you follow the instructions for rooting via Gfree in the wiki.

you are just soft rooted you will need to go through the root through adb

jjp023 said:
So I'm fairly new to rooting but I have had android since the day it came out and I am good with the system. I have a g2 running a root of Visionary. I wanted to install a custom rom, so i was in Rom manager and i flashed in Clockwork Recovery, that went fine, and then i clicked back up current rom. I changed the name to original Rom, then the phone went blank then it had a g2 with a red triangle with an exclamation point in it. Does that mean the phone was bricked or what mode was that in? I pulled the battery and powered the phone on while holding the volume down. I think clicked the recovery option and the phone produced the same black screen with a G2 with a red triangle with an exclamation point in it. I then pulled the battery again, powered it up with the volume down button and did a factory reset and now my phone is back to how it was out the box running regular software.
Any idea what I did wrong? Or what went wrong? I would like to throw visionary back on and do a temp root and throw in a custom rom. My end goal is to do it once and have the phone run flawlessly and fast and never mess with any settings again. Help please!
Click to expand...
Click to collapse
You can't load a custom recovery with only temp root (I'm guessing that's all you had). What you saw was the stock recovery (so your phone was actually fine and you didn't have to factory reset). If you want to load a custom ROM, you will need to follow one of the permanent root guides first (use the wiki or I just wrote another guide if you can't get ADB working). If you did have permanent root (check for S-OFF in the bootloader), try flashing the ClockworkMod recovery again (sometimes it doesn't take the first time).

ianmcquinn said:
You can't load a custom recovery with only temp root (I'm guessing that's all you had). What you saw was the stock recovery (so your phone was actually fine and you didn't have to factory reset). If you want to load a custom ROM, you will need to follow one of the permanent root guides first (use the wiki or I just wrote another guide if you can't get ADB working). If you did have permanent root (check for S-OFF in the bootloader), try flashing the ClockworkMod recovery again (sometimes it doesn't take the first time).
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
Thanks for the help, I appreciate the quick responses. I hade visionary. I temp rooted it and then perm rooted by jus clicking the perm root on visionary. Not sure if that would do the same. I dnt think I have the confidence yet to perm room through terminal and writing scripts. what way would u suggest to perm room and What roms would u suggest that are relativly novice leve and provide signifcant improvement

jjp023 said:
Sent from my T-Mobile G2 using XDA App
Thanks for the help, I appreciate the quick responses. I hade visionary. I temp rooted it and then perm rooted by jus clicking the perm root on visionary. Not sure if that would do the same. I dnt think I have the confidence yet to perm room through terminal and writing scripts. what way would u suggest to perm room and What roms would u suggest that are relativly novice leve and provide signifcant improvement
Click to expand...
Click to collapse
Not positive how Visionary attempts to permroot, but you should check to see if you have it. Hold the volume down while powering on to enter the bootloader. The first line will say S-OFF if you have root and S-ON if you don't. If you have S-OFF, go ahead and try to flash the ClockworkMod recovery again (it just may not have worked that first time). If you have S-ON, or still have problems flashing the recovery, you can use either of the guides I linked to in the earlier post (you don't have to write scripts, but will need to use terminal---just follow the instructions carefully and watch for typos).
As far as ROMs, once rooted, you can try any of them really easily to see what you like best (be sure to make a backup first and you can always revert back). They are all pretty friendly to use right out of the box.

My phone is back to stock so I can't check lol. The link you posted titled guide seems pretty user friendly. I will attempt that root tnite... I will not do the h boot bc I dnt want more risk of a brick. Once I root I will flash clockworkrecovery. So in rom manager i should flash clockworkrecovery then scroll down to the bottom of it and backup current rom.how can I confirm its backed up? And once it is backed up I am clear to install new roms correct
Sent from my T-Mobile G2 using XDA App

If you were already S-OFF, doing the factory reset shouldn't return you to S-ON, so you could still check if you wanted to.
As far as backing up goes, once you choose backup in ROM Manager, your phone will boot into the custom recovery and you'll actually see all of the files getting backed up (there's also a progress bar). The backups are stored on your SD card in the clockworkmod directory (if you want to check to make sure it's there). After you have the backup, you're free to start testing new ROMs.

ianmcquinn said:
If you were already S-OFF, doing the factory reset shouldn't return you to S-ON, so you could still check if you wanted to.
As far as backing up goes, once you choose backup in ROM Manager, your phone will boot into the custom recovery and you'll actually see all of the files getting backed up (there's also a progress bar). The backups are stored on your SD card in the clockworkmod directory (if you want to check to make sure it's there). After you have the backup, you're free to start testing new ROMs.
Click to expand...
Click to collapse
So jus confirmed s on... so I will root using the guide u provided tnite.. few more questions jus to be safe I dnt wanna be a annoying but I appreciate the help...
1. Once rooted and in rom manager I should first flash clockworkrecovery then click back up current rom?
2.if I get back to the g2 with red triangle screen I should clikc power and volume down and which option should I choose at that screen?
Sent from my T-Mobile G2 using XDA App

jjp023 said:
1. Once rooted and in rom manager I should first flash clockworkrecovery then click back up current rom?
Click to expand...
Click to collapse
Yup.
jjp023 said:
2.if I get back to the g2 with red triangle screen I should clikc power and volume down and which option should I choose at that screen?
Click to expand...
Click to collapse
This just means the ClockworkMod recovery did not flash properly (and you are seeing the stock recovery). Just boot the phone normally and try flashing the recovery again in ROM Manager. If that doesn't work, there are other options we can try, but it should work fine once you are actually permrooted.

Sounds good. I'm trying to prepare myself to do this root later tnite.
I want to make sure I get the command right in terminal.
After the money sign and number signs there are spaces correct?
So my keystrokes shoule be (I dnt press $ or #)
$(space)su(enter)
#(space)cp(space)/sdcard/root_files/perm_root/data/local/perm_root(enter)
#(space)chmod(space)777(space)/data/local/*(enter)
#(space)/data/local/perm_root(enter)
Sent from my T-Mobile G2 using XDA App

You don't need to type the space at the start of the commands (they will already be there). Also you are missing a space in the second line:
cp(space)/sdcard/root_files/perm_root(space)/data/local/perm_root(enter)
Otherwise, looks good.

I know exactly what you're talking about with the triangle and red exclamation mark. Happened to me when i first flashed clockwork mod (CWM). What fixed it for me was to flash it TWICE when using Rom Manager. The first time you try to flash it, it doesn't always work, so you just reboot as normal (not into recovery) and flash CWM again and it should fix it.
Sent from my HTC Vision using XDA App

What's the use of roms now if recovery is flaky?

I know they are two different things that one relies on the other to work. I understand that rom devs are usually different people than those working on the recovery program.

You gotta start somewhere...

2.5.x.x recovery in the root thread works enough that you can flash roms with no issues.

I don't know if there's a new version of recovery yet. What I meant by flakiness was the issue that some were having, including me, that the phone would always boot into recovery if it was off and you were trying to charge it.

herbthehammer said:
I don't know if there's a new version of recovery yet. What I meant by flakiness was the issue that some were having, including me, that the phone would always boot into recovery if it was off and you were trying to charge it.
Click to expand...
Click to collapse
That's a known issue with ALL clockwork recoveries and there probably will NEVER be a fix.

This may be the case but since the evo and epic used cwm recovery, the shift is the first phone I've experienced this snafu with. Maybe I was just lucky in the past. And yeah, I'm impatient for it to be fixed. I gotta chill out.

Why are you charging with the phone powered off anyway?

Compusmurf said:
Why are you charging with the phone powered off anyway?
Click to expand...
Click to collapse
because bump charging makes unicorn for reals

Compusmurf said:
Why are you charging with the phone powered off anyway?
Click to expand...
Click to collapse
It charges about 10 times quicker.

cloverdale said:
It charges about 10 times quicker.
Click to expand...
Click to collapse
Definitely

So is this recovery causing all the issues that are happening after root? Like the heating up/lag/low quadrant scores?
I'd like to root just to be able to remove things and use wireless tether, but honestly the phone works fine for me right now.

Recovery
You don't actually need to flash the CWM 3.0 recovery. I too like to charge my phone while it's turned off, and after reading about that bug, I just set up my phone to fastboot boot the CWM from preludedrew. What that does is it loads the new custom recovery, but without over-writing the original. From there you can follow the directions to install the custom ROM.
I'm running Evervolv, and so far it seems to be pretty great. Of course you don't get 4G and the camera is buggy still, but you can take pictures and the wifi actually goes faster now.

Then what's the best rom and recovery out for the shift?
Sent from my HTC Vision using XDA App

Quick question guys, since were on the topic of recovery idk if this is the correct "recovery" or not, I came from the evo so its not much different for me but when I did a nandroid backup for my evo I would select backup/restore and select backup google proprietary system files or something like that, I don't get that option with my shift, I just get backup, is that the same?

Compusmurf said:
That's a known issue with ALL clockwork recoveries and there probably will NEVER be a fix.
Click to expand...
Click to collapse
This is not the case with my EVO 4G. I can charge the phone when it's off without the recovery booting up. This is the case with CWM 3.0/2.6.X.X

Where can I download the recovery for the shift?
Sent from my HTC Vision using XDA App

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic

syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App

Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??

Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App

OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App

syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!

syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.

last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.

You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???

Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.

lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.

Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.

lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!

And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?

syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App

OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!