Database Info

What is radio_dump!?

I have a TON of these 37mb files on my SD card. They are all *.bins. What are they?

Anyone.....

sounds like a crash dump from a debug version of a radio app.
Sent from my Nexus S using XDA App

There are literally like 100 of them. The dates and and times are Xmas and every five minutes.

this also happened to me, but yesterday. do you have the app tunein radio? i think that may be the problem.

Nope....
jaker.the.skater said:
this also happened to me, but yesterday. do you have the app tunein radio? i think that may be the problem.
Click to expand...
Click to collapse
Sent from my Nexus S using Tapatalk

well ok. nevermind then haha

hah2110 said:
I have a TON of these 37mb files on my SD card. They are all *.bins. What are they?
Click to expand...
Click to collapse
Same here. I had approximately 30 of them. My guess is from failed ota attempts due to rooting.
Sent from my Nexus S using XDA App

Just checked my phone today and I have the same thing, dated Jan. 10.
I'm running CM7 Alpha 2-2.

I have 4 of these I wonder what it is.

I had about 20 of them today. My phone seems to reboot randomly when using a Bluetooth headset. Anyone know if there is a radio update anywhere?
Sent from my Nexus S using XDA App

nobody knows? this practically filled up all my space and i had to delete them

Paul O'Brien thinks it's a crash dump of the ril.
He's tweaked his MCR custom ROM to not write it.
I haven't seen it yet on my phone...stock. Weird how some get it and some don't.

I have like 6 of these files on my stock gingerbread NS too.
Is it safe to delete them?

sagech said:
I have like 6 of these files on my stock gingerbread NS too.
Is it safe to delete them?
Click to expand...
Click to collapse
Yes. Delete away.

I've got this problem once in a while too (twice today, last time before was 5 days ago)
I think it's the same problem as here http://forum.xda-developers.com/showthread.php?t=906435
Since some have it and some don't, might it be related to an app? The only app i think i have launched today and not on previous days is "Antennas" (great app, but seems to stay in background when you think you closed it)
Stock Nexus S i9023 Rooted.

i've got 33 of them
not sure if i can delete them or not, but looks like you guys have without problems.
i.imgur.com/4j3YS.png
nexus s, CM7

had 4 of them on my stock 2.3.4
removed them now.and will monitor when there will be a new one.
so far only radio using apps i have are the stock apps.

I am also having this issue with nexus S with baseband i9023XXKD1, randomly it asks for pin code and a radio_dumpxxxx.bin file is created in the 'sd card'.
Using simyo (kpn) in Spain which uses Orange network.
Has anyone found what the problem is?

Radio dump bin files seem to get created when the phone loses its 3G connection - they're safe to delete and should be deleted to save space, since 37 MB each adds up. Also, not every baseband version works on every carrier. Some ROMs do include baseband, so you may end up with a new one without realizing. My Nexus S originally came with baseband B1 which worked find on my carrier. Now I've got D1 which also seems to work fine. Maybe your D1 isn't compatible with Orange - try B3 or B1 instead.

[Q] Radio issues with Nexus S, Hardware problem?

Hi,
My Nexus S is having a strange issue that when turn the phone on it picks up that I'm on Orange UK but from then on it says emergecy calls only or no service but shows signal in the status bar. If I try and call someone I get no mobile network messages but I can get a data connection and use the Internet although very slowy. Strangest thing is that if I put no sim card in the status bar still shows signal.
I've tried different radios and tried both Offical stock 2.3.4 and CM7 7.1.0 but same results, I've also tried turning 3g off but I'm now out of ideas so can anyone give me some tips please?
Thanks

Can you give specifics? Phone model, Baseband version (found in Settings >> About phone). Not all radios are the same and you can end up bricking the phone flashing wrong radio version.
Sent from my Nexus S using xda premium

[email protected] said:
Can you give specifics? Phone model, Baseband version (found in Settings >> About phone). Not all radios are the same and you can end up bricking the phone flashing wrong radio version.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Anyway, the standard radio the i9020a comes with is the UCKF1 or KB3 as I have heard. http://forum.xda-developers.com/showthread.php?t=1116884 is where you will find the radios. Just flash the correct one. How you will know whats the correct one is it will be stated after the phone model. for example I9020AUCKF1 the A after I9020 is for the carrier ATT and after the thats the radio it came with. just reflash the correct radio through CWM and you should be ok. If not PM and I will help you further

heinst said:
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Click to expand...
Click to collapse
Flashing I9023 radio on I9020 will brick the phone as it may not even boot into recovery, fastboot may not work too. Just a word of caution.
Sent from my Nexus S using xda premium

