Database Develop

k-jam, another brick in the wall (dead after rom update)

Hello folks,
Today I flashed with the ROM in thread 'T-Mobile USA 2.17 ROM (Custom)'. After it came up, I ran through the screen align and wizard. When it was all done installing extended rom etc it restarted on its own. After booting back up, everthing was really slow and there was no cell signal. The battery icon had an ! mark on it and when clicked, it says unknown battery. At this point everything keeps freezing and genrally not working including no activesync connection possible. I restarted into the bootloader and tried to flash again. It completed, but now I just get the tmobile boot screen, and eventually it restarts again, never completing the boot. This is when I notice that it doesnt seem to have a radio rom (GSM) version listed, but rather a gap where it should be. I ended up pulling the battery out and trying to get back into the boot loader again, and now I cant get it to power on in any way.
I guess that is enough said. The only other thing to note is that everything was working fine prior to the attempted update, I was merely hoping to get a performance boost, as I was using the original rom.
Any thoughts?
Thanks!
B. Ramsey

Fixed!
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.

No dice
After installing the 2.17 ROM, no more GSM, and same problems. I reflashed back to the previous and it works again..

Re: Fixed!
pterodyne said:
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
Click to expand...
Click to collapse
THANK YOU SO MUCH for posting this! I also had a brick because of the same setup - trying to use the custom TMOBILE ROM. I had the same symptoms you did - basically non-responsive and no radio stack and no USB connection. I was not getting anywhere with any other ROM. Now, at least I have a working device.
Still no AKU2 though
Let me know if you manage to get an AKU2 ROM on your device!

That's worrisome. Do you know if the CID unlock was successful? (I think it's scripted into that custom upgrader)
If you're feeling adventurous, you could try intalling the custom 2.17 Cingular upgrader I made (it's on the FTP server). If that's successful, then the problem is with the T-MO upgrader. Based on all the folks having success with that T-MO upgrader though, I imagine the only issue might be a corrupt download. If the Cingular upgrader results in the same behavior, then the problem is either with the CID lock or some odd hardware problem.
I'm truly perplexed by the issue you're having..sure wish I knew how to help ya.

Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
My device is a QTEK 9100. I was upgrading from the ROM on my device when I got it:
ROM 1.1.7.5 9/22/2005
Radio: 01.01.10
Protocol: 4.0.13.16
ExtROM: 1.1.7.105
My carrier is TMobile, so I figured the TMobile custom rom that was built off of the latest QTEK would be a good bet for me - but instead I ended up with no Radio.
I have the IMATE ROM you refer to - maybe I'll try to go to that as an interim step to get to the QTEK ROM I really want, since you had success with that method.
What I don't understand is why the Vanilla QTEK 2.17 (which is what I tried after the TMO Custom 2.17) gave me problems. I don't recall the exact error message, but basically it said it couldn't use that ROM on my device.

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
When you say it was already unlocked, don't you mean SIM unlocked? It would be unusual to buy a phone that is already CID unlocked.

I bought the unbranded k-jam from Simoncells.com. All I did was put my tmobile sim card in it and it worked. I guess I dont know the difference between SIM and CID unlocking.

Well theb that's where you went wrong, sim unlock refers to ur phone being able to use any world sim card...cid unlock refers to country Identification...if ur fone is not cid unlocked then wen u install foreign roms it will bugg up ur fone...dats wat happened to u and that other fellow pterodyne...I sim and cid unlocked my fone. ran the tmo 2.17 custom rom without a problem....plz do ur research on upgrading roms b4 u bash them...most factory fones don't come cid unlocked so I'd b surprised if urs did (tho it prolly came sim unlocked)...

Problems updating Radio ROM

Hi all,
I have a Spanish Vodafone P3600. (S300). I've run into problems while updating the radio ROM and several other things.
I've managed to change the SPL, all versions, no problem. Even the hard SPL. The problem arises with almost ALL ROMS and ALL RADIO ROMS. I put the PDA in bootloader mode and I begin the updating process. Well, it stays at 0% all the time, both in PC screen and PDA screen. When I am tired of waiting (more than 30) minutes, then I have to take the battery off. The PDA goes into bootloader and I have to apply the unbrick procedure.
I have only been able to put the FAMAN 3.5 Spanish ROM (WM6) so the PDA works when I unbrick it. However, it does not have RADIO ROM and it shows "no GSM" at boot and obviously I cannot use it as a phone.
Is it broken? Why can't I flash the radio ROM? Somebody with a similar problem?
Thank you all very much in advance.
Best,

Unsolvable problem
Thanks all for the feedback. Pof was kind enough to address the problem.
I ditched the radio bootloader (not the regular bootloader) and a a result I cannot flash the radio. It seems that the phone has to be sent for repair.
"if it works... don't touch it" I should have paid attention to this

