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.
Related
I have problems to use the Hard-Spl v1. I have a new HTC-Kaiser from T-Mobile. I start the Application HARD-SPL (I want to upgrating with Dutty´s ROM)
I run the kaiser-hardSPL.exe on Computer (PC)
I follow instructions on screen!!!!!
on the mobile i the question to start the applikation i answer Yes and then i get a with screen on the HTC Kaiser. NO tri-color-screen !!!
Please help, thx
Thomas
Thomas_Germany_Hamburg said:
I have problems to use the Hard-Spl v1. I have a new HTC-Kaiser from T-Mobile. I start the Application HARD-SPL (I want to upgrating with Dutty´s ROM)
I run the kaiser-hardSPL.exe on Computer (PC)
I follow instructions on screen!!!!!
on the mobile i the question to start the applikation i answer Yes and then i get a with screen on the HTC Kaiser. NO tri-color-screen !!!
Please help, thx
Thomas
Click to expand...
Click to collapse
From what I've read you need to remove your sim card and your microsd card then try again
There is no simcard and microsd in the htc Kaiser.
on the HTC Kaiser is the original T-Mobile software, nothing else
Perhaps your problem is related to new SPL... take a look at http://forum.xda-developers.com/showthread.php?t=349476
Cheers.
When your phone is booting up, look in the lower right corner. If you have a line that reads:
D 1.57.00.00
Then you most likely have the issue in the thread mentioned by jcespi2005. If you have:
D 1.56.00.00
Then its probably something else (as 1.56.00.00 should be able to do the HardSPL).
Why not flash the old SPL to the device then you can use Hard_SPL. I havent checked but arent there original ROM available(of course CID/carrier specific) from before 1.57.
wpbear said:
Why not flash the old SPL to the device then you can use Hard_SPL. I havent checked but arent there original ROM available(of course CID/carrier specific) from before 1.57.
Click to expand...
Click to collapse
The real problem is SSPL used to flash HardSPL is not working with this one, so you can't go back to previous SPL... don't know what shipped ROMs are out that allows flash over this SPL...but perhaps this can be a way to go...
Cheers.
The Rom of my Phone is d.1.56.00.00 !
I do a hardreset, but Hard SPL dont work!
well... for the Tilt you can't flash the "official" ROM back to the device because of an "Invalid Vendor ID", I'm not sure why this is but it just doesn't work. You can however flash the AKU0.4.4 ROM to an unmodified Tilt so the CID apparently is good on that ROM. However I've done this and it does not fix the "white screen" issue on the affected devices.
sirsycho said:
well... for the Tilt you can't flash the "official" ROM back to the device because of an "Invalid Vendor ID", I'm not sure why this is but it just doesn't work. You can however flash the AKU0.4.4 ROM to an unmodified Tilt so the CID apparently is good on that ROM. However I've done this and it does not fix the "white screen" issue on the affected devices.
Click to expand...
Click to collapse
oh well it was an idea. Another reason for me to put off the Tilt purchase.
wpbear said:
oh well it was an idea. Another reason for me to put off the Tilt purchase.
Click to expand...
Click to collapse
I might be returning mine because of this. Bummer.
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?
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
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