Develop Bugs

I give up!!!!

I upgraded...so I thought to this version...
Rom Version 4.01.16 eng
Rom Date 02/04/01
Radio Version 4.21.00
Protocol version 32s54 now I cant get into bootloader, cant use the phone, or internet on my SX-56...nor can I boot by flashing....What Have I done wrong should I just use it as a paper weight? Remeber If I press the power button and soft reset to just goes back to the Tmobile screen an continue to boot as a normal Alt-Ctrl-delete. I have tried xdairt and himayla..cant get it to work...
someone plz guide me through this I want my pda!!!!

Try the option fix-bootloader from the XDATools.
Then you should be able to enter the bootloader, and reflash your device...
HTH
Stefan

after XDA1 ugrade to 4.01.16 not able to do up/downgrade !
Have upgraded my XDA1 to ROM-version 4.01.16 Eng.
Now I wanted to install a different version, but I failed.
The PDA is working so far, but I can't upgrade/downgrade anymore.
When I use OSImageTool, there is a connection error displayed in the black command window:
ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host. error getting connection type.
Can somebody please help me ?

Re: after XDA1 ugrade to 4.01.16 not able to do up/downgrade
Stefan_PDA said:
Have upgraded my XDA1 to ROM-version 4.01.16 Eng.
Now I wanted to install a different version, but I failed.
The PDA is working so far, but I can't upgrade/downgrade anymore.
When I use OSImageTool, there is a connection error displayed in the black command window:
ERROR: GetConnectionType - An existing connection was forcibly closed by the remote host. error getting connection type.
Can somebody please help me ?
Click to expand...
Click to collapse
There are many postings concerning this problem.....
You have to flash via SD-Card....
HTH
Stefan

Cant get into bootloader via pressing pwr botton and soft reset. I've have also hard reset the device and i still get nothing

Have you tried the fix-bootloader option from the xda-Tools?
Stefan

yes...but all i get is tthe command prompt...and i click yes is there something else i must do...tried edit2003 but still nothing

Cannot execute
Cannot execute "C:\DOCUME~1\Ovynten\LOCALS~1\Temp\Rar$EX00.203\RSUpgrade.exe"
wHAT THE [email protected]#$ DOES THIS MEANS? If uI could only understand this maybe I could get mt PDA working again.

Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....

Broken Radio ROM blocks official O2 rom, MaUpgradeUt_noID.exe fails "error 114"....
Hello
I hope someone here is able to help me.
I have spent the whole of the last 48 hours (no sleep) trying to fix my O2 XDA Exec. I *believe* that I have tried everything suggested on this forum and on Buzz's site but there is just so much on here now that I may well have missed something.
History:
Over the last few months, my phone has gradually got more inconsistent - dropping calls, refusing to answer calls, losing signal and so on. On Jan 1st, I turned it on and it had lost all my settings - Opera reg code, Wifi encryption, O2 net settings, etc.
I spent the last week with sometimes having network, sometimes not. Finally it just gave up altogether. In Settings>System>Device Info, "Radio Version", "Protocol version" and "IMEI" are all completely blank. When booting, the red text states "No GSM".
Reading around this site it appeared that I should be able to reinstall the radio ROM from the official O2 download however this errored with the Incorrect Country Code error. I have carried out full hard resets and still cannot get any Radio ROM visible. I assume that the lack of IMEI is affecting the official O2 downloads?
Since then, I have tried most variations on this site of ROM installs using MaUpgradeUt_noID.exe suggested in the wiki (with and without entering mtty code: "set 14 0").
Full three-part ROM and radio-only ROM install attempts all fail with the Error 114 "Radio Rom Update Error" (the radio ROM is always attempted first).
The only success I have seen was an update of Bootloader from 1.00 to 1.01 which worked completely perfectly and proved that the PC can indeed connect to the XDA when it feels like it.
After two days of earning no money ( I am self-employed) and no money to spend on support, I wonder if anybody has another suggestion for me?
In case it helps: ROM version: 1.30.107 WWE, ROM date: 04/11/06, ExtROM version: 1.30.162 WWE
All advice welcome
Thanks
Leapy

