[q] error [296] : Upgrade only - 7 Mozart General

I tryed this ROM on my Mozart:
ERROR [296] : UPGRADE ONLY
I get an Error mesage of (296) upgrade only and it says The NBF file cannot be used for your phone, please get a newer NBF file. Can anyone help me out without me having to bake my phone? Any answers would be great!"
In about phone is PD67100

nikolav said:
I tryed this ROM on my Mozart:
ERROR [296] : UPGRADE ONLY
I get an Error mesage of (296) upgrade only and it says The NBF file cannot be used for your phone, please get a newer NBF file. Can anyone help me out without me having to bake my phone? Any answers would be great!"
In about phone is PD67100
Click to expand...
Click to collapse
I need some info from you (link to the rom) but to flash roms with different vendor id's we need HSPL , and HSPL isn't jet developed .

Related

English Cingular 8525 ROM update available: v1.34 radio 1.16

Here is another new ROM from the still unreleased Cingular 8525: HTC Hermes (HERM100) branded from U.S. Operator Cingular.
ROM Version: 1.34.502.1
ROM Date: 09/22/06
Radio: 1.16.00.00
Bootloader: 1.06
As always, download link on the wiki upgrading page:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades
If you have questions be sure to read the Hermes wiki first, specially the Upgrading FAQs.
Notes on this ROM:
* See the threads on the previous Cingular ROMs for upgrading issues such as enabling video calls, band selection tab, ExtROM customizations, PTT button, etc...
-v1.30
-v1.31
-Downgrading instructions
UPGRADING INSTRUCTIONS:
* People with bootloader <= 1.04 just follow the normal procedure (run RUU twice after invalid vender ID error).
* People with bootloader 1.06 (those who have flashed the cingular 1.31 rom) need to downgrade to bootloader 1.04 first:
1) Put your device in bootloader mode by holding the side Ok button and the power button and at the same time reset with the stylus.
2) Upgrade to a ROM matching your CID, that is a ROM from your vendor (TyTN owners use the TyTN rom, dopod owners the dopod rom, jasjam owners the imate rom, etc...). This will get you back to bootloader 1.04
3) Flash the new 1.34 ROM as usual (run RUU twice after invalid vender ID error).
Enjoy
Guys, i'm at work and still haven't had time to flash it on my Hermes, so the first flashing it please update the OS build and protocol version on the wiki. Thanks
Any chance that we have release notes for this ROM uploaded as well?
Thanks.
cant run the rom file, it said file corrupted. i downloaded twice, both time it said rom file is corrupted. please re upload the rom
Tried to flash from 1.31 to 1.34 - but I get error message ERROR [294] INVALID VENDER ID
Anyone had any luck flashing 1.34
Doesnt upgrade from 1.31 - just get an invalid vender id error...
EDIT: can't downgrade either using the bootloader method - seems like we are now stuck on this rom until a solution is found!
Have you tried to restart the falshing SW without touching the hermes and without disconnecting the USB?
You are supposed to do this a second time when you get this error
Eric
Eric Duprat said:
Have you tried to restart the falshing SW without touching the hermes and without disconnecting the USB?
You are supposed to do this a second time when you get this error
Eric
Click to expand...
Click to collapse
Yep - tried this with Dopod, Cingular 1.30, and HTC ROMs - all get the same invalid vender ID error...
tried that, but it is no help
ROM FILE is corrupted. download 3 times, everytime it got erros and said the rom file is corrupted. please re upload the rom
netboy said:
ROM FILE is corrupted. download 3 times, everytime it got erros and said the rom file is corrupted. please re upload the rom
Click to expand...
Click to collapse
ROM file is fine. Runs OK here - just cannot flash to a 1.31 device...
netboy said:
ROM FILE is corrupted. download 3 times, everytime it got erros and said the rom file is corrupted. please re upload the rom
Click to expand...
Click to collapse
Clear your cache, rom file is OK, I checked the md5sum of it.
Same here - Invlid vendor ID.
Something's fishy here. Some can downgrade and some cannot. What's your device's CID awharton if I may ask?
It makes sense that a direct upgrade from 1.31 -> 1.34 will fail. However, a downgrade to the original TyTN ROM for users having a real TyTN (CID QTEK_001) followed by an upgrade to 1.34 should work. I believe TyTN owners have been reporting success at downgrading from 1.31 although this is mystifying too as one would expect that the bootloader version downgrade should prevent this also....
Sleuth255 said:
Something's fishy here. Some can downgrade and some cannot. What's your device's CID awharton if I may ask?
Click to expand...
Click to collapse
Its a Orange M3100 SIM unlocked (HERM100)
let me REBOOT my pc and try again.
i cleared my cache. still got erros. and said can not unpack, file is corrupted..
@people getting invalid vendor ID:
Please report:
- which device do you have: TyTN, Vario II, SPVM3100, DOPOD 838pro, etc...
- Your device CID: QTEK_001, CDL__001, O2___102, etc... can be checked by "info 2" bootloader command, leave blank if you don't know it.
- Current ROM on your device before trying to upgrade
- Bootloader version
Sleuth255 said:
Something's fishy here. Some can downgrade and some cannot. What's your device's CID awharton if I may ask?
It makes sense that a direct upgrade from 1.31 -> 1.34 will fail. However, a downgrade to the original TyTN ROM for users having a real TyTN (CID QTEK_001) followed by an upgrade to 1.34 should work. I believe TyTN owners have been reporting success at downgrading from 1.31 although this is mystifying too as one would expect that the bootloader version downgrade should prevent this also....
Click to expand...
Click to collapse
True - thinks this makes sense. As Orange haven't released an upgrade yet I can't test this out. Need someone that has a Dopod or TyTN to experiment...
I'm trying this now. I got the same invalid vendor ID (HTC TyTN, running 1.31), and now I'm flashing back to 1.18. This seems to be working, albeit very slowly. I'll keep you updated if I can upgrade from 1.18 - 1.34; the flash to 1.18 should take about 25 minutes.
For people on Cingular, does push to talk work on this rom? If not, then this is not the final rom.

