[Q] SIM Card Not Recognized after Install - T-Mobile Samsung Galaxy Note II

Similar to http://forum.xda-developers.com/showthread.php?t=2375050 (except I made an efs backup), my SIM card is no longer recognized. Backed up everything using default Clockwork Mod recovery settings 6.0.3 on Wind T889v.
I installed roms in this order:
http://forum.xda-developers.com/showthread.php?t=2675066
http://forum.xda-developers.com/showthread.php?t=2488986
Of course, I noticed the SIM card was no longer being recognized upon installing Slim
In the past GT-N700 ROMs for T0LTE have worked fine. I was running BeanStalk 4.4.2 W0etweaks with working phone and sim card. The issue occured when installing.
As if my phone had not detected a SIM card, phone number, IMIE SV, and IMIE show up as "uknown".
I am not too sure how to proceed? Ideas?

I've had similar issues with some versions of TWRP where flashing an Omni 4.4 nightly would leave me with no signal and an unknown IMEI. Flashing the very same ROM with CWM would work. (Odd, I know.)
FWIW I just flashed the latest t0lte Omni nightly with TWRP t0lte 2.7.0.0 earlier today and everything's been fine.
Another thing to look into is SELinux and making sure it is set to permissive.

Darkshado said:
I've had similar issues with some versions of TWRP where flashing an Omni 4.4 nightly would leave me with no signal and an unknown IMEI. Flashing the very same ROM with CWM would work. (Odd, I know.)
FWIW I just flashed the latest t0lte Omni nightly with TWRP t0lte 2.7.0.0 earlier today and everything's been fine.
Another thing to look into is SELinux and making sure it is set to permissive.
Click to expand...
Click to collapse
Tried with CWM 6.0.3 with no luck. Tried with Phiz Touch 6.07.9-t0lte, and no luck as well. I will try TWRP t0ltecan 2.7.0 shortly. Which version of CWM did you get it to work with?
Tried setting SELinux to permissive via https://play.google.com/store/apps/details?id=com.mrbimc.selinux, but it made no difference. Am I supposed to do something after I set it to permissive?

TWRP 2.6.0 Will Not Work
ForgottenSolstace said:
Tried with CWM 6.0.3 with no luck. Tried with Phiz Touch 6.07.9-t0lte, and no luck as well. I will try TWRP t0ltecan 2.7.0 shortly. Which version of CWM did you get it to work with?
Tried setting SELinux to permissive via https://play.google.com/store/apps/details?id=com.mrbimc.selinux, but it made no difference. Am I supposed to do something after I set it to permissive?
Click to expand...
Click to collapse
I was not able to install TWRP t0ltecan 2.7.0, but I was able to install TWRP t0lte 2.6.0. And the installation, along with any other 4.4 ROM fails with the following error:
Code:
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/external...
Error flashing zip 'external_sdcard/omni-4.4.2..
I will try other ROMs with CWM 6.0.3 and Philz TouchWiz. Hopefully, I will figure something out...

Could this be the same problem?
Hmm... I've been troubleshooting different ROMs with no luck. But could this be the solution? http://forum.xda-developers.com/showthread.php?t=1970338

Fixed My Phone!
ForgottenSolstace said:
Hmm... I've been troubleshooting different ROMs with no luck. But could this be the solution? http://forum.xda-developers.com/showthread.php?t=1970338
Click to expand...
Click to collapse
Indeed, I had to flash my modem. For users like me, of the T889V, download the modem from http://androtransfer.com/?developer=cmenard&folder=SGH-T889 and flash the file using the recovery of your choice (I used TeamWin 2.7.0). Note that you will need to install openrecovery-twrp-2.7.0.0-t0lte.zip (and not the can version openrecovery-twrp-2.7.0.0-t0ltecan.zip, as that version will not install). You can flash your modem at any time, and it will not affect your current ROM. You don't need to clear dalvik cache, cache, or do a factory reset; just flash the modem file.
This problem occurs because you try to install a ROM that's not for your phone. So in my case, OmniRom included a modem not for my version (international). Because the modem is normally not included in ROM packages, it doesn't matter which ROM you install. To get back to a working state, you need to flash your original modem.
Hopefully this helps someone.

Uhh... not really
ForgottenSolstace said:
Indeed, I had to flash my modem. For users like me, of the T889V, download the modem from http://androtransfer.com/?developer=cmenard&folder=SGH-T889 and flash the file using the recovery of your choice (I used TeamWin 2.7.0). Note that you will need to install openrecovery-twrp-2.7.0.0-t0lte.zip (and not the can version openrecovery-twrp-2.7.0.0-t0ltecan.zip, as that version will not install). You can flash your modem at any time, and it will not affect your current ROM. You don't need to clear dalvik cache, cache, or do a factory reset; just flash the modem file.
This problem occurs because you try to install a ROM that's not for your phone. So in my case, OmniRom included a modem not for my version (international). Because the modem is normally not included in ROM packages, it doesn't matter which ROM you install. To get back to a working state, you need to flash your original modem.
Hopefully this helps someone.
Click to expand...
Click to collapse
Well, turns out I was wrong. I'm back at where I started. Somehow, after rebooting once with the new ROM, I started getting the exact same problem with no service and unknown IME.
Tried flashing the modem with no luck.
Is there a reason why this would only work for the first time? Is it possible that I installed an app that caused this problem?
Will update if I find any solutions...

