SIM card not detected after reboot - Xiaomi Mi A1 Questions & Answers

Ever since I got this phone, There has always been this error "SIM card not detected" and it's extremely annoying to deal with as you have to restart the phone every time until it works (It took me 8 restarts to fix it today)
It's definitely not a hardware issue as my phone is brand new and so is my brother's phone (Tried both slots as well) and the sim card isn't even a year old
I've seen some people with the same issue. How in the world can this be fixed? I really don't want to return the phone as I like it very much
I'm rooted right now with stock rom but this has also occurred the first day (Totally stock)

This is happening to me as well and it's infuriating to say the least. I don't recall seeing the issue stock, it only seems to happen once I load magisk but I haven't fully tested that.
The issue is also usually preceeded by a reboot that gets stuck in the android one screen, meaning that I have to reboot the phone 3 times before it actually works. VERY annoying.
I think I'll re-flash the phone using the script that keeps my data and will run it stock for a few days to see if there's any difference.

Same here. I didn't experience a similar issue on 16.4 but there are other issues there. Hopefully when stable comes out, it'll work correctly.

I ran the phone re-flashed to stock yesterday and didn't run into the issue. The flashing process re-locks the bootloader so I think it's either:
1- Some issue with having an unlocked bootloader
2- Magisk 16.0 bug
3- Magisk 16.0 bug while bootloader is unlocked (I don't know if magisk can be installed but the bootloader re-locked after installing)

I had exactly the same issue on an Asus Zenfone 2. I was wondering if it was a sim card problem.

hacktek said:
I ran the phone re-flashed to stock yesterday and didn't run into the issue. The flashing process re-locks the bootloader so I think it's either:
1- Some issue with having an unlocked bootloader
2- Magisk 16.0 bug
3- Magisk 16.0 bug while bootloader is unlocked (I don't know if magisk can be installed but the bootloader re-locked after installing)
Click to expand...
Click to collapse
I did find the cause and how to fix it
The cause is the stock rom itself, It has issues regarding baseband but it doesn't happen to everyone and I don't know why
The only fix that I've found is to flash a custom rom.
I've been using aex rom for 2 weeks now and I haven't got a single issue so far

Related

[Q] Says Bootloader is locked when not. Bricked Nexus 4?

Around a week ago everything was force closing on my N4 so I decided to reboot it, when I did it got stuck in boot loops. Because of this I went to wipe the data and cache so I could flash a Rom but when I did all my data from my SD partition had disappeared. This has happened to me before and the way I solved it last time was to unroot and flash back to stock using the Nexus 4 toolkit. However when I went to do that this time it said my boot loader was locked so I couldn't complete the task. So then I unlocked the bootloader which apparently is successful but when I refresh the bootloader it seems to be locked again. Over the last week I have tried sideloading zips, force flashing, unrooting, unlocking the bootloader and all this on both a mac and windows toolkit.
When researching this problem I only could find one thread which resembled my problem on xda however it was about the Nexus 7 and the person ended up sending it back to Asus. Would be great if someone good respond, thanks!
(Also my device is a Rooted UK 16gb if that helps)
It sounds like your emmc flash memory is bad. Not being able to lock or unlock the bootloader is a sign of that. You should warranty the device.
I agree. I faced a similar problem on my Optimus 2X. It started with occasional bootloops, and last week it got to the point where it was boot-looping after every boot w/ force closes, missing data, and e2fsck did nothing, because the fixed errors came back within hours. Definitely sounds like your memory chip has called it quits.

Unstable & Unusuable

It sounds melodramatic but maybe someone else has encountered the same problem and can help.
I got my phone last week and used it for a couple hours before I decided to root and flash a custom ROM onto the phone. I didn't realize that the kernel had dmverity and proceeded to try and root my phone like any other phone.
I followed the usual steps in installing root for the first time. I used Odin to flash twrp onto the phone and proceeded to restart into recovery. I had forgotten to copy supersu to my phone before I restarted it and this is where my problems began. I swiped on the twrp page where it warns of dmverity but because I didn't transfer supersu I had to restart the phone and get it on. The problem being the phone was now stuck in a bootloop and I somehow managed to get supersu onto the memory and flashed it. I was able to boot into the rom but it was extremely unstable. I could work for maybe 5 minutes before the phone froze, got very hot, then shut down. It would go into a bootloop and succeed maybe 1/20 times, all the while the phone got very hot. I flashed a custom rom onto it and it kind of worked but would still freeze and restart every once in a while. I found the stock bootloader, rom, cp, csc, and flashed those. My phone is now stock everything but the crashes still occur frequently (basically every time I try to use it) and I'm at a total loss as to what to do.
I've rooted all of my phones since I got my S3 several years ago and I've never had a problem like this. Anyone know how I can fix this? My phone is model G935w8 so I know it has the exynos processor and rooting is possible, but I must've done something horribly wrong for it to be like this. Any help is appreciated.

S5 reboot issues

Hello, i will try to be as elaborate as I can cause I know you guys here are really knowledgeable when it comes to smartphones. So, here are the issues I am currently experiencing with my G900F phone. Just a background, everything in my phone is stock (rom, recovery, kernel) no changes done yet. It currently runs MM with a security patch of February 2017. As of now, I can't boot into the phone.
1. . I was able to successfully root it with CF auto root.
2. I started experiencing random restarts. I tried obtaining the last kmsg however it does not exist.
3. I tried flashing a new ROM thinking maybe there is some rare bug in the stock rom i currently have. I flashed TWRP via Odin, to be able to flash a new ROM. Odin successfully flashed the recovery however when i proceed to install a new ROM through TWRP the phone gets stuck in a bootloop. I do not experience this in the stock recovery
4. I was able to restore the phone through Smart Switch device intialisation. However, with everything stock I still experience the random reboots.
Bottomline: Is there anyway I can fix this on the software side (e.g. flash/update this or that)? And if not, do you think this is a hardware problem? Worth mentioning it's got a yellow screen bug but if i press hard on the back of the phone it disappears. Also, I can boot into stock recovery and download mode without any problems.
Thanks and sorry for the long post really need your insights.
Sorry you are having issues. I apologize if I missed this, but have you tried downloading the official firmware for your device from sammobile or similar sites, then flash that through Odin?

[Help!] N910T3 Strange Crashing/Bootloop - Crashes even while in Recovery

Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).

TWRP and LineageOS working fine. But I locked the bootloader after. Is this trouble?

After installing TWRP and LOS I unknowingly locked the bootloader.
I had the idea this was the course of action to protect your phone. Only after did I noticed messages saying not to lock it.
After that the phone automatically rebooted and TWRP apparently detected the problem and did something to fix things I suspect. It was too fast and I can't recall the details.
Anyway, everything works fine. Apart from the warning message during boot, that everyone also gets.
My question is:
Will this be a problem when upgrading TWRP or LOS? Or is there anything I should be worried about?
Thanks

Categories

Resources