Sorry I should have said I have i9023 and have tried kf1 kd1 and jk8 radios all with the same results so far.
Sent from my GT-I9100 using XDA App

immolo said:
Sorry I should have said I have i9023 and have tried kf1 kd1 and jk8 radios all with the same results so far.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
What the next step would be is to try a new sim card. Go to your carrier and ask for a new one. If same results then its the phone and I'll assist you more.
Don't forget the thanks button.
Sent from my Nexus S using xda premium

Managed to borrow someones sim card at work today and it was the same result so it does seem to be a hardware problem now.
Sent from my GT-I9100 using XDA App

Yes. That would seem to me like the problem. I'm sure you restored your phone and completely wiped the SD? Also did you try pulling out the battery while the phone was on wait 30 seconds try turning the phone with out the battery then put the battery back in and turn it on? I'm sure you have done that you seem like a decently tech savvy fellow.
I've called Samsung before and I hate to say it but their repair policy is horrendous. You'll need another phone cause you'll be without yours for 2-4 weeks. They want to send "you your original phone back." Even their battery exchange is the same. You send your bad battery to them. They receive it process it then send you a new one. Motorola and apple have their repair department to be easy and quick which is what the consumer wants. More so apple cause you can go right to the local store and get a new one in 10 minutes. Motorola takes 2 days. Better than Samsung still.
Thats it for my rant! Just wanted to give you a heads up of what you will hear. Hope it all works out.
Sent from my Nexus S using xda premium

heinst said:
You cant brick your phone flashing the wrong radio....youll just have to have the correct radio as a back up. I flashed every radio for the nexus s and its not bricked.
Click to expand...
Click to collapse
yea, try flashing a CDMA radio on a GSM phone and see how that works out for you!
edit: actually, this sounds exactly like the ns4g i bought the other day. try making an emergency call and see what happens. really, that's how i fixed mine.

thedudejdog said:
yea, try flashing a CDMA radio on a GSM phone and see how that works out for you!
edit: actually, this sounds exactly like the ns4g i bought the other day. try making an emergency call and see what happens. really, that's how i fixed mine.
Click to expand...
Click to collapse
Well I dont think some one is that dumb to flash a CDMA for a GSM......if you are, you should stick to the iphone

Well it looks like I'm taking a trip to a service centre today let's hope it doesn't cost me too much to repair.
Sent from my GT-I9100 using XDA App

I've the same problem.
from morning my phone doesn't want find my sim card. Yesterday it was working fine.
I've try to reflash my radio but nothing.. now i'll try with odine, restoring... something older

d128b said:
I've the same problem.
from morning my phone doesn't want find my sim card. Yesterday it was working fine.
I've try to reflash my radio but nothing.. now i'll try with odine, restoring... something older
Click to expand...
Click to collapse
I tried that last flashing the xxka3 rom with no luck but let me know if you get any better luck then me.
Sent from my GT-I9100 using XDA App

Did you have any luck with Odin? I'm currently waiting for Samsung to diagnosis my problem so it would be nice to know at least one of us fixed this with software.
Sent from my GT-I9100 using XDA App

immolo said:
Hi,
My Nexus S is having a strange issue that when turn the phone on it picks up that I'm on Orange UK but from then on it says emergecy calls only or no service but shows signal in the status bar. If I try and call someone I get no mobile network messages but I can get a data connection and use the Internet although very slowy. Strangest thing is that if I put no sim card in the status bar still shows signal.
I've tried different radios and tried both Offical stock 2.3.4 and CM7 7.1.0 but same results, I've also tried turning 3g off but I'm now out of ideas so can anyone give me some tips please?
Thanks
Click to expand...
Click to collapse
I've had a similar issue in the past. Restoring my EFS made it work again.
But before that issue, I also had another problem where no amount of radio flashing and EFS fiddling would fix it. Sent it to Samsung and it came back with a form with a hand written note saying "BGA failure".
So I imagine this problem is more common than it might seem. *shrugs*

Restoring the EFS would have been one of my first moves but I was given the phone in this state with no backups made.
Just crossing my fingers that Samsung doesn't charge me a king's ransom to repair it.
Sent from my GT-I9100 using XDA App

Nexus s search bug

I get repetitive search presses automatically every so often...anyone know why this is happening? I searched on Google and it says that it is a bug on some nexus s Canadian version..but there are no fixes at the moment..anyone also having this problem?
Sent from my Nexus S using Tapatalk

It's in all versions. There is another new thread on here that suggests flashing a new radio fixes the issue. Haven't tried it yet but will.

donnieace said:
It's in all versions. There is another new thread on here that suggests flashing a new radio fixes the issue. Haven't tried it yet but will.
Click to expand...
Click to collapse
Thanks going to check out some radios and report back
Sent from my Nexus S using Tapatalk

