Database Info

Hanging G1 on all haykuro builds

On every haykuro build that I install, no matter what, it will either get stuck on the G1 screen or android/htc screen during boot after a restart.
I have reflashed my phone to RC29, re rooted, re installed JFRC33, and then tried updating from there 3 times and still I get the same problem.
It is really pissing me off now because it makes no sense that it won't work for me but it does for everyone else.
here is a log of the phone during the hanging G1 screen
http://pastebin.com/f58ba7818
haykuro said it is the new build.prop that is causing my problems but why would it only affect me and no one else?
If anyone has any idea of what is wrong, please suggest what to do.
JUST FYI
Yes, I did wipe before installs
Yes, I have completely reflashed my phone to RC29 and then re-rooted
Yes, I have checked the MD5 sums of all the files I use
It's unbelievable annoying.
Thanks in advance to anyone that can help.

Wait a little linger!
k when flashing to the haykuro builds the first couple time it takes a little to boot. your not waiting long enough. I almost took my battery out to start over again when bam the htc boot screen appeared. Trust me re root your phone from RC29 and add the 5.02h build and you will be all set I promise. you don't have to add Jf 1.42 RC33 build first. Once you get all set then update the radio. Hope I helped!

Well I waited well over 3 hours before and it was still hanging. and the output from the log looks like the build.prop is causing it to crash.. but I don't know why. I have flashed the recovery.img and I know that I am using test keys.

Payne IV said:
On every haykuro build that I install, no matter what, it will either get stuck on the G1 screen or android/htc screen during boot after a restart.
I have reflashed my phone to RC29, re rooted, re installed JFRC33, and then tried updating from there 3 times and still I get the same problem.
It is really pissing me off now because it makes no sense that it won't work for me but it does for everyone else.
here is a log of the phone during the hanging G1 screen
http://pastebin.com/f58ba7818
haykuro said it is the new build.prop that is causing my problems but why would it only affect me and no one else?
If anyone has any idea of what is wrong, please suggest what to do.
JUST FYI
Yes, I did wipe before installs
Yes, I have completely reflashed my phone to RC29 and then re-rooted
Yes, I have checked the MD5 sums of all the files I use
It's unbelievable annoying.
Thanks in advance to anyone that can help.
Click to expand...
Click to collapse
Don't know if this will help but, have you tried completely reformatting your sdcard and trying again, or preferably trying a different card? I have problems flashing when using my 8gb card, yet the 1gb card that came with the phone works fine..

Payne IV said:
On every haykuro build that I install, no matter what, it will either get stuck on the G1 screen or android/htc screen during boot after a restart.
I have reflashed my phone to RC29, re rooted, re installed JFRC33, and then tried updating from there 3 times and still I get the same problem.
It is really pissing me off now because it makes no sense that it won't work for me but it does for everyone else.
here is a log of the phone during the hanging G1 screen
http://pastebin.com/f58ba7818
haykuro said it is the new build.prop that is causing my problems but why would it only affect me and no one else?
If anyone has any idea of what is wrong, please suggest what to do.
JUST FYI
Yes, I did wipe before installs
Yes, I have completely reflashed my phone to RC29 and then re-rooted
Yes, I have checked the MD5 sums of all the files I use
It's unbelievable annoying.
Thanks in advance to anyone that can help.
Click to expand...
Click to collapse
you probly have a low class memory card and they are slow So it may take a while.....like the post above says swich cards and yull be alrite

Well I'm not using apps-to-sd.. would the sd card still affect it? I'm able to install the port fine and set it up, but after it reboots is when it gets stuck on the G1 screen.

yess it would because it is updating the system from the card

I tried again with my freshley formatted 1 GB card that came with the phone and still I get the hanging G1 screen.
I really don't think it has to do with the SD card, I think that it's something else.

bump.. anyonee?

have u updated to the new SPL and radio images that are on his site?

My devphone hangs for me on the Android startup. Now I can't do anything other than fastboot.
Bootloader: 0.95.3000
Baseband: 2.22.19.23
I can't even recover to any of my previously working firmwares because my baseband version isn't 1.22.14.11. I'm stuck!

Fixed the problem with an Alt-W wipe at the recovery console.