extract everything from the exe and do an upgrade without the radio.nbf

did you read what he said? its the radio that's bad and needs replacing
i don't know, sorry

poussin69 said:
extract everything from the exe and do an upgrade without the radio.nbf
Click to expand...
Click to collapse
I am now totally confused.
I know there was a smiley at the end of your comment, I just can't work out if you are being funny or astute (or both?). Can you explain how reinstalling the non-radio ROMs will help? Would that restore the IMEI?
TIA
Leapy

Midget_1990 said:
i don't know, sorry
Click to expand...
Click to collapse
Thanks for responding anyway. At least I am not crying alone in the wilderness.
It would be terrific to find a fix, though.

Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
http://www.buzzdev.net/index.php?option=com_content&task=view&id=78&Itemid=1

pof said:
Try to flash the radio from Buzz's unlocker with MaUpgrade_NoID.exe
Click to expand...
Click to collapse
Thank you for the suggestion, I just tried as you proposed. "Error 114 - Radio ROM Update Error" *sob*!
It's a real shame. It's actually the ideal phone for my needs.
Leapy

1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!

http://forum.xda-developers.com/showthread.php?p=994444#post994444
first as recomended i disabled usb from activesync
then downloaded mtty 1.42
connected the usb and started mtty
chose usb
white screen.....
typed set 14 0...
some gibrish on the screen....
ran the rom update....but it informed me that the rom is not for my device...
typed task 0 in mtty (not sure bout the command but its on page 2 of the forum)
ran the update....nothing same error....
now i saw that my universals screen was blank....
removed the battery....and then restarted my universal....
this might help you...
rtask 0/1/3/4

pof said:
1. Disable Activesync (connection settings -> uncheck "allow USB connections").
2. Put universal in bootloader mode
3. Connect device to computer using USB cable.
4. Start HHD Usb monitor (trial version is OK).
5. File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
6. In the upper part there are two tabs: basic and complete. Click on "Complete".
7. Click on MaUpgrade_NoID.exe and start the radio flashing process, if everything went fine you should see all the USB traffic output on USB monitor window.
8. When radio upgrade fails, click on Edit -> Export and Save as type "ANSI Text files".
9. Save the text file and zip it.
10. Attach the output here or upload it to ftp if it's too big.
Only with this we can see exactly why it fails
Good luck!
Click to expand...
Click to collapse
Thank you. I think I did everything exactly as you instructed.
Please find attached the zipped log file.
I would welcome your advice.
Leapy

Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not

Error 114: Radio Rom Update Error
WOW I have the same problem.....
but this commands for mtty...did nothing to my problem.
ERROR 114: RADIO ROM UPDATE ERROR
I don't know if that helps you....on my PDA it says Upgrade Radio Stack Please Wait...
I have the perfect phone....but it is not a phone anymore...and I go crazy.
Is there any way to update the radio rom from SD card??
Please Help

posted reply to incorrect post - cannot delete post - ignore. Please see next post.

pof said:
Radio is corrupted, and device cannot check SecLevel (wait interpreter timeout), it returns default seclevel=FF (unprivileged) and correct CID (O2___001), however when switching to radio bootloader to upgrade the radio, device doesn't answer to any 'rerase' command, that's why the utility gives out flashing after receiving no response to 3 "rerase 0 10000" commands.
Probably this is a bit "crazy", but if it is your last chance... try the following commands in mtty, and try to upgrade the radio again after this:
Code:
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
Don't do it if you can fix your device by any other means (warranty, service centre, etc...) because I'm not sure if it will work or not
Click to expand...
Click to collapse
Well, I too am a little "crazy" so I did as you suggest.
I tried to put Buzz's "unlock" radio v 0.0.0.0 ROM on using MaUpgradeUt_noID.exe. And guess what, it fails again but with a different error!
Error 150: ROM UPGRADE UTILITY ERROR. "This rom upgrade utility is not designed for your device. Please get proper ROM Upgrade Utility and try again!"
I attach the USB Monitor log if it proves any use?
I will try and use the official O2 ROMs and see how that goes.
Thanks again for your assistance, I truly appreciate it.
Leapy

