Just received 29.2.A.0.129 update for my C5 (single SIM E5506) from Wind (Canada). This is an update from 29.2.A.0.122, and still Marshmallow 6.0. Android security patch level July 1, 2016. For some reason the OTA kept failing but it worked on Sony PC Companion. Really hoping it fixes some of those bluetooth issues on this phone...
Hi Jets,
if still BT problems try this:
The solution was quite simple. If you received Marshmallow via XC and a software repair doesn't fix several issues, remove the sim card and the SD. Reboot the phone and perform a software reset.
After the software reset proceed with the setup of the device, connect to WiFi and allow it download and install software updates from What's New. One of them will be a maintenance update with no information whatsoever.
Turn off the phone, put back the sim and the SD card. Turn on the phone. Enjoy your C5 fully functional and issues free.
It worked for me, have to thank YoGem the author of this trick
bico2016 said:
if still BT problems try this:
Click to expand...
Click to collapse
Hi bico2016,
At what point do you need to connect the watch for BT? To install the SIM and SD or after?
Related
I have 2 Galaxy notes that have been stock since day 1 with no modifications other than sim unlock via code. I waited patiently till the official ICS release came out to do my first ever phone update using Kies. After the update, 1 is running perfectly and the other has a notification stating that the sim card is not valid, contact customer care. I swapped sim cards and got the same error. Both Sim cards on other phone working properly.Restarting phone didn't resolve the problem. After a few seconds to minutes from time of reboot (in which phone recognizes network and I can make phone calls normally), the same error occurs sometimes with the code in place of the Service Provider name (63081)? I tried factory reset using phone menu and it wiped it clean but still same error. I tried reinstalling the ICS firmware/rom update provided via KIES and I'm still getting the same error.
I researched this plenty and noticed that others have had similar problems with sony phones after ICS update with no resolution.
Any suggestions?
is rooting possible yet to try another rom?
Can I go back to GB though I don't have a backup?
It sounds like a bad modem flash.
Why not make a nandroid of the good phone and restore it on the bad phone.
Thanks for your reply. I resolved it. Even though I had tried a different sim from the same company for a nother number and it hadn't worked, I still decided to make a new sim for my number and that seemed to resolve the problem. Still odd as to why ICS update would do that.
rangercaptain said:
It sounds like a bad modem flash.
Why not make a nandroid of the good phone and restore it on the bad phone.
Click to expand...
Click to collapse
I have a galaxy note i717r. I have been having troubles with the sim card not being recognized at all. I purchased a new sim tray complete with sd card slot. I replaced it and it seemed to work. After two days however the phone once again said No Sim. I purchased yet another sim card tray and tried that but wasnt able to solve the error at all this time. Please help if you know of the solution.
ps: I have also reformatted, reinstalled firmware, rooted it and tried titanium backup fix, and installed "vanilla" firmware to see if that would help. Nothing fixed it.
Good Luck
Bachelder said:
I have a galaxy note i717r. I have been having troubles with the sim card not being recognized at all. I purchased a new sim tray complete with sd card slot. I replaced it and it seemed to work. After two days however the phone once again said No Sim. I purchased yet another sim card tray and tried that but wasnt able to solve the error at all this time. Please help if you know of the solution.
ps: I have also reformatted, reinstalled firmware, rooted it and tried titanium backup fix, and installed "vanilla" firmware to see if that would help. Nothing fixed it.
Click to expand...
Click to collapse
I just went through this same problem. After I replaced the SD reader my phone still didn't work, so on a last-ditch effort I used the KIES utility available at KIES -> Tools -> Firmware Upgrade and Initiation. This reset to the phone to full factory specs, just AT&T's updated android JellyBean 4.1.2. This worked and I was able to see my SIM card and get on the AT&T network.
Of course, afterwards I had to reroot and reload all custom software.
If you do this, make sure you have the latest version of KIES.
Good luck
My parents just got a new Unlocked US Edition Moto G 2014, and it is on Kit Kat out of the box. I was assuming it would just update to Lollipop during the first boot. But nothing, and checking for System Updates is not working.
We do not yet have a SIM in this new phone for several more days.
Since I am not there in town, I do not want to try and drag my parents thru the awesomeness that is sideloading an OTA.
So basically - Can Android OS Updates like Lollipop be downloaded strictly via a wifi connection (using the System Updates feature) on a SIM enabled device like a phone. Obviously it is possible on wifi only devices like tablets.
Does anyone have any official proof/documentation of how this is handled? Or even users posts showing it not working until a SIM is installed? I don't want to waste any more time trying to get the update if a SIM is required on a phone. Which is odd because my phone is Unlocked - so there is no "Official Carrier", so who provides my OTA? The carrier I choose to use? Motorola? Or Google?
Thanks in advance!
Anyone have the issue where the SIM card isn't recognized? I'm on the RR newest ROM and the card isn't being recognized...I'm about to try the stock ROM and see how that goes.
Similar problem
I`m in a similar position I think. However, my phone recognizes the SIM but when checking the SIM-status the mobile radio seems to be off. I can´t change preferred network type, it just jumps back to "TD-SCDMA/GSM/WCDMA/LTE , I get no results when searching for mobile networks and when I use the *#*#4636#*#* - menu the "Turn on radio"-option wont respond. I`m on latest stock firmware and the phone is still displaying IMEI-numbers. I bought my unlocked European version of Oneplus X yesterday on an auction site, the seller has good reputation and he claims that it worked fine for him. I got a new SIM-card today thinking that would have solved the problem, no luck there however. I also did a hard reset and downgraded to an earlier version of a stock firmware and the error is still there. I noticed I had TWRP v.2.8.7.0 blu_spark r5 preinstalled when I bought it, its a custom kernel right? Could something related to the kernel be the root of the problem or the baseband? Any suggestions on what to do next?
Dear community,
when I updated my dual sim phone H818p (AME region) via OTA to MM - version v20c, I realized that phone calls and SMS messaging do not work after the phone is encrypted. When trying to take or receive a call no connection is established and the phone app gets stuck. Additionally SIM2 does not connect automatically to the network anymore. Interestingly, internet via phone providers still works on both SIMs. This phenomenon is reversible, in unencrypted mode everything works flawlessly. Since I need encryption for use as company phone I have a real problem here.
I meanwhile also tried to flash the new version v20d which was recently released in Europe, but encountered the same bug with this ROM. Also resetting the phone to factory settings or flashing the ROM in refurbish mode with full memory wipe did not change a thing.
LG support (I have to use Middle East because of the phone region AME) is not very helpful. They only offer help if I send the phone in and do not comment on the issue itself.
In case anyone has similar issues with MM on the H818p (or other phones of the LG G4 family), please let me know, especially if you have found a fix to this problem.
Back to Lollipop
Since nothing worked to solve my problem with any MM version of the H818p stock software, I wnet back to Lollipop via LGUP - v10l. Very disappointing that LG apparently distributes software via OTA which has such serious flaws.
Update: I am back to Android 6 via OTA. Via another entry I learned that the bug disappears, when deactivating the SIM-lock and restarting the phone. Now phone calls and SMS work normal again also while the phone is encrypted.
Sent from my LG-H818 using XDA-Developers mobile app