Database Develop

Phone doesn't read my SIM

I have been using CM11 (14-03-2014 I believe), without major problems until yesterday. Sometimes my phone seemed to disconnect from my SIM and I had to re-enter my pin code to reconnect to my operators network. But as of yesterday my device doesn't seem to recognize the SIM card, It doesn't ask for a code at all and can't make any connection whatsoever. I didn't change a thing, this problem started out of the blue.
I wiped cache and dalvik, updated to the latest CM nightly (08-05) but that didn't make any difference. In other threads I read about the baseband that might need an update, but I can't check which version I have now because when I try to enter the hidden menu I get the no network connection error. The strange thing is that CM11 has worked with (I guess) the stock baseband.
Is my phone tripping or could it be that my SIM card is broken?
Help and thoughts will be very much appreciated

Try it on stock to be sure about it.

After some searching I found a phone that could fit a regular SIM card, a Blackberry 9900. My SIM worked perfect in this phone, so that is not the problem.
I Also did a complete wipe and installed a stable version of CM 10.1.3, but that didn't seem to help. I hoped that a downgrade would have done the trick. I might try a ICS ROM or the stock firmware, but I kind of lost hope and i'm starting to think this problem is hardware related in stead of software. I'll report back with results on stock firmware and the ICS ROM.
How can I make sure the SIM reader in my phone is working properly?

Sorry for double posting, but I got an update:
SIM wasn't working with ICS so I decided to go back to the stock ROM. However, when I tried to flash V20B.kdz with KDZ_FW_UPD, the program got stuck at wParam=2010 and iParam=210. The phone is now stuck in S/W Update mode, and I haven't found a way to restore it yet. I will argue a little more with my phone when I get back from work, I'll open a new thread on how to unbrick when I can't do it myself.

Beunhof said:
Sorry for double posting, but I got an update:
SIM wasn't working with ICS so I decided to go back to the stock ROM. However, when I tried to flash V20B.kdz with KDZ_FW_UPD, the program got stuck at wParam=2010 and iParam=210. The phone is now stuck in S/W Update mode, and I haven't found a way to restore it yet. I will argue a little more with my phone when I get back from work, I'll open a new thread on how to unbrick when I can't do it myself.
Click to expand...
Click to collapse
My good friend i know i probably come 2 late but here is the anser 4 future users!!
http://forum.xda-developers.com/showthread.php?t=2069723
its supose to freese in ther!! (not ther but ....)

I have the same problem, and exactly the same error at reflash.
Dead end. Buy a new phone .
I tried to flash it about 80 times. One guy from a gsm repair has a bit luck and make it work at the first, but then, when he wanted to repair my imei, the phone stucked again in S/W Upgrade.

cannot devunlock after reset

