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!
Related
I have an untouched HTC One M7 Google Play Edition phone that is stuck on Android 4.4.4. I am not sure what I should do at this point to get lollipop. I tried manually updating the phone by booting into recovery mode and selecting "Apply from phone storage". (I previously manually downloaded the update on the phone). This just quickly flashes "invalid operation" on the screen and the phone reboots. I see that there are many directions I can go from here, but I am not sure which one is best for my phone. I have concluded that Google has forgotten about me and I am not going to automatically get Lollipop. Incidentally, I bought my phone unlocked from Expansys and not from a Carrier. I am currently with Telus.
MZimbaro said:
I have an untouched HTC One M7 Google Play Edition phone that is stuck on Android 4.4.4. I am not sure what I should do at this point to get lollipop. I tried manually updating the phone by booting into recovery mode and selecting "Apply from phone storage". (I previously manually downloaded the update on the phone). This just quickly flashes "invalid operation" on the screen and the phone reboots. I see that there are many directions I can go from here, but I am not sure which one is best for my phone. I have concluded that Google has forgotten about me and I am not going to automatically get Lollipop. Incidentally, I bought my phone unlocked from Expansys and not from a Carrier. I am currently with Telus.
Click to expand...
Click to collapse
Anybody?
Hey all,
Looking for some assistance here. I apologize in advance for not having specifics on everything, but it's been a couple years since I've needed to do anything with this phone (SM-G900A). I picked it up used a couple years ago and shortly after, I did a NOX unlock and rooted the phone for two reasons - using Titanium Backup and to unlock the WiFi hot spot. I recently noticed that something had happened and my root access wasn't working correctly- guessing from one of the OTA updates that was attempting to occur on my phone. I say attempt, because I don't believe they ever successfully installed since they always seemed to error out. I'm currently on StraightTalk, not an AT&T customer. Something weird was up with it though, because I could never uninstall the Xposed Framework or app, yet Pokémon Go was recognizing it was rooted and blocking my access. I should also mention that I had towelroot running on the phone and it's showing the custom unlocked padlock on startup.
Fast forward to last night- I wanted to return it back to the stock ROM so I did my research, found a couple different tutorials that included the correct ROMs and applied one - G900AUCU1ANCE_G900AATT1ANCE_ATT.zip. After flashing, the phone will not boot and freezes halfway through the swirls around the Samsung logo, then goes blank. The blue notification light also stays lit on the phone.
Thinking it was most likely bootloader related, I found another ROM that included separate AP, BL, CSC files. I attempted to flash the bootloader, which failed and I got the following error on the phone - SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
At any rate, it seems like my boot loader somehow got corrupted or isn't compatible with this ROM, but I was hoping some of you experts out there could provide some answers. At this point my phone is dead, so I'm hoping I can get it restored very soon.
Thanks in advance guys!
The issue identified in this thread (http://forum.xda-developers.com/galaxy-s5/help/g900a-stuck-samsung-logo-black-screen-d-t3050369) seems very similar to mine as well as what's described on this website- http://www.galaxys5update.com/fix-black-screen-with-pulsating-blue-led-on-galaxy-s5-g900a/
I'm seeing the pulsing blue light as well. How do I find the 4.4.4 OA1 Kernel identified in the first link?
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 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.
I think I'm pretty much ****ed.
The thing is, I wanted to reinstall a stock version in my XT1900-6 but, in the process, I followed an old post here, and downgraded it to 8.0.0/OPSW27.57-40-14/19 (april 18 patch). The problem is, when I was running the script, I didn't pay attention that, at the end, the bootloader was being locked.
Now, I can't unlock it to flash another version.
When I try to go to Settings > Developer > Unlock OEM, the option is gray ("Connect to the internet or contact your carrier"). The thing is, I have no Wi-Fi nor my SIM card is working, only bluetooth is working.
I tried to update via sideload but I always get the error that adb wasn't able to mount the image and the code "Total xfer: 0.00x" in the cmd.
Is there some way to save my phone?
Well, im having the same problem too...
https://forum.xda-developers.com/moto-x4/help/locked-oem-grayed-t4002041