Yes I have updated the radio and the SPL but still the problem persists. I did a complete re isntallation of DREAIMG.nbh with the 1 GB card that came with the phone (after I formatted the card) and then rooted, isntalled the modified recovery.img, then I installed 5.0.2 again, and I still got the same result.
I really don't understand.

I really wish someone knew how to fix this I miss those soft keyboards.

[SOLVED] HELP Installing CM 4.2 on Mytouch3G

Hey guys so I'm pretty tech savvy and i know my way around this phone but something weird's been happening. I had CM 4.2 on my Mytouch3G. I tried applying a theme which made it not boot up anymore(bootloop).
I did make a nandroid backup before but when i tried restoring with it, it keeps getting stuck at the green mt3g screen or at the second loading screen. I've tried flashing the rom again but gets stuck at the same place. If I just install the htc 1.6 update it works fine. But when I go to apply the CM 4.2 update it gets stuck again. I have wiped a million times, and fixed ext system also a bunch of times. I have also unrooted also by applying sappimg.nbh and starting over. Rooted, tried again, but nothing, still getting stuck at the loading screen. I have gotten it a couple times to go all the way to the home screen but i get com.android.phone force close.
Also i've tried going from stock htc 1.6 to CM 4.1.99 and up, not just straight to CM 4.2 so i don't know what to do.
Any help appreciated!

I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.

charkosh said:
I seem to be having this problem as well.
Phone just freezes at MT3g loading screen.
4.1.9.2 seems to load fine, however 4.2.1 flashes properly, but phone just sits at green loading screen.
Click to expand...
Click to collapse
Maybe a mytouch issue? Hopefully we can get some help.

lupascu.marius said:
Maybe a mytouch issue? Hopefully we can get some help.
Click to expand...
Click to collapse
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.

bluecluenj said:
You didnt say the steps you took to flash it. Did you do the step by step instructions on Cyan's OP? You cant just flash it like a normal ROM you have to do what he says on his post. I followed the steps and my MT3G works fine with it.
Click to expand...
Click to collapse
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.

Make sure you wipe before applying rom

Mr Bill Florida said:
Make sure you wipe before applying rom
Click to expand...
Click to collapse
Do people even take time to read the original post, or do they just blurt out things that sound helpful? I said towards the middle of the post that i've wiped a million times and also tried fixing ext filesystem. I appreciate anyone trying to help but please read my post carefully!

I have the same problem guys, but oly with 4.2.3.1
http://forum.xda-developers.com/showpost.php?p=4851283&postcount=3677

i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.

jayzusfk said:
i HAD a similar problem when i went to 4.1.999 the first time but i fixed it.
i prefer amon ra's recovery 1.2.3g. i wiped the file system AND cache. then i did the 1.6 update followed immediately with the CM update. i rebooted and let it load up completely, then rebooted into recovery again and applied the new theme.
i actually went through the process a couple times before it worked flawlessly. it may have been a different problem though, since i was getting past the mytouch splash and about 10 seconds into the android splash before it would freeze.
Click to expand...
Click to collapse
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.

lupascu.marius said:
Thats a good idea...i'll try amon ra's recovery image and see if there's different results. Will post back soon.
Click to expand...
Click to collapse
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.

lupascu.marius said:
So i tried everything from scratch but with amon ra's rec image this time. It gets passed the first boot screen and right after the second android screen it goes straight to a black screen. Have tried a few variations of installing and same thing happens everytime...This blows, i'm so stuck.
Click to expand...
Click to collapse
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks

lupascu.marius said:
But i did say the steps...i first flashed the htc recovery image like it CM said to do. I even said in the post that i already had cm 4.2 on my phone but had to reflash after a theme froze my phone at the boot screen. I know its a different install process compared to any other rom.
Click to expand...
Click to collapse
Actually if you have an MT3G I believe you don't flash the 1.6 recovery image, but flash the 1.6 ADP rom. That is what I did since I was already rooted but with AmonRa's donut rom, but wanted to give Cy a shot, and I had no problems flashing this HTC ADP 1.6 DRC83 , then reboot manually but while rebooting I pushed home fast while it was rebooting to get me to the recovery screen, then I just flashed Cy's 4.2.2 then I went to the market and downloaded his Cyanogen updater and checked for an update, then found the update 4.2.3.1 and downloaded that straight to my phone and then choose to reboot and it automatically installed 4.2.3.1 straight to my MT3G with no problems at all.
From Cyanogen:
Download: Android 1.6 Recovery Image. (This isn’t like a typical "recovery" image we know -- it’s simply HTCs version of an update.zip.)
* Magic32A and Magic32B users only: Download this HTC_ADP_1.6_DRC83_rooted_base.zip

