[REF] About emergency dialing failures on the Vibrant - Vibrant Android Development

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

Related

Change imei for captivate

Is there way to change IMEI on captivate?
Sent from my Inspire 4G using XDA App
amitson16 said:
Is there way to change IMEI on captivate?
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
It is Illegal and no
There is currently no way to do this as the algoriythm of the EFS nv_data.bin is unknown publicly. I may attempt to dissect it for resurrection purposes one of these days.
tjsooley said:
It is Illegal and no
Click to expand...
Click to collapse
i could be wrong but i think the poster wants to restore their original IMEI that was likely changed to a generic by a particular flash.
I think it would be hard to make the argument that changing an incorrect/corrupted IMEI back to the devices original/proper imei is illegal.
bames said:
i could be wrong but i think the poster wants to restore their original IMEI that was likely changed to a generic by a particular flash.
I think it would be hard to make the argument that changing an incorrect/corrupted IMEI back to the devices original/proper imei is illegal.
Click to expand...
Click to collapse
If thats the case, there are a couple threads on restoring it and the nvdata files.
boborone said:
If thats the case, there are a couple threads on restoring it and the nvdata files.
Click to expand...
Click to collapse
I know...one of them is mine =)
I haven't been able to fully test on a gingerbread rom because i haven't ended up witha corrupted imei on one. I have had the improper product code on every GB rom however and did test this and it will fix your product code on a GB rom. In the past i had corrupted IMEI's on froyo roms and using this fix to restore product code always restored my IMEI to its original as well. Its worth a shot if you have corrupted product code and/or imei on GB. It just test on mosaic and fixed my product code to the proper US ATT code.
http://forum.xda-developers.com/showthread.php?t=881162

[Q] Baseband?

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.

[Q & S] Swapping IMEIs between 2 Captivate?

Questions and Suggestions.....
I just got a second captivate, this one WITHOUT a cracked screen!! Now i realize i could just teardown and swap the main board, or the digitizer itself, but... that would be too simple!
Or i could just call my provider and change my imei with them... but who wants to talk to their provider??
Or.... i could do something fun and learn, by cloning my phone. from what i understand, all i would need to change is my IMEI, contained in my EFS.. and i have several backups of my good efs, and could easily backup the new one.
Is it simply as easy as copying the efs folder over with root privilages? or better to do an ADB dd (data dump) then tar it and odin? or ADB push/flash....
Is there anything im not considering? Is there any real risk if I have my EFS backed up? Any other ideas? suggestions? discussion?
any neat/interesting things to do with a copied phone set?
I have mine dd'ed and ready to flash with heimdall(i don't think ODIN will touch the EFS partition, but Heimdall will if you put it in there) So IDK, I would talk to conexxion2005 or AdamOutler about this!
thats what i was thinking...
Yahh, Or contact Benjamin, I forgot his last name, but he made Heimdall
Just dd the efs partition and flash it with heimdall. Thats all you have to do.
Code:
dd if=/dev/block/stl3 of=/sdcard/sdext/efs.rfs
do the same with your new phone to make a backup of it. Change the name of the efs file so you dont overwrite it. When you get done, swap the serial number stickers. I didnt tell you all this. Its illegal
it's personal development for learning purposes.
This is why I value second opinions.
now to get 2 (active) sims for the same imei.....
they both have ICS RC3.1 on them ive had the one a few hours.
one with silver speaker mod, one with out. if you dont know silver speaker mod, GO FIND IT NOW! READ THE FIRST 4 PAGES AT LEAST!
this is what ive been dealing with for the past 2 months......
but it works just fine....
I dropped it a good 10 feet, but it was fine, 20 minutes later took out of my pocket to see this...
http://dl.dropbox.com/u/19201431/Images/cracked%20to%20****%20but%20works.jpg
Lol my sister's looks exactly the same!
Just flashed it yesterday, it's weird to feel all those cracks under your thumb, and it still works.
I'm not sure DDing then flashing it to another device will have the correct effect but it's worth a shot. I can do remote IMEI repair for the Infuse and Vibrant 4G but their EFS structure is different from the Captivate. I know for a fact you can't just throw nv_data.bin files around and expect the IMEI to follow as it won't. However, DDing the zone then flashing could result in the desired effect.
LET US KNOW!
How would I know for sure? By checking the about> phone?... Running ice cream sandwich so I'm not sure if the dialer codes will work
I wonder if any of this would help me with my borked IMEI? I'm on the network default IMEI (the one ending in 0000) and I really want my original IMEI back...
Any ideas?
Do you think it would help flashing to stock including CSC files? Then immediately booting into stock recovery to force it to apply this CSC?
I know it does some funky things in that first recovery boot.. Applying settings and such...
adzidek said:
I wonder if any of this would help me with my borked IMEI? I'm on the network default IMEI (the one ending in 0000) and I really want my original IMEI back...
Any ideas?
Click to expand...
Click to collapse
This would only help if you had a backup of your original
IMEI
TRusselo said:
This would only help if you had a backup of your original
Click to expand...
Click to collapse
crap.
Any ideas on how/who might be able to help me?
There is a guide in the captivate development section on how to restore imei
TRusselo said:
There is a guide in the captivate development section on how to restore imei
Click to expand...
Click to collapse
thanks, but I tried all that already. I'm looking for someone who can decrypt/hex edit my original IMEI into my nv_data.bin...
Sent from my SGH-I897 using Tapatalk
connexion2005 said:
I'm not sure DDing then flashing it to another device will have the correct effect but it's worth a shot. I can do remote IMEI repair for the Infuse and Vibrant 4G but their EFS structure is different from the Captivate. I know for a fact you can't just throw nv_data.bin files around and expect the IMEI to follow as it won't. However, DDing the zone then flashing could result in the desired effect.
LET US KNOW!
Click to expand...
Click to collapse
It worked for me.

