I had this issue after I downloaded and flashed the most recent factory image for my Moto G5S Plus (XT1806) from this post: https://forum.xda-developers.com/showpost.php?p=76070231&postcount=24. At the time, it was NPSS26.116-48-12, build date March 1st.
The restore succeeded after following these instructions, except after the restore, my Wi-Fi was broken. Mobile data and other connections worked (not sure about Bluetooth), and the Wi-Fi MAC address was shown as 02:00:00:00:00. I tried re-flashing the modem and fsg partitions and erasing the modemst1 and modemst2 partitions, but it didn't fix my issue. Reflashing everything from scratch using the same image also did not help.
I was only able to solve the problem by flashing an older image entirely from scratch, specifically NPSS26.116-48-9 with a build date of January 11th. After that, the system showed the correct Wi-Fi MAC address and prompted for an update to the latest OTA release after setup.
I hope this helps someone avoid the panic and troubleshooting I went through.
Edit: Basically just putting this here because past me panicked and ended up following his own guide to fix a separate but related problem. Future me can sometimes be an idiot but I'll be him someday so I really shouldn't talk **** about him. Future me would be really angry at current me if I didn't at least write down the steps past me took to fix my latest problem.
The issue: OTA updates were failing because my /system partition had been mounted read/write in TWRP before taking the backup. As a result, no updates would install.
Solution: Go through the instructions linked in the above topic, ignoring any Preflash validation failed errors while flashing gpt.bin. At this point, the phone boots up clean but with no IMEI. Check for and accept every OTA update available. Once updated to Oreo, IMEI reappears.
Hey buddy, i'm facing the same problem. i was able to restore my mac address but after a while phone reboots and the mac address again resets to 02:00:00:00:00
I followed every step mentioned in the post correctly and also tried custom rom's but still no permanent solution.
any help would be appreciated.
Thank you
Related
Possible fix for unknown baseband
Hey everyone!
So yesterday my phone was running normal and all was fine! Then out of no where it softreboots everytime it loads into android.
Logcats didn't really show anything, Dmesg did though, it was showing that my radio was crashing and then noticed the all information related to baseband imei and cell networks was unknown.
So I did some research and people were saying that the persist partition corrupts itself. No known reason as to why but I then remembered the our efs partition is related to that partition.
So after all of this I remembered I had a complete back up of the android L I have been helping with. I factory restored back to complete stock flashed twrp and copied over my twrp back up. I did this while at the beginning of the setup wizard. I then rebooted back into twrp made sure my backup was showing. I then restored only the efs partition.
I restarted the phone and BOOM it works again.
So my main point is always have a backup of everything safe and put away. and if you end up having the baseband unknown issue restoring efs will fix it
Thanks!
To be honest not much new here, backup efs once and store it somewhere, but most of the time a cache reflash/wipe solves the issue if it happened randomly.
ふかつどう
Well wiping/reflashing cache many times didn't help at all. I only posted because I have seen a lot of people with the same issue and never found a fix.
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?
I recently upgraded to EMUI 5.0 but it was a little buggy so I decided to downgrade.
I found this website that I can't show because this website won't let me put it in, that 'showed' me how to downgrade back to Marshmallow but as I was doing it my device for soft-bricked and now I am in a boot loop and none of the recovery options work. Also cannot erase all data (it fails every time I try)
I would be really happy if I could get my phone back to how it use to be.
P.S. I have a backup of all my files so I don't mind what happens to my data on the phone.
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.
Hello. Noob here. A few years ago I bought used XZ1 Compact which had the green screen camera problem, and you couldn't receive calls. Seller also told me that bootloader is messed up. I flashed the phone with Emma, and everything started functioning. I used the phone for ~3 months, and one day it just lost almost every info about itself. IMEI, Wi-Fi mac address, bluetooth, baseband, prob gps as well. I started searching online for info and I came to conclusion that the chip maybe lost it's contacts with the board and that I would need to cook it in the oven. I have just put in the drawer, and took a backup phone, and didn't come back to look at it until few days ago.
I tried flashing the firmware with Emma, Flashtool, newflasher, TWRP with at least 10 different firmwares that I could find, flashed kernel, installed Lineage OS 18.1, tried to root the phone with Magisk 22 and confirmed that the phone was rooted with Root Checker 6.5, yet I wasn't able to get access with ES file explorer, adb, or Flashtool. I tried also Magisk 20, but the OS didn't see it was installed. I wanted to try things suggested in these 2 links https://nerdschalk.com/fix-empty-im...d-wifibluetooth-issues-restoring-twrp-backup/ , https://romprovider.com/repair-imei-qualcomm-snapragon/ , but since the phone wasn't really rooted I couldn't get the access to some files so couldn't really say if these how to guides would fix my problem. I did delete modemst1 and modemst2 through twrp, but that didn't help.
I probably lost attest keys in this whole process. I did manage to get Bluetooth to work, I think I got some baseband info in some of the instances, and Wi-Fi mac address moved from unknown to 02:00:00:00:00:00. I can read my (at least I think it's mine) IMEI with Emma, and Wi-Fi MAC address with Emma, Flashtool or adb (not sure which one).
Can someone tell me if there is any hope for this phone? I really hate throwing things that can be fixed in the garbage, but I think I'm loosing too much energy to try to save this phone from becoming waste.