Database Info

Upgrading Radio on G4 locked device?

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)

NBD 8.x doesnt do anything!

Hy everyone. I tried installing NBD 8.1, 8.2, and 8.3 on my phone today and it goes well. It says it has finished updating my phone and then when I start my phone, it says its being customized and I see everything being installed. After it is done installing, it resets. When it resets it is just the same old thing. It looks the same way it did when I first bought the phone. Im using a Cingular 8125 if it makes any difference. Thanks.

Your phone is still CID locked.
Follow this tutorial to unlock it, and follow the steps closely.

i wouldnt follow that tutorial just yet. You still need to give us a little more information like if your wizard is a G3/G4. You can only cidunlock your wizard if it is a G3.

I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek

mirekluza said:
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
Click to expand...
Click to collapse
I agree! I'd been flashing my G4 phone from about 5 months ago with different ROMs (almost continuously)... ShellTool is the best tool that I tried to flash ROMs without risk.
Cheers!

mirekluza said:
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
Click to expand...
Click to collapse
nobody bothers to read anymore and dont know what the search link looks like. The just jump on the bandwagon. But its true i had a hard time following some instructions but i got through it.

Really??
I used shelltool 2 times without problem, but then i get the 1 time a message - flashing done after 8 minutes and the flash wasnt really on the phone. Since then i use RUU (which is in the love wizard rom package) and it works for me.
Today i tried flashing nbd 8.3 to faria aku 3.3 and other faria rom with aku 4. In both casec the flashing stoped at 99% and i had to reflash it with nbd rom.
The flash didnt end , cause i have cid-locked phone?? I would like to have a newer aku(i have 2.3). HELP

I used Shelltool to install the rom I had. It finished after about ten minutes, and then I hard reset my device.
Whenever I start my phone up now it just hangs on the Cingular start up screen and this is what it says.
IPL 2.25
SPL 2.25
GSM 02.25.11
OS 6.6.6.666
Any idea what went wrong or if there is any way to fix this?
Thanks

Are you using Vista?

Nope. I used Windows XP Pro.

I had the same problem with shelltool on xp pro sp2. Get the phone in bootloader mode and flash again. Maybe with RUU , which is in the wizard love rom package. Just replace the .nkb file (rom file) to one u want.

I don't like this topic name. It should be: "I don't know how to install new rom"

A few advices from long time shelltool user
(I used it to flash "faria real thing", several version of "crossbow reloaded", "xda mobile", "pandora", "wrcx3"). I am on a locked G4 phone.
a) I always start by flashing the original ROM of my provider (in my case T-Mobile CZ) in normal way. This may not be a needed, but I read that it is *recommended*to flash your provider's ROM to have some stable base. It takes about 10 minutes or so.
b) Afterwards I flash using shelltool (see shelltool documentation how it is done)
Possible problems with shelltool
a) It does not end and the flashed phone seems to be frozen (clock is not updated etc.):
No problem, flash is done. After 30 minutes from the flash start just take your phone, do the hard reset and everything will work ok.
This (shelltool not ending) happens often, but as I said - it is no problem.
b) The wrong flash
Either the shelltool is interrupted prematurely or it the phone freezes during restart afterwards.
No problem, just reflash your provider's ROM in normal way and try again shelltool.
This happens only very rarely and I never went through this more than once.
Conclusion
Since the shelltool is limited to flashing only OS, you should not ever brick your phone in this way... The most you can do is to screw up your OS - which can be quickly recovered by flashing the official ROM from your provider.
Flashing by normal way is more dangerous: if you flash a locked phone with the ROM containing more than just OS, you can easily brick your phone (if you flash ROM just with the OS you will wonder that nothing has changed - at least this is like I understand it).
Mirek

zoki said:
I don't like this topic name. It should be: "I don't know how to install new rom"
Click to expand...
Click to collapse
I have to agree with you Zoki. Has nothing to do with your ROM.

zoki said:
I don't like this topic name. It should be: "I don't know how to install new rom"
Click to expand...
Click to collapse
I'm sorry. I didn't mean to offend you or anything. I just thought I did it the right way the first time and that something went wrong but not on my part because I followed directions doing it. I'm not saying anything bad about the rom. Sorry!!
I'll try to do it with the RUU then. Thanks a lot.

Is my phone half bricked?

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

Can someone please point me in the right direction? New Vista comp, need hard SPL

I've been out of the loop for a while. I just bought a new computer with Windows Vista and I just got a Tilt tonight. Trying to find out where to begin reading to unlock, Hard SPL and flash the MobileVista 3 Premium ROM. It's kind of confusing with all the old links. I don't know what's Vista compatible or not.

