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
Related
Just wondering what would be the difference between these two...which one should i do or do i do both...i read the jumpSPL thread but i'm still not clear on what differences are...is jumpSPL basically bypasses any bootloader whereas the Hard-SPL you have to be at bootloader 1.5...someone pls shead some light...TIA
The way i understand it is that SSPL is loaded onto the phone when running, emulates the original bootloader and then flashes. This means if something goes wrong, you still have your original bootloader to fall back on.
HardSPL overwrites your original bootloader, but once done means the bootloader will always be there to fall back on as it does not allow the rom to overwrite it.
Don't pretend to know the tech stuff, but its nice to have a safety net. If anythings wrong there, please correct
yep, SSPL is an old SPL that gets loaded into memory, not stored.
Hard-SPL is one I've hacked up with various features, and I heartily recommend running it on your device.
thanks for the replies...
Olipro if you recommend to Hard-SPL instead then thats all i needed to know...thanks...
but if you load an OEM ROM package, it will overwrite the Hard SPL.
There's a bit of a trick to NOT overwriting it, correct?
-Mc
Nope... HardSPL will bypass the SPL flashing part of an OEM ROM... as it does with the two published ROMs for the Kaiser/Tilt
SSPL on the other hand doesn't affect the bootloader and will load what is in the ROM, however there is an issue with the Kaiser SSPL at this time. HardSPL is your best bet for flashing.
sirsycho said:
Nope... HardSPL will bypass the SPL flashing part of an OEM ROM... as it does with the two published ROMs for the Kaiser/Tilt
SSPL on the other hand doesn't affect the bootloader and will load what is in the ROM, however there is an issue with the Kaiser SSPL at this time. HardSPL is your best bet for flashing.
Click to expand...
Click to collapse
According to this thread:
Can be uninstalled by just reflashing a shipped SPL, so no warranty is lost
Click to expand...
Click to collapse
And according to this thread, you had to extract the .nb files from the ROM and delete the 01_SPL.nb and repackage the whole thing.
So, how do you remove the custom SPL if you want to return it to factory fresh?
-Mc
McHale said:
So, how do you remove the custom SPL if you want to return it to factory fresh?
Click to expand...
Click to collapse
ok... Assuming you're starting with a Tilt with HardSPL and the HTC ROM:
1. Reflash the ATT ROM
2. Extract the ATT ROM with NBHextract.exe
3. create a new NBH using htcrt using only the ATT 01_SPL.nb
4. Put your NBH file containing only the SPL into an empty directory on your PC
5. Copy KaiserCustomRUU.exe to that folder
6. Copy the SSPL-KAIS.exe to your phone
7. Run SSPL-KAIS.exe from your phone
8. Flash your "custom" NBH containing only the ATT SPL.nb by running KaiserCustomRUU.exe
9. After it's finished verify your SPL by holding down power and camera buttons while doing a soft reset.
10. Send your phone back to ATT
pretty sure I've covered it all... Let me know your results, I've not actually tried this yet but intend to tomorrow since I have scroll wheel issues.
Good Luck!!
thanks. that actually makes sense.
-Mc
sirsycho said:
ok... Assuming you're starting with a Tilt with HardSPL and the HTC ROM:
1. Reflash the ATT ROM
2. Extract the ATT ROM with NBHextract.exe
3. create a new NBH using htcrt using only the ATT 01_SPL.nb
4. Put your NBH file containing only the SPL into an empty directory on your PC
5. Copy KaiserCustomRUU.exe to that folder
6. Copy the SSPL-KAIS.exe to your phone
7. Run SSPL-KAIS.exe from your phone
8. Flash your "custom" NBH containing only the ATT SPL.nb by running KaiserCustomRUU.exe
9. After it's finished verify your SPL by holding down power and camera buttons while doing a soft reset.
10. Send your phone back to ATT
pretty sure I've covered it all... Let me know your results, I've not actually tried this yet but intend to tomorrow since I have scroll wheel issues.
Good Luck!!
Click to expand...
Click to collapse
Just tested this process this morning... it works exactly as advertised.
sirsycho said:
Just tested this process this morning... it works exactly as advertised.
Click to expand...
Click to collapse
How would this process differ for an 8525 as opposed to a Tilt?
shughes said:
How would this process differ for an 8525 as opposed to a Tilt?
Click to expand...
Click to collapse
The process is essentially the same but you'll want to use the CustomRUU for the Hermes and obviously you'll be extracting the SPL.nb from Hermes ROMs. The general steps should work fine for Hermes. I believe MrVanx has a very detailed guide on how to do this exact thing on the Hermes, you may want to look that up.
I didn't read the unlocking SIM procedure by jocky properly. I understood that I MUST get HardSPL installed, and so I go the JumpSPL1.56-KAIS.exe to the phone and then executed it. It got me the tri-color screen (Is this called bootloader?) and then I executed the KaiserCustomRUU.exe from the flash-HardSPL.zip thinking that this will put in the HardSPL into the ROM. The progress bar went upto 95% and then it exited with error and after that the "Recovery" option of the loader hasn't been able to revive the phone. Every time, I put the battery back in and power it up, I get the tri-color screen with the following message:
RUUNBH (on the top right hand side of the screen)
KAIS1*0
SPL-1.56.0000
CPLD-8
I think I now understand the mistake I made. I had a bunch of .nbh files in the directory from where I ran the KaiserCustomRUU after extracting and that is why it must have failed. Now every time I get the tri-color screen when I boot up.
Can someone please help me recover from this position? I have now got the actual simunlocker zip from the original thread and extracted it with folder names and so now I am ready to try again, only if I can recover from the mess I created. Please help!!!
mtty recovered, but I get back the bootloader every time I power up
I used mtty (set 14 0 and boot) to make the phone work (now data was lost and all my prgrams were still there). However, every time I power up my phone, the tri-color screen is back. How can I resolve this?
When I run mtty, I get the following messages on mtty:
set 14 0
HTCST ÚÈÒHTCE
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
FMD_ReadSector+, bad block no=0xFAC0, status:0x0
flash the original rom your device came with! only shot buddy!
Thanks for the advice. Where do I get the original ROM and how do I flash it? After the mess I created, I want to be doubly sure. I remember the versions of ROM that the phone used to show during bootup was R1.27.12.11 and D1.56.00.00 (I don't remember the G number). Appreciate if you could let me know. I have downloaded the Radio ROM numbered 1.27.12.11... is that the original ROM?
if it's a tilt, flashing the original rom will not work, you will get an invalid model error. Instead, use this one RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe. Trust me, been there done that. (twice)
Once you've done flashing to RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe and you want to unlock, HardSPL, then flash it back to RUU_Kaiser_CINGULAR_WWE_1.57.502.2, then start w/ step 1 from simunlock.
the_passenger said:
if it's a tilt, flashing the original rom will now work, you will get an invalid model error. Instead, use this one RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe. Trust me, been there done that. (twice)
Once you've done flashing to RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe and you want to unlock, HardSPL, then flash it back to RUU_Kaiser_CINGULAR_WWE_1.57.502.2, then start w/ step 1 from simunlock.
Click to expand...
Click to collapse
Did you mean to attach the ROM because it isn't there? I found this thread http://forum.xda-developers.com/showthread.php?t=335568 and it shows a ATT_SPL ROM. But, I ran out of free download limits from rapidshare for today (tonight). Is that the correct procedure? And when you say "flash" the ROM, please correct me if my understanding is wrong:
1. Get the bootloader running (tri-color screen). In my case, just power cycling does it.
2. Have the .nbh file for the ROM and the KaiserCustomRUU.exe in a folder with no other files in it in your PC.
3. Execute the .exe file which should take me thru the prompts on the PC to flash the ROM. I should see a progress bar on the PC as well as cellphone.
Is this procedure correct?
If I am able to get the device back to original state, I will need to find out how I can get the HardSPL loaded "definitively" as well.
sigh, I thought you know how to flash. Anyway, i'm being nice tonight.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
get the 1.61.502.2 from that link. put your phone into that tri-color screen, run the exe file you just download. That will bring your Tilt back, if you want to unlock the phone, then read my previous post again, and again and again if you still dont get it.
the_passenger said:
sigh, I thought you know how to flash. Anyway, i'm being nice tonight.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
get the 1.61.502.2 from that link. put your phone into that tri-color screen, run the exe file you just download. That will bring your Tilt back, if you want to unlock the phone, then read my previous post again, and again and again if you still dont get it.
Click to expand...
Click to collapse
I know why you feel that way. But, since I screwed up a simple process, my grey cells have really degenerated. My apologies for being dense. I did download that file from the original post of the thread, but now I have run out of free downloads from Rapidshare and I don't have a paypal account. I have to wait another 1hr before it allows me to download. I will try using the Cingular file to flash the device. Fingers crossed!!!
It'll work, dont worry. Just get a new ip and d/l from rapidshare.
Got error 294: Invalid vendor ID, just 1% into flashing. How can I make the phone not go into the boot loader every time I power it ON? Currently, I am using mtty to boot it out of the bootloader.
PS: I had earlier today downloaded the Cingular ROM, but its size as shown in Rapidshare is different from the one you pointed to. I will try that once Rapidshare allows me to.
Looks like the vendor id got screwed up when I had incorrectly flashed the device as I am not able to send emails (POP yahoo mail) or get Direct Push Mail (Outlook) working now. Before this attempt of mine to unlock the SIM, the yahoo and outlook was working fine. Now, during activesync, it says "waiting for network". I am able to browse the internet using PIE though.
I hope the AT&T ROM flashing works.
Downloaded the 1.61 ROM and was able to flash it successfully. It installed all the apps that came with ROM. However, I am not able to access my yahoo POP mail nor my Outlook. I am able to browse the internet though.
Is there a way to get the original AT&T ROM (v1.56) with the 1.27.12.11 radio? I know that that ROM worked fine with my data connections.
Edit: I am able to sync Outlook and Yahoo successfully now with the 1.61 ROM itself.
Thanks to all who helped me with this. I can't thank enough.
Try this first: http://forum.xda-developers.com/showpost.php?p=1894935&postcount=135
i screwed up TytnII
dear all...after flashing my tytnII with DCS V1.3 rom my tytnII is unable to boot up again. the only show on the screen is word "smart mobility" and 3 red lines below it. i have tried everything included hard reset, remove sim card and SD card but still wont help me. i also tried to flashed again but i cannot communicate with activesyn anymore. please if there still way to safe my baby...
Enter to bootloader,and then flash again
thank you for you advice.finally my tyntII is back on line...thanks again my man
jockyw2001 said:
Try this first: http://forum.xda-developers.com/showpost.php?p=1894935&postcount=135
Click to expand...
Click to collapse
Thanks jockyw2001.
Now that my phone is working nicely with the modified AT&T ROM, I want to attempt unlocking the SIM again. I screwed up when I tried to install HardSPL. I will write the procedure here from what I understood from your posts (and thank you very very much for your work). Appreciate if you can confirm that before I show my stupidity again.
Steps:
1. Go to the bootloader by executing JumpSPL1.56-KAIS.exe from the phone
2. Connect thru USB to my Win XP laptop (the loader should show USB)
3. Unzip the contents of flash-HardSPL.zip into an empty folder which will put KaiserCustomRUU.exe and kaiser_hardSPL_1.0.nbh files into the folder.
4. Run the .exe file from that folder which will bring up the ROM loader utility which will automatically load the .nbh file located in the same folder. This will result in the HardSPL being loaded into the phone and the SPL string as seen on the boot loader will change to SPL-1.0 OliPof. Is that a confirmation that HardSPL is loaded?
Can I get out of the boot loader mode after loading HardSPL and continue to use my phone and then attempt the SIM unlocking later?
My phone currently has the AT&T ROm v1.61.502.2 with the Radio ROM v1.27.14.09. Will jocky's unlock method work with this?
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.
Friends,
I read through the faqs, instructions, and did my research. Still, there are a few questions.
I have been successful in upgrading to Gullum's diamond rom which is awesome btw. Now, I am on the prowl checking out other roms from the other authors.
Each time I perform the hardspl which successfully goes through w/no glitches . At the bootloaded screen (tri-color) it shows KAIS1*0 MFG SPL-1.0.OliPOF.
Shouldn't it read HARDSPL Version 3.? after the spl update?
Basically, in a nutshell this is what I did:
1. CID unlock program "kaiser- CID Unlocked
SPL01.0 OLIPOF
2. HardSPL Version (per authors instruction)
3. ROM Upgrade.
Please advise for the advance instruction,
Tvos
Did you jumpSPL before you upgrade to HardSpl 3.xx?
If not, search for JumpSPL!
Also, you dont need to CID unlock everytime. just once is enough.
I agree, it must be the jumpSPL. Jocky's thread is stick in the ROM development.
ditto this happened to me and jumpspl was the answer
no, i didn't use jumpspl before hardspl..
I actually used hardspl 3.56 with Laurentius26 and everything works beautiful!
w/o jumpspl..
All the steps are pretty basic, but question on the following:
1b. pull out the battery, REMOVE SIM and SD CARDS !! and reinsert battery (this step *is* important)
2. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe
** When I copy the .exe to my device, is it to the storage card? Previous step states to remove sim,sd card, and battery.
** If I install JumpSPL1.56 successfully, I don't need to install 1.93 correct?
6. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
7. After I run KaiserCustomRUU.exe, then I should be able to run
HardSPL v3.07, v3.28, v3.29 and v3.56 - per authors instruction.
8. Reload the authors ROM.
Is this correct?
please advise and thank you!
tvos
You copy the JumpSPL onto your device memory!(becuase you have already removed your SD card)
When you install JumpSPL 1.56 without anyproblems then you dnt need 1.93, correct.
Then run HARDSPL 3.xx...
Flash your rom.
tried JumpSPL1.93-KAIS.exe, then SDA application lock still nothing..
okay - did all that and KAIS1*0 MFG SPL-1.0.OliPOF still shows.
any ideas?
tvos
tvos said:
tried JumpSPL1.93-KAIS.exe, then SDA application lock still nothing..
okay - did all that and KAIS1*0 MFG SPL-1.0.OliPOF still shows.
any ideas?
tvos
Click to expand...
Click to collapse
let me ask .. when you first tried to hardspl did you run into whitescreen? if so you probably need to use the same version of jumpspl 1.56 or 1.93 that you used to get past whitescreen. Secondly once you have copied the jumpspl file to your device you have to run it from there.
Hope this helps.
p.s. glad to see you got the rom flashed .. sorry couldn't respond sooner
Hello...
I own the AT&T Tilt and first used app to unlock the device,sid, cid etc.
HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free)
Everything ran fine when updating the rom.
After that, I then ran hardspl thinking that it updated the spl but didn't. After that, moved on to Gullums, Laurentias, and Dutty's rom (testing each one). No problems flashing, however it's not the correct hardspl installed.
So I decided to post and see what could be done to get the correct hardspl on there.. I have tried everything with jumpspl (both versions) and didn't take. I tried this about 4-5 times - nada.
I noticed that HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free) stated for Kaiser, but I own the tilt. Does that matter?
ANy ideas would be appreciative.
Tvos
tvos said:
Hello...
v1 - CID Unlock & Flash any ROM to your device (4 free) stated for Kaiser, but I own the tilt. Does that matter?
ANy ideas would be appreciative.
Tvos
Click to expand...
Click to collapse
no it doesn't as they are the samething except the tilt lacks the front camera. i don't know why u are having problems. using jumpspl i have switched between all of these newer spls provided by jockyw... hmm
tvos said:
no, i didn't use jumpspl before hardspl..
I actually used hardspl 3.56 with Laurentius26 and everything works beautiful!
w/o jumpspl..
All the steps are pretty basic, but question on the following:
1b. pull out the battery, REMOVE SIM and SD CARDS !! and reinsert battery (this step *is* important)
2. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe
** When I copy the .exe to my device, is it to the storage card? Previous step states to remove sim,sd card, and battery.
** If I install JumpSPL1.56 successfully, I don't need to install 1.93 correct?
6. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
7. After I run KaiserCustomRUU.exe, then I should be able to run
HardSPL v3.07, v3.28, v3.29 and v3.56 - per authors instruction.
8. Reload the authors ROM.
Is this correct?
please advise and thank you!
tvos
Click to expand...
Click to collapse
OK. First off, if your bootloader shows you as having an SPL or **Olipof then you have a HardSPL installed. You can then flash to your hearts content. Second, you don't need to flash HardSPL ever again, unless uprading the HardSPL that is. All you need to do is download the ROM and then flash it.
JumpSPL is only used when uprading SPL number that is all. If you install a HardSPL and bootloader says **Olipof or whatever then HardSPL is installed. After this only update the ROM by downloading a new one and flashing........
Hmm,
if it's any consulation, so far I like Laurentius rom...
I will keep trying - just to refresh the steps.
1. remove battery, sim, storage card,
2. insert battery, usb
3. install JumpSPL1.56-KAIS.exe
4. remove usb, re-insert and then run flash hardspl
5. install hardspl version 3.x
correct?
tvos
The steps you have mentioned are correct FOR UPDATING THE SPL VERSION. you dont need to go through this every time. Once HardSPL is installed it stays installed, even after a ROM flash........
If you use the original HardSPL, bootloader shows SPL as 1.0Olipof or something. If you install a newer HardSPL it shows as SPL: 3.28, 3.29 etc Hard.
If you are unsure, go into bootloader and see what SPL version your phone is at. If it shows 1.0 Olipof, 3.28 Hard, 3.29 Hard or [anything else] Hard then you have a HardSPL installed and can flash ANY rom you like. Only one exception to this. DO NOT flash an HTC ROM after HardSPL or you MAY need to re-flash HardSPL before changing it to a cooked one at a later date.
I thought after running "HTC Hard SPL V1 CID Unlock - POF" I then needed to run HardSPL 3.xx.xx . After that, I could upgrade to what ever rom I choose?
If so, I guess that I'm done...
tvos
tvos said:
I thought after running "HTC Hard SPL V1 CID Unlock - POF" I then needed to run HardSPL 3.xx.xx . After that, I could upgrade to what ever rom I choose?
If so, I guess that I'm done...
tvos
Click to expand...
Click to collapse
If you run V1 CID Unlock - POF, check the bootloader for the SPL version. If it says 1.0 Olipof, i think it is anyway. If Olipof is showing in the SPL field of the bootloader then you have version 1 of the HardSPL installed and can flash any ROM. The updated HardSPL's ie 3.28, 3.29 etc are only to try to help with a few minor bugs that some ROM's have. I currently have 3.29 installed on my Kaiser and the Diamond ROM installed and all works like a charm. Any bother give me a shout.
going offline to get some food. Back on later. Good luck. If your bootloader shows Olipof, get a ROM flashed for god sake........lol
DO NOT flash an HTC ROM after HardSPL or you MAY need to re-flash HardSPL before changing it to a cooked one at a later date.[/QUOTE said:
are you talking about a HTC rom released from the HTC for a release update?
right now, i have been using Laurentias rom and I like it a lot! only thing I hate is when the backlight goes dim.. I know there is a hack for that..
I'd like to find a rom that is bare bones, at&t, outlook, office, bluetooth, gps all included then I can start working my way in building it.
I think someone said Rotohammer's rom was built this way?
THank You for all the help!!!
Tvos
Click to expand...
Click to collapse
OK, I am not sure if this is your problem after this long of a thread...
It looks like you are trying to jumpspl 1.56 over hardspl. Instead, run sspl-kais.exe on your tilt after you have removed your cards. Then on your computer, run the customruu with the desired hardspl version.
in kyphurs words:
How to Install 3.2x.Hard SPL:
1. Plug the device into your PC
2. Copy Jump/Soft to your device. use JumpSPL If you have the "White Screen" issue, if you don't, you can use SSPL-KAIS.exe.
3. Take out your SD card & SIM Card.
4. Run Jump/Soft SPL on your device
5. Wait for the bootloader screen to appear and "USB" to show.
6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
7. Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.
8. Run KaiserCustomRUU.exe and flash the SPL
You may have tried this, but it might be that you are just using the wrong jump spl. I have not used the 1.56 version since I don't need it but I think it is for people that can't hard spl. Hope this helps.
thanx dude.. I did all that already, no luck...
I have 1.0 Olipof which is fine. I was able to flash different roms w/no problems and as stated above, I am set ready to go rom upgrading..
so far I really like: L26_Kaiser_DIAMONDV9 rom which works beautifully!
a few little quirks here and there, but these can be tweaked..
thank you all!
tvos
ok, I guess I just don't understand why your phone won't flash the .nbh file to change your hardspl. If 1.0 is working, then who cares, right?
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