I was running the carbon pie rom and thought there was too much lag for my liking so I flashed Task's AOKP after doing a factory reset and wiping the cache/dalvik. Now I don't get any 3G connectivity and on some occasions I receive full bars but only with a "G" where the 3/4G should be. Also I will sometimes have the phone go from 5 full bars of 3G to none and no network connectivity. I have tried reflashing, and flashing back to Carbon with no differing results.
Any help would be greatly appreciated.
andymyrick said:
I was running the carbon pie rom and thought there was too much lag for my liking so I flashed Task's AOKP after doing a factory reset and wiping the cache/dalvik. Now I don't get any 3G connectivity and on some occasions I receive full bars but only with a "G" where the 3/4G should be. Also I will sometimes have the phone go from 5 full bars of 3G to none and no network connectivity. I have tried reflashing, and flashing back to Carbon with no differing results.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
hows the ol' IMEI? try a new modem? if all else fails, flash back to stock and then start over with aokp.
xBeerdroiDx is correct. Make sure your IMEI is there, if so try a new modem.
I just had an issue with not being able to get LTE recently after a TW ROM flash. New modems / ROM flashes wouldn't solve it. Something got borked and I had to reflash stock. I just ODINed a rooted image and everything was back up and running.
Don't wanna sound like a broken record considering xBeerdroiDx seemed to cover it, just wanted to highlight my own experience since it was similar.
Sent from my SGH-I747 using xda app-developers app
Thanks for the quick replies, but what radio do I flash and where can I find it?
I just found that my IMEI is 0 and my IMEI SV is 00. Not sure what to do from there.
Did you take a backup of your nv data? Or make a nandroid of existing ROM before installing a new one?
andymyrick said:
Thanks for the quick replies, but what radio do I flash and where can I find it?
I just found that my IMEI is 0 and my IMEI SV is 00. Not sure what to do from there.
Click to expand...
Click to collapse
If your IMEI reads 0, you do not need to flash a new modem, that will not fix the problem. I assume you didn't back up your NV data / EFS folder?
If you have not you will need to manually create and inject your IMEI back into your phone. No other way will fix this, not even an ODIN back to stock.
Read the directions here for how to do it: [FIX/TOOL] Backup/Restore/Fix IMEI & Data Restore Tool v3.0
I don't know how to backup my nv data so no I didn't do that. And I thought I made a nandroid but i think i lost it because i just installed TWRP from CWM. I feel like im a lost case with this phone and don't know what to do because not only can I not figure out how to do this but I also have a mac that cant run a VM because the laptop is from '06.
If you backed up using CWM, it would be under /clockworkmod Check under there.
andymyrick said:
I don't know how to backup my nv data so no I didn't do that. And I thought I made a nandroid but i think i lost it because i just installed TWRP from CWM. I feel like im a lost case with this phone and don't know what to do because not only can I not figure out how to do this but I also have a mac that cant run a VM because the laptop is from '06.
Click to expand...
Click to collapse
Nandroids would not restore an IMEI, even if you had one and flashed back to it, your IMEI would still be gone. Also, unless you deleted your CWM backups by hand, they are still there. You would just need to reflash CWM to have access to them again. Nandroids are not interchangeable between recoveries.
Unfortunately you would need to use a friend's computer if you don't have a windows machine. If that's not an option, you can try to bring it to the retailer or send it to samsung... You can always flash back to stock and try and say you are having data issues ever since you updated with Kies to JB so they don't void your warranty. Might work?
Whenever you flash a ROM you run the risk of losing your IMEI. If/when you get this sorted out, you should look into making a backup in the event it ever fails again, you can simply flash it back.
i think when you do a factory reset, it erases the backups. I made a nandroid but it was a long time ago.
andymyrick said:
i think when you do a factory reset, it erases the backups. I made a nandroid but it was a long time ago.
Click to expand...
Click to collapse
Factory reset won't remove your backups. I run a factory reset before I flash any ROM and my backups still exist. Please see my above post. I just edited it and has a solution for your nandroid problem at least.
Factory reset does NOT delete backups. It does NOT format internal SD where the backups are stored by default. This is, unless, you specifically told it to format/clear internal SD.
So the long and short is this, buddy: RPelham posted a link that can help you try and recover your IMEI. If you don't have access to a pc, download the latest stock recovery (a thread in the Android dev section) and flash your s3 back to stock for return purposes. There's also a thread in there u believe about removing root. Somebody chip in with more info if you've got it for this guy
See if you can make a phone call.
I can make a phone call if I'm on WiFi but I can't do anything if I'm away from wifi
Sent from my SGH-I747 using xda app-developers app
first, try RPelham's suggestion to try and recovery your IMEI. getting that back and running is the preferred method.
if you decide to return/exchange your s3, follow the suggestion below to reset.
here's a link to a page that details how to setup your phone for return. this page is for the i9300 but i've included the links for i747 to use whenever an i9300 file is requested. after your nandroid restore and initial boot, see what base band you're on to know which modem you might need. read over the link a few times to become familiar and proceed at your own risk.
factory restore page: http://forum.xda-developers.com/showthread.php?t=1721380
i747 stock recovery: http://db.tt/AvISQtPy
i747 modem list: http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
I am having some real issues trying to figure out how to go through this process. Does anybody know of a youtube tutorial or something? Do I need to be on a stock rom in order for this to work? I'm running the Carbon rom currently which is an AOSP rom. I've installed the drivers. I dont know what else to do. I can't get the programs to recognize my phone.
And my IMEI says 0
My IMEI SV says 00 and my mobile network state keeps saying connecting. and my serial number does not match the number under my battery.
andymyrick said:
I am having some real issues trying to figure out how to go through this process. Does anybody know of a youtube tutorial or something? Do I need to be on a stock rom in order for this to work? I'm running the Carbon rom currently which is an AOSP rom. I've installed the drivers. I dont know what else to do. I can't get the programs to recognize my phone.
And my IMEI says 0
My IMEI SV says 00 and my mobile network state keeps saying connecting. and my serial number does not match the number under my battery.
Click to expand...
Click to collapse
Refer to this thread for the fix:
http://forum.xda-developers.com/showthread.php?t=1801997
Quasimodem said:
Refer to this thread for the fix:
http://forum.xda-developers.com/showthread.php?t=1801997
Click to expand...
Click to collapse
I tried using that. but everytime i tried to follow the instructions, my phone didnt get recognized by the software and I don't know why. Also, I don't know what to do since im not running the stock rom and i tried entering the information into the terminal but that also didn't work. All of my drivers are installed properly multiple times over.
andymyrick said:
I tried using that. but everytime i tried to follow the instructions, my phone didnt get recognized by the software and I don't know why. Also, I don't know what to do since im not running the stock rom and i tried entering the information into the terminal but that also didn't work. All of my drivers are installed properly multiple times over.
Click to expand...
Click to collapse
Use the script commands in post #2 for an AOSP ROM
open terminal emulator, give it root with the su command and type:
echo 0 > /sys/class/android_usb/android0/enable 0
echo smd,bam > /sys/class/android_usb/android0/f_rmnet/transports
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo 1 > /sys/class/android_usb/android0/f_acm/instances
echo rmnet,acm,diag > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
Related
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Gandicela said:
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Click to expand...
Click to collapse
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
Mate, firstly this is the hard way of recovering from "Unknown Baseband" issue. Finally the simple solution was only to download and install an app called SELinux Mode Changer from PlayStore. Then using that app, change SELinux from Enforcing to Permissive resolved everything related to IMEI, EFS, and Unknown Baseband. So hard way I did; i didn't know any better then.
By the way the link is correct. Start from the procedure from the line that says "Installation Instruction [Mobile odin is now have support for NOTE2]"
You must be in download mode (Vol Down, Home, & Power button all pressed together) to flash the Stock ROM using Odin. But where is your status now? If in recovery, can you re-install a ROM? If u r able to reboot back up to OMNI, just install the SELinux app and u will be good to go.
Cheers!
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
karlonicolas said:
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Nice, thanks!
For all others that might face "unknown baseband" with 4.3 to 4.4 flashing of ROMS, SELinux Mode Changer app from Playstore will fix that problem. Install the app and set SELinux from Enforcing to Permissive.
i hope your problem is fixed.
i'm not too familiar with CM roms, as i have been using stock since gingerbread. but you have to first do a full wipe before flashing from CM to stock. did you do that? perhaps you can go to recovery, do a full wipe, include Dalvik and Cache. Then go to bootloader and flash your rom.
by the way, my chipset is qualcomm yours may be exynos. if so, then i'm not confident about this solution because i have tried this several times, but only on note 2 LTE.
good luck!
I have a Samsung Galaxy Nexus GSM - I tried updating the CM 11 nightlies and ended up losing my IMEI number. The number defaulted to 04999*. I visited a local mobile service vendor here and got it reprogrammed (not sure how he did it but turns out he had a small box to program it). But now, I was on Android 4.2.1.
I then created an EFS backup using the Team Win Recovery. Now I tried flashing the stable CM 10.2 maguro release from Cyanogenmod but still I see losing my IMEI every time I flash.
Once updated, I tried to restore my EFS from the backup using TWRP but still the IMEI shows the default.
If I restore the entire backup (system/boot/data/efs), the phone rolls back to Phone 4.1.2 and IMEI is restored back.
Please suggest how I can upgrade to CM 10.2 or CM 11 nightlies without losing IMEI
I have gone through many posts on XDA on IMEI and seems like the restore works - Doesn't work for me. Is there any specific format changes in the way EFS partition between 4.1.2 to 4.3?
Or should I update to 4.2.2 factory and then to 4.3 factory and so
Thanks
Ghanashyam
re-plug - none with any solutions?
same boat
I am in the same boat here, no backup in /efs folder /factory or /data/radio
IMEI stuck at the default 0049*
ghanashyamprabhu said:
I have a Samsung Galaxy Nexus GSM - I tried updating the CM 11 nightlies and ended up losing my IMEI number. The number defaulted to 04999*. I visited a local mobile service vendor here and got it reprogrammed (not sure how he did it but turns out he had a small box to program it). But now, I was on Android 4.2.1.
I then created an EFS backup using the Team Win Recovery. Now I tried flashing the stable CM 10.2 maguro release from Cyanogenmod but still I see losing my IMEI every time I flash.
Once updated, I tried to restore my EFS from the backup using TWRP but still the IMEI shows the default.
If I restore the entire backup (system/boot/data/efs), the phone rolls back to Phone 4.1.2 and IMEI is restored back.
Please suggest how I can upgrade to CM 10.2 or CM 11 nightlies without losing IMEI
I have gone through many posts on XDA on IMEI and seems like the restore works - Doesn't work for me. Is there any specific format changes in the way EFS partition between 4.1.2 to 4.3?
Or should I update to 4.2.2 factory and then to 4.3 factory and so
Thanks
Ghanashyam
Click to expand...
Click to collapse
I was going to suggest flashing to 4.2/4.3 before trying to flash it again. Are you on Sprint/Verizon/someone else? I haven't had any issues upgrading to CM 11 nightlies.
You should try and get it repaired at a local mobile service shop. If you are in India, am sure you will find such shops easily.
But I did that and if I try to reflash I lose IMEI again and have to settle with the ROM in the nandroid backup.
Still looking for solutions as to why I lose IMEI when I upgrade to 4.2.2 or 4.3.
Also with the ROM that I got it fixed on, I dont get OTA update as well
Sent from my Galaxy Nexus using xda app-developers app
ghanashyamprabhu said:
You should try and get it repaired at a local mobile service shop. If you are in India, am sure you will find such shops easily.
But I did that and if I try to reflash I lose IMEI again and have to settle with the ROM in the nandroid backup.
Still looking for solutions as to why I lose IMEI when I upgrade to 4.2.2 or 4.3.
Also with the ROM that I got it fixed on, I dont get OTA update as well
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Hi, seen this thread, decided to chime in. You should have this thread (http://forum.xda-developers.com/showthread.php?t=2592480) merged with this one, seems to me they're still about the same thing/goal/trial and error.
Have you tried to fastboot flash 4.2.2 factory images? Sorry if the question is out of sync, still trying to grasp what's happening.
Since that would give you an earlier bootloader version, you could then put your theory to the test and update to 4.3, manually. Android versions/bootloader versions are supposed to be backward compatible (there's some info on google about that, I could track it down if you want/don't want to take my word for it, which would be fine)
After the IMEI repair from the mobile service centre, here are the details on the state of the phone.
Recovery - TWRP touch 2.6.3
Product name tuna
Baseband I9250XXLJ1
Boot Loader version PRIMELC03
Android version 4.2.1.
IMEI is a non-generic one and the mobile connectivity works just fine!
And then I downloaded the factory image for maguro (Galaxy Nexus) takju-jdq39(Android 4.2.2)
On unzipping the download zip, I find the following files
bootloader-maguro-primelc03.img
flash-all.bat ( script to flash everything/ boot loader/ radio and ROM)
flash-all.sh ( shell script to do the same as flash-all.bat)
flash-base.sh (Flashes baseband radio and the boot loader)
image-takju-jdq39.zip (rom image)
radio-maguro-i9250xxlj1.img (radio image)
so instead of using the flash-all.sh, I just tried updating only the ROM using
fastboot -w update image-takju-jdq39.zip
Even on this, when I reboot, I don't see network connectivity and my IMEI is again a generic one.
here' the log that I get when I update using fastboot. Note that its not fastboot flash / instead its just fastboot -w update
http://pastebin.com/2E7cA3P8
The command seems to update recovery, boot and system -
So still not sure what's causing the IMEI to be generic - When I see the /data/radio/log/nv.log it says
nv_data.bin not found
nv_data.bin.md5 not found
default nv restored
Does that ring a bell?
a2f said:
I was going to suggest flashing to 4.2/4.3 before trying to flash it again. Are you on Sprint/Verizon/someone else? I haven't had any issues upgrading to CM 11 nightlies.
Click to expand...
Click to collapse
I had tried that - but what ever update I do, be it 4.2.2 or 4.3 or 4.4(kitkat CM nightly), I still end up with a generic IMEI.
And I bought the phone on Google Store, its a Galaxy Nexus GSM version not tied to Sprint or Verizon. I am using it in India.
Ummm... Do you have a backup from correct efs? I guess you could - *I'm not sure, never tried it myself* - copy those to /factory, and reboot? nv_data is very familiar, I'm sure I've read about it, so let's search more about that before actually trying what I suggested?
I thought you could be suffering from a corrupt partition, and if the partition doesn't get deleted and just formatted, it might cause issues.
beekay201 said:
Ummm... Do you have a backup from correct efs? I guess you could - *I'm not sure, never tried it myself* - copy those to /factory, and reboot? nv_data is very familiar, I'm sure I've read about it, so let's search more about that before actually trying what I suggested?
I thought you could be suffering from a corrupt partition, and if the partition doesn't get deleted and just formatted, it might cause issues.
Click to expand...
Click to collapse
I don't really know who reads the nv_data.bin. Is that the boot loader or the radio.img. I guess who ever reads it, it copies it over from the /factory to /radio. I haven't checked if the nv_data.bin and nv_data.bin.md5 are the same ones between the working ROM and the non-working
will post the result shortly.
So on the working ROM, I checked if the /factory/nv_data.bin and /factory/nv_data.bin.md5 are the same as that of the /data/radio/nv_data.bin and /data/radio/nv_data.bin.md5.
I used the ubuntu dex to diff the hex files and they don't match.
Now, on to flash the non-working ROM and see if anything changes between the working and the non-working ROM in /factory and /radio
So on the working ROM, I checked if the /factory/nv_data.bin and /factory/nv_data.bin.md5 are the same as that of the /data/radio/nv_data.bin and /data/radio/nv_data.bin.md5.
I used the ubuntu dex to diff the hex files and they don't match.
Now, on to flash the non-working ROM and see if anything changes between the working and the non-working ROM in /factory and /radio
First person to help gets paid for your time...
Problem: I have a s3 i747 from att.
it has 4.3 stock.
I use srs to unlock all my phones.
well when I went to unlock this one it said it had new security.
Usually when this happens I odin this file that downgrades the modem.
well I did it and now I have null imei and unknown baseband
I tried restoring to stock, didn't help. Through kies and odin.
I need to put it back the way it was... can someone please help..... ill paypal you as soon as its working again...thanks
So you're currently at stock, unlocked? Does the phone boot at all?
These threads may help:
http://forum.xda-developers.com/showthread.php?t=2658486
http://forum.xda-developers.com/showthread.php?t=2722660
yes it is still stock 4.3. no its not unlocked. everything works and boots fine. just no signal because of null imei and unknown baseband.
I think I need to just flash a modem via odin....I just don't know which one
http://forum.xda-developers.com/showthread.php?t=1831898
There's seems to be a rash of this happening in the past month. You'll probably find that link helpful but first check and see if others found a better solution.
Yes. Flash the 4.3 modem.
As of 4.3, flashing any older modem will no longer work, resulting in an unknown imei and baseband version. Flashing back to the correct modem nearly always solves this issue.
It will be like this from now on btw. You cannot use any modem except the one which matches your current firmware build.
This means our free unlock method no longer works unfortunately. But you can get unlocked for just a few bucks using one of the many services online. I know some are on ebay, but google will find others as well.
I installed cwm and downloaded the modem but im lost from there.
do I rename it update.zip?
Nope, just flash like you would any other rom.
Because you asked about renaming it to update.zip though, I have to ask if you are certain you are in cwm? If you had previously updated via ota it may restore the stock recovery every time you reboot. If this is happening, reflash cwm in Odin, but uncheck auto reboot. Wait until it says PASS, then unplug and pull the battery.
Next put the battery back in and boot to recovery. (Volume up, home, power. Release power only after it vibrates)
If you are sure you are in cwm though, just flash the modem normally.
Yes im sure its cmw. when I open recovery and look for the zip its nowhere to be found. that's why I was asking if I should change the name.
I did try it by changing the name but the file still doesn't show up.
It's an IMEI problem. If you haven't made a backup of the IMEI folder you can't do anything.
Sent from my SM-G900H using XDA Free mobile app
daddydv said:
Yes im sure its cmw. when I open recovery and look for the zip its nowhere to be found. that's why I was asking if I should change the name.
I did try it by changing the name but the file still doesn't show up.
Click to expand...
Click to collapse
Make sure the sdcard is mounted. Have you tried getting to it on both internal and external cards?
Thin_Bezel said:
It's an IMEI problem. If you haven't made a backup of the IMEI folder you can't do anything.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
Not true. 90% of unknown baseband and imei problems ive helped people with lately just needed the correct modem. And even if it were the imei, I can still help with that. Im convinced in this case its just the modem though.
Thanks doc... that was the problem...imei and baseband are back. donation has been sent....thanks again.
Hey thanks man! I do appreciate it, but I am just glad I could help! I will definitely put it to good use though! (Broke the lcd on my S3 a while back and haven't had the disposable funds to fix it. Something always comes up...lol!) Will be adding it to my savings for this purpose!
Anyway, since we were slightly on the IMEI topic, there is a backup you should do if you haven't already. (Root is required for this to work though.)
Its super simple and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
DocHoliday77 said:
Hey thanks man! I do appreciate it, but I am just glad I could help! I will definitely put it to good use though! (Broke the lcd on my S3 a while back and haven't had the disposable funds to fix it. Something always comes up...lol!) Will be adding it to my savings for this purpose!
Anyway, since we were slightly on the IMEI topic, there is a backup you should do if you haven't already. (Root is required for this to work though.)
Its super simple and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
You can also use qpst to backup imei. Windows app. Free. Lots of walkthroughs around for those less comfortable with cli.
Nvm. 10char
azuziel said:
You can also use qpst to backup imei. Windows app. Free. Lots of walkthroughs around for those less comfortable with cli.
Click to expand...
Click to collapse
I know, I already have it and have used it and other tools to help fix at least 700-800 S3's, probably more! (No, i do not charge for my help either.) I dont tell about it or give it out unless its absolutely needed for a legitimate imei restore though. Too many people try to use it illegally and Im not willing to take the chance. Its the main reason most of the info has been deleted from everywhere. Only a few threads here and there get by the mods it seems.
Anyway, to my knowledge, no one who has run this backup has ever lost their IMEI. It even seems to help for those occasions after flashing a cm rom where the imei displays "unknown". (Apparently, at least on the T999, cm sometimes has problems reading the nv data. If rebooting several times doesnt solve, stock firmware does).
At this point I believe if you run this backup, you will have no need for a .qcn or .txt file backup, which is why I just dont mention it anymore. And if it does happen, people can pm me and ill be happy to help fix it.
Because of how I understand this backup to function, I do believe if it had been run during first boot, we would've never seen so many imei problems to begin with! I just dont understand why Samsung refuses to do this!
Anyway, that's why I dont mention those tools anymore. If you have any questions about any of it, please feel free to PM me and ill try to explain better.
Hi,
Can a modem/hardware be damaged by a rom? Are there files that can get corrupted and left behind after a wipe/reinstall that would cause this...
Rogers Optimus G e975, 2 years old, out of warranty, decided to root and install KitKat.. Went well, worked fine with aosp_geeb-kitkat-4.4.houstonn-v3. Decided to try different rom, loaded "E975 official update Kitkat 4.4.2 V20A" from this site (following instructions posted with it). Loaded fine, but after first text message mobile network went to constantly searching, then periodically a red 'x'. Wiped and reinstalled previously working aosp build, but modem/radio remained inoperative. Then installed factory KDZ back to Jellybean. Still same problem until I took phone with me somewhere, and I was able to get a signal, but it was real spotty and kept disconnecting where I used to get good signal..
Thanks for looking.
Check Ur IMEI. Do u have EFS Backup?
same here
i am having the same problem
Yes I have a efs backup folder with 3 img files in it that I made sure to copy elsewhere. I did restore them but that didnt seem to make a difference.
tredmill said:
Yes I have a efs backup folder with 3 img files in it that I made sure to copy elsewhere. I did restore them but that didnt seem to make a difference.
Click to expand...
Click to collapse
Factory reset Clear Cache. Clear Dalvik..
Flashing Stock again also helps sometimes
Murshad007 said:
Factory reset Clear Cache. Clear Dalvik..
Flashing Stock again also helps sometimes
Click to expand...
Click to collapse
Thanks. Done that a couple times. The IMEI number and all that shows correctly up in the Settings>About menu.