Database Develop

Having problem after radio upgrade from 1.02 to 1.06.02

I have a O2 XDA IIs. I can't figure out what I did wrong. After the upgrade, no sounds comes thru speakerphone when I receive a call and call out. This happaned after I used the phone for like a half a day without soft reset. Once I soft reset the unit, it went back to normal. I tried going back to 1.02, but the problem remain.
Here is how I did the upgrade. I extract the xdaIIs_launchROM_v1.12.62_178; remove the files ms_.nbf, nk.nbf and radio_.nbf in the directory; downloaded the french 1.06.02; Put just that ROM into the directory. Start BaUpgradeUt and it indicates the old version and the new version and the upgrade went smoothly without any error.
I did the same thing to go back to 1.02. I tried install all my software from scratch without using the backup, but the problem remain.
I read thru most of the thread and saw there is a tool called xda3nbftool. Do I need to use this?
Appreciate anyone can help!!!!

That tool is only needed if you are trying to do none same carier upgrade.
Thus I would need it as to use the o2 rom on my T-mobile I would need to fix it with that tool and a fix.bat (wiki, getting started)
In your case you are doing a same carrier upgrade.
This should work out of the box (as in run the ship exe).
Most of us have done a radio only upgrade using the 1.06.02 FRA, and have not had any problems.
In your case I would reflash using the launch rom, try it out an you might have a hardware problem.
What I read that you did looks correct.
Only thing I am not sure is did you do a Hard reset after the install ?? But I am sure you did.

Your problem is not the upgrade, I had the same problem when I was using 1.02 radio rom and THAT'S WHY I upgraded to 1.06.02.. The problem seems to be random so far and there's no real fix as far as I know. Do a search, you're not alone with this problem...

I have that problem too when using 1.02, but after flashing to 1.06.02. This problem did still appear twice - I think this is the signal reception problem. You might try to notice that whether this happens always in the same area you are in.

Thanks for all the input. I did not have this problem before I tinker with the Radio ROM. So, I am thinking this may actually related to the ROM flash. I don't think it's related to reception since my provider coverage is very good. I am giving it another try and may ended up sending it in for repair. Having to soft reset every few hours is not fun.
Regards,

leochan2005 said:
I have that problem too when using 1.02, but after flashing to 1.06.02. This problem did still appear twice - I think this is the signal reception problem.
Click to expand...
Click to collapse
I also had this on 1.06.00 and 1.06.02 radio. After upgrading to 1.33 main ROM (from Siemens SX66) I have not noticed such problems. I've also noticed that you'll never have such a problem whan you have a bonded headset, even when headset is powered off.

mamaich said:
leochan2005 said:
I have that problem too when using 1.02, but after flashing to 1.06.02. This problem did still appear twice - I think this is the signal reception problem.
Click to expand...
Click to collapse
I also had this on 1.06.00 and 1.06.02 radio. After upgrading to 1.33 main ROM (from Siemens SX66) I have not noticed such problems. I've also noticed that you'll never have such a problem whan you have a bonded headset, even when headset is powered off.
Click to expand...
Click to collapse
mamaich, I think you are correct. I tried this yesterday by bonding my bluetooth headset which I did not do after the radio ROM upgrade. So far, the problem does not re-surface using the phone for more than 12 hours without soft resetting. What else does the 1.33 main ROM change?

that problem appear 4 times today. When a number get connected, time started counting, no we could not hear each other. Each time I need to soft reset.
Also, using Spite backup 3.14 to recover previous backup including mms and sms, mms cannot be received any more (I sent myself one), but sms ok.
My god! hard reset again....install everything again.

ok. some update. It happened again even I have the bonded blue tooth device. I notice however, if I go activate bluetooth and disable it, it comes back to normal without soft reset.

It seems no one can find out what is happening on the radio of XDAIIs

New Radio 1.13.00

The BA_DT_WWE_DutchRetail_14000_556_11300 has a new radio 1.13
I have converted this to a TYPE I file.
I have updated wiki with that info
http://wiki.xda-developers.com/index.php?pagename=BA_Radio_1.13_Upgrade
It has been tested (that is to say the flash works)
Have fun.

Seems like the GPRS "cannot connect" Problem has been fixed in this stack.
Cant manually reproduce the problem like i used to be able to, so time will tell, but so far so good

problems with no hearing the caller
Is the problem "no hearing the caller" solved with this radio radio 1.13? I can't solve this problem. Can anyone help me?

Re: problems with no hearing the caller
chaniko said:
Is the problem "no hearing the caller" solved with this radio radio 1.13? I can't solve this problem. Can anyone help me?
Click to expand...
Click to collapse
Only time can tell, and it's to early to say yet.