ForgottenSolstace said:
Well, turns out I was wrong. I'm back at where I started. Somehow, after rebooting once with the new ROM, I started getting the exact same problem with no service and unknown IME.
Tried flashing the modem with no luck.
Is there a reason why this would only work for the first time? Is it possible that I installed an app that caused this problem?
Will update if I find any solutions...
Click to expand...
Click to collapse
have you tried selinux mode changer? you may try devil or agni kernel also

You could try to Odin back to your device's stock rom. Which ever version is appropriate for your bootloader.
Hastily spouted for your befuddlement

Coug76 said:
You could try to Odin back to your device's stock rom. Which ever version is appropriate for your bootloader.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Tried flashing stock via Kies. Still the same problem.
Also, ran into this video: https://www.youtube.com/watch?v=Pai4BH3AWq8 but on Stock, there was no option 6 or way to see FTM.
On custom 4.4 roms, you get the "Mobile Network not Available" when trying to fix null IMEI (update: IMEI shows up as null/null).
Any help would be appreciated.

ForgottenSolstace said:
Tried flashing stock via Kies. Still the same problem.
Also, ran into this video: https://www.youtube.com/watch?v=Pai4BH3AWq8 but on Stock, there was no option 6 or way to see FTM.
On custom 4.4 roms, you get the "Mobile Network not Available" when trying to fix null IMEI (update: IMEI shows up as null/null).
Any help would be appreciated.
Click to expand...
Click to collapse
Did you do the emergency recovery in Kies?
Hastily spouted for your befuddlement

Coug76 said:
Did you do the emergency recovery in Kies?
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Yes.

The Modem Likely Burned
After a long week of research, I believe I determined the cause of the issue: when I flashed the Slim Rom, it burned out my modem on my motherboard, as the ROM was not built for my Note variant (T889v). I spoke to a repair technician in my local area, and he was quite certain that my modem had been damaged (likely burned) from the unsupported ROM installation. He was very familiar with such a scenario. It means you have to replace your phone if you want to be able to use your SIM card, make calls, use data, etc..
The modem consists of small transistors (radio, and other communication parts). Even if you take apart your phone, you won't be able to see burn marks. The only way to be *somewhat* sure this is the case is to try recovering your EFS partition to an earlier point when your phone was working. Luckily for me, I had this. I also had a modem backup. Both failed. If all of this, and flashing stock fail, you've got a hardware issue.
This means you're out of luck if you want to send your phone in for repair; Samsung will know from that (corrupt) data in the modem that you broke your phone from flashing a custom ROM. So it doesn't matter if you triangle away or flash stock -- you're out of luck if you have a warranty. You will be charged the retail value of your phone + shipping, so you're probably better off selling your phone for parts.
It's a sad day for me, but a dawn for new days where I will make SURE that my phone's model is supported.
Let this be a cautionary tale for you as well.

ForgottenSolstace said:
After a long week of research, I believe I determined the cause of the issue: when I flashed the Slim Rom, it burned out my modem on my motherboard, as the ROM was not built for my Note variant (T889v). I spoke to a repair technician in my local area, and he was quite certain that my modem had been damaged (likely burned) from the unsupported ROM installation. He was very familiar with such a scenario. It means you have to replace your phone if you want to be able to use your SIM card, make calls, use data, etc..
The modem consists of small transistors (radio, and other communication parts). Even if you take apart your phone, you won't be able to see burn marks. The only way to be *somewhat* sure this is the case is to try recovering your EFS partition to an earlier point when your phone was working. Luckily for me, I had this. I also had a modem backup. Both failed. If all of this, and flashing stock fail, you've got a hardware issue.
This means you're out of luck if you want to send your phone in for repair; Samsung will know from that (corrupt) data in the modem that you broke your phone from flashing a custom ROM. So it doesn't matter if you triangle away or flash stock -- you're out of luck if you have a warranty. You will be charged the retail value of your phone + shipping, so you're probably better off selling your phone for parts.
It's a sad day for me, but a dawn for new days where I will make SURE that my phone's model is supported.
Let this be a cautionary tale for you as well.
Click to expand...
Click to collapse
why would they know? flashing the stock upgrade flashes a modem as well. could just as easy be a bad upgrade. if you don't tell them they wont know
also what slimrom did you download that did this? sorry I just reread the OP. Neither of the roms you mentioned would do that to your phone. I have flashed many roms from both of those devices and never had an issue.
---------- Post added at 10:32 AM ---------- Previous post was at 10:16 AM ----------
flash the appropriate rom in recovery and tell if it works
http://forum.xda-developers.com/showthread.php?t=2554226