To Leapy...
How did this problem started to you??
I have been using this phone for 1 week, after that I changed my SIM card with another one called MAGIC-SIM card, (programmable) with 8 SIM numbers.
After that day ALL the **** started!!!!!
I had problems during my dialing the number on phonepad...
when I was trying to make a call... it hang up.
After some soft reset...it didn't ask me for PIN.
After a hard reset.... on boot screen it said NO GSM
and then on antenna icon on the top of the screen the antenna had a little x on the right side.
Then the known problem ERROR 114: RADIO ROM UPDATE ERROR
I can update any rom I want but not the Radio ROM

leapy said:
I will try and use the official O2 ROMs and see how that goes.
Click to expand...
Click to collapse
well, I tried the O2 update and just got the generic "CID" error - twice. So I guess I am no nearer fixing this issue...
All advice welcome.
Leapy

leapy said:
Well, I too am a little "crazy" so I did as you suggest.
[...]
I attach the USB Monitor log if it proves any use?
Click to expand...
Click to collapse
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.

my friend got the exact same problem with his EXEC, and send it back to O2, they charge him apprx USD500 for mainboard replacement.....(fiuhh.....)

pof said:
Sorry but the capture was from the erase commands... not from the failed radio flash... please try to flash 0.0.0.0 radio again and attach the right capture... also make sure activesync is not running when starting the radio upgrade, and if it fails once, run MaUpgradeUtility twice without disconnecting the device from USB.
Click to expand...
Click to collapse
Thanks for your continued assistance.
I tried twice with the 0.0.0.0 radio ROM and this time the error has reverted to Error 114 again. With both these attempts, I noticed that the displayed "currently installed" ROM versions were blank - previously I saw the actual on-board version numbers. Not sure if that indicates anything?
Capture logs attached:

leapy said:
Not sure if that indicates anything?
Click to expand...
Click to collapse
That indicates you previously had activesync enabled and now don't.
Exactly same error as before, radio bootloader is not responding when the RUU sends 'rinfo' and 'rerase' commands to it, then the RUU gives up trying.
You can backup the radio ROM from another device with "d2s 60000000 00800000", and theoretically you should be able to load it into yours by using "L" command... but I'm not experienced with universal bootloader and can't say for sure if this will work and the right commands to do it... so please wait until someone reads this and can help you more than me, or research by yourself if you have the time to do it

Brick Hermes, stuck at WM6 Screen, help!

Recently tried upgrading my SPV M3100 from WM5 to black WM6. Everything was going fine and I had installed the following
SPL (Bootloader) version 2.10.Olipro (HardSPL v7)
Radio version 1.43.00.00 (optional)
Was updating to ROM version: Windows Mobile 6 LVSW 160607 when USB cable was disconnected before installation ands I am now left with WM6 screen only
Can anyone help?

If you stuck in the wm6 boot screen and have flashed HardSPL 2.10 already you can just enter the bootloader and reflash your ROM again. Why do you use nearly 6 months old ROM (LVSW)?

Did you try to reflash the ROM?
Just switch to the bootloader and run the update again.
If the updater is complaining about "Not able to do so" you might need another ROM, but that method worked to or three times for me.
Cheers,
Jago

tried raflashing but activesync won't pick up phone

you do not need active sync to pick it up. Just enter the bootloader and run RUU.

how do you reflash without activesync?

Read this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick

