Can't upgrade OS BUT phone is unlocked! - 8125, K-JAM, P4300, MDA Vario Software Upgrading

So I been trying to upgrade my OS to the tnt 1437, however every time I try my old OS keeps popping up (OS: 5.1.xxx (Build 15671FARIA.3.5)) ... so for the last 3 days I been trying to search this site for any answers, however all I get is that only happens if the CID is locked, but my phone isn't 1) I unlocked it before to upgrade it in the first place to the above mentioned OS and 2) I checked its status with the Wizard Service Tool (which is AWESOME). So i'm at a lose here as to why every time I either upgrade or downgrade the ROM the same OS keeps showing up. BTW Everything else I can upgrade except the OS. Any help is appreciated. thanks!

I've had this.. flash the original rom (or wizard_love rom or something) and then reflash your WM6 ROM.
Don't forget to hard-reset when you're using the ShellTool to flash

Yea I forgot to mention I've done that. I've downgraded to both button ROM and love ROM however I get the same results, the IPL and SPL are downgraded but not the OS. The only thing I have NOT done is the hard rest, is that the missing link here?

Related

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)...

Downgrading Upgrading LokiUnlock Overwhelmed and Confused Plz help

Ok I purchased a new Cingular 8125. It is a G3 Version. It was purchased with these settings
Original
Ipl 1.08
Spl 1.08
GSM 01.09.11
OS 1.8.11.1
New
Currently I Upgraded it to the HTC Release ROM from
HTC's website Settings now are
Ipl 2.25
Spl 2.25
GSM 02.25.11
OS 2.25.11.1
I want to use Risi's new 2.26 Rom but I can't CID/UNLOCK my phone. I noticed that there are MANY others here with the SAME problem.
I'm Begging for some assistance.
We need
1. Instructions on how to Downgrade to 1.8.11.1 so that we can use LOKIWIZ to unlock it. Thereby enabling us to use cooked up roms.
Been looking all over for the programs that are needed to do this. And I'm just as lost as ever. I definately do not want to brick my 8125 but I'm out of options.
http://forum.xda-developers.com/showthread.php?t=263116
Forget the warning at the top, I just used this method and on my new 8125 with the same firmware you are running and it worked fine. Take your time and follow directions. If you are not absolutly sure after reading the instructions stop and forget it. Download all the tools you need and do a dry run in your head.
Oh, I just found all this information a couple days ago by searching and spending time on the forum reading.
thanks man. im doing it right now the downgrading process hopefull it works. pray for me. if it does work ill have your children, build a shrine in our honor, and send 5 strippers to your house. if it fails i shall smite thee to hell on earth and take your first born.
well ive tried everything man. I went BACK to that old rom. Did the CIDunlock deal it apparently worked. But Nothing else does. It goes back to the old 1.xx rom then i made the mistake of upgrading to risis rom immediately. that didnt work. kept everything the same but installed the EXT rom. so i went BACK to the 1.xx rom unlocked again and then installed the 2.17 shipping rom. It instaleld but the OS stayed stuck at 1.xx. I ran risi and it only installed the ext rom again. I'm beginning to think my device can never support any cooked up roms and have given up. I'm installing the HTC shipped 2.25 rom now and hope that everythings all good and gravy again and all my numbers match up again. Hopefull this will be the case.

Downgraded NBD to Button, then tried to upgrade to Cingular ROM, but getting errors

