Develop Bugs

imate kjam won't boot past splash

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

New Dash, Trouble flashing to WM6.1 *please help!*

Alright got a new dash and carefully began to flash to 6.1 from 5.0.
I first did a hard reset.
Then ran the app unlock.
Reset device.
Downloaded Ricks WM6.1 and ran the auto.bat
Followed instructions.
Screen turns white.
Run the ROM updated.
ERROR: Connection or something..
Turn off device and enter boot mode by holding camera.
Downloaded the Dash_Software_Update_1.22.531.4.exe and ran it succesfully
Phone wont turn on at all..
I can enter boot mode though with the camera button.
What should I do? The original dash software doesn't even seem to install correctly and I cant CID unlock because I can only boot into the tri-color screen. Help is much appreciated.

T-Mobile wm6 ROM
proph3t said:
Alright got a new dash and carefully began to flash to 6.1 from 5.0.
I first did a hard reset.
Then ran the app unlock.
Reset device.
Downloaded Ricks WM6.1 and ran the auto.bat
Followed instructions.
Screen turns white.
Run the ROM updated.
ERROR: Connection or something..
Turn off device and enter boot mode by holding camera.
Downloaded the Dash_Software_Update_1.22.531.4.exe and ran it succesfully
Phone wont turn on at all..
I can enter boot mode though with the camera button.
What should I do? The original dash software doesn't even seem to install correctly and I cant CID unlock because I can only boot into the tri-color screen. Help is much appreciated.
Click to expand...
Click to collapse
Put T-Mobile's wm6 ROM back on your device and start all over again.

proph3t said:
Alright got a new dash and carefully began to flash to 6.1 from 5.0.
I first did a hard reset.
Then ran the app unlock.
Reset device.
Downloaded Ricks WM6.1 and ran the auto.bat
Followed instructions.
Screen turns white.
Run the ROM updated.
ERROR: Connection or something..
Turn off device and enter boot mode by holding camera.
Downloaded the Dash_Software_Update_1.22.531.4.exe and ran it succesfully
Phone wont turn on at all..
I can enter boot mode though with the camera button.
What should I do? The original dash software doesn't even seem to install correctly and I cant CID unlock because I can only boot into the tri-color screen. Help is much appreciated.
Click to expand...
Click to collapse
I think you will need to upgrade from WM5 to WM6, then flash again up to WM6.1 ... been doing this a while now and have never seen much success with jumping generations.
I'd guess this is because of IPL/SPL versions.

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.

Diamond Stuck up at the welcome screen

Dear Sir
My diamond got stuck up at the welcome screen or else in the alignment screen. I've flashed many roms number of times before but this time this happened after a hard reset- using Macadam 1.2 (latest).
My bootloader reads - Diam140 MFG 64M; SPL-1.40. Olinex. After this I've flashed back to the latest indian stock rom i.e. First to (RUU_Diamond_hTC_Asia_India_1.93.720.4_Radio_Signed_Diamond_52.62.25.34_1.13.25.24_ShiP) but know result & (RUU_Diamond_hTC_Asia_India_1.93.720.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.07_Ship_R). After going through the forums- I understood that I've to step down to stock spl. But even after successful flashing, the boot loader shows the same- "SPL-1.40.OliNex".
I'm unable to use the jump SPL, because I can't pass through the alignment screen. Please help, is there any way to JUMP SPL without operating the phone.
Or else how can I come back to the stock spl.
Please Help.........................
Regards
Furthermore, I've tried using mtty to following the procedure:
Correct sequence is as follows:-
1. Launch ActiveSync on PC
2. Go to connection settings
3. Uncheck the Allow USB Connection
4. bring the device to bootloader. AND connect to the PC.
5. Now, run mtty1_1_.42_538 on PC.
6. CMD>task 29
7. Flash the ROM of your choice
Then flashed the stock rom again. But the problem remained.
jockyw2001 - suggested me on PM to do- "in mtty: set 16 0 then reboot'- but nothing happened. Or I didn't follow the correct steps... can anyone explain & help please....

[UPDATE]where do I get the commands for mtty
Can anyone tell me the link where I can get the commands to be used in mtty... Is there anyway to bypass the screen alignment part during start up after a hard reset.... how can I JumpSPL in a handset where the touch screen is not working.. but the screen is not completely dead, i.e. on tapping the "+" sign is moving after around 5 or 7 mins of the tap...
Please help guys.... I'm waiting to be rescued by some WM wizard from this great community.....
Regards

wizards- all'r failing or what- very few people with clear funda
cmonex please help....

hi man
i had the same problem, with all the rom around
than i understand that the problem was the radio rom
try to flash the lastest radio..i use the 1.13

Flash a Rom without screen alignment
Hi
If you on bootloader and you have 1.40olinex then flash a 1.13 radio then flash a Rom without Screen alignment process. It might help. Good luck