(TL;DR available)
I have a Zenfone 2 (Z00A) and I used to have LineageOS (Android N 7.1) installed, however after some time I noticed the SIM Card wasn't getting detected anymore. At first I tought it was Lineage, so I updated it to the latest experimental, still, nothing. Then I decided to test the SIM in another phone with the same version of Lineage, with my old Zenfone 5, and the SIM still worked. So I reset my Zenfone 2 back to stock ROM, stock Bootloader, stock everything, and the SIM worked. Still thinking it was Lineage, I installed Ressurection Remix, which also requires the MM Bootloader, and the SIM didn't work once again.
*** TL;DR ***
I believe the MM Bootloader is causing the phone to not read the SIM card. It only happens with this provider, since other providers' cards are still recognized. It's very weird. Any help is fairly appreciated.
(This is my first thread and english is not my primary language so sorry for any mistakes.)
1) Which stock ROM does it work with , surely its MM bootloader ?
2) Which TWRP did you have installed.
3) Depending on Which TWRP you do have and what stock ROM (answers from 1&2 above) , you back up stock rom which works , back up in TWRP and simply restore it, a two minute job .
Depending on all answers above...
Try slim7 ROM till linos is fixed . RR is based on linos.
Latest linos does take approx 5 mins to register sim after reboot, don't touch device , leave screen / display setting to half hour and watch it connect without touching the phone.
This question should be answered in thread of ROM development you had trouble with , reading related threads is also wise .
https://forum.xda-developers.com/showpost.php?p=71270877&postcount=25
timbernot said:
1) Which stock ROM does it work with , surely its MM bootloader ?
2) Which TWRP did you have installed.
3) Depending on Which TWRP you do have and what stock ROM (answers from 1&2 above) , you back up stock rom which works , back up in TWRP and simply restore it, a two minute job .
Depending on all answers above...
Try slim7 ROM till linos is fixed . RR is based on linos.
Latest linos does take approx 5 mins to register sim after reboot, don't touch device , leave screen / display setting to half hour and watch it connect without touching the phone.
This question should be answered in thread of ROM development you had trouble with , reading related threads is also wise .
https://forum.xda-developers.com/showpost.php?p=71270877&postcount=25
Click to expand...
Click to collapse
1) I am currently running SuperZen which is based on Android L, works fine.
2) 3.0.2 and I tried with older 2.x.x versions too, no success.
3) Can you specify a little more? A bit confused with what you mean.
I will try LineageOS once again, and shall also try Slim7.
I posted this here since I didn't, and still don't, beleive this has to do with the ROM, but with the Bootloader itself.
I read a lot of threads, including the one you sent me, tried everything without success.
Thank you for now!
kronkraken said:
1) I am currently running SuperZen which is based on Android L, works fine.
2) 3.0.2 and I tried with older 2.x.x versions too, no success.
3) Can you specify a little more? A bit confused with what you mean.
I will try LineageOS once again, and shall also try Slim7.
I posted this here since I didn't, and still don't, beleive this has to do with the ROM, but with the Bootloader itself.
I read a lot of threads, including the one you sent me, tried everything without success.
Thank you for now!
Click to expand...
Click to collapse
Backed up, completely wiped, installed MM Bootloader and flashed Slim7. No SIM. Set Sleep Timer to 30 minutes, rebooted, unlocked screen and left the phone for 10 minutes. No SIM. Did it again but this time didn't even unlock the phone, no SIM. Completely wiped and flashed LineageOS, same process, no SIM. Even went further and tried CM13 (Android M), same process and still no SIM. At this point I am 99.9% sure it is the MM Bootloader that is causing the issue, because as soon as I fallback to the L Bootloader and flash any L ROM, like Stock ASUS or Super ZEN the SIM works fine.
Try stock M , there's been about 6 stock updates in stock M
timbernot said:
Try stock M , there's been about 6 stock updates in stock M
Click to expand...
Click to collapse
Not sure where I can find Stock M, but I found an update on ASUS' Website, Firmware version UL-4.21.40.144 that is Brazil specific, wonder if it has something to do with the SIM not working.
kronkraken said:
Not sure where I can find Stock M, but I found an update on ASUS' Website, Firmware version UL-4.21.40.144 that is Brazil specific, wonder if it has something to do with the SIM not working.
Click to expand...
Click to collapse
are you from Brazil ?
It shouldn't by rights , yes there was probs with Brazilians receiving signal but jrior dev , incorporated those fixes for Brazilians into CM which should be carried through lineageOS.
I don't have anytime right now but will help you update.
Watch you don't brick doing anything daft.
:crying::crying:
timbernot said:
are you from Brazil ?
It shouldn't by rights , yes there was probs with Brazilians receiving signal but jrior dev , incorporated those fixes for Brazilians into CM which should be carried through lineageOS.
I don't have anytime right now but will help you update.
Watch you don't brick doing anything daft.
:crying::crying:
Click to expand...
Click to collapse
Okay, for now I will just restore my backup! Thanks!
kronkraken said:
Okay, for now I will just restore my backup! Thanks!
Click to expand...
Click to collapse
I was able to get the Official MM Bootloader installed, and SIM works fine. Not being able to install any MM-based ROMs tho, they all give Error 7: "This package supports Ifwi Versions: %2; 0094.0183;this device has Ifwi version ."
Related
So I took out my age old xperia M(single sim) a couple of days ago and installed cm 12.1 on it. The only issue I'm facing with it is that if I keep the phone on standby for a while the phone completely and silently shuts itself off. When this happens it doesn't turn on with the power key as well so the only way to turn it on after this happens is by removing and re inserting the battery and then pressing the power button. (phone boots normally then)
This problem only appears when the phone is in standby. I could use it 2hrs straight and the phone would keep functioning normally as long as I don't keep it on standby for a long period.
I've tried tons of different cm12.1 roms and factory reset the phone multiple times but the problem is there with every single rom. Haven't tried any rom that isn't based on 12.1 yet.
Strange thing is that this standby dead thing doesn't happen when there is a music app that's playing some song while in standby. Even if the phone is on silent and media volume is 0. So the temporary fix is to keep playing some song and keep media volume at 0. I would be really happy if someone comes up with a permanent solution though. Thanks. Any help would be greatly appreciated
Was the problem present on the stock ROM?
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
kurtbvb said:
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
Click to expand...
Click to collapse
No, I don't think so. Which version did you come from? I would suggest flashing 15.4.A.1.9 first because most custom ROMs use it as base and doesn't offer full compatibility with older versions.
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
RagzyB said:
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
Click to expand...
Click to collapse
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
elmkzgirxp said:
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
Click to expand...
Click to collapse
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
RagzyB said:
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
Click to expand...
Click to collapse
Flashtool. Some files are required which custom recoveries can't flash.
Just flashed the above mentioned ftf file and then rooted the phone, installed twrp and then cm 12.1 based rom. Everything runs perfect now. No random shut downs and Sim card works as well.
Thanks you so so much
Hi,
I am completely new to the Custom Rom Scene and most likely did a whole bunch of things wrong, but I can't figure out what I did wrong, even tough I extensively searched the Forum.
I have a D855 bought in Germany and installed TWRP 2.7.8.0.
Originally I was using the LG Stock Rom of Android Lollipop.
Then I tried flashing various Marshmellow Roms + OpenGapps but all, altough looking fantastic, seem to have the same issue:
After booting the phone my SIM card is not detected and Wifi can not be turned on.
In the System-info menu there is no Information shown regarding IMEI, etc and no Information regarding wifi, the Wifi-macadress shown is 02:00:00:00:00:00.
I hope I did not do anything idiotically wrong, maybe someone can point me in the right direction to fix this?
Thank you a lot in advance
Cheers
-fr3sh-
Could just be hte rom mate. I recommend trying Resurrection Remix. Its a 6.0 rom as well download that and go through the set up and tell me how it works.
FawkiDied said:
Could just be hte rom mate. I recommend trying Resurrection Remix. Its a 6.0 rom as well download that and go through the set up and tell me how it works.
Click to expand...
Click to collapse
Thank you for your support, however I just couldn't stop playing around with the phone meanwhile and managed to get everything working:
First, I wiped everything in TWRP
Then, flashed ALL of these: http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
Reboot, now everything is working.
To get Bliss installed, I then wiped cache and dalvik and intstalled the Bliss-Rom + OpenGapps
Everything seems to be working perfectly now.
PLEASE CLOSE/DELETE
Thanks again for your quick reply Fawki
Hello this is my 1st post on this forum, i have a 7105 lte no operator and im from portugal. Ive tried cm rom and after that Dn4 rom, all works great except for gps. I was in the change i gess that afected my gps lock, i have read and the only thing i think that haven,t tried was the nv rebuild but, say a custom and won,t allow me to reset. I havs tried with stock rom, with dn4, with root and without same thing.... can anyone help me?.
Choco Man said:
Hello this is my 1st post on this forum, i have a 7105 lte no operator and im from portugal. Ive tried cm rom and after that Dn4 rom, all works great except for gps. I was in the change i gess that afected my gps lock, i have read and the only thing i think that haven,t tried was the nv rebuild but, say a custom and won,t allow me to reset. I havs tried with stock rom, with dn4, with root and without same thing.... can anyone help me?.
Click to expand...
Click to collapse
Flash stock ROM again.
Sent from my GT-N7100 using Tapatalk
Allready did that multiple times. Also my nv rebuild says custom and dont allow me to acess it
Like this... this post resumes my problem... HELP
d0ctorj3kyll said:
Hi
XDA newbie, still learning where everything is! I posted this question in the general help thread but got no replies, then I found this section so please pardon the repost
I have a rooted Galaxy Note 2 N7105 (t0lte I think) running Samsung Stock software 4.4.2. I have previously installed various version of CyanogenMod and Ditto Note, and somewhere along the line have lost my GPS functionality! Running CWM recover, not sure what version off the top of my head. The exact issue is that when I turn GPS on, it shows the "searching" symbol endlessly and will not lock to any satellites.
I have tried reflashing the modem and every GPS fix app that I've seen suggested on forums, and it still will not lock my location by GPS. Power saving (wi-fi and mobile network) location still works.
From my research, I believe the NV Rebuild method (listed here http://forum.xda-developers.com/showthread.php?t=2211690) is what I need to do in order to fix the problem. However when I access the hidden dialer menu and select NV Rebuild it tells me "Not Support in Custom Binary!" Other people have had this issue and posted asking for help in the thread, but nobody replied or helped them.
As I mentioned, I am running stock Samsung software, not a custom ROM. The phone is rooted, and I do have a few Xposed modules installed. I also used Triangle Away and my bootloader shows the device status as Samsung Official. It also showed Official in settings when I tried to run the NV Rebuild. As far as the information went, this should be all I needed to make NV Rebuild work, but it still gave the custom binary error.
Does anyone have any suggestions for how to get around this? Do I need to completely unroot my phone and reflash a vanilla copy of Samsung 4.4.2 before it will work, or is there a workaround to make the service menu read my phone as official and run the NV Rebuild?
Any thoughts or ideas would be HUGELY appreciated as this issue has been driving me mental! (Please let me know if you need further information and I will try to provide it ASAP)
Thanks in advance!
Click to expand...
Click to collapse
Helpppp
Choco Man said:
Helpppp
Click to expand...
Click to collapse
Try lineageOS 14.1. My GPS was dead after going back to kitkat after lineage. NV rebuild also not support in custom binary. Found the solution here https://forum.xda-developers.com/ga...nt-n7105/rom-lineageos-n7105-t3538310/page136
From lineage I did only a format(not wipe or factory reset, I dont know what is the difference) in TWRP 3.2.3 and flashed zip of the omnirom kitkat, and GPS was working, then format and flashed official FTM ROM. Maybe not need to go via omnirom, for me it was clear that kitkat is not getting the fix and it was easier to flash a zip kitkat than an image from Odin.
chitz852 said:
Try lineageOS 14.1. My GPS was dead after going back to kitkat after lineage. NV rebuild also not support in custom binary. Found the solution here https://forum.xda-developers.com/ga...nt-n7105/rom-lineageos-n7105-t3538310/page136
From lineage I did only a format(not wipe or factory reset, I dont know what is the difference) in TWRP 3.2.3 and flashed zip of the omnirom kitkat, and GPS was working, then format and flashed official FTM ROM. Maybe not need to go via omnirom, for me it was clear that kitkat is not getting the fix and it was easier to flash a zip kitkat than an image from Odin.
Click to expand...
Click to collapse
Your solution gains my interest. I am using GT-N7105 too. The road of Roms I have been through is Lineage 14.1 -> Resurrection Remix 5.8.5 -> Stock 4.4.2
When I went back to the Stock rom, GPS totally unable to detect any satellite using any GPS tools app. IMEI blank but Baseband is still there, the weird thing is the phone network signal works without issue. :angel:
Have been trying many ways to fix GPS including reflash stock rom but still failed. I went back to resurrection remix 5.8.5 and GPS works without issue but IMEI is still blank.
Any recommended omni rom as you mentioned? and what is official FTM rom? A stock rom?
I had no problem with mobile data on official ROM but from the day I installed CM 13, I can not using mobile data anymore.
First of all, I installed CM 13 beta, then CM 13 stable and some nightly builds. Nothing changed!
I installed AOPS Nougat 7.0 Beta2 few weeks ago on my C2005.
I had "CM13-UNOFFICIAL-20160104-NIGHTLY" and data did not work, I updated it to "stable-20160527-NIGHTLY" (via cmupdater) and nothing changed. After few months, I installed AOPS Nougat 7.0 Beta2 but I can not use the data yet. I installed Nougat Beta2 via TWRP boot manager and wiped everything (all the data, cache, etc.) .
There is few weeks I've installed CM 14.1 on my C2005 and updated it to some nightly builds but the problem still exists after several months and several Android versions.
I installed CM 13 "stable-20160527-NIGHTLY" on my wife's C2005 and the data works a charm! Even I tried to flash mine to that version but problem still exists to my phone even with that version.
The only different between my phone and my wife's C2005 is that I didn't install TWRP on her phone and just installed CM13 with it's own recovery.
I tried instructions described in this link and the problem has not not solved yet.
The last thing is when I enable mobile data (SIM 1 or SIM 2) the cross mark but it does not change to H+ or other marks that shows I'm using data (attached screenshot).
Is hardware problem possible for this issue?
How can I provide CM logs for this problem to find out what's wrong with my phone?
Does someone else have such a problem?
Any idea about debugging and providing some logs?
Any idea about debugging and providing some logs?
Read the bug section of Cynogenmod
http://forum.xda-developers.com/showpost.php?p=69518095&postcount=12
Device-related bugs
– Dual: no internet on 2nd SIM
Click to expand...
Click to collapse
Also, try flashing your device with official rom 4.3 again and try using internet on it. If it works you are doing something wrong in flashing other os, if not, it's device related.
Thanks for reply. Actually I can not use data on SIM1. It's OK for me and it shouldn't be necessarily on specific SIM.
I'm looking for another way of checking data rather than reflashing to official ROM and install CM again. Something like reading /var/log/something.log in Linux distros. Is anything like that possible on AOSP or CM?
No. You can try however reflashing and clean installing aosp 7 or cm14 again, alongwith with THIS patch for dual sim users. But before you install anything make sure you are on 4.3 firmware, or you are likely going to face the same problem again.
Data works on 2nd SIM.
Thank you all for your help.
Believe it or not, the data on 2nd SIM is usable, but 1st SIM.
It could be Edge or HSPA.
As the known bugs says, data is now work on 2nd SIM, I always tried to enable data on the 1st SIM, but few nights ago I had enough free time to check all the options and finally it worked!
hi i have had the pleasure of using the developer oreo img and enjoyed it,but decided to reflash stock noughat img
until the official oreo comes out.heres where my issue started,after a successful flash and start up,my sim no
longer shows as inserted,i even tried a restore of my noughat back up.the only way my sim will work nowis with the
oreo stock img reflashed..anyone else have this isssue
Are you sure you flashed all the files included in the Nougat fastboot package zip? There must be an image called 'modem' and anoter 'dsp' which should take care of that.
Try reflashing the Nougat image once again.
I will try again
Having the same exact issue
Flashing the MR3 factory image results in no SIM card, same with fkashing MR1 @TheCrazyLex
EDIT: reflashed again the next day and it's now working....ugh annoying
Had exactly the same issue. Although on initial boot back to Nougat, everything worked fine.
It was only after a restart or two the SIM was then undetected.
I'm flashing stock Nougat again just now, hopefully that resolves it for me too.
EDIT. Ok I've now tried flashing multiple images, they all flash successfully and boot successfully, but none of them are detecting a SIM card.... any ideas anyone?
EDITS AGAIN: It would appear now working after flashing Oreo again, then back to Nougat. Very odd....
I want to lock the bootloader again, which is how I ended up in this mess, so I'm now flashing latest Global ROM again, rebooting and then attempting to lock the bootloader again.
I shall update with results.
any update in the same boat
I'm still having same issues,I'm just using Oreo which is working really well.only downfall I noticed is tethering doesn't seem to be working on it
Are you running the right image as Razer and Three have their own build so wanted to point this out as ThreeUK may not work right with the Razer build. i Remeber them saying something about making sure you use the right build
UPDATE - if anyone is having this issue.
--Take the Oreo preview and flash_all.bat via bootloader
--Let it boot and get in to Android just so you can enable debugging via dev options
--reboot to bootloader and flash_all.bat with the latest Three or Global image
--Again let it boot and enable debugging again
--Now reboot to bootloader, and do BOTH the following in fastboot:
---- fastboot flashing lock_critical
---- let it reboot and go back to bootloader again and perform the next lock
---- fastboot flashing lock
Once finally back in, only then did I have a locked bootloader + working SIM card.
Hope this helps someone.
Locking the bootloader doesn't fix things lol. I was on Oreo yesterday and flashed back to nougat and had signal and relocked the bootloader then 10 minutes later .y phone rebooted and lost sim. Only was to get it back was flashing Oreo then booting then flashing nougat mr1 and got my sim back. Then I locked bootloader and took the ota and now I'm back to normal and can take otas again
This is such a weird issue. like for instance I went back to MR1 from Oreo and had signal but when I picked the bootloader and ota to MR3 it was gone.then just unlocked bootloader flashed MR3 still nothing. So went back to Oreo and it worked and then flashed MR1 again and randomly worked even after the ota to MR3
So absolutely random.
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
SIM card issue
Hey @parky169, @Roxas598, @linuxct, @kickassdave, @joemossjr
Thanks for posting about this issue that you saw about the SIM not being detected. Our engineers would like to learn more about this and EXACTLY what happened. Can you please PM me with the details:
What carrier you guys are on?
What was the previous build you were on before you flashed the Oreo developer build?
Can you please walk me through EXACTLY what happened that caused the SIM to go undetected
Were any APNs changed prior/after?
Were any changes made to the files or phone (rooted, custom ROM, etc.) prior to flashing the O build?
How did you resolve this situation? Is this repeatable?
Thanks again for testing the developer build! Please PM me if you run into any more issues!
Best,
Khanger
parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Same issue as the rest. I wonder if this will work with the Oreo OTA modem img, I'm gonna give it a shot. I will report back
EDIT: Well there is probably no reason it shouldn't have worked I would assume the modem images are identical in 8.1 Dev and 8.1 OTA, but it does work by putting the 8.1 MR0 OTA modem img in the 7.1 MR3 and flashing. Honestly i ws too lazy and didn't want to wait for the Dev image to download and I already had a copy of the 8.1 OTA ON MY pc.
Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!
Jonlines94 said:
Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!
Click to expand...
Click to collapse
I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?
NoXXX said:
I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?
Click to expand...
Click to collapse
Any update on this? I am in the same boat after standard OTA update. Can not save apns either. (at&t)
Thanks!!!
parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Thanks for finding a fix. I was worried my phone was jacked up. I was having the same issue. I wanted to downgrade from Oreo since there is an issue with HDMI not having audio. I got signal now whoooo