Can't flash anything after installing PDAVIET 2.07.06.PV - P3600 ROM Development

I've been using Mun_rus's WM6 ROM for quite a while and seeing that PDAVIET's rom was built on a more recent WM6 ROM I decided to flash PDAVIET 2.07.06.PV.
Since then I cannot flash anything on my Trinity, the update utility starts and when the progress bar reaches around 84% half the screen on the Trinity goes funny. The progress bar on the PC reaches the 100% (while the screen on the Trinity goes blank slowly slowly) but upon restarting the device PDAVIET ROM loads up again intact as if I have just done a soft reset!
I've even tried flashing WM5 again but without any success.
Trying to flash Hard-SPL does not work either and I'm running out of ideas now :-( Anyone else has this problem please? I would love to try flashing a ROM with an original IPL SPL but cannot find one. My bootloader currently says IPL 1.5/SPL 9.99.CP.

Yes I am having a similar problem. It starts to flash then stops reboots and on my pc says image fiile corrupted. I have re downloaded and extracted the files but it happens everytime. However. My trinity when it reboots is stuck in the splash screen.

I had a similar problem, though not quite what you're describing. Try removing the Mini SD (storage card) before flashing.
Also, try entering bootloader fisrt before before flashing from PC.
Hope that helps.

i have the same problem...
i get 100% done and than it is still the old one..

Well, I have now sorted it. Go to this link read first post and download and use the unbrick.
http://forum.xda-developers.com/showthread.php?t=308691&highlight=splxploit-windows
I had to run it 3 times but it has worked and now I have flashed a new rom on it and it is working fine now

deniser said:
Well, I have now sorted it. Go to this link read first post and download and use the unbrick.
http://forum.xda-developers.com/showthread.php?t=308691&highlight=splxploit-windows
I had to run it 3 times but it has worked and now I have flashed a new rom on it and it is working fine now
Click to expand...
Click to collapse
I've run the splxploit a couple of times as well. It seems to finish the process succesfully but the problem persists :-( And mine is not stuck on splash screen, the device boots normally, it's just that whatever I flash does not work. Any more ideas please?

I tryed the all i think, read the all forum up and down, started in different ways, but no rom of SSL apply...
What is that!
I am stuck with this rom?

Any of the pro cookers can help with this please? I just need to understand what could be wrong, not necesseraly a solution

capeli said:
I had a similar problem, though not quite what you're describing. Try removing the Mini SD (storage card) before flashing.
Also, try entering bootloader fisrt before before flashing from PC.
Hope that helps.
Click to expand...
Click to collapse
Hey many thanks Removing the miniSD solved my problem I flashed at least a 100 ROMS in my life and never bothered removing the memory card before ... but there you go

hi, i had the same problem. i flashed my trinity with original htc rom and after that when i tried to flash with any other rom it gave me success message after every try but in my phone there was still the same htc rom. i used that : http://forum.xda-developers.com/showthread.php?t=293632 AND IT WORKS. FROM THE MOMENT WHEN I USED THAT FILE I FLASHED MY TRINITY 2 TIMES WITH THE SAME ROMS WHICH DIDN`T WORKED PREVIOUS. you need to copy that file to your trinity and follow the instructions from the readme file. in my case i only opened it ,it started bootloader mode ,i disconected usb and connected it again and started ROMUpdateUtility with rom which i wanted.

interesting... so why does the miniSD card affect the flash?
kta- had you tried running sspl and then flashing during your failed attempts? (just curious)

Related

PV HERMES Rom Expired????????

