Database Users

**Rooted Phones*** Reset back to First Time Root

Ok apparently in my futile attempts to OC the Pure Hero 1.0 Rom I've totaly got something hosed up. The phone works but features that others have working flake out on me. Is there a way to wipe fully the whole thing and reset back to the rooted 2.1 Rom as we did before the Recovery image.
If it is as simple as just flashing the original developers Rom please don't flame me..I did search.
I do a factory wipe then Dalvik Wipe then Ext Partition wipe before flashing an image.
I currently can't get Wifi to work on Punk.Kaos Rom nor on the Pure Hero (I think that was an issues though)..
Thanks for all the hard work you guys do....

copy a rom you want to use to your sdcard. then go into recovery, wipe the phone, then flash zip from sdcard. done!

That is what I have been doing and some of the settings are still flaking out and the Kaos rom is V15 he fixed wifi in v2. I can't even get Jamezelle's sensable rom to even flash with out a boot loop at animation.
Thanks for the help.

No nandroid backup?? I know before flashing the first Rom on the phone I made a nandroid back up on my wifes and pretty much do everytime before flashing a new rom. These things are priceless

Follow the the original root procedure.

*Suggestion*, when phone boots.... open setcpu and adjust the CPU OC setting.... maybe...

id say go to the downgrade to 1.5 from 2.1 root thread and do that and then re upgrade and reinstall the recovery image.

I agree with doing a full downgrade to 1.5 and rooting again. I had problems similar to yours and this solved the problem. Good luck.
-------------------------------------
Sent via the XDA Tapatalk App

Thanks I just wanted to confirm that should be the process of going to 1.5 thne to 2.1 and restoring the Recovery. One last question and then a Mod can close this thread. The Rom Manager in the Market will that work for us or is that a Droid only thing?
Thanks for the great advice.
Forgot to answer the nandroid backup yes did it before every new flash of a Rom they would come back weird also. Secondly how do I get my SD card back to full Fat32 and not the ext+Fat partition for A2SD mode? I never could get the A2SD to work fully.

A2SD with damagecontrol Rom

A little over a month ago I flashed the damagecontrol ROM and haven't looked back. Aside from having 2.1 early, I was also able to access su features, blah blah blah. My question is: I am still losing internal memory even after enabling A2SD, partitioning my SD card into three sections (ext3, swap, and probably fat32 or something). I noticed a gain of about 40mb right away but each time I download a program my internal memory shrinks. Any ideas? I'm not a pro at this but really wanting to learn.
-------------------------------------
Sent via the XDA Tapatalk App

joshuaharp said:
A little over a month ago I flashed the damagecontrol ROM and haven't looked back. Aside from having 2.1 early, I was also able to access su features, blah blah blah. My question is: I am still losing internal memory even after enabling A2SD, partitioning my SD card into three sections (ext3, swap, and probably fat32 or something). I noticed a gain of about 40mb right away but each time I download a program my internal memory shrinks. Any ideas? I'm not a pro at this but really wanting to learn.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Even with A2SD there are still files that get written to internal storage for cacheing. You will see your memory go down.

Ah. I didn't realize that. Are there other ways to free up the internal memory? I'm down to around 25mb...
-------------------------------------
Sent via the XDA Tapatalk App

If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.

the same thing is going on with my phone i only see an added 40mb onto the internal storage when i put on a2sd,when i hear about other kids that get around 90mb when using a2sd.

