HTC Beetles (HW6515) radio firmware corrupted, need help - General Topics

Hi!
I asked this question first on another board, but XDA-Dev is for me the best board when it come to hard question.
So here's the problem : I think I messed up my device while trying to flash it with a french rom.
I edited the rom and swaped the headers with Hexedit from the english roms to the french roms in :
RadioFS.nbf
RadioOS.nbf
CEOS.nbf
EXTROM.nbf
But here's the problem... while flashing the device, the RadioOS is stuck at 0.1%.
If I remove the RadioOS.nbf & RadioFS.nbf from the hpRUU.ini then it flash the unit, and everything is ok except that I cannot active the Radio (cell phone), it lookup the device.
Here's what I see from the Asset Viewer:
Radio Present : Yes
Radio Firmware Version :
Radio Protocol Stack Version :
Radio Bootloader Version :
Radio File System Version :
Default Radio GDFS Version :
I've tried to reflash the device with bigrom, but no luck, it just flash CEOS.nbf & EXTROM.nbf.
Finally, if I try to flash de device from windows with the ROM12132Beta (with activesync disabled) I get an Error 514 message : device failed verification. So I hacked the rom to get it to flash (with hexedit I replaced the 3 letter language with blank space) but it get stuck at 1.0%.
So do you know if there's is a way to force the flashing of the RadioOS.nbf & RadioFS.nbf? (maybe directly from the SD card?)
Thank you very much in advance!!

Please anybody has a little idea?
Because since this is a US device and I'm in Canada I'm not covered by the warranty, so I'm really screwed. I understand this is an HP device, but it is manufactured by HTC and I'm sure that if there's a place where there's people that know well the HTC devices, it's here.

I have the same problem. I'm going to use a sd card to reflash my HW6515. Did u solve the problem?

Not really... I sent it back for repair...
Not really great because this mean I'm 2 months without my PDA
You can also check this thread at BuzzDev :
http://buzzdev.net/index.php?option=com_simpleboard&Itemid=59&func=view&catid=28&id=23221#23221
Fuzy said :
PS.
When flashing sometime the process stop at1%. I hard reset and started flashing again. Finally after repeated trials, flashing was successefully. So, try to insist.
fuzy
Click to expand...
Click to collapse

Related

fragged my mda_c with official update

Hi all,
yesterday, i thought it's a nice day to do the official german t-mobile 1.12 upgrade on my official german t-mobile mdac. It wasn't.
After the upgrade (no errors) the bootscreen shows:
no gsm, and only one Version number: 1.12.01 Ger
on the bottom line.
After it bootet, i get no gsm and no bluetooth working. When i connect by usb, active sync hangs for about 3-5 minutes. If i try to repeat the upgrade, i get something like wrong device, and it shows empty fields on the version screen. I tried to do the update by extracting the official update rar and start the update by MaUpgradeUT_noID.exe, but it says something like wrong device.
I tried this to the same with the 1.13 upgrade from the xda ftp, same thing. I tried a rombackup from sd-card that i found somewhere on the net, but the bootloader says wrong section=1 not allowed.
Is there anybody wo could help me to resurrect my poor little mdac?
Thanks alot,
J
Hi J.
Don't know how to solve all your problems with upgrading, but did you copy the first bytes of your own romdump to the downloaded rom? Otherwise your device won't accept it, you can find a lott about this in other threads. try searching for BigStorage and you will everything about rom upgrades.
Good luck, M
Upgrade your device with the imate rom 1.12 wwe using MaUpgradeUt_noID.exe ,it should work ,then try to upgrade to the german rom upgrade.
Good luck
ongoing revival
Ok, i tried that big storage thing, i replaced the id in the new image from my backup (broken) rom, and when trying to upgrade from sd-card, i get Section = 1 not allowed update.
I'm trying to upgrade the radio stack from the bootloader screen with MaUpgradeUT.exe, but it seems that the usb port doesn't work: for 10 minutes, the update screen stands at 0%, then an error appears:
Radio Rom Update Error.. i should reset, reconnect and retry.
Any more ideas? Is there a possiblity to do the normal "online" update (not via bootlaoder/backup-image) just from sdcard?
Please Help
J,
Last night I did a BigStorage in a very easy way. I followed the description in the thread about upgrading to radio 1.13. You'll have to unzip the shipped rom, decode nk.nbf it with dnbf. Then you replace the usual bit pattern and encode nk.nb1 again. After that you can use maupgrade with or without the noid function like a regular apgrade.
Hope it helps you, M

