Hi, i tried all HardSPL Versions i could find, but that happens every time:
- The ROM Upgrade Utility starts,
- i check all the answer boxes, until the diamond asks if the bootloader program is ok and i push the button.
- the Bootloader starts (3-colored screen), and the progress bar at the top of the screen comes up, but shows 100% after a few seconds.
- The ROM Upgrade Utility says Upgrade is finished and the Diamond resets, but shows still original spl Version.
I Installed net 3.5 compact, does not help.
Yes i read the instructions and i propably did ROM Upgrades a dozen times in the past years, but i am still clueless. Plz help.
The Modifier said:
Hi, i tried all HardSPL Versions i could find, but that happens every time:
- The ROM Upgrade Utility starts,
- i check all the answer boxes, until the diamond asks if the bootloader program is ok and i push the button.
- the Bootloader starts (3-colored screen), and the progress bar at the top of the screen comes up, but shows 100% after a few seconds.
- The ROM Upgrade Utility says Upgrade is finished and the Diamond resets, but shows still original spl Version.
I Installed net 3.5 compact, does not help.
Yes i read the instructions and i propably did ROM Upgrades a dozen times in the past years, but i am still clueless. Plz help.
Click to expand...
Click to collapse
Is it a U.S. version Diamond?
http://forum.xda-developers.com/showthread.php?p=2963492#post2963492
Stupid me
Hi, now i tried the ROM Upgrade (not the HardSPL) and it works. Seems that the HardSPL Upgrade worked from the very beginning, but i got fooled by the T-Mobile start screen still showing 1.93 (at the bottom of the screen), and the ROM Upgrade Utility also told me that the current ROM version is 1.93.something.
... ok Upgrade finished, says 2.03.something now so something changed after all.
... Yep thats the new ROM, i made it.
But after the soft reset theres is still the T-Mobile start screen withe the magenta dots i dont get it: new ROM, but still T-Mobile Logo???
ROM Version is now 2.03.401.2 WWE , does that mean v6.4FullHDTFl.nbh is installed?
Related
Hi,
First, I ran some tests on my kjam. The kjam came default with the kjam rom on it, naturally. I wanted to CID unlock this phone, so I downgraded the rom to button's "beer glass" splash screen rom. Then I was able to run aWizard successfully to CID unlock the phone. I then upgraded back to the original kjam rom. Both the downgrade and the upgrade went smoothly.
I then found out I wanted to customize my splash, so I downgraded again. I customized the main splash (not the HTC one) using aWizard. Worked like a charm. I also ran some extra itsme tools to read and write from rom in some locations I needed access to.
Everything was working great at that point. But the downgrade ROM didn't properly respond to some of the printed keys on the kjam keyboard, so I thought I should upgrade again. However, this time, I decided I want to keep my splash etc., so I tried to upgrade only my radio and OS rom, as backed up by aWizard previously from the original kjam ROM. I used aWizard to restore the selected areas of ROM, rather than the RUU tool.
I upgraded the radio ROM, didn't reboot the device to keep the radio and OS in sync, upgraded the OS ROM, just as that was happening, the phone received a phone call (or text message, do not know which), and hung. While the aWizard eventually completed the upgrade, the phone did not reboot or "un-hang" itself after aWizard displayed success (there was no error on the console window).
So I soft rebooted the phone. The splash screen came, but without a GSM version on it. I was like, "shoot!", something bad must have happened, lets just put the full kjam rom on this, and get it over with - never mind the custom splashes. So I went into bootloader and applied the kjam rom.
Now it displayed the GSM version as well on the splash screen, but again, it never left the splash screen. I was like, again, "shoot!", lets just go back to that old downgrade ROM with the funny keyboard, then we can figure this out again. So I went into the bootloader and applied the downgrade ROM.
Alas, the beer glass splash screen remained hung as well! And actually, since then, I've downloaded and installed ALL ROMs I've been able to find - ALL of them have hung.
My bootloader is still working fine and dandy...any idea why this might be happening? Was the problem in the phone call I received? In using aWizard without rebooting? In using aWizard at all? In trying to manually edit the machine ROM using itsme tools (mind you, those edits worked fine until I started updating the GSM/OS ROM)?
And oh, after hanging for a while on the splash screen, the phone screen starts flickering real bad (whilst still on the splash); in case that provides any help.
To clarify the bootloader situation a little more:
I've got FULL bootloader capability. I can mtty into it, I can write commands, I can install full new ROMs from the bootloader, etc. So this would seem to indicate my phone may not be a brick yet...its a brick that can display changeable wallpapers I even figured out how to draw progress bars and write text to the bootloader screen using MTTY commands. Fun, actually! Its a $700 etch-a-sketch pad
same probleme
Hi sir mimarsinan,
i have Qtek9100 with same probleme. Please give solutione for me to use phone again.
Thank you
Lionel
PS:
sorry for english
no good
Hi Lionel,
better not wait for him to reply to your request...
go here: http://forum.xda-developers.com/showthread.php?t=276963 and see solution that worked for many
good luck
Can any of you facing same problem post the reason(s) you believe to be responsible for the situation?
I think that in my case (yes, it happened to me too) was the fact that i flashed only OS chunk ending up with IPL/SPL 1.xxx and OS 2.xxx and i didn't use any RUU; instead i used an itsme program (podcread.exe)
cheers
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...
Hi,
I tried many times to install the hard spl version 1.34 on my new Diamond, but I have always the same problem:
- the program start
-it run since the boot loader mode appear on the screen
-then appear the progress bar and then ..... NOTHING.
I'm not new to flash and add new software, infact before the Diamond I had a Trinity flahed many and many times (Kaiser, Elegance Edition, etc....).
What can I do to solve the problem ? Really I don't undestand.
Please If someone has solved the problem post the solution.
Thank's
Post your SPL upgrade procedure, step by step.
We'll try to see where you might've gone wrong.
Did you sync your diam with active sync?
Did you try the spl-manual?
Maybe it is also good to give a link to the post you got the SPL from, so we know exactly which version you have (signed/unsigned).
I could not do it on my macbook pro either. IN teh end I resorted to boot camp and it worked fine
The procedure I made is still the same.
1. connect to activesync
2. start the exe
3. the screen of the diamond star the boot loader mode
4. appear the progress bar both in the pc screen and the diamond screen
5. the procedure stops and no data are transferred to the diamond
I tried all the three version of hard spl but the problem is still present.
The version of hard spl (from 1.24 to 1.34) is the one you can find in the first page of the forum.... belive me I did it many times in the past and I read very well the procedure suggested in the post.
However I will try to use boot camp.
Thank' s to everibody .
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???
hi guys,
have done the Hard SpL 1.3, added radio 1.5 and tried flashing the WWE JADECore + Manila2D 1.2 PTG version successfully but however the device does not go pass the HTC screen.
i then tried to flash Mary V3.7 lite but it does not load. Requires me to do recovery. However upon recovery , it shows by hello nasty - smart mobility. Stuck right there
i flash JADECore + Manila2D 1.2 PTG again... its loading and successful, however it still reboots to hello nasty - smart mobility and stop again.
Did i miss something out? i dont understand as i assume after the Hard SPL and radio , the rest of the rom can be flashed.
i Have tried several times with this rom and mary's rom
and have soft resetted several times.
Hope for some help.
any help at all?
try official ROM first
hmm okies..
could it be that i didn't unlock the phone yet?
now its in bootloader mode.
how do i flash the unlocker or official rom in?
i still have the original wm5 disc
tried flashing the RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship original wm6.1 rom but it stops at 28% everytime i try.
the custom roms flash nicely and everything boots up until the first or 2nd page then it stops.
i'm on SPL 1.3olio and i guess the radio doesnt matter but its a 1.5
anyone could help? i'm offering a small token via paypal for anyone who can walk my trinity back to the light..
Although Olipro's Hard-SPL 1.30 is the newest version, many people have reported not being able to upgrade their device with this version running. For now it is recommended to use 1.20 or Des' crash-proof SPL for successful upgrades
Click to expand...
Click to collapse
Found at http://trinityguides.info
have used SPLxploit and it changed to SPL 3.03000
what do i do next? install HardSPL? Install CID unlocker?
boot from SD?
someone ? anyone?