Related
So today i rooted my desire, and tried installing the Sense 2.2 HD.
The installation failed and now i cant boot up, get stuck at the white screen with HTC logo. Connected SD card through USB in recovery mode, and formated it multiple times successful into all kinds of formats (fat16, 32, ext2, 3) in both windows and ubuntu.
Now when i try to run the update.zip or any rom file from recovery i get the following error
E:Cant mount /sdcard
(No such file or directory)
or some other problem
Any help would be nice
Moved to Q&A.
Take a look HERE. Hopefully this should sort you out.
I've did a wipe data/factory reset, is it still rooted after that?
Cant get this crap to work. It boots straight into Fastboot usb now. But it wont find the sd card. Its the stock sd with 4 gig. My pc finds it and it works
How do i get my phone to recognize the sd card?
Yes you should still be rooted, a wipe/factory reset won't unroot your handset.
All you need to do is the fastboot command to get your SD card recognised again. If this doesn't help, I'd try a new or different card.
Wow took awhile. Downloaded an RUU and went into fastboot and updated.
All sorted then?
Just ran into the weirdest of problems. I had a rooted desire with Latest Clockworkmod Recovery and Villainrom. I saw some roms that required i had AmonRa so i flashed that using unrevoked. I did'nt like amonra's recovery so i used rom manager to flash clockworkmod back. It wouldn't stick permenantly, i.e. on a hard boot it'd revert back to amon ra.
Today i did the same, then asked rom manager to backup the current rom. It rebooted, amonra applied the clockwordmod update... then clockworkmod recovery started.. then started backing up the rom, upon completion it just rebooted without asking and kept on rebooting on the HTC logo, did'nt go ahead from that. I took the battery out and then re inserted it.
What happened next is weird. I user wiped the phone (using amonra) it gave me an error
Formattting SDCARD:.android_secure...
E:Cant mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(no such file or directory)
Error mounting /sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
Skipping format of sd-ext
After this when the rom booted, the phone refused to recognise the sd card, and the charging light wouldn't turn on when i connected a usb cable OR the charger. I tried replacing another sd card that was working on my htc hero and it wasn't recognized either. I tried my orignal HTC Desire SD card (16 gb) in the hero and it showed a 14 gb unformatted partition on linux. when i tried mounting it , it mounted correctly. I immediately copied my data off the sdcard.
Please note that i had a 512 + 32 mb ext4/swap partition besides the rest of the fat32 partition which wasn't recognized in linux. After repartitioning the sd card i tried the sd card in the desire again but it's not working. Right now i can't mount or access any sd card in the desire, nor can i use adb to connect to the desire. I tried unrevoked to patch the clockworkmod recovery again but it doesn't recognise the phone at all. I'm thinking the rom is screwed up and i'm trying to patch another rom again on the phone but i can't since i can't access the sd card.
I'd also like to mention that using the amonra i tried repartitioning the sd card after this whole mess and it did'nt give me any error, so i'm thinking it did get to access the sd card.
Please any help would be appreaciated.
ok i just figured out that it's s-on on my phone now. So now i have a htc desire with amonRA recovery and S-on with Villainrom 1.0 installed on it. It's not showing usb debugging mode when i connect the data cable, nor is it accepting any sd card.
If possible can anyone tell me how i can :
1. Turn S-on without using usb debugging etc ?
2. Use unrevoked some other way
3. Unroot the phone to root it totally over again.
i had this problem the other day.
Check out this thread. worked for me. Read it through first so you know what your going to be doing.
http://forum.xda-developers.com/showthread.php?p=7616115#post7616115
THANKS ! I've finally got the sd card to be read but i'm wondering that post is for the legend, will that work on my desire ? i mean those image files etc ?
Thanks for the tip man, i googled the words (which i couldn't find to express my problem) i.e. bricked usb and found my solution for the desire here http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
Hello,
I have a PVT4 Desire with erasezize 40000
I am rootes and s-off
Recovery : Clockworkmod Alpharev Recovery 2.5.1.8
After i switch from Starburst Rom to a normal apps2sd+ rom, i got this:
E: Can´t mount /dev/block/mmcblk0p2 (File exists)
Error everytime in Recovery.
This error comes before i have to confirm the wipe of the dalvik cache.
I unrooted the phone with a official RUU and rooted it again and did s-off again,
but the error still exists.
Stock Rom is working, recovery is working, but i am afraid of flashing a new rom
Please help
Thank you
Do you still have the ext partition? I believe this is the error that you get when there is no ext partition.
no, i don´t have a ext partition, because it is a rooted stock rom running now without apps2sd+
its a new sdcard fat 32
do you mean if i create a new ext partition on the sd card, the error disappers ??
Yes but i don't know if there is any point in doing that.
ok, i created a new ext 3 partition on the sd card, but the error still exists
I found the exact error in a different thread here.
They managed to solve it
dunno if its of ne help....but i had the same prob of "E:Can't mount /dev/block/mmcbld0p2 (file exists)" with my HTC Desire with cynogen recovery mod and leedroid.
phone was getting stuck at boot screen. only recovery was working. i unmounted the SD card, deleted the ext3 partition through Disk Management in windows and mounted the card again. Now, android booted (but without A2SD) i downloaded ROM Manager and used the option "partition SD card" and like a miracle, the phone rebooted, partitioned my SD card, and rebooted back to android (this time WITH A2SD working!!!)
hope it gets as easy as this for u guys as well.
(P.S. : before A2SD, my internal space showed 92.4 mb, after A2SD started functioning, internal memory showed 130.2 mb)
PVT4 Desire's can't use CWM - they have to use AmonRA as highlighted in the stickied at the top of the General thread
stuck in bootloop, with same error in recovery
i have somehow managed to screw the device, it wont boot stuck at htc white screen, id really appreciate if you could help, i cant manage to get adb setup on my computer to list the connected devices maybe the driver issues
what i did to get into this was this:
1.i was using a custom rom from Auraxtsense 8.3 with Amon.RA recovery
2.i got into Rom Manager n install clockworkmod recovery just out of curiosity, the next reboot i was stuck on the htc screen
3.i can get into recovery n stuff, but i cannot mount my SD card, ive somehow managed to get my data out of the card by using it from another phone
steps tried:
1.i tried to go into fastboot n use a RUU to flash it but i got a Error 171 usb connection error
2.tried using Android fastboot commander but it fails to flash any type of file
i cannot understand the right process to go about things please help me, even if i can setup adb with the right drivers, access it from hboot or so push files make it stock then root n stuff again
formatted the sdcard totally to fat32 also n then tried via recovery to partition n all no luck
AceNik said:
i have somehow managed to screw the device, it wont boot stuck at htc white screen, id really appreciate if you could help, i cant manage to get adb setup on my computer to list the connected devices maybe the driver issues
what i did to get into this was this:
1.i was using a custom rom from Auraxtsense 8.3 with Amon.RA recovery
2.i got into Rom Manager n install clockworkmod recovery just out of curiosity, the next reboot i was stuck on the htc screen
3.i can get into recovery n stuff, but i cannot mount my SD card, ive somehow managed to get my data out of the card by using it from another phone
steps tried:
1.i tried to go into fastboot n use a RUU to flash it but i got a Error 171 usb connection error
2.tried using Android fastboot commander but it fails to flash any type of file
i cannot understand the right process to go about things please help me, even if i can setup adb with the right drivers, access it from hboot or so push files make it stock then root n stuff again
formatted the sdcard totally to fat32 also n then tried via recovery to partition n all no luck
Click to expand...
Click to collapse
Flash the rom again but no wipe.
I get the /dev/block **** when I wipe Dalvik cache but everything is working fine.
GoogleJelly said:
Flash the rom again but no wipe.
I get the /dev/block **** when I wipe Dalvik cache but everything is working fine.
Click to expand...
Click to collapse
i cannot access sd card, when in recovery n try to choose option flash zip from SD it gives this error
tried RUU also but get that stupid USB error
u think guys at HTC RMA will fix it?
Format the SD Card and see if that works.
Thanks, Steps that worked
GoogleJelly said:
Format the SD Card and see if that works.
Click to expand...
Click to collapse
hey thanks, i did that plus i also needed to run this command that seemed to have fixed the issue
Code:
fastboot oem enableqxdm 0
although i followed 2 threads
No-ADB-No-SD
&
Usb Brick Function
but jus used the command n formatted memory card n stuff worked not i couldnt move those 2 files mentioned here to the system since cat commands couldnt work
im still unsure device seems restored using my earlier rom from AuraxtSense with Data2SD
i still wonder if it completely fixed, n whether i should go ahead n create a goldcard, n like i need a guide to know what are the perfect things to do to keep as backup when such stuff happens
dunno if its of ne help....but i had the same prob of "E:Can't mount /dev/block/mmcbld0p2 (file exists)" with my HTC Desire with cynogen recovery mod and leedroid.
phone was getting stuck at boot screen. only recovery was working. i unmounted the SD card, deleted the ext3 partition through Disk Management in windows and mounted the card again. Now, android booted (but without A2SD) i downloaded ROM Manager and used the option "partition SD card" and like a miracle, the phone rebooted, partitioned my SD card, and rebooted back to android (this time WITH A2SD working!!!)
hope it gets as easy as this for u guys as well.
(P.S. : before A2SD, my internal space showed 92.4 mb, after A2SD, internal showed 130.2 mb)
the error's gone, but problem exists
hey the error of the recovery not being able to access memory card is gone, but now when within the android OS the problem is when connected to the computer the charge sign or even the prompt to mount as disk drive does not show in the notification
in short i need to mount my memory card on the computer n the android OS cannot figure out how, is there somethin that may still be locked, i issued a command earlier from fastboot to get the earlier problem go
Code:
fastboot oem enableqxdm 0
You have the USB brick issue. The misc partition gets corrupted.
If you search you will find the solution.
Sent from my HTC Desire using XDA App
Jpcurrie said:
You have the USB brick issue. The misc partition gets corrupted.
If you search you will find the solution.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
hey thanks, i tried here
i need some help
Code:
3. Get flash_image from the attached files below
Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)
4. Repeat step 3 a couple of times if it doesn't seem to work well.
5. All done! Reboot, you should have normal usb connectivity. Post your 'fastboot oem boot' log and intermediate steps if it fails.
i got the 2 files on my sdcard, im rooted but S-ON, i tried the 3 commands
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
chmod u+x /data/flash_image
in terminal emulator on phone, but when i press enter jus shows # again
then tried /data/flash_image misc /data/mtd0.img
says illegal instruction or somethin as an error
can you help me if im doin this rite? i browsed the /data/ folder via a ESFile Browser it seemed to be empty
I had this issue with my SD using, i solved it. Just partition your SD with 512mb for ext2 primary and the rest for fat32 WITH ALSO primary partition, I was using FAT32 Primary and EXT Logical, thats why i got the error =)
Hope it helps, and sorry for my bad english
hi guys, im also getting the following error... E:cant mount /dev/block/mmcblk0p2
i have searched for days now trying to find the solution, i see something about adb and command lines etc but i have no idea how to do that!
plus i see that it means that ineternal partitions are somehow messed up, but i only get this error with one of my sd cards.. my old one works fine. so surely it is a sd card problem,
i have so far tried partitoning with cwm recovery, in windows, using gparted and no luck.. as anyone found a definate solution yet?!
thanks
Solution to E:cant mount /dev/block/mmcblk0p2
moley10 said:
hi guys, im also getting the following error... E:cant mount /dev/block/mmcblk0p2
i have searched for days now trying to find the solution, i see something about adb and command lines etc but i have no idea how to do that!
plus i see that it means that ineternal partitions are somehow messed up, but i only get this error with one of my sd cards.. my old one works fine. so surely it is a sd card problem,
i have so far tried partitoning with cwm recovery, in windows, using gparted and no luck.. as anyone found a definate solution yet?!
thanks
Click to expand...
Click to collapse
hey i had this problem a few weeks back
refer this thread just to get the update.zip file
1.format your SD card to FAT32, put update.zip on it
2.boot into fastboot, connect usb cord to phone n computer
to get into fastboot mode
press volume down + power held for a few seconds when phone is off
then press volume down once n enter fastboot
then connect the phone to the computer
3.on the computer run command prompt n browse to the director with android SDK n go into the tools folder
execute this command
Code:
fastboot oem enableqxdm 0
4.once this is done, the SD card is then recognized by the recovery
5.now reboot go back into recovery from the same volume down+power sequence n then say flash zip from SD card
to get into recovery
vol down + power at start n then select recovery (having access to recovery is important)
then choose flash zip from sd n flash the file update.zip from your sd card
basically the fastboot command n format of the sd card should be fine to let you flash a new ROM zip file n get the phone started
but the issue is actually called a USB brick in which, you lose access to bluetooth, battery drains a lot, n there is no way to access mem card via usb on the computer its not recognized
hence i flashed this update file from that forum there, which describes the fix in detail
Hi All,
I have a problem with my SD card. My phone doesn't recognise SD card after I created ext4 partition through partition magic on windows 7. Here is what happened.
- I have rooted desire running CM 7.0.3.
- I wanted to go back to Starburst 1.4 rom.
- I have class 4 16 gb sd card (fat + ext3) with 512 mb of ext3 and rest fat32 (this was when everything was running good)
- I flashed the new rom through CWM, but only got like 54 mb on sd left.
- So I manually formatted ext3 and changed it to ext4 using partition magic on windows 7 (connected sd card through a reader).
- After that I flashed the new rom, but still got the same size left.
- After that I went back to CM7.0.3 which is working fine for me.
However, at this time, my phone doesn't recognise my SD card.
- I saw that I can't format ext in recovery as i get this error
E:Can't mount /dev/block/mmcblk0p2(File exists)
Error mounting SDEXT: !
I believe I was able to install CM7.0.3 coz it was a small rom was fit directly into phone's internal memory.
At this time, I can't see my SD card on phone. Can't play music or install any files or anything.
Looking for some quick help.
Thanks,
Satyam
Hi,
I had the same problem.
I got someone to format my SD card in there phone, then reverthing worked.
Regards
Matt
topgunmatt said:
Hi,
I had the same problem.
I got someone to format my SD card in there phone, then reverthing worked.
Regards
Matt
Click to expand...
Click to collapse
Hi Matt,
So are you saying that you got your SD card formatted by someone else using Rom Manager ?
- As of now, when I click on the inbuilt ROM Manager in CM7, it says " The SD Card needs to be mounted to use ROM Manager!"
That means my SD card is abviously not read by my phone.
Looking for some help. I don't want to do something silly at this time.
Atleast, as of now my phone is not bricked and is working, just the SD is not.
Any suggestions/comments or link to my problem is more than welcome.
Thank You
Hmmm, i smell another usb brick here, we've had so many these days, and all by people using cwm and flashing gb sense roms...just to prove i'm right, can you connect the phone to your pc? If you're not able to do that, then u have 100% chance it's a usb brick.
OMG !! yeah you're right.. now when I connected my phone using a USB, it doesn't give me the option to "mount USB".
What do to from here ? I don't know what is a USB brick and am pretty poor with linux commands !!!
Plz help.. However I can see a a couple of ROMs through recovery mode in my SD card, but can't flash those which require an EXT.
Plz help !!!!!
sroy001 said:
OMG !! yeah you're right.. now when I connected my phone using a USB, it doesn't give me the option to "mount USB".
What do to from here ? I don't know what is a USB brick and am pretty poor with linux commands !!!
Plz help.. However I can see a a couple of ROMs through recovery mode in my SD card, but can't flash those which require an EXT.
Plz help !!!!!
Click to expand...
Click to collapse
Haha, calm down its'no biggie believe me
Here you can find a tutorial on how to fix it: http://forum.xda-developers.com/showthread.php?t=691639
Feel free to ask if you need further help (bus is farkin boring).
vnvman said:
Haha, calm down its'no biggie believe me
Here you can find a tutorial on how to fix it: http://forum.xda-developers.com/showthread.php?t=691639
Feel free to ask if you need further help (bus is farkin boring).
Click to expand...
Click to collapse
Hi,
Are you saying that formatting SD card and making fresh ext partition through a media reader will not help in this case ?
I am very confused so to say.. I read the link that you posted, it talks about CID which I'm not able to find.. Can't see that option in fast boot (recovery).
Is there some other way to fix all this ?
Any more tricks/ suggestions are more than welcome..
Please see detailed info about my issue in the post
sroy001 said:
Hi,
Are you saying that formatting SD card and making fresh ext partition through a media reader will not help in this case ?
I am very confused so to say.. I read the link that you posted, it talks about CID which I'm not able to find.. Can't see that option in fast boot (recovery).
Is there some other way to fix all this ?
Any more tricks/ suggestions are more than welcome..
Please see detailed info about my issue in the post
Click to expand...
Click to collapse
Nope: i'm sorry but there is no other way...the problem lies in the misc partition, and that one doesn't get touched by simply toying with your sd, it's on nand, and no rom flashing/nandroid restore can touch it either. This process is the only way to go. CID can be obtained via adb command, i hope you'll have it installed and set up correctly.
i just fixed my brick lol . i found out bcuz i coulnt enable bluetooth
vnvman said:
Nope: i'm sorry but there is no other way...the problem lies in the misc partition, and that one doesn't get touched by simply toying with your sd, it's on nand, and no rom flashing/nandroid restore can touch it either. This process is the only way to go. CID can be obtained via adb command, i hope you'll have it installed and set up correctly.
Click to expand...
Click to collapse
Hi,
Okay I get it.. I need to fix my nand partition, now question -
1) I can figure out the 1st step "Find out your CID. Go into fastboot mode, and do 'fastboot oem boot" - Nothing happens when I click on fast boot option in recovery mode. The other method CID generator also asks for CID.. how do I get that.. that's my biggest question.
2) How can I see the rom version.
I know, I might me sounding stupid, but I'm not a pro.. used to love flashing new ROMs earlier and this time I just messed it up.
Need some step-by-step help.. I might be asking for too much, but I trust this forum and believe Android has too many fans hooked to it.. so I will get some help
sroy001 said:
Hi,
Okay I get it.. I need to fix my nand partition, now question -
1) I can figure out the 1st step "Find out your CID. Go into fastboot mode, and do 'fastboot oem boot" - Nothing happens when I click on fast boot option in recovery mode. The other method CID generator also asks for CID.. how do I get that.. that's my biggest question.
2) How can I see the rom version.
I know, I might me sounding stupid, but I'm not a pro.. used to love flashing new ROMs earlier and this time I just messed it up.
Need some step-by-step help.. I might be asking for too much, but I trust this forum and believe Android has too many fans hooked to it.. so I will get some help
Click to expand...
Click to collapse
Also just want to let the forum know that I'm running a custom ROM (CM 7) and don't see the option of software info under Settings>About phone. Any other way to find out rom version ???????/
Ok, sorry man, i was out for a ride
To see the CID you have to type "fastboot oem boot" in the terminal, after navigating to the path where you have the sdk, for example:
"cd c:/sdk/tools"
"fastboot oem boot"
Then you should get all the info, together with the CID ofc...obviously you need to have adb installed and working in order to do that (there ia a lot of tutorials for that, just use the search function).
As to rom version, you don't need it, just download the mtd0.img, open it with the hex editor and mod it with your CID, then go for the next step
I dont believe you have bricked your phone, i think you have created a partition on it without making it a primary partition along with the fat32 parition.
boot into recovery and mount your SD card to your PC. Reformat the whole card and then it should work again, you may just be able to go into your partition software and amend to show 'primary' on each, if not read on. Couple of options then, download ROM manager from the market and reformat the ext3 using rom manger if not do it via your windows software but make sure both partitions are set to 'Primary'.
vis-tec said:
I dont believe you have bricked your phone, i think you have created a partition on it without making it a primary partition along with the fat32 parition.
boot into recovery and mount your SD card to your PC. Reformat the whole card and then it should work again, you may just be able to go into your partition software and amend to show 'primary' on each, if not read on. Couple of options then, download ROM manager from the market and reformat the ext3 using rom manger if not do it via your windows software but make sure both partitions are set to 'Primary'.
Click to expand...
Click to collapse
It's a usb brick, not a plain brick: when you plug it to pc the phone usually doesn't even light up the led.
sorry, i read that he had full use of his phone bar the SD card
- I saw that I can't format ext in recovery as i get this error
E:Can't mount /dev/block/mmcblk0p2(File exists)
Error mounting SDEXT: !
Click to expand...
Click to collapse
hi, seems you got bad partition on your sd card, since it s normal that you can't mount sd while plug on usb.
did you already put out your sd card out the phone and try to read it with a usb scard reader plug on your computer??
cid error mean you have messed-up your misc partition which is the one in your nand where the recovery is located... didn't see any error about this in your thread...
in the boot, should fail with error misc partiton cid unknown etc...
have a try about sd card reader it's easer than misc error fix
give a try on this site and try using gparted cd live... don't need to be expert in linux command (it s a graphical interface) should you know that FIRST FAT32 PRIMARY partition and LAST EXT3 (is less fast but really more stable and relyable fs) PRIMARY partition
hi, still me sorry for spamming, just found a nice TUT using gparted on xda http://forum.xda-developers.com/showthread.php?t=535914
fragargon said:
hi, seems you got bad partition on your sd card, since it s normal that you can't mount sd while plug on usb.
did you already put out your sd card out the phone and try to read it with a usb scard reader plug on your computer??
cid error mean you have messed-up your misc partition which is the one in your nand where the recovery is located... didn't see any error about this in your thread...
in the boot, should fail with error misc partiton cid unknown etc...
have a try about sd card reader it's easer than misc error fix
give a try on this site and try using gparted cd live... don't need to be expert in linux command (it s a graphical interface) should you know that FIRST FAT32 PRIMARY partition and LAST EXT3 (is less fast but really more stable and relyable fs) PRIMARY partition
Click to expand...
Click to collapse
Fixing misc doesn't take more than a minute if you have a working adb...repartitioning micro sd card takes loads of time instead, especially if it's big, coz you have to backup all of your data then copy them back, and that's a pain, especially if the sd isn't very fast.
Anyway you might be right there, just the other day a guy had a similar issue caused by multiple ext partitions not being recognized properly. I just thought it was a usb brick coz it's very common since the new gb sense roms rolled out and people started partitioning like crazy with cwm (which really SUCKS at that), and this either cause misc corruption or messed partitions on sd card: i'd suggest everyone to partition with amon them flash back any 3.0+ cwm to flash the rom, if you don't have the chance of using linux live cd (but you really should).
All sorted --------- RESLOVED !!!!
Okay Listen all Desire Owners-- I was able to fix this USB brick without having to go through all which was available on internet..
What I did -
1) Came home and formatted my EXT4 to ext3 and simply reflashed cm7 rom
All worked like charm - Now My SD card is mountable and works perfectly
Good for you
Anyway make sure you set up adb properly on your pc, it will save your life some day: it takes a while but it's worth it...i wouldn't get inti the rom flashing thing without it. Just a suggestion
Bests.
Hello all,
Okay, am definitely a noob, although have been able to root and make some major changes to my Desire with the help of this great forum since the last one year. Tried to look this up in the noob post and others, tried a lot of things folks suggested in other posts but not working.
Ran into a major problem this week when I tried to move to Leedroid's Gingerbread ROM using a brand new minisd I bought (Sandisk 8GB). Was running Leedroid's v2.5.0 earlier. Here are the steps I followed for the new card>
1. Backedup my stock MiniSD data (and formatted it)
2. Downloaded Easeus and partitioned my new MiniSD (using card reader) with first 7gigs of FAT32 and secondly with 500 MB of EXT3. (Cant seem to find an option for the swap)
3. Copied ROM and Radio into the new MiniSD
4. Booted into recovery through CWM v2.5.0.1 - wiped clean, tried to flash the ROM. Success message. Radio flash - Success message.
5. Reboot phone - stuck at HTC logo whitescreen!
Went into partitions menu on recovery and checked the mount, and I see this error:
E: Can't mount /dev/block/mmcblk0p2 (File exists)
Error mounting /sd-ext/!
I know this error can occur for a lot of reasons, but what I am more worried about is - did I just brick my desire? Am I just using an outdated CWM version? How do I upgrade now?
Thank you for any help..really appreciated.
SOLVED!
Upgraded CWM Recovery. Instead of EXT3, I re-formatted into EXT2, reloaded the ROM and Radio. Flashed!
Reboot successful.
well since it works already try with EXT3 or EXT4
they are faster than EXT2, you will see the diffrence