Have a G3 unlocked Wizard (Cingular 8125).
Have been running different ROMS to see which one I like.
Recently stayed with NBD 8.0 for a while.
Last week battery went to heck, apparantly during a reflashing.
Probably due to the battery, I could never reflash and would always get
stuck in bootscreen @ 98%, no matter how long I charged the battery
(using stock charger and battery in-phone.)
I purchased a cradle battery charger and a new battery from ebay (which works great BTW).
Now I can flash... I think.
I managed to flash in "Xda_MiniS_LaunchROM_v154102" and my phone works.
I even got caught up on my voicemails. But every time I try to
upgrade to stock Cingular or T-Mobile, the RUU says incorrect ?nk.nbf? file.
(The actual ROM file).........What gives?
This is what comes up upon bootup.
ipl-1.01
spl-1.01
gsm-1.12.10.0
os-1.5.4.2
I'm using an XP machine with ActiveSync 4.5. Never had a problem
re-flashing before. I tried looking through the threads without success.
Any help would be appreciated.
i was going to say try that xda mini rom. thats what fixed my problem , then i was able to flash a tmobile rom. then tne wm6.
http://forum.xda-developers.com/showthread.php?t=298613 I used this thread. try the tmobile rom on g3.7
joihan777 said:
Have a G3 unlocked Wizard (Cingular 8125).
Have been running different ROMS to see which one I like.
Recently stayed with NBD 8.0 for a while.
Last week battery went to heck, apparantly during a reflashing.
Probably due to the battery, I could never reflash and would always get
stuck in bootscreen @ 98%, no matter how long I charged the battery
(using stock charger and battery in-phone.)
I purchased a cradle battery charger and a new battery from ebay (which works great BTW).
Now I can flash... I think.
I managed to flash in "Xda_MiniS_LaunchROM_v154102" and my phone works.
I even got caught up on my voicemails. But every time I try to
upgrade to stock Cingular or T-Mobile, the RUU says incorrect ?nk.nbf? file.
(The actual ROM file).........What gives?
This is what comes up upon bootup.
ipl-1.01
spl-1.01
gsm-1.12.10.0
os-1.5.4.2
I'm using an XP machine with ActiveSync 4.5. Never had a problem
re-flashing before. I tried looking through the threads without success.
Any help would be appreciated.
Click to expand...
Click to collapse
It may be the RUU you are using. Try flashing the Cingular rom using one of the RUUs I attached below. I personally have never had this problem before so this is my best suggestion.
Is it possible that somehow it got re-locked????
Also, evrytime I try to upgrade out of 1.05 ROM the RUU process stops at 85% and then says nk.nbf not for this PDA.
No, except you didn't have a successful CID-unlock (e.g. Unlock when IPL and SPL is 2.xx, and flashed to WM6 using ShellTool, then you think that you have been unlocked, which is actually not)
Update: Even though I haven't been able to load the official Cingular ROM or
the T-Mobile 2.26 ROM, I HAVE been successful in loading NBD 8.0.
I DON'T GET IT!!!!! Why would NBD load but official carrier ROMs get stuck at 85%?
Although my G3 is is currently working again, I'll still do some more experimenting.
I don't know what an extended ROM is, but I wonder if mine was corrupted
during the power failure when attempting to downgrade last week from NBD to Cingular?
I'll post my results hoping this will help others.
Edit: An hour later- I tried another official WM5 ROM form HTC, no dice. Froze @ 85%
just like the other WM5 Official ROMs. On a hunch, I tried to install the newest NBD 9.2.
IT WORKED! WHY can I install NBD ROMS but not Official WM5 ROMs?
Now the first splash screen is the *dated* green stepped graduated green from 1.05. The current info:
IPL- 2.25
SPL- 2.25
GSM- 02.25.11
OS- 6.0.0.0
Itai! This is tough!
EDIT: OK, it's now 4am and I'm seeing double....
Tried Wizard Service Tool, a very efficient program by mestrini.
Apparantly, my extended ROM was hidden. So the WST unhid it. Now we'll see what this does.
According to WST, there was no pagepool found in WM6 or WM5 location.
Could this be why WM5 updates didn't work?
4:22am, even cat gave up on me...
Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.
So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.
joihan777 said:
According to WST, there was no pagepool found in WM6 or WM5 location.
Could this be why WM5 updates didn't work?
4:22am, even cat gave up on me...
Click to expand...
Click to collapse
Page Pool is set in ROM image, not hard-coded in hardware.
mfrazzz said:
Sorry if I missed something here, but if you have a CID Unlocked phone and you downgrade back to a 1.xx IPL/SPL, then you will be CID Locked again when you upgrade. Anytime you downgrade to 1.xx you have to redo the CID Unlock process while you are down there before going back to IPL/SPL 2.xx or higher.
So redo going back to the Button rom, do the lokiwiz unlock, make sure both IPL/SPL are 1.xx (so you may have to flash button a couple of times) then upgrade to Cingular, T-Mo or whatever official 2.xx rom.
Click to expand...
Click to collapse
Didn't work. I'm certain I'm unlocked, both by lokiwiz program saying so and
Wizard Service Tool saying so. After the unlock I was successfully able to
load NBD 8.0 & NBD 9.2 ROMs, but not the official T-Mo/Cingular WM5 ROMs.
WST found the pagepool completely missing in both WM5 & WM6 sectors.
The extended ROM was also hidden. Both of those items have been corrected
so later today I'll redo the entire process just to make sure all is well.
starkwong said:
Page Pool is set in ROM image, not hard-coded in hardware.
Click to expand...
Click to collapse
Thanks. More clues to this puzzle!
Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.
goofeyass said:
Try flashing the empty extented rom. Most new roms don't have extended roms, so if your extended rom is corrupt it may be keeping wm5 to load. Which explains why NBD roms work.
Click to expand...
Click to collapse
Thanks, I just now tried this approach. I used mestrini's Wizard Service Tool to 'format' the extended rom. As of this moment I've just downgraded to Button 1.05 ROM and going to use lokiwiz's unlocker.
There is a rom out that will flash an empty extended rom without changing anything else.
http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
I have formatted the extended rom.
Then I tried to redo the Button-->Unlock-->T-Mo 2.26.
Still process stops at 85% when installing T-Mo ROM!!!
Also, the splash screen doesn't seem to be working?
goofeyass said:
There is a rom out that will flash an empty extended rom without changing anything else.
http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
Click to expand...
Click to collapse
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
I would recommend flashing ---->http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
???
in my opinion it is a waste of time to downgrade to flash a new/original rom...i've flashed about 100 or so roms since late 2005, multiple devices, jumping from carrier rom to latest wm5/6 builds..never had an error.
Do what you like of course, im just saying save 10 mins and flash straight to whatever you're wanting to try. goodluck and happy flashing
BTW like I said before... for those of you with dual/quad core procs, try putting the romupdateutility.exe on real-time priority and check it, I flash in roms in less than 3 mins, everytime, no errors
goofeyass said:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
I would recommend flashing ---->http://forum.xda-developers.com/attachment.php?attachmentid=42076&d=1182515673
Click to expand...
Click to collapse
Is there a correct method for using those files? I installed them to the Wizard's Windows/ Startup directory & rebooted. They sorta ran, but when I checked the extended ROM with WST, it reported the extended ROM was empty =)
Now I'll go around again Button 1.04-->Lokiwiz Unlock-->T-Mo 2.26
goofeyass said:
How long are you waiting when its at 85%. I've had them stay at 85 % for over 5 minutes before.
Click to expand...
Click to collapse
Good point... HOW long are you waiting. If you are doing an RUU, you should just let it run. Official roms will "Hang" at 85%, and I've had them hang for over 5mins before also, but they always finish.
As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...
mfrazzz said:
As someone used to post, you should start the RUu, then head to the kitchen, go get coffee, a snack, whatever. Just ignore the flashing process until its done...
Click to expand...
Click to collapse
Very well said. Lol. It's true though. If you just ignore it, it will seem to go faster. I noticed the same thing too. If you are flashing an official rom, it will almost always stop at 85%, sometimes for a long time... Just let it go and it should eventually finish.