lupascu.marius said:
Quick update for anyone with any ideas. I finally got it to boot up and it runs great except for two things I've notices so far. When i try to add widgets nothing pops up and when i go to settings the window comes up for half a second then goes away and back to home screen. Now what I did to fix it was partition the sd card which i was told is NOT necessary. Then after i got it to work i tried again with a sdcard that was NOT partitioned and it did the same thing again, black screen no-go. So it seems like if you don't partition the sdcard on some phones the phone freezes at a black screen. Keywords being "some phones". So for anybody who knows how to fix the widget and settings problems not opening, please help me....Thanks
Click to expand...
Click to collapse
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....

mavsfan said:
I would go ahead and put Cy's latest back on your sd card, and also download the HTC_1.6_ADP rom if you have a MT3G (Magic 32B) or a Magic 32A and put that on your sd card. WIPE WIPE WIPE - I always wipe three times, and wipe cache also, then flash the 1.6 ADP rom then reboot but while it is rebooting hold down home to get back to recovery screen then apply Cy's on top of the 1.6 ADP rom.
I went ahead and just put Cy's 4.2.2 (instead of 4.2.3.1) on my sd card along with the HTC 1.6 ADP Rom and flashed the HTC 1.6 ADP rom first, then rebooted manually from the recovery screen, then quickly hold down home while rebooting to get back to recovery screen and applied any zip Cy4.2.2. Then when I signed in went to market to download Cyanogen Updater and set that up and then checked for updates and it found 4.2.3.1. I dowloaded that from my phone and then it was automatic from there, just asked if I wanted to reboot and apply and I said yes. Up and running with no problems so far....
Click to expand...
Click to collapse
That is the exact process i run thru. Sorry for the confusion, the reason i said htc recovery 1.6 is because thats what htc calls it. So i do have the htc 1.6 adp.....and i do wipe a lot also

This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.

Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).

jayzusfk said:
This is probably a dumb question as I assume you would have mentioned it, but are there themes involved in any of your troubles or are you staying with stock 4.2.3.1? I only ask because I was having the same issue with the SECOND android splash crashing because I had tried to install a theme before booting into Cyanogen at least once.
I also don't think you should reboot after installing the 1.6 base like mavsfan was suggesting, though I'm not sure if it's related to your issues.
Click to expand...
Click to collapse
The problem i have is with the stock 4.2.3.1 not the themes...and i've also tried without rebooting after installing the 1.6 base and just go straight to applying the CM update

pascanu said:
Try booting it up without an sdcard inserted. If it works that means it's your card. Card issues are very hard to diagnose and even harder to solve (other than reformat).
Click to expand...
Click to collapse
Hey thanks for your suggestion, i have tried that, I've reformatted, I've tried different SD cards and nothing changed. I'm pretty sure the sd cards are good...

[SOLVED]Finally...
So for anyone having similar issues, here's what i did to finally get this working.
Apparently with Cyanogen's newest ROM's you HAVE to partition your sdcard, so the Rom will run on certain phones. I don't know if its all phones because there's only a few people that i've heard to have this problem. So here's the steps:
Things you will need(all these can be found in this forum)
1. Phone+sdcard
2. sappimg.nbh
3. FlashRecovery.apk
5. AmonRa's recovery image(has more options than CM's RecImg)
6. Htc ADP 1.6 stock donut rom
7. CM 4.2.3+
8. A theme(optional)(check out the Eclair 2.0 theme)
Starting from scratch
1. a. Put sappimg.nbh on sd card and turn the phone off.
b. Turn phone on by holding VOLUME DOWN+POWER
c. Apply the stock sapphire image and boot up to home screen.
2. a. Now put FlashRec.apk and AmonRa's recovery image on sdcard.
b. Install a file manager like Astro and install FlashRec.apk
c. Now open it and click Backup Recovery Image.
d. Now erase whats in the box and type /sdcard/name.of.recoveryimage.img
e. Yes you do have to type .img after the recovery image name.
f. Then click flash.
3. a. Now put the HTC ADP 1.6 Rom and CM 4.2.3+ Rom on the sdcard.
b. Reboot into recovery by holding HOME+POWER.
c. Now partition your sdcard by selecting it from the menu(the one that says +swap)
d. Now convert ext2 to ext3. After that I did:
4. a. Wipe, format ext3, wipe
b. Flash HTC ADP 1.6
c. Wipe, format ext3, wipe again.
d. Flash CM 4.2.3+
e. Wipe, format ext3, wipe one more time
f. Reboot, now it should work, give it some time to boot up.
Adding the theme
1. Make a nandroid backup before starting to save you the hassle.
2. Put your theme.zip on sdcard and reboot in recovery again.
3. Choose apply any zip and choose the theme from the list.
4. Reboot once its done and enjoy.
If anyone has any questions about anything here go ahead and reply or PM me. Have a good one guys, hope this helps anyone.
Oh and if you guys see any mistakes let me know so i can fix it, its pretty late right now

