Related
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
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?
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
Hello,
I've tried to update my phone using the shelltool method and my phone crashed during the update.
Now it can't boot. it's freezed on the splash screen.
I've tried to put the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE rom and it does nothing.
I have a G3 device, the IPL/SPL is now 1.01
Thanks in advance for your help
Flash back to official carrier ROM.
I have already tried using the bootloader method. it tells me that the device is not compatible
Try it doing the storage card method.
I also tried and it tells me I don't have the right
Before the first update, I have made a backup of the OS ROM but the file format is NBA. Is there a solution to reuse my original ROM?
In Addition to the SD method, the bootloader is password protected
Try reflashing the ROM you were flashing in the first post using the RUU in bootloader mode. You shouldn't need to use the shelltool to flash that one. Then when you get that flashed on there do your CID unlock. After that you should be able to flash any ROM you want.
I've tried tu put Button's ROM using the RUU in bootloader mode and its still blocked
Try flashing the wizard love rom then. I'm not sure where it is at the moment, but you can find it on here somewhere.
I also tried this ROM
I have made some research.
At the beginning (when my first upgrade crashed) someone on a chat told me to do a doctest.
No the problem is that the memory is damaged.
When I try a hard reset, I have the message "format is failed"
Any idea?
You've got me on this one, I don't think I've run across anyone else ever having this problem. By the way, did you remove any miniSD card that you had in the phone before flashing? Having one in there while flashing tends to cause people problems.
Also, I just realized that you said that you used sheeltool to flash the first time when you flashed the button rom and that it changed your IPL/SPL to 1.01. Flashing using shelltool won't change your IPL/SPL, it skips those files if they are added to a rom since they are the files that will destroy a G4 device. So, if it did change them then that's where you did something wrong. Why don't you start over and explain exactly what you did on the first flash with the button rom and see if we can't figure it out from there.
OK I'll explain from the beginning
Before beginning the flash, I have made a backup of the ROMs (OS, Radio and Ext) with aWizard.
I wanted to put a french WM6 ROM. In the the tuto, it was told to use shelltool to do this. For an unknown reason, the phone crashed. So I had to reboot the phone because it was freezed and after this point it did'nt boot.
I went on a chat to get help and someone told me to start the bootloader and with mtty enter the command doctest (I think he's a joker becose today I saw this command is very dangerous).
When I saw this command doesn't work I discovered this forum and tried 2 of the 3 methods to unbrick a phone in the wiki.
I can't use the SD one because the boot loader is password protected.
I also discovered today that the IMEI number doesn't correspond to the label on the phone.
Here is my story .
http://forum.xda-developers.com/showthread.php?t=276963&page=7&highlight=wizard+bootloader+password
This post seems to have helped many. Read from beginning to end, then try to follow it. Good Luck.
raskell said:
http://forum.xda-developers.com/showthread.php?t=276963&page=7&highlight=wizard+bootloader+password
This post seems to have helped many. Read from beginning to end, then try to follow it. Good Luck.
Click to expand...
Click to collapse
I'can't use imei check because my imei is invalid
Why do you think your IMEI is invalid? If the only reason is that it shows a different one on the box than it shows in aWizard or whatever program you're using, don't worry about it because that seems to happen quite a bit. Usually it's because it got put in the wrong box. Anyway, you're in luck, I have a program that I believe I downloaded off of XDA which is a version of the IMEI-checks unlocker with the master unlocker code for all wizards.
Well, I was going to upload that tool for you but after trying 6 times to upload it and it failing each time I figured that maybe I should wait a little bit and try again later.
I think the IMEI is different because the one given from imei-checks is different from the one on the label back the battery.
Also, when I tried to order an UNL file with the IMEI given by the unlocker, they told me its a wrong number
Lets try this again.
Still failing to upload. I'm not sure why, but I'll try yet again later.
I sent you in PM the address of my ftp server
OK. Decided to upload a new ROM as my phone was getting slow and unusable.
It's an O2 XDA (Touch Diamond) with:
Touchflo v3 Build 29946
ROM 1.93.206.6 WWE
09/08/08
Radio 1.00.25.05
Protocol 52.29.25.12H
Boot R1.00.25.05
I downloaded Olinex's unsigned developer Hard SPL and I extracted the NBH file and renamed it DIAMIMG.NBH following the advice here:
http://forum.xda-developers.com/showpost.php?p=2707841&postcount=4035
On soft reset I pushed the vol down and back buttons to get the boot loader stripes, then let go.
I now have a screen which says "Loading..." and has done for 20 minutes. I have now got the phone on charge while I wait for some help to see what to do next, just in case this is a critical stage - don't want to brick it.
Reading through again I am concerned that this was a procedure for rom upgrade not Hard SPL install, can someone tell me please?
Thanks in advance for any help.
Well, I ended up taking the battery off to get it to reboot. It seems to boot fine back into the old ROM.
I still intend to upgrade it (to SwiftBL's v7.5) but have a few questions:
1. Can the HardSPL be run from the internal storage card? If so is it simply running the exe from the unpacked zip from within a folder? ActiveSync is a bit too flaky for me.
2. Do I need the SIM card in the phone at any stage of the ROM upgrade?
3. On the original ROM I get a drop down menu to setup the phone to the UK O2 network settings. If I load a new ROM, will I need to know these settings?
Cheers
1. HardSPL cannot be run from storage. Only Activesync or Bootloader
2. No. You can flash without SIM card
3. You can use connection setup on any new ROM. Usually starts straight after initial setup.
OK here's where I'm at now.
Downloaded jockyw2001's HardSPL 1.24
Ran it and it got as far as prompting me to run on the phone. I said 'Yes' and the HTC screen went black as expected.
Next stage was to run the DiamondCustomRUU.exe file which I did but this is waiting for ActiveSync. ActiveSync will not sync with the phone now, I guess because the phone is not 'on'?
Where do I go from here?
Use the Hard-SPL in my sig with your RUU.
Thanks, will do (it's not the one mentioned in the ROM author's description though).
So how do I recover the phone from the black screen now? Is it safe to remove the battery to reset?
Battery pulled after reading this post:
http://forum.xda-developers.com/archive/index.php/t-427945.html
I'll try the SPL you mentioned now.....
Had a good search but can't find out. This Olinex zip contains just one file RUU_Signed.nbh.
Where do I get the other files from to run this?
use the attached . It has the RUU exe and the nbh.
Thanks. This is a signed version I see, was going to use SwiftBL's ROM which requires unsigned.
May take a look at other roms that use signed unless you think that I can load the SwiftBL rom with this version?