Database Info

[Q] no service

Okay, I had upgraded to 10.1 Aries and it was working fine and I tried changing some things with UOT kitchen and I got a "no service" problem. I have tried reinstalling from stock a couple of times but it doesn't make any difference. tried flashing a different modem and that didn't work either. The phone boots up and wi-fi works, but not the phone or data. Tried flashing an efs restore file and that didn't work either. Bill's paid for tmobile. I tried restoring from a nandroid backup and there is no change. IMEI is all zeros IMEI SV is 02 mobile network state is disconnected.
what to do?

Flash back to stock then reflash cm10.1

I use this one click to restore my IMEI/service issues
http://forum.xda-developers.com/showthread.php?t=1500427
Then flash an ICS ROM
Flash CM10.1

Cooptx said:
I use this one click to restore my IMEI/service issues
http://forum.xda-developers.com/showthread.php?t=1500427
Then flash an ICS ROM
Flash CM10.1
Click to expand...
Click to collapse
er... I flashed back to stock about three times and it didn't make any difference. I used Odin to flash KC1, then KJ6, then a kernel with CWM.

Have you upgraded from a GB ROM to an Team Acid ICS ROM? Their upgrade script automatically backs up you efs files.
Try extracting the tar file from the backup and taking the contents and stick it in the efs folder. That worked for me once :/ there is also a script Team Acid posted per my request somewhere in the Stupid Questions Thread.
Check this out ! :
http://forum.xda-developers.com/showthread.php?t=2035032

Flash back to stock then flash aries release 3. Next time u get the no connection turn off wifi and just wait longer. Sometimes it just takes a bit after boot. Reflashing the modem (make sure you are flashing fb padded modem). That should do it. I started reflashing a modem after aries every time then realized i just had to wait an extra 20 seconds after booting up. Release 3 pretty good with this
Sent from my SGH-T959V using Tapatalk 2

I have the same issue. Had been running Aries beanstalk since it came out, switched to dao's pacman and after a couple days it seems the radio chip quit or something. Tried different modems, restoring nandroid, flashed back to stock, went and got a new Sim card. Nada. So... Yeah I had to pay 5 bucks for a new phone lol
Sent from my SGH-T959V using xda app-developers app

After doing more testing.. Kb5 and kc1 dont flash... You need to flash kd1 and up and make sure they are padded.
Sent from my SGH-T959V using Tapatalk 2
And if u do install aries then flash kc1 by mistake it will say baseband unknown imei unknown.. But you dont have to do one click.. Just flash padded kd1 ki1 lb6 anything besides kb5 and kc1. I think it has to do with byte size of modem file.

Cooptx said:
Hit me up with your old one
Check this out ! :
DD-Ripper's Secret
Click to expand...
Click to collapse
Haha I gotta mail it back to them
Sent from my SGH-T959V using xda app-developers app

guess i'm f**ked then...well I giot a galaxy 3 somewhere around the apt, not a galaxy s 3 but the little fat one with the tiny screen:crying: I can still take pictures with the phone

I don't remember exactly where but there should be a folder on your SD card with all the efs backups created when you upgraded to mtd.
The filename should be efs-backup.tar and it could also have numbers in the backup name

Cooptx said:
In a folder called backup
That is where I found mine
Check this out ! :
DD-Ripper's Secret
Click to expand...
Click to collapse
mine too. i'm always checking that folder because I always forget whats in it. I see it and am like what the hell is that and then, oh yeah....duh! was never really sure if that was good stuff in there. thankfully never had to use it......yet!

CSP III said:
mine too. i'm always checking that folder because I always forget whats in it. I see it and am like what the hell is that and then, oh yeah....duh! was never really sure if that was good stuff in there. thankfully never had to use it......yet!
Click to expand...
Click to collapse
I tried restoring from some other efs backup but I'll look around and see if there is any more backups. I have the sd card saved on my hard disk as well. There should be several backups. Somehow, though, I don't think its the imei or 10.1 is storing the IMEI in a different place or folder. This is too bad because the Aries version of 10.1 is really nice.

I pretty much have the same problem. After upgrading to 10.1 I can't get any reception even though I tried flashing stock and padded modems on 10.1.

i found several efs backups in the backup folder, but expanding them and replacing the efs folder on my phone makes no difference at all, IMEI is still 00000000 ..... unless 10.1 uses an efs folder in a different location that is. This is acting like there is a second backup location for the phone information that,if you don't delete it or overwrite it, restores the bad efs informaiton.

Nvm... deleted.