Help Anyone?! Frozen on Boot (Not truely bricked)

Disclaimers: I hate asking for help and never have here before, but I'm at wits end. Yes, I've read the FAQ's, the Wiki and Googled myself silly. I've been working on this for over a day now, so I'm not asking for help casually.
Problem: MyTouch 3G TMOUS Will not boot into Android. I can load recovery, fastboot, etc., but when I try to boot android it goes to the green MyTouch 3G screen and there it stays. I've left it for 40 minutes a couple of time, and there it remains.
Cause: I've flashed several ROMs onto this phone before. I flashed one last night and it never booted.
I didn't make a Nandroid backup (stopped doing that ages ago since I never had a problem).
Attached is an ADB bugreport, if it's any help.
THANK YOU in advance for any help you can give me!
Recovery: RA-sapphire-v1.5.2G
SPL: HBOOT-1.33.2005 (SAPP30000)
Radio: 2.22.19.261
I've tried:
1) Flashing different ROMs
2) Flashing different recoveries
3) Flashing different SPLs
4) Even flashed the radio once
Problem remains unchanged.

I assume you already may have tried this... but have you made sure the partition setup of your SD Card matches the configuration the ROMs are expecting?
If not then you can partition using Amon_RA's recovery Rom. Also, clear your Data partition as well before you install a ROM (Again, I assume you probably already did this).
Lastly, try to keep this sort of thread to the general section

Thanks for the idea, CatalystNZ! Yes, I have tried about four different ROMs, and several different partition configurations to include straight fat32 and even booting with no SD card. I've also swapped out the sd and the sim with my cliq... all to no avail unfortunately.

Are you doing a full wipe before flashing?

Can someone not just post a unconfigured nandroid backup for him? You should always do a nandroid backup, and backup your sd card contents onto your pc, better safe than sorry mom always said.

I have had this happen as well and was very worried. I didn't believe my MT3G was really bricked, but...
I ended up backing up all my fat32 stuff, totally reformatting the SD card with fat32, then repartitioning with Amon Ra 1.5.2 with the file system specs the ROM your trying to use requires. Hopefully that will work. If not I'd go all the way back to a stock ROM (the sappimg.nbh which will reflash your entire stock images.) From there you have to-reroot, etc. (I resorted to this once as well)
Good luck!

Yes, if someone wouldn't mind passing me a spare nandroid backup, I'd love to give that a whirl.
I have been wiping before all flashes - everything right down to battery settings and tilt or whatever. I've formatted and partitioned multiple times with the recovery, xp, and even gparted a couple of times - no dice.
Lesson learned - nandroid backups good. Quasibrickage - bad.
I'm going to look into the sappimg.nbh bit tomorrow morning at work. That sounds like it has potential too!
Thanks again all!
*** djlman, the sappimg.nbh did solve my problem, the phone is back from the dead and my marriage is saved (it's my wife's phone). THANK YOU!

[Q] CWM not working right on new MT