mattlowry said:
why would they know? flashing the stock upgrade flashes a modem as well. could just as easy be a bad upgrade. if you don't tell them they wont know
also what slimrom did you download that did this? sorry I just reread the OP. Neither of the roms you mentioned would do that to your phone. I have flashed many roms from both of those devices and never had an issue.
---------- Post added at 10:32 AM ---------- Previous post was at 10:16 AM ----------
flash the appropriate rom in recovery and tell if it works
http://forum.xda-developers.com/showthread.php?t=2554226
Click to expand...
Click to collapse
I doubt it was a bad upgrade, as I've tried everything possible to fix my phone. Recovering EFS partition, flashing stock with Kies, recovering modem, flashing the original ROM that worked earlier... nothing fixed it.
The problem occurred immediately after installing Slim. Then, any rom I installed after that did not solve my problem.
Pretty sure it's a hardware problem.

Related

[Q] No ROMs taking, keep getting no MD5 message, phone close to bricked.

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?

[Q] No Network or IMEI number, :-S

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!

Hardbricked S3, would like to verify options

Hi,
I'm fully aware of how silly it is to be in this situation. I opened a thread thinking it was in the T-Mobile S3 forum and flashed the downloaded ROM. But regardless, I made an unfortunate mistake.
The ROM was Stockdroid 4.4.2 from the i9300 forum on this site. My phone is a T999v S3. Before beginning any flashing, I rooted and ran Odin to install Philz Touch 6 recovery and "T999VVLUEML2_T999VYVLEML2_T999VVLUEML2_HOME.tar.md5". I was bouncing around firmwares looking for something that could fix the "Camera Failed" error (front camera works when charging but not anywhere else, any advice on that would be greatly appreciated), and I guess I lost track of exactly what I was downloading.
Anyway, after flashing the ROM the phone will not boot, and is almost completely unresponsive. The only life I can get out of it is when I connect it to the computer before taking the battery out, then putting it back in. A red light will shine at some point during that. In device manager the S3 is listed as QHSUSB_DLOAD. This leads me to think I can make use of one of the debricking tutorials on this site for the t999v.
The phone is a 16gb model, but I don't have a 16gb card. Before I go out and buy it, I want to know if buying it should solve the problem. I've read the debrick solution will not work with a 2gb card, but I tried anyway with no luck.
If it does work, great. If not, is my only other solution sending the device in for JTAG?
Thanks in advance for any and all help. I know this problem has been an impossible amount of times, but I wanted to pose the issue specifying the exact scenario I'm dealing with.
Yes the De-Brick thread under Developement will/should work. Make sure there is an image for your variant on that thread, before you buy the SD Card.
Once you successfully De-Brick, I will help with the Camera issue. Its pretty easy to fix in most cases.
Great, thank you!
I'll get back today on whether or not the method ends up working. The debrick image I've been using on my 4.4.2 T999v (on Windmobile) was from this thread:
http://forum.xda-developers.com/showthread.php?t=2439367
As for the Camera issue, should I start a new thread, or can I go ahead and post here?
That's correct thread for your Image. Just be sure you grab for T999V. There are other T-Mo variants too.
For the Camera, continue here when done De-Bricking.
Hi, I just got back and loaded the image on a 32GB microsd. The phone booted up just fine!
I followed the rest of the guide and attempted to reinstall the "T999VVLUEML2_T999VYVLEML2_T999VVLUEML2_HOME.tar.md5" file using ODIN, but it failed during the process. What do I do from here? I would like to be able to use the phone without the 32gb card being taken up like this. Should I try installing a 4.3 ROM of some sort?
Edit: Tried it again and the flash was successful. Just about to install a recovery image, but assuming the install went well I'm guessing I am brick-free? Thank you for the help, Perseus71.
I'll update my post if I run into any other problems regarding the brick, but for now what should I be doing with the camera issue?
I've tinkered a bit with the camera firmware with no luck, and have flashed 4.3 stock again with no luck. What should I do to resolve this issue?
Good to have it back from Brick.
As to Camera, do you still see the Camera Failed issue ? Particularly on the Stock Camera from the 4.3 you just flashed ?
DO NOT use 3rd Party Camera apps until this issue is resolved.
Perseus71 said:
Good to have it back from Brick.
As to Camera, do you still see the Camera Failed issue ? Particularly on the Stock Camera from the 4.3 you just flashed ?
DO NOT use 3rd Party Camera apps until this issue is resolved.
Click to expand...
Click to collapse
Good to know, I'll refrain from using third party camera apps. And even after flashing the above firmware it says Camera Failed.
The problem started on stock 4.3 before any ROM installing/rooting occurred. I tried the obvious clearing app cache, factory reset and wiping dalvik cache, but no luck. Since then I've been installing different ROMs and Camera Firmwares (ZDFE02, ZDFI02, etc), and moving around and setting permissions for SlimISP bin files. I know the rear works when it's being charged, and that the front camera works just fine. I just don't know what I can do to get it working. I've read that replacing the camera itself may not even fix the problem.
Yes I'd say wrong firmware is the Cause. Typically when you do Factory Reset, wipe /data and then Flash the complete firmware image in Odin, it should work. Usually it will contain the correct firmware.
So even though you flashed the image as part of De-Brick process, I suggest do the Odin Flash again. Make sure to do Factory Reset first. When finished, boot to Stock Recovery and wipe Dalvik and Cache.
When phone boots, try Camera by itself before you enter your Google account.
Perseus71 said:
Yes I'd say wrong firmware is the Cause. Typically when you do Factory Reset, wipe /data and then Flash the complete firmware image in Odin, it should work. Usually it will contain the correct firmware.
So even though you flashed the image as part of De-Brick process, I suggest do the Odin Flash again. Make sure to do Factory Reset first. When finished, boot to Stock Recovery and wipe Dalvik and Cache.
When phone boots, try Camera by itself before you enter your Google account.
Click to expand...
Click to collapse
Alright. I flashed the 4.3 image mentioned above with Odin, no problems there. Before flashing I did a dalvik/cache wipe and Factory Reset. When finished, I booted to Stock Recovery, but there was only an option to wipe Cache. Instead I opted to both wipe Cache and do another Factory Reset.
Unfortunately I booted the phone up again, skipping the connect to Internet and Google options, and went directly for the Camera App. I still receive the Camera Failed error.
What should I do from here? Does this mean the Camera itself is faulty? And will replacing it actually solve the problem (or could it be a mainboard issue)?
Also the Camera Firmwares currently on are as follows:
Rear
Camera - ZDFE02
Phone - ZDFI02
Front
Camera & Phone - S5K6A3
Probably a firmware issue, but could be hardware. ZDFE02 is the version your rear cam is currently using. ZDFI02 is what is included with the firmware build you are currently on. Back on ICS, we could update this ourselves, but Samsung has since locked that down. If you could find a way to write the newer version from Phone to Cam it might help, but i don't know of any way to do this anymore.
You said you've been installing different roms and cam firmwares. How were you going about that?
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
Probably a firmware issue, but could be hardware. ZDFE02 is the version your rear cam is currently using. ZDFI02 is what is included with the firmware build you are currently on. Back on ICS, we could update this ourselves, but Samsung has since locked that down. If you could find a way to write the newer version from Phone to Cam it might help, but i don't know of any way to do this anymore.
You said you've been installing different roms and cam firmwares. How were you going about that?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
For ROMs I would simply boot into a custom recovery and flash them, along with kernels, heeding any warning signs in threads. I wouldn't run into any errors, and could swap between 4.3 and 4.4.2 without issues. I didn't extensively test out the ROMs, but it seemed fine.
For Camera Firmware, on a StockMOD 4.3 ROM I dialed *#34971539# to get into the CameraFirmware menu. From there I could write new firmware depending on the SlimISP bin file transferred to the internal root. I can't remember thinking back if the Camera firmware actually changed when I did this, but the Phone firmware did (or maybe vice versa, I'll try again -- I know there was a change after writing).
So I do remember reading you can't downgrade lower than 4.3, that must be true then? If I could go down to ICS I could force the Camera Firmware to change?
What's the target Camera Firmware here? Does it need to be the same as the Phone Firmware (i.e. ZDFI02)?
ZDFI02 is newer. You'd need to do the Phone to Cam F/W Write operation.
I also wondering if maybe the files in /system/etc/cameradata folder are the wrong ones. Been a while, but I think that's where you should find some camera files that should match the name if the firmware versions mentioned above.
Maybe some one can confirm this....
I not sure if you flash an ICS rom if it'll work. Might be worth a shot though.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
ZDFI02 is newer. You'd need to do the Phone to Cam F/W Write operation.
I also wondering if maybe the files in /system/etc/cameradata folder are the wrong ones. Been a while, but I think that's where you should find some camera files that should match the name if the firmware versions mentioned above.
Maybe some one can confirm this....
I not sure if you flash an ICS rom if it'll work. Might be worth a shot though.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Could I use the ZDFI02 firmware from this thread?
http://forum.xda-developers.com/galaxy-s3/general/jb-4-1-2-camera-driver-t2006128
I'll find a way to get the Camera Firmware to ZDFI02 and get back to your both.
I going to guess that using that would be ok, but I cannot say for sure since it is for the I9300, which is a very different device from ours.
Sent from my SM-N900T using Tapatalk
Well, I loaded StockMOD 4.3 back on, and while it enables me to write Camera Firmware (no longer greyed out), the Camera Firmware will not change from ZDFE02 to ZDFI02. Do you have any suggestions as to what I can do to get around this? Will downgrading to ICS lead me to another brick?
It shouldn't brick. Can't think of any reason it would. Stability might be more of an issue though.
Sent from my SM-N900T using Tapatalk
Alright, I've loaded on a 4.0.4 ICS ROM. When I input the *#34971539# code, I get the error "Unfortunately factory test has stopped."
Now that an ICS ROM has been loaded, what is the method for flashing the ZDFI02 firmware to CAM?
It was using the dialer code. I guess that since it's an ICS app trying to make changes to your 4.3 firmware it's running into compatibility issues. It sounds like you are doing it correctly, just the versions must be too far apart....apologies for putting you through the hassle of doing all that. It was the best thing I could think to try though. If I think of any other ideas I will certainly let you know. There might be a way to load it using terminal emulator, but I've no idea how you would go about that.
Only other thing would be to try and edit the code of the Factory Test app on 4.3 to enable the Phone to Cam F/W Write option. I had looked into it briefly back on 4.1.2, but Im too much of a novice when it comes to java. I'd still love to know if it's even possible though. We were able to enable JB camera features before the official release by doing the F/W write, so you never know when that could happen again!
Sent from my SM-N900T using Tapatalk
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
It's another sort of shot in the dark, but you could try replacing the camera module. Find a YouTube video showing the S3 disassembly, it really not that difficult, and you can find the camera module online fairly cheap.
Sent from my SM-N900T using Tapatalk
t999
hi friends
my s3 sgh-T999 is bricked:crying:
i can access downloading mode but when i try to put phone in recovery mode phone just show robot logo for a second then restart
i tried every solutions(flash recovery,flash stock or any other roms and ...) here but nothing changed
sometime phone boot and some chines words appear with one button !!
*odin 307 detect phone
http://forum.xda-developers.com/attachment.php?attachmentid=2668840&stc=1&d=1396652278
thanks
If you can get in download mode and it is seen by odin, flash the latest firmware.
Sent from my SM-N900T using Tapatalk

