No voice but radio otherwise works!? - Nexus S General

I got the OTA ICS update back in December. Since then my SNS has not allowed any voice traffic. Data, both 2G and 3G (including HSDPA) works fine as does WiFi. When I try to make a call it just beeps and says "Call ended". When I try and call the handset I get a message saying "calls are not currently being connected to this number". I've therefore been using my Atrix (with the same SIM) until Google sorted this out but decided to have another go at fixing it.
I therefore unlocked it, installed CW recovery and tried a CW nightly build, with the same result. I then decided to go back to stock 2.3.6 but get the same problem!!!
I've tried a different SIM. I do a factory wipe and cache wipe before each install.
This is driving me up the wall. Does anyone know what I'm doing wrong?
I'm on t-mobile UK, using a SIM unlocked I9020T. I've had a search but can't find anyone with the same problem - apologies if I've missed a relevant post.

Have you checked you vpn settings are correct?
Sent from my ARCHOS 80G9 using XDA Premium HD app

DarkhShadow said:
Have you checked you vpn settings are correct?
Click to expand...
Click to collapse
Thanks for the response.
Do you mean APN?
If so, yes, I have checked and they are correct. I don't think incorrect APN would affect voice though. Wouldn't it be data and MMS that were affected?

Which radio do you currently have? Have you tested any other radio for your device?

Oogway13 said:
Which radio do you currently have? Have you tested any other radio for your device?
Click to expand...
Click to collapse
I've tried a few radios....... however I think I've sussed it:
The IMEI has somehow changed! The IMEI reported in 'About phone' is different to the number printed on the back of the phone. I'm guessing it happened when I flashed the first OTA ICS. How would that change the IMEI?
I might add that it's a legit handset, bought new by me from Carphonewarehouse.
Any ideas how I get it back to the correct IMEI?

Cowie said:
I've tried a few radios....... however I think I've sussed it:
The IMEI has somehow changed! The IMEI reported in 'About phone' is different to the number printed on the back of the phone. I'm guessing it happened when I flashed the first OTA ICS. How would that change the IMEI?
I might add that it's a legit handset, bought new by me from Carphonewarehouse.
Any ideas how I get it back to the correct IMEI?
Click to expand...
Click to collapse
You EFS has corrupted, this can happen by flashing ANYTHING
There's a few ways to possibly restore it with no backup but I don't have links, just try searching forums
Sent from my ARCHOS 80G9 using XDA Premium HD app

http://forum.xda-developers.com/showthread.php?t=1523756
That thread is when my efs corrupted, maybe try something there, also once it works make a .img backup with the commands posted
Sent from my ice cream powered Nexus S

Thanks for the info DarkhShadow. I've read through the posts but think I'll wait until tomorrow to give it a go. I'm knackered and likely to make a mess of things.
I've got an old .nv_data.bak together with an old nv_data.bak.md5 in my /efs but that's about it.

Cowie said:
Thanks for the info DarkhShadow. I've read through the posts but think I'll wait until tomorrow to give it a go. I'm knackered and likely to make a mess of things.
I've got an old .nv_data.bak together with an old nv_data.bak.md5 in my /efs but that's about it.
Click to expand...
Click to collapse
Copy them to a safe place and then delete /efs and reboot, it will remake some files you can "possibly" use
Sent from my ice cream powered Nexus S

Really struggling with this.
The NS is rooted using CW recovery and I've run su-version#-signed.zip. All seems to go well - no errors. When I come to try to back up /efs (using adb pull) it is apparent that I don't have su. Obviously when I then try to back up I get a permission error (thought it was worth trying anyway).
I've gone through the rooting and su process three times now in case I'm missing something. I'm using the stock 2.3.6 and I'm slowly losing the will to live.
Any help would be much appreciated.
EDIT - I've managed to use Root Explorer to get su, then mount the drive as r/w before renaming /efs and rebooting. The IMEI is now correct but the damn thing still doesn't allow voice.

Related

Install 3.2.2 after LTE Upgrade