richard_g_johnston said:
how do you reflash without activesync?
Click to expand...
Click to collapse
Simply - flashing process itself is not done by the Active sync (its icon is grey when flashing). I have tried to flash a ROM this way and it works. You just have to input correct values to the RUU yourself. Bootloader is the tri color screen. You can access it by holding power and ok button while using the stylus to soft reset the device. Hermes will pick up the usb connection.

Please read the WIKI and flash an original WM6/WM5 rom before attempting to flash a cooked rom.. then make sure you know what you are doing before flashing the cooked.

tried both
http://wiki.xda-developers.com/index...Hermes_Unbrick
http://forum.xda-developers.com/showthread.php?t=286755
still no joy
my device
IPL-1.04
SPL-2.10.0lipro
how do u run RUU in bootloader mode?

richard_g_johnston said:
tried both
http://wiki.xda-developers.com/index...Hermes_Unbrick
http://forum.xda-developers.com/showthread.php?t=286755
still no joy
my device
IPL-1.04
SPL-2.10.0lipro
how do u run RUU in bootloader mode?
Click to expand...
Click to collapse
Put your device into bootloader mode.
Connect it via USB to your PC.
Run the RUU on your PC (like if you had Active sync working).
Flash the ROM.
(should work with all cooked ROMs)
Update: I tried it now with the Schaps 4.20 - it is working.

When you run ruu it should create ROMUpgradeUt.exe if it says it fails to find the device just run this. I usually take a copy before clicking to close the error box.

where do u locate RUU.exe
sorry I'm not an expert in this

RUUWrapper.exe should be in the folder with the image you are flashing. Sorry if I confused you saying ruu.

When you download the cooked rom it comes in rar or zip containing 2 files - one with extension .NBH and the second one is RUUWrapper.exe (resource upgrade unit), unpack them to one folder and run RUU.exe Be sure to flash only ROM for your device otherwise you will kill it for good.

tried running RUU but get error 260, i.e. cannot pick up phone on USB

See post 12

yeah, tried running ROMUpgradeUt.exe, but still no joy

markafreeman said:
See post 12
Click to expand...
Click to collapse
If this does not work for you - then you can use flashing from the SD card (no USB needed for this kind of flashing) . But try what markafreeman suggests first.

Lets try some troubleshooting:
Whne you connect your device in the bootloader (red green blue screen) to your pc what does it say?
In the white part of the screen on your device it should say USB - then it will work.
If not you can still try flashing the ROM from the SD card - you will need a card reader though for this kind of flashing.

Cant flash, ERROR 246