Just upgrade to 1.13 radio.
Let's see.....

MDAIII,
Good job with the instructions which makes it very easy to upgrade. Works better than 1.12 radio. Wish the bluetooth would not give the "insufficient memory" error.
Thanks.

Updated to 1.13
Update works fine.
GPRS Problem seems to be gone. (Works here by now)
SMS works fine (1.12 gave me a little problem here)
Bluetooth works fine (Fast on/off)
Nothing to mourn ATM

No negatives yet here. Haven't encountered the 'no sound' issue yet. I haven't noticed any improvements, though.

I'm glad to hear about the GPRS. Has anyone tested the WiFi feature and how long it takes to connect to activestync? I have notices that my BA, after upgradeing to the new Shipped Asia ROM, takes a really long time to connect to activestync (about 1min.) compared to older radios. Which took at the most 5 seconds to make a handshare.

Will This work on a SX66?

hakushox, it will. Follow the instructions MDAIIIUser has laid out on wiki.

when i just tried it says its not designed for my phone

Then you didn't follow the instructions properly.
You can always use maUpgrade_noID.exe

sprite backup after upgrade??
hi all,
if i upgrade my radio and after the hard reset, i restore with sprite backup, will it downgrade the radio as well?
please reply urgently! i cant resist the temptation to upgrade!

will doing a Radio update only make me have to reinstall all my programs and settings....if so, is there an easy way around this.....

Doing a radio update WILL make you have to do a hard reset. You will get errors when you try to restore your backup using sprite. You will have to re-install your applications after a radio update. Thats why i;m waiting till my questions have been answered before I upgrade since I just upgraded the ROM last week.

TheLastOne said:
You can always use maUpgrade_noID.exe
Click to expand...
Click to collapse
I tried that on the TypeI Radio, diddent work. I diddent try it on the TypeII though but it should work.
studdocs said:
if i upgrade my radio and after the hard reset, i restore with sprite backup, will it downgrade the radio as well?
Click to expand...
Click to collapse
Well I did the nasty thing and used Sprite Backup to restore, wanted to try since this was only a Radio upgrade.
Works perfectly until now.
But to really test this new Radio, one should not use any Restore functions.

Okay, so only time will tell whether this new Radio ROM will fix the known echo issues during bluetooth carkit telephone conversations...
It's been like a day now, I assume peeps who upgraded yet would have made several phonecalls by now... :twisted: hehe
So... wots the verdict?.. :?
Edit: Nevermind, f*ck the verdict. I've gone in, full throttle. I'll let you know the outcome, going for a ride right now.