Bricked Wizard

sorry if this post seems to be a repeat , but i tried the search option and the results were not fruitful
a friend of mine , while trying to upgrade to a TNT ROM , didn't HardSPLed the device first , and successfully changed the ROM of the device , now it is stuck on the blue screen with SPL and IPL versions , and no response . for some reason , the device can go to bootloader mode , but it can not be reflashed , and it does not respond to a hard reset command.
please advise on what to do
regards
When it is in the bootloader mode, and connected via USB, is there a little USB icon in the bottom left? If so, simply flash your phones carrier ROM and all should be fine with it again. You can then apply HardSPL and flash to the TNT or any other ROM that you want to. Is your device a G3 or G4 by the way? What are the numbers after IPL and SPL?
well my friend says that the USB icon is visible there , and the device was indeed a G4. the thing is , what exactly should he do , in order to flash the ROM , since non of imate roms work for it. should he use any special software?
i'll greatly appreciate your help
Is he using Vista or XP?
he is using Windows XP , could it be the PC OS that caused interference?
Well, only if it is Vista does it really matter. He needs to get ahold of an original carrier ROM, such as the O2, or T-Mobile one and flash it to his phone, then HardSPL it, then upgrade to 6 or 6.1.
Download and flash Wizard_love Rom,it might do the trick,then HardSPL and upgrade to any wm6 or 6.1 rom.
What exact error it gives while flashing imate official rom ?
well the wizard has been an imate ,and it was flashed with an Original imate ROM already , but no success , any other suggestions?
thanks again
error [294]invalid vendor ID :
This Update Utility can not be used for your PDA phone.Please check your update utility.
here is the picture
http://i35.tinypic.com/29v03rl.jpg
and could you please give a link to the Love ROM?
thanks
Download wizard_love Rom from this link:-
http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
well he first got this error while upgrading
http://i33.tinypic.com/ivjz8o.jpg
then he managed to upgrade , but had the very first screen after ugprading on PPC screen , and nothing happens
it also gives a failure message while trying to manually Hard Reset after upgrade
please advise on what to do next
greatest appreciations
No SD Upgrade even tough... MTTY hahahaha
king_dani said:
well he first got this error while upgrading
http://i33.tinypic.com/ivjz8o.jpg
then he managed to upgrade , but had the very first screen after ugprading on PPC screen , and nothing happens
it also gives a failure message while trying to manually Hard Reset after upgrade
please advise on what to do next
greatest appreciations
Click to expand...
Click to collapse
It seems you need to follow the drugstore MiniSD upgrade but...
I guess you dont have another wizard to make a bacuk up... so wait a minute...
You don have hardspled yopur device...!!!
HAHAHAHA forget it!mmmm
Maybe mtty... folow mi signature maybe works
See you There Men!!!!

Corrupt HD?

Hi,
I've just upgraded to a new Dutch rom, but since then I only have trouble.
I get different colours (like drivers are not loaded), it keeps getting stuck or resets itself, and nothing helps.
I've tried to put on a different rom, with succes, but I still have the same problems.
On startup, however, I see the right colours.
I also put back the latest original ROM, but no luck...
Can anybody help me?
guessing you have hspl 1.14 installed
Yeah, I reinstalled that, as one of the latest things I did.
The problem you describe happens when you flash a 1.56 based rom with 1.14 HSPL. First flash a stock 1.56 ROM (a new SPL is then flashed as well) or use the new HSPL. Then you should be fine. So no, it's nor corrupt!
For more info, read crackwhore's guide (sticky)
Well, I'm trying to do so now, but it keeps getting stuck at 0%...
Does it matter I have an NLD-version, and not a WWE?
Update: I cannot get a proper connection via activesync, and through the bootloader it stays at 0%, and after a while the update utility says no.
Update 2: ah, thanks to troubleshooting, it looks fine!
THANKS!

Categories

Resources