Hello.
I have installed a PV Hermes WM 6.1 Rom.
It now says : thank you for using this software...etc
I think it was for betatesters, and now it shows only a splash screen, and i CANNOT install another ROM.
I tried to install by starting in BOOTLOADER, but it does not help.
What can i do???
emipop said:
Hello.
I have installed a PV Hermes WM 6.1 Rom.
It now says : thank you for using this software...etc
I think it was for betatesters, and now it shows only a splash screen, and i CANNOT install anothor ROM.
I tried to install by starting in BOOTLOADER, but it does not help.
What can i do???
Click to expand...
Click to collapse
I think I read somewhere (but have not tried), do a hard reset, and when the screen that says Tap to begin using your device pops up, start attempting to flash from there.
But they "should" flash from the bootloader screen.
I had exactly the same problem. Tried all the tricks to go back to the previous ROM. I also tried boog321's hard reset idea, but it just puts you back into the bootloader. HOWEVER, when I then went through the screen alignment process (just for fun), lo! it works!
The problem is that i can`t get inside windows anymore. It stays at the screen 3 seconds after power up. Is there a way to hardware reset?
emipop said:
The problem is that i can`t get inside windows anymore. It stays at the screen 3 seconds after power up. Is there a way to hardware reset?
Click to expand...
Click to collapse
Just flash a different rom dude!! probably a expired beta rom.
i have tried to falsh 4 differnt ROM`s. It makes 2% and says rom orrupter or something.
Tried installing via MicroSD card? I installed the same ROM a while back...
Hey. I just re-flashed right now after I installed an expired beta by mistake.
Start with the Hermes connected USB, showing the splash out of luck screen.
1. Hold both Power and the ok button on the left and then RESET with the stylus. It should go in tri-color mode
2. Flash a known good ROM
Good luck!
Bro just flash your ppc using other ROM (flash it in bootloader mode) when its in the hermes rom upgrade tap the (force using safe SSPL) it will do the trick.
I already said i did that.
After 1% it stopped and says : ERROR 270. UPDATE ERRROR: The image file is corrupted please check your update utility.
I have done this with 5 roms now.
Will try microsd install.
Hope you have Hard SPL, you need it for sd card flash...
I solved the problem with the bad ROM.
I downloaded an official rom from here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
I has done a clean install.
But i still can§t install another rom, from the forum.
Will try again.
emipop said:
I solved the problem with the bad ROM.
I downloaded an official rom from here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
I has done a clean install.
But i still can§t install another rom, from the forum.
Will try again.
Click to expand...
Click to collapse
Are you sure you have HardSPL installed and CID unlocked your device?

HELP! - Cannot flash bootloader away from SPL-0.41.coke

I have a major issue here. Please bear with me.
I flash my phone to the official 6.1 rom a few months back. Now I recently decided to try a custom rom by NFSFAN. So first thing was to flash the bootloader by IMCokeMan version 0.41. After doing that I flashed the custom rom. Once it booted up my phone kept reboot itself every few seconds or so. It turns out now that it was a battery issue, but I was sure the battery was fine and thought it was simply an incompatibility issue with the rom.
So I then tried to flash the official 6.1 rom back on, but it froze at 44% and then threw a 262 error after a minute or so. I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Then I thought I'd try the NFSFAN's rom again. So I flashed that. Once it successfully finished and started to load it freezes at the Telus splash screen and "No Radio" appears in red on the screen.
So this is where I'm at. I've tried to flash nearly every bootloader I could find and no matter what I do the bootloader always shows "SPL-0.41.coke". I can't flash any official rom including Telus, Bell or Sprint as they each freeze at different spots but consistently at the same spot individually (Telus at 44%, Bell at 30-some%, Sprint at 29%). I can flash custom roms as well as the beta wm6.5 rom but those don't fully load and give the "No Radio" error.
The ONLY rom I can successfully flash is an old 6.0 rom that someone dumped from a telus vogue. But in this rom under "Device Information" the rom is 1.11.661.1 and the radio version field is blank! And I cannot make data connections, as in I cannot connect to the internet, etc.
So my question to anyone that may know is: why am I having these issues with the radio version? How can I get rid of the SPL-0.41.coke bootloader?
And what can I do at this point? Any help from anyone is a thousand times over appreciated!
There's another copy of this thread at PPCGeeks.com:
http://forum.ppcgeeks.com/showthread.php?p=792095#post792095
-Chris
*********** bump-a-doo? *************
eeps! similar issue! did I brick it???
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
cbstryker said:
I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Click to expand...
Click to collapse
I've been reading through the ImCoKeMaN's unlocker sticky (http://forum.ppcgeeks.com/showthread.php?t=20370), and I noticed there is a "VERY IMPORTANT / Warning" referring to the 0.40 rom you used. Here's what it says:
If your carrier did not release a rom and you flash an exe of another carrier with the 0.40 unlocker you won't be able to flash ANY rom until unlocking again (this requires booting into WM)
Click to expand...
Click to collapse
then it points to this: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
Hopefully that helps you out.
esskay said:
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
Click to expand...
Click to collapse
hey, I answered this question of yours already over here http://forum.xda-developers.com/showthread.php?p=3526872#post3526872
Detroit Doug
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Viper Matrix Wireless said:
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Click to expand...
Click to collapse
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Detroit_Doug said:
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Click to expand...
Click to collapse
I answered his question on his thread. You forgot one thing though Doug. He doesn't have a radio. He'll need to flash back to stock before he flashes a custom. Doesn't this get frustrating???

Please help!!

i just loaded a new rom onto my diamond. after installation the phone turns on and displays touch diamond then sits there for about 20 seconds then reboots. its keeps doing it. what can i do?!! ive tried loading another rom but it seems to keep doing it.
When you put you phone into bootmode, does it still restart then?
And have you tried a hard-reset?
it did stay in boot mode, but once i loaded a new rom it did the same thing. i had to load a couple roms before it stuck and started working. thanks for your help.
bigk05 said:
i just loaded a new rom onto my diamond. after installation the phone turns on and displays touch diamond then sits there for about 20 seconds then reboots. its keeps doing it. what can i do?!! ive tried loading another rom but it seems to keep doing it.
Click to expand...
Click to collapse
Maybe this link will help to solve the problem: http://forum.xda-developers.com/showpost.php?p=3433851&postcount=22
Option 2:
If the link above method doesn't work for you, then just simply but your device into bootloader and flash a stock ROM then go back to a cooked ROM and everything she be ok.
Go Here to Find Stock Roms It doesn't matter which one you chose as the goal here is to remove the bloated ROM which happens from too many flashes.
hi, i know this post is a little old but MY DIAMOND IS DOING THE SAME EXACT THING!
i just started leaerning how to do all this, and the only HardSPL that worked on my phone was 1.24.
i updated to that spl, then i upgraded the radio but when i did the rom flashing event i am left with a messed up phone, resulting in only turning on and off, not getting past the touch diamond screen.
PLEASE HELP ME.
Guide to completely restore your messed up device
This little guide is made for newbies who are stuck after flashing images in a wrong way or flashing wrong things.
Note: This is only for GSM Touch Diamond!
This Guide does not include the MTTY Procedure!!
Q. What does this mean?
A. Well, if you are still facing some problems after following this guide, it's time to use MTTY.
Q. what is MTTY?
A. It's a flashing procedure before flashing a ROM, it actually formats your phone (you internal storage will not be lost) and then you are able to flash a ROM.
Q. When do I have to use MTTY?
A. You have to use it before every ROM flash. Before you proceed with step 14, you must read this! It's the only step you need to do it, except for the latest cutsom ROM flash.
Perform a hard-reset (Hold Center button + reset)
Go into bootloader mode by holding volume down and pressing the red reset button
A red-green-blue-white screen will appear. In the white part of the screen, there should be the word 'Serial'
Connect your phone to the computer.
If the word 'Serial' changes into 'USB', you succesfully connected your phone
Go to this link and download 'Unsigned-Hard-SPL-Diamond-OliNex.zip'
Extract it to an empty folder.
Run RomUpdateUtility.exe, make sure your phone is still connected
Follow the steps, check device for prompts after PC shows loading bar. it should go to black screen now.
SPL flashes, device automatically reboots, job done.
to confirm you got it installed, go into bootloader mode and verify the screen shows 1.40.OliNex.
note: you will not see the SPL version during normal boot, that is the OS version, not SPL!
Now you have re-flashed Hard-SPL, it's time to flash a stock ROM.
Make sure your phone is connected again
Download a stock rom (ie from here) and run the executable.
Follow the instructions, and be patient.
You're done now. You are now able to flash a custom ROM of your choice.
If you can't get your device to work, not my problem! If this didn't help your device is bricked. You'll have to return it to HTC.
And of course I am not responsible for any trouble you get with this guide.
Don't you understand some steps or do you still need help?
Try reading this. It is a great tutorial about flashing your device including the MTTY procedure.
If you still can't get a clue of it don't hestitate to PM me!
You can also add me to msn, see the msn icon to the right of my post.
when i tried to upgrade to 'Unsigned-Hard-SPL-Diamond-OliNex.zip' the progress bar on my phone and the computer go up to 100% in less than 2seconds, then it says 'error [270]: update error
the image file is corrupted. please check your update utility'
And on my devices bootloader screen it says 'upgrade ROM code error please try again'
devyn_ciara said:
when i tried to upgrade to 'Unsigned-Hard-SPL-Diamond-OliNex.zip' the progress bar on my phone and the computer go up to 100% in less than 2seconds, then it says 'error [270]: update error
the image file is corrupted. please check your update utility'
And on my devices bootloader screen it says 'upgrade ROM code error please try again'
Click to expand...
Click to collapse
Are you using Vista? If so, try it on another computer
Another problem could be that the package is corrupted. Try downloading it again.

Apparently I have severly bricked my S620.

I was attempting to change to ookba's 3VO ROM but the operation failed and the ROM did not install. I did get the recovery instructions screen and followed them but the phone did not reset to the previous ROM (NRGZ28's EnergyROM 52409). The phone hangs on the Windows Mobile screen. I have done the following -
1) Followed ookba's recovery instructions and gotten the tri-band screen. However whenever I try to flash back to the T-Mobile ROM (any version) I get Error 260.
2) Followed stylez hard reset instructions and gotten the reset screen but the phone hangs on the Windows Mobile boot screen. A hard reset does not occur.
3) Followed NRGZ28's "In Case Things Go Wrong" instructions and gotten the tri-band screen, however when I try to flash the EnergyROM (or any other non T-Mobile ROM) I get corrupted image errors.
4) I have used jockeyw2001's bootloader but get Error 260
Also, the power button does not turn the phone off. I have to remove the battery to get it to shut down. I think I have tried all the recovery steps I know if. If anyone has a suggestion or solution I would be most appreciative. Thanks.
The Rotagilla said:
I was attempting to change to ookba's 3VO ROM but the operation failed and the ROM did not install. I did get the recovery instructions screen and followed them but the phone did not reset to the previous ROM (NRGZ28's EnergyROM 52409). The phone hangs on the Windows Mobile screen. I have done the following -
1) Followed ookba's recovery instructions and gotten the tri-band screen. However whenever I try to flash back to the T-Mobile ROM (any version) I get Error 260.
2) Followed stylez hard reset instructions and gotten the reset screen but the phone hangs on the Windows Mobile boot screen. A hard reset does not occur.
3) Followed NRGZ28's "In Case Things Go Wrong" instructions and gotten the tri-band screen, however when I try to flash the EnergyROM (or any other non T-Mobile ROM) I get corrupted image errors.
4) I have used jockeyw2001's bootloader but get Error 260
Also, the power button does not turn the phone off. I have to remove the battery to get it to shut down. I think I have tried all the recovery steps I know if. If anyone has a suggestion or solution I would be most appreciative. Thanks.
Click to expand...
Click to collapse
Maybe its safe to assume you have a hardware issue? Since the initial flash and following consecutive flashes failed, maybe its a bad USB cable? I would try reflashing the shipped T-Mobile ROM from a different PC altogether using a different USB cable. Since your phone gets to the Bootloader (multicolor) screen means it's not bricked. Try different PC and cable hardware...
Will do. I did try another hard reset and the boot screen has sat for over 20 minutes without getting past it.
Or try flashin stock ROM via SD
you must flash to official rom to make any progress at this point. at least thats what i had to do when my computer auto-restarted in the middle of one of my flashes.
Fixed, thanks for the help.
bricked excalibur
how did you fix it cause i'm having the very same problem
Switched from a PC running Windows 7 to one running XP.
muga said:
how did you fix it cause i'm having the very same problem
Click to expand...
Click to collapse
Welcome to the forum
Also reading here would help http://forum.xda-developers.com/showthread.php?t=415225
Well that didn't work for me its stuck it the multi colour screen and pc not flashing it. When it does recognise and start to flash i see a count down screen like the one on pc but only stops at 3percent
muga said:
Well that didn't work for me its stuck it the multi colour screen and pc not flashing it. When it does recognise and start to flash i see a count down screen like the one on pc but only stops at 3percent
Click to expand...
Click to collapse
Muga, It's also happening to me. I had previous flashes with different roms Kavana's, rose, energy (6.1 release) and everything went well with no problems at all. But a few days ago, I tried to flash my excalibur with the latest release by NRGZ28 (energy rom 6.5) and what I think what happened was that I didn't run the unlock file aplications (since I didn't have to do it in the other flashes, because I already had unlock the phone with the first upgrade) that's the only explanation I can get. At the end, I came up with the frozen screen and I've tried the bootloader steps, original rom installation, hard reset with no succes at all. What I get is the same error you have.

[Q] Problems with bootloader [SOLVED]

I had 3.29 HardSPL, i used Android on nand for quite some time, after that i decided to flashed back to WinMo to check something out, in one of the guides, it told me to put the kaisimg.nbh and kaisdiag.nbh, (i had flashed back to WInMO several times but never included the Kaisdiag.nbh, since the guide mentioned it i thought it was something good to do)
i used the official WM6.1 and entered bootloader as usual... then my device reset in the middle of flashing...
When i tried again bootloader got stuck at 'Loading...' and the bootloader was now showing 3.34.000
Now i am unable to flash the windows ROM or HardSPL as they all got stuck in the bootloader at 'Loading...' also tried with bootloader in USB mode... nothing
Please help me... thanks in advance
BTW, luckily the android kernel was still functional and i can use it for now...
I posted this in the TyTn General Discussion section but since i got no reply for days, i reposted it here, so sorry in advance for the double thread.
Put the kaiser in boot mode, connect to a pc and flash an original rom from windows. Then reflash hard spl.
l1q1d said:
Put the kaiser in boot mode, connect to a pc and flash an original rom from windows. Then reflash hard spl.
Click to expand...
Click to collapse
Thanks for the reply... i tried this, dont know if i did something wrong but it still got stuck, i used the stock 6.1 asian, it was originally a swedish kaiser so do i need that particular rom?? i will try again...
I tried RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.rar but while it was flashing, it got to 1% on the computer and then the device just resets
It said Error [294]: Invalid vendor ID
the update utility could not be used for your PDA phone on my PC
Finally solved... i went to htc website and downloaded the update using my phones serial number... i successfully flashed back to WinMo using that ROM... now i can use hardspl again... thanks for all the help

Categories

Resources