First of all, hi, i was reading a lot from this forum, and i must say, im impressed. Nice job!
Anyhoo, im running WM 6.1 (Lite) (http://forum.xda-developers.com/showthread.php?t=364031) on my HTC TyTn.
Now id like to flash it into, i dunno, the full version, or 6.5, or something else, but it wont.
I connect it through active sync(on my desktop pc), and i run 'Force Using Safe SSPL', i get the error : ERROR 246. The Update Utility cannot get response from your PDA Phone. Please check that your USB cradle/cable is connected properly between the PC and your PDA Phone. And also check your PDA Phone.
Click 'Exit' to quit.
I tried to run SPL-2.02/2.10/2.30 and then it goes into bootloader, and at 1% it says 'file corrupted'.
I tried those things on my laptop, too, but still the same problems.
Can anyone help me?
Rgrds

Install NetFrameworks from v1 to v3.5 make first your device is runing a functional rom.... or your rom... then perform the Hardspl v7 by olipro hardspl 2.10 and then try to upgrade some other... the fact here is.... how could you have 6.1 and now you are trying to make hardspl... oh bTW dont use SSPL please you gonna damage your device if it is not ready damaged.

Do i install NetFrameworks on HTC or on my PC?
Why not use SSPL? Which option should i use?

Do i install NetFrameworks on HTC or on my PC?
Why not use SSPL? Which option should i use?

hi,
when i try to perform the Hardspl v7 by olipro hardspl 2.10 i the following error:
Error 206 update problem
http://img97.imageshack.us/img97/107/48319879.png
please help me

nvr, worked it out.

Try this,
1. Make sure you have HSPL 2.10 or New Bootloader
2. Put Your device into bootloader mode (Until there a "SERIAL" in the bottom of ur device), connect it to PC (Now "SERIAL" change to "USB")
3. Run 838Pro_SEA_ENG_WM6_Upgrade_20070712 (official ROM or U can RUN other official ROM can be found on www.htc.com ), don't click "AUTODETECT",
4. Checklist the option button of SPL-2.02/2.10/2.30 New Bootloader and Is it Hard-SPL?, after that just click next2 until flashing started
5. If it didnt work repeat step 1-3 and checklist the option button " Force Using Safe SSPL " then follow all flashing step
6. Run AT&T Strip, link: http://www.4shared.com/file/61372397/e2bf76c0/official_ATT_WM6_striped.html
7. Flash WM6.5 ROM you want
Hope its usefull cause I use this when my hermes couldnt load and every flashing it's stuck on 1%
Good Luck

ksemeks said:
nvr, worked it out.
Click to expand...
Click to collapse
I'm having similar problems too, Please kindly share how you worked it out.

HardSPL + MTTY, an almost bricked HTC Diamond!

I really need some help!
I was following the the post The DEFINITIVE MTTY Thread!! REVISED 02-11-09 and I made a mistake as follows;
blanktruth said:
Ok, first of all I did not think that it was this dangerous to use MTTY!.
I followed everything and came to these lines
---------------------
Cmd>task 8
Cmd>
---------------------
But after Cmd>task 8 my device restarted immediately before the second line Cmd> appears and I panicked and disconnected my device and pushed the wrong buttons while "Touch Diamond" logo was on the screen.
Now, nothing happens. I can not start from the beginning because I can not start the bootloader by pushing Vol Down and the small red reset button...
Is there anything else left for me to try? Or should I throw my HTC to garbage?
Click to expand...
Click to collapse
Now, I do not know how, but I brought my HTC to bootloader mode and now I can see it via MTTY. But I mistakenly formatted the Internal Storage while I was trying to bring my HTC to bootloader.
Is there any way to upload the DIAMIMG.nbh file to Internal Storage? Or should I follow a different way to save my HTC Diamond?

i have the same probnlem!! with my diam300
my bootloader show not Diam300 64m but only 64M on the first position in 3color mode... plz help

Connect the Diamond and run the customruu.exe from your desktop, this should work.

how to connect if i used mtty... its clear everything what i have on device storage and in bootloader canot start stock or developed rom...
if i want start hard spl its say invalid model it....

blanktruth said:
I really need some help!
I was following the the post The DEFINITIVE MTTY Thread!! REVISED 02-11-09 and I made a mistake as follows;
Now, I do not know how, but I brought my HTC to bootloader mode and now I can see it via MTTY. But I mistakenly formatted the Internal Storage while I was trying to bring my HTC to bootloader.
Is there any way to upload the DIAMIMG.nbh file to Internal Storage? Or should I follow a different way to save my HTC Diamond?
Click to expand...
Click to collapse
The only thing to do now is to flash back a stock ROM or use a custom ROM with the RUU.

Solved!...
Dom1n8tr1x said:
First of, your device is supposed to soft-reset after the "task 8" command and you should have been holding down the "Volume Down" and "Back Buttons" to begin flashing your new ROM. The whole idea of using MTTY is to format your Main Storage and flash a new ROM. Therefor you should have loaded the ROM that you wanted to flash onto your Internal Storage.
Click to expand...
Click to collapse
Thank you for your reply.
Actually I had uploaded the ROM to my internal storage, but during trying to bring my phone to bootloader mode, I formatted the internal storage...
Anyway, what I did now is, first I opened the USB Connection feature from ActiveSync, and then used CustomRUU.exe to Flash the ROM...
Everything is solved now...
Thank you very much all...

ilijan said:
how to connect if i used mtty... its clear everything what i have on device storage and in bootloader canot start stock or developed rom...
if i want start hard spl its say invalid model it....[/QUOT
bootloader is all you need to revive the phone
connect it to usb in bootloader mode and just install an oficial diamond rom from an windows xp pc.
it's easy
Click to expand...
Click to collapse

plz write here step by step guide how you solved

How it was solved...
ilijan said:
plz write here step by step guide how you solved
Click to expand...
Click to collapse
Actually the most crucial part was to bringing phone to boot loader mode. And I think I managed that by pushing the Volume Down and Back (the arrow pointing left) buttons immediately after restarting my phone. And I had to do this after taking out the battery and putting it back after 5 sec.
When I pushed these buttons at the start up the phone tried to install the ROM from my internal storage, but as I explained I had deleted it by mistake. Therefore it could not find the ROM. I disconnected my phone from my PC and the screen started to say something like Retrying USB connection or waiting for USB connection, something like that.
I restarted my PC in Digitally Signed feature disabled by pressing F8 during start-up. Reconnected my phone to PC (the screen of the phone was still blinking as waiting or retrying usb connection). And voila the phone screen changed to boot loader mode...
The rest was easy. I opened the USB connection feature from ActiveSync and used CustomRUU.exe with a ROM to flash my phone...
That is all...

1. plug phone in to computer in bootloader
2. run customruu or stock from rom update on computer
3. wait for rom to flash to device
4.???
5.profit

but my booloader dont show model ID: DIAM300 64M what i had befor
and show me only: 64M
and any flash error with invalid model id, i canot flash, rom, stock rom, or hardspl...
understand me.. im not totaly noob... i used mtty X times... but now have this probles

can somebody help me?
my diamond dont have model id...
before i had in bootloader mode DIAM300 64M model id, but now i havent got... its show only 64M,
every rom flash stopped at 1% cose model id error,
every hard spl falsh finished 100% but after flash when device restart write model id error...
i cant do anithing... can somebody help me?

For everyone facing problems after flashing his/her device, take a look at the link in my sig.
There you can find a guide to restore your diamond.

you dont understand me..
i canto flash any rom any hard spl becous my diamond dont have device ID...
in bootloader dont show DIAM300 64M but only 64M
after all flash say error mobile ID...
i try mtty, hard reseted, soft... and nothing
after start its show me only first stock screan, the red text on the right bottom sight dont start: 1.17.25.14
2.100000
geny d2x
its maybe wrong but i forgot what waz here...
how can change device model ID? form 64M back to my stock DIAM300 64M?

Try another version of Hard-SPL, some people report that 1.40 not fully works.
I suggest you try 1.94 Olinex.

my diamond is death... if somebody know how can heal it... plz write me...
my device ID is missing... so i cant flash any rom, any hard spl, any radio...

try this? http://forum.xda-developers.com/showthread.php?t=409425&highlight=invalid+model+id

im not sure but i dont think one can brick his/her phone after hard spl, thats the reason of hard spl in the first place that u dont brick it. boot loader is always present

Guide
if you are using Windows XP try the following steps:
Connect your device to your PC
In Active Sync > connection settings > check Allow USB connections (which you have un-checked while doing MTTY)
Find a ROM with CustomRUU.exe / diamond wrapper
Now enter into bootloader mode(forget about the device ID)
Go to customRUU.exe and run it
Follow the ROM installation steps
This will help you installing your new ROM.
I had a similar problem and i resolved it by follwoing the above steps.

Guide
if you are using Windows XP try the following steps:
Connect your device to your PCIn Active Sync > connection settings > check
Allow USB connections (which you have un-checked while doing MTTY)
Find a ROM with CustomRUU.exe / diamond wrapper
Now enter into bootloader mode(forget about the device ID)
Go to customRUU.exe and run it
Follow the ROM installation steps
This will help you installing your new ROM.
I had a similar problem and i resolved it by follwoing the above steps.