no radio-stack after rom-upgrade

Hi!
It's the first time I'm posting here, but after some days of search, I've found a lot about upgrading / downgrading, but nothing about my problem.
I've an MDAcompact / T-Mobile PM10A / Austria and tried to upgrade to BigStorage-Rom according this thread: " Magician to 1.13 + 1.13 Radio + BigStorage ALL-IN-ONE Guide ". I've backed up my original Rom, but after the flash, there was no radio-stack at all (booting device: "no GSM" on display).
I've tried to update the radio-stack again - error message: 114 - error upgrading radio-stack, the same with 1.12 and 1.13. I've tried to downgrade the rom to 1.12 - ok, but no radio-stack. I've tried to restore the original Rom via SD-card in bootloader-mode - device says: not allowed.
Can anyone help me?
Thanks in advance!
did u try to use an origional rom? i mean a non Bigstorage rom upgrade ? because that should fix the problem ( atleast i think it shoud)
Try Downloading the origional t-mobile1.13 rom and upgrade ur device using that install file . If i am not mistaken the first thing that is upgraded is ur radio stack then the extended rom and finally the operating sytem ( if u upgraded u would see that it does it in 3 steps).
I've tried that. As soon, as I upgraded to the original rom from T-Mobile, it stopped at the radiostack-upgrade. After that, I opened the "original".exe-file from T-Mobile with winrar and tried to upgrade again, but without the "radio.nbf"-file, what was no problem. After that, I tried to update with the "radio.nbf"-file (stand alone) again, but the "error 114"-statement came up again.
I got this error before, but only because I flashed my device with the wrong ROM.
(...I once misread "Universal" as a meaning and not as a device codename, and flashed the wrong Radio stack. Thing worked, but radio invalid, no phone capabilities. Fortunately, a reflash with the correct radio ROM found here saved me. And my $300 investment. -.-)
Either the radio part of the ROM's accidentially corrupted (download again), or the radio driver is incompatible with your device hardware. I'm not aware of Minis being avaliable in anything other than GSM tho...
I downloaded the original rom-version from the official T-Mobile website. Fact was: up/downgrade of the rom itself "ms_.nbf/nk.nbf" no problem (I've extracted the exe-file via winrar to a folder and made that several times to up/downgrade), but update of the radio-stack "radio_.nbf" not possible, ended in error 114. The point is: as soon as I start the update-utility, it shows the "Device CE Image version", "Device Extended Image Version" but no "Device Radio Image Version", it looks like no radio-stack is installed at all.
I got that exact same error through the aforementioned Universal ROM debacle (-.-). Radio failed to flash, no radio at all.
There should be a standalone radio stack somewhere in the FTP for magician. I know I saved mine with the 1.12.00 version. Try flashing with that, there's a file inside that allows you to bypass the version detection IIRC (which allows a from-scratch flash). Flashing a standalone radio stack will hard reset your system, but otherwise will not touch anything else.

Simple Question

I have AT&T Treo. Can someone please answer this:-
* I tried to SIM unlock using the 3 step procedure. It did get unlocked BUT the 2nd step failed and 3rd also. Which means that I am now with DOWNGRADED radio. Since I am unable to go to steps 2 & 3 I am not able to rewrite the original backed p radio.
* The phone did not work in London on any network properly, no GPRS and frequent Voce call problems.
* Can someone please provide a new radio or the better one (not the hermes one) from the original ROM
* I can't upgrade to WM6 it says some unsupported device, help
* If I flash the official wm5 on it (if it does) will it become locked again/
OLIPRO why don't you help TRO guys. You are always after HTC !!!!
Read this thread about flashing your ROM/ROW - particularly ppg. 2-3
tmknight said:
Read this thread about flashing your ROM/ROW - particularly ppg. 2-3
Click to expand...
Click to collapse
i tried this but it says unsupported device update
Extract the ROM image from the updater of your choosing and flash using the SD card method. If you need assistance with this, let me know.
alber786 said:
I have AT&T Treo. Can someone please answer this:-
* I tried to SIM unlock using the 3 step procedure. It did get unlocked BUT the 2nd step failed and 3rd also. Which means that I am now with DOWNGRADED radio. Since I am unable to go to steps 2 & 3 I am not able to rewrite the original backed p radio.
* The phone did not work in London on any network properly, no GPRS and frequent Voce call problems.
* Can someone please provide a new radio or the better one (not the hermes one) from the original ROM
* I can't upgrade to WM6 it says some unsupported device, help
* If I flash the official wm5 on it (if it does) will it become locked again/
OLIPRO why don't you help TRO guys. You are always after HTC !!!!
Click to expand...
Click to collapse
WM6 to Wm5, where is the shipped generic WM5 ROM???
summiter said:
Extract the ROM image from the updater of your choosing and flash using the SD card method. If you need assistance with this, let me know.
Click to expand...
Click to collapse
Dear Sumitter, thanks a lot for being so helpful. I have some queries:-
* I have branded treo 750,i unlocked it using the SPL method but could never complete steps 2 and 3, the result was stuck with old radio. I then updated the radio (not the hermes one).So I am on unlocked official wm5 with standard radio.
* When I ran generic wm6, it says unsupported device, what to do?
* I have an unbranded (not done manually,i bought it like that from a store,its from palm) and upgraded it to WM6 by using the generic WM6 release from palm, I want to have the original wm5 generic ROM which was on my device, where can I get that and was it possible to download it from device before the upgrade? Where can I get the shipped generic WM5 ROM for the generic treo and will it be possible to downgrade it?
Please tell me, thanks a lot

Can't upgrade OS BUT phone is unlocked!

So I been trying to upgrade my OS to the tnt 1437, however every time I try my old OS keeps popping up (OS: 5.1.xxx (Build 15671FARIA.3.5)) ... so for the last 3 days I been trying to search this site for any answers, however all I get is that only happens if the CID is locked, but my phone isn't 1) I unlocked it before to upgrade it in the first place to the above mentioned OS and 2) I checked its status with the Wizard Service Tool (which is AWESOME). So i'm at a lose here as to why every time I either upgrade or downgrade the ROM the same OS keeps showing up. BTW Everything else I can upgrade except the OS. Any help is appreciated. thanks!
Anyone? Anything?
Did you remember what version of IPL and SPL when you unlock your Wizard? It is only unlockable when IPL and SPL is 1.xx (i.e. Downgrade to Button's ROM first). You may post your WST log here for more chance to know what the problem is.
Here you go here is the log:
Wizard Service Tool v4.2.1
12/11/07 23:07:22
CPU Manuf. FAILED
MODEL: Wizard
=> Bootloaders:
IPL: 1.01 (G3 device)
Built on Sep 19 2005 at 18:00:32
Copyright (c) 2003 High Tech Computer Corporation
Getting more info...
=> Firmware:
OS: 5.1.xxx (Build 15671FARIA.3.5)
ROM: 3.8
Registry AKU: FARIA.3.5
Radio values FAILED
=>Extended_ROM:
Version: faria V4.0
Name: Extended_ROM
Status: hidden
Getting drives,disks and partitions info...
=> Drives and partitions:
|--Handle--|---Size---|
6e9d5352 - 9.99M (0x9fd800)
eea9813a - 48.23M (0x303c000)
2fb23f92 - 50.95M (0x32f4000)
efb23f3e - 2.94M (0x2f0000)
cfb23fb6 - 3.06M (0x30fc00)
All Done.
Did you flash back to the T-Mobile 2.26 ROM before you tried to flash to another custom ROM?
kegobeer said:
Did you flash back to the T-Mobile 2.26 ROM before you tried to flash to another custom ROM?
Click to expand...
Click to collapse
Yes I tried both the button ROM and the love ROM with no change ... On another note I can change the IPL and the SPL with no trouble however the OS always stays the same.
Not the love or button - the original carrier ROM, either T-Mobile or Cingular.
Have you tried doing a hard reset, and then flash to the T-Mobile ROM from a different computer?
kegobeer said:
Not the love or button - the original carrier ROM, either T-Mobile or Cingular.
Have you tried doing a hard reset, and then flash to the T-Mobile ROM from a different computer?
Click to expand...
Click to collapse
I just tried what you mentioned however I got the following error when I was doing the ROM update .... fyi I got it from the tmobile site ... when I ran the rom update I got:
error [326]: invalid command
this nbf file cannot be used for your pda phone. please check your nbf file.
It looks like you originally skipped the 2.26 rom. I did the same thing the first time I flashed a rom. Try flashing back down to the Button rom, then to the 2.26, then the tnt 1437. It worked for me.
Am I doing something wrong here cause every time I try some downgrade its always the same OS that shows up ... 3.3.0.0 that NEVER changes, everything else does.
i have the same problem..
8125hacker said:
i have the same problem..
Click to expand...
Click to collapse
What OS does your phone boot with?
bad flash rom, you need junk the phone or donate to XDA-developers
first take out the sd card.then flash your phone with buttons 1.0 rom.hardreset. then flash it again with buttons rom. unlock the device totaly with the unlock software. hardreset. flash with original t-mobile us 2.26 rom
halfway above 80% pull the usb plug. the phone get stuck and the update program will tell you it doesnt respond. reset the phone (little hole on the side) you will see the 3 color screen . now restart the 2.26 update and when
you get at the part that it starts looking for the phone connect it. sometimes
it just works , sometimes you need to try a few times.. it wont ruin the phone
as i had this many times due to a crashing computer. wjen its done do a hardreset and install the rom you wanted.
hope this helps you guys
da_jojo said:
first take out the sd card.then flash your phone with buttons 1.0 rom.hardreset. then flash it again with buttons rom. unlock the device totaly with the unlock software. hardreset. flash with original t-mobile us 2.26 rom
halfway above 80% pull the usb plug. the phone get stuck and the update program will tell you it doesnt respond. reset the phone (little hole on the side) you will see the 3 color screen . now restart the 2.26 update and when
you get at the part that it starts looking for the phone connect it. sometimes
it just works , sometimes you need to try a few times.. it wont ruin the phone
as i had this many times due to a crashing computer. wjen its done do a hardreset and install the rom you wanted.
hope this helps you guys
Click to expand...
Click to collapse
Out of curiosity when I downgrade to any of these roms am I looking for the OS to downgrade or just the IPL/SPL?
cgigate said:
bad flash rom, you need junk the phone or donate to XDA-developers
Click to expand...
Click to collapse
how is it a bad flash rom if the IPL/SPL and GSM all change everytime i change roms. The only thing that doesn't is the OS.

Stuck at bootloader

Hi Everybody,
First of all let me thank in advance any help and expertise provided.
So the problem i need to solve is the following. I have the S200 (bought in germany, so it's the O2 XDA NEO), and as soon as i bought it, as it was in german, i managed to flash it with a rom in English (1.5 years ago)
Now, i tried to flash it with a Touch rom (don't remember which. PDA VIET? maybe) and it didn't work and now i'm stuck at the bootload with the current message:
IPL 2.20.0001
SPL 2.20
I've tried several roms and some (apparently) flash but then get back to this bootload screen, others don't flash at all.
Anyone can help me then solving this? I'd like to install one of the Touch roms, if not possible just bring it back to life with any WM5 roms...
Thanks in advance again
Cheers
L
Search for an official WM5 ROM like from o2 or Qtek! Connect your Neo via USB to your PC and start the update process! That#s all to bring your device back to live!
Thanks for the quick reply, but i tried this already but it doesn't work as well. I did somehing to the SPL (i was doing it a bit blindfolded as i'm quite newbie in this) and i think that's why i cannot flash anything anymore, not sure.
Is it normal to have SPL 2.20 (no other digitis after the 20)?
ANd to bring it back to life, do i have to install one of the original roms? can't i simply install the Touch versions?
Thanks again
Cheers
Try a really official WM5 ROM, like from o2 Germany! And when I correctly understand which Touch ROM you mean, it can't be used to recover your Phone!
Ok, tried as suggested but got
error 296
This NBF file cannot be used for you PDA phone. Please newer NBF file
Suggestions?
Thanks in advance
Hmm, also tried with RUU_Prophet_220739_2207119_021921_QTEK_GER_Ship_NO_IPL_SPL.exe
from List of Available Original Shipped ROM Versions, and got Error [300]. This Update Utility cannot be used of your PDA. Get Newer Update utility.
Also tried with this one
RUU_Prophet_220739_2207119_024721_QTEK_GER_Ship.exe
From the same place,
Error [294] Invalid Vendor ID
Help?
find for o2 neo rom, from o2, thats the only way, coz in bootloader u cant bypass CID, so go for google.. or PM me...i willl give u the link!!
or go on the following link.. there is a rar file with no vendor ID.. use that.. u will have ur phone back...
ftp://xda:[email protected]/Uploads/Prophet/Prophet-roms/Original-Shipped-ROMs/
malhaar said:
or go on the following link.. there is a rar file with no vendor ID.. use that.. u will have ur phone back...
ftp://xda:[email protected]/Uploads/Prophet/Prophet-roms/Original-Shipped-ROMs/
Click to expand...
Click to collapse
thank you for your reply, i tried from that link several roms including this one RUU_Prophet_215738_2157127_023021_QTEK_FRE_Ship_NoVendorID.rar
No vendor ID. This was the only one that started the flashing process, but stopped at 80% with the error [326] This nbf cannot be used for your PDA phone. Please check your nbf file...
Anyone, tips?
How to proceed. Thanks in advance for the help provided.
Try PDA Viet Step 1
Try PDA Viet Step 1 Temp
hi
my htc prophet got into boot mode too and wondering how to recover it ...does this method I mean full charge with an original charger work for anyone ....can you please what you got by this exiting experiment .
regards
Try this.
If that fails post again but be more specific e.g. what did you do before this happened?
Having the same problem too, try to flash many rom on my 818 pro, but once the process done, it stucks on boot loader screen
can anyone solve this problem? i have the same
but i can install (flash)rom after flash end and prophet restart it stuk on bootloader plz help me
Try and flash the QTEK NVID WM5 AKU2.2 ROM. I'll find a link soon, but I think there's a copy on skyn3ts FTP.
Try this: ftp://xda:[email protected]/Roms...'s/RUU_Prophet_220734_2207114_024721_NVID.exe
hi the link dosent work pls help us
more info
i have t-com tc 500 wich before i want to upgrade it ,has prophet touch rom version7
sorry i can use the link
downloading
saied 1 said:
hi the link dosent work pls help us
more info
i have t-com tc 500 wich before i want to upgrade it ,has prophet touch rom version7
Click to expand...
Click to collapse
That means it is unlocked. Try the ROM I linked earlier just to get the device usable.
hi thanks for yor fast reply but i download the rom that you link and run it in 80 percent of flashing the new rom i have wait few minutes and in device the process bar become red after afew minutes it goes blue(green) and continue but again in 95 percent get red and after minutes i recive the eror that tell : ERROR [320~328] : INVALID COMMAND please chek your nbf file idont know what should i do
and i found this on read me file that comes with rom you linked above
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
my bouth spl and ipl is 2.58.0001
please help me
2.58.0001
Click to expand...
Click to collapse
Never seen that before...

Categories

Resources