willowmp said:
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
Click to expand...
Click to collapse
I just threw a 4GB Class 6 in and partitioned it. Before that I was running the stock 2GB (Class 2 I think). I've been considering a few options but not sure what the process should be and how to proceed:
- dalvik cache to sd
- jit compiling (alhtough, I've almost completely ruled this out due to rumors of instability issues)
- swapping sd (I'm not sure if this will have ill-effects on my system or not)
I would feel at more liberty to experiment if I knew what to do if my phone ran into an error that crippled it (i.e., stuck in boot loop). I'm really fresh to this, so it's a bit intimidating at first.

joshuaharp said:
I would feel at more liberty to experiment if I knew what to do if my phone ran into an error that crippled it (i.e., stuck in boot loop). I'm really fresh to this, so it's a bit intimidating at first.
Click to expand...
Click to collapse
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...

willowmp said:
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
Click to expand...
Click to collapse
This kernel (.29 kernel, right?) is one I've been recently considering. I've made a nandroid backup through ROM Manager (is this as good as RA-Amon's recovery?). I'm not sure what to do with this should something go wrong...unless I can boot up and have access to the ROM Manager app – I'll cross that bridge when I come to it. Some questions:
concerning flashing a recovery
- what exactly does this do? (as I understand it, it writes a recovery file to my sd card, so that i can boot up in recovery mode should something cause my os to fail...is this correct?)
concerning the godmode overclocked kernel
- how long have you had this flashed on your phone?
- can I flash over my current ROM (damagecontrol 2.08.1)?
- will I lose info and have to wipe everything not on my SD card?
- I've partitioned my sd card for A2SD, will this cause problems?
- how long is your battery life on average?
Thanks dude.

willowmp said:
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
Click to expand...
Click to collapse
What did you set your swap and ext on when you partitioned your sd

xxxk15 said:
What did you set your swap and ext on when you partitioned your sd
Click to expand...
Click to collapse
ext: 1024 (or whatever the first 1gig choice is, I believe it is something like this)
swap: 30 (I believe, or whatever it automatically pops up as when formatting)
Through Dconfig I have apps2sd, dalvik to sd, and sd swapping with the default 30mb enabled.
Dalvik heap is set to 16mb and lowmemkiller set to less. JIT not enabled.
Current version DamageControl, the 768 overclocked kernel and toast's newest radio.

joshuaharp said:
This kernel (.29 kernel, right?) is one I've been recently considering. I've made a nandroid backup through ROM Manager (is this as good as RA-Amon's recovery?). I'm not sure what to do with this should something go wrong...unless I can boot up and have access to the ROM Manager app – I'll cross that bridge when I come to it. Some questions:
concerning flashing a recovery
- what exactly does this do? (as I understand it, it writes a recovery file to my sd card, so that i can boot up in recovery mode should something cause my os to fail...is this correct?)
concerning the godmode overclocked kernel
- how long have you had this flashed on your phone?
- can I flash over my current ROM (damagecontrol 2.08.1)?
- will I lose info and have to wipe everything not on my SD card?
- I've partitioned my sd card for A2SD, will this cause problems?
- how long is your battery life on average?
Thanks dude.
Click to expand...
Click to collapse
RA-Amon's custom recovery is a must and is vastly more important than a back-up app. RA-Amon's recovery is an actual recovery image, thus as long as your phone boots up to the HTC logo you should be able to access RA-Amon's recovery and thus restore the backup before the phone is even accessing the rom.
Flashing a recovery image is like flashing a rom, but instead of a rom you are flashing a recovery image. Your phone has a stock recovery image on it right now, I don't know the key combo but hold a certain pattern of keys down while turning the phone on and you will enter it. It looks I think like a triangle with an ! in the middle or something. This is sorta useless for us though because I don't think you can really do much with it.
When you flash a recovery img (RA-Amon's) that stock recovery image is just replaced with Amon's. After you do flash the recovery holding the HOME and power button to turn the phone on and continuing to hold it will cause you to enter Amon's recovery, which is a green menu. From this menu you can amke backups/restore them, wipe the data on the phone (factory reset), flash .zips (roms, bootscreens, themes, kernels) and other things.
What you are referring to the writing backup to sd card is called nandroid. Nandroid is an option in the recovery, so yes if you do flash the wrong rom or your phone won't boot up (boot loop or whatever) as long as you can access recovery which is one of the first things loaded when you hit the power button (unless you really do something spectacular like flashing a gsm hero's radio you almost always will be able to get into recovery. don't even touch radios right now, flash the wrong one and your phone won't even turn on/charge. aka your motherboard will be totaled) so you will almost always be able to nandroid recovery your os if something does go wrong.
In short before you do anything flash the recovery.
Now on to your other questions. I have been running the overclocked kernel for one day, but it appears stable and seems to be working good for me. When you flash a kernel you always flash it over a rom, because if you do it the other way the rom will replace the kernel. So yes once you have damagecontrol or another rom that supports that kernel you can simply go into recovery and use flash .zip to flash the kernel over the rom. As always make sure to make a nandroid before doing so.
DamageControl supports apps2sd, and you enable it to use a2sd using the Dconfig app that is included in the rom. It is generally a good idea to partition your sd card whenever you switch between roms unless they say it is fine. You should go ahead and copy over a backup of your sd card to your computer, however you need not format or wipe your sd card when flashing roms. Honestly I don't think you need to partition your sd card again, unless after you flash the rom the os won't boot up all the way or loops/crashes. If it does then partition the sd card and try rebooting the phone and it should fix it.
Also you can format and partition your sd card in recovery under Other.
As for my battery life I have been switching b/w roms and such and I just started using the OC kernel, but with the DamageControl rom back when I only had that flashed my batt life was good.
However I do have 3 batteries and an external battery charger for my phone. Check out the accessories section of this forum, 2 batteries and the charger for 11 bucks from Hong Kong on ebay.
Hope I helped.

So, through the damagecontrol dconfig app I banned "sense", rebooted and now my phone is stuck in a bootloop. Do I restore from previous nandroid backup or do I need to flash my phone? Suck.

joshuaharp said:
So, through the damagecontrol dconfig app I banned "sense", rebooted and now my phone is stuck in a bootloop. Do I restore from previous nandroid backup or do I need to flash my phone? Suck.
Click to expand...
Click to collapse
Just want to say first off: "I am an idiot". Nandroid backup from 5 days ago, booted up by holding *home and *power, then selecting to restore. Very easy. I can actually breathe now. Back in business. Sorry to waste your guy's time. We can keep the thread going minus my drama...

joshuaharp said:
Just want to say first off: "I am an idiot". Nandroid backup from 5 days ago, booted up by holding *home and *power, then selecting to restore. Very easy. I can actually breathe now. Back in business. Sorry to waste your guy's time. We can keep the thread going minus my drama...
Click to expand...
Click to collapse
It's all good.
See why I emphasized flashing your recovery before messing with anything? xD

xxxk15 said:
What did you set your swap and ext on when you partitioned your sd
Click to expand...
Click to collapse
I set the swap to 32mb and ext3 to 512mb I believe...does this sound right?

willowmp said:
RA-Amon's custom recovery is a must and is vastly more important than a back-up app. RA-Amon's recovery is an actual recovery image, thus as long as your phone boots up to the HTC logo you should be able to access RA-Amon's recovery and thus restore the backup before the phone is even accessing the rom.
Flashing a recovery image is like flashing a rom, but instead of a rom you are flashing a recovery image. Your phone has a stock recovery image on it right now, I don't know the key combo but hold a certain pattern of keys down while turning the phone on and you will enter it. It looks I think like a triangle with an ! in the middle or something. This is sorta useless for us though because I don't think you can really do much with it.
When you flash a recovery img (RA-Amon's) that stock recovery image is just replaced with Amon's. After you do flash the recovery holding the HOME and power button to turn the phone on and continuing to hold it will cause you to enter Amon's recovery, which is a green menu. From this menu you can amke backups/restore them, wipe the data on the phone (factory reset), flash .zips (roms, bootscreens, themes, kernels) and other things.
What you are referring to the writing backup to sd card is called nandroid. Nandroid is an option in the recovery, so yes if you do flash the wrong rom or your phone won't boot up (boot loop or whatever) as long as you can access recovery which is one of the first things loaded when you hit the power button (unless you really do something spectacular like flashing a gsm hero's radio you almost always will be able to get into recovery. don't even touch radios right now, flash the wrong one and your phone won't even turn on/charge. aka your motherboard will be totaled) so you will almost always be able to nandroid recovery your os if something does go wrong.
In short before you do anything flash the recovery.
Now on to your other questions. I have been running the overclocked kernel for one day, but it appears stable and seems to be working good for me. When you flash a kernel you always flash it over a rom, because if you do it the other way the rom will replace the kernel. So yes once you have damagecontrol or another rom that supports that kernel you can simply go into recovery and use flash .zip to flash the kernel over the rom. As always make sure to make a nandroid before doing so.
DamageControl supports apps2sd, and you enable it to use a2sd using the Dconfig app that is included in the rom. It is generally a good idea to partition your sd card whenever you switch between roms unless they say it is fine. You should go ahead and copy over a backup of your sd card to your computer, however you need not format or wipe your sd card when flashing roms. Honestly I don't think you need to partition your sd card again, unless after you flash the rom the os won't boot up all the way or loops/crashes. If it does then partition the sd card and try rebooting the phone and it should fix it.
Also you can format and partition your sd card in recovery under Other.
As for my battery life I have been switching b/w roms and such and I just started using the OC kernel, but with the DamageControl rom back when I only had that flashed my batt life was good.
However I do have 3 batteries and an external battery charger for my phone. Check out the accessories section of this forum, 2 batteries and the charger for 11 bucks from Hong Kong on ebay.
Hope I helped.
Click to expand...
Click to collapse
Dude...helped IMMENSELY! I'm still digesting it.
That's good to know about flashing radios. I was going to flash the most recent one for 2.1 roms on CDMA heros, but I think I'll wait to hear more about it.
I think I feel comfortable flashing the .29 kernel over my current ROM. I gotta be honest though, the DConfig thing kind of weirds me out now, after trying to use it. I'm not sure which button is going to cause my phone to freak out.

If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
Click to expand...
Click to collapse
I'm considering doing this but have read that this causes issues with nandroid backup. Have you experienced this?
-------------------------------------
Sent via the XDA Tapatalk App

Openfire ROM Problem

Apologies for the double post but I'm dying to get my wildfire back working.
Rooted it yesterday with unrevoked, attempted to add the Openfire ROM this morning with everything going fine untill the reboot. I'm now stuck on the white HTC screen and have been for the last hour. Any help would be great, cheers.

did u do nandriod back up first
Sent from my Archos5 using the XDA mobile application powered by Tapatalk

I backed up the stock firmware I already had manually, before it prompted on the flash.

did you do a full wipe before flashing the rom?

No i didn't, thought it would be safer incase something went wrong?

run your restore then I couldn't get it to work either
Sent from my Archos5 using the XDA mobile application powered by Tapatalk

if you did a nandroid backup of your stock rom then you should be fine to wipe, since you did not wipe and flashed the new rom over your stock rom, apps and settings will conflict, therefore not work...

Right I see, I'm currently going through what I'm guessing is the restore....recovery - Nandroid, I'll let you know how I get on.
Thanks again.

Nope I seem to be getting nowhere here, can someone point me in the direction of the restore?

you didn't do nandroid backup did you haha, you'll have to install an RUU file to return to stock rom, or just do a full wipe and flash a new rom like openfire or wildpuzzle.

Where can I find the RUU file and how do I access my SD card? USB won't let me get to it, I'm guessing the phone is in charge mode?

go into recovery - partitons menu - mount sd card (or somthing like that) to open your memory card

Spot on, I'm on downloading an ruu file now, going to load it up with a stock rom then try flashing it again, but wiping it this time.

Infact how do I do a full wipe? I'm after the easiest way to get the phone booting up so I can flash it properly?

Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.

go into clockwork recovery and click the title "wipe data/factory reset" and then flash the ROM you want to use.. to install a ROM:
- "install zip from sdcard"
- "Choose zip from sdcard"
- "click the zipfile"
- "yes"
- "reboot"
and if you want to install RUU dont ask me never done that

Reggie24 said:
Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.
Click to expand...
Click to collapse
How did u restored it .....????

sunny_16977 said:
How did u restored it .....????
Click to expand...
Click to collapse
From the HBOOT screen go to recovery, then nandroid, restore, and to the appropriate time/date.
I've still had no luck with actually flashing the phone though. Back to Android 2.1 for me.

I'm 99% percent sure you have the OC issue some ppl incl myself on here have - try reinstalling openfire if thats what you wanna use - and then go to wildpuzzle thread - dl 0050 and flash it. If i'm correct phone will be fine and use openfire - but will NOT be overclockable. I wish Jacob had my phone or got hold of a phone w that problem...

I had problems with the Wildpuzzle 8.0.11 ROM, it would just sit there (did a ADB logcat on it, but I've lost the actual log... sorry! ) ignoring a duplicate entry (yeah, I did a full wipe . Removed WP and put on the latest OpenFire ROM... omg... what a difference to the stock ROM! Soooo much faster, even before I overclocked it.
I'd say, if you have boot issues with WP give OpenFire a go. Certainly worked a treat on my Wildfire.

[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!

ClockWorkMod Recovery Problem

Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!

fixed it
I unplugged the battery and did a factory reset/format in ClockWorkMod. I rebooted and all seems well so far.

20 minutes is a looong time for Cyclonic to boot. Is it still working ok? As far as CW goes, I only use Rom Manager to downlod what I want/need. When it comes to flashing I wipe everything manually and flash from recovery. I don't trust the app. But thats me.
Sent from my PG06100 using xda premium

+1 to that. I always use the same Method for Flashing Roms ( The one linked in my Sig ) . Clear everything Manually. I try to never deviate from that. Reason being, after Flashing literally hundreds of times I've found it to be the most reliable way to Flash a Rom. Meaning the least amount of possibilities for issues later on down the road .

alarmpro said:
Hi, I used the paid version of ClockWorkMod Recovery to backup, then download the 'Cyclonic Rom'. Well, it rebooted to a 'Cyclonic Rom' startup screen (animated lettering) - but that's it. I'm wary to unplug the battery if it's actually flashing, but this has been going on for 20 minutes or more. Can I pull the battery and see what happens? How long does a new ROM take to install, this is my first one. Thanks.
BTW: These CAPTHCA's are getting tough! This will be the 4th try!
Click to expand...
Click to collapse
Flash newsense.
And don't forget to wipe dalvik.

I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.

jdjohn said:
I have been searching (as in using the 'search' function) for a solution or answer to this, but couldn't find anything. This seemed to be the best thread to dig up instead of starting a new one.
Within Clockworkmod, whenever I try to go into recovery (either trying to 'reboot into recovery' or installing a ROM from SD card), it always throws me into Android System Recovery 3e instead of CWM recovery. Of course the stock recovery doesn't recognize my downloaded ROM.
I've also noticed that trying to update a ROM in HBOOT via a new PG06IMG.zip file on SD root is not working, except to wipe all my system and apps data, and then returning me back to rooted 2.2. HBOOT seems to read the new zip file fine, but when I reboot nothing has changed.
I've read wiki and lots of other stuff, but I can't seem to find an answer except that MAYBE that I need a new kernel first??? Okay, let the flaming begin.
Click to expand...
Click to collapse
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.

Did you get this sorted?

bilgerryan said:
You need to flash recovery first, it is the first option in ROM Manager. You can't update a ROM with PG06IMG.zip, nor can you do it in the bootloader. Flash the recovery, wipe everything (data, cache, dalvik cache, system, sd-ext) then flash a ROM.
Click to expand...
Click to collapse
Chad The Pathfinder said:
Did you get this sorted?
Click to expand...
Click to collapse
No, still having trouble. I have flashed ClockworkMod Recovery (version 5.0.2.0) in the ROM Manager app, but when I 'reboot into recovery' within the app, it goes to the Android System Recovery. I'm also confused about the 'apply sdcard:update.zip' option in ASR...seems like that would update something if the file was set up properly.
I guess I need to search for a tutorial on how ASR and HBOOT work. Sorry to bother you guys with the basics.

Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531

bilgerryan said:
Try this onehttp://forum.xda-developers.com/showthread.php?t=1663531
Click to expand...
Click to collapse
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!

The only thing I use Rom Manager for is to get the recovery. The way I go into recovery is to turn my shift completely off (do a battery pull to make sure its completely off) then hold the volume down and power buttons at the same time until the bootloader screen comes on. (While there see if it says S-off near the top) then using the volume buttons highlight the recovery option and push the power button. Then when you're there use the volume buttons to navigate through the various fields and hit enter to select. I hope this is helpful to you. Good luck!
Edit: by the way, when you first get to the bootloader screen, it will automaticly do a check showing a few green lines. Thats ok. Just wait until its finnished then go into recovery the way I stated.

jdjohn said:
Will check it out, thanks! I'm leaving town today, so not sure if I will be able to experiment before I go, but I will not give up!
Click to expand...
Click to collapse
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium

CNexus said:
How did you root? It seems as if you have a locked bootloader and/or S-ON if the custom recovery is not taking
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.

jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.

bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Was thinking that myself. Will have to wait til I get back, though...headed out of town. Thanks guys!

jdjohn said:
From bootloader screen:
Speedy XE Eng S-OFF
Hboot-0.93.2011 (PG0610000)
Radio-1.08.01.0111
eMMC-boot
Nov 15 2010, 13:16:46
I haven't tried Dread's CW-Enhanced yet. I just don't understand why the standard CWM recovery from ROM Manager doesn't work. I'm probably missing something obvious.
Click to expand...
Click to collapse
Hmm, never mind then, it seemed as if your bootloader was still locked if the recovery wouldnt flash
bilgerryan said:
Just flash Dread's in bootloader, make sure it is named PG06IMG.zip (that is a zero) and place on the root of your SD and go back into the bootloader and hit update when it tells you to.
Click to expand...
Click to collapse
Yeah, just do what bilgerryan said (make sure that you download the one that says "flash through bootloader" or something along those lines)
Before flashing, download some md5sum tool and make sure it matches the one given on there
Sent from my PG06100 using xda premium

Finally got back to this and was able to install and use Dread's CW-Enhanced. So far I have only flashed the Speedy Rooted OTA 2.77.651.8 (bascially 2.3.4 rooted). GB had some features I was wanting, but missing, after rooting back to Froyo.
But before continuing on to other ROMs, I was wondering how you guys handle restoring basic apps and data each time you flash a new ROM. Or, do you only use extra play phones for new ROMs and not your daily user? It would seem that every time you flash, you need to restore SuperUser, Titanium, ROM Manager (ClockworkMod, then probably Dread's enhanced image file), Terminal Emulator, etc. And of course contacts and messaging history and other stuff like that.
So far, after flashing a ROM, I usually download Titanium (or MyBackup) and restore apps and data from backups before continuing. Do you just keep certain APK files on your SD card and install from ADB instead of re-downloading from Google Play Store each time?

I flash ROMs on my dd. Usually when I falsh a new ROM (not a nandroid) I fresh install my apps through the play store. Especially if switching between GB, ICS and JB! Some apps work well if carried over by tb but not all. You'll just have to experiment to see what works with your shift and what doesn't.

Also, the recovery only ever needs to be flashed once
What I used to do is backup my current rom with all my data and settings and then wipe + flash a new rom. If i liked it, then I would move my full box of apps and data to the new rom, but restoring data can go wonky so I always made a backup before doing that too. If i didnt like it, I would either restore my original backup for a bit or keep flashing new roms until I either found one I liked or got tired and restored my backup lol