Siemens SX66 ROM Update Issue - MDA III, XDA III, PDA2k, 9090 Software Upgrading

I have a Siemens SX66 Cingular branded PPC. I downloaded the latest Official ROM Update but get the Wrong Country ID error. I found out that this was due my phone being an AT&T varient even though the phone says Cingular. So I wanted to know is anyone has the original ROM update that came out before the Siemens-1.33.10-Full_Update and if so could provide it to me thank you in advance. I need to put an offical rom back on my phone so I can send it back to cingular so they can send me a replacement phone.

Go to the SX66 Standardization Project to get the most recent ROMs for the SX66; they have both Cingular & ATT versions.

I went there but it's not an official version number which cingular will check for.

hakushox said:
I went there but it's not an official version number which cingular will check for.
Click to expand...
Click to collapse
Try following the instructions here:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Errors
You will need to run the upgrade a second time for it to install, the first time clears the previous contents, the second time the upgrade should run.

That wont work already tried that. Thankz for the resond though. BTW how do you like that new wizard OS on your sx66?

hakushox said:
That wont work already tried that. Thankz for the resond though. BTW how do you like that new wizard OS on your sx66?
Click to expand...
Click to collapse
Did you edit the .conf file as outlined in step 4? This worked for me. You may also try the MaUpgradeUt_noID route as well.
I prefer WM 2005 over 2003 I'm willing to work with the warts and try to advance the ball

Ya it gets rid of that error but then i get a error in the checksum

hakushox said:
Ya it gets rid of that error but then i get a error in the checksum
Click to expand...
Click to collapse
go back and make sure you have edited the editfix.bat file correctly, there is a set of three lines to recalculate the checksum and update it for each of the nba files (xda3nbftool -c -u ?????.nba).

hakushox,
The only way to get back to an officially supported ROM on the AT&T variant of the SX66 is with the MaUpgradeUt_noID. Now, I have not tried this, but here is what you'd need to do. Download the official Siemens update for the 1.33.10 System, and launch it. Once the first screen screen appears, open the Windows File Explorer, and search for nk.nbf. The one you are looking for will exist in a temp directory, and will exist with ms_.nbf, and radio_.nbf. Copy these files to a easy to find directory as these are the files you'll need to do the downgrade with. Cancel the offcial upgrade tool. Now, download the MaUpgradeUt_noID tools from this site, and extract it to a directory on your computer. Copy the .nbf files into that directory. Now, place your phone into boot loader mode, and place it in the cradle. Wait a few minutes for the OS to detect the "new" sync device. Finally launch the MaUpgradeUt_noID tool, and step through the screens. Once completed, it will place System 1.33.10, Radio 1.06.02, and Extended 1.33.110 ROMs on your device.
This works because the MaUpgradeUt_noID tool does check the ROM ids, and will let you flash any IDed rom onto your phone. As you can imagine, it is a rather dangerous tool if you don't have a good idea what you are doing, which is why I have tried to get it away from the Standardization project.
-Chris

Worked like a charm much thanks

Excellent!
-Chris

I tried uploading the original SX66 Cingular rom to the FTP but for some reason its not responding, if some one wants it email me and I will send it.

SysCrasher13 -
I am interested in downloading the factory Siemens SX66 firmware, after upgrading the firmware my SD slot no longer recognizes SD Memory... very strange.
Please let me know where to download the factory firmware.
Note: I have (2) SD PNY cards that work fine in my PPC4100, however, my SX66 doesn't recognize either card and wondering if this maybe a compatibility issue. I'm going to swap the 512MB with a SANdisk tomorrow to see if this rectifies the problem. Can anyone confirm SD compatibility issues with the SX66 --- is there a SD Memory quick reference chart available for the SX66?
Mike

Let me know if anybody has any ideas before I send it in for repairs...
Thanks - Mike

Related

How to Downgrade Your Wizard (STEP BY STEP) Instruction