Error 238 or 300 when trying to flash RUU_TMobile_US_226102_22610105_022511_WWE_Ship

I used HardSPL successfully on a Wizard that was formerly:
IPL 2.21.0001
SPL 2.21.0001
GSM 02.19.11
OS 2.21.2.8 GER
It's showing SPL 2.21.Olip, yet all my attempts to flash the phone with the Original T-Mobile USA Rom (RUU_TMobile_US_226102_22610105_022511_WWE_Ship) end up with errors.
If I use the RUU provided with the above ROM, it ends up with an Error 300 (Invalid Update Tool). Using SoftSPL or RUU MUN with the .nbf-file from that package both ends up with an Error 238 (File Read).
I just want to turn this T-Mobile Germany phone into one with the Original T-Mobile USA Rom so if anyone knows how to do this, solving the above problems, any help would be greatly appreciated.
Just to make sure, with an Original shipped Rom such as the T-Mobile USA one, I don't have to make sure to extract the provided IPL/SPL-files it contains before flashing on my G4, do I?
Scotty_73
try this:
Scotty_73 said:
I used HardSPL successfully on a Wizard that was formerly:
IPL 2.21.0001
SPL 2.21.0001
GSM 02.19.11
OS 2.21.2.8 GER
It's showing SPL 2.21.Olip, yet all my attempts to flash the phone with the Original T-Mobile USA Rom (RUU_TMobile_US_226102_22610105_022511_WWE_Ship) end up with errors.
If I use the RUU provided with the above ROM, it ends up with an Error 300 (Invalid Update Tool). Using SoftSPL or RUU MUN with the .nbf-file from that package both ends up with an Error 238 (File Read).
I just want to turn this T-Mobile Germany phone into one with the Original T-Mobile USA Rom so if anyone knows how to do this, solving the above problems, any help would be greatly appreciated.
Just to make sure, with an Original shipped Rom such as the T-Mobile USA one, I don't have to make sure to extract the provided IPL/SPL-files it contains before flashing on my G4, do I?
Scotty_73
Click to expand...
Click to collapse
hello, sometimes the RUU is old, and is not possible to flash roms (because is ooold tool ok)
try downloading a newer RUU and copy the .NBF file in to the RUU folder, now you should be able to flash the ROM you have choosen to your WIZARD
GOOD LUCK!!!
tigrisimo said:
hello, sometimes the RUU is old, and is not possible to flash roms (because is ooold tool ok)
try downloading a newer RUU and copy the .NBF file in to the RUU folder, now you should be able to flash the ROM you have choosen to your WIZARD
GOOD LUCK!!!
Click to expand...
Click to collapse
Thanks for your advice but how could the RUU included in a rom package be outdated if it's specifically meant to be used to flash that rom? I did however follow your suggestion and tried several other RUU's as well, unsuccessfully unfortunately. I would expect the newest available T-Mobile USA Rom would have included the newest available RUU.
So, are there any other suggestions?
if you have a G4 use my setting... i used softspl & romupdatutility_noid...
i´ve uploadet it for you...
just copy in the nk.nbf in the folder and run START-sSPL.exe !

Help please...For my HTC Fuze

