Database Users

On a subject totally unrelated to anything else going on:

Damn near burst a vessel earlier, doods. I had downloaded the newest darchdroid, and was looking forward to some oc'd, jit-enabled, vanilla goodness. I booted into recovery, wiped everything, and tried to install. Ut oh! Got a bad download. No es bueno. But, imma careful sob, so I have like 4 nandroids sitting on my SD....2 from flipz' latest betas, 1 from the original fresh toast, and one from dc 2.0.8. And it was a damned good thing, too! The backups off the newest would NOT boot. They kept looping. I tried rewiping, nothing. No good. Finally, I tried one of the other nandroids, and It worked first try. Because I'm a curious person, I then immediately booted to recovery and tried my most recent nandroid (the first one that bootlooped). This time it worked like a charm. Consider this evidence that having more than one nandroid in storage is never a bad idea. Anyone with a clue about what might have happened, and why the nandroid wouldn't work...until suddenly it did?

dood, Nandroids are for pansies.

Maybe it has a bad temper, too.
-------------------------------------
Sent from your mom!

@Kcarpenter- Well, paint me pink and stick me in a pot! (i was gonna make a joke about your wife and my root, but in this current climate, it prolly would have gotten me banned for being off topic in my own thread)
@jerry- you're prolly right. I know it has my sense of humor, cause it keeps effing with me when I'm drunk....

Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo

phenicks said:
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
Click to expand...
Click to collapse
Na. I had a totally bad download. It never even finished installing. I'll try it again this afternoon, when I'm near a computer.

I am not sure if this will help, but I had a loop problem and I noticed it started when I installed an app. This was in my nandroid back up. If you boot, it will go into loop.
Through adb start removing programs in the /system/app/. I ended up removing the program (apk and/or odex) and it stopped the loop without rebooting. Not sure why it did this.
Once you find the program that may cause this, restore your nandroid and only remove that apk or odex.
Just try it and see if this works.

you should wipe and clear data before nandroiding back. probably why you had a boot loop. With recovery theres no reason why you cant take 5 seconds and wipe everything before nandroid. If you did do a wipe and clear data before hand then my sincere apologies.

Yeah, I rewiped MULTIPLE times (each time I tried to nandroid recover, so, like, 6 times or so). Thanks, though.

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

[Q] Error formatting /data!

