Related
hi,
well my motorola bluetooth stereo headset is of no use now that i cant shift from the KJAM_wwe_216901_216901_020710_ship rom to 208070_101_11310_qtek_wwe_test rom..
i actually have all the tools lookwiz and ewizard to unlock the cid..tried both to unlock the cid..with a error mess saying cannot copy itsutil.dll bcoz its in use,,plz reset the phone or the active sync and try again and then it wud give a mess saying cid unlocked and the phone wud reset itself...
after the phone boot up tried upgrading the phone goes in the bootloader mode and i get a mess saying [296] UPGRADE ERROR..plz download another nbf file..
tried downloading the rom again and repeated the process..with no effect
also tried to put the phone in bootloader manually by pressing camera and reset and upgrading with no effect..
PLZ advice as in what exactly Should BE donewhere exactly m going wrong..
Thanx
ankesh
well no reply so far...there can b two things either i ques was foolish or people have become too cold to reply..
neways thanx 2 HDUBLI i was able to do it after two complete days of work...
he is one of the most underrated member of this forum..i think people shd start respecting his work now
Any chance you could post here what you did? I'm facing same situation now, can't downgrade from 2.17 to 2.8.
Hi..
Flash any of the two custom ROMs...Button or TMO 2.17...then upgrade or downgrade to yr ROM of liking
anky26 said:
well no reply so far...there can b two things either i ques was foolish or people have become too cold to reply..
neways thanx 2 HDUBLI i was able to do it after two complete days of work...
he is one of the most underrated member of this forum..i think people shd start respecting his work now
Click to expand...
Click to collapse
I have another, less harsh theory. It's that no one had a useful suggestion for you until HDUBLI came along and offered advice. Or, your problem has been experienced by others and based on reading the forum and a little experimentation on your part, you could have solved it.
Rather than lash out at everyone because they didn't overwhelm you with solutions, you should be thankful these forums exist in the first place.
If you are uncomfortable or unfamiliar with the risks and issues associated with ROM flashing, I suggest you stick with what your carrier provided. This is a friendly and sharing forum, but you won't make any friends by bearing unreasonable expectations and criticizing.
Glad your issue was resolved.
hdubli said:
Hi..
Flash any of the two custom ROMs...Button or TMO 2.17...then upgrade or downgrade to yr ROM of liking
Click to expand...
Click to collapse
I can't get it to work. I flashed succesfully CUSTOM_RUU_Prodigy_2170702_217_20710_TMO_US.exe and CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe but afterwards with both ROMS when I try to flash 2.08 Qtek test ROM, it goes nicely all the way to colors screen and then stops with "error [296] upgrade only".
I noticed that SPL stayed 2.17 after both ROMS, is it the reason 2.08 won't go through?
search forum carefuly...you hv to CID Unlock everytime.I hv been doing this...Pls try and post here
Hdubli I bow down to you, you teh guru
I flashed Button's ROM and then ran cid-unlock with aWizard 1.2. After that I succesfully flashed Qtek 2.08 ROM. Thanks for the help, man!
Want to go back to qtek9100 1.1.7.5 9/22/05 ROM
hdubli said:
search forum carefuly...you hv to CID Unlock everytime.I hv been doing this...Pls try and post here
Click to expand...
Click to collapse
Hdubli,
I have a bit of a similar problem here. I have a Qtek9100 with the ROM Version: 1.1.7.5 ROM date: 09/22/05.
Recently, I upgraded to AKU rom, but I see that this rom is unstable and gives me problems with wifi which used to work flawlessly on my original rom. I just want to go back to the 1.1.7.5 ROM.
In your post, you asked to flash a CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe rom and then CIDunlock and then flash old rom. My question is,
1. is this Custom rom the actual qtek9100 1.1.7.5 Rom ? If yes then I can just do this step.
2. If not, then you said that I need to CID unlock. Would cid unlocking void the warranty.
3. Further, if I cid unlock, do you know where do I find the installer for qtek 1.1.7.5 ROM, dated 9/22/05.
I know lot of questions here, but i would really appreciate any help on these.
Please advise.
Anup
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)...
can anyone explain which one is the best one for 8125 g4 locked
and how im am to go about it thanks alot sorry for the noob question
Just depends on your operator, so you need to try yourself and find out which is the best one.
i have at&t and running on wm 5
Basically, like starkwong said, it's pretty much trial and error. You have to try out all of the different Radio ROMs to find out which one works best for you in your area. Nobody here can really tell you for sure which one will work the best for you, unless maybe they live just down the street from you or something.
i know that im just asking is it safe and not brick my phone because its not unlocked in anyway
Normally Radio ROM can be updated directly with the Update Software (RUU) regardless unlock state of CID.
OH NO!
I have a Cingular 8125 G3 unlocked and have TNT's Touchflo rom on it. I tried updating my radio using Faria's 2.69.11 updater, but now my phone won't work, usb won't work, and when I reboot, it reads the IPL/SPL is still 1.xx and the OS is 6.00.0.0 but there is NO GSM line at all! Seeing how I can't the usb to work, I can't flash it with the T-Mobile rom or anything, however I can transfer things onto the phone via IR. So is there something out there I can use to fix at least the usb so I can reflash my phone. Thanks in advance!
Got it!
Nevermind, I got it working. I was able to transfer the bootloader.exe file over to my phone, ran it, and then was able to reflash my phone. Whew, I was so scared. Anyhow, thanks for all the info on this page, I love this site!
I tried reflashing my IMATE KJAM to WM6
The process went till 35% and then got disconnected.
Now its stcuk on the Bootloader Screen(Three colors screen)
Tried the Hard Reset(comm mann+voice button+reset)
It doesnt do a hard reset, the same screen flashes back again.
Tried reflashing i get the Error 300
The previous ROm was crossbow underground edition.
Please help and let me know whats next that i can do.
paraozzy said:
I tried reflashing my IMATE KJAM to WM6
The process went till 35% and then got disconnected.
Now its stcuk on the Bootloader Screen(Three colors screen)
Tried the Hard Reset(comm mann+voice button+reset)
It doesnt do a hard reset, the same screen flashes back again.
Tried reflashing i get the Error 300
The previous ROm was crossbow underground edition.
Please help and let me know whats next that i can do.
Click to expand...
Click to collapse
You know what the totally histerical thing about this is? This is the exact same reason I made my first post. LOL.
Alright I'm gonna try to help you seeing as how it doesn't look like too many others are looking here.
I have several questions first before I can help you.
1. Who is your wireless service provider? IE: T-Mobile, Cingular, Etc...
2. What Is your IPL/SPL?
Answer these 2 questions for me and I will be able to better help you.
Thanks for the quick reponse
Now the irony is i am here in nepal and i use the phone as a simple mobile phone, but as far as i know i remember flashing a T-Mobile ROM while upgrading to WM6, the IPL and SPL both are 2.26, i unlocked the device while upgrading..
Thanks
Kushal
paraozzy said:
I tried reflashing my IMATE KJAM to WM6
The process went till 35% and then got disconnected.
Now its stcuk on the Bootloader Screen(Three colors screen)
Tried the Hard Reset(comm mann+voice button+reset)
It doesnt do a hard reset, the same screen flashes back again.
Tried reflashing i get the Error 300
The previous ROm was crossbow underground edition.
Please help and let me know whats next that i can do.
Click to expand...
Click to collapse
Hey!
ok lets c if I may be of some help here,if u r in bootloader screen than try to reflash again T-mobile 2.26 rom and if it goes alright than go on to flash any other wm6 cooked roms.
or
if it doesnt flash than i wud suggest u reflash back the buttons 105 rom to get back to ipl/spl 1.05,than again use lokiwiz tool to unlock cid & reflash T-Mobile to gain ipl.spl 2.26
hope it works out.it happened once with me also, I did the same & now I'am running wm6 XM6r3 Rom,Secondly u can use the WST TOOL by Mestrini to verify ur device status, u can even Cid unlock ur device with it, Goodluck
Yup man flashing the T-mobile 2.26 did the job..
Great thanks for the same..
paraozzy said:
Yup man flashing the T-mobile 2.26 did the job..
Great thanks for the same..
Click to expand...
Click to collapse
glade you got it up and running good luck and happy flashing
I just flashed my Diamond with the: RUU_Diamond_HTC_NOR_2.03.409.1_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
I'm an norwegian that's in the US studying, so they only gave me the norwegian version. Anyways, everything worked fine until flash, but now my phone refuses to register on the network (AT&T)!
Took the sim-card back to the at&t nokia phone, worked the first time...
I really wants to use my Diamond instead of the crappy nokia, but it would be a shame to downgrade to 1.93 (which worked just fine...).
Someone, please have a solution for me?
simply install a new radio....try 1.00.25.07 that seems to be the only quadband radio..
(you have to flash an hspl before)
It's stuck on 0% and won't continue... Tried several roms :-/
no service?????
is there a soution to this no network problem
THERE IS A CROSS IN THE RECEPTION BAR AND WHEN YOU DIAL OUT IT SAYS "OPERATION FAILED"
any replies appreciated
Quite bad if the official RUU more or less bricks the device, at least turns into just a little computer
It screwed up my Diamond aswell The gprs is completely dead, been up all night trying to fix it, several hard resets etc, nothing helps... if it was a cooked rom I could tolerate it but official roms screwing up our phones this easily pisses me off.
Mine worked again, with the old 1.93 rom!!
What the hell did they do to 2.03? I suppose the radio rom is different at least... But I couldn't change to the old radio when I had 2.03, tried using the HardSpl...
Is it possible to flash _once_ with everything from 2.03, but the 1.00.25.05 radio (which is the one from 1.93)? Doing it sequentually doesn't work.
So what I did, as the final solution:
Flash with stock 2.03 rom
HardSPL
Flash with 1.05.25 radio
Works perfect!
Hmm i did the other way round with my o2 XDA Diamond (1.93 Stock)
1. Hard SPL
2. New Radio Rom (1.09.25.23)
3. 2.03 official Ger HTC Rom (without vendor lock)
works great as well
I've seen this issue a couple of times too. With 1.93 as well as with 2.03. Did not figure out what was the cause but never had a chance to bring the device back to life with some uninstallation or radio flash. I always went back to the SPB Backup from the night before it stopped working propperly.