Develop Bugs

Can't flash anything after installing PDAVIET 2.07.06.PV

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)

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???

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]Phone does not boot, can only go to bootloader

Hi guys,
So i researched a few days before trying to root, install a custom rom (LeeDroid) and flash a custom rom
I managed to do it yesterday and everything was working fine. It is a really great rom.
But today I powered down my DHD and I can't boot anymore. The phone keeps rebooting (it vibrates one time, i see the HTC green logo, then a black screen, vibrates and so on...). The only way to stop this process is to hold the vol- key wich takes me to bootloader (so it appears the phone is continuosly powering off and on)
I already tried and bootloader is working fine, but when a I try any option that requires a reboot, the phone starts this process of power up and down.
Does anyone have any idea of whats happening?
Thanks guys!

Did you perm root your phone?
You could try reinstalling the stock rom too.

Go to bootloader, select recovery, do a full wipe and reflash your ROM. If you get a bootloop when you enter recovery, get stock RUU from XDA and use that.

Yeah I permrooted it.
But, how can I install a new rom without recovery?

I thought that you already flashed LeeDroid, and if you did, you have ClockworkMod recovery. But if that is not the case, use a RUU.

jkoljo said:
Go to bootloader, select recovery, do a full wipe and reflash your ROM. If you get a bootloop when you enter recovery, get stock RUU from XDA and use that.
Click to expand...
Click to collapse
Sorry man... I overlooked this post...
To better describe what I did:
-Radio s-off
Eng S-off
Instaled Leedroid (followed every recomendation he did in the post)
Flashed the radio he suggested
Got the phone working, tested a little bit, charged and then I powered off
When powered on again I got this bootloop
______________________________________
So, do you still recomend RUU?
Can I find any guide here on XDA?
Thanks!
edit:Forgot to mention that I get the bootloop even if I choose recovery on bootloader
edit2:
So after I came home I found de RUU post.
So here are some questions:
Mosts of the RUUs are in .exe extension, so I think that's the ones I should be looking for.
Can I download any version?
I'm currently downloading de WWE Asia version since my phone came from India. Only English (india) was available from stock, but I will not try to do anything before I'm sure of what to do.
When I plug the usb cable the bootloader changes to USB bootloader (or something like that). From the little that I found aboutt RUU I should run with the phone on that condition. Is that correct?
Thanks again, and sorry for the constant editing

Really sorry for double posting, but I need to update.
I managed to install the RUU. The program worked fine and I got the confirmation of installed rom, but when the phone rebooted it got stucked on the bootloop again.
Can this be a hardware problem? Is there anything else that I can do having access only to bootloader?

Okay, it is a hardware problem. The RUU wipes everything clean and installs a new system, and as it does not seem to help, the problem is definitely in hardware side.

After I was almost giving up I tried a different version of the RUU and the phone booted!
I already rebooted it a few times and it seems ok.
Thanks for the help jkoljo!

Nice job, which RUU did you use?
I think that there was a bad block in your phone's internal memory, which got fixed when the RUU wrote on it a few times.

jkoljo said:
Nice job, which RUU did you use?
I think that there was a bad block in your phone's internal memory, which got fixed when the RUU wrote on it a few times.
Click to expand...
Click to collapse
I used the Asia_WWE_1.32.707.1
I was trying to use a 1.72 version and still got the bootloop, but the asia version worked just fine.
I´m really glad the phone is working now, the only downside is that I´m back to the stock rom.