well i decided today to Flash a ROM on my HTC Fuze and was following all the steps but then an Error message popped up when I was running the ROM which states
ERROR [296]: UGRADE ONLY
This NBF file cannot be used for your PDA Phone. Please get a newer NBF file.
what is a NBF file? how do i get a newer NBF file?how do i upgrade the NBF file I have now?
Thank you in advance..
jigganotguilty said:
well i decided today to Flash a ROM on my HTC Fuze and was following all the steps but then an Error message popped up when I was running the ROM which states
ERROR [296]: UGRADE ONLY
This NBF file cannot be used for your PDA Phone. Please get a newer NBF file.
what is a NBF file? how do i get a newer NBF file?how do i upgrade the NBF file I have now?
Thank you in advance..
Click to expand...
Click to collapse
Did you hard spl before flashing?
http://forum.xda-developers.com/showthread.php?t=410150
Otherwise try to download the package again and reflash.
EDIT:
Your error could also refer to a wrong RUU, try this custom RUU:
http://forum.xda-developers.com/showthread.php?t=410761
I did Hard Spl before i attempted to flash RC4 elite ROM...
jigganotguilty said:
I did Hard Spl before i attempted to flash RC4 elite ROM...
Click to expand...
Click to collapse
And you tried with a custom RUU?

A big Mistake, I flashed my room with the Radio NBH file

Dear Gentlemen,
I mad a big Mistake, I flashed my room with the Radio NBH file, My room v. 1.25 , IPL-V1.00
ATHE100, SPL-V1.07.0000. I download the new Radio 1.57 NBH file and use the ROMUpdateUtility.exe wich I got it from the Temp files came from upgrading the room to 6.5. coz I did not know how to upgrade the radio.
The proccess began and after few seconds the device stope responding except that I can but it in bootloader status. I think the Room is dameged and I need a way to recover the system again and upgrade it to the leatest ver.
Please if someone can Help.
Thanks.
I did try flashing the room
I did try flashing the room with "Athena_SPL1.2_WM6.1_R0-CleanEdition_MiChY" but I got this message ERROR [270] : update error.
another error
This is another error, Please see the attaches image. whem i'm trying to flash it with another room.
ahmadkaram said:
Dear Gentlemen,
I mad a big Mistake, I flashed my room with the Radio NBH file, My room v. 1.25 , IPL-V1.00
ATHE100, SPL-V1.07.0000. I download the new Radio 1.57 NBH file and use the ROMUpdateUtility.exe wich I got it from the Temp files came from upgrading the room to 6.5. coz I did not know how to upgrade the radio.
The proccess began and after few seconds the device stope responding except that I can but it in bootloader status. I think the Room is dameged and I need a way to recover the system again and upgrade it to the leatest ver.
Please if someone can Help.
Thanks.
Click to expand...
Click to collapse
Sorry to hear this.
You should have read a bit more first as you would have realised that you can't flash a radio without unlocking.
Using the unlocker would have changed the SPL to 1.2 and allowed you to flash the radio.
Have you tried doing a hard reset first?
You can only flash the original branded ROM for your machine now if you can find it.
Have a look in the wiki for original shipped roms.
I have a feeling the SPL1.07 was a dutch or german ROM that is very hard to find.
Good luck
Regards Lakeman

Update to 1.66 FAILS

Hi
My HD2 is original unmofidied one. Has stock ROM and I didn't install anything on it yet. I went to update the ROM version to 1.66 from the link posted on the first thread on this forum.
My phone is HD2 with these versions:
ROM 1.48.707.2 (71294) WWE
ROM date 11/09/09
Radio version 2.05.51.05_2
Protocol version 15.28.50.07U
Tried to run the file RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
Program starts working, changes the display on my HD2 to the reb/blue/green HTC preboot screen and then displays the gauge. Going into about 2% of the process of updating the ROM I get the following error message:
ERROR [294] : INVALID VENDER ID
This Update Utility cannot be used for your PDA Phone. Please check your Update Utility.
Why is that? I thought that ROM above is stock rom unmofidied and that should flash just fine without any tweakings at all on my HD2. I don't want to mess around with my HD2, just wanted to update the ROM.
hi
you must apply HSPL before upgrading your rom ,the subject have been treated in another topic .
every hd2 is cid locked... so you can only install rom that you download from htc website using your serial number.
however you can use
1. goldcard method http://forum.xda-developers.com/showthread.php?t=572683 to flash any original rom regardless of language/region
2. use uspl , http://forum.xda-developers.com/showthread.php?t=606713
it flashes any ROM using the original SPL to your device (no warranty void)
3. use hspl http://forum.xda-developers.com/showthread.php?t=611433
you can also return to your original spl if you need it for warranty , everything is explained in that threead

Categories

Resources