it only affects the i9020a (AT&T version) and the false search activations are related to signal strength, the lower the signal, the more often the search will fire.
Officially, according to Samsung, 2.3.6 fixes the issue.
Playing with different radios can have an impact, the best will be the most recent (the one included in 2.3.6). The software fix mitigate the problem by suppressing search activations that it thinks are false positives.
For a true fix is sending it to Samsung for a screen replacement. I got my phone back and have had no false search activations since. I told them that I was on 2.3.6 and that I was still having search activations, they authorized a repair. replaced the screen and that's that.

On the official 4.0.4 OTA for the i9020A and the bug is STILL present.
I popped my SIM in and did some browsing on 3G in my house (terrible signal) and after about a minute, the search button began firing.

crachel said:
On the official 4.0.4 OTA for the i9020A and the bug is STILL present.
I popped my SIM in and did some browsing on 3G in my house (terrible signal) and after about a minute, the search button began firing.
Click to expand...
Click to collapse
Are you using the new radio for 4.04 too?
Sent from my Nexus S using Tapatalk

Imppy said:
Are you using the new radio for 4.04 too?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Yep.. this occurred on a completely stock, OTA 4.0.4 with the new radio.

I had this problem a few months ago. I resolved it by flashing the following radio:
http://forum.xda-developers.com/attachment.php?attachmentid=766907&stc=1&d=1320037083
This is latest radio for I9020A Radio UCKF1 (New Version) from this thread:
http://forum.xda-developers.com/showthread.php?t=1116884
If you plan to change you radio, make sure you backup your EFS folder.

Are you on nexus s 4g? The new radio kj1 for nexus 3g seems to have fixed the issue!
Sent from my Nexus S using Tapatalk

I haven't seen it with UCKE1 or UCKJ1

i don't have the search bug, but have the automatic back firing bug? anyone have this too?

[Q] Installing V21Y 2.3.4 Update and corrupting cell connection

I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA

As far as I know from lurking on the G2x forums, only stock Gingerbread and a rooted version of stock Gingerbread are available. I don't think any third-party ROMS have call audio working. The reason is that the official update changed the baseband.

Jlloyd97 said:
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
Click to expand...
Click to collapse
By updating the ROM with LG's update tool to 2.3.4, u also updated the baseband, and if u read around the forums here for the G2x, you can easily find that none of the custom ROMs work with the new baseband because of compatibility issues, you can only use ROMs that are based off of the official 2.3.4 update but there arent any yet.
Although im quite surprised tech support said it was a known issue, i wonder how many other people have called having this problem because they dont read around.
Anyways, hope this helps clear things up
Sent from my LG-P999 using XDA

thanks for the quick responses. I read the ROM install instructions multiple times, but did not read about the underlying baseband since I was running Weapon G2x gingerbread with no problems and thought the 3 wipes recommended prior to the install would take me back down to a clean phone.
Appears I have a tablet till the updates are released.
Also, Tmobile tier 2 support had a KB item on this issue, but it was caused by earlier versions of the software update failing prior to completion and causing the SIM card/network errors.

Jlloyd97 said:
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
Click to expand...
Click to collapse
All EB ROM's based on ICS are not compatible with the latest March bandbase.

You can downgrade to v21e July 2011 baseband if you want to use other ROMs.
Sent from my LG-P999 using xda premium

kesara said:
You can downgrade to v21e July 2011 baseband if you want to use other ROMs.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I don't want to seem lazy, but man, I've been looking all around for the "downgrade" baseband thread, where is it?
[email protected]

mustangtim49 said:
I don't want to seem lazy, but man, I've been looking all around for the "downgrade" baseband thread, where is it?
[email protected]
Click to expand...
Click to collapse
There isn't one. You use the same kdz method that ppl are using to update to v21y. just switch the 21y.kdz with 21e.kdz when using the method.

cricketAC said:
There isn't one. You use the same kdz method that ppl are using to update to v21y. just switch the 21y.kdz with 21e.kdz when using the method.
Click to expand...
Click to collapse
Yes
Sent from my LG-P999 using xda premium

Jlloyd97 said:
thanks for the quick responses. I read the ROM install instructions multiple times, but did not read about the underlying baseband since I was running Weapon G2x gingerbread with no problems and thought the 3 wipes recommended prior to the install would take me back down to a clean phone.
Appears I have a tablet till the updates are released.
Also, Tmobile tier 2 support had a KB item on this issue, but it was caused by earlier versions of the software update failing prior to completion and causing the SIM card/network errors.
Click to expand...
Click to collapse
Just look for the rooted version of the new update in the dev section by Kwes. Your phone will be fine then.
Sent from my LG-P999 using xda premium