I just received my US 3G model Xoom back after having the LTE upgrade done and like an idiot, flashed the ROM below instead of just rooting the already installed 3.2.2 ROM
[ROM/UPDATE] Android Honeycomb 3.2.2 - Stock & Rooted
I'm experiencing the same Wifi issue a lot of other users are reporting so I've reverted back to the Stock image. My problem is I didn't root and nandroid before installing the ROM above so I can't get to 3.2.2. I can only get as far as 3.2 and then Android reports it's up to date.
Any ideas of how to get to 3.2.2 other than the ROM above? I'll buy a USB Host cable if I can find the proper .zip files to upgrade from 3.2.
mmayhew said:
I just received my US 3G model Xoom back after having the LTE upgrade done and like an idiot, flashed the ROM below instead of just rooting the already installed 3.2.2 ROM
[ROM/UPDATE] Android Honeycomb 3.2.2 - Stock & Rooted
I'm experiencing the same Wifi issue a lot of other users are reporting so I've reverted back to the Stock image. My problem is I didn't root and nandroid before installing the ROM above so I can't get to 3.2.2. I can only get as far as 3.2 and then Android reports it's up to date.
Any ideas of how to get to 3.2.2 other than the ROM above? I'll buy a USB Host cable if I can find the proper .zip files to upgrade from 3.2.
Click to expand...
Click to collapse
http://dl.dropbox.com/u/22648028/HLK42Bsystemboot4g.7z
That will get you to HLK42B which is 3.2.2. These are the boot and system images which you can flash thru fastboot, something you should be familiar with if you flashed back to stock images...works the same way. However, this the earlier version from the Pilot group which I was part of. Apparently the ones being sent out now are HLK75C or something like that. I am trying to find anyone with one of the recently updated Xooms that can dump the System/Boot images for me. Until then, these are better than nothing and will get you back up on 4G
AceXMachine said:
http://dl.dropbox.com/u/22648028/HLK42Bsystemboot4g.7z
That will get you to HLK42B which is 3.2.2. These are the boot and system images which you can flash thru fastboot, something you should be familiar with if you flashed back to stock images...works the same way. However, this the earlier version from the Pilot group which I was part of. Apparently the ones being sent out now are HLK75C or something like that. I am trying to find anyone with one of the recently updated Xooms that can dump the System/Boot images for me. Until then, these are better than nothing and will get you back up on 4G
Click to expand...
Click to collapse
Perfect, thanks a ton man. Is there a better place than the 'Xoom Android Development' XDA forums to look for the most recently dumped images?
mmayhew said:
Perfect, thanks a ton man. Is there a better place than the 'Xoom Android Development' XDA forums to look for the most recently dumped images?
Click to expand...
Click to collapse
Not that I know of at the moment. Trying to get someone to dump the new images for me. Also, forgot to mention, password for that 7zip is "solarnz"
AceXMachine said:
Not that I know of at the moment. Trying to get someone to dump the new images for me. Also, forgot to mention, password for that 7zip is "solarnz"
Click to expand...
Click to collapse
Thanks again. Up and running on the 3.2.2 build with no problems.
I took a nandroid after I unlocked the bootloader (which also does at least a factory reset). Can you use that?
Sent from my Xoom using Tapatalk
Unfortunately this did not work on my verizon xoom. I am still getting no internet connection even though it says 3.2.2 Initially it said the sim card was unknown, so I took it out and put it back in and did a reboot. It no longer gives that error, but I still don't get 3g or 4g.
Switch your network to cdma only and power down and back up. That will let it activate.
Sent from my Xoom using xda premium
I don't have the option for cdma only. Mine says home only and automatic. I don't have the LTE/CDMA option at all. I am on 3.2.2
Sent from my PG86100 using xda premium
short/y said:
I took a nandroid after I unlocked the bootloader (which also does at least a factory reset). Can you use that?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes, that would be great.
Sent from my Xoom using XDA App
bathanr said:
I don't have the option for cdma only. Mine says home only and automatic. I don't have the LTE/CDMA option at all. I am on 3.2.2
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I have this problem too. I can't get 3g/4g to work on any pre-3.2.2 image including this 'pilot' 3.2.2 image uploaded here. I can get 3g working with the ROM mentioned in my original post but wifi doesn't work.
Sent from my Xoom using XDA App
If you can create a link or pm me the backup as well that would be great
mmayhew said:
Yes, that would be great.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I've uploaded a Rogue Recovery backup to MEGAUPLOAD -- http://www.multiupload.com/BTA7S2DMPZ. Unzip everything and put the files in clockworkmod/backup/<some-name> either on your microSD card or your internal memory and then boot into recovery (again, I took it with Rogue Recovery V1.2) and do a restore.
I've verified that this is the stock 3.2.2 by inspecting system/build.prop in the system backup -- it says the version is HLK75C.
Sorry, guys, but today's an exceptionally busy day for me so I don't have the time to monitor this board and answer questions as to how to flash Rogue or whether it'll work with the standard CWM or any of that. Hopefully someone else can step up and help with those questions.
How do I dump the system? I will post it if I new how.
Sent from my Xoom using xda premium
short/y said:
I've uploaded a Rogue Recovery backup to MEGAUPLOAD -- http://www.multiupload.com/BTA7S2DMPZ. Unzip everything and put the files in clockworkmod/backup/<some-name> either on your microSD card or your internal memory and then boot into recovery (again, I took it with Rogue Recovery V1.2) and do a restore.
I've verified that this is the stock 3.2.2 by inspecting system/build.prop in the system backup -- it says the version is HLK75C.
Sorry, guys, but today's an exceptionally busy day for me so I don't have the time to monitor this board and answer questions as to how to flash Rogue or whether it'll work with the standard CWM or any of that. Hopefully someone else can step up and help with those questions.
Click to expand...
Click to collapse
Thanks again for the files. I updated to rogue recovery. I created a CWM folder on my SD card and did the restore. It restored fine. I boot up and it shows 3.2.2 and it also shows build version HLK75C. It still does not show 4G nor does it have the option under mobile network settings to choose LTE/CDMA. I have been on the phone with verizon and they have no clue. Motorola said tech level 3 will call me within 24-48 hours.
You need stock files to get that back. It should show lte/CD a in network settings. You could drive to a 4g area and it should activate.
Sent from my Xoom using xda premium
hammer4203 said:
How do I dump the system? I will post it if I new how.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
You need to flash the modded recovery, then in adb shell, run
mount /data
mkdir /data/media/Stock
dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/data/media/Stock/system.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/media/Stock/boot.img
sync
Then reboot and pull the files, should be in a "Stock" folder on the internal storage.
*Thanks to solarnz for these instructions
---------- Post added at 04:05 PM ---------- Previous post was at 04:00 PM ----------
bathanr said:
Thanks again for the files. I updated to rogue recovery. I created a CWM folder on my SD card and did the restore. It restored fine. I boot up and it shows 3.2.2 and it also shows build version HLK75C. It still does not show 4G nor does it have the option under mobile network settings to choose LTE/CDMA. I have been on the phone with verizon and they have no clue. Motorola said tech level 3 will call me within 24-48 hours.
Click to expand...
Click to collapse
You guys are wiping the cache and davlik after flashing right?
Is there a way to dump the img files without modding anything? I just sent my xoom out and will be receiving it completely void of any user information so I can do it at that time, but I really don't want to modify the recovery.
nubsors said:
Is there a way to dump the img files without modding anything? I just sent my xoom out and will be receiving it completely void of any user information so I can do it at that time, but I really don't want to modify the recovery.
Click to expand...
Click to collapse
I doubt it. Instructions I received specifically stated that the modded recovery would be needed. You can try unlocking it and running the commands to see but I doubt it will work. You could also try backing up the stock recovery using:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/recovery of=/data/media/Stock/recovery.img
But I believe the modded recovery is what allows the device to be mounted. Wonder if this could be done via fastboot. I have to go to work or I would test it on my own Xoom. Will try later unless someone has already posted images by then.
Ok, I have pulled HLK75C images which should be flashable through fastboot thanks to short/y's Rogue CWM nandroid backup. Usual disclaimers apply here, don't try this unless you know what your doing, not my fault if something messes up. That being said, download images here: http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z zip password is "AceXMachine" without the quotes. After unpacking files go to the command prompt
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
It goes without saying that you need your xoom unlocked for this, need adb setup/working and may need to wipe data. I would do a nandroid backup of your current config before doing this. I was able to restore the "data" backup from a previous backup after restoring the "system" and "boot" from short/y's backup. Only problem I had was my market shortcut on the home screen had to be replaced since my "data" backup had the link to the older market. I rooted this before pulling these images so you should already have root when you flash this. I tested and have working WiFi and 4G with this setup. Feel free to ask questions or PM me if needed. Thanks again to short/y for his nandroid backup...even if he did make me load the Rogue recovery just so I could use it ;P

Baseband

I'm about at my wits end trying to figure out this problem of mine.
Here's a quick overview of my situation, so I don't have to go through it again:
http://forum.xda-developers.com/showthread.php?t=1301091
Anyways, I decided to take another shot late at night to see if I could get this working. I'm running on 3.2.2 right now, build HLK75D, with no 3G/4G connectivity. I looked at a screen shot of a stock updated 4G Xoom's settings and I noticed that my baseband is the only thing different.
Is there some way to change the baseband from what it is now (CDMA_N_03.1A.54P) to "CDMA_N_03.1A.52P ltedc_u_05.15.00"?
I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.
Jewremy said:
I'm having the same problem. Downgraded, took updates, overwrote the radio image. Oops. No LTE. Gone. You can re-activate it on 3G, but that's about it.
Click to expand...
Click to collapse
Yeah, well, I don't have either 3G or 4G. My Xoom says activation successful over Wi-Fi, and I have full signal with the Verizon towers, but it just doesn't connect.
I still haven't heard anything back from Motorola regarding any way to get the baseband back to the LTE version.
Guys use Motorola stock imgs, but remove your sim card after you flash it. See if it connects to 3g then. If not look for the hlk75c stock root on here flash that with your sim in.
Sent from my Xoom using xda premium
HLK75C is the Verizon one. Try to flash this.
http://forum.xda-developers.com/showthread.php?t=1294824
Sent from my Xoom using xda premium
hammer4203 said:
HLK75C is the Verizon one. Try to flash this.
http://forum.xda-developers.com/showthread.php?t=1294824
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.
Did you flash hri66? What kernels have you tried? Oh and are you in a 4g area, cuz that can cause an issue if your not.
Sent from my Xoom using xda premium
http://forum.xda-developers.com/showthread.php?p=18224270
AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.
Sent from my Xoom using xda premium
hammer4203 said:
http://forum.xda-developers.com/showthread.php?p=18224270
AceXMachine's post has a 7z file that should put you back. He did the same thing as you and he is back up.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I've tried AceXMachine's solution. Still no deal.
No matter what image I've used, I still have no option for LTE in my mobile network settings. My baseband still has never changed back to LTE.
I live in the dead center of a strong 4G area. My 4G was working fine prior to making the stupid mistake of flashing over what Motorola sent back.
Jewremy said:
We've tried that. No dice. I think it may be the bootloader that turns the radio on/off. HTJ85B or whatever it was overwrites the bootloader. If you power down, then power up BP (hold vol up + vol down on boot), it says LTE Radio OFF Cold booting linux. We need to turn that LTE radio on.
Click to expand...
Click to collapse
And that is exactly what mine says when I power up BP.
I just received a total generic e-mail response from Motorola telling me to make sure to check for updates, etc.
I replied to them and told them that my baseband is the wrong version and that my LTE radio is turned off. Lets see if they can provide anything to help out.
Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.
Sent from my ADR6400L using xda premium
hammer4203 said:
Anyone know how I can get you the baseband from my xoom? I am rooted on hlk75d. Just give me some directions and I will pull it for ya.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I think it involves pulling your build.prop?
http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
dethrok said:
I think it involves pulling your build.prop?
http://android.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Click to expand...
Click to collapse
No. This is lower-level software. It's part of the bootloader, governs the radio. The build.prop files are the same between 3.2.2 back from moto and 3.2.2 upgraded from stock.
I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.
Sent from my Xoom using xda premium
I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039
Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.
hammer4203 said:
I am not find anything on how I can extract the file it files you need! Makes no sense. I know there has got to be a way to just pull the radio and make an update zip.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.
It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. EDIT: Nevermind. Don't bother.
zarkuu said:
I actually think it is a kernel or kernel module issue. I started another post in this direction. http://forum.xda-developers.com/showthread.php?t=1305039
Basically I can see the "wrigley" LTE modem in /system/build.prop and dmesg but I don't see the device in /sys/bus/usb/devices so the system can't use it. I thought the kernel lived in boot so I am surprised that flashing a new boot.img doesn't fix it, but for me at least it doesn't.
Click to expand...
Click to collapse
See above in this same post.
Well, this is all hurting my head. Motorola e-mailed me back and said they were bumping my case up to their repair escalation team and I'll be getting a call in 1-2 days.
Hopefully they'll still help me out when it was my own stupid fault that I screwed up my connection. Maybe they'll be able to give me a solution to turn the radio back on.
Jewremy said:
It is not. I'm about 90% sure that this is a bootloader issue. If you boot up in BP tools mode, it says LTE radio is off.
It can't be the radio (aka baseband) 'cuz none of the updates change the baseband. Always the same one even on HRI39 and HRI66. I'm thinking the baseband is contained in the ebb partition, also known as the bootloader. Reflashing the bootloader is extremely risky. You really don't want to do that. It's at /dev/block/mmcblk1p1. Controls the whole boot sequence. The HTJ85B update overwrites/updates the bootloader, which is what could cause our issue.
Click to expand...
Click to collapse
OK, this makes sense to me since I have flashed back to HRI66 and did OTA updates to HTL85B and nothing else would presumably have changed it back. My mistake was probably allowing the device to boot under HTJ85B. If I had just done it through recovery and then flashed back to HLK75C it wouldn't have touched the bootloader. I bet some people didn't do that and so they work when flashing various restores. I understand it is risky to flash the bootloader (because if it goes wrong you won't be able to even go to fastboot) but what other option is there other than RMA back to Moto? Do we think Moto will be releasing stock images for this new bootloader anytime soon? That's really more of a rhetorical question I think.
I guess if someone wants to try making a backup I might try flashing it.
From http://forum.xda-developers.com/showthread.php?t=1294824
Pulling your own images
1. Flash a custom recovery
2. Boot straight into recovery.
Code:
adb shell
mount /data
mkdir -p /data/media/images
dd if=/dev/block/platform/sdhci-tegra.3/by-name/ebb of=/data/media/images/bootloader322.img
sync
Then reboot back into android and pull it off your device.
See if you can use this.
http://forum.xda-developers.com/showthread.php?t=1270848
Sent from my Xoom using xda premium
I'm in the same boat: http://forum.xda-developers.com/showthread.php?t=1299485
Hopefully we'll find an answer soon.
hammer4203 said:
See if you can use this.
http://forum.xda-developers.com/showthread.php?t=1270848
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
No dice. I've checked all the OTA updates I know about:
19dea2ba1ae5.signed-trygon-HTJ85B-from-HMJ37.19dea2ba.zip
7a15c95f18ba.signed-trygon-HLK75-from-HLK42B.7a15c95f.zip
7ac6aeb09117.signed-trygon-HLK75D-from-HLK75C.7ac6aeb0.zip
a5de99b3e437.signed-trygon-HMJ37-from-HRI66.a5de99b3.zip
In HMJ37 from HRI66 (3.0.1 to 3.1) I see a bootloader.bin along with this in the updater-script
Code:
assert(package_extract_file("bootloader.bin", "/tmp/bootloader.bin"),
moto.set_mbm_update("/tmp/bootloader.bin"),
delete("/tmp/bootloader.bin"));
There is nothing else that does an "set_mbm_update" in any of the other updates.
On the upside the md5sum of this bootloader.bin matches my own dd dump of the ebb partition.
Code:
c3a74df4a356c0e4158fd592cc8be693 bootloader.img
c3a74df4a356c0e4158fd592cc8be693 /tmp/updates/bootloader.bin
I'd be interested to see if someone can take a dump of their ebb partition as I documented earlier and see if the md5sum matches. if it does, then we will know the bootloader is not the problem. If not, then this is something new to try. Basically we need the dump and then an update.zip to flash it. If someone can provide the dd dump then I can make the update.zip. That should be safe enough to flash I think.

Rooted Incredible flashed to Straight Talk Stuck on 2.2

Hey guys. I've read that this is a common issue. I am rooted and stuck on 3.26 and I'm wondering if there's anything I can do to get it to update. It starts to download 4.08 but it doesn't reboot after I hit install. I read about loading stock roms but I'm not sure if I can do that being flashed to Straight talk. Anything will be appreciated! Thanks.
Christiie said:
Hey guys. I've read that this is a common issue. I am rooted and stuck on 3.26 and I'm wondering if there's anything I can do to get it to update. It starts to download 4.08 but it doesn't reboot after I hit install. I read about loading stock roms but I'm not sure if I can do that being flashed to Straight talk. Anything will be appreciated! Thanks.
Click to expand...
Click to collapse
Well you should be able to flash any rom you want. Service and data settings are stored deeper than roms reach. The only way those settings will get wiped out is if you do a factory reset from hboot, or from the storage and sd menu within the os. If something at the os level is required, you can just backup before hand, and then restore if somethimg dosent work. You should just be able to flash the stock 4.08.605.15 rom in the dev section right over 2.2 without wiping anything if you want to stay stock.
The ota will not install because you are rooted. For it to imstall you must be unrooted and complete stock.
That being said i do not have straight talk, so i dont know all the details. You could use QPST http://dinc.does-it.net/QPST/ to backup all those settings to a file on your pc, and then restore them if something ever goes wrong.
Thanks so much! If I have any other questions when I do this can I PM you?
Christiie said:
Thanks so much! If I have any other questions when I do this can I PM you?
Click to expand...
Click to collapse
Sure no problem. I would definitley setup qpst and backup your service and data settings, and do a nandroid before doing anything.
How hard was it to get data working when you flashed it to straight talk, i heard that was the trickiest part? I am thinking of doing this my self. Verizons new plan just sucks for a 1 phone plan.
I didn't do it myself. I get all my phones from a guy that flashes them to ST and the data works perfectly . If you can figure it out or find someone who can its definitely worth it.
Sent from my ADR6300 using xda app-developers app
Christiie said:
I didn't do it myself. I get all my phones from a guy that flashes them to ST and the data works perfectly . If you can figure it out or find someone who can its definitely worth it.
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Just hook it up to qpst or cdma and you can get all the settings you need easy as 1 2 3

Backup IMEI Nexus 4

So on my Nexus s, i had a nightmare and i lost my imei number, had to get the phone replaced, once i got it back i made sure backed up my imei foldr "efs" everywhere, just wondering is it the same folder for the nexus 4?
italia0101 said:
So on my Nexus s, i had a nightmare and i lost my imei number, had to get the phone replaced, once i got it back i made sure backed up my imei foldr "efs" everywhere, just wondering is it the same folder for the nexus 4?
Click to expand...
Click to collapse
yeah
this is no samsung device, so no, your imei won't get lost!
Sent from my Nexus 4 through Tapatalk
P0MM3S said:
this is no samsung device, so no, your imei won't get lost!
Sent from my Nexus 4 through Tapatalk
Click to expand...
Click to collapse
I had the same on my SGS2 - so are we saying we don't need to worry about this on non-Samsung devices?
No you don't, it's just Samsung who think putting something important in an unprotected area of the filesystem is a good idea.
ah really brilliant, 100% sure?
italia0101 said:
ah really brilliant, 100% sure?
Click to expand...
Click to collapse
it's a 100% samsung related problem, no other phone has it
Sent from my Nexus 4 through Tapatalk
Although it's nice to hear that loss of your imei is not possible on non-Samsung phones, it doesn't explain how the OP lost his. Obviously, became corrupted.
If backing-up /efs (imei) can be done harmlessly, would it not be a good idea to do so? Has anyone attempted to backup their efs on the Nexus 4?
Sent from my Nexus 4 using xda premium
There is no /efs
Like had already been said, that's a Samsung thing. Anyway, the OP hadn't said he lost his IMEI, just he wanted to make sure he couldn't.
Rusty! said:
No you don't, it's just Samsung who think putting something important in an unprotected area of the filesystem is a good idea.
Click to expand...
Click to collapse
I'm still laughing with this comment.
Dr Zoidberg said:
Although it's nice to hear that loss of your imei is not possible on non-Samsung phones, it doesn't explain how the OP lost his. Obviously, became corrupted.
Click to expand...
Click to collapse
Please read carefully. The OP mentions he lost the IMEI on his Nexus S (Samsung device) and not Nexus 4.
Lost IMEI on Samsungs is very easy to fix. I've not heard of a Samsung having a permanently lost IMEI, it was always a case of reflashing the stock firmware and taking a new efs backup.
Also, losing your IMEI is usually caused by poorly designed ROMs, good ones usually back it up for you beforehand, but even better ones don't lose it. You can't really blame Samsung, they aren't the ones flashing a custom ROM are they? I bet nobody ever lost their IMEI from a Samsung OTA.
skezza said:
Lost IMEI on Samsungs is very easy to fix. I've not heard of a Samsung having a permanently lost IMEI, it was always a case of reflashing the stock firmware and taking a new efs backup.
Also, losing your IMEI is usually caused by poorly designed ROMs, good ones usually back it up for you beforehand, but even better ones don't lose it. You can't really blame Samsung, they aren't the ones flashing a custom ROM are they? I bet nobody ever lost their IMEI from a Samsung OTA.
Click to expand...
Click to collapse
Its not easy to fix then you don't have an efs backup ... Believe me . it was straight up gone and needed hardware replacement
Sent from my Nexus 4 using Tapatalk 2
CMW recovery started backing up the /efs folder just to be safe on Samsungs, so it shouldn't be a problem these days anyway.
Yes, there were a few (poorly designed) roms on the nexus s that over wrote /efs and those who were "efs-****ed" couldn't do anything about it. For the galaxy nexus however, there is a way to recover lost /efs data, as found by devs on xda. Still a design flaw on samsung's part though, imo. But you need not worry about this on your nexus 4.
italia0101 said:
Its not easy to fix then you don't have an efs backup ... Believe me . it was straight up gone and needed hardware replacement
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Actually I just lost my note 2 efs file 2 hours ago and I dint have any efs backup. I just downloaded stock firmware and flash via Odin. Factory reset and voila its alive again. Actually I thought I need to get to service center tomorrow but thank god Odin worked lol
mr_trisx said:
Actually I just lost my note 2 efs file 2 hours ago and I dint have any efs backup. I just downloaded stock firmware and flash via Odin. Factory reset and voila its alive again. Actually I thought I need to get to service center tomorrow but thank god Odin worked lol
Click to expand...
Click to collapse
no offence, but if it was that easy dont ya think i would have done that ? i tried literally everything.. it was a design law on the Nexus s. once it was gone, it was gone. no reflashing did anything.. they had to replace the hardware to get it working again
but anyway. glad it cant happen on my N4
im having a big problem with my new nexus 4.
rooted. running factory stock.
when i tried to install a custom rom , the radio of the phone stopped working i get no service anymore wi-fi is stuck on ''turning on''
tried restoring my back up rom even reinstalling the factory rom but nothing worked.i read different forums related to that problem but got no answer. seems my EFS is corrupted. when i go in settings about phone status . i dont see my emei ,my phone number, my carrier, nothing.
please help!!
joggz16 said:
im having a big problem with my new nexus 4.
rooted. running factory stock.
when i tried to install a custom rom , the radio of the phone stopped working i get no service anymore wi-fi is stuck on ''turning on''
tried restoring my back up rom even reinstalling the factory rom but nothing worked.i read different forums related to that problem but got no answer. seems my EFS is corrupted. when i go in settings about phone status . i dont see my emei ,my phone number, my carrier, nothing.
please help!!
Click to expand...
Click to collapse
sounds to me like you need to have it replaced. despite what others have said there is an efs partition on this device and it can be corrupted. :highfive:
joggz16 said:
im having a big problem with my new nexus 4.
rooted. running factory stock.
when i tried to install a custom rom , the radio of the phone stopped working i get no service anymore wi-fi is stuck on ''turning on''
tried restoring my back up rom even reinstalling the factory rom but nothing worked.i read different forums related to that problem but got no answer. seems my EFS is corrupted. when i go in settings about phone status . i dont see my emei ,my phone number, my carrier, nothing.
please help!!
Click to expand...
Click to collapse
You just have to flash the stock android on your nexus 4 and it will work perfectly.
Sent from my Nexus 4 using xda premium

I think it's BRICKED this time!

Ok, I was on a custom ROM for LS980 and all of a sudden it rebooted and I had no control of anything. There was no service either.
So first thing I did was a reboot. no good. Then I went booted into TWRP and restored my last backup, thought this would surely fix it but nothing. Still booted but had no functionality, plus now it started to go into a boot loop. Tried recovering different versions and no luck.
Then, I decided to use the Flash Tool recovery method. It worked in the sense that there was no longer a boot loop, but I still had no service and could not use a lot of the functions like updating PRL/PROFILE and few of the apps would not launch like the quick remote, it would say "SIM not ready"
I'm pretty much out of ideas at this point as I only have the flash tool option and since I lost recovery.
Is this considered BRICKED or does anyone have an idea? thanks
centro714 said:
Ok, I was on a custom ROM for LS980 and all of a sudden it rebooted and I had no control of anything. There was no service either.
So first thing I did was a reboot. no good. Then I went booted into TWRP and restored my last backup, thought this would surely fix it but nothing. Still booted but had no functionality, plus now it started to go into a boot loop. Tried recovering different versions and no luck.
Then, I decided to use the Flash Tool recovery method. It worked in the sense that there was no longer a boot loop, but I still had no service and could not use a lot of the functions like updating PRL/PROFILE and few of the apps would not launch like the quick remote, it would say "SIM not ready"
I'm pretty much out of ideas at this point as I only have the flash tool option and since I lost recovery.
Is this considered BRICKED or does anyone have an idea? thanks
Click to expand...
Click to collapse
If you are still able to enter in the ROM it's not Bricked....
Put the phone in Fastboot and flash a recovery via Fastboot commands.
Then you can wipe everything (except internal) and flash a new ROM.
I've never fastbooted before. Is there a quick tutorial link for this?
Sent from my SPH-D710 using XDA Free mobile app
There is no normal fastboot mode as on other phones. Best thing i think try to go back to stock via kdz/tot method and reinstall root and recovery
Sent from my LG-D802 using XDA Premium 4 mobile app
basti2909 said:
There is no normal fastboot mode as on other phones. Best thing i think try to go back to stock via kdz/tot method and reinstall root and recovery
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So I tried the flash tool again using different TOT files. ZV8 and ZVA files caused boot loops. The only file that almost worked was the ZVC file. By almost I mean, there's no boot loop, and i'm able to use the stock ROM however certain things don't work, like when launching the quick remote app, it says "SIM not ready", or stock video cannot play "Unsupported file type" error, and most importantly I'm not able to get any service.
The good part is, my wifi is working. So next I tried to root, however I get this a "unable to open /system/xbin/su: no such file or directory" (i'm attaching the photo for reference).
Thanks for any other tips of directions.
remove sim card and reinsert try that. Not working.
also check your imei. If its not there you may need to recover it from a twrp backup, (recover the efs that is) at least from the time you had no issues. Not working?
Also I read nothing about wiping. (wipe everything except internal sd) before performing a clean instal. Check for same issues, not there victory.
be carefull with full backups, they might contain the issue you are experiencing.
bachera said:
remove sim card and reinsert try that. Not working.
also check your imei. If its not there you may need to recover it from a twrp backup, (recover the efs that is) at least from the time you had no issues. Not working?
Also I read nothing about wiping. (wipe everything except internal sd) before performing a clean instal. Check for same issues, not there victory.
be carefull with full backups, they might contain the issue you are experiencing.
Click to expand...
Click to collapse
this is a ls980 so I can't remove the Back cover unless there's a way I don't know.
Also, I lost twrp recovery when I used the flash tool and tot method. Now, i'm trying to root and get recovery back but can't even root.
Sent from my SPH-D710 using XDA Free mobile app
I am not very familiar with your model. But on the d802 there is a small slot on the side of the phone with a small hole. With the phone in box was a small metal device which you could poke in hole and the slot would open. Maybe other user could confirm.
Did you backup your twrp backup of the phone? Then now is also the time to put it back if the tot method deleted it.
Anyway did you check your imei, (dial *#06#, it should show your imei). usually when service is lost there is something wrong with imei, or simcard.
imei can be recovered by the efs backup in a twrp backup. Simcard via putting out back in, reboot, etc.
bachera said:
I am not very familiar with your model. But on the d802 there is a small slot on the side of the phone with a small hole. With the phone in box was a small metal device which you could poke in hole and the slot would open. Maybe other user could confirm.
Did you backup your twrp backup of the phone? Then now is also the time to put it back if the tot method deleted it.
Anyway did you check your imei, (dial *#06#, it should show your imei). usually when service is lost there is something wrong with imei, or simcard.
imei can be recovered by the efs backup in a twrp backup. Simcard via putting out back in, reboot, etc.
Click to expand...
Click to collapse
Thanks for all your help! sounds like its definitely a imei and Sim related issue.
I don't have any backups but I can get to the factory recovery which has an adb side load option. Do you think I can side load a stock ROM this way? If so, what type of file do I use?
Sent from my SPH-D710 using XDA Free mobile app
centro714 said:
Thanks for all your help! sounds like its definitely a imei and Sim related issue.
I don't have any backups but I can get to the factory recovery which has an adb side load option. Do you think I can side load a stock ROM this way? If so, what type of file do I use?
Sent from my SPH-D710 using XDA Free mobile app
Click to expand...
Click to collapse
you can go to download mode and flash a stock rom, but that wont help get you imei back sir if thats whats gone cant help you with that without a backup. Even though there are guides somewhere
bachera said:
you can go to download mode and flash a stock rom, but that wont help get you imei back sir if thats whats gone cant help you with that without a backup. Even though there are guides somewhere
Click to expand...
Click to collapse
Yup, that's what I figured after numerous flash tool and tot files.
I found this link that sounds suspiciously like what i'm facing:
http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
Itching to get home and try it.
Sent from my SPH-D710 using XDA Free mobile app
Can't get the software to recognize that the phone is connected via USB even though I reinstalled drivers and restarted.
I'm pretty much stuck.
Since I have no imei does this also mean it's a bad esn?
Sent from my SPH-D710 using XDA Free mobile app
With no imei.. It's confirmed gone.
Lim Wee Huat said:
With no imei.. It's confirmed gone.
Click to expand...
Click to collapse
Damn. now I have a small lg tablet:banghead:
Sent from my SPH-D710 using XDA Free mobile app
Found this, it may help. I haven't tried it, so it's up to you....
http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
matt_tee said:
Found this, it may help. I haven't tried it, so it's up to you....
http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
Click to expand...
Click to collapse
Yea tried this but stuck on step 8 like one of the commenters.
Anyone else have last ideas before this phone goes on the auction block?
Sent from my SPH-D710 using XDA Free mobile app
centro714 said:
this is a ls980 so I can't remove the Back cover unless there's a way I don't know.
Also, I lost twrp recovery when I used the flash tool and tot method. Now, i'm trying to root and get recovery back but can't even root.
Sent from my SPH-D710 using XDA Free mobile app
Click to expand...
Click to collapse
uy can remove sim, on left side there is a tray just use any sim removal & bingo.
I wonder how can people use a phone & dont even know that they can remove sim... lol
RohanM said:
uy can remove sim, on left side there is a tray just use any sim removal & bingo.
I wonder how can people use a phone & dont even know that they can remove sim... lol
Click to expand...
Click to collapse
So I removed Sim and reinserted it and still no imei. At least I know there's a Sim card access.
Sent from my SPH-D710 using XDA Free mobile app
Well if you got no imei and no backup, you can't fix it home.
Sent from my GT-I9300 using XDA Premium 4 mobile app

Categories

Resources