I'm having all kinds of trouble with my MT. I originally flashed CM7 from stock with CWM after wiping factory and cache. The flash errored out the first time, but worked the second time. The gapps install errored out so I just tried rebooting without stock google apps. The phone just booted to the Motorola logo and didn't go any farther. I let it sit for over 20 minutes and no go.
I had made a backup so I went back to CWM to restore the phone. Again, I did a factory and cache wipe, ran the restore, rebooted, but now the phone boots to Motorola logo, then reboots into CWM. So weird!
I have a theory that it has something to do with a hardware problem. When I try to flash another rom (besides cm7) the screen goes blank (no text) and then goes back to the root menu. I tried booting to CWM then plugging it in and removing the battery but after an varied amount of time the phone shuts off.
I've searched and searched and I can't find where anyone's had a problem like this and NOT been able to get the phone back. I'd like a solution, but I'd also like to know if i'm the only one who's had this problem!
thanks!

Never mind
I got it working! I tried a different battery in it and it worked! I'm not sure if it was the battery or I just did the right combination of things, but I'm glad to be back! But for anyone who is having the same issue here's what I did:
Running CWM 5.0.2.6
1. Wipe factory/cache/davlik
2. format sd card
3. shut down
4. use pc to copy stock nandroid backup from androidforums (google "stock triumph restore")
5. boot back to CWM,
6. restore the backup and reboot, should work
**IF you have md5 checksum error, use adb via usb to run these commands and immediately try to restore again:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
# exit
**Make sure to unmount the sd card before restore.
Again, I really don't know if it was battery or not, but I tried this before changing batteries and it didnt work!

But wait, there's more!
Ok, now that I'm able to get back to stock, I'm still unable to flash any custom roms. I wipe/factory reset, format /system, then install update from sd card. When I confirm the update, the screen goes blank (no text), then goes back to the main menu! It does this with any rom!
Any help?

dont think triumph is supported phone according to cwm ?

garrmack said:
Ok, now that I'm able to get back to stock, I'm still unable to flash any custom roms. I wipe/factory reset, format /system, then install update from sd card. When I confirm the update, the screen goes blank (no text), then goes back to the main menu! It does this with any rom!
Any help?
Click to expand...
Click to collapse
You want to choose zip from sd card. Not install update
Sent from my VS910 4G using xda premium

I knew I'd word something wrong
I meant to say that. I did install zip from sd.

garrmack said:
I meant to say that. I did install zip from sd.
Click to expand...
Click to collapse
Are you running the latest cwm?
Sent from my VS910 4G using xda premium

Yep, 5.0.2.6. I just tried CM7 .04 beta because I have a friend who flashed it successfully on his MT. When I ran it it said it was installing for maybe 4 seconds and then said complete. When I rebooted all I got was the Motorola logo.
I just got this phone. Is it possible that Motorola changed something with the hardware to make it not work?

I've managed to get CWM running a little more stable by replacing the boot.img file with the one from CM7, but all I get when I run the zip is this:
-- Installing /sdcard/CM7.zip
Finding update package...
Opening update package...
Installing update...
Install from sdcard complete.
that all takes about 6 seconds and I get just the motorola logo when I reboot.
It still goes blank (no text) when I try to flash any other rom (like stockROM) so something is definitely screwy.

I don't know if this has anything to do with it, but I have a friend with a Triumph who successfully flashed cm7. I looked at his phone and found that the model number on his is WX345 while mine is WX435. Maybe my version really does have issues with clockwork?

vizionforever said:
dont think triumph is supported phone according to cwm ?
Click to expand...
Click to collapse
I did notice that the Triumph isn't listed on Clockwork's site. It is, however, listed on xda. Maybe its not officially supported?

figured it out! It had something to do with the sd card. I was using a 16gb class 10 PNY card. I put the stock 2gb back in it and it worked like a charm. Don't know if it was a defective card or the phone/clockwork just didn't like it.

Bay PONY...Noticed that my pny class 10 16gb was slower(or just took longer to mount and search for media, cause it's bigger) than the 16gb samsung class 2 that came with my epic...Dunno; but glad to hear CWM works! now you can switch back cards
PS. what root method u use command line or gingerbreak?

vizionforever said:
PS. what root method u use command line or gingerbreak?
Click to expand...
Click to collapse
I've tried both. I like the gingerbreak b/c it adds superuser app for you. Both worked fine though...
But since I installed CM7 I didn't need to root it first.

Problems after getting back to stock ROM from CM7

Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up

Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.

CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.

I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.

A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.

Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.

Still have to restart the phone every 1-3 apps installed. This is driving me crazy