Hey Guys....
I am still working on this DIY but this is how I was able to accomplish reverting back to my OEM Cingular 8125 state.
If someone could plase let me know how to replace the very first SPLASH Screen from "HTC" to CINGULAR, I would greatly appreciate it.
By following the steps below, you will have almost everything back to its original state.
Be sure to download all the necessary ROM files: OS ROM, Radio ROM, splash.bin
Place your OS ROM and Radio ROM inside the c:\sWizard\ROM folder.
DOWNGRADE YOUR OS AND RADIO ROM
1. Download aWizard 1.3b Beta Version (Attached File or Latest Version) from the following link: http://forum.xda-developers.com/viewtopic.php?t=37386&highlight=awizard
2. Unzip the folder to your root directory (C:\aWizard or D:\aWizard). You need to avoid having spaces your directory name. This is the reason placing folder in the root.
3. Make sure you have an active connection via Active Sync.
4. Run the aWizard.cmd file from C:\aWizard
5. Run "e" command FIRST !
6. Run "u" command. Your Wizard will reboot.
7. Run "w" command to update your ROM. You will get a prompt to choose your ROM. If you did not place a valid ROM inside the ROM folder, then you wont see it from this list. Also, if you placed your aWizard in other directory with spaces (i.e C:\ MY DOCUMENT) then you wont see it either. Just let it run. It will take close to 20 minutes. At the end, it will as you to hard reset.
8. Run "r" command to update your Radio ROM. Same as Step 7.
Replacing Splash Screen (Back to Cingular)
1. Place the splash.bin file inside the c:\aWizard\lib
2. Open up CMD and navigate to c:\aWizard\lib
3. Type in the following command "pdocwrite.exe -n 1 splash.bin 0x002d0000"
pdocwrite.exe = this program is located inside the LIB folder
splash.bin is a file that I converted.
4. Once completed, please reset your Wizard and now you will have Cingular's Splash (2nd Splash)
Updating the EXT ROM
1. I did this manually by utilizing Active Sync to copy over all the Cingular ROMs to the Wizard and running it individually.
2. Reset and you will now have all the programs Wizard came with.
FAQ
Q. My Wizard is stuck on a splash screen and it wont do anything.
1. Hard reset your Wizard
2. Hold onto Camera Button while turning on the Wizard and you will get the boot screen.
3. Plug in your USB Cable
4. Run one of the known ROM files with .exe extention. When this happened to me while downgrading,
I had to reload the latest iMate ROM.
5. Start the downgrade process again by following the above instruction.
reverting back to original cingular rom
Thank you for this.
Don't you have to REINSTALL original Cingular Rom or does this do that by removing imate updated ROM?
js
Re: reverting back to original cingular rom
urologyhealth said:
Thank you for this.
Don't you have to REINSTALL original Cingular Rom or does this do that by removing imate updated ROM?
js
Click to expand...
Click to collapse
When you install Cingular ROM, it will remove/overwrite the existing iMate ROM.
Be sure to place your ROM files in the the ROM folder.
If your running the aku2 imate rom, many people will have problems running awizard or lokiwiz to unlock the CID, I had to run the tmo uk rom update (.exe one) which replaced the imate, and then restore the rom files I had backed up for cingular, although the extended rom is still locked, thats annoying.
jvanbrecht said:
If your running the aku2 imate rom, many people will have problems running awizard or lokiwiz to unlock the CID, I had to run the tmo uk rom update (.exe one) which replaced the imate, and then restore the rom files I had backed up for cingular, although the extended rom is still locked, thats annoying.
Click to expand...
Click to collapse
can you please share how you change the very first splash screen on your 8125 ? its the only thing i wasnt able to do or know how to do.
thanks
FarSeide, I'm pretty sure that even the stock 8125's from Cingular showed the HTC screen first, the cingular screen second, and finally the Windows Mobile screen. If that's the case, then your 8125 is as good as new as far as Cingular is concerned.
Also, if anyone upgraded to the AKU2 I-mate ROM, you cannot do the process you described, because (as someone else mentioned) the lokiwiz program will not work. What you need to do is FIRST install a different ROM using an exe file (a good example would be the leaked AKU2 Q-Tek ROM exe file), and only after that entire upgrade process is completed, can you now use lokiwiz to unlock the SuperCID and install the Cingular ROM.
kingbear2 said:
FarSeide, I'm pretty sure that even the stock 8125's from Cingular showed the HTC screen first, the cingular screen second, and finally the Windows Mobile screen. If that's the case, then your 8125 is as good as new as far as Cingular is concerned.
Also, if anyone upgraded to the AKU2 I-mate ROM, you cannot do the process you described, because (as someone else mentioned) the lokiwiz program will not work. What you need to do is FIRST install a different ROM using an exe file (a good example would be the leaked AKU2 Q-Tek ROM exe file), and only after that entire upgrade process is completed, can you now use lokiwiz to unlock the SuperCID and install the Cingular ROM.
Click to expand...
Click to collapse
Eli,
thank you for the info. I wanted to put this together because when I tired to do this, there were information but scattered all over all forums. just wanted to help others so that they dont go through the same thing i did.
i was following these instructions and i got a
NOTIFICATION ERROR
cannot execute repllog.exe
so what i had to do was hard reset, boot screen , re-installed imate, ...
i guess i will try it again, what do you guys think
hmmm... sorry to say but my 8125 only ever showed the cingular splash. No HTC, no WinMob. I had assumed that Cingular somehow replaced all 3 splash screen with theirs.... In fact, I never even knew there was more than one splash screen until I upgraded to the Qtek rom.
I'm in trouble
I tried to downgrade the ROM and now I'm hung in the i-Mate SPLASH SCREEN. I tried the hard reset and it hangs every time. I can't get a connection through active sync obviously so what are my options. How can I get a working device.
I'm freaking out.
Please HELP!!!!!!!!!!!!!
Re: I'm in trouble
hellomoto_25 said:
I tried to downgrade the ROM and now I'm hung in the i-Mate SPLASH SCREEN. I tried the hard reset and it hangs every time. I can't get a connection through active sync obviously so what are my options. How can I get a working device.
I'm freaking out.
Please HELP!!!!!!!!!!!!!
Click to expand...
Click to collapse
relax... i was exactly where you were...
first, hard reset your device.
Hold the Com Manager, Voice Command and press the soft reset with your stylus.
before you turn the device back on, hold the camera button then turn on the power. you will receive the boot screen. Plug in your USB Cable and kick off the EXE file. Load one of the known ROMS like the iMate ROM.
reload and try again. I am willing to bet that you disconnected the USB Cable while updating to Cingular ROM.
Good luck and dont worry.
does anyone have the exe for the original Cingular ROM ?
my colleague tried to update his 8125 with my imate rom.....and did not unlock it first.
all he has is the bootloader now, the update gives the well known Error: Invalid Vender ID
Any help is greatly appreciated
Thanks !!
Get a copy of the proper ROM on a SD card, and reload it that way.
This is the easiest way out of that box......
Thanks,
but how to get the Rom reloaded from the SD card onto the device using the bootloader ?
dirty_harry said:
Thanks,
but how to get the Rom reloaded from the SD card onto the device using the bootloader ?
Click to expand...
Click to collapse
THAT part is easy.
Note that the SD card image is NOT a file. You have to raw write it onto the card, which will destroy the filesystem - so back up the card first! psdwrite will do the job. You also need the image (PREVIOUSLY copied from a SD-made backup with "psdREAD")
To restore it, insert the card, hold the CAMERA button, and power on. The phone will tell you to press VOICE to restore the SD image (it looks to see if there's a valid one in there)
Note that with 1.x bootloaders this will happen with the BACKLIGHT OFF, and you only have 3 seconds or so to press the key - so have a flashlight handy. 2.x bootloaders turn the backlight ON.
Hit VOICE. The image will be verified (checksummed) and if it is good, it will be loaded.
That's it. Takes about 2-3 minutes. When it finishes it will tell you to press any key, and when you do you'll end up at the tricolor screen.
Power off and back on, and the phone will cold boot the new image.
This will work even if you can't run an RUU loader, so long as you can get that first prompt up. It is a VERY effective rescue method.
IMHO before you hack on the firmware in these things you should make an SD card backup just for this reason.
Which tools is best option for ROM backup to Mini SD?
Hi,
Just read your message about writing ROM to Mini SD card.
I'd like to do just that.
I want one or two ROM's for safekeeping stored somewhere instead only a backup or official copy on my pc.
As i've read restoring from SD is safer and faster..
I don't intend to use the SD card for anything more than just that.
In the Prodigy Service Manual (Prodigy Service Manual -XA(0813-2005).pdf) HTC uses mtty.exe. There are also instructions in the PDF.
Since HTC uses this, it should do exactly what i want, i guess?
Or is there a better tool?
Thanks,
Allegro.
P.S: Will a restored ROM from Mini-SD look fresh to HTC?
Or will they see it's a self restored copy instead of a official HTC restore?
Will it reset "everything"?
I was able to fully restore CIngular 8125 ROM, EXTROM, All Splash Images using the SD Restore.
100 Cingular OEM Spec has been restored...
I hv updated T Mo custom ROM..but now can't downgrade even by Awizard utils....can any one throw some light on this?

Downgrading WinMob 5 to Win2003SE

Hi there
I'm trying to downgrade my Qtek9090. I have WinMob 5 and I want it to be the Rom from http://www.orange.ch/offers/orangePhones/spvM2000/spvM2000Rom?ts=1144157178509.
Now, I got the MaUpgradeUt_noID.exe and I did just use it like its written...
Now I have Win2003se but none of that stuff provided by Orange in this Rom (At the first start it said some stuff was missing and it xould be deleted). Then I tried again without the MaUpgradeUt_noID.exe and still get a country error...
Do I have to re-partition the memory like I did for the WM5 update?
Thx for answers...
greetz
Well for wm5 you most lickly got rid of your ext rom as you wanted it for storage.
So now there is no place to flash the extrom so the cabs that are part of the extrom do not run and thus you get no ORANGE related files.
What you need to do is create a new EXT rom partion and flash the rom again.
This time you can delete the radio.nbf and the NK.nbf and just leave the MS.nbf (it will be a lot faster).
First of all, thanks for the reply!
great...now, how do I do it? Do I need a special size of the rom?
Sorry to say this but.....
Please read wiki
Ta
For more info you can read here
omfg this looks like work..
Sorry MDAIIIUser I used the search button (but only for the forum, my bad)...But anyway, I know you are very busy just read some threads while waiting for an answer...But you're doing a great job...All of the people here in fact...
i'm also downgrading to WM2003SE according to the directions on wiki,
BUT i have 2 questions:
1. i bought my qtek 9090 as a stand-alone qtek9090 (so not combined with a provider). does this mean i don't need the Extended ROM?
2. i aksed this question in another topic aswell, but lateron i found that this topic is more acurate to my question..so sorry for that!
here's the question:
in the manual, it says I have to download my latest favorite WM2003SE ROM version (which in my case is the Dutch Qtek DANGA001 version 1.40.00, EXTROM 1.40.556),
and FROM that file i should copy the nk.nbf to my "\DOWNGRADE TO WM2003SE\" folder..
and THAT'S what seems impossible to me, since the Rom-update i downloaded is an .exe application, and not a .zip or .rar archive..
so how should i get/extract/copy the nk.nbf file out of this Rom-update .exe file..?
i simply skipped that step but now my device keeps crashing every minute (even DURING soft and hard resets!)
HELP!
spdfrx said:
and THAT'S what seems impossible to me, since the Rom-update i downloaded is an .exe application, and not a .zip or .rar archive..
so how should i get/extract/copy the nk.nbf file out of this Rom-update .exe file..?
Click to expand...
Click to collapse
execute the application and search in C:\Documents and settings\NAME\Local settings\Temp for your file.
if you don't find it, continue on your application and try again.
thats how i had to do extract the files from my swisscom update file (wich was an exe file too)
I downgraded my spv m2000 from wm5 to 2003 and everything is fine apart from the phone doesn't work.
It just says no service all the time, can anyone help please?
Thanks.
Check the radio version on the boot screeen to see if the device sees it.
Check that you see the version under settings.
Check that you have a sim in the device
Check that you not in flight mode.
ok now onit thanks for the quick reply
Be also aware that in the boot process the radio can sometimes not load, no know reason for this but fixed with a soft reset (stick up the hole).
My device sees the radio version on the boot screen (1.06.02)
I can see the version under settings and i have a sim in and flight mode is off but still no luck.
Shall i try another sim?
Try your sim in another phone (and another sim in that phone).
What do you see at the top of the screen (should be a bar chart with an x) if you have no link.
I put another sim in and now it's all fine GPRS and Phone works
thanks for the help.
Would the device be affected if you had a pin code on the sim?
The sim code is only for the sim card.
Without the sim pin code you can not unlock the sim card.
Thus the radio will not connect to a carrier and you will not beable to phone out.
A phone lock is a lock that stops you putting in a different sim card into the phone (thus you need to stay with the same carrier)
This is a device lock and needs to be unlocked on the device to be able to put in a different sim from a different carrier.
Tool found on wiki
I would think that your first sim is either no longer valid (out of date or is a pre-paid with no money) or it has a sim lock that you dont not have the pin code of and failed to mention that it asked you for it.
Anyway have fun with the BA and read wiki for more info.
Thanks

Rom Update: Error [260]

While trying to update my MDA Vario with the new AKU 2 ROM of T-Mobile the RUU puts the MDA in bootloader. Then Windows notifies me of a new unknown USB device and the update utility gives me an communication error with error code [260] - upgrade failed. :shock:
1) How to solve this problem as this would make me or
2) Is it possible for someone to make a complete backup on a mini SD card of his HTC Wizard? From what I have read on Internet this can be written to a file. When posted on the XDA ftp I can write this file back to a mini SD card and restore a original ROM (for this I need a short tutorial).
option 2 assumes that the problem is related to the ROM. I super CID and SIM unlocked using the well known tools. Maybe this has gone wrong at some point :?: ?.
I'm having the same problem moving up to a custom 2.26. Did you ever find a solution.
Thanks,
Jeff
dont qoute me on this.. but i believe its an issue with the update utility... hopefully someone else can confirm or deny this..
but you can try this one:
i dont know how much either of you know so i will try some directions with this...
take my rar file, extract them to a folder, lets use c:\rom for an example
if you rom you have is in an *.exe format then use winrar to extract the rom to a folder then take the nk.nbf file and copy it to c:\rom and then run the update utility
if your rom is already in a rar or zip file then just extract the nk.nbf file to the c:\rom folder and then run the update utility
hope that helps
shogunmark said:
dont qoute me on this.. but i believe its an issue with the update utility... hopefully someone else can confirm or deny this..
but you can try this one:
Click to expand...
Click to collapse
I really appreciate your help, but before I risk bricking my phone, could you tell you tell me how this differs from the ROMUpdateUtility_Wizard_NoID.exe and RUU*.* that are part of the custom ROM update package I already have?
Thanks,
Jeff
datawrhsdoc said:
shogunmark said:
dont qoute me on this.. but i believe its an issue with the update utility... hopefully someone else can confirm or deny this..
but you can try this one:
Click to expand...
Click to collapse
I really appreciate your help, but before I risk bricking my phone, could you tell you tell me how this differs from the ROMUpdateUtility_Wizard_NoID.exe and RUU*.* that are part of the custom ROM update package I already have?
Thanks,
Jeff
Click to expand...
Click to collapse
the custom rom that you have, does it have the NoID update utility already?
ANSWER
I spent a few hours fiddling with this, and it turns out that my problem was that I have a miniSD installed. Make sure you pop your miniSD out of the slot before you begin the update, and it should work.
Re: ANSWER
doomcomplex said:
I spent a few hours fiddling with this, and it turns out that my problem was that I have a miniSD installed. Make sure you pop your miniSD out of the slot before you begin the update, and it should work.
Click to expand...
Click to collapse
WTF that is WEIRD
i have flashed many roms and never had an issue with the sd card being in... but will definitely file that in the back of my brain in case i ever run into the same issue
shogunmark said:
the custom rom that you have, does it have the NoID update utility already?
Click to expand...
Click to collapse
Yes, it does. Oh, I also tried this without the MiniSD in the device (a known but really strange problem). Still getting the error.
Error 260 Finally Gone!!!
Well, just for the heck of it, I tried xelencin's 2.26 ROM update from another PC...and it succeeded.
Clearly, it is a new issue related to my laptop but it is probably going to quite a bit of trouble to track down.
Thanks everyone,
Jeff
Re: Answer
doomcomplex said:
I spent a few hours fiddling with this, and it turns out that my problem was that I have a miniSD installed. Make sure you pop your miniSD out of the slot before you begin the update, and it should work.
Click to expand...
Click to collapse
WTF!!! I had the exact same problem. Popped out the Mini-SD Card and voila! The Bootloader started!
Thanks man!!
Ty man ... MS card out and it is working .... yea
i cant get this to work PDA PHONE ROM UPDATER, send a black screen to s200 and then gives error 260

