Related
How does one go ahead and flash to an updated Radio Rom on a G4 Cingular locked Wizzard? I am currently running NBD 8.0 using 2.25 radio and would like to try out faria's 2.69 radio...and have the nk.nbf file for the radio. Do I just flash it using ShellTool as I have done with all the other full operating systems? Is this even possible to flash the radio on a G4 locked device?
http://forum.xda-developers.com/showthread.php?t=319751&page=18
im not sure if you read the nbd 8.0 thread lately but you asked this similar question and it was answered for ya if you still dont understand just mail me
mdajunkie said:
http://forum.xda-developers.com/showthread.php?t=319751&page=18
im not sure if you read the nbd 8.0 thread lately but you asked this similar question and it was answered for ya if you still dont understand just mail me
Click to expand...
Click to collapse
oh, sorry man totally missed your response
my only last question is, do I still copy over and run the cert and enablerapi cab's on the phone before I use shelltool, or just flash the rom without it?
fliplyricist1 said:
oh, sorry man totally missed your response
my only last question is, do I still copy over and run the cert and enablerapi cab's on the phone before I use shelltool, or just flash the rom without it?
Click to expand...
Click to collapse
no you dont need to run those cabs again. all you have to do is just replace the nk.nbf file and run shell tool and thats it less than five minutes and your working with a new radio. Now if 2.69 dont satisfy you look in the cingular and t-mobile radio threads i have posted a zip file with a variety of radios collected from all over the wizard forums so you can test and try them all if you like. enjoy
edit: the file should be in the first or second page of each thread
i don't believe that you have to use the shelltool method in order to flash a radio rom. on my first rom flash, i followed the "Faria G4 Step by step installer with instructions" and did use shelltool for the OS part, but i used the regular RUU and flashed the 2.19.11 radio with no problems, without installed the enable rapi and cert cab.
thanks a bunch guys...im going to flash it now
are you going to go through the shelltool process? or install it simply with the RUU? i know it's a lot to ask you to put your device at risk but i'd just like to know if G4 Radio ROMs can be upgraded with RUU. i'm using 2.19.11 right now (with the radiofix) but i've heard 2.69 can give me better results. just would like to see if i can go the easier, RUU route.
Azimuth21 said:
are you going to go through the shelltool process? or install it simply with the RUU? i know it's a lot to ask you to put your device at risk but i'd just like to know if G4 Radio ROMs can be upgraded with RUU. i'm using 2.19.11 right now (with the radiofix) but i've heard 2.69 can give me better results. just would like to see if i can go the easier, RUU route.
Click to expand...
Click to collapse
just a headsup...but a shelltool 2.69 flash messed up my nbd installation (would freeze at the nbd splash screen)
had to flash back to original factory cingular rom, and then reflashed the radio using ruu tools....and it worked perfectly.
now im just trying to reinstall nbd succesfully (always have a hard time with 8.0 for some reason)
Hi I'm thinking of returning my m600 to the Orange SAV because of a speaker problem.
I tried a wm6 ROM and then downgrade (with difficulties) to my original wm5 rom , then found a way to put original orange bootloader screen, but the extendedROM is still the PDAMobiz Prophet WM6 (and there is no more installation process at hard reset like when I was using wm6), and I need to put the one which was furnished by Orange (I have a backup of it using awizard).
I succeed in unhidding the extendedROM2 folder (thanks to another post), then delete the PDAMobiz files and put the Orange one, but after hard-reset nothing install, and when I reveal the extendedROM2 folder PDAMobiz files reapear.
So I hope there is another way to restore my orange content.
What about the warranty if it has been flashed and then downgrade and make it as the original one?
thank you for helping a Newbie
Strange Official ROMs include extended_rom that are written upon flashing process. Are you sure you used an official?
Else...
You can try to use my software (WST - check signature) that, although made for wizard, i believe will work.
Best thing is to use the READ ROM feature before flashing to be sure that the addresses are the same (should result in a 10MB file that can be opened with Winimage)
The other way is to get pdocread.exe and itsutils.dll and get the extended rom partition handle and then use pdocwrite to flash an extended rom.
Last option is to get an official RUU and extract the nk.nbf and then from it extract the extended_rom chunk. Then make a nk.nbf with only that chunk and pack it back into an RUU exe.
your choice
You flash your Orange Rom wrong!
If you use a Original Firmware ... all are overwriten! Ext Rom too!
Don't worry, the first thing Orange do when the phone reachs their labs is to flash it with the official rom, test it and send it back to another customer if it works.
I think even with your pirate wm6 rom you would have met no trouble but I'm quite sure they won't even notice you changed the ext-rom.
If you really want to be sure, just unlock the extrom, delete the content and relock it
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.
Hello everyone!
I need complete ROM WM6 not just upgrade. The same way we install new operating system after formatting hard disk.
Due to so many trials (sometimes successful sometimes unsuccessful) of flashing hacked ROMs, I think so many files either got displaced, missed or corrupted. Due to which some testing results unwanted things.
If somehow, we succeed to get complete ROM not just upgrade we can assure ourself that phone is safe atleast in terms of testing.
Thanks everybody
Em, each ROM here is a complete OS. There is nothing that stays behind if you flash another ROM to your phone...
frauhottelmann said:
Em, each ROM here is a complete OS. There is nothing that stays behind if you flash another ROM to your phone...
Click to expand...
Click to collapse
Somewhat agree but I've a question just to clear my confusion because I'm facing lots of problems and I want to minimise all. Previously, I run uspl_116_jockyw.bat I never used rom update utility of USPL instead I run ROMupdateUtility of ROM. Somedays back I ran SD card flashing but unsuccessful due to that I flashed ROMupdate Utility of USPL first time and finally I succeeded to flash ROM. After that I noticed I never need to run USPL again.
Now my question if we're flashing complete ROM and we're making new installation not just upgrade then USPL nb files must be removed from vox. Am I correct? If not I'm sorry.
Thanks
No, the SPL, Radio, Spalsh Screen and the OS are all diffenrent parts. All unofficial ROMs here are just the OS. So if you only flash unofficial ROMs nothing will chnage the other parts. It's different with the official ROMs, which usually contain SPL and Radio too.
ragsAnurag said:
Somewhat agree but I've a question just to clear my confusion because I'm facing lots of problems and I want to minimise all. Previously, I run uspl_116_jockyw.bat I never used rom update utility of USPL instead I run ROMupdateUtility of ROM. Somedays back I ran SD card flashing but unsuccessful due to that I flashed ROMupdate Utility of USPL first time and finally I succeeded to flash ROM. After that I noticed I never need to run USPL again.
Now my question if we're flashing complete ROM and we're making new installation not just upgrade then USPL nb files must be removed from vox. Am I correct? If not I'm sorry.
Thanks
Click to expand...
Click to collapse
My understanding it that it's because USPL & ROM are stored on seperate Flash memory so Flashing USPL will not Remove your ROM and Flashing ROM will not remove the USPL.
Roland
Ok,
Do you feel flashing OS don't damage other parts or flashing other won't effect OS?
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