[Q]Back to stock. (How-To for a broken USB port)

Okay, so here's my issue. The usb port in my phone is dead, and I don't have 30 bucks to send it to mobiletechvideos to fix it. I also do not have a soldering iron, solder, and a desoldering braid to do it myself. Therefore I cannot use Odin via my computer anymore.
I downloaded Mobile Odin Pro v3.00, and becuase I am on Cyanogenmod 9 (REMICSv1.3) I am unable to load Mobile Odin. It states that it did not expect the file system and closes. To my understanding this is a failure of the APP/App maker (Chainfire) becuase the app does not know how to recover from a MTD to BML conversion. (And by failure i just mean it doesn't work, I am not implying he's bad or the app is bad). I'm really hoping that he can figure it out, 'cause right now I'm stuck with pure ICS roms (And I hate the look of ICS, hence using a TouchWiz themed ICS rom...)
So, with that said...
Is there (and this is high hoping) a CWM flashable .zip that will convert from MTD to BML that I could use?
Process would look something like this:
1. Power phone off
2. 3 button boot into Recovery
3. Wipe data/factory reset
4. Flash zip (MTDtoBML.zip)
5. Reboot into recovery
6. Flash Gingerbread rom
7. ???
8. Profit.
I ask becuase I don't want to be on ICS anymore. It has more issues than my grandma's back, and I just plain old enjoy gingerbread. (flash addict).
If so, could someone direct me to the zip file, or at least explain why this is or is not possible?
Kind of fiending for some old school Cognition or Perception (can't find active DL links), or maybe some old gingerbread roms...
Thanks,
Arisenhavok
Bump.... any ideas?
Sent from my SGH-I897 using xda premium
If you don't like ics, try miui, cm7, or my phrog or phobos roms. All use mtd, and you should be able to flash from your cm9 setup to one of them.
Fyi, it may take two flashes for the room to "take".
I've taken a look at both lewa and phrog and they seem yo have a significant issue or two listed in the op. Miui is EOL if I remember. I guess I'm more geared towards a BML RFS Touchwiz rom. But I suppose I will once again have to try looking for another mtd rom
Sent from my SGH-I897 using xda premium
I'm in a similar situation as OP except the radio also doesn't work apparently and have been wondering what I can do with it aside from just use it as a wifi-enabled media device. Since we're able to overwrite as least SOME files in the efs folder (nv_data.bin), I got to wondering if I could replace the entire system partition (or as much as possible) with a known good one (I have a second Captivate that works fine) to make certain there's nothing in software that is messing with the radio. So I'd copy everything from the good phone to SD card and then from SD card onto bad phone. I assume the only major hurdles other than inability to write some open files perhaps would be the SN & IMEI. If I can locate where those are kept, I could edit before copying. Being new to smartphones and this OS, there must be something I'm missing since this seems so simple.
And yes, I've flashed 2 other CM ROMs (I bought it with one on it) and flashed different radios but it never sees the service. It is also unlocked.
Replacing the efs partition will only at best get you to a generic imei. Your cell radio gets no signal because the efs partition and radio don't communicate or there's a hardware issue. Best bet is to send it to mobile tech videos and let them fix it for you. It's cheaper by far than a new phone.
Sent from my SGH-I897 using Tapatalk 2
Arisenhavok91 said:
Replacing the efs partition will only at best get you to a generic imei. Your cell radio gets no signal because the efs partition and radio don't communicate or there's a hardware issue. Best bet is to send it to mobile tech videos and let them fix it for you. It's cheaper by far than a new phone.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Unlocking it may have also broken it. Probably why they sold it in the first place. Best bet is to use it as a wifi media player with apps and games unless you plan to send it out
Sent from my SGH-I897 using Tapatalk 2
Arisenhavok91 said:
Replacing the efs partition will only at best get you to a generic imei. Your cell radio gets no signal because the efs partition and radio don't communicate or there's a hardware issue. Best bet is to send it to mobile tech videos and let them fix it for you. It's cheaper by far than a new phone.
Click to expand...
Click to collapse
I have 3 other phones I can use so it's not worth sending off. I figured I'd resell it for parts so I wasn't concerned with bricking it. I was hoping to verify whether the radio would work or not to get more money out of it. What controls whether the efs can communicate with the radio chip? Drivers obviously, which is what I gather flashing a new "radio" does. What file in the efs controls radio comm that could be corrupt?
I guess I should also specify by no service, it's not the circle and slash, but 4 gray bars. Phone status shows network as unknown (it will not find any when you do a search) and disconnected. SIM card works in 3 other phones and all 6 contacts seem fine in the suspect one. WiFi and GPS work OK. Maybe I should disassemble and verify antenna contact is good?
Arisenhavok91 said:
Unlocking it may have also broken it. Probably why they sold it in the first place.
Click to expand...
Click to collapse
He'd claimed it was because of the bad USB port. I've never read about unlocking rendering the radio useless. I'll have to look that up. It seems so simple to unlock these Galaxy S series.

[Q] Disable IMEI check on Jelly Bean ROMs

Hello guys
Is there a way to disable "Wrong IMEI Notification" on system startup?
I know how to restore IMEI, but my network works fine with generic IMEI, so I don't care about it much.
The only thread I was able to find is here:
http://forum.xda-developers.com/showthread.php?t=1862416
It's about 4 months old and no answer is given.
Currently I'm running Helly Bean 4.2.1 (Release - 05.01.13)
Thanks in advance
archildroid said:
Hello guys
Is there a way to disable "Wrong IMEI Notification" on system startup?
I know how to restore IMEI, but my network works fine with generic IMEI, so I don't care about it much.
The only thread I was able to find is here:
http://forum.xda-developers.com/showthread.php?t=1862416
It's about 4 months old and no answer is given.
Currently I'm running Helly Bean 4.2.1 (Release - 05.01.13)
Thanks in advance
Click to expand...
Click to collapse
It's cooked into the system apps, so unless someone has the knowledge to change it, the answer is no.
Fixing the problem is quite easy though and takes 15min at most after a good TiBu backup, if it gets too annoying, take that extra 15min
BWolf56 said:
It's cooked into the system apps, so unless someone has the knowledge to change it, the answer is no.
Fixing the problem is quite easy though and takes 15min at most after a good TiBu backup, if it gets too annoying, take that extra 15min
Click to expand...
Click to collapse
I flashed "i897uckk4 Odin One Click NO Bootloaders, Re-partition, Full Wipe" - IMEI is still some generic 0049...
What should I do now?
archildroid said:
I flashed "i897uckk4 Odin One Click NO Bootloaders, Re-partition, Full Wipe" - IMEI is still some generic 0049...
What should I do now?
Click to expand...
Click to collapse
Is it still giving you the error msg?
Is your phone a refurb?
BWolf56 said:
Is it still giving you the error msg?
Is your phone a refurb?
Click to expand...
Click to collapse
I was on Helly Bean 4.2.1 and it was giving me an error message because of wrong IMEI.
I didn't have efs backup, so I backed up everything and flashed stock kk4 assuming that it would restore my IMEI, but it's still 00499...
So how do I restore my IMEI?
No it's not refurbished.
archildroid said:
I was on Helly Bean 4.2.1 and it was giving me an error message because of wrong IMEI.
I didn't have efs backup, so I backed up everything and flashed stock kk4 assuming that it would restore my IMEI, but it's still 00499...
So how do I restore my IMEI?
No it's not refurbished.
Click to expand...
Click to collapse
That's actually how you restore your IMEI.. By flashing Odin KK4. Did you restore anything after flashing?
I went ahead and did a little google search (which can go a long way ). Here's what I got: http://forum.xda-developers.com/showpost.php?p=24175451&postcount=2
BWolf56 said:
That's actually how you restore your IMEI.. By flashing Odin KK4. Did you restore anything after flashing?
I went ahead and did a little google search (which can go a long way ). Here's what I got: http://forum.xda-developers.com/showpost.php?p=24175451&postcount=2
Click to expand...
Click to collapse
First I flashed Odin kk4 - wrong IMEI, reflashed few times, no luck. Than Eclair, Froyo - same result
Guide mentioned above didn't help, there were no files in /data/radio, and there is no folder /factory, or /data/factory. I copied nv_data.bin from /efs to /data/radio set chmod 700 but it didn't change anything.
Any more ideas?
Seems like I'm just unlucky (
Now flashed back to HellyBean 4.2.1, restoring backups...
archildroid said:
First I flashed Odin kk4 - wrong IMEI, reflashed few times, no luck. Than Eclair, Froyo - same result
Guide mentioned above didn't help, there were no files in /data/radio, and there is no folder /factory, or /data/factory. I copied nv_data.bin from /efs to /data/radio set chmod 700 but it didn't change anything.
Any more ideas?
Seems like I'm just unlucky (
Now flashed back to HellyBean 4.2.1, restoring backups...
Click to expand...
Click to collapse
Umm Your file explorer probably doesn't have root rights if you can't see those or you have to show hidden folders in settings.
BWolf56 said:
Umm Your file explorer probably doesn't have root rights if you can't see those or you have to show hidden folders in settings.
Click to expand...
Click to collapse
I'm using ES File Explorer (root settings were checked, permissions granted) and Yes, I rooted device (first flashed corn kernel).
Already flashed HellyBean 4.2.1 (10JAN13). Will take a chance after restoring backups.
Just tried to do like described in the link - folder /data/radio is empty for me, unable to find /factory folder
I wonder why flashing stock kk4 didn't restore IMEI ((
I backed up efs folder after installing Odinkk4, but I don't think it can help.
Good thing is that my carrier works just fine no matter IMEI
Anyway, thanks for trying to help me out. :good:
@archildroid, Josh at Mobiletechvideos.com I believe can restore your imei without having a back up. There will be a charge for it, but next to Adam Outler, you won't find a better set of tech fix it hands.
Sent From The Land Of Frag
I have tried lots of methods to restore my IMEI, but no luck.
One thing I encountered: This wrong IMEI popup has "Galaxy S Settings" icon in the corner, so I froze it with Titanium and the popup disappeared.
Of course you lose all the abilities, that Galaxy S settings have - TV Out, Color tuning etc.
I hope someone with sufficient knowledge will modify Galaxy S Settings, to disable this popup.
P.S. Before changing anything in system apps, MAKE NAND BACKUP, I'm not responsible for anything you do to your phone!
archildroid said:
I have tried lots of methods to restore my IMEI, but no luck.
One thing I encountered: This wrong IMEI popup has "Galaxy S Settings" icon in the corner, so I froze it with Titanium and the popup disappeared.
Of course you lose all the abilities, that Galaxy S settings have - TV Out, Color tuning etc.
I hope someone with sufficient knowledge will modify Galaxy S Settings, to disable this popup.
P.S. Before changing anything in system apps, MAKE NAND BACKUP, I'm not responsible for anything you do to your phone!
Click to expand...
Click to collapse
Usually, going back to stock KK4 with Odin fixes your IMEI problem. Once there, you make a backup of your efs folder and you're set for your android's life. It's a one time backup (as long as you don't delete it..) and can be restored whenever.

Categories

Resources