Flashing a New ROM, Get an Incompatible Baseband Version Error?

Warning: This post is long, and probably full of grammatical errors due to my writing it late at night. a TL;DR is included at the bottom, but to fully understand my problem, I encourage you to read the whole post.
Hello, xdadevelopers community. I really need your help. So, recently I learned how to install custom ROMs myself and the experience has been really informative but also very struggling. To make a rather long story short, I bought a used G3 from my friend, had him root it, put a custom ROM on it, and everything was working fine. Only, that ROM was on Android 5.1.1, which was contemporary to when it was flashed. I wanted 6.0.1, so I went about getting it. I eventually got that up and running with Resurrection Remix, but the battery life was completely awful. Idle is okay, but using the device results in completely intolerable battery life. I asked Reddit what to do, and someone recommend crDroid for it's great battery life. I attempted to install that, and that's where I got the problems discussed in this post.
Post where I got the ROM and GApps from
Specific ROM and GApps I got:
- crdroid-6.0.1-20160118-vs985
- So I go the one for Android 6.0.1, and the most recent one at that, last updated on the 18th of January, for my G3 model the vs985
- for GApps, I selected "ARM", "6.0", and "Stock" from the menu
Could another problem be that the ROM is 6.0.1, and the GApps are 6.0? If so, open GApps version exists of 6.0.1.
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally. I navigated to the ROM folder it was located it, selected it, and swiped to flash the ROM. I got the following in response:
Installing '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Checking for BASEBAND version 35B
ERROR: It appears you are running an unsupported baseband. assert failed: h3.verify_baseband("35B:MPSS.DI.2.0.1.c1.13.4-00005") == "1"
E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Error flashing zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
So basically it failed to flash, apparently because of both an unsupported baseband version and a failure to execute a certain binary. Well, if you know how to fix the executing issue, that'd be great, although that's now what I'm focusing on here. I'm focusing on the baseband, because I believe that may be causing the failure to execute (although, as a newbie, I'm not sure if that's actually true). Apparently it was looking for version 35B, and that's not what I was running. When I set up my current ROM again just to be able to use the device, and checked for the baseband verion, it simply says "Unknown". Also, if you check out that link to the post above, it says:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
. Well, I never installed a custom kernel, but I assume my friend did, because when looking at the kernel version on my phone it says:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
.
I'm assuming if it was a non-custom kernel it would just have multiple numbers separated by periods, not have all that info, and it specifically says "CM" in there, so I assume that should work, but am not for certain.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
So that's it. I realize this post is incredibly long but feel like if it was shorter, potentially important information would be nixed. I have a TL;DR below for your convenience, but as I just said, to get all the important information, read everything above, please.
TL;DR:
Tried to install a new ROM
Failed
Failing apparently due to unsuppported baseband version
I can't determine my baseband version b/c my settings app returns "Unknown""
If baseband is unsupported, how do I know which are?
Also apparently "E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip' " is a thing. Caused by unsupported baseband version or entirely different problem all together?
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Please read the whole post to get all the detail needed.
NeatAndClean,
Thank you for providing the detailed information in this thread, so let's get to business.
First thing I want to straighten out is that you said your Baseband Version says "Unknown", i think you should check your IMEI information, if your IMEI is "null" then there is another problem to fix first.
If you have tried restoring from a backup after the "Baseband Unkown" issue and the Baseband Version still says "Unknown", then something happened whilst, or after you tried flashing CrDroid. At this moment I am not so knowledgeable about how to fix the Unkown Baseband issue, but it is a well known problem and usually coincides with the IMEI "null" issue. If you still are having that problem, I will try to find out how to fix it.
However, I will provide you with my full answer so this can hopefully get fixed at your preferred pace.
To start out, my questions are:
1. What ROM/Version of that ROM are you running right now? (I assume it is Resurrection Remix 6.0.1?)
2. Do you have a backup before trying to flash CrDroid? If so, I would suggest restoring from your backup to fix your "Settings Unkown" issue.
Once your Baseband "Unknown" problem is fixed, you can continue on to flash CrDroid (This time, it should work). Now I just downloaded the CrDroid zip file, that you used, on my PC. And just from opening it I can already tell that it is deeply based on CyanogenMod, but with some tweaks to make it CrDroid. Reason I mention this is because of this quote:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
I'm not super knowledgeable on downloading Custom Kernels, but i do know that your Kernel:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
is (I'm 99%sure) a CyanogenMod Custom Kernel, which comes when you flash a CM ROM.
Mine is:
3.4.0-CM-gc6520f1
[email protected] #1
Click to expand...
Click to collapse
and I'm running CyanogenMod 13, 6.0.1 on my vs985. Point is, you should be all set to flash CrDroid based on your Kernel.
Now, the "Unsupported Baseband" issue when flashing, at least CM based ROMs, is a known error recently. (In the past year I'd say) So the very common way to get around this, without having any issues, is to:
1. Go into your downloaded ROM zip, the zip you wish to flash, in your case it's crdroid-6.0.1-20160118-vs985.zip.
2. Extract the files into a folder (I'd recommend naming the folder the name of the .zip file, for ease in the end)
3. Open the extracted files folder
4. Open "META-INF" ==> "com" ==> "google" ==> "android"
5. Within that "android" folder, open "updater-script" file with Notepad, or a similar text editor.
6. Delete this line of code:
assert(getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "vs985" || getprop("ro.build.product") == "vs985" || abort("This package is for device: g3,vs985; this device is " + getprop("ro.product.device") + ".");
assert(g3.verify_baseband("35B:MPSS.DI.2.0.1.C1.13.4-00005") == "1");
Click to expand...
Click to collapse
7. You should be left with "ui_print("Target: lge/g3_vzw....." in your case.
8. Overwrite the edited "updater-script" back to it's directory (the android folder)
9. (Make sure you don't save it as a .txt file, it should still be a "File" (no extension))
10. Now go back to the "crdroid-6.0.1-20160118-vs985" folder after editing and saving "updater-script"
11. Select all the files/folders within, and add them to a .zip archive (Recommended by using WinRar)
12. You should end up with a .zip file visually identical to the original crdroid-6.0.1-20160118-vs985.zip, except this one has the edited "updater-script"
13. The edited one^ is the only one you need now, and is the one you will be flashing
14. Also, if you're curious I have done this many times with CyanogenMod, on vs985, and can assure you nothing bad will come of this... I assume the same is with CrDroid as it is deeply based on CM. (As long as you're "Unknown Baseband" problem has been fixed.
This procedure essentially gets rid of the Baseband/Model Check, ensuring a successful flash. Also as you can see in the code, it checks for the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Baseband/Modem version, I believe "xdabbed" makes a flashable version of the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Modem, which should eliminate the need to edit the updater-script. However, I strongly recommend to do the "updater-script" fix rather than trying to flash a different Baseband, as I have heard flashing a new Baseband can easily brick your phone, and you really do not need to do it.
I have Baseband: MPSS.DI.2.0.1.c1.13-00008, which does not match the "Baseband Check" and my ROM still works like a charm after the updater-script fix.
However, before you flash the edited crdroid-6.0.1-20160118-vs985.zip with your TWRP seperately, with the Marshmallow (6.x) ROMs right now, if you plan on using GApps you need to flash the ROM AND the GApps file at the same time in your custom recovery. Otherwise you will most likely get errors and you will need to re-flash the ROM and GApps.
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Click to expand...
Click to collapse
To answer this, no it is not a problem, you were correct.
1. The LG G3 is an ARM device
2. GApps only uses the first two digits in the OS version (i.e. 5.0.x or 6.0.x) (<==That "x" variable is the third digit in the OS version, and does not matter in GApps
3. All in all you have the correct version of GApps, no you just need to flash it at the same time as your edited ROM.
The procedure you did to flash the ROM was all good:
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally
Click to expand...
Click to collapse
This is great, again the reason it didn't work was because of the mismatch in the Baseband Check, which shouldn't persist after following the instructions in the "updater-script" fix.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
Click to expand...
Click to collapse
1. The Baseband Version is not supposed to state "Unknown", as i said in the beginning, this is a problem that happens sometimes, I am not sure why, or exactly how to fix it, but if you do some research I'm sure you will find something, I will also do some research so I can try to help you with that if it is not fixed by a Factory Reset or a Restore from Backup
2. The Baseband Version that a specific ROM calls for will be in that "updater-script" I was talking about, at least that's how it is for CyanogenMod based ROMs. I think your stock Baseband Version will work with any custom ROM, as long as it is a ROM made for your specific phone. That being said, I do think that the latest Baseband Version for your specific phone does improve Network, Cellular and GPS Connectivity, but again I do not recommend venturing there yet, until you have alot of background on it and can do it safely.
3. If the ROM you intend to flash doesn't support your Baseband, chances are the ROM is not made for your phone or you somehow have a Custom Baseband that is not made for your phone. I say that because even though you get that Baseband error when flashing CM based ROM, it is still supported, it's just that you do not have the "latest" Baseband Version I believe.
I do believe I have answered all of your questions, at least I hope so. I'm sorry that some things I could not answer in great detail, but I tried my best so that you could continue on enjoying your device. I also have the VS985 so I'm familiar with the device.
Summary:
1. Before anything try to Restore from Backup to fix the Baseband "Unknown" issue, as fixing this is priority. If that does not work I will try to find a fix online, or you can try to beat me to it.
2. Once that is fixed^ you can carry on with the "updater-script" fix i included.
3. Then flash the edited ROM and your 6.0, ARM OpenGApps at the same time (one right after another, without a Reboot in between)
4. Then you should honestly be all set
5. Your Kernel is all set for CrDroid
6. The GApps you said you downloaded is all good for the CrDroid version you downloaded
7. You could also try to flash back to vs985 stock (10B) this will hopefully give you your Baseband back if you still need it after Restoring from Backup
7. You should get no errors now! Yay. Now you can enjoy a Battery Optimized beautiful Marshmallow ROM
Click to expand...
Click to collapse
Please let me know if you have any confusion, I would be happy to provide you with clarification, screenshots etc.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Edit: I'm not sure if Fastboot is actually working. I can't get it to do anything. It just hangs on whatever command I give it, and it continues to hang until I unplug USB, then fails.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Click to expand...
Click to collapse
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: forum.xda-developers.com/showthread.php?t=2785089 - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Edit: Sorry, I didn't reach 10 posts yet, so you gotta drag 'n drop the links
Williquah said:
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot http://forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
http://http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: http://lgflashtool.net/index.php/tot-method/ - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Click to expand...
Click to collapse
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
---------- Post added at 09:09 AM ---------- Previous post was at 08:37 AM ----------
Knux Kitsune said:
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Knux Kitsune said:
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Click to expand...
Click to collapse
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Williquah said:
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Click to expand...
Click to collapse
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
*Solution*
Knux Kitsune said:
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
Click to expand...
Click to collapse
Awesome, well that's good that you eventually reached your goal. I can't say for sure why your connection was unstable on the Stock Kit Kat, but the 35B baseband is for 35B (5.1.1) Lollipop. The TOT method flashes back Stock Firmware, which is 10B (I believe 4.2.2) - KitKat so you would then need the Stock Modem IMG: (10B Modem File) but you are past that.. which is great. The Phone Service not responding is, I'm sure, a result of the incompatible 35B Modem mixing with 10B (4.2.2) Software Version. That's why flashing XDABBEB's Stock ROM fixed it (at least the second time around), because it includes all the stock IMGs, including the stock Baseband Version (10B).
But I'm so glad that you re-flashed and wiped again, because you have literally managed to return it to complete stock. Your baseband is official, and seems to me.. completely fixed!
Just confused with this:
It seems to run faster on Marshmallow than it did on Lollipop.
Click to expand...
Click to collapse
Are you running Marshmallow now? Or Kit Kat? I think I just lost you at some point haha.
But congrats on fully flipping your situation around! And in fact, because you fixed your Baseband issue, this thread is now completely answered! :good:
The TOT Method does wonders, doesn't it :victory:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Knux Kitsune said:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Click to expand...
Click to collapse
Ohhh, I see. I totally agree with you, it really makes no sense... the phone was built a certain way, it was meant to be used like that. Why the providers "nerf" them, I don't know. Even with the FM radio, they disable the receiver on the phones, I assume so that we are forced to stream instead, and they make more money. It's absolute sh**. But yeah, alright well that's cool, I might have to flash that myself actually, Marshmallow is lookin' really nice, as long as the battery life ain't too bad I'm gonna test it out myself!
Excuse me, first i´m sorry for my bad english language. I have same problem the unsupported baseband, but till now i just feel confused. I flash the Resurrection Remix Nougat on twrp and says unsupported baseband error. What should i do first? Flash the new baseband? If it yes, which baseband version is suitable for my device. Im using LG d855 and running android 6. Or i must unlock bootloader before flashing the new ROM? Thankyou, hope anyone will answer my stupid question.
I am using micromax q372 smartphone, had an android 5.0 stock ROM, and now i have installed resurrection remix 5.5.9, and my DEVICE OFFICIALY DOESN'T SUPPORT, and I garbed all of my luck and installed it, and now I have a fully working custom ROM on a unsupported device, the only problem I had was with the data connection, and I sorted it out, now everything is working, .............now I want to install resurrection remix 5.9.X , and my device doesn't is not on the support list, so ....can I do it , without any bugs? .......plz advice me

[SOLVED] S3 T999 "No SIM card" beyond Andorid 4.x.x (Lineage, OctOS)

Hello.
The short story is I found one s3 t999 in the drawer and it had 4.x.x ROM. Without paying much attention I flashed the latest TWRP and installed Lineage 7.1.2, but I get "No SIM card" error and am essentially without a network. I'm using a non-tmobile SIM card.
The problem synopsis:
The S3 T999 yields "no SIM card" error with anything beyond Android 4.x.x.
- Tried with Lineage 14.1
- Tried with the latest 7.1.2 OCtOS
- Tried with a LP 5.1.1 OCtOS rom
they all say NO SIM CARD and subsequently "No Service".
Once I restore my touchwiz 4.1 ROM via TWRP - I get network reception and I can make and receive calls.
Can anyone walk me through the problem? I work with linux and flash my other phones with ease, which means I can execute any suggestions momentarily.
THANKS
You need to flash the latest stock ROM, then twrp, then custom ROM.
audit13 said:
You need to flash the latest stock ROM, then twrp, then custom ROM.
Click to expand...
Click to collapse
If I understand correctly, I need to Odin-flash the latest stock rom, which I found it to be JB 4.3. Will this affect my SIM lock situation, seeing as I don't use a tmobile SIM.
Also, Odin requires that I enter "download mode", which TWRP (currently installed) does not seem to have. Odin does not 'see' the s3 connected (whilst in recov. mod).
Does that mean I need to flash a stock recovery first, and if yes, where do I get it and does it matter which stock recovery is being installed?
Flashing the latest stock rom should not affect the sim lock.
You can boot to the bootloader from twrp.
Just flash the stock with Odin, no need to flash anything before hand.
audit13 said:
Flashing the latest stock rom should not affect the sim lock.
You can boot to the bootloader from twrp.
Just flash the stock with Odin, no need to flash anything before hand.
Click to expand...
Click to collapse
Quite right, I was about to sideload-flash a stock recovery I unearthed here, before I noticed in TWRP in the Advanced menu having the "Download" option right next to sideload, so I booted directly into download mode Odin'd the latest stock rom I found (JB 4.3) and I do still have cell reception.
Does that mean I go into DL mode now, sideload TWRP and proceed to install Nougat (and hoping to have network access)
THANKS A BUNCH
You can flash the tar version of twrp from Odin. Then flash custom ROM, and enjoy
audit13 said:
You can flash the tar version of twrp from Odin. Then flash custom ROM, and enjoy
Click to expand...
Click to collapse
ALL DONE.
I Odin'd TWRP 2.8.6, from there I sideloaded TWRP 3.1.1 then upgraded via IMG install from within and installed OctOS 7.1.2 nightly.
Would you recommend Lineage over OctOS?
Thanks for the tips!
You could have install twrp 2.8.6 and flash the 3.1.1 zip from recovery.
Sorry, I can't make any rom because I haven't owned an s3 for a few years.
Glad you got it all sorted
audit13 said:
You could have install twrp 2.8.6 and flash the 3.1.1 zip from recovery.
Sorry, I can't make any rom because I haven't owned an s3 for a few years.
Glad you got it all sorted
Click to expand...
Click to collapse
Unfortunately, right off the bat, LED notification isn't working when a call is missed. I tried to call my number to inspect reception and when the call was registered as missed - no notification light is present - at all. Despite being enabled in settings.
Some custom ROMs have bugs so I recommend trying others until you find one you like. I used to flash my s3, s4, Nexus 5, LG g2 all the time and would come across minor bugs. At least your sim works with newer custom ROMs.
I'm now using an iPhone but still get the urge to hop back to android.
audit13 said:
Some custom ROMs have bugs so I recommend trying others until you find one you like. I used to flash my s3, s4, Nexus 5, LG g2 all the time and would come across minor bugs. At least your sim works with newer custom ROMs.
I'm now using an iPhone but still get the urge to hop back to android.
Click to expand...
Click to collapse
Quite right. I nandroid all of my ROMs so I can give few a spin and return to the one I fancy the most.
And yes, my SIM is now recognized and communications flowing . All I needed was the latest stock rom requirement tip and I was done.
Thanks for that.
audit13 said:
Some custom ROMs have bugs so I recommend trying others until you find one you like. I used to flash my s3, s4, Nexus 5, LG g2 all the time and would come across minor bugs. At least your sim works with newer custom ROMs.
I'm now using an iPhone but still get the urge to hop back to android.
Click to expand...
Click to collapse
Fux's sake! I spoke too soon.
Overnight, the phone (with Nougat) lost network again and in the morning showed "no SIM card". A restart remedies the problem for about 10 minutes before it completely refuses to acknowledge its SIM .
I downgraded with Odin to JB 4.3 and it appears to have network coverage for about two hours now. I'm about toss this piece of garbage 'fone' in the bin.
Is there any reasonable explanation as to why this idiot of phone of mine looses connection, just willy-nilly?
Maybe these nougat roms are too buggy. How about some older cm roms?
Freakin' antique isn't holding service more than few hours (at best) regardless of ROM installed. Even if there is a sequence of actions that can make this piece of garbage 'fone' work well - I'm no longer interested in investing a single minute further. Goes in the bin, end of.
Life's too short.
Just to update those who'll likely one day google and find this.
After going back and forth for as many days... my personal reason for losing connectivity on the s3 was because of a FAULTY SIM CARD. Had it replaced and network coverage came flowing.
As for those wishing to upgrade to Nougat or MM as I have, YOU NEED TO UPGRADE TO THE LATEST STOCK ROM, BEFORE MOVING ONTO NOUGAT.
Matter is now closed.

Categories

Resources