Yup having the same issue with my friends phone. Someone mentioned downgrading the baseband, the only way I know how to do that is by using the tool that helps you unbrick the phone. please correct me if im wrong or have any idea what ive just said

What exactly is the benefit of the new march 2012 baseband (other than breaking custom ROM compatibility at this point)? Looking for apples-to-apples comparisons of a custom ROM running with old baseband and new baseband (other than broken cell voice calls).
A similar ordeal happened for Virgin Mobile's Optimus V line, where a new baseband came out, everyone jumped on it, but it caused occasional random reboots and no apparent benefits, and couldn't be downgraded. Eventually devs had to apply fresh LG released kernel source code & recompile kernel for new baseband to be stable.

Whyzor said:
What exactly is the benefit of the new march 2012 baseband (other than breaking custom ROM compatibility at this point)? Looking for apples-to-apples comparisons of a custom ROM running with old baseband and new baseband (other than broken cell voice calls).
A similar ordeal happened for Virgin Mobile's Optimus V line, where a new baseband came out, everyone jumped on it, but it caused occasional random reboots and no apparent benefits, and couldn't be downgraded. Eventually devs had to apply fresh LG released kernel source code & recompile kernel for new baseband to be stable.
Click to expand...
Click to collapse
As much as I miss ics, the new baseband pretty much fixes everything. Battery lasts forever, GPS lock right now and I've seen accuracy to 3ft. No random rebooting. Fast, smooth, dripping butter everywhere. Other than that, no real reason to flash it.
[email protected]

Phone audio messes up

EDIT: Sorry for this worthless thread. This issue was already discusses, resolved and summarized in this thread http://forum.xda-developers.com/showthread.php?t=1776843&highlight=owain+baseband
I didn't find it via searching though, so atleast maybe this thread will help searches get what they are looking for.
Does the CyanogenMod nightly work with the March 2012 baseband? I did the Lg update tool from my windows 7 PC. The phone rebooted into the operating system when the updater only red 4 percent and the updater never moved from there. I went into settings about phone and saw that I had the March baseband, so I unpluged the cable and restored my backup for my cyanogen mod ROM. I thought everything was fine but this morning I realize when I make phone calls all I hear is clicking noise. I remember reading on the forums about the new baseband only working with certain roms. I'm not sure if I need to somehow redo the Lg updater with the kdz method maby or need a new rom. Thanks for any info Dave
Sent from my LG-P999 using xda app-developers app

Might need to flash the new baseband fox in Owain's thread, first post.
http://forum.xda-developers.com/showthread.php?p=24163822

So I restored the LG update 21y rom and the phone works fine. Tried JB Hackfest, no luck. Tried the 21e OTA, same clicking. Back to 21y and it works great. I'm not rooted yet on the 21y though and really don't like the options. I'm about to read through the recommended thread above, but if anyone else knows how to get custom roms working with march baseband, or which roms will work, let me know please. Thanks Dave.

Thanks for the link. After reading through that and finding the owain zip for new baseband (patch or something), I searched owain baseband and found this thread that talks about it a bit too, http://forum.xda-developers.com/showthread.php?t=1714536. Restoring cm7 newest nightly now and flashing owain (new_baseband.zip). Be back in a minute to let you know if it worked.
From the first link you gave me it seems that it may be made for ICS roms.

So I'm still not sure if it worked. It seems to have, but all I got was voicemail for the two people I called. However, the second one, the screen went black (normal) as I was listenting to the VM, but when I took it away from my head to hang up the screen didn't come back. I tried shaking it, and moving it toward and away from my face (proxy sensor), no luck, I tried the top button, then the volume buttons and the capitive touch, then it rebooted itself. Will play with it for a few more days and report back.

The screen turning off problem you're talking about has nothing to do with baseband. It's a recurring problem on a bunch of G2x's with CM7. It's random, though; some people have the problem some don't
Sent from my LG-P999 using xda premium

rtotheichie said:
The screen turning off problem you're talking about has nothing to do with baseband. It's a recurring problem on a bunch of G2x's with CM7. It's random, though; some people have the problem some don't
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Well, I've had the phone since April 2011 and it hasn't been a problem with multiple rom, kernel and baseband configurations, build.prop tweaks and terminal emulator scripts. After it rebooted I called a friend and made sure it could go in and out of screen black out while I was talking. He heard me fine on regular and speaker, disconnected call without any issues. It seems the new_baseband.zip worked like a charm.
http://owain.hopto.org/T-Mobile%20LG%20G2x%20%28p999%29/Domination/new_baseband.zip