I was running WP8 on a T899M Ativ S for some time with full interop unlock and all capabilities. After a recently pushed upgrade (no idea how it was installed), I noticed that the internet was no longer functional. The only thing I could figure out to do that might fix it was to reset.
Reset DID fix the internet not working issue; however it caused more problems.
It blew away the dev unlock and now I can't get the device to dev unlock again. I suspect it's because the device changes some registry entries ("prodportalurl"?) to "127.0.0.1" so it now cannot reach the site needed to dev unlock.
The error I'm receiving is:
Status: Error communicating with the windows phone dev center. Please set the correct date and time on the phone, check the internet connection on the device, and try again later.
(Obviously, I've done all those and it's not working so I'm here.)
How can I get this fixed?
Thanks,
Kevin

flash the rom and custom csc. what carrier is it, bell?

[HELP] Dying Moto X (XT1058), trying to save it, any help appreciated

Hello,
So my Moto X (1st gen, 2013, XT1058) used to work fine on KitKat but after it auto-updated to Lollipop it started messing up more and more every day. The phone is fully stock and locked. Here's a brief list of problems:
random freezes and crashes of apps and the OS itself
random screen freezes (doesn't respond to touches) or completely blank screen apart from the notification bar, often times nothing help but a reboot
random reboots, "optimizing apps" every so often on boot, especially when on charger
flaky and unreliable WiFi, not connecting when it should or disconnecting at random including when screen goes off (despite having "always on" selected)
GPS would sometimes have difficulty acquiring lock and would lose lock randomly (worked just fine before)
I'm not quite sure what to do at this point. It's the AT&T variant which means the bootloader is not unlockable. It is also updated to the latest OTA (build LPAS23.12-21.7-1) which means no rooting method works, or at least I haven't been able to find any. So I can't get even a temproot. I tried everything I could find, nothing worked and I'm running out of options. I love this phone and I'd like to get it back to working order. I'm wholeheartedly hoping someone here will have some good advice or some resource I haven't tried.
Here's what I tried so far:
multiple factory resets, both from system settings and through recovery
didn't help, works for a while but all the issues reappear soon after
rooting with KingRoot
failed, rooting method not available
rooting using this method
failed (not surprising, it does mention it doesn't work on OTA)
unlocking BL via Moto's official unlock service
device not supported
installing moforoot
failed, mofoverify just quits silently and the phone shows a message about some missing fastboot var
unlocking BL using Sunshine
says the device should be supported but then fails acquiring temproot, the phone just reboots
reflashing stock KitKat from here (file: ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip) via fastboot
failed, OS/BL downgrade not allowed
reflashing stock Lollipop from here (file: ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip) via fastboot
partial success, managed to flash a few parts, however it fails on all relevant partitions (gpt, boot, system), reports "downgrade not allowed" just like with KitKat which is surprising, this version/build should be exactly the same as what's currently on the phone
wiping userdata and cache via fastboot
didn't help
I might have tried some other things/methods too, this is just what I could remember right now.
Again, I'd very much appreciate if someone could help me revive this phone. I enjoyed using it while it was working well and I'd like to get it back to that state. Any help is very much appreciated.
Cheers!

I'm having exactly the same issues on my wife's moto x. The only thing I've been able to do for a temporary fix is to enter stock recovery and clear cache. Is there really no root/custom rom method for this device?

unable to install January security path update

I updated my moto x4 from Oreo to pie using flash using boot loader. my boot loader is still locked and software status is official too. It still is unable to update to January security update. Please help !!

yes I have also facing same issue... i have also try by safe mode but shows something not right .... reconnecting to server... might be Moto update Services try to connect moto server which has not able to connect due some issue in server... hope so this is issue...
you can connect to moto support team let me know what they are say for this issue.

They told to reset and try again.. to do that I got to backup my data which LL take time.. so on hold as of now

Yup, same here. I got the Android 1 Google Fi model (Bootloader unlocked, unrooted). I'll try again in a week and see if it resolves itself.

And another ~ bought 2, mine showed the update 3 days before my wife's but won't start (download and install now, via wifi only and it reverts back to the settings screen). She got the notification last night and it took first try. First time I've had this issue in the 4 months I've had the phone, just glad I'm not alone here....

Since you're official/fully stock, there's not really any alternatives besides factory reset or await for full image is available to manually flash via fastboot method. You do not need to unlock long as you stick with motorola firmwares. Links in FAQs thread.

Nothing new here? Mine keeps nagging me to do the update, start it and it shows getting to 17% on step 3 of 6, then just kicks me back out to the setting screen.
This is my first android phone (from a flip), couldn't get lineageos to work with my provider (RedPocket) and have neutered as much of the google crap as possible. Right on down to disabling all permissions for Play Store. Could that be part of my issue?

It has been nagging me since last few weeks, no solution apparently

New Update:
Could actually able to fix the issue by installing a vpn and set it as a USA based server.
My phone was bought in US and I was using it elsewhere. After using an USA based IP it downloaded the update and voila.

(SOLVED) bootloader unlocked x4 XT1900-01 One fi useable here?

just got a used x4 from ebay. on bootup before I get to the hi there screen of a factory reset, I get "phone can't be checked for corruption. please lock the bootloader" and the screen that just says android one. Then in a few seconds the hi there startup screen displays.
So clearly it has been motorola bootloader unlocked (EDIT which is fine for me).
and says it has android one (EDIT which I now realize is fine for me).
also says "verity mode is set to logging" whatever that is...
about - software variant - google fi (EDIT: I guess this means I can use google fi, though at present I am using an AT&T SIM for prepaid)
It is 64GB/4GB.
It came with 8.1, I'm updating it -
EDIT got it to 9 with Oct 1, '19 security update
Is that going to be a problem with the guides here like for twrp and flashing roms and stuffs?
THANKS!
--
it seems @Neffy27 's FAQ answers a lot of this...
https://forum.xda-developers.com/moto-x4/help/moto-x4-f-q-s-thread-t3814393

This is a keeper for me, with the caveat - if I modify it I don't get OTAs.
Apparently even as little as flashing the boot logo to cover the bootloader unlocked warning - no more OTAs.
Very nice phone!