[Solved] Baseband unknown IMEI unknown HELP! - Galaxy S Advance I9070 General

When i flash CM based roms i lose my baseband and imei, i have tried flashing a lot of roms and every rom makes my baseband and imei unknown. I used to flash roms all the time and this would never happen, but one time before flashing omni rom i accidentally wiped /system in CWM, and after that every rom has the same problem. I have tried flashing stock via odin and that brings back the imei and baseband every time, but i don't wan't to use stock. Can anyone help me?

One more thing. I have tried backing up both efs and modemfs while on stock and then recovering them on CM but it doesn't work, Also I have noticed that the efs folder is not empty when the baseband and imei are unknown.

[email protected] said:
One more thing. I have tried backing up both efs and modemfs while on stock and then recovering them on CM but it doesn't work, Also I have noticed that the efs folder is not empty when the baseband and imei are unknown.
Click to expand...
Click to collapse
Try with this http://forum.xda-developers.com/showthread.php?t=2165344&page=4

shut_down said:
Try with this http://forum.xda-developers.com/showthread.php?t=2165344&page=4
Click to expand...
Click to collapse
the user in that thread is on ginger bread, wouldn't the process be different in jelly bean?

It won't be a problem since you're issuing commands through ADB. Just have rooted JB + cocore + working busybox and give it a try.

here is what i did in terminal emulator:
$su
#busybox mke2fs /dev/block/mmcblk0p7
mke2fs: can't format mounted filesystem
it seems that /efs is mounted but android isn't recognizing it, I'm on CM11

I've read in other threads that nv_data.bin is my imei, but when I went to /efs to see if I have a nv_dada.bin I noticed I only have a nv_data.bin.md5 and a nv.log, this is what the nv.log had inside:
Sun Jan 1 00:00:03 2012: NV data back-up begin.
Sun Jan 1 00:00:03 2012: nv_data.bin does not exist.
Sun Jan 1 00:00:03 2012: NV data backup stopped due to NV data size.
Sun Jan 1 00:00:03 2012: MD5 is turned on.
Also I have noticed that nv_data.bin.md5 is 0B

bump

[email protected] said:
bump
Click to expand...
Click to collapse
Better try searching about that problem, on our sections. Do not use other phones fix because we can have differend partitions, so you can mess up even more...

I have searched and tried almost everything, nobody has experienced this problem

[email protected] said:
I have searched and tried almost everything, nobody has experienced this problem
Click to expand...
Click to collapse
On what baseband is your phone? The one from Hong Kong make this problem, and no one solved it.

I'm on the latest Italy Firmware, and I have been able to flash roms before without experiencing these problems.

I found a thread where there was an Odin flashable modem/baseband so now I'm going to try to flash that on TC CM 11 and report back... good luck to me

still baseband unknown

Some additional things I have noticed...
When I flash the Italy Firmware, which the CSC is I9070ITVLQ5, after the flashing process finishes ODIN shows the blue "RESET!" and even if I wait it doesn't show "PASS!" and my phone goes in a bootloop, so i have to go to recovery to wipe data/factory reset, and only then it will boot, now every thing seems to work good, but, when I go to setting the baseband should be I9070ITVLQ5 but it shows I9070XXLQ4. I've flashed one other firmware and the same happens, bootloop and the baseband doesn't change.
What I'm going to try is revert back to gingerbread and then update it via Kies... maybe then i could flash CM roms... good luck to me!

[email protected] said:
Some additional things I have noticed...
When I flash the Italy Firmware, which the CSC is I9070ITVLQ5, after the flashing process finishes ODIN shows the blue "RESET!" and even if I wait it doesn't show "PASS!" and my phone goes in a bootloop, so i have to go to recovery to wipe data/factory reset, and only then it will boot, now every thing seems to work good, but, when I go to setting the baseband should be I9070ITVLQ5 but it shows I9070XXLQ4. I've flashed one other firmware and the same happens, bootloop and the baseband doesn't change.
What I'm going to try is revert back to gingerbread and then update it via Kies... maybe then i could flash CM roms... good luck to me!
Click to expand...
Click to collapse
well, that pass/reset in odin doesn't matter. just wiping data and cache will solve it and i too experienced it many times, afik in our device imei is in efs and you may have want to search about it. i found a thread somewhere for this problem and solution is clearly written there, if i get that thread i will say

