[Q] EFS and Support

Search This thread

AplusJ

New member
Jun 11, 2014
2
1
So today I think I messed up pretty bad.
I was installing the Carbon Rom via fastboot and after, I went to delete the cache and userdata.
Now, I didn't notice anything strange, I was at home and on wifi. Until' I tired texting a friend. I noticed that nothing was showing up. No IMEI, no number, no baseband!

I was planning on running a data recovery tool on the / area whenever I next can, but if I can't get the EFS back, what would be the next course of action?
Flash stock and send it back to Google to get fixed?

Also, what is the exact location of the EFS directory on the nexus 5's?
Someone offer me some guidance, I feel so lost!
Thanks, Alex. :confused:
 

jd1639

Inactive Recognized Contributor
Sep 21, 2012
16,833
5,404
Minnesota
So today I think I messed up pretty bad.
I was installing the Carbon Rom via fastboot and after, I went to delete the cache and userdata.
Now, I didn't notice anything strange, I was at home and on wifi. Until' I tired texting a friend. I noticed that nothing was showing up. No IMEI, no number, no baseband!

I was planning on running a data recovery tool on the / area whenever I next can, but if I can't get the EFS back, what would be the next course of action?
Flash stock and send it back to Google to get fixed?

Also, what is the exact location of the EFS directory on the nexus 5's?
Someone offer me some guidance, I feel so lost!
Thanks, Alex. :confused:

First, how did you flash carbon in fastboot?

Second, there is no efs folder it's a partition

Try flashing the cache.img in fastboot

Sent from my Nexus 5 using XDA Free mobile app
 

AplusJ

New member
Jun 11, 2014
2
1
First, how did you flash carbon in fastboot?

Second, there is no efs folder it's a partition

Try flashing the cache.img in fastboot

Sent from my Nexus 5 using XDA Free mobile app

I have restored it to stock, and it's all fine. But stock sucks.
And I mean in recovery.img, clockwork touch.

The problem lies within the radio.img, as that is the thing stopping the baseband coming.
Will try reflashing Carbon and then putting the stock radio.img onto it. :silly:
 
  • Like
Reactions: DaringDomino3s

jd1639

Inactive Recognized Contributor
Sep 21, 2012
16,833
5,404
Minnesota
I have restored it to stock, and it's all fine. But stock sucks.
And I mean in recovery.img, clockwork touch.

The problem lies within the radio.img, as that is the thing stopping the baseband coming.
Will try reflashing Carbon and then putting the stock radio.img onto it. :silly:

You could have just flashed the cache.img on fastboot and would have solved your problem without losing your custom Rom or data. Something to remember if it happens again.

Sent from my Nexus 5 using XDA Free mobile app
 
  • Like
Reactions: danarama

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    First, how did you flash carbon in fastboot?

    Second, there is no efs folder it's a partition

    Try flashing the cache.img in fastboot

    Sent from my Nexus 5 using XDA Free mobile app

    I have restored it to stock, and it's all fine. But stock sucks.
    And I mean in recovery.img, clockwork touch.

    The problem lies within the radio.img, as that is the thing stopping the baseband coming.
    Will try reflashing Carbon and then putting the stock radio.img onto it. :silly:
    1
    I have restored it to stock, and it's all fine. But stock sucks.
    And I mean in recovery.img, clockwork touch.

    The problem lies within the radio.img, as that is the thing stopping the baseband coming.
    Will try reflashing Carbon and then putting the stock radio.img onto it. :silly:

    You could have just flashed the cache.img on fastboot and would have solved your problem without losing your custom Rom or data. Something to remember if it happens again.

    Sent from my Nexus 5 using XDA Free mobile app