I have unlocked my CID on my G4 phone, I have downloaded SNN version 2.0 I have a question, do I just hook my phone through active sync or is there a special way to install a rom? Really could use some details here. I've read the newbie instalation post but it leaves this part out. Thanks
dwilha said:
I have unlocked my CID on my G4 phone, I have downloaded SNN version 2.0 I have a question, do I just hook my phone through active sync or is there a special way to install a rom? Really could use some details here. I've read the newbie instalation post but it leaves this part out. Thanks
Click to expand...
Click to collapse
Yep, if you have xp, another option is to flash it with a miniSD card or in the bootloader mode
I dont know your situation
lost
I have XP, I tried it and got the 3 red colors, I unhooked the usb and and rebooted the phone and it came back ok, but it updated nothing, I really want wm6 but just dont understand.
explanation Please
OK I downloaded TNT TouchFlo, This is what I see when I download and open it what do I do from here no read me's, There is a Bootloader , nk.nbf , RUUGetInfo.exe file, RUUResource.dll file, XP_ROMUpdateUtility.exe file,
Do I need to drag and drop a file into something or just click on one of the exe files. This is not explained in the newbie section. Thanks again
dwilha said:
I have unlocked my CID on my G4 phone, I have downloaded SNN version 2.0 I have a question, do I just hook my phone through active sync or is there a special way to install a rom? Really could use some details here. I've read the newbie instalation post but it leaves this part out. Thanks
Click to expand...
Click to collapse
A G4 device cannot be CID unlocked,what you mean by saying You got it CID unlocked,Have you applied 'HardSPL' what IPL/SPL it shows at present ?
I applied the hard one and the IPL is at 2.21.0001 and SPL 2.21.0lip
dwilha said:
I applied the hard one and the IPL is at 2.21.0001 and SPL 2.21.0lip
Click to expand...
Click to collapse
All you have to do is run the RomUpdateUtility.exe. I would recommend making sure you don't have any screen savers running on your pc and that you put your phone into "airplane mode" from your comm manager before clicking the update utility.
Once you click on the rom update utility you will be presented with a series of screens. The first two screens you have to check off that you understand and press next. It will then get your current rom settings then you click update then next.
The point that the your phone is being "flashed" is represented when you have a progress bar. Make sure you don't touch your pc or your phone. The process takes about 10 minutes to complete. It may also seem to "freeze" around the 99% or 100%, just let it be, this point of the process always takes longer. The process will complete with a screen saying that you've successfully updated your device, it will then send an order to reboot your phone. Congrats you've updated your phone.
error 300
everything was going good , then error 300, invalid update tool, The update utility cannot be used for your PDA phone. Please get newer update utility.
Thats what it says and I have the 3 color screen on my phone, what do I do now? LOL Hope its still ok. Everything worked fine till the update bar appeared then that message appeared.
Negative.
That is NOT CID-unlocked, just to trick RUU as if it is unlocked. If you use WST, you can still see your CID is locked.
?
What is WST, and what do I need to do?
newbie1221 said:
You are correct, you are CID unlocked. All you have to do is run the RomUpdateUtility.exe. I would recommend making sure you don't have any screen savers running on your pc and that you put your phone into "airplane mode" from your comm manager before clicking the update utility.
Once you click on the rom update utility you will be presented with a series of screens. The first two screens you have to check off that you understand and press next. It will then get your current rom settings then you click update then next.
The point that the your phone is being "flashed" is represented when you have a progress bar. Make sure you don't touch your pc or your phone. The process takes about 10 minutes to complete. It may also seem to "freeze" around the 99% or 100%, just let it be, this point of the process always takes longer. The process will complete with a screen saying that you've successfully updated your device, it will then send an order to reboot your phone. Congrats you've updated your phone.
Click to expand...
Click to collapse
newbie1221
You are wrong here,its not CID unlocked,its just tricked into CID unlocked with a patched IPL/SPL,whereas,its not actually CID unlocked.
Don't miss guide the people.
dwilha
With IPL2.21.0001 and SPL 2.21.0lip,your phone is HarSPL,its temporarily tricked into CID unlock,yes,you can flash any wm6 or 6.1 rom onto it,by just hook up the phone with pc via usb cable and run the RUU exe application included in the rom,it'll start to upgrade,but if you have problem,download the 'Mun's RUU' and replace it with the RUU application in the Rom and run it.
zabardast_1 said:
newbie1221
You are wrong here,its not CID unlocked,its just tricked into CID unlocked with a patched IPL/SPL,whereas,its not actually CID unlocked.
Don't miss guide the people.
dwilha
With IPL2.21.0001 and SPL 2.21.0lip,your phone is HarSPL,its temporarily tricked into CID unlock,yes,you can flash any wm6 or 6.1 rom onto it,by just hook up the phone with pc via usb cable and run the RUU exe application included in the rom,it'll start to upgrade,but if you have problem,download the 'Mun's RUU' and replace it with the RUU application in the Rom and run it.
Click to expand...
Click to collapse
Okay my fault, i should have phrased my statement correctly. That's what i meant to say but in the end the CID needs to be "unlocked".
Thanks guys, but with the SPL and IPL where they are I should be able to flash correct? When I do I get error 300 as I posted earlier, Yoy also state to download Muns I think, how do I replace the Ruu in it, Please explain.
dwilha said:
Thanks guys, but with the SPL and IPL where they are I should be able to flash correct? When I do I get error 300 as I posted earlier, Yoy also state to download Muns I think, how do I replace the Ruu in it, Please explain.
Click to expand...
Click to collapse
Download the RUU MUN from the attached file,extract the zipfile and copy and paste all the contents of the unzipped file RUU MUN to the folder of the Rom you downloaded and then run the RUU, or extract the 'nk.nbf' file from the Rom folder and paste it in the RUU MUN folder and run the RUU,ok
You Guys Rock
You guys ROCK, I have windows mobile 6, wahoooooooo. Thanks so very much.
I dont suppose you might know of a rom that looks like the iphone?
guess I better not press my luck, Thanks so much
CAB files
I want to add the voice calling thing and I find there are cab files for that, how do I add a cab file is it the same as a flash, or is it just copy and paste to the device? Thanks again you guys have helped me so much.
dwilha said:
I want to add the voice calling thing and I find there are cab files for that, how do I add a cab file is it the same as a flash, or is it just copy and paste to the device? Thanks again you guys have helped me so much.
Click to expand...
Click to collapse
Thanks !,glade you got it
Just copy and paste cabfile anywhere in the phone,preferably 'My documents' and execute it there in the phone,after install,you can delete the cabfile to save space
Cheers!
need help
Helo dears I have a G3 i-mate k-jam wanted to update it. Unfortunately I updated it to 3.08 with IPL_SPL_3.08 tool. Now when I try to update it, all the process goes as usual (from 0 to 100%) but after restart first screen appears win6.1 the next screen win 5 as it was. I think I have to downgrade SPL from 3.08 to 1.06 first, and then I’ll be able to update it. But how??? Pls help me.
Thanks in advance
Best regards
azhar63 said:
Helo dears I have a G3 i-mate k-jam wanted to update it. Unfortunately I updated it to 3.08 with IPL_SPL_3.08 tool. Now when I try to update it, all the process goes as usual (from 0 to 100%) but after restart first screen appears win6.1 the next screen win 5 as it was. I think I have to downgrade SPL from 3.08 to 1.06 first, and then I’ll be able to update it. But how??? Pls help me.
Thanks in advance
Best regards
Click to expand...
Click to collapse
Perhaps ! its still CID unlock,did you CID unlock it before upgrading to IPL/SPL 3.08 ? download WST 4.2.2 tool and run the 'CID Action' button to verify the CID lock/unlock status.
Don't downgrade directly from 3.08 to 1.xx,Sometimes SPL freezes at 3.08 and won't get downgraded if you flash Button's Rom 1.05 to downgrade directly,First try to downgrade to 2.xx by downloading and flashing the official Rom,then after that downgrade to 1.xx through Button's Rom.
Related
Upgraded to Dop ROM form original Imate ROM. Now I can't get back. Upgrade is stuck at 95%..or I get Error [296] "Upgrade only This NBF cannot be used on your PDA Phone.. Please get newrer NBF file" . If flash Dop again it works, but refuses to flash any Imate. I guess I'm not the only one here having this problem...many have posetd this problem in different ways but now one gave a concrete answer.
Please let try to solve this.
Thanks
whehe, i'll ask someone who flashed mine back to a JAMin (thought he did it with a-wizard, hope he can help you out).
only the OS itself can be flashed back, you manually have to replace the extended ROM with the JAmin one (total commander, delete existing extended ROM, transfer files through IR to exdended ROM, hard reset to install the extended ROM, bla).
the GSM ROM and the bootloaded itself cannot be flashed to an older version.
yeah, i know, it sucks
Thanks tCC for replying with this goosd news. As for the extended ROM replacment, that's OK and can be easely done.
I realy appreciate your assistance in this and awaiting your next post.
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
tya
swartb said:
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
Click to expand...
Click to collapse
First let me thank you swartb for replying and trying to help by posting and uploading. And of course tCC who offerd to help in the first place.
Second, the link for the file you uploaded is not correct, and if you allow me i think this is the right one:
ftp://ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
And as far as enablerapi.cab here is the thread for it:
http://forum.xda-developers.com/viewtopic.php?t=50768&highlight=enablerapi+cab
Currently I'm downloading them and will let you know the result.
Thank you both again
swartb said:
Hi,
i'm the one who flashed the JAMin of tCC. In fact, it's not that difficult. Just follow these steps:
- execute enablerapi.cab on your device (search on the forum for this cab file)
- download awizard, extract
- copy the jamin os rom to awizard\rom\Jamin\
- start awizard.cmd, make sure your device is connected through activesync
- select option 'w' to write the os rom. just follow the instructions.
- the flashing can take up to 30 minutes so be patient
-if the flashing has finished hard reset your device
I've uploaded the jamin os and ext rom to
ftp.xda-developers.com/Uploads/Prophet/JaminAwizard/
Click to expand...
Click to collapse
can you cid unlock after installing an older rom?
still it's not working...
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Hi,
I don't remember if I did see that error message. But if do a hard reset after this error the os rom is not updated?
And be sure just to update the OS rom and not the other roms (radio, spl & extended) because that doesn;t work.
I have just completed this aWizard process and now need to hard reset, but the program "clear storage"is not there anymore.
How can I hard reset the prophet without the software?
I will post the steps here when it is done :wink:
Could ran the aWizard with the OS rom in the aWizard folder (not \aWizard\rom\jamin\ ) but could not find way to hard reset the prophet, so reflased back to Dopod.
Hope another person continues from here :wink:
Re: still it's not working...
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Re: still it's not working...
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Thanks. Guess I can live with it for now. The Dpod rom is quite stable. No soft reset for 2 days and response looks like quicker than after soft-reset 8)
Re: still it's not working...
Tamagochi said:
ahegazi said:
Dear swartb,
I tried it many times over and over and I still get this error after waiting of 14-15 min. every time.
CopyFileToTFFS(acidunlocked.bin:0, 0, 00010000)
ERROR: ITWriteDisk - An internal error occured.
Please see the attached images.
Any solution? Thanks
Click to expand...
Click to collapse
Its because the CID of your device is still locked. And certainly you have IPL/SPL 2.00. or higher. Swart did it with no problem because he has an unlocked CID.
You have to downgrade your IPL/SPL to 1.xx (I still dont know the correct method) and then unlock CID and then you can flash any ROM you want
Click to expand...
Click to collapse
Thanks Tamagochi, Yes you are right, I have I IPL 1.00 and SPL 2.15.0000
The problem now is how to dowgrade form 2.xx to 1.xx. What are those methods that would help? I can try all of them and see if it works.
Finally it's resolved
I'm back to my imate ROM. Detailes in here:
http://forum.xda-developers.com/viewtopic.php?t=52244&start=25
Hi there,
My currently installed Rom was RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe. (thank you jester for you good job)
Nevertheless, this ROM is in English and I wanted to downgrade to a French One before the selling of my device.
I have tried to install the downgrade kit detailed in this topic : http://forum.xda-developers.com/showthread.php?t=267344
The first step went OK but while trying to make the secnd step, my qtek is blocked at the boot splash screen showing the Jesterz picture and red information about the SPL and so on on the upper left corner... without starting... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Don't worry, its nowhere close to being dead. If you have superCid, then use the SD card image to restore in bootloader mode. However, if the Cid is locked, then you would need a utility that can unlock Cid without Activesync mode (coz in your case, you would not be able to get an Activesync connection). imei-check.co.uk has a utility ($38 i guess) that unlocks Cid in bootloader.--- else show it to a professional. (in my country, I would have to shell out around $20 to get such a problem fixed at a mobile repair shop)
illanz said:
... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Click to expand...
Click to collapse
Just take out the battery for about 10 minutes and re-insert. If it does not re-start, do a soft resert with the stylus and hopefully you should be fine
Hy,please help!
after downgrade, it doesnt work anymore.... i mean... i cant start the mobile!
after the downgrade i disable the USB data cable and now the mobile is dead... it doesnt starts from the ON/OFF Button and even if i connect the USB cable it makes nothing! No Led on... nothing! absolutly DEAD!!!
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Try this in order to reach the bootloader:
Hold down the camera button and reset the device. (Boot Loader Mode is: Press Camara + Soft Reset, then release soft reset and KEEP PRESSING camara button till appear the Boot Loader.)
it doesnt work
I seem to have a simular problem. this is my post in another topic. It seems to fit better here.
This is what I tired so far:....
I used the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_S hip-NoVendorID and it often hangs and was slow with Push Email over GPRS.
I tried to find a way to downgrade but hadn't had time sofar. When I logged on XDA Developers Site I saw there was a new Image.
So I thought Great I dont need to find how to downgrade.
I don't know what G4 and G3 is so as everybody let's try the higest best one.
I uploaded the RUU-Prophet-G4-AKU3.3-Jester-b1
Wrong...
Now as previously stated I get to the multicolor screen with IPL 2.09 and the SPL 2.20..0001 on the screen and that's it.
I can get to the bootloader and load the same image again and get the same result.
I can load another image on and it loads to 80 Percent and says error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file.
If I try an older Version it tells me upgrad only
And when I try to upload the G3 version it tells me error[300] invalid upgrade tool. This upgrade utility canot be used for your PDA Phone. Please get newer Upgrade utility.
Trying to use the nf.nbf or the G3 with the ROMUpdateUtility_NoID of the G4 doesn't work either.
If I would like to do the downgrade tool I need a Active Sync connection which I don't have.
I have no more thoughts. Please Help.
If you would have just read the forums better you would have known if your device is a G3 or a G4. (read this!).
Now it appears you have tried both for an update. Which may possibly have bricked your phone.
But... first things first. Can you get into the bootloader? (read wiki HERE on how to do that).
If you can still get into the bootloader then there is still a possibility for updating.
Try upgrading with the latest Qtek rom (note: this is an official rom, this one works for both G3 and G4! And since it's the latest you should be able to upgrade to this one).
Instructions quoted from another post of me:
You could try the 2.20 qtek rom which seems to be working well for quite some people (found here).
Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found here ) to upgrade.
Update instructions:
1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.
2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.
Inside the RUU_TOOLS there is prophet and in that one WWE, when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).
You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).
3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.
Click to expand...
Click to collapse
This should give you a good enough idea of what to do. This should work (new rom combined with no NoID updater).
However, if it's impossible to get yourself into the bootloader your options of upgrading your device are getting smaller.
Downgrading of a complete rom is only possible on a CID unlocked G3 (when it's CID unlocked you would know! because you would have done that yourself) and not on a G4 device.
Flasing a G3 device with a G4 rom or G4 device with a G3 rom might possibly turn your phone into a brick. This can easily be avoided by reading the forums properly and know what you are doing.
If anything (even if it's a small thing) is not completely clear to you about upgrading/downgrading your device I'd recommend not doing so.
edit: oh yeah... if you have a G4 device (which you should know by now) you cannot downgrade from this rom (well, only via a payed online service). And when you have a G3 device you could try and CID unlock it (read wiki + forums) before you want to downgrade, or don't downgrade at all.
But whatever you do, don't try to downgrade it without doing any of those things because you'll get into trouble. (to put it down bluntly)
illanz said:
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Click to expand...
Click to collapse
If you have reached the bootloader screen, just run my installer (or any official ROM) to get your phone working again.
My Prophet Died
I need help, to restore my Prophet, i upgrade wrong rom, i need will try the SD Backup, where can i see this process ?
Sorry my Inglish is too bad.
I've merged a couple of threads under this one, as they are all about the same problem (mostly)
Opening a new thread for the same problem isnt very useful
Hi RaptorRVL
Thank you very much for your patience in resuming all this for me.
I do try to read the forum but it isn't like a manual where you find the procedure stepby step. Like the G3 and G4 version I have newer come across until now. Sorry.
I tried the image you metioned and I have the result that at 80% it tells me error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file
Any more thoughts?
As you seem to be an expert Can you let me know more about goldcard solution.
Cheers
Mick
From a readme I once found inside an update:
* ERROR [320~328] : INVALID COMMAND
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
Click to expand...
Click to collapse
Doesn't sound too good really. Maybe someone else here on the forums know what to do with this error :/
You did use the ROMUpdateUtility_NoID.exe and not the normal updater right? Can remember someone getting a similar error when using the wrong updater, but I'm not sure about that though...
edit: try doing a search on the prophet forums for "INVALID COMMAND" maybe there is a helpful post in there somewhere...
THANKS!! I was worried b/c i had the same problem today. I've been looking for so many threads abt this problem. Thanks for ur help guys!
same problem
so i have the same problem. I want to downgrade and it break at 95% invalid file. But now XDA is still alive. I can`t go into the bootloader but i tried this file: RUU_Prophet_220734_2207114_024721_NVID.exe
and now my Prophet is still running again. Hope i can help you. Good luck.
peter paul
P.S. sorry for my english, but its good to learn it again
Credit goes to the creator of the HardSPL files V3.28/3.29; JockyW
Simple Step-By-Step Installation of 3.28 Hard SPL:
I have decided to expand on what has already been posted for those noobeees that are having hard time understanding the HardSPL procedures and are hesitant to flash new cooked ROMs fearing the process was not really explained in details.
You only need two files; SSPL-KAIS.zip and Kaiser-HardSPL-3.28.zip. Save both files on your PC in their own folder for easy access later. Follow these steps to the tee, Do this only if you have your device CID unlocked already ( OliPoff method ):
1. Save then unzip SSPL-KAIS.zip inside a folder on your PC, then copy the unzipped “SSPL-KAIS.exe” onto your device. To do this, connect your device to ActiveSync, After Syncing, Click on Tools from the ActiveSync window, and then click on Explore Pocket PC. “Mobile Device” window appears, Copy SSPL-KAIS.exe by dragging it inside the “Mobile Device” window.
2. Unzip “Kaiser-HardSPL-3.28.zip” in its own folder on your desk top. It will unzip into two files; KaiserCustomRUU.exe and Kaiser-HardSPL-3.28.nbh.
3. Remove your SIM card and your SD card from device. Your device will power off when your SIM card is removed. Power up your device. You are still connected to your PC via USB at this point. Your phone will sync again since it is still connected.
4. On your device, go to “File Explorer” and locate SSPL-KAIS.exe that you copied earlier on your device main memory and click it.
5. Wait for the Bootloader Tri-Color screen to appear and "USB" to show.
6. On your PC bottom tray, Right-click the ActiveSync icon, go into “Connection Settings” and ensure “Allow USB Connections” is unchecked
7. Unplug your device from the USB port, wait 5 seconds, plug it back in.
8. Go to the folder on your PC that has “KaiserCustomRUU.exe” and click it. This will flash the HardSPL on your device.
9. When done flashing, do a soft reset, and you should be good to go.
10. You can use the above steps to flash Kaiser-HardSPL-3.29 if you so desire.
Good luck
Tilt will not receive ROM
I tried flashing the below upgraded Kaiser Rom on my ATT Tilt but now I have the tri-color screen:
KAISI*0
SPL-1.93.000
CPLD-8
The first time it stopped loading at 15%, recovered and now I am getting vendor ID error (294 invalid vendor ID).
I tried others ROMs (including this one) but it just does nothing 0%, errors out, recovery and repeat (update error 262).
After removing battery the tri-color screen says "serial", once I plug in the USB it says USB, but no firmware can be loaded on it.
Does someone have basic firmware that will load when an ATT Tilt gets in this state?
Any help is really appreciated. I just got this thing too. Below was the update I tried that kill my Tilt.
'RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship.exe' that you can find
did u hardspl?
Yes, I had to use the JumpSPL1.56-KAIS (HardSPL fix).
TiltedHTC said:
Yes, I had to use the JumpSPL1.56-KAIS (HardSPL fix).
Click to expand...
Click to collapse
Sounds like your phone is still CID LOCKED. Unlock it using the software posted somewhere else on XDA but NOT in this thread, and try to upgrade the SPL after unlocking.
One way to find out if your device locked or unlocked is that you can try to revert back to the AT&T OEM ROM and flash it. You would then be certain that the CID is locked if your device accepts the OEM ROM.
I wish you posted your troubles in the ROM post where you downloaded the ROM where it belongs; My instructions have nothing to do with your device ROM issues.
I believe you are exactly right! Do you know where there is copy of the AT&T OEM ROM? I would love to have my phone working again.
Sorry for my ignorance. Where is the ROM section for my AT&T Tilt. I got the ROM link from modxxxx .com
Thank you for the assistance.
TiltedHTC said:
I believe you are exactly right! Do you know where there is copy of the AT&T OEM ROM? I would love to have my phone working again.
Sorry for my ignorance. Where is the ROM section for my AT&T Tilt. I got the ROM link from modxxxx .com
Thank you for the assistance.
Click to expand...
Click to collapse
The following link is to Pof's full and clear post on unlocking your device CID. Use it carefully.
http://forum.xda-developers.com/showthread.php?t=334679
Search the forum for RUU_Kaiser_AT_T_CINGULAR_WWE_1.62 Rom, download and then flash. you will be set.
Cingular/AT&T OEM ROM
Download the AT&T OEM ROM from the following link:
http://rapidshare.com/files/55298724...GULAR_WWE_.exe
This is just because I feel good today... Otherwise I would ask you to take the time and do the search yourself. Noobee Spoon-feeding Time...
I found this link to put OEM ROM back:
http://forum.xda-developers.com/showthread.php?t=335568
but the RUU ROM for the AT&T link would not load on my tilt (step 2 of idiots guide). I also did a search for the RUU_Kaiser_AT_T_CINGULAR_WWE_1.62 Rom but no hits.
At least I know what went wrong, now I need to recover the original Rom.
update:
This newbee still won't eat. I got the file (your link is to the same file) but I am getting the same 294 invalid vendor error (after 1%).
I rebooted computer and tried it again with same 294 error.
did you just use jumpspl and used that to load a rom?? why oh why.......
Tilted newbie, did not read enough. Any solutions?
A question.
On your PC bottom tray, Right-click the ActiveSync icon, go into “Connection Settings” and ensure “Allow USB Connections” is unchecked
Do you have to do this ?
I never did that.In my settings USB connections is enabled and it seems to work
/Linus
thaaaanx
i must admit this is the best and clearest step by step guide i have come acrooss thanks a lot mate
just a quick thought..... maybe you should give some credit to jocky
Also,
It wouldn't hurt to mention the "white screen" issues people get when running SSPL.
In such a case they need to use Jump SPL 1.56 or 1.93.
Link Here
Ta
Dave
Thnks man for tutorial. I think it usefull and simple for newbies.
So now, when my Kaiser has Hard-SPL v1 and custom ROM, I can do above steps to upgrade SPL? And then upgrade to custom ROMS without touching SPL?
Thanks
kpcz said:
So now, when my Kaiser has Hard-SPL v1 and custom ROM, I can do above steps to upgrade SPL? And then upgrade to custom ROMS without touching SPL?
Thanks
Click to expand...
Click to collapse
Correct.
Hard SPL's allow you to flash custom ROM's no matter what version.
Ta
Dave
ok, thanks - will give it a try!
It appears there is no way to recover.
Any great excuse that should be used when I take it back for repairs?
I have a Cingular 8125, I have flashed many ROMs and the last one is TNT 20273, IPL/SPL 3.08 and radio 2.19
Recently each time I have to soft reset it takes a very long time to reboot. It can be several hours.
I tried to downgrade to official Cingular rom but RUU doesn't work anymore, there is always a connection problem and it only makes a soft reset that takes hours to come back.
I tried also to force bootloader mode with camera button+reset, running enterbl.exe and disabling usb connection in Activesync but nothing worked.
Once it restarts it works fine until I have to reset but when it happens I have to wait hours to use it again.
I am desperate, I will appreciate any help or comment.
Thanks in advance
talvae
the bootloader couls be the problem. have you tried to downgrade to 225/226 what ever it is?
all you need to do is take the original rom and dump it using core kitchen or hypercore. you will see (should see several partitions once you break down the nbf back into it's parts (nb's)
using nb to nbf you can see which partitions are which and just recompile the new nbf with just the ipl/spl. then flash that new nbf using the upgrade utility.
one important question: G4 or G3?
do you have the Wizard Service tool made by mestrini?
you can figure out what type of device it is, as well as use it to flash nb's onto your phone perhaps... (dont quote me on that ask mestrini.
S.V.I said:
the bootloader couls be the problem. have you tried to downgrade to 225/226 what ever it is?
all you need to do is take the original rom and dump it using core kitchen or hypercore. you will see (should see several partitions once you break down the nbf back into it's parts (nb's)
using nb to nbf you can see which partitions are which and just recompile the new nbf with just the ipl/spl. then flash that new nbf using the upgrade utility.
one important question: G4 or G3?
do you have the Wizard Service tool made by mestrini?
you can figure out what type of device it is, as well as use it to flash nb's onto your phone perhaps... (dont quote me on that ask mestrini.
Click to expand...
Click to collapse
Thank you S.V.I., it s a G3.
Let me check if I understood, what you suggest is to use WST to flash a nb containing only ipl/spl 2.25?
If it is correct, do you think reflashing ipl/spl 3.08 could fix the problem?
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Nicely thing
S.V.I said:
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Click to expand...
Click to collapse
I think it is so much process to reflash but its interesant to try dump original roms... i never heard it... it sound very cool. just try to reflash from begining like it never was unlocked... wizard love etc etc etc.
S.V.I said:
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Click to expand...
Click to collapse
Thank you S.V.I,
I have extracted the IPL and SPL from the original 2.26 cingular rom using the last version of WST, I have four .nb files.
Now I have to write them to my wizard but I would appreciate some advise.
Should I write each file using WST? or nessesarily I should make one rom with only this blocks and write that file?
talvae
does anyone have the official TMo Dash 3g ROM upgrade (ver 1.17.531.6) that was on Tmo's site? It's been removed from their site, and I searched in the forums but can't seem to find it.
edit...never mind...found it.
It's still up on T-Mobile's site.
Try: www.t-mobileusa.com/wmupgrade
Was thee just now.....
Dash 3G Update
http://rapidshare.com/files/331920783/RUU_Captain_S_TMOUS_2.06.531.4_Radio_Signed_MAPLE_61.36t.25.29_3.47.25.48m_Ship.rar
brad1825 said:
http://rapidshare.com/files/331920783/RUU_Captain_S_TMOUS_2.06.531.4_Radio_Signed_MAPLE_61.36t.25.29_3.47.25.48m_Ship.rar
Click to expand...
Click to collapse
Any chance someone can mirror this on mediafire? DOWNLOAD SPEED ON RAPIDSHARE IS AT 38K RIGHT NOW!!!!
official tmo 6.5 locks up at 27%
anyone find a fix for this?
happens with hard spl 1.17 and 1.19
I would imagine if you "reset" the spl to 1.17 or 1.19 it will load.
I loaded it on a "virgin" Dash 3G new out of the box. During the upgrade process, it reset at 13%, and then paused for a FEW MINUTES at 27% (using XP).
Go back to this thread and reload the "Original SPL" on your Dash, and then try again. http://forum.xda-developers.com/showthread.php?t=550620
Works fine, EXCEPT for the notifications and reminders "VIB" functions as set up in my Profile settings. Looks like HTC is determined to "upgrade" the volume control at the expense of full profile functionality.........looks like the end of the road with WM (Sph) for me. I rely on the vibrate reminders in particular for meetings etc. Back to 6.1 for the moment.
Spl 1.26.0000
Good Day,
To load this without error...
First Download
Dash3G (Maple): SSPL, HardSPL and original SPL by Jock Dash3G then extract to a file and remove 1.19 hard spl.nbh and any other nbh files.
Then Extract the The new 3g rom to a file, copy the spl.nbh from there into the file you extracted Dash3G (Maple): SSPL, HardSPL and original SPL by JockyW
Run the auto exe and flash the new spl to your Maple.
after the phone is done customizing flash the new rom.
Work for me... Good luck
Spl 1.25.000
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Still not able to flash the T-Mobile version
Tried the ideas on here but still cannot get this version flashed.
abofihmi said:
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Click to expand...
Click to collapse
Upgrading to 6.5
Of course, T-Mobile tech support's solution is to send a new phone! I don't believe for an instant that this will have ANYTHING to do with solving the problem but, well, it is new and shiny!
When I downgraded to 6.1, that changed the spl to 1.17 from 1.19. Is
that what is being referred to? I tried the hard reset before as well.
Tried to upgrade from 6.1 to the t-mobile official version. I don't seem to have a problem going to the Windows Mobile 6.5 3VO version. I tried calling T-Mobile tech support but, surprise, their solution is to send me a new Dash! Okay, I don't mind the new phone but it really shouldn't be necessary. I guess having a new one will be easier to do the official upgrade.
Any instructions on what I should do to get the phone in a format so I
can do the upgrade would be appreciated. Is there a way to do the
upgrade from the memory stick?
abofihmi said:
I folowed your instruction but I have an issue with with flashing the original SPL, it stop on 97%, after a while i gave up and after rebooting the phone the SPL reads 1.25.000 then flash the t-mobile 6.5ROM and it went through and my phone is happy. me too.
Click to expand...
Click to collapse
I have confirmed this. You can not just run Jockys RomUpdateUtility.exe though, it will not work. You must run the auto.bat from within winmo. If you are stuck at the tri color then just reflash any spl (jocky) using the romupdateutility and it should boot. Then run the auto.bat. It will freeze at 97%, remove battery and USB, insert battery. You will see tri color with error code. Run T-mobile update and it should work.
EDIT:
Ok so to recap
1) Extract Jockeys HARD SPL and T-Mobile's 6.5 Rom into seperate folders.
2) Delete any .nbh files from Jockys directory
3) Copy the SPL.nbh from T-mobile directory into Jockeys
4) Run jockys auto.bat with your phone started up in windows mobile.
5) It will freeze at 97%, wait a minute and remove battery and usb.
6) Re-insert battery and power on. You will see tri color with error code.
7) Run the ROMUpdateUtility.exe from T-mobile 6.5 directory.
If you are stuck at tri color and cant boot into windows mobile to run auto.bat:
1) Follow steps 1 - 3 above.
2) run the ROMUpdateUtility.exe in Jockys directory. It will complete but will not change the SPL for some reason and boot into windows mobile.
3) Continue from step 4 above.
I downloaded the new ROM from t-mobile but it’s an executable. How do I extract the spl from this file?
Any help would be appreciated.
If you right click the ROM you can extract it. Just extract it to a folder. Then follow the instructions.
Finally got this to install!
I had to revert back to my original SPL by replacing the hard_SPL in the main folder and then running auto.bat (just running the RUU doesn't work).
The I ran the new T-Mobile ROM and it froze, but installed the new SPL.
Ran it again and it worked!
Hi aaronbaird1
Very thank you for the instructions to fix. 6.5 ROM update I was successful.
thanks a lot