Self-dangerous noob here. NC 1.2, theoretically returned to stock
History:
Got NC 1.2
Rooted w/ManualNooter 4.5.25. Everything seemed to go great. So...
Downloaded, backed up, and flashed CM7 in ROM Manager
Wouldn't boot...hung on n COLOR screen
Same results w/ Phirerom (CM7 based - doh)
Able to restore MN4.5.25 from CWM - BUT noticed "Error formatting /data!" during nandroid restore. Didn't seem to matter...restore successful
Get "Error formatting /data!" no matter what
Able to boot into CM7 from SD, but it has "problems". For instance, there are no "back" or "return" softkeys. So there is no way to navigate around any app! Only the hard "n" home key works
Reflashed stock 1.2
Seemed to work, began to ask me to reregister. BUT, it won't display the keyboard, so I'm stuck at the "Login with your existing B&N...." screen! Keyboard flashes up and then immediately disappears!
As an noob, it occurs to me that all my problems are related to my inability to format the /data partition (if it's even called a partition).
Can any of you awesome people help me? And, if I'm in the wrong forum, any directions would also help. Thanks.

Same error here
If anyone can help with this it would be much appreciated.

have you tried removing CWR then do the 8-boot reset?

No, every time I've done it, it boots into CWR. Maybe REMOVING it will help. lol. Sorry to be so inept. I can flash the 1.2 stock that will remove CWR. Is that the way to do it?

Worked like a charm
Removing CWR and 8-boot-interrupts did the trick. I'm now back to a fully stock NC 1.2.0. Ready to roll up my sleeves and re-brick!
This is the most amazing community. The closest thing I have to any technical knowledge is speaking a little Klingon. VERY little. But, I have learned more here by reading these threads for a couple hours...OK, several hours... than my wife has learned in a dozen trips to the apple store. I feel more empowered every day. You are all great. Can't thank you enough.

Goldie, I wasted a bunch of time on this last night. I'm guessing you have a new nook. If you do, slap cwr on your SD (3.0.2.8 or something) and look for the thread that tells you how to repartition your nook. Follow instructions to set it to the old way. After that run manualroot zip through cwr. Reboot to cwr and wipe data, system, cache. Finally install your rom of choice from your SD card through cwr. That's what I did to finally get it to work.

Thanks. I'll give this a try. As you probably guessed, I DO have a new NC, and while I was able to get it back to 100% stock, and easily reregister it, I had the same results. The ONLY way I can get CM7 running is off the SD card. So, I'll try the partitioning trick. Why do I get the feeling this is going to work? Unfortunately, I'm not on dev's time... I'm at work by 7:30am EDT, but in bed pretty early. I REALLY appreciate the response. Later this week I'll install SDK, and all my tools at home so I'll be able to stay up all night with you awesome folks.

still looking for the thread on re-partitioning. I found the thread on restoring, but I get the error every time I try to reformat the /data.

No luck. I can restore to stock 1.2, reregister, and MN 4.5.25, all easily. BUT, once I flash CM7 (or Phiremod 6.3, etc.) it hangs at the "n C O L O R" screen (C O L O R flashing at various speeds just to fool you into thinking it's actually going to work). Here's what I've noticed...after flashing CM7, the ADOBE screen no longer flashes up at boot. Once it fails to boot the Adobe software, it won't boot at all. So, for now, I guess I'm running CM off my SD unless anyone can suggest anything.

Goldie u have to repartition to get it working. Ill go look for the thread. Also maybe you should try out the cm7 mod over the phiremod Tom. I'm on phiremod now and the lag is killing me
Wow that was painful to find. Needs a sticky.
http://forum.xda-developers.com/showthread.php?t=1094371
Edit: I take that back about the lag, set your cpu to 1200 in the ROM and change yourgovernator to interactive for an amazingly smooth experience

I've been going nuts trying to figure this out. I too ran into the "error format /data" message but I powered through it only to end up at at the Android logo--nothing. Out of frustration, I returned to CWR and wiped everything--like on my Evo (did not go through to mounts option). That seemed to go through /data but I don't know the difference between a wipe and a format (I'm looking...). Still got bootloops. I tried to return to stock but the 8 interrupts wouldn't work.
Pressing START and N worked though and that got through to CM7 and it's working great now but I'm afraid to do anything else because I still get the "error formatting /data" message.
I've heard horror stories (bricking beyond repair--if that's possible) of users repartitioning their drives though so... I hope there's another solution out there.

I love this community!!
Sys:
Thanks a million!! Everything perfect!! I just can't say enough about this awesome community, all the amazing devs.

heh you're more than welcome . i hope this helps anyone else that stumbles on your thread as well. Ive been having fun with my nook but i think its time to trade it out for something a little bigger. Maybe ill just wait till att gets its flavor of gs2 idk. So many choices out there!

thanks guys!
i just had the same problem and falshes all kinds
of zips until i found this post.now i've launched cm with status bar
really really thanks

this worked great for me too! i had a nookcolor bought in december and it had a messed up chargerand 6 really bright white spots that were really noticiable. went to b&n store and the guy just gave me a new one. it came with 1.2 and i had the cwm sd from the old one. so tried restoring my cm7 backup from the old one and error formatting data came up. flashed this zip, and im wondering, since these are too different nookcolors, should i restore the cm7 backup or flash it brand new. because i had a ton of stuff on the old one and i dont want to lose it. so can i ust do advanced restore and restore data, or can i restore the whole thing or just flash and slowly get my stuff back?

update cwm
ok not sure if you fixed it or not yet, but i had the same problem for awhile too until i found a post
your probably using cwm 3.0.0.28 just updated it to 3.2.0.1

bl3achcrazy said:
ok not sure if you fixed it or not yet, but i had the same problem for awhile too until i found a post
your probably using cwm 3.0.0.28 just updated it to 3.2.0.1
Click to expand...
Click to collapse
i have tried 3.2.0.1 but get same error message

3.2.0.1 on the bootable card or already on the eMMC? It has to be on the bootable card.

Thanks
It works after getting my nook color around 2pm today and taking it home. I was working on this thing all day I tried several ways and this one worked!!! Having issues with wifi that's all

[Q] 2.3.3 OTA Rooted problem...

Hey I would have posted this on a different thread but i cant because i just made this account they want atleast 10 posts...
heres the deal... i have a rooted evo and running cm7 which i like, but i was dropping calls and where i live i should have good service. so i got the updated radio/wifi/ ect package and flashed it... it installed but did not help with the call issue... i heard many other having the same problem.
so i flashed the ota root update... which seemed like it did it really fast (wasnt watching the whole time) and the phone rebooted but gets stuck at the white htc evo screen, i let it sit there for 20 mins nothing, so right now i am recovering my old cm7... just wondering if anyone has that same problem or can help with getting better voice reception on cm7.. like i said i have tried the package for radio ect... and my prl was updated before i flashed to stable of cm7 so that should be in good standing i would imagine... thanks..

The obvious first question is, did you do a full and complete wipe of everything before you flashed the ROM?
As far as your signal, it may have been just in my area, but I know a few people that had problems texting and making calls, getting a "Network Is busy" error.

yea i did the wipe data/cache i wasnt dropping calls before the cm7 so im not sure right now im shootin to myns seeing how that is... cm7 was first flash i did
well as im trying to flash to the myns its looking like the samething... ill go through the steps...
have zip file in root of sd card
open up rom manager, have the newest clockwork thing installed
i goto flash from sd wipe data and cache are checked... i already have a backup so i skip that part
it installs.... says install is done and reboots itself... but seems to stay on that white bootscreen
if i take the battery out then i can reboot with recovery from the save file i have

blah i dont know... i got the ota installed... looked like it got a bit better reception.. i updated prl and came back to cm7 same probs... i dunno maybe ill just have to let go of cm7... really dont want to though its so sexy lol

I had the same weak signal issue with cm7 and had dropped calls and data dropping to 1x. I am on stock rooted 2.3.3 and reception is good again. Liked cm7 but need a phone I can use in the boonies.
Sent from my PC36100 using XDA Premium App

Dude, please, don't use ROM Manger.
Just boot to recovery, hopefully, you have Amon Ra, if not, search how to get it on your phone, it's not hard, do a FULL WIPE, full, wipe everything in recovery, then flash the ROM in recovery.
No offense to the Dev, I know he's a great guy, a smart guy, hard worker that makes a contribution, but Rom Manager is not the best way to do this.

Yea had to do it manually but nymph works now liking it so far

ok now i have different problem.... got the myn working liking it, but my market is completely different, not just the theme, but the apps i usually download... so tried to flash new market but it just open/closes quickly... any ideas for that?

Not sure by what you mean by the apps you usually d/l.
One thing about the Market in these newer ROMS is that sometimes, you just need to give it some time to fully sync before all your apps so up...
You should pull the market out of the zip file for the ROM and re-install that one, but you'll have to delete the one you have installed now, first.

umm usually download ninjump cant find that just some games that are usually on my phone the market on cm7 had them... ill give it a try though

look on the android market website

can flash to miui or restore to stock htc root but .....

This is my first post in XDA.I hope this is the right spot for this questions.
I have searched everywhere for the answers to this question before posting. I flashed to CM7 with the tiamat kernel awhile back. I love CM7 but was curious to see what other rom developers are doing.
I ALWAYS do a back up before doing any flashes. I backed up my CM7 and my base rooted HTC downgraded 2.2 through RM. I was able to flash to synergy with no problems and restore to CM7. I decided to check out MIUI over the weekend. I flashed it with no problem. Last night I wanted to try mikshifted-g and Supreme Sense . I could not install either of them . The both stalled once CWM started to install. It was stuck on updating. There were no errors. I took the battery out and tried to restore CM7 backup through CWM. The restore went as expect but when I went to reboot it was only the HTC logo. I took the battery out and went back to MIUI through CWM and the phone booted. I then did a restore of my original rooted 2.2 the phone booted. I tried to install the above again on a fresh HTC stock rooted phone through RM and still had the same thing happen.
My question, is why I am not able to flash any other roms successfully other than restoring to MIUI and stock rooted htc 2.2 ? Installing Synergy works !
I do a full flash of system,data, cache and dalvik cache. I am not sure what I am missing.
If I understand correctly MIUI is a GB kernel as well as the others so there should not be a problem of compatibility ? I am assuming I still have root ? My HBOOT does say S off and PG 06001. I will try downloading CM7 through MIUI again to see if it works through RM. Sorry for the long post. I wanted to give as much detail as possible. Thanks in advance for any help
Richard

My suggestion would be don't use ROM Manager to flash, wipe or make nands. Do everything manually through recovery. I've seen too many people have the same type problems when using ROM manager.

what I have noticed is the progress bar in cwm doesn't work with sense roms, at least it never did in the mikshifted roms i tried and they take a LOT longer to install than cm7. How long did you let them sit at the install screen with that blank progress bar? Try clearing all your data/caches then install a sense based rom but leave your phone alone for like 10 minutes while it sits at that screen with the blank progress bar that says mikroms or whatever it says (been awhile since i used one). It shouldn't take 10 minutes but if your phone sits at that screen for that long then you know for sure it isn't working. I pulled my battery a couple times before i realized that's what was happening. I read about it somewhere online.

I have tried both RM and CWM. Both have the same results. 99% of the time I prefer the manual CWM method. Sorry I did not make it more clear.
I did re-flash CM7 with no problem. I do let the rom flash sit for a while but I will try longer since you say it takes longer with the roms in question. I let it sit for a few minutes. That seems like it should be more than enough. CM7 is pretty quick to install as well MIUI like you said. I love the layout and features of MIUI but since I am in a 4G area seems to defeat the purpose of having 4G if you can't use it. To be realistic though 4G is spotty in Atlanta and I mostly end up for 3G or using my wireless at home. I will probably end up with CM7 again since I like it equally as much as MIUI. If I wait longer for it to install and it does not work is there anything I should be looking at as the culprit other than myself

you were right, it just took a LONG time to install. I thought I was losing it. It took over 5 minutes. I am used to the install times of the MIUI and CM7 . Thanks for telling me to wait a little long. It's always the simple overlooked things like patients

My advice is just make sure you do a FULL Wipe before flashing a Rom. Like on THIS GUIDE, saves headaches later. Aslo, as you've learned Sense Roms usually take quite a bit longer than MIUI ,ASOP, or most others. But yes patience is important .

I definitely do a full wipe . I used all the guides here to make sure I did everything correct. I did not realize that the sense roms took longer than the CM or MIUI. I love the layout of MIUI. I wished it at some point 4G was going to be a part of it but I understand why it will not be .
4G in Atlanta, GA is not reliable, at least on my shift with sprint. I hate to pay for a feature that I am not able to use on regular basis. It's so spotty here I have gotten used to it.
I was never a big sense fan but it seems like if you want to have the 4G feature you use either use CM or another Sense rom right ? I got the shift because of how solid it's built and many reviews favor the EVOs or Galaxy S on Sprint
Thanks for all the feedback
Richard

Well you might want to give [AOSP ROM] S.O.A.P. ROM (sense-ish on android phones) a try. Sounds more like what your looking for. It's by one of the Shift members here.