PradeepMurugan said:
well, that pass/reset in odin doesn't matter. just wiping data and cache will solve it and i too experienced it many times, afik in our device imei is in efs and you may have want to search about it. i found a thread somewhere for this problem and solution is clearly written there, if i get that thread i will say
Click to expand...
Click to collapse
believe me I have tried wiping data/factory reset and also wiping the cache many times, my problem is still there

M0shi said:
believe me I have tried wiping data/factory reset and also wiping the cache many times, my problem is still there
Click to expand...
Click to collapse
I read in another forums, for another devices, if you flash another modem.bin in the rom, it works, i don't try this but you don't loose anithing triying
Sorry for my bad english, hope you undestand me

shompy said:
I read in another forums, for another devices, if you flash another modem.bin in the rom, it works, i don't try this but you don't loose anithing triying
Sorry for my bad english, hope you undestand me
Click to expand...
Click to collapse
Thanks, I will try that after i go back to jb...
Right now I'm on GB, used this tutorial http://forum.xda-developers.com/showthread.php?t=2100642 , network is working but my baseband is still LQ4, everything stock i flash my baseband stays LQ4... weird :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Okay so I got back to Jelly Bean LQL, my baseband is still LQ4, I tried flashing the LQL modem.bin via ODIN (on a tar file) and via CWM with a script someone made, still no change

Related

/Cache partition cannot mount in CWM, makes flashing custom ROMs impossible: HELP!

Hi everyone, I've searched everywhere and can't find an answer to this question.
I received a Nexus S with the bootloader already unlocked. I used fastboot to push the CWM recovery to it, and with it used .zip file to flash superuser to gain root.
I can boot the phone and use it without issue, but when I go into the Recovery menu, several error messages regarding its inability to mount the /cache partition comes up.
This means that I cannot backup, restore or flash anything, and I don't want to mess around with partitions in GParted until I know what to do.
Any suggestions here? Your help is greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you go to the "mounts and storage" menu, are you able to "format cache"? Give that a try and reboot to recovery and see what happens.
Hey thanks for the response. Unfortunately since I can't mount the /cache partition I can't format it. That was one of the first things I tried.
Here's what it looks like when I try to format /cache:
Code:
Formatting /cache
E:format_volumeL no MTD partition "cache"
Error formatting /cache!
Sent from my HTC Vision using XDA Premium App
When you boot the phone normally, you're able to go to /cache with Root Explorer or another file explorer type app or not?
Maybe try an older version of Clockwork, or even stock recovery to see if you can format/mount/wipe from one of them.
have the same problem but i can't boot in android either it just hangs at google logo and if i boot in recovery i get this error (didn't flash any roms yet it happend after i flashed clockworkmode
i was able to boot andriod again with odin but clockwork still gives the cache error so i still can't flash anything else on it
I have the exact same problem and I cannot flash any roms in my Nexus S at all.
@awryter : Is your nexus S the new "i9023"? Because mine is the new Nexus S, it might be the reason why our phones are different from others. And have this error :S
mine is alsof the Europeanen model i9023
Sent from my Nexus S using XDA Premium App
I just bought my Nexus S yesterday, and I seem to be having the same issue. I was able to unlock the bootloader just fine, as well as flashing ClockWorkMod, but as soon as I tried to install the netarchy kernel I noticed it wouldn't work.
I'm also using the I9023 if it makes any difference.
A new insight to this problem.
Most people, or even all the people, who have this problem. Are using the new i9023 Nexus S.
There are people who are using the i9023 Nexus S and have their phones rooted without problems. But their phones come with GRI40 instead of GRI54.
So I'm guessing it might be a problem of GRI54 i9023 Nexus S
navlem said:
A new insight to this problem.
Most people, or even all the people, who have this problem. Are using the new i9023 Nexus S.
There are people who are using the i9023 Nexus S and have their phones rooted without problems. But their phones come with GRI40 instead of GRI54.
So I'm guessing it might be a problem of GRI54 i9023 Nexus S
Click to expand...
Click to collapse
I have GRI54, and have it rooted just fine. It's just the cache partition that's not working for me.
rooting worked also for me, it's just that cache problem asswell
Maybe i used the wrong term. Installing custom firmware didn't work due to cache problems. Rooting on stock works fine for me, though titanium backup said its not rooted at all, even when superuser permissions are granted. Maybe you guys wanna try titanium backup and see if you are having the same problems as me?
navlem said:
Maybe i used the wrong term. Installing custom firmware didn't work due to cache problems. Rooting on stock works fine for me, though titanium backup said its not rooted at all, even when superuser permissions are granted. Maybe you guys wanna try titanium backup and see if you are having the same problems as me?
Click to expand...
Click to collapse
Looks like you're right. Titanium Root installed fine, asked me for super user permissions, which I gave it, and then it told me it didn't have root acces.
grwn6 said:
Looks like you're right. Titanium Root installed fine, asked me for super user permissions, which I gave it, and then it told me it didn't have root acces.
Click to expand...
Click to collapse
yep same over here
Yup, which brings me to why i used "Unable to root" as a term for our problems. Because we are not fully rooted in some sense yet.
But of cos the source of the problem comes from the cache which seemed to be 'non-existant' or 'non-writable'
And only GRI54 i9023 users have this problem.
after installing busy box , TI backup says it's rooted
suboxide said:
after installing busy box , TI backup says it's rooted
Click to expand...
Click to collapse
I can confirm this.
Rebooting after installing busybox removes the root rights again. I'm not sure if this is intended, but from what I've seen so far, I'd guess not.

