imate kjam won't boot past splash - Upgrading, Modifying and Unlocking

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

Related

recovering the brick xda mini s

I tried to update the rom on my wizard, however it seems like I have basically messed it up beyond repair. I followed instruction to recover to factory default by pressing voice and comm button. I do get the screen where it says to press send in order to format. But, when I press send button -- the format fails. I have updated the rom by using CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe. It did update but wizard will not continue with boot process, it is stuck at the initial screen with ipl/spl screen
IPL 1.06
SPL 2.26
GSM -- I cant remember,
OS 1.5.x
Is there any way of recovering it -- or this is my brick for time being, until Linux is made to load on it? I would appreciate any help -- this is driving me crazy.
Thanks in advance.
Nick.
follow the instructions here,
http://forum.xda-developers.com/showthread.php?t=285435
also just try flashing you original rom again
if you have a boot screen, it's not a brick
nbhanji said:
I tried to update the rom on my wizard, however it seems like I have basically messed it up beyond repair. I followed instruction to recover to factory default by pressing voice and comm button. I do get the screen where it says to press send in order to format. But, when I press send button -- the format fails. I have updated the rom by using CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe. It did update but wizard will not continue with boot process, it is stuck at the initial screen with ipl/spl screen
IPL 1.06
SPL 2.26
GSM -- I cant remember,
OS 1.5.x
Is there any way of recovering it -- or this is my brick for time being, until Linux is made to load on it? I would appreciate any help -- this is driving me crazy.
Thanks in advance.
Nick.
Click to expand...
Click to collapse
Hiya.I don't know if it could work on an American Wizard.But I have a ROM that worked on mine.Mine was a o2 Mini s from the UK.If you manage to put it in bootload mode then there's a way out for it.
Just let me know if u can. My email: [email protected]
i have is xda o2 mini too -- I had bought it on ebay. please let me know how to solve that. when I try to format -- I get format failed. I am stuck now. it wont boot nor do anything
thanks
nbhanji said:
i have is xda o2 mini too -- I had bought it on ebay. please let me know how to solve that. when I try to format -- I get format failed. I am stuck now. it wont boot nor do anything
thanks
Click to expand...
Click to collapse
do you have an 'xda mini' or an 'xda mini S'?
o2 xda mini S -- similar to wizard or cingular 8125
if you can get into bootloader (hold camera button and use stylus to reset) you can flash the original rom from there
I dont have original rom saved. I bought the phone on ebay. I am able to update the roms -- but again it just hangs at the point of splash screen. problem began -- when I was using shelltool to upgrade to wm6 and my cell phone ran out of battery. I then tried to recover using formatting -- which it fails. I can update the roms -- from custom, to love to wm6 but it just hangs at the splash screen.
Logically it seems that it cannot find OS anymore. I get the blackscreen that has HTC logo on top left and diagnostics with oks on everything, then splash screen comes on and it just seats there.
any ideas -- I would be thank ful for that.
Nick.
if the battery is the problem, charge it outside of your wizard if possible.
are you cid unlocked?
is it g3 or g4?
what brand is your phone? try to download the rom from their website and flash that
I got another battery and got that working -- like I said, I can update the roms but it still hangs at the splash screen. it is g3 and according the to manual that came with it -- it is german model. I downloaded the rom from the o2 site and tried to apply that -- it fails with error # 300
quoting from the ruu read me file
"error [300]: invalid update tool
this error message will appear when you use the incorrect ruu version to upgrade"
are you CID unlocked? because it seems to me that, that is the reason

Screen fades to black when trying to flash ROMs

Hello everyone.
Apologies if this has been addressed somewhere already, but if this is the case, I was unable to find it.
I have a French Orange Diamond, which I was able to flash w/o problems with Hrad-SPL 1.30 by Olinext, and then with the RUU_Diamond_HTC_Europe_1.37.401.3_Radio_Signed_Dia mond_52.26a.25.09_1.00.25.03_Ship Rom. This worked flawlessly, and I have been a very happy camper since!
Tonight, I tried to upgrade the radio ROM to 1.00.25.05. To do so, I first installed the developer version of Hard-SPL 1.40 by Olinext, which went very well. Then, I tried flashing the radio, and instead of getting the bootloader, I got the colorwheel, and almost immediately afterwards the phone screen faded to complete black. After a little while, the ActiveSync (4.5) window disappeared from my XP SP3 PC screen, and the phone waited there until the flash process timeed out and it entered recovery mode. This happens every time now, and I am always able to recover perfectly.
Thinking it might be related to the Hard-SPL, I flashed back to version 1.30 by Olinext, and then even reverted back to the stock 1.37. Whenever flashing an SPL, the screen still fades to black, but the process completes ok, whereas whenever I try to flash the radio, it will always time out with an Error 262, apparently comms-related.
Has anyone encountered this in the past? Anyone know what/how to fix?
Thanks!
P.S. I forgot to mention that if I copy the EnterBootloader.exe onto the phone and run it from there, the screen will also fade to black in exactly the same way.

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.

ROM flash gone bad?

Brand new GSM TP2 with Dutch (NL) language ROM
I installed the Olinex HardSPL and checked it on the Bootloader screen.
I downloaded the AthineOS ROM and used the included CustomerRUU.exe file to flash the phone, running it and the ROM from my PC. All went without a hitch, finished at 100% in a minute or two, but now the phone won't get past the initial TOUCH pro 2 screen, the one with the red RGD rows at the bottom of the screen.
Please tell me I didn't brick it and it's an easy fix. What went wrong?
Same thing happened to me yesterday. The good people here showed me how to fix it. As long as you had HardSPL installed, you should be able to recover. See thread below for the fix:
http://forum.xda-developers.com/showthread.php?t=566371
Thank you! I did confirm I could go into bootloader and I did see that the HardSPL is installed. I even tried to reflash the ROM I used the first time. No luck there, though the RUU ran all the way through again. It stops at the point that the phone tries to reboot. I'm now downloading the Stock European WWE ROM to see if that will bail me out. I guess there's still some hope.
Success!!! As you said, Thank you, thank you, thank you, thank you

Categories

Resources