Hello,
I have encountered problem with my i9300. Mobile does not detect SIMCARD, I have tried on two cards. I tried other versions of ROM, but all these were CM 12. I have passed some pages of forum, but I cannot be certain with installing any patches. Is there any way how to get over this?
I don't want do downgrade from CM12
My OS: CyanogenMod 12.1-20150825-UNOFFICIAL-i9300, as I remember that was Archidroid ROM
Any hints?
Check your imei and see if its still there
Related
good day to all,
I've got sony xperia z3 tablet compact; LTE version, SGP621 (scorpion). I've managed to unlock bootloader, install twrp, install cm-12.1-20150704-NIGHTLY-scorpion.zip, with gapps and superSU root.
What I realized after some time - when I was out of reach of my wifi - that cellular network (broadband) is not working. More specifically, there are no entries in main settings menu for "mobile network" and also in "about" section, there is nothing about network or broadband. Could you advise me how to get it working?
I thought I mistook my device for "scorpion_windy" one, and installed cm same version for scorpion windy, but with no luck obviously,
SGP621 should be indeed pure "scorpion"
cyanogenmod's support for this device is for me a little bit misty, I'm not sure if it is official or unofficial, what is supported and what not. Most importantly, how can I get the modem working with it.
Beside missing modem, I see no issues with CM 12.1 nightly on this device so far.
skroslak said:
- that cellular network (broadband) is not working.
Click to expand...
Click to collapse
modem is working in android 5.1 aosp from free xperia project,
I'm gonna try another build of cyanogenmod
btw, I also tried android M preview on this device, however I can't get it out of safe mode. Anyhow, I don't want to run "preview" on my daily device, just wanted to have a look.
Could you post an exact guide how you did this? I am looking for tutorials for weeks now and nothing specific there. A step by step guide would be great...
Hello everyone,
I’ve running resurrection remix for the last few months and it is running almost flawlessly except for one thing: my cell phone can’t be seen or find other deviced. I think it is probably related to the weird BT MAC address issue. I’ve read some guide - some say it is needed to restore the efs partition, others have a very complicated method to restore it.. Anyway, what’s the definitive guide to fix this issue ?
It's fixed in Lineage OS so that's an option for you.
14.1?
Jangoux said:
14.1?
Click to expand...
Click to collapse
13 and 14.1
Hello Everyone,
I am having a weird problem.
I recently bought Samsung Galaxy S6 (SM-G920F) from someone else ( used for 5 months ). When I checked the OS, it has been already rooted and a custom OS was added. The firmware was ver. 6.0.1 . So, I tried updating. But because the ROM was unofficial, I couldn't do the update from Settings.
By using Odin and a stock firmware from Sam mobiles (sammobile.com/firmwares/galaxy-s6/SM-G920F/), I installed 7.0 OS.
I don't remember which region I choose, but it worked perfectly except for mobile network.
After update, the network isn't working. System says that sim is detected. But If I try making a call, it says "Network Not Registered". I have seen lot of post with this kind of issue but nothing worked so far. After I showed this to my repair guy, he said only old ROM ( or custom ) ROM will solve this issue, but after this you cannot update the OS.
Is this really possible? Phone working with Older Version or Custom ROM, but not with updated one?
If provided right guidance, I will try resetting my phone.
Note: I am from Nepal, and I cannot find any firmware application for this country.
Thanks in advance
Yes. Many devices do not work with newer software.
As for your issue you might want to check your apns as none of Nepals are in the stock apn config. Go in and configure it and you should be fine.
Yes you lose all updates on that device with a custom rom and 7.0 was the last official update the device will see short of the crappy security updates.
zelendel said:
Yes. Many devices do not work with newer software.
As for your issue you might want to check your apns as none of Nepals are in the stock apn config. Go in and configure it and you should be fine.
Yes you lose all updates on that device with a custom rom and 7.0 was the last official update the device will see short of the crappy security updates.
Click to expand...
Click to collapse
Hello Zelendel,
I tried configuring the APNs ( Added automatically by carrier ), but it did nothing. Anyway, does APN has to do anything with mobile calls ? I know it is responsible for mobile data services, but for voice services, I have no idea
abiraln said:
Hello Zelendel,
I tried configuring the APNs ( Added automatically by carrier ), but it did nothing. Anyway, does APN has to do anything with mobile calls ? I know it is responsible for mobile data services, but for voice services, I have no idea
Click to expand...
Click to collapse
Yes it controls everything from calls to data. Might want to call your carrier and see if the device has to be added to their network. The Sim might be tied to another device. I know some carriers in some countries do this.
Hi all,
Its time to upgrade Android 4.0.4 to a newer version.
Whats-app isn't working anymore and some other apps.
I would like to run it smoothly with all functions working correctly, especially GPS. So the latest android isn't needed i think.
I am thinking of CM12.1 (5.1) to start with. I know i have to resize my system partition and flash a compatible recovery.
But i can't find a step by step guide as this is a pretty old version. I hope someone can point me in the right direction.
thanks
As far as I remember, you don't have to repartition until Android 6.
Also, Android 5 ROMs are quite outdated, and might contain several security vulnerabilities. I would recommend going for LineageOS 11 ROM (Android 4.4.4) by grzwolf here on XDA. It contains latest Android Security Patches. Here's a KitKat compatible recovery: https://forum.xda-developers.com/showpost.php?p=79196916&postcount=230
Earnell said:
As far as I remember, you don't have to repartition until Android 6.
Also, Android 5 ROMs are quite outdated, and might contain several security vulnerabilities. I would recommend going for LineageOS 11 ROM (Android 4.4.4) by grzwolf here on XDA. It contains latest Android Security Patches. Here's a KitKat compatible recovery: https://forum.xda-developers.com/showpost.php?p=79196916&postcount=230
Click to expand...
Click to collapse
Thanks for your advice. I should get this working.
However I see Gapps from 2016 have to be used. Will GMaps and the Play store update themselves to a new version after installation or will i get stuck with the old ones?
ANDRiMiON said:
Thanks for your advice. I should get this working.
However I see Gapps from 2016 have to be used. Will GMaps and the Play store update themselves to a new version after installation or will i get stuck with the old ones?
Click to expand...
Click to collapse
It seems like you need to flash ROM, boot into it, then reboot to recovery and flash latest OpenGApps, reboot again and then you should be able to sign in to the play store:
https://forum.xda-developers.com/showpost.php?p=79585838&postcount=242
Hello everyone for some day I try to install lineage os 17 on a samsung galaxy a10 sm-105fn without concrete results my I still rooted my device it and the best custom rom that we can put on this type of device? I followed the tutorials on the forum my nothing goes on my phone
divinityxx159 said:
Hello everyone for some day I try to install lineage os 17 on a samsung galaxy a10 sm-105fn without concrete results my I still rooted my device it and the best custom rom that we can put on this type of device? I followed the tutorials on the forum my nothing goes on my phone
Click to expand...
Click to collapse
I have also been trying to flash my SM-105FN for a few days now. These guidelines seem to work for select devices.
Perhaps devices with different firmware allow other ROMs to run whilst other's don't, including firmware versions where Samsung may of changed something with their bootloader etc during updates. It might be useful to collect some information for those who where successful in flashing SM-105FN to find out what firmware they used to get their ROM working.