()()()()()()() everyone having the force close issue read this ()()()()()

More and more people keep having this problem. Your phone suddenly has tons of force closes, and becomes unfunctional. Well we seem to have a problem with our recovery, possibly causing a corrupt partition. There is a solution .......use odin to flash the stock recovery tar found in development. Boot into stock recovery.. wipe data, and cache 3 times each ,and boot the rom back up. Then use rom manager to flash the tmobile gs2 cwm recovery. This does work. And has been proven numerous times.
Here is the stock recovery http://forum.xda-developers.com/showthread.php?t=1360943.
If for some reason you still have this issue after following my advice. Use odin to flash the stock firmware tar found here http://forum.xda-developers.com/showthread.php?t=1342348. After your done. Let it boot. If u get the force closes. Then proceed to power off, boot into stock recovery, and then wipe your data/cache, and reboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Excellent post... Thx
another good one Silver Thanks....im curious as well to see how many are really having this issue<<<
Is there a difference between the TMobile GS2 CWM recovery and the CWM recovery flashed using this method (http://forum.xda-developers.com/showthread.php?t=1340526)?
I had the described problem, but wiping and reloading the intended ROM in CWM recovery fixed it.
That is good but alot of times that does not work. It can actually get to the point where it will not read the internal sd card
How are you guys flashing....and what are you flashing that is giving you these issues.
I have yet to experience these issues on T-Mobile or skyrocket roms.
What are the exact steps you follow when flashing a from to begin with?
Sent from my SAMSUNG-SGH-I727 using XDA App
I have experienced this on stock, and custom roms. And im not the only one. Alot of people have had this issue
Lets put it this way enough people have had this problem, and more will to the point where i made this thread, and asked a mod (jayharper08) to sticky it.
yes ALOT have......they may not have known it was a known issue and solved it. but it is there.
I am not saying you guys are not having issues...there has to be a reason I am not which is why I ask.....What steps exactly do you guys use to flash a rom and what roms. The process to fix it is great but if we could prevent it in the first place wouldn't that be better????.
silver03wrx said:
I have experienced this on stock, and custom roms. And im not the only one. Alot of people have had this issue
Lets put it this way enough people have had this problem, and more will to the point where i made this thread, and asked a mod (jayharper08) to sticky it.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
Silver,
Question...based on several of your other posts in threads, if we have 2.3.6 and use http://forum.xda-developers.com/showthread.php?t=1340526 to root/install recovery, are things ok?
Or should we still follow this thread to update CWM via ROM Manager?
Thanks.
^^^
That was my question too. What's the difference between the two recovery's?
I was having the issue too. I had the issue on stock(pure from store) as well as stock rooted, skyrocketeer, and cm7.
One thing I have tied it to, which I am not sure is the true reason but I was too impatient to test it thoroughly, is excessive SMS messages.
I have over 32k messages currently stored on my HTC Inspire. These have been moved from my G1, to Nexus One, to Inspire with no issue at all. When importing to my Skyrocket, the messages will import fine for a while. Afterwards, I would get random FCs, screen freezes up(can't do anything, not even turn off the screen), and network disconnects. I can force a reboot by holding the power button and it will work for about 5 minutes and then repeat the issues as before.
At first I thought it was the specific device having radio issues so I exchanged it for a new unit at Best Buy. I was still having the same issues with the new unit so I just figured I could cut my losses (on screen protectors and phone case) by just returning the until outright. I figure I will wait for the ICS update for this phone, hoping it will be more stable. Maybe at that point I can compare with other phones available as well.
I have had this problem repeating several times even after flashing the Rom and repeating steps as mentioned. I think it does it with a certain number of apps that downloaded from the market.
silver03wrx said:
More and more people keep having this problem. Your phone suddenly has tons of force closes, and becomes unfunctional. Well we seem to have a problem with our recovery, possibly causing a corrupt partition. There is a solution .......use odin to flash the stock recovery tar found in development. Boot into stock recovery.. wipe data, and cache 3 times each ,and boot the rom back up. Then use rom manager to flash the tmobile gs2 cwm recovery. This does work. And has been proven numerous times...
Click to expand...
Click to collapse
Is this a problem that develops as you start flashing more and more ROMs? Is there a known cause?
I'm new at this stuff - just rooted and tried my first ROM this week. I'm tempted to try others but if chances are good that I'll run into problems/issues even if I'm going about things the right way - I might hold off on making a change given that the phone is stable right now.
Thoughts?
NO rom does not cauz this issues. What causes issue is when you restore data from ur backups. Plus there is problem with cwm it does not fully wipe data because cwm was not particularly made for our phone. That being said you do not have to worry about a thing. I am flashaholic and i used to flash every other day since i m with Sky ice cream rom by Sean i don't flash a lot. Don't worry just try out all the roms you won't have problem by roms at all. There was only one rom that had problem Alien the first or second build.
Locoman_ said:
Is this a problem that develops as you start flashing more and more ROMs? Is there a known cause?
I'm new at this stuff - just rooted and tried my first ROM this week. I'm tempted to try others but if chances are good that I'll run into problems/issues even if I'm going about things the right way - I might hold off on making a change given that the phone is stable right now.
Thoughts?
Click to expand...
Click to collapse
Thank for the reply.
BTW, I'm using Sean's Sky IC too. Sooo nice.
Do you need to go into download mode to flash the recovery in ODIN? Or do you do it when the phone is just turned on regularly?
You have to go to dload mode in order to flash recovery. and use odin.
nutsngum said:
Do you need to go into download mode to flash the recovery in ODIN? Or do you do it when the phone is just turned on regularly?
Click to expand...
Click to collapse
I tried this process and I wanted to flash a new ROM. But in recovery mode it wouldn't read my SD card, and when I transferred the .zip to my internal memory and I tried to install it said I had no space.
Any ideas?

wifi issue how to fix?

please how to fix wifi. I tried many roms and kernels and every modem but the wifi still doesn't work.
how do you guys make it work? please someone answer me bcoz in my other posts nobody helped
manzifa45 said:
please how to fix wifi. I tried many roms and kernels and every modem but the wifi still doesn't work.
how do you guys make it work? please someone answer me bcoz in my other posts nobody helped
Click to expand...
Click to collapse
Give us some more info.
What rom are you currently using?
Did you follow the directions and do a factory reset before/after flashing the rom?
What else are you flashing or doing?
bhundven said:
Give us some more info.
What rom are you currently using?
Did you follow the directions and do a factory reset before/after flashing the rom?
What else are you flashing or doing?
Click to expand...
Click to collapse
CM9 with KJ6 padded modem
I followed all the instructions and now I flashed CM7 everything
work well even the wifi but I would like to have ICS thanks
Jeffsf did help you in your other post he gave you all the info needed.
That's pretty rude to say you weren't helped.
jeffsf said:
CM9 works just fine for WiFi. It is only the T-Mobile WiFi Calling feature that does not work on any ICS ROM for the SGS4G.
Changing the modem has nothing to do with the Wifi driver. It sounds like a bad flash or the way data was restored.
I'd read the Q&A thread - http://forum.xda-developers.com/showthread.php?t=1729121 and post any unanswered questions there.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
There is several of your posts that where answered as well based on this same topic.
And this is what you said not long ago
i thought this phone was a good deal and now i m deceived and
this coming month i m looking to get a sony xperia, samsung is a real s*** dont
even know why people continue to compare it to the greatest iphone.
Click to expand...
Click to collapse
Shortbus-Driver said:
Jeffsf did help you in your other post he gave you all the info needed.
That's pretty rude to say you weren't helped.
Click to expand...
Click to collapse
i have tried everything, flashed every rom,every kernel,every modem given here and the wifi doesnt work except on GB roms
and i was surprised that there is zero "0" videos on youtube about this phone!
i was thinking make one and post the link here where i flash CM9 from stock kj6 2.3.6 with CWM 5.0.2.8
and u will tell me if i did something wrong
manzifa45 said:
i have tried everything, flashed every rom,every kernel,every modem given here and the wifi doesnt work except on GB roms
Click to expand...
Click to collapse
I think it is interesting that you say you have tried everything, but I don't know what everything means, because wifi works for me on every rom. So you did not try everything, you are doing one thing wrong that no one else is having a problem with.
manzifa45 said:
and i was surprised that there is zero "0" videos on youtube about this phone!
Click to expand...
Click to collapse
Considering we are here on XDA, and this is a forum, we usually write text (you know... this stuff) and you have to read it. If I or any other developers for this phone took the time to make a video on how to do something that is better explained in text format, we would never get time to dev anything (and you would hear my wife constantly yelling at me while I'm making a video... I don't need to expose you to that world!).
manzifa45 said:
i was thinking make one and post the link here where i flash CM9 from stock kj6 2.3.6 with CWM 5.0.2.8 and u will tell me if i did something wrong
Click to expand...
Click to collapse
How about instead, you do things one step at a time. At each step, write down what you did and the results. Be as detailed as you can. Use correct english, so we understand what you are saying. (you instead of u, because instead of bcoz, etc...)
When you get all done, post to this thread and we will help!
bhundven said:
you do things one step at a time. At each step, write down what you did and the results. Be as detailed as you can
Click to expand...
Click to collapse
thank you i really apreciate
ok i was running CM7(which is smooth and work great, thanks to team acid) but decided to try again...and here is what i'm doing:
- i returned to stock 2.3.6 via Odin and CWM is 3.0.2.8 in Red (don't know why, but you probably do)
- to have CWM 5.0.2.8 i flashed a kernel (Basic with a Twist SGS4G KJ6 1.1.3)
- then after rebooting twice i get into cwm 5.0.2.8 and i did wipe data/factory reset,wipe cache partition,wipe dalvik cache
- then install zip from SD card...then flash "cm-9-20120830-UNOFFICIAL-galaxys4gmtd" (that i downloaded twice to make sure the package is good)
- reboot and flashed Gapps and reboot again and flashed the "kj6_padded_modem"
- i rebooted twice and entered cwm and did wipe cache partition,wipe dalvik cache, fix permissions
after a reboot when i turn on wifi it tells me "wifi turning on" and didn't detect any signal but all other stuff work.
hope its clear than before
Tried getting closer to the router? Your wifi is accessible with other devices? You HAVE wifi?
Sorry if that sounded mean, but like Bryan said, there are no problems with wifi an any rom I have used either.
Sent from my SGH-T959V using xda premium
sunsurfer42 said:
Tried getting closer to the router? Your wifi is accessible with other devices? You HAVE wifi?
Click to expand...
Click to collapse
Of caurse i do!! the router is in my room signal is excellent with stock 2.3.6 and CM7. only on CM9 it shows "wifi turning on" and least forver
let me try to attach pictures. i will stay on 2.3.6 stock or cm7.:crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think you might be missing a key step.
Go back to stock.
Flash basic with a twist to get the right recovery.
Wipe data/factory reset.
Wipe cache.
Wipe dalvik cache
Go to mounts "WIPE SYSTEM"
Flash rom.
Let it do is thing and reboot you into cm9.
Then reboot into recovery flash gapps.
you shouldn't need to flash the radio if you already had kj6 before, I never do. But what I like to do is repeat the wipes and fresh install of cm9 after the initial install from gb just to be on the safe side though I'm sure it's over kill, then flash the gapps. restart and let the phone settle in before I mess with it. Works for me every time.
Sent from my SGH-T989 using xda app-developers app

[Q] Help! Stuck on Raoming After Flashing CM10 Nightlies

I have been trying to fix this problem and browsing threads with similar issues all night for about 6 hours and nothing seems to work.
I have been running on stock ICS 4.0.4 which I rooted and unlocked awhile back with no problems. I finally had the time to attempt to flash cm10 and I wanted to give it a shot, so I backed everything up, wiped data, wiped cache, wiped davlik, format /system. The ROM I attempted to flash was the newest version of cm10 nightlies 12-28 and gapps. After flashing everything went well and the phone booted up in cm10, but it is stuck on roaming. I tried everything that I could find in the forums and nothing seems to be working. I wiped again and tried to restore from my backup and the problem is still there, so I even went a step further and used Odin to flash fully stock unrooted/locked ICS 4.0.4 again and still have the same issue. The IMEI numbers matched up both times after flashing and I also made a backup before and even restored it to my phone as well, so I know that's not the issue.
Most of the threads I read said people were having success with "reprovisioning" their phone, but when I dial *2767*3855# nothing happens on my phone at all. Am I doing something wrong? Are there any other solutions out there that I might have missed?
Please help me so I don't have to return to the Verizon store when they open.
Thanks in advance!
You have to change to ruim/sim in mobile network settings
Should be under cdma subscription settings. Flashing to cm 10.1 changes it to Nv.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also system select you should change to automatic, not home.
I can't find any of those settings in my settings menu. I am back on stock ROM unrooted and locked with everything reverted to factory settings.
Ahh no idea on stock rom or tw. This is for cm.
It's strange to me because after wiping everything and restoring to factory locked settings, you would think it would go back to what it's automatically set to...
I got it!!!
Basically I used Odin to port a stock ROM that was already rooted and went through the flashing procedures as usual. Then I used what you gave me above and it is now working. Thanks so much for your help it's really appreciated!
And to think after all the trouble I went through reflashing everything that was all I had to do :laugh:
Thanks a lot!
xNali said:
I got it!!!
Basically I used Odin to port a stock ROM that was already rooted and went through the flashing procedures as usual. Then I used what you gave me above and it is now working. Thanks so much for your help it's really appreciated!
And to think after all the trouble I went through reflashing everything that was all I had to do :laugh:
Thanks a lot!
Click to expand...
Click to collapse
I'm new to odin and am having the same problem you are having. How did you unlock the bootloader and put cwm or twrp without data. I can't get the ez tools because wifi doesn't even work.
Ok. I was wrong wifi does work. In all my panic I did the wifi password wrong. How embarassing... And it's fixed!
Glad to see you sorted it out. Was going to suggest flashing back to cm 10.1 to access the settings.
Don't let this experience turn you off. Cyanogen mod is really great.
If you don't want to deal with the roaming problem I'd recommend flashing cm 10 12/16 nightly. Everything works peachy with the exception of the Bluetooth bass bug. You can fix it by making a call though.
Cm10.1 has low call volume but it runs really smooth. When you flash it you have to either not flash gapps so you can change the settings I mentioned in previous post, bypassing getting stuck on activation, and then flash gapps OR use the four corner trick to bypass activation (if you flashed gapps). After you change the mobile network settings, reboot and data should be fine.
It's really not that hard of a process. I got stuck in roaming the first time I flashed 10.1 but I understood what the problem was before hand. I flashed 10.1 and gapps immediately, like I always do with cm, and was stuck on the activation screen. I forgot the four corner code to bypass the activation process also. When I tried to restore a nandroid I couldn't cause it moved all the files around.
To make an already long story short, I had to download 10.1 to my SD card to flash without gapps and make the settings change.

[Q] [SOLVED] No EFS backup. IMEI lost.

So, I unlocked bootloader of my N5. Flashed CWM Touch. Didn't make any kinda backup (I know I'm stupid) and flashed paranoid android. Now I'm not getting any signals on it. Please, I'm in need of desperate help. Any solutions?
EDIT:
Flashed stock image, good as new This should help people who are as stupid as me
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
rootSU said:
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Trying this
vin4yak said:
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
Click to expand...
Click to collapse
But, I did not wipe data/factory reset..I went into mounts and storage and wiped everything except sd-card
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Go to your custom recovery and wipe everything (data/cache/dalvic)... Now flash the rom.zip and gapps.zip and finally reboot and see whether you're able to get a signal or not?
OR
You could use this guide to return to full stock and check... http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
jd1639 said:
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
7alvi said:
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
Click to expand...
Click to collapse
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
The 2 lines is are normaly
Try again with admin rights
7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
That could be because you extracted the image-hammerhead xxxxx.zip file. dont extract it. it should be there like it is on this picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I officially pronounce this phone as un-brickable. Yes it's fixed. IMEI, baseband siganls everything is back... @rootSU I owe you a beer man. I can't emphasize how ****lessly scared I was...thanx a lot!
No worries
Sent from my Nexus 5 using Tapatalk
Just pumping this thread.
I've gone through a few steps but have ran into a snag.
Heres the synopsis;
My device was randomly shutting down while charging so I decided to factory reset to see if that helped.
When I did the the device entered a boot loop and when I went into recovery it would say can't mount cache etc.
I tried re flashing 5.0.1 Lrx22c but again it got stuck in a boot loop.
I managed to flash 4.4.4 and the device finally turns on.
The only problem is that the phone appears to be without any network connection. Google playstore cannot open and crash's and so does the camera and gallery applications. Adding a sim card does nothing to help.
I'm not sure how to fix this problem and I'm at a point where I need to ask for help. I'm Canadian and bought the device through one of our providers, Rogers, and am starting to think that there is a specific set of 'roger' img's that I need to flash and not the ones from the developers site.
Any input would be much appreciated.
Bump bump ^^
There is no such thing as carrier specific factory images. Did you try reflashing the radio, or a different radio? Remove and reinsert Sim? Might be hardware issue otherwise ..
Sent from my Nexus 5 using Tapatalk
At my wit's end.
I realize it's been 2 weeks since you posted but, in the hope that you are subscribed still Radioman66, I'm curious if you did ever manage to fix/reinject your IMEI; I'm Canadian too btw, though I bought my Nexus 5 through Google Play. I've tried flashing stock everything: bootloader, radio, boot, system, cache, userdata via fastboot; only then did my phone reboot properly, but it still has a habit of crashing/rebooting every so often. No IMEI & no cellular reception thus far, so I can only conclude that there is some data corruption at play here. Fortunately it was easy to find my unique IMEI via a sticker on the inside of the back cover of my Nexus 5, for those who aren't aware.
So I'm in the opinion that the issues of bootloops and my IMEI corruption (dialling *#06# on the dialer calls up a bold IMEI header but no number whatsoever) first occurred when my battery drained to zero. I was using a custom rom at the time, Optipop Dark Deodex with f2fs formatted data and cache partitions, + Multirom & multirom compatible TWRP. I'm at a loss for why the EFS partition and thus IMEI would even be accessed by the phone for writing/reading or how a corruption of the partition could even occur. Perhaps I was receiving a text message right at that very moment it turned off? Perhaps f2fs is to blame, who really knows...main thing is my IMEI is corrupted and I'm left with a smart brick, it being no longer a smart phone.
Anyway, long story short it's been like 2 days of searching around but I think this free tool "Setup DFS 15.01.17.0.zip" at cdmatool dot com (can't post link as a newbie so replace dot with a period) may be the real deal; it's possible to download it without registering i.e. demo mode ( which makes you wait tens of seconds between operations). Despite my general comfort with adb, fastboot, cmd tools in general, the CDMAtool's manual is full of stuff and acronyms I don't really know about yet, like COM Ports and what not but I'm hoping to soon understand this tool and will report back my failures/successes. If anyone would be kind enough to perhaps walk me through what I would need to do, I'd be super thankful!!!t
Welp, cheers to not even knowing about the existence of ESN/EFS/IMEI before this unfortunate juncture LMAO--I will definitely make sure to backup my EFS partitions before flashing custom roms from now on...

Categories

Resources