Please help, I think I bricked my PPC! :(((

I tried flashing WM6 on my QTEK 2020, but I had the wrong version. I begun the upgrade having it on bootloader and after a while an error about updating radio occured. Now, my PPC powers up, but it gets stuck on the beginning with the "QTEK" logo with the clouds and the blue led that indicates the bluetooth is activated. Neither soft nor hard reset does anything and I can't flash the original rom through bootloader (I can boot the PPC in bootloader).
Does anyone have any idea please?

If you posted this in the Qtek2020 (Himalaya) forum, you might get a quicker response.

Thread moved out of the BA section

Maybe you should try reflashing. Just flashing a new ROM and then just a radio might do the trick.
How did you flash? With the No_ID?
And what were you trying to flash? A BA ROM while you have a HIMA?

OK!
It's ok now! I flashed the WM6 Rom having my PPC on bootloader and everything's fine!

Its very good to hear that..btw which rom did u flash before and what have u flashed now

I really can't remember what the previous rom was, but it was for another brand! It was stupid to flash that one! The one I have now is this:
http://forum.xda-developers.com/showthread.php?t=332945
But I have a problem. The PPC restarts randomly even if I do nothing with it. I haven't overclocked it.

It is not got sign, if your PPC restarts randomly. Better you flash it again.

I flashed again the ROM from "Himalaya Mobile 6" category and the following link:
http://forum.xda-developers.com/showthread.php?t=332945
but my PPC keep restarting and one more thing, WM6 kills my battery! I've got to charge it every day, before I charged it every 3-4 days. Does anyone have any idea what I should do? Can I put WM2003 now?

Hmmm... I'm using the 7c ROM from that page with no problems at all.
Did have some issues with some older apps and the config for TomTom when I switched to WM6, but not anymore.
What do you have installed, and what versions?

I have installed nothing but WM6!

Wi-Fi Trouble

Lately I've been having trouble connecting thru wifi. I went to the wifi settings, under Network Adapter and when I select the wifi adapter I see that's set for server assigned IP, but in the field below this there's this weird numbers (fe80::218:41ff:fe2) instead of the IP.
Is anybody else having this problem?
I've been able to get rid of this by Hard resetting a couple of times, but it's a hassle having to re-install & configure everything.
I got my unit second-hand a couple of weeks ago, everything was fine till I changed the SPL from 1.0 Olipro to 3.28 Hard. Since then I've flashed 3.29 & 3.56 Hard, same problem, like I said before a Hard Reset fixes this for a while.
Today I flashed HTC rom 3.34.721.2 & radio 1.70.19.09 and all was fine. A while later I noticed the same weird "IP".
I've read in some threads here people reporting trouble or lossing their wifi, but I've never read of an answer or the reason for this identified.
So...anybody have an Idea?

It does display such a thing when on server assigned IP indeed, but it works just fine that way, wouldn't call it a "problem".
Is your ROM a WM6.1 one? If it's 6.0 as might be since you had HardSPL 1.0 and don't say you changed ROM, you should leave HardSPL 1.0. The 3.x versions are for WM6.1 only.
EDIT: I just read the line where you say you flashed another ROM and it works - that emphasizes my thought that your previous ROM was 6.0 and you flashing the not compatible 3.x SPLs broke WiFi connection and other things like the 3G display that didn't work. Now you flashed a 6.1 ROM and it's fine again as it's OK with the SPL you have now.

Actually my ROM was WM 6.1
If you'd read my signature you'd find that my old ROM (3.28.405.0 WWE) & my new ROM (3.34.721.2 WWE) are both WM 6.1. That's why I wanted to update my Hard SPL in the first place.
My wifi started acting up when I updated the Hard SPL. Now I flashed the latest HTC WM 6.1 ROM & I haven't had any more trouble with my wifi. (At least for now)
Thanks

I have the same problem tried re-flashing with new spl and new roms but no joy. It began while I was on stock rom from orange tried to flash to dutty xtreme 2.1 problem still there.
Now I have kept the custom rom and reflashed to spl 1.14 stock and problem is still there. My wifi seems permanantly messed up. In the IP box I have fe80::218:41ff:fec6
Please someone help.

Problem with HTC Kaiser Tytn II - please help...

So my problem is - I put android on my htc tytn II and it worked (well kinda) but anyway I decided to switch back to Windows Mobile...
I installed 1.27.x.x radio , found a Windows Mobile 6 ROM and put (Like in the instructions ) Kaisimg.nbh(renamed from ruu_signed.nbh) and Kaisdiag.nbh to my SD card and then started flashing... It flashed smth,rebooted automatically and started booting android again...
Then I hold again camera button + power+ reset and since then when I put EVERY .nbh file on my sd card and try to flash it it STUCK on "Loading.." If I try to flash it with USB It stays at 0%.
The only exeption is if I try to flash from USB the rom that I tried to flash before from my sd card.. then it starts 0%..1% and reboot the phone...
P.S: Please help me...I think my device is not Broken but I dont know what should I do to fix it...

To flash back to WM from android put your kaiser into bootloader (multi colored screen) Then connect to usb. Download any WM build that is recent (I suggest Phoenix 3 for this, you can flash whatever you want later). After you download it open and run the included RUU that came with it and it will flash it on there.

hmm, I also had experienced the similar problem on my 1st time flashing back to WinMo.
When you are trying to flash via USB cable and the process stopped at 1% I guess there is also a message about "Invalid vender ID" right?
and if the text in your bootloader (tricolor screen) doesn't mention anything about hard such as "3.29.0000" (not "3.29.hard")
then
you've lost your hard SPL that's why you cant flash any .nbh to your phone.
I had managed to solve this problem by flashing stock WM rom for kaiser. The rom also has to be suitable for your phone, I mean if your kaiser is originally from France, then use French kaiser stock rom. Or if you are using AT&T Tilt use kaiser cingular stock rom.
you can find the list of shipped roms for kaiser here :
http://shipped-roms.com/shipped/Kaiser/
If you still have the "invalid vender ID" error message, try another stock ROM.

Thanks man you're my hero! I though I lost my phone.. anyway i bought new one - Nokia 2730 Classic but Ill sell the kaiser...
Thanks Anyway ... you're god!

Have the same problem...
Firstly, I'd like to point that the reason for the hard SPL getting overwritten by an original SPL is NOT HAVING UPDATED HARDSPL to a newer version that prevents accidental overwrite. This is instructed in the previous steps before actually installing Android. That was my mistake (I had HardSPL 1.0 OliPof), and now I can't flash no rom to my Kaiser (which thankfully works quite well in Android).
What happens (please correct me if I'm wrong) is that "KAISDIAG.NBH" is a modified, standalone hardSPL that will flash to the phone the SPL that comes with the "KAISIMG.NBH" you put in your SD card with "KAISDIAG.NBH"). In my case, I used the WinMo 6.1 spanish version 3.29.412.0, which, resulted in my phone being flashed with the original SPL 3.29.
Now, it seems many users have fixed this locating the correct stock rom and flashing it in their Kaisers. But to others, like myself, nothing seems to work. I believe that this is because we not only need a stock rom for our specific Kaiser model, but also it has to be compatible with the SPL that accidentally got installed in the phone. The problem is what if such rom doesn't even exists?
I'm really thankfull for all I learned by reading the forums (and from my mistakes ) and I know I'm in no position to make requests, but here goes what I think could help the users like myself to fix this, if posible:
1) Guide to identify what model of Kaiser we have (maybe it's already there, I just couldn't find it)
2) Complete list (or lists) of stock roms (There are some around, those are easy to find I think, but it doesn't hurt to share different sources)
3) Something like a JumpSPL for Android would be more than awesome...
Thanks in advance to everybody, sorry for my own stupidity . Any idea or help would be much appreciated,
Daniel

hmm, I'm not sure if it has to be compatible with the SPL.
In my case, I was flashing a very old WWE stock rom which has original SPL 1.56.
I also had been very desperate because any stock rom I found seems doesn't work and I even didn't know where originally my kaiser came from because I get it from my uncle. So I tried to flash any WWE stock rom I could found but nothing works. I read from Wikipedia that based on my phone model (Kais100), this model was only sold as AT&T tilt for US. But the problem is my phone is HTC branded, not AT&T tilt. Well, based on this information I also tried to flash some cingular stock rom but the result was just the same.
After contacting HTC Customer care, I know more info about my phone. They told me that based on my phone product ID, my kaiser was originally shipped for US, but unfortunately they can't provide me stock rom for my phone model. So I searched myself but this time I had better objective : to search HTC branded rom but for US.
finally, after days of search. I've found the rom that is suitable for my phone. Its called HTC WWE Brightpoint US which has original SPL 3.29 at the bottom of the list on the website I told you on my previous post.
few weeks ago I also accidentally overwrite my HardSPL again, but this time I did it with the stock ROM which has original SPL 3.29. But this problem also solved by flashing the stock ROM I've found before via USB cable.
So, I guess it has nothing to do with spl version.
Keep tying don't give up.

Update: Step 1 completed! YAY
Using the serial number and some obscure google searching, I came to the conclusion my KAIS130 is australian. Cheers, mate!
I verified this by being able to download stock roms from the australian HTC site with my Kaiser serial number. But at the moment of writing this, have downloaded two roms and no luck yet. 5 minutes remaining for the third one... Wish me luck...
Daniel.

Well... Now what?
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel

cuartetoraro said:
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel
Click to expand...
Click to collapse
sorry to hear that..
well, extract the .nbh from exe and flash it via sd card is the method that made me overwrite my hard SPL in the first place.
hmm, did your phone comes with operator brand, such as three or something?

-Rif- said:
sorry to hear that..
hmm, did your phone comes with operator brand, such as three or something?
Click to expand...
Click to collapse
No, it's HTC unbranded. Now, something strange here: the label behind the battery has the serial number: HT830GB06075 and the P/N (guess it's part number) :99HCY194-00, but to the left of the camera, another label with the part number: 36H00563-00M and below says DATE:061107(TB02)/US.
I don't know if that's normal, but it caught my atention because my phone seems to have been dissasembled (little label over screw is teared). Maybe my Kaiser isn't Australian after all...