2.26 rom and nbf error

ok...i got the error from upgrading from 2.17 hacked rom to the 2.26 official rom. tried to read whatever i can but looks like solutions were given for cingular ipl etc...
can someone help me out? when i run the official rom, it updates to 1% and then i get the nbf error. i tried to run loki but mda not recognized by my usb connection.
stuck now...please help!!!
actually, tried to run machinagod's RAPI unlocker..but MDA not recognized as connected...this was part of xelencin's 2.24 rom updater.
please help!!!
Hi,
you must provide more information if you want someone to help you.
First and most important: what does it mean your phone is stuck? Stuck where? Does the screen come on? Can you get the bootloader screen? (for the bootloader screen: hold the two keys on the right side of the device and press shortly the reset hole; if you see the three colors screen then you have the bootloader!)
bye
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
m3m3 said:
i get the screen with the 3 colors, and usb at bottom left. when i run the official t-mobile 2.26 update, the screen goes gray and there is a bar with % done. when that kicks in, i get 1% done then it stops. on my computer screen, i get the nbk error, saying the nbk file that i have is not for my phone.
i looked for fixes but all the fixes require activesync connections which i am unable to connect with. just fyi, when i plug in the usb cable to my laptop, i hear the *ding* for usb noting it is connected but the activesync connection is not available.
thanks in advance for your help.
-mike
Click to expand...
Click to collapse
Before your battery goes flat i suggest you to re-install your old rom. Don't know why 2.26 is not working, maybe you downloaded a corrupted archive. To install your old rom it is not required that activesync sees your phone. Go in bootloader mode and flash your old rom back.
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
m3m3 said:
i dont think i downloaded a corrupted rom file because i downloaded it from 2 different places, one from Tmobile site directly from my tmobile account.
what bootloader program should i use? please advise and location to download...
thanks,
mike
Click to expand...
Click to collapse
bootloader program??? There's no bootloader program!
What i'm trying to tell you is:
- Your phone is stuck for unknown reasons. In this state you cannot recharge your battery!
- Before the remaining battery charge becomes too few, reinstall your old rom (the one you had before trying 2.26)
- When your phone -with the old rom- will be working again, then you'll have all the time to investigate on the causes of this failure.
- Now hurry up and install the old rom before it's too late (unless you have a second wizard that you can use to recharge the batteries)
To install the old rom you must go to the three-colors screen (the bootloader), connect to USB (but activesync won't start!) and start the rom installer.
bye
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
m3m3 said:
risi,
sorry...how do i get to bootloader screen? is it the tricolor screen? has anyone had the same problem that i'm having, going from 2.17 hack to 2.26 official?
what program can i use to load my original rom with?
sorry for the semi-newbie questions...desperate to revive my MDA...
again, thanks.
-mike
Click to expand...
Click to collapse
to go to the bootloader screen you must keep pressed the two keys on the right side of the device and, while keeping them pressed, shortly press the reset button. the bootloader screen IS the three colors screen. when you get the bootloader screen, reinstall your previous rom (2.17).
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
i didnt bring the phone with me to work...i will try to reflash with old rom...for now...i am using my old hp 6315 (yikes! - remember the probs with this phone?? lol
m3m3 said:
i plugged the phone in the wall charger and the battery charged up all last night so i am not worried about the battery...
i just cannot figure out how to load the old rom i had.
Click to expand...
Click to collapse
to load the old rom you must:
- get to the bootloader screen (the three colors one)
- download the 2.17 rom's ,exe archive (download it from the same place you took it last time)
- connect the phone to USB (don't worry if activesync doesn't see it)
- start the rom .exe file
thanks risi...
hope i can get it back man...
m3m3 said:
thanks risi...
hope i can get it back man...
Click to expand...
Click to collapse
I hope so! About the problem you had with 2.26, i don't know why it happened. Is your phone a T-mob USA MDA? If it is not then you must CID unlock it before flashing a different operator's rom.
Bye
yes, it is a tmo usa mda...or i would think so since i bought it from a factory store (not an authorized dealer). anyway man...i will keep you posted...for now, using my trusty hp 6315. lol
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Anais said:
Hello,
I have a similar problem. I updated my QTEK 9100
with a T- Mobile 2.24 ROM. Now I need to go back to the original QTEK Rom, namely RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe, but after starting the upgrade process the program refuses to downgrade the device and says get a newer nbf file.
Is there a way to force a downgrade?
Many thanks in advance
Click to expand...
Click to collapse
Is your phone CID unlocked? If so, then you must download the wizard_upgrade_noid tool from the ftp server and use it to install the 'down'grade.
In details:
- be sure your phone has been CID unlocked (and is not a G4)
- download the wizard_upgrade_noid (i don't remember the name exactly) tool
- use winrar to extract the original qtek rom .exe archive
- copy the noid tool to the folder where you extracted the qtek rom
- run it
bye
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Hello,
Just some small updates: My phone has currently the Mr Clean 2.3 firmware loaded : IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
Previously I was using RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe and had no problems. After upgrading to xelencin t-mobile based US rom I had trouble when making data transfers over GPRS. Then I decided to test Mr clean. Altough I data transmission has improved a bit it's still not so good as with my original RUU 2.17 release.
Unfortunately I am unable to revert to this version. Also having tried to downgrade using Faria's Custom downngrade file only the IPL was downgraded to 1.05 and the SPL file stayed to 2.24.
I tried then to reapply RUU_Prodigy_2170702_21707102_20710_QTEK_WWE_Ship.exe but I recieved the error message UPGRADE only.
Since apparently this is unstable I decided to reapply Mr Clean and now I have again IPL 2.24 SPL 2.24 GSM 02.25.11 and OS 2.24.10.1.
I suspect that the data problems are due to the fact that these new radio versions are not compatible with our provider. I live in Luxembourg so we use LUXGSM.
Is there a way how I can revert to my old 2.17 software.
Any coments are highly appreciated.
Greetings
Anais said:
Hello Risidoro,
At first thanks for your fast answer. Since I have a QTEK I don't beleve it's CID locked. How can I verify if the phone is CID locked? Is there a tool to check this?
I proceeded exactly as you advised. I used Winrar to extract the files and used the Wizard_RomUpgradeUtility_noid I downloaded from the ftp site.
Then I copied the nk.nbf file to the respective folder but the utility after having completed the initial 2 screens says:
ERROR [238] : FILE READ
The update utility cannot open the requested file. Please check your update utility.....
any ideas
Greetings
Click to expand...
Click to collapse
Hi Anais,
try flashing with the RUU (Rom Upgrade Utility) tools that you find in this thread: http://forum.xda-developers.com/viewtopic.php?t=56088
Download the archive RUU.rar and extract its content somewhere in your PC. Copy in the same location the nk.nbf from the rom and run the .exe.
bye

problem upgrading to WM6

does anyone know why my imate kjame would give an error or Windows/autoconfig.exe doesnt exist.
i have tried a number or roms but the phone failed to upgrade to wm6. it then reverts back to the wm5 after encounting this error.
i have tried the CID unlock but there is no hope
can anyone please assist me urgently.
ghumanfly said:
does anyone know why my imate kjame would give an error or Windows/autoconfig.exe doesnt exist.
i have tried a number or roms but the phone failed to upgrade to wm6. it then reverts back to the wm5 after encounting this error.
i have tried the CID unlock but there is no hope
can anyone please assist me urgently.
Click to expand...
Click to collapse
We need more information than this if you want help...
1. Wireless Carrier?
2. IPL/SPL?
3. Roms tried?
4. How have you been trying to flash roms? What method of flashing?
5. What is your PC's operating system(your computer, not PPC)
EDIT>> Answer these questions for me and I will try my best to help you tomorrow some time. I live in Cental US so I might not get your messages until later tomorrow your time but I will respond in the morning tomorrow.
info
forgive me if there is anything that i dont get correct....
1. Wireless Carrier?
i am assuming that this is the service provider and that is vodacome for me. it is a not the same as vodafone however they have a JV running
2. IPL/SPL?
IPL - 2.16.0001
SPL - 2.16.0001
rom version - 2.16.9.1
radio - 02.07.10
extROM - 2.16.9.101
OS - WM5
3. Roms tried?
i tried one of the ROMs that my IT team provided to me. i have attached the rom.
i also tried Octvio's rom (ROM_Wizard_OCTAIVOI_OS_1908_v4[1].8_PP6MB)
i also tried CB-AIRAF
4. How have you been trying to flash roms? What method of flashing?
here i loaded the EnableRapi cab file and ran it on my wizard. then i ran the lokiwiz.bat file on my machine. i didnt see any error there so i take it that it ran fine.
5. What is your PC's operating system(your computer, not PPC)
i am running XP SP2 on my notebook.
couldnt attach any of the files... not sure what was causing the problem
ghumanfly said:
forgive me if there is anything that i dont get correct....
1. Wireless Carrier?
i am assuming that this is the service provider and that is vodacome for me. it is a not the same as vodafone however they have a JV running
2. IPL/SPL?
IPL - 2.16.0001
SPL - 2.16.0001
rom version - 2.16.9.1
radio - 02.07.10
extROM - 2.16.9.101
OS - WM5
3. Roms tried?
i tried one of the ROMs that my IT team provided to me. i have attached the rom.
i also tried Octvio's rom (ROM_Wizard_OCTAIVOI_OS_1908_v4[1].8_PP6MB)
i also tried CB-AIRAF
4. How have you been trying to flash roms? What method of flashing?
here i loaded the EnableRapi cab file and ran it on my wizard. then i ran the lokiwiz.bat file on my machine. i didnt see any error there so i take it that it ran fine.
5. What is your PC's operating system(your computer, not PPC)
i am running XP SP2 on my notebook.
Click to expand...
Click to collapse
Ok I see that you have a G4. Lokiwiz is a waste of your time since you have a G4.
Here is what you need to do:
Because you have a G4, you can't just flash a rom because of the DOC chip.
There are 3 ways I know of to flash a G4.
1. Download shelltools - install enablerapi.cab and cert_spcs.cab and reboot your device. connect with activesync and place the nk.nbf file of the rom of your choice in the shelltools directory and run shelltools and follow the directions in the readme. If you do it correctly, you will end up successfully flashing your device.
Link: http://forum.xda-developers.com/showthread.php?t=293480
2. Download SoftSPL and place the nk.nbf file of your choice in the RUU folder included and run SoftSPL and it is fully automated. It will call the RUU and your device will be flashed in about 7 minutes.
Link: http://forum.xda-developers.com/showthread.php?t=329147
3. Use the HardSPL(CID UNLOCK) and unlock your device prior to flashing. This will allow you to just flash roms at your leisure with no problems whatsoever from now on BUT it is still in developement so use at your own risk.
LINKS: http://forum.xda-developers.com/showthread.php?t=332330
http://forum.xda-developers.com/showthread.php?t=332320
I hope this helps you. I personally have a G3 so this is not my area of expertise...
wm6
thanks alot me. it upgraded properly
i am trying get all add ons.
ghumanfly said:
thanks alot me. it upgraded properly
i am trying get all add ons.
Click to expand...
Click to collapse
No problem... Now you're at the fun part. Add ons!!
add ons
when it comes to add ons,I was reading on the Rom Kitchen thread and and I couldn't see much more that could be added to the rom that Faris V5's nbf file.it seems to be one of thee most comprehensive files that I have come across. the only issue is that it runs a bit slow but it cool.I might just need to do some memory management.
other than that I would recommend the file.
do you have any other recommendations?
have u seen the article that microsoft wants xda dev... to remove all of its roms from the website?
ghumanfly said:
when it comes to add ons,I was reading on the Rom Kitchen thread and and I couldn't see much more that could be added to the rom that Faris V5's nbf file.it seems to be one of thee most comprehensive files that I have come across. the only issue is that it runs a bit slow but it cool.I might just need to do some memory management.
other than that I would recommend the file.
do you have any other recommendations?
have u seen the article that microsoft wants xda dev... to remove all of its roms from the website?
Click to expand...
Click to collapse
I personally use the TNT.1437 TouchFlo and TNT.1437 Professional+HTC Home roms personally modified to have a 10MB page pool. They are quite fast and are almost 100% stable with only minor bugs that are barely noticible...
Here is a link to the 10MB Version of TNT.1437 Touchflo
http://www.megaupload.com/?d=TM2N1W2R
Here is a link to the 10MB Version of TNT.1437 Prof+HTC Home
http://www.megaupload.com/?d=RZFKY868
If you would like, I can speed up the performance of faria's rom also and then upload the new nk.nbf file for you to try. Just let me know.
speed
Yes, please.... speed it up for me. if there are any other applications (add ons) that you feel should be added to the nbf file then please add them.
i have already shared the nbf file with many guys at work. we would be grateful if you can assist.
one last thing, i noticed that there is a 3G icon under the comms manager. one of the guys said that we should not have any issues accessing 3G even if the phone didnt come with it. is it possible to use 3G on these phones?
cmd> prompt when i use mtty
--------------------------------------------------------------------------------
hi,
i;ve managed 2 screw up my wizard
everything was going well
i flased sucessfully 2 three different roms..
then i flased the tnt latest beta rom
i worked fine
i reflased the same rom by mistake as i wanted 2 flash a diferent rom
this is when the problem sarted..
the upgrade got stuck at 66%
i waited for 15 minutes..
then i disconnected the usb from the phone & since then the phones stuck in the bootloader..
i've used mty
this is where i'm in unknown teritory..
it gives me cmd> prompt
no USB prompt..
any sugestions??

Categories

Resources