Hi, I'm really not sure which baseband to use for my O2X
I'm running CM7.1, and I have been reading a few things that changing the bb might make things a bit better (reception/call quality/etc).
Does anyone have any suggestions and is it a risky process? Would I need to reflash my rom & will I lose all my settings unless I do a NAND backup/restore?
Thanks,
brezzo
brezzo said:
Hi, I'm really not sure which baseband to use for my O2X
I'm running CM7.1, and I have been reading a few things that changing the bb might make things a bit better (reception/call quality/etc).
Does anyone have any suggestions and is it a risky process? Would I need to reflash my rom & will I lose all my settings unless I do a NAND backup/restore?
Thanks,
brezzo
Click to expand...
Click to collapse
Flashing BB will erase the user space so you'll have to restore a Nandroid Backup after. It takes 10 min maximum, not very hard.
If you're using CM7 a Nandroid Backup is correct, as it uses standard ext4 format for partitions. And then you'll have exactly the same phone but with a new baseband, last thing is to install matching RIL with GetRIL market app, only a matter of seconds.
I can't give any advice on which BB to flash as is it very variable among people... The gold rule is that if your sound during call is good, your network accesses are good, no need to change.
CM7 works with any BB it's just a matter of opinion. Many users seem to have latest 0823 BB, but some use an old Froyo BB as well...
Striatum_bdr said:
Flashing BB will erase the user space so you'll have to restore a Nandroid Backup after. It takes 10 min maximum, not very hard.
If you're using CM7 a Nandroid Backup is correct, as it uses standard ext4 format for partitions. And then you'll have exactly the same phone but with a new baseband, last thing is to install matching RIL with GetRIL market app, only a matter of seconds.
I can't give any advice on which BB to flash as is it very variable among people... The gold rule is that if your sound during call is good, your network accesses are good, no need to change.
CM7 works with any BB it's just a matter of opinion. Many users seem to have latest 0823 BB, but some use an old Froyo BB as well...
Click to expand...
Click to collapse
Thanks mate, I currently have 405 and I have no idea if it's froyo or not, but I think it is. It seems to work fine so I don't think I'll go through the hassle of changing.
I currently have 405 and I have no idea if it's froyo or not
Click to expand...
Click to collapse
yes 405 is froyo. maybe you should check this link
Code:
http://forum.xda-developers.com/showthread.php?t=1082195
at the moment I have CM7.1 running with bbaseband 725, I haven't hand any issues with it yet. Give it a try
Sent from my Optimus 2X using XDA App
Striatum_bdr said:
last thing is to install matching RIL with GetRIL market app, only a matter of seconds.
Click to expand...
Click to collapse
i have got this app on your recommendation and it indeed says my RIL doesnt match by baseband. If i click the button within the app for download and install new RIL will this wipe all my data? or will it just replace the RIL??
many thanks
Fulwood Sedge said:
i have got this app on your recommendation and it indeed says my RIL doesnt match by baseband. If i click the button within the app for download and install new RIL will this wipe all my data? or will it just replace the RIL??
many thanks
Click to expand...
Click to collapse
Will only change a driver (RIL), nothing more is done.
Related
I tried 5 different roms and i feel cyanogenmod 6 rc2 version is stable. but i am worrying if i try one more custom rom then will it break my phone?. Please tell me how many time we can install roms in the phone.
Will it create a bad sector on my phone.
dlcsboop said:
I tried 5 different roms and i feel cyanogenmod 6 rc2 version is stable. but i am worrying if i try one more custom rom then will it break my phone?. Please tell me how many time we can install roms in the phone.
Will it create a bad sector on my phone.
Click to expand...
Click to collapse
Well as long as you're wiping between different ROMs you should be fine. And even if you are there won't be any permanent damage. The only way you can brick your phone is by installing a bad/old radio.
Even if there's a limited number of "flashing" the phone you won't reach it before you get a new phone.
Likely in the millions of times.
Don't worry about it.
Its the same question like "how many times can you write data on a sd card", you already got a new one when you reach that number
Flash memory has a certain number of read write times until it fails. But that number is so high that it will be years from now.
how can i know if i have a bad sector??
Amritttt said:
how can i know if i have a bad sector??
Click to expand...
Click to collapse
You have to wipe/install a new rom and copy logs to sd card from either other or advanced menu, havent used amon_ra recovery in forever
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
androidcues said:
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
Click to expand...
Click to collapse
Lol, I may be able to tell you soon, flashing nightlies every day
How many stars are there in the Galaxy?
Flippy125 said:
Lol, I may be able to tell you soon, flashing nightlies every day
Click to expand...
Click to collapse
EVERY DAY ISN'T ENOUGH!!!!!!!1111oneeleven
Flippy125 said:
Lol, I may be able to tell you soon, flashing nightlies every day
Click to expand...
Click to collapse
Hey, I am a total newbie but I would like to flash the nightlies as well. I usually backup all my apps and settings using Titanium Backup, do a Nandroid backup, wipe and then flash the new ROM. However, backing up all apps and settings using Titanium Backup and restoring them after flashing the nightly is quite time consuming. Even worse is arranging the application short cuts / widgets on the desktops after a fresh install.
Nandroid will allow me to go back to backed up version after I have played around with the nightly for a few hours. But then I lose all the features of the nightly once I am back to my old ROM. As I am carrying only a single phone, it becomes mandatory for me to restored the Contacts, Messages, Applications and Settings after flashing a new ROM.
It may sound stupid but is there a better and faster way of doing things without having to restore all applications/settings from the backup so that I also could try out the nightlies? How do you manage this?
For the most part, you can flash nightlies without a wipe, if you're going from CM to CM. If you see weird behavior after flashing, then go back and wipe, and if that doesn't work do a complete wipe and flash.
If you're on another ROM, then I would definately wipe...
Sent from my Nexus One using XDA App
Exactly 6.3 times. That is all. But nobody mentions it.
danger-rat said:
For the most part, you can flash nightlies without a wipe, if you're going from CM to CM. If you see weird behavior after flashing, then go back and wipe, and if that doesn't work do a complete wipe and flash.
If you're on another ROM, then I would definately wipe...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks, danger-rat! I'll give it a shot
meechto said:
Thanks, danger-rat! I'll give it a shot
Click to expand...
Click to collapse
I strongly suggest wiping cache and dalvik-cache prior to flashing a new nightly, it prevents **** and doesn't affect your settings/files
Haven't been on CM for awhile, but if you use Launcher Pro or ADW they have Homescreen backups. Have had good luck with MyBackUpPro too.
Ken
3 times. 1...2...crunch...3. Haven't you all seen the tootsie pop commercial?
androidcues said:
So, how do we get to the answer of how many times one can flash their phone?
That is such an interesting question. The answer must be had!
Click to expand...
Click to collapse
How many licks does it take to get to the Tootsie Roll center of a Tootsie Pop? LMAO, that's what I WANNA KNOW!
I'm having trouble with a custom ROM I installed recently, in that my "radio" will not work. In other words, I have no service and no 3G (or 2G for that matter) and i would really like to keep Cyanogen Mod 7.0.2 on my phone. PS - Wifi works no problem.
I'm with Telus in southern Ontario, Motorola Milestone, Androidiani Open Recovery, rooted and CM7 is installed as of right now.
I'm hoping there's someone who can help.
R1PP3R said:
I'm having trouble with a custom ROM I installed recently, in that my "radio" will not work. In other words, I have no service and no 3G (or 2G for that matter) and i would really like to keep Cyanogen Mod 7.0.2 on my phone. PS - Wifi works no problem.
I'm with Telus in southern Ontario, Motorola Milestone, Androidiani Open Recovery, rooted and CM7 is installed as of right now.
I'm hoping there's someone who can help.
Click to expand...
Click to collapse
Did you apply the baseband after you flashed the ROM?
If you go into AOR, select Change Baseband and choose Telus.zip. Reboot.
No one ever explains that you have to do that, i guess I'm still a bit of a n00b and not afraid to admit it lol. Thanks man, it's working!!
Haha, it only shows it sometimes, it's one of those things that people take for granted that everyone knows I guess!
skadude66 said:
Did you apply the baseband after you flashed the ROM?
If you go into AOR, select Change Baseband and choose Telus.zip. Reboot.
Click to expand...
Click to collapse
Hello, i am a newb as well. and have the same problem. by re flashing are you talking about using RSD lite and the Telus file to flash the phone?
Kulch said:
Hello, i am a newb as well. and have the same problem. by re flashing are you talking about using RSD lite and the Telus file to flash the phone?
Click to expand...
Click to collapse
Not at all. By reflashing I meant the ROM he was using. What I mean by changing the baseband is that you go into AOR and select the Change Baseband option.
Sent from my Milestone using XDA Premium App
i might of figured it out. we'll re post if i messed up
alright i applied the baseband. telus.zip but i keep getting a force close error.
? any ideas
Kulch said:
alright i applied the baseband. telus.zip but i keep getting a force close error.
? any ideas
Click to expand...
Click to collapse
A force close in AOR? I've never heard of that before..
Kulch said:
alright i applied the baseband. telus.zip but i keep getting a force close error.
? any ideas
Click to expand...
Click to collapse
If you are getting force closes after flashing: Make sure that your cleared both the cache and Dalvik Cache partitions in AOR (scroll to the bottom).
This usually helps a LOT. If this don't help with the force closes, you may need to clear data also...but you will lose all data so a backup using something like Titanium may be a good idea.
R1PP3R said:
No one ever explains that you have to do that, i guess I'm still a bit of a n00b and not afraid to admit it lol. Thanks man, it's working!!
Click to expand...
Click to collapse
I don't think this is true. I am not trying to be picky, but effort has been made to ensure that installation is as easy as possible. These forums are very newb friendly and most people don't care about repeated questions. But it is not true to state that "no one explains you have to do that".
It is pointed out in 2 different spots:
From the instructions in the CM7 thread (emphasis/bold added by me):
Installation:
- use OpenRecovery Apply Update menu to install the zip copied to /sdcard/OpenRecovery/updates
- data wipe/factory reset is highly recommended when you are upgrading from another rom/firmware (or having any issues )
- the included RIL files are for the European frequencies, if you are in Canada, US, Lat Am or Thailand, you will need to replace them to get 3g working
- if you are in France, you should replace ro.product.brand=MOTO_RTEU with ro.product.brand=MOTO_RTFR in /system/build.prop (the ap_gain_france.bin will be used then)
OpenRecovery Mod (with CyanogenMod for Milestone specific customizations):
http://code.google.com/p/androidiani-openrecovery/
Non European radio files can be installed from menu in Androidiani OR.
From the FAQ (linked in the CM7 first post):
Help! My phone can't connect to my carrier's data or voice network
Please choose the appropriate baseband for your phone from either Androidiani recovery or another recovery that support baseband RIL file installation.
In the Androidiani recovery menu, navigate to CHANGE BASEBAND (main page) and choose the appropriate country/provider.
Did anybody have issues like this with CM9 and how to solve them?
Nobody had issues like this?
not me at least
hassanalip21 said:
not me at least
Click to expand...
Click to collapse
well I do and need all the help that I can get
come on guys, nobody?
ok then, is there a tutorial to put it back to original state? original kernel and everything?
The best way is to recover older Nandroid backup.
przemcio510 said:
The best way is to recover older Nandroid backup.
Click to expand...
Click to collapse
and if I don't have it?
I bought telephone with CM9 on it and have this issue with modem that I can't solve
I'm going crazy over here with this phone
simeparanoja said:
I'm going crazy over here with this phone
Click to expand...
Click to collapse
My suggestion would be to wipe data, possible flash back to stock, or just wipe data and play around with some different radio's. I've had similar issues, not as bad as yours, but different radio seemed to fix it.
I'm in in canada, east, on telus. I'm using the fascinate with galaxy i9000 rom/kernel/radio. I find the best radio's to be the KG2, KG3, and KC3.
Have you used any apps to disable permissions? like autostarts, one time I had an issue where my phone wouldn't dial any calls in my own area code. I found out it was autostarts, and a permission I had enabled.
-Maniac
Think that permissions are enabled, as far as I can see.
Problem is that I'm noob on this area, I got this phone with darky on it.
When you say to wipe data, on which data do you mean and how to do that?
how to flash? Where can I find stock rom and some tutorial?
thank you
simeparanoja said:
Think that permissions are enabled, as far as I can see.
Problem is that I'm noob on this area, I got this phone with darky on it.
When you say to wipe data, on which data do you mean and how to do that?
how to flash? Where can I find stock rom and some tutorial?
thank you
Click to expand...
Click to collapse
I would start with testing some different modems. This is pretty simple, and might just fix your problem.
When I say wipe, I mean a factory reset. I'm not familier with that rom, but in the settings their should be something to do a factory reset.
A sure way would be to boot clockworkmod, select the option to do a wipe/factory reset.
Note, both of the above methods will wipe your apps/data. Perhaps your SDcard as well. So if anything is important, I would do a backup.
Perhaps you should do a nandroid backup anyways, just incase it don't fix your problem and you won't waste any more time have to reinstall everything and set it all up again.
Here are a few reasons on why emergency dialing has failed in the past:
#1. Invalid IMEI / Corrupted EFS
If you have a corrupted EFS then it's possible for 911 calls to fail, even on stock, and normal calls may still work. If your IMEI is 004999010640000 then your EFS may be corrupted.
#2. Bad libaudio
We had a bad libaudio in CM7.1 that caused 911 to fail.
#3. Mismatched GPS libraries
Don't swap GPS libraries with other devices. The RIL executes a ipc_recv_gps command during a 911 call which, if the GPS libraries are all messed up, can crash the RIL because it couldn't communicate correctly. If GPS matters that much to you, use a BT GPS receiver. Don't swap RIL libraries either while you're at it.
This list may not be exhaustive.
Thanks FE
I am one of the few with a corrupt IMEI. I tried to restore from the sdcard backup using root browser, but it seems the correct IMEI was lost at some point during my CM9 flashing expeditions - corrupted SD card requiring format.
Obviously I have the correct IMEI from my phone's sticker. Do you know a way to manually enter this number back into the correct files?
EDIT:
Turns out I have multiple efs directories in /sdcard/backup and the oldest one had the correct nv files. Instructions from post 167 of http://forum.xda-developers.com/showthread.php?t=1839655 worked. Now the phone registers the correct efs in system > status. But every time I reboot I get a text message saying something like "Terminal cannot be configured automatically, contact customer service for support."
Any thoughts on how to deal with this annoyance?
EDIT 2: error on my carrier's end. They didn't like me changing the IMEI. I am winning.
So, just to make sure I understand, if we use your Froyo RIL test build, does that mean that 911 should work all the time? I understand that I should do some testing, I'm just looking for your opinion on the matter.
Thanks.
salazar.r1 said:
So, just to make sure I understand, if we use your Froyo RIL test build, does that mean that 911 should work all the time? I understand that I should do some testing, I'm just looking for your opinion on the matter.
Thanks.
Click to expand...
Click to collapse
The CM10 one? The CM10 test build has libaudio and libsecril-client changes. The CM10 nightlies already have the GPS changes, and when I had someone test the CM10 test build, they said GPS location did not transmit, but looking at the logs it still got past the part that previously crashed.
FE whats the best way to recover from a corrupted imei without an efs backup?
I've already tried (http://forum.xda-developers.com/showpost.php?p=30644270&postcount=116) with no luck
ferhanmm said:
FE whats the best way to recover from a corrupted imei without an efs backup?
I've already tried (http://forum.xda-developers.com/showpost.php?p=30644270&postcount=116) with no luck
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=1264021
Although don't know if just the IMEI is the problem with 911, or if the other parts of the efs would still be corrupted and cause problems.
So lemme ask you something.. are these the only things that us Vibrant owners should worry about cause 911 issues? Or are these just some of the causes?
Sent from my SGH-T959 running 4.1.1
FaultException said:
The CM10 one? The CM10 test build has libaudio and libsecril-client changes. The CM10 nightlies already have the GPS changes, and when I had someone test the CM10 test build, they said GPS location did not transmit, but looking at the logs it still got past the part that previously crashed.
Click to expand...
Click to collapse
Do the CM9 nights already have the fix also or only CM10?
Sent from my SGH-T959 using Tapatalk 2
FaultException said:
Try this:
http://forum.xda-developers.com/showthread.php?t=1264021
Although don't know if just the IMEI is the problem with 911, or if the other parts of the efs would still be corrupted and cause problems.
Click to expand...
Click to collapse
Did the entire guide no dice.
Read this http://forum.xda-developers.com/showpost.php?p=29501858&postcount=164), flashed to stock, got back imei. lold
Flashing to stock JFD restores corrupted IMEI. Verified by checking sticker under battery.
younix258 said:
So lemme ask you something.. are these the only things that us Vibrant owners should worry about cause 911 issues? Or are these just some of the causes?
Sent from my SGH-T959 running 4.1.1
Click to expand...
Click to collapse
No promises.
mexicandroid said:
Do the CM9 nights already have the fix also or only CM10?
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Yes, but it's recommended to stay on CM10 and our CM9 branch won't be getting any more work. (Including the libsecril-client commit)
Anyway you can make a version of CM10 with a bigger app partition size and smaller system size?
Sent from my SGH-T959 using Tapatalk 2
Hi,
I have a problem wit the CM11 nighly builds. Since the Kernel was updated (begin of Feb.) I must insert my PIN number of the simcard more than one times a day.
Often I must insert my pin 2-4 times at one day.
I have also clean the caches, but the problem is still there.
Also the usage of the idoak Kernel does not fix this Problem.
Have someone the same trouble. How can I fix this problem?
I'm quite sure you didn't flash the ROM in a proper clean way.
I think it's ROM related and not kernel related. Try a full wipe with cache cleaning as well as formatting system under mounts and storage in cwm.
Then flash your ROM + Gapps and maybe your kernel.
Backup your current ROM just to be sure, you can restore /data after clean install with advanced restore to get your apps etc back.
Sent from my LG-P880 using XDA Premium 4 mobile app
I had the same issue. I resolved it with newer nightly and clean install.
Cheers
Ur loosing connection to network, probably due to ril problems. Check my sig for possible solution
I have done yesterday the following.
1. Backup current ROM
1. Clean /system
2. Clean Dalvik
3. Clean cache
4. Wipe All
5. Install CM11 Nighly
6. Reboot (phone comes up)
7. restore /data from backup
But now before 30 Minutes I must insert my Pin number again.
It seems that the problem came when the phone wakeup from deep sleep.
It might also be caused by a faulty or not properly inserted Sim card.
Sent from my LG-P880 using xda app-developers app
Yes maybe, but I have this problem not before update.
I have also fixed the sim card with a tape in my phone.
Problem still there
Hi,
the problem is still there.
I have now make a complete clean installation with cleaning of /system too.
But sometimes I must insert the PIN again.
Currently I have installed the nightly build 11-20140308-NIGHTLY-p880 with the default kernel.
I have enabled debugging and logged the reason. The log file is attached in this post.
Can anyone please look at the logfile.
For me it looks like that the phone disables or lost the radio.
I hope you can now help me.
Works with another ROM
I have installed last saturday the ROM NAMELESS and the SIM problem is not there, all works fine.
So there must be a problem in the orginal CyanogenMod 11 version.
I think the developers from the CM11 should search the problem.
By the way, the NAMELESS ROM has much better battery usage.
heliflieger9 said:
I have installed last saturday the ROM NAMELESS and the SIM problem is not there, all works fine.
So there must be a problem in the orginal CyanogenMod 11 version.
I think the developers from the CM11 should search the problem.
Click to expand...
Click to collapse
Same on my phone (ril bug/sim-pin-bug).. with Original LG Firmware no problem at all.. with CM11 several times a day I have to enter the pin.
heliflieger9 said:
I have installed last saturday the ROM NAMELESS and the SIM problem is not there, all works fine.
So there must be a problem in the orginal CyanogenMod 11 version.
I think the developers from the CM11 should search the problem.
By the way, the NAMELESS ROM has much better battery usage.
Click to expand...
Click to collapse
Although your problem seems to be solved, I wanted to be sure that the hint from Flying_Bear was understood.
What is important in @Flying_Bear signature is not the process of flashing, but his method of patching the RIL, which is described here http://direct.xda-developers.com/showpost.php?p=46751745 .
I tried it, and believe it makes a huge difference.
Did you try that?
Ottonet said:
Although your problem seems to be solved, I wanted to be sure that the hint from Flying_Bear was understood.
What is important in @Flying_Bear signature is not the process of flashing, but his method of patching the RIL, which is described here http://direct.xda-developers.com/showpost.php?p=46751745 .
I tried it, and believe it makes a huge difference.
Did you try that?
Click to expand...
Click to collapse
No, I did not try that, because I won't change this every time I install a new nightly. I think this is so, is it?
I see, that the RIL in other ROMs like Nameless ROM work, why did the CM developers not change it?
heliflieger9 said:
No, I did not try that, because I won't change this every time I install a new nightly. I think this is so, is it?
I see, that the RIL in other ROMs like Nameless ROM work, why did the CM developers not change it?
Click to expand...
Click to collapse
Yes, that is understandable, When I had that problem I considered the opportunity of tweaking the RIL every time I updated a Rom, then since many, many nightlies and with iodak 9.95 kernel I did not see baseband wakeock appearing again, so I almost forgotten the matter.
Though I believe that it is not necessary to replicate the process described by Flying_Bear from the beginning to the end. All you have to do is getting a modified "telephony-common.jar" then, after each upgrade, copy that file into /system/framework, give it the correct permissions/owners and reboot.
Mind that I did not try this method, and don't know if it makes sense at all, maybe @Flying_Bear can give us a confirmation. If it worked, it would be no much hassle.
Inviato dal mio GT-P3110 utilizzando Tapatalk
Unfortunately, telephony-common.jar is usually incompatible from nightly to nightly (usually). With practice, the process takes only a few mins. Try upgrading weekly instead of nightly
I have now tested the RIL changes from @Flying_Bear for two days.
It works and I must not insert my SIM-Card pin again.
I see in official CM thread that some people have currently also RIL problems. Did the CM developer know about this problems?
heliflieger9 said:
I have now tested the RIL changes from @Flying_Bear for two days.
It works and I must not insert my SIM-Card pin again.
I see in official CM thread that some people have currently also RIL problems. Did the CM developer know about this problems?
Click to expand...
Click to collapse
not sure if they know there are specific problems, but the solution was presented to them back for cm10, and arcee rejected it due to many mentions of eternityproject inside the code itself (which normal users don't care about, as they care about stable RIL, and don't care who contributed)
Check this
http://forum.xda-developers.com/optimus-4x-hd/orig-development/ril-baseband-fix-t3134167