CID unlocking is tottaly your choice. Alot of ppl would say that its better (and they are probably right) but before attempting that using vista you have to play with the PC's drivers (to make it resemble XP)
those type of unlockers are probably the only thing u might face trouble with using vista...
but since ur warranty is still applicable, just flash hard spl. It will do the needful perfectly and after that u can flash any ROM u want. U can flash hard spl and roms using vista without any problems
go here for flashing hard spl
http://forum.xda-developers.com/showthread.php?t=396922
if there is a particular ROM you have ur eye on, go to the thread of that ROM and see what hard spl the chef reccomends (as there is more than one type of hard spl)
good luck

mazin13 said:
CID unlocking is tottaly your choice. Alot of ppl would say that its better (and they are probably right) but before attempting that using vista you have to play with the PC's drivers (to make it resemble XP)
those type of unlockers are probably the only thing u might face trouble with using vista...
but since ur warranty is still applicable, just flash hard spl. It will do the needful perfectly and after that u can flash any ROM u want. U can flash hard spl and roms using vista without any problems
go here for flashing hard spl
http://forum.xda-developers.com/showthread.php?t=396922
if there is a particular ROM you have ur eye on, go to the thread of that ROM and see what hard spl the chef reccomends (as there is more than one type of hard spl)
good luck
Click to expand...
Click to collapse
Thanx for the reply. How to I fix the drivers? The recommended IPL SPL was this: IPL CPLD-8
SPL 1.0.OliPof
My phone is used, it's not under warranty, so I'm not concerned about returning it. CID or Hard SPL? Which do you think would be better? I just want to flash different ROMS until I find one I like.
Flashing was so much easier with my Artemis.

Clarification about SPL

I've read the wiki article about SPLs, located here
http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
What is the difference between Flashing and installing?
And I've a few clarifications to make. There was this note that says "You should never use a SoftSPL to flash a full ROM to your device. You should only use them to flash a new SPL and once the new SPL is on your device, then flash the ROM! This is why you need to extract the SPL and flash it first and then once it is "HARD" on your device you can flash the ROM."
From what I understand, a SoftSPL cannot be used immediately until the SPL is extracted first, then flash it, then flash the ROM.
Then why not provide 2 things, the extracted SPL and the ROM, rather than both in one, and thereby create the need for the warning in the article?
Sorry if I sound like a noob, cos I really am!
Thanks!

ferns_mccanus said:
I've read the wiki article about SPLs, located here
http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
What is the difference between Flashing and installing?
And I've a few clarifications to make. There was this note that says "You should never use a SoftSPL to flash a full ROM to your device. You should only use them to flash a new SPL and once the new SPL is on your device, then flash the ROM! This is why you need to extract the SPL and flash it first and then once it is "HARD" on your device you can flash the ROM."
From what I understand, a SoftSPL cannot be used immediately until the SPL is extracted first, then flash it, then flash the ROM.
Then why not provide 2 things, the extracted SPL and the ROM, rather than both in one, and thereby create the need for the warning in the article?
Sorry if I sound like a noob, cos I really am!
Thanks!
Click to expand...
Click to collapse
Think of it in PC terms, installing is downloading a program Adobe Flash or
Itunes ans installing it on your hard drive. Flashing is like going from Windows XP to Vista, you are replacing your operating system.
Generally , anything installed will get erased after a hard reset, anything flashed will survive a hard reset.
Generally the spl's are extracted from the roms already and are available in the forum to flash to your phone. Once your phone is flashed with Hardspl there is no need to flash a new spl for every rom.
Stock roms come with a new spl for every version, cooked roms do not contain an spl. There fore your phone must be flashed with a hard spl prior to flashing a custom rom.
Some say that when flashing a cooked rom that you should , for performance sake, flash the patched spl (hardspl ) that came with the rom that the cooked rom is based on ie: 3.56hard for roms that are based on AT$T 3.56.xxxx 6.1 roms or 3.34hard for 3.34.xxxxxx WWE based roms. I personally have seen no " hard " evidence of this. I have always used 3.29Hard whether I was flashing stock or cooked roms.
For more info, Dave has a nice thread on this
http://forum.xda-developers.com/showthread.php?t=498320

Further clarification about ROMs
Thanks for the reply, I think I'm understanding all these a bit more.
Another thing to clarify:
Basically, my phone comes with PAPAGO, a navigation software pre-installed. In other words, after a hard reset, it's automatically installed. So if I do a ROM upgrade, does that mean I won't have this software anymore?
Thanks!

ferns_mccanus said:
Thanks for the reply, I think I'm understanding all these a bit more.
Another thing to clarify:
Basically, my phone comes with PAPAGO, a navigation software pre-installed. In other words, after a hard reset, it's automatically installed. So if I do a ROM upgrade, does that mean I won't have this software anymore?
Thanks!
Click to expand...
Click to collapse
That is correct, you will not have it anymore, unless the new rom includes it.

but im pretty sure there is a program to install from a sd card to newly flashed rom. so if the navigator software is on card then you could do this