Hi,
well I have tried, still Echo :-(
I use Radio 1.13 now.
I have echo when only using the MDA and
I have echo when using a Lintech Bluetooth adapter in my Nokia Cark-91.
The first can't be a Bluetooth problem, the second one is a bluetooth problem, even after stack BT-3900.
So I think it's a great device, but as a phone it realy sucks.
I think the bluetooth is the biggest problem.
Hope it can be fixed soon.
Regards,
Max

Just HAVE a bluetooth insufficient memory error.
GPRS seems okay so far.
No caller hearing problem.

Radio Rom Issue ? Reception Issue ?

Have a weird problem and wanted to see if anyone knows a fix.
I have siemens sx66 running wm2003
When using the phone through out the day the phone part of it stops making and recieving calls, even a reset wont fix the issue, after about 5 mins it will reconnect to the network and start to work fine, this happens about 5 times a day. It is not a reception issue since the phone worked fine in my house for the last year, it just started happening.
I upgraded to Helmi AKU3.2 1.3.2b windows mobile 5 and it seems to be more stable. Now when i lose the connection with the network a softreset will allow it to reconnect back to the network. One time when it disconnected i went into device information and for radio rom it said NONE, could this have something to do with the problem, is the phone deleting the radio rom or not seeing it sometimes?

Update:
To try to fix this issue I first smacked it a couple of times, this did nothing to resolve the problem, I then took the entire phone apart to see if there was anything broken, after noticing nothing I smacked the phone a couple of more times. After putting the phone back together the issue is still there.

doing a soft reset when "Radio: NONE" pops up seems to be the only solution.
btw, have you upgraded to Radio 1.15.00?

Hi all.
I'm facing the same issue.
Since I upgraded to Helmi's AKU3.2-1.3.1 I noticed, that the Radio Stack suddenly is lost. You will get no error message. Switching the BA on you will note that the Radio Icon has an "!". Soft resetting will not work. But strange enough, if putting th BA into craddle (or using an USB cable for syncing/charging) and then soft resetting will work, the radio unit is re-enabled again.
I'm now on AKU 3.2-1.3.2 and the issue still exists.
Unfortunately you cannot reproduce this behaviour. Sometimes it happens, but you can be happy and the BA is working for day's without any trouble.
Beside this: the BT stack performance is the worsest I ever met. Just noise, jitter and a very short range using my Headset (Plantronics M2500)
I will try AKU 2.6 this weekend hoping it will be more stable.

yes upgraded to radio rom 1.15 from 1.13 hoping it would fix the issue. Do you guys think the issue is hardware or software?

dr.x
You may want to downgrade from 1.15. There have been several reports in different posts that 1.15 presents several random problems. I installed it for about 2 weeks, but then my phone started making sounds like screetching metal, which led me to believe that I had a loose wire on the speaker or something like that. Then, I remembered about some people complaining about this Radio, so I decided to downgrade. Have not had that problem again. Moreover, I seemed to have weird reception problems in areas where I normally had good signal as well.
All in all, my bets are towards the Radio rather than the BA itself. So, downgrade your Radio and stop hitting your BA before I have to call "BA Services" for domestic violence :wink:
Hope this helps!

dr.x said:
yes upgraded to radio rom 1.15 from 1.13 hoping it would fix the issue. Do you guys think the issue is hardware or software?
Click to expand...
Click to collapse
Hi.
I upgraded to Radio ROM 1.15.00 long time ago und as it worked fine.
As I mentioned before, i faced the problems with disappearing Radio Unit first after I upgraded to AKU 3.2-1.3.1
So I suppose, it will have to do with this ROM Version (AKU 3.2-x.x.x)
Regards
Chuck

Problem with WM5 on BA - No Radio...

Hi
Tried looking through all the threads and checking what I have done but still no joy hence post.
Have upgraded my old BA PH20B (I have another one so no panic) to WM5 with the latest WM2k5_AKU3.2_32mb_v1.3.2 setting Operator to ORANG001 (Orange UK).
1st time I tried everything seemed fine except although I had a signal from Orange I couldnt ring the phone (went to answer machine) and if I tried calling out the call disconnected with 0min 0sec calltime. I did receive a text message saying I had missed a call (me calling phone to test). But couldn't make or receive calls.
So I tried again from scratch twice and both times I have no signal and in Device Info have "Radio version: NONE" - followed instructions to the letter anyone any ideas?
Cheers
RichardC
ps. I can re-flash ROM OK.

this happened to me, too. but only when i changed batteries...
try to soft reset until the word NONE is replaced by the radio rom version (during boot up).
good luck!

Thanks for that, did soft reset and suddenly I have a radio ROM, so removed battery and inserted SIM then no radio again. Soft reset and radio back...weird
Now I can make calls and receive text but can't call phone (engaged or answerphone, maybe network I guess) but also GPRS connection info wrong so guess better start searching for info on that now. lol.
Thanks for the tip.

Check out my signature - use the links provided.

_TB_TB_ said:
Check out my signature - use the links provided.
Click to expand...
Click to collapse
Makes sense thanks...just the GPRS issue now. lol

Just stepped through GPRS settings not changing anything but clicked OK at the end and it works now. Looks like install didnt configure everything fully.
Weird issue I now have is dialling out cancels and yet the phone I dialled rings about 10 seconds later (very weird).
When receiving a call - nothing happens on the BA, no ringing down phone calling out from then when the network drops the call the BA makes a small burp sound. So it knows it should be ringing but something is stopping it.
Tried upgrade to 1.15 Radio ROM - same. So now going to try downgrade to original WM2003SE Radio ROM version (1.06) and see how that goes unless someone has another bright idea?

same issue here
I am now experiencing the same issue, suspect its battery related though...hope someone can come up with something better than that. :lol:

_TB_TB_ said:
Check out my signature - use the links provided.
Click to expand...
Click to collapse
You'll need to update those links for the new forum it seems.

Tried everything but although it all worked phone usage was inconsistant. Sometimes calling out works, sometimes just drops call with duration 00:00. Sometimes receives a call, other times goes straight to voice mail or un-obtainable tone even when signal fine and 2nd BA running WM2003SE works fine (same operator, Orange UK). Bluetooth also needed re-boot most of the time to be enabled. So reverted to WM2003SE for now .

just for comparison i have an xda iis that works fine phone and all and im in wm2k5......except cam doesnt work lol gunna fix taht later .....i used radio version 12.00

hirsty said:
just for comparison i have an xda iis that works fine phone and all and im in wm2k5......except cam doesnt work lol gunna fix taht later .....i used radio version 12.00
Click to expand...
Click to collapse
Thanks for that I tried 12 and then finally went back to standard WM2003SE radio version out of desperation. Nothing worked.
When I have the energy! I may try upgrading my other (newer) BA to see if that helps but first I need to backup my current ROMS as it works faultlessly under WM2003SE...why am I thinking of upgrading I ask myself

Alhumdulillah
everything is working fine for me
AKU 3.2 owns
CAM is fine
ricardo there must be some other problem i hope u didnt drop the phone too many times
looks more like a hardware problem to me

Hi
Phone is 100% OK with WM2003SE, so not a hardware issue...may try again soon, thanks for input.

No Sound in Call (Intermitant)

Occasionally I have a problem where when making or receiving calls I pick up and there is no sound. If I Soft Reset I can make the call and it works fine. It's been starting to happen more often recently, and is really bugging me. It happens both when I'm using the phone speaker, and my headset.

what rom are you using? I have noticed the same thing the last couple of days since upgrading to L26 M2D v1

ah, here it is the same thread.
I use WM 6.1 htc version
Is there no bugfix?

Have you tried flashing a new radio?
Ta
Dave

data at info:
ROM: 3.28.407.0 GER
funkempfänger (i guess it's the radio): 1.65.16.25
protocoll: 25.83.40.02H
it was updated with the new htc 6.1 version what i've heard.
or can i downgrade it to a version that is working fine? when yes, where is the file to do so..

Right now I'm using Radio 1.58.16.27, I'll try another one, which do you recommend?

I was using 1.65.29.22, switched to 1.65.24.36 (I was using this with L26 diamond V12 with no issues)
had the same issue today.

hm, looks like a big upcoming problem for everyone...

what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff

virusv69 said:
what roms does everyone have? any "recently added" apps or changes?
ill start
L26_KaiserTouch_V1_M2D
NETCF 3.5
HTC AudioManager_2_0_1819_2129
Opal stuff
Click to expand...
Click to collapse
Old thread but still, I've been experiencing this issue on the Hyperdragon series of ROMs from late October. Also had this problem in the past on some of Dutty's roms. The latest Raphael version (15/11/2008) has not exhibited this problem in 4 days. Only difference I can see is a slightly newer version of MSVC (1.6.19965).
Cheers.

gatewayer said:
hm, looks like a big upcoming problem for everyone...
Click to expand...
Click to collapse
I am getting the same problem intermittently, with a soft reset as the solution.
I am running a bone stock AT$T rom,recently upgraded to 6.1. It started happening post upgrade.
An upgrade problem?

same here... im playing around with different radios, it has to be a radio issue imo

I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine

1stPeregrine said:
I would just love to have this issue solved. It's not new whatch here; http://forum.xda-developers.com/showthread.php?t=383539
Peregrine
Click to expand...
Click to collapse
My phone rings and notifies just fine when Texts,emails and calls come in. It answers just fine, but there is no sound. Then when I try to call people back, there is no dial sound and the call appears to not go through, until I do a soft reset, then all is back to normal.....................for a while.......................

I'm having this issue also. The other party can hear me when I answer, but I can't hear anything after the initial incoming-call ringing. A power-cycle restores normal operation but only for a while.
ROM: 3.28.405.0 WWE, 05/02/2008
Radio: 1.71.09.01
Protocol: 25.75.40.02.eMo

I'm in same boat as everyone else here.
Sometimes my phones rings, but when I answer I have no sound and other party can't hear me. Other times, my phone doesn't ring and all audio is muted (despite volume on). Soft reset is the only thing that works for me.
I gotta say this is really pissing me off. I'm missing lots of important calls because my phone doesn't ring when it should, or if I'm lucky it rings but has no audio so I have to soft-reset and wait 5 minutes for my phone to reboot & re-establish signal all whilst my clients are trying repeatedly to call me.
I'm willing to try other radios, but no one seems to have any working suggestions.
Thought maybe it was software, since I don't remember this happening after my initial WM6.1 upgrade. Uninstalling S2U2 didn't work (happened again today). Just uninstalled Voice Command, too, but haven't tested yet. VC's been flaky since upgrading to 6.1, working sometimes, failing to announce calls other times, plus occasional VC crashes at boot claiming "out of memory" which is blatantly untrue.
Just out of curiousity, is everyone with this problem using Voice Command, or just some of us?
Think I might have to go back to WM 6.0 since 6.1 didn't solve my Bluetooth issues plus screwed up Destinator...oh well. Schap's WM6 4.31 was best ROM anyway.

Anyone having any luck with this problem?
Like I said, I was running AT$T WM6 with no issues. The I updated to WM6.1 and started having these call issues.
Last week I flashed to HD III still no joy. SJ says that he is running the same radio as me, 1.65.24.36 with no problems.
Is it " my " phone? Microsuck 6.1 ? The radio ? Has anyone solved this with a new radio flash ?
I run a business on this phone and it is getting really frustrating, I don't want to go back to 6.0 just so I can get my phone calls?
I'm not just whining, looking for sucess stories.

Hi, havent been here in a while but i thought i'd add to the list. I have recently flashed HD3 (one of the early november editions) and it was without problems until friday when i dropped my fone. Ever since then i have had the intermittent sound in call which is only fixed by a soft reset (exactly the same as denco7). I haven't changed the radio since dutty's 1st diamond rom (a while ago) as i haven't had any problems but now im thinking about it.
Current setup (from device info):
ROM version: HD_III_Jade WWE
ROM date: 09/30/08
Radio version: 1.65.24.36
Protocol version: 25.94.40.06H
Not using MSVC

Recently flashed to HD III Blackstone hoping this might work but still having the problem.
I also flashed radios 1.65.24.36 and 1.70.18.02
and now I am running 1.70.19.09....... and it is still happening. It has got to be something in WM 6.1. Cannot be a software conflict, because it was happening when I was running bone stock AT$T 6.1 upgrade with no software add ons.
Again, I would hate to think that I have to downgrade to 6.0 just to get my phone calls.

Damn WM6.1 sound!
Well, I thought I'd let everyone know that I've uninstalled all my favorite apps from my Kaiser. No MSVC, no S2U2, occasional hands-free Bluetooth, and no A2DP. In that time, I've had only 2 incidents of no sound for the last 3 weeks--much better than no sound every few days or even several times a day. Don't know that the apps have anything to do with it since denco7 had same problem on an unadulterated AT&T ROM.
The big question is why do we all have the same sound problem but most WM6.1 Kaiser users do not (if everyone did I'm sure there would be a lot more *****ing). If we could reproduce it at will, we'd at least have something to focus on. Not knowing that, I'll have to guess and say that I suspect one or more of the following:
WM6.1 and/or the 1.65+ radios required for WM6.1 introduced some sound bug (deadlock, dereferenced pointer, etc.). The more apps that interact with sound and/or the radio, the more likely the bug will be triggered. But even if this is true, why does it happen to us but not to others?
The bug exists only in a particular base ROM source used by the ROM cookers. Still, should be affecting more people.
Maybe people who customize their phones are more likely to reset and clear any conditions that lead to no sound? Doesn't seem likely, but hey...
The problem exists only in specific Kaiser versions, perhaps even in conjunction with only specific WM6.1 builds and/or radios. I think there's been 5+ different hardware versions of the Kaiser line, but I can't find where I read this or how to tell what version your Kaiser is.
Bluetooth affecting sound? Got absolutely nothing to back this up other than WM6.1 supposedly fixed a lot of Bluetooth problems and during the time of my frequent lockups, I was using A2DP to stream an audiobook to my car's Parrot MK6000. Finished the audiobook & quit traveling so much, so I rarely used Bluetooth during the last few weeks when I've had only 2 no sound incidents. BTW, I upgraded to WM6.1 specifically because of the Bluetooth fixes, hoping they fixed the 100% CPU usage after finishing a hands-free call and fixed the A2DP dropping after calls. WM6.1 didn't fix either, so what did they do? Maybe their "fixes" just introduced new problems?
Possible dead zone f'ing up the radio and consequently sound? I offer this only because when I was working in a particular dead zone I had frequent sound problems. For some reason, my phone has problems reconnecting after leaving this dead zone and I have to reboot. Occasionally it would reconnect without rebooting, but I never correlated this to no sound. However, I haven't been there in weeks, and my problems with sound decreased (although I also uninstalled apps & quit using Bluetooth as much). Went there last Friday, and while I was there I found I had no Windows sounds. Could dead zones or even just temporary signal loss be f'ing up the radio and consequently the sound?
These are all just guesses--I'm just throwing out some possibilities so we can find something in common between us. However, I gotta say that if I don't find a solution soon, I'm going to switch back to WM6. Threaded messages are nice, but they're not worth this no sound headache.
BTW, I'm using:
AT&T Tilt (purchased within a month of initial release)
ROMeOS v4.21.1 (OS v5.2.20273, AKU 1.3.3)
Radio 1.71.09.01