wierd flashing problem - P3300, MDA Compact III ROM Development

Hi All,
Got my artemis running 4.0 full, and USPL/CID unlocked.
I want to upgrade to 4.02 so I've downloaded it, but running the first batch file doesn't do what I'd expect: I'm activesynced, and it runs and counts up to 100% - the screen then flashes the linux tux logo and goes black, and the rom update utility fails to connect.
If I reboot my phone it's fine, but it doesn't bode well for the full flash.
Any suggestions? If it's a known issue and I should go straight into the full step2 flash, then fair enough, but I don't want to brick my phone...
Ric

Assuming your spl is still at version 1.11 there is no need to run step one again. You just go straight to step 2.
I have flashed loads of roms on my phone, always just step 2. My spl has stayed at version 1.11 ever since the first time it was done.
Hope thats helps......

cheers
...flashing it now at stage 2. seems to be going OK. anyone know why step 1 failed? does it only work 1st time and then once CID unlocked it doesn't?
do i really need to flash it twice to make sure it takes - i've seen this read but really don't understand the reasoning...

Related

Stuck in bootloader but with a very weird screen

Ok, I have been trying to update to the latest official O2 exec rom, specificaly: Xda_Exec_Upgrade_v113188
I flash the rom, radio, well all that comes wit it and I get this weird screen (see attached pic). What can I do? Any ideas?
Thanks!
fernandosaez said:
Ok, I have been trying to update to the latest official O2 exec rom, specificaly: Xda_Exec_Upgrade_v113188
I flash the rom, radio, well all that comes wit it and I get this weird screen (see attached pic). What can I do? Any ideas?
Thanks!
Click to expand...
Click to collapse
happend to me once.
if you have the same problem as i did, you have a rom update that was written badly into the rom memory.
what you see is supposed to be a splash image, but because the rom is not written properly - all you see is a bunch of bits.
the reason it's "stuck" there is probably the same reason - the rom is not complete and it can't load.
1. put your device in BL mode
2. flash to a different rom (including a radio rom), preferrably one with spalsh images (jwright's roms have those usually)
3. make sure the upgrade reaches 100%
4. wait 10 seconds, then unplug & hard reset
if that doesn't work -
search the wiki on how to use MTTY to clear and reset the partition table on universal ('task 28 aa' ? if i remember correctly, but please double-check)
then after doing that, repeat the steps i wrote earlier, and you should be fine.

Problems with Hard spl

Ok so i wanted to instal the new swiftblade 4.0 rom,its my first time.So I downloaded hardspl developers edition,well you know the unsigned hradspl.I did all the steps and when the process started in took only a minute if not less,after this minute it said that i have succesfully installed hardspl ,but it said it would take 10 minutes. My phone reboted and it was like a new diamond,I had to set it up again and the data was erased.So I entered bootloader mode and in didn't show me that i had hardspl installed.Can anyone help me?I want to install the swiftblade rom
sounds to me like you were successful in your upgrade usually takes a few seconds- not sure what hardspl you flashed but check back in the thread from where you got it to confirm what should say at boot mine says Olinex on it - hope this helps
It doesn't say the right thing, I have tried both Sighed and Unsighed Hard SPL Same old thing.Takes a few seconds and then says like it was successful ,but when I enter bootloder mode it doesn't say the right things

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

Fixed: Verizon Vogue Stuck at vzw splash screen

This is the first time I've messed with this phone I've flashed many different models in the passed but this is the only one that is giving me issues and the worst part is that its not mine so any hell i will greatly appreciate it.
Here is what i did read what ever i can to get more accustomed to this phone. and searched everywhere to help me figure out what i can do.
So i flashed the unlocker. Coke 2.31
after i did that i flashed nfsfan's 1.5 rom using usb cable.
no i cant get into the operating system at all it hangs at the vzw splash screen.
Is there a way to get this phone back to normal? i cannot connect thru activesync and when i tried to reflash using sd card it shows the loading screen for a split secon then goes back to the bootloader.
Please help its my bros phone i need it up and running asap.
Thank you
This post helped quite a bit
ArcaneMagus said:
Just thought that I would post what happened to my phone and the steps that eventually recovered it in case it helps somebody else:
My phone was stuck with "No Radio" on the boot loader screen and the SPL as "SPL-2.31.CoKe", but none of the 3.x ROMs would flash properly that I tried. So here are the steps that eventually recovered it (mostly...):
1.) I installed the ROM above from the tri-color screen (power+camera+reset). I still had no radio, but it was letting me past this and booting up to WM. http://forum.xda-developers.com/showthread.php?t=357762
2.) I then re-flashed the 2.31.CoKe boot loader (not sure if this step is necessary but listing what worked...)
3.) I tried to install RUU_Vogue_VZW_WWE_3.14.605.1_Radio_3.37.78_Ship.exe but it failed at 10% restarting to RUUNBH screen and the installer gave me Error [290]: Invalid Command
4.) I then tried to install the latest sprint ROM straight from the HTC site:_Touch by HTC (Sprint)_RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_2_Radio_3.42.30_AM_NV_2.04_Ship this looked like it was going to fail at the same part the Verizon rom did as it rebooted at 10% to RUUNBH screen, but the Sprint installer did something (I heard the computer lose and gain connection multiple times) and eventually it went right back and continued on from 11% and finished successfully.
5.) Rebooted and I had a radio now! Rather then risking trying to install the Verizon ROM again I went straight to the custom ROM I had originally started out with: NFSFAN 6.5 V6 which is working fine for me, except the GPS which is what started out my adventure of the last 3 days...
Just a note: for all flashes except the final one I simply waited till it was at the "Tap the screen..." stage till flashing. I never let any ROM but the final one run it's customization.
Click to expand...
Click to collapse
The above method works on a Vogue that is stuck on the bootloader screen with no radio.
Or if you get a rom to install and it stops at a windows screen that says no radio.
the only difference i tried was i didn't use the HTC Official Sprint rom, as i could not find it.
I used this rom.
RUU_Vogue_4350_ALLTEL_WWE_3.10.671.1_RS3.42.30_NV2.02_PRL30031_SHIP.exe
I let all customizations run on the last rom update.

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.

Categories

Resources