champ1919 said:
Nvm... deleted.
Click to expand...
Click to collapse
Does anyone know whether the imei information is located in a different location with MTD roms? I have been using the efs folder.
back on my old Galaxy Apollo for the time being -- they are still developing for this phone. Must be a lot of them out there.

I have the same problem. I was using Aries 10.1 just fine. Everything worked great. Then all of a sudden I get no signal. I tried restoring back to stock oneclick w/ factory reset several times. I have an EFS backup which I've restored several times both manually and automatically. No signal, no baseband version, no IMEI. It says unknown on settings for IMEI.
Any help would be greatly appreciated.

Cooptx said:
You can still get signal with an unknown imei it will just take a not longer the first time to connect. I know it isn't a fix but just a thought.
No luck here. I let it sit for 30+ minutes.
Click to expand...
Click to collapse

Also worth nothing that while on CM7 I tried every modem without any success. And I did try doing the oneclick back to stock with the same outcome.

baseband unknown :((

So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!

aamzalag said:
So i must have messed up my phone while using the all in one root unlocker and so on. Im not sure what i did, but i finally got my phone to boot, and now i get no service. Im on tmobile and it says i have no sim card. When i go into about phone it shows baseband unknown.
I really have no idea what to do. Ive never been stuck in this situation. Maybe someone more experienced can point me in the right direction?
any help would be appreciated!
Click to expand...
Click to collapse
so furthermore, it looks like i have no data partition anymore, i can go on my chromebrowser on the phone and browse the web but when i try to install anything it says no sdcard. I also cant move anything to the phone via windows, it just freezes even tho i can see the phone and go into the internal storage.
Im really screwed here. Ive also used the fastboot files to flash back to google stock, but for some reason continue to find everything borked.
HELP PLZ!!! ahah

Also, finding that i cant mount any partition, cache, data, anything liek that. It seems like my partitions have been messed up . Not sure how to resolve that

Well it looks like your the first one to brick the nexus 5. If your imei is missing your screwed.
P.S.A DON'T USE TOOLKITS
Sent from my NEXUS 5

Might be helpful to others to explain exactly what you did to your phone.

lafester said:
Might be helpful to others to explain exactly what you did to your phone.
Click to expand...
Click to collapse
He used a tool kit. Who knows what it did to his phone
Sent from my NEXUS 5

I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?

aamzalag said:
I realize that maybe using the toolkit may not have been a good choice but considering im already here. Constructive advice might be a little more helpful... I know that with my old verizon GS3 if i lost my imei/ similar info, i could nv flash myself and get it back in certain cases. Does a similar thing not exist for the nexus 5? Id imagine that a truly unlocked device like this one should have a method to get back from anything?
Click to expand...
Click to collapse
If you've flashed the stick images and it hasn't fixed it then you might be out of luck. With the n4 there is a thread on how to restore the phone with LG nv flash in download mode. I don't think the tools or files are available yet for the n5 tho
Sent from my NEXUS 5

i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit

So you can't fastboot flash anything? Can you fast boot flash twrp recovery from the android SDK on a PC?
Sent from my Nexus 7

aamzalag said:
i dont know what i did, but i restored the factory image one more time, then booted to stock recovery and wiped all partitions. The phone booted and my imei and baseband are back. Working 100% now. Gonna sit out the rooting and so on for now. time to relax for a bit
Click to expand...
Click to collapse
That's how I fixed my N4. I flashed the factory images 3 times.

Glad it's working finally
Sent from my Nexus 7

Ya, fastboot continued to work, and iw as able to flash the factory images.At first those werent fixing anything. the final time i flashed it right before it worked again, i let the phone sit and run the boot screen for about 30 minutes before i went to stock recovery and wiped. Then it booted perfectly.
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.
Thanks all its working perfect now. The device is amazing,!

aamzalag said:
The previous times i had flashed twrp and wiped which i believe was the cause in the first place.,!
Click to expand...
Click to collapse
Sames just happened to me, but I didnt use a toolkit, i did it all manually.
Quick flash of the factory image sorted it. :victory:
UPDATE: Flashed TWRP again....All ok this time.

You guys unlocked the bootloader first right?
Sent from my SGH-I747

This has just happened to me. I have installed the stock images 2 times now.
Is there anything you guys did differently to make it work?

My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Edit:
Managed to fix it by using a slightly different set of fastboot commands.
Here's what I did:
adb reboot bootloader
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot -w update image-hammerhead-krt16m.zip
fastboot reboot-bootloader
That worked for me

WRAITH07 said:
My N5 decided to wipe the baseband and IMEI when I went to wipe the cache through recovery. Tried to reflash factory images 5 times and each time, when the phone boots up, hangouts, camera and gallery apps force close and I still have no network signal or IMEI/baseband.
Worst bit is all I did was wipe the cache partition, done that a million times and never had this problem
Anyone know what i can do?
I've relocked the bootloader for now but I can't call Google because my only phone is the Nexus 5 so that's out of the question.
Click to expand...
Click to collapse
After you flash the factory image, boot into recovery and do a factory reset.

You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk

cmstlist said:
You mentioned a cache wipe. Was this in CWM or TWRP? My N5 hung trying to do a cache wipe in CWM. After rebooting the sdcard was inaccessible. The solution was to flash TWRP from fastboot, and do an advanced wipe of only the cache, and give it TIME. Like 5-10 minutes. After another reboot I had the sdcard and radio back, but some write permission issues. One more reboot and everything was ok again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had this issue while wiping cache in TWRP 2.6.3.0
Sent from my Nexus 5 using Tapatalk

[Q] TWRP vs CWM in radio issues

So I've heard a ton about twrp botching the n5's radio on flash. Mainly, my question is if either twrp or cwm is fixed in this regard. Also, is it as easy to fix as:
root -> radio gets messed up on new ROM -> download factory image -> fastboot flash the radio img -> no signal issues?
Thanks.
EDIT: Also, if my signal goes down should I flash the 4.4.1 or 4.4 radio?

First I've heard of twrp botching the radio.

jd1639 said:
First I've heard of twrp botching the radio.
Click to expand...
Click to collapse
Must have fixed it then. Whew.
Sent from a phone.

shbaldw said:
Must have fixed it then. Whew.
Sent from a phone.
Click to expand...
Click to collapse
2.6.3.4 fixed pretty much all of the big issues. I've been wiping cache and other things with it, no issues.

The radio botching happens when restoring a backup from a different nexus 5 in twrp. As the efs partition is device specific and restored in twrp it breaks the radio because of the mismatch in information.
If your signal is weaker in 4.4.2 the recommended is going with the 4.4 radio
Sent from my Nexus 4 using xda app-developers app

Alex240188 said:
The radio botching happens when restoring a backup from a different nexus 5 in twrp. As the efs partition is device specific and restored in twrp it breaks the radio because of the mismatch in information.
If your signal is weaker in 4.4.2 the recommended is going with the 4.4 radio
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Don't backup the efs partition. Who does that anyway. Do it once and save it off device.

As Alex said, it isn't exactly TWRP killing the radio. The problem is that TWRP puts powerful tools such as EFS restore in the hands of people who don't know what EFS is. A few people (myself included) didn't know better and flashed the EFS from our previous phone to the new one, resulting in pain, tears and lots of ice cream consumption.
As I said, do not blame TWRP for borking the radio. But maybe blame them for giving rocket launchers to deer hunters.

leblvin said:
As Alex said, it isn't exactly TWRP killing the radio. The problem is that TWRP puts powerful tools such as EFS restore in the hands of people who don't know what EFS is. A few people (myself included) didn't know better and flashed the EFS from our previous phone to the new one, resulting in pain, tears and lots of ice cream consumption.
As I said, do not blame TWRP for borking the radio. But maybe blame them for giving rocket launchers to deer hunters.
Click to expand...
Click to collapse
Yea, that would not be a good thing to do

Alright. I'll back up the EFS to my computer and flash away. Thanks, all of you.
Sent from a phone.

[Q] Any way to recover lost EFS?

Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.

Cheesy Wotsit said:
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Click to expand...
Click to collapse
The same thing happened to me. Flash the latest version of TWRP, wipe your cache again, and your phone will be back to normal.

not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app

ddloco said:
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.

_MetalHead_ said:
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
Click to expand...
Click to collapse
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go

So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk

Elisha said:
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox

TheAtheistOtaku said:
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
Click to expand...
Click to collapse
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk

Elisha said:
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know, still doesnt hurt to be caution though

ddloco said:
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
Click to expand...
Click to collapse
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.

_MetalHead_ said:
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
Click to expand...
Click to collapse
Thanks for the help guys. Got it up and running again more by accident than anything. Seems like MetalHead was correct, the partition was fine but just not readable. Unfortunately in order to get up and running again I flashed all the stock images in flasboot and did a full factory reset in the stock recovery which fixed the problem. Sounds like I could have done without the full wipe after all but at least it's all fixed now.
As for backing up the EFS, lesson learned. I had the 1st official TWRP on the phone which had no option for EFS backup like the current one. Guess what I'll be doing right now??
Anyway, happy man again and thanks to all that replied :good:

I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app

Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )

ddloco said:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thats a bummer man. What kind of phone are you using now?
Lowresolution said:
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
Click to expand...
Click to collapse
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app

_MetalHead_ said:
Thats a bummer man. What kind of phone are you using now?
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it , thanks mate Just upgraded my version of TWRP .

the nexus 4 is my phone I gave to my wife now that its hers I'm lucky to pick it up just to hop on xda but when its her Facebook time she hurrie up and kick me off lol the phone I'm using is an HTC inspire 4g it sucks
Sent from my Nexus 4 using xda app-developers app

[Q] Everything is messed up

idk what happened i was using my phone as normal and was using snapchat, then my camera crashed and rebooted my phone. then i noticed that i didn't have signal so i went to the settings and noticed that everything that has to do with ril is gone like imei, imei sv.
i have tried taking the sim out and back in but it wont work,
also my camera wont work, google play store crashes, but one weird thing is that my modem version does not show in settings but it does in when entering the bootloader. i flashed stock 4.4.2 but still nothing is working
please i need help, have tried searching the forums but cant find any thing this similar sorry if this has been answered before (and i don't have a efs backup because im stupid..)

try reflashing your rom/gapps

Which mods did you have on your phone before it crashed?
Sent from my Nexus 5 using Tapatalk

simms22 said:
try reflashing your rom/gapps
Click to expand...
Click to collapse
already did that, but still no go, also it turns out i cant access my sd card on the pc nor on the nexus 5

nemofbaby2010 said:
Which mods did you have on your phone before it crashed?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
was using multirom with the sense 6.0 port, and xposed. that was pretty much it

FettleifIsMyUserName said:
was using multirom with the sense 6.0 port, and xposed. that was pretty much it
Click to expand...
Click to collapse
did you flash the stock rom zip or did you use the actual factory images?
try using the factory images youll lose everything but you might get your phone back: https://developers.google.com/android/nexus/images#hammerheadkot49h

nemofbaby2010 said:
did you flash the stock rom zip or did you use the actual factory images?
try using the factory images youll lose everything but you might get your phone back: https://developers.google.com/android/nexus/images#hammerheadkot49h
Click to expand...
Click to collapse
used the factory image didnt work, internal sdcard is gone, gonna try one more time

flashed the 4.4.2 factory image, still the same problems no imei or nothing and the sdcard is blank

FettleifIsMyUserName said:
flashed the 4.4.2 factory image, still the same problems no imei or nothing and the sdcard is blank
Click to expand...
Click to collapse
Sounds like another flash memory failure. Call Google and see if they'll RMA it.

FettleifIsMyUserName said:
flashed the 4.4.2 factory image, still the same problems no imei or nothing and the sdcard is blank
Click to expand...
Click to collapse
Have you flashed the cache.img? Try flashing it 2-3 times... Or just head over to stock recovery and format cache 2-3 times and then do a factory reset.. These things needs to be done via the stock recovery and not a custom one.
I had a similar problems some weeks ago and this solved it!

theesotericone said:
Sounds like another flash memory failure. Call Google and see if they'll RMA it.
Click to expand...
Click to collapse
i live in norway we cant send them to google directly it has to go trough the company where u bought it, say for an example my carrier telenor which would then deal with the problem. but i bought mine of ebay because i wanted it faster (due to problems of the 2012s nexus 7 where we didnt receive it before november.) so i guess the phone is pretty much useless now?

vin4yak said:
Have you flashed the cache.img? Try flashing it 2-3 times... Or just head over to stock recovery and format cache 2-3 times and then do a factory reset.. These things needs to be done via the stock recovery and not a custom one.
I had a similar problems some weeks ago and this solved it!
Click to expand...
Click to collapse
didn't notice your comment, ill try it and report back

nope...wiped the cache 3 times then a factory reset in stock recovery booted up still the same problems

Don't know if this will work in your case but it may be worth a try http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833

Give a try to this method too maybe it will work for you.:good:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447

i had the same issue when running the Nexsense port. There was a known issue that it would break the sensors back when it first got released but the DL link got removed immediately. after that there was a post to correct the sensors. but there was another issue with it as well. seeing as it was a NAND backup, it was very possible it re-wrote you EFS partition on your phone which stores you IMEI and other data like that. The only possibility of getting that back, is if you did a backup of the EFS partition prior to having an issue. just a warning: DO NOT FLASH ANOTHER PHONES EFS PARTITION TO YOURS. the only way to get the phone to work again with a messed up EFS partition (from what i have seen) is through replacement device unfortunately

http://forum.xda-developers.com/showthread.php?p=52414651 to let all of you know it is solved
Tapatalk-kal küldve az én Nexus 5-el