Related
I am from India and I exchanged my iPhone 4S for a Moto X 2014 just this evening wanting to try my hands on the Android experience.
I do not know what the seller did to this phone but I now have two issues. I tried to call the seller immediately after I noticed these problems when I came home but the number is switched off. Shame on him!
After Google'ing I found this forum for android support so I hope posting the problems here would give me some solution
Problem #1: Every time when I boot my phone, it has the warning screen which says "Warning unlocked bootloader".
Problem #2: The warning went off and landed me on the home screen. I connected to my WiFi and saw that there is a software update. I downloaded it and chose to install it. It kept rebooting for 4-5 times and then said "System Update - Failed".
Can anyone please be patient enough to give me step by step solution with download links to get my Moto X2 back in shape as how it was out of the box?
I googled a lot for the keywords "relock bootloader moto x 2014", "unroot moto x 2014" and plenty of links with different download links came up. I do not know which one to trust. I am not dumb and I can easily follow instructions. So, please anyone wanna help?
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Nek0x90 said:
If the OTA (software update) is failing, maybe it's because the firmware you have was installed via custom recovery, not stock, or even the firmware is custom too, that's why you get a bootloop if you try to install the update.
Can you post a screenshot of your "About phone"? (Settings>About phone).
Click to expand...
Click to collapse
Thank you for the reply. Attached the screenshot.
i64.tinypic.com/2nu3asn.png
I fiddled around to find out how to get into the Fastboot mode... and I observed something weird there..
AP Fastboot Flash Mode (S)
60.16 (sha-#some checksum number key with date 2015-04-02 and time#
CPU: MSM8974AC EA1.1
eMMC: 2048MB Samsung RV=07 PV=0B TY=57
Battery OK
Device i UNLOCKED. Status Code: 3
Software status: Official
I mean Seriously? I see the word Samsung in a Moto phone? I so regret buying from this seller... too much for a first Android phone :crying:
Well I also managed to Google more and installed the device drivers and the Fastboot software in my Windows PC.
Booted my device in fastboot mode and issues the below commands:
fastboot devices
#my device was shown#
fastboot oem lock
#told me to use the command with begin#
fastboot oem lock begin
#Said something like the image is ready#
Nothing happened then though. I powered on my device and I still see that warning. Still the software update is failing. :crying::crying::crying:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Nek0x90 said:
You don't need to unlock your bootloader, it is already unlocked, that's why the bootloader says that the "Device is unlocked", but also says your firmware is stock (Status software official).
If your firmware is stock, I don't know why its failing to apply the update, maybe is because your phone has a custom recovery. Try to enter into that option in the bootloader and see what happens.
Click to expand...
Click to collapse
I am not trying to unlock my bootloader. I am trying to restore it back to the "out of the box" state. I mean I want to lock it and I want it to be in the state how it usually is when bought from the store.
Ok... I google'd how to go into the recovery mode and found this link (teamandroid.com/2015/01/08/enter-recovery-mode-moto-x/).
I followed those steps:
1. Turn OFF your phone.
2. Press and hold the Volume Down button for 2-5 seconds. While holding the Volume Down button, press the Power Button for 1-2 seconds and release.
3. I used the Volume down key to highlight "Recovery" and clicked on the power button to select it.
4. My screen went off. I mean the light gone.
Then I had to press and hold the power on button, it booted my phone with that warning unlocked bootloader message.
What am I doing wrong?
UPDATE:
I did a fastboot, connected phone to PC and issued the below command from PC and get below error:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
UPDATE 2:
I enabled the developers option (by tapping on the Build number multiple times)
So, I installed an app called MobileUncle Tools.
I then opened the app from my mobile and clicked on "Reboot into recover".
It says "Please root your Android first".
OK.. so looks like the phone is not rooted - which is good.
Only the bootloader is unlocked. All I need to figure out is - re-lock my bootloader and make the system update go through successfully.
Any help please?
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Nek0x90 said:
You must unlock the Developer Options in your phone, and then activate the debugger mode to be able to use adb commands like "adb reboot recovery".
In the About phone menu in settings, press five times the option of "Build number", then the Developer options in settings will be available. Navigate to that menu and activate the Android debugging option, then you should be able to use adb from a command window in your PC.
EDIT: Also, you have to press the up volume button in the bootloader to choose an option, not the power button.
Having the bootloader unlocked doesn't affect system updates via OTA or anything if your firmware and recovery are stock. Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery.
Click to expand...
Click to collapse
I have one question for you:
What do you mean by "Your firmware seems to be stock, so there's no problem with it, but I'm not sure about your recovery".
My understanding is - you are saying my stock firmware is intact because it said Official in the fastboot screen. Right?
Ok... now back to the recovery check... I think I did it.
1. I went in the fastboot mode
2. Used volume down key to scroll down to Recovery option (2nd option)
3. Pressed Volume up key to select it
4. The phone rebooted (The white screen "warning unlocked bootloader" message was displayed this time too)
5. I saw a dead android symbol with the word "No command."
6. I pressed Power and Volume Up key. I saw the recovery screen I guess. There were many options - Wipe data, Wipe Cache, Install from SD, etc.
What do I need to check there?
EDIT:
Ok I noted this number from there:
Android system recovery <3e>
LPE23.32-25.1
followed by the options
reboot system now
apply update from sdcard
etc.
I think this is what has happened:
Google says "LPE23.32-25.1" is the Android 5.1 Lollipop update (v23.16.1, build LPE23.32-25.1)
However, the current Android version on my device "About" screen is 4.4.4
The OTA system update, my device telling me about is Android 5.0 Lollipop version: 22.21.19.en.EU (which is a lower version than my recovery's version)
My menu options look all white and after google'ing I realize that it has Android L's menu. Please see the screenshot i65.tinypic.com/14l4mmb.png
Could that be that reason? What can I do t rectify it?
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
joseph_1802 said:
1) You most likely will want to keep your bootloader unlocked, since it'll give you more freedom to deal with roms and flashing. It won't affect taking OTAs, in fact, I've just taken the 6.0 OTA and my bootloader is unlocked.
2) Don't worry about the Unlocked Bootloader Message. That can be fixed by flashing the correct logo.bin file.
3) If your device is in KitKat (4.4.4) but your bootloader is from Lollipop (5.0 or 5.1), DON'T TAKE THE OTA. There's one post here saying that it'll cause a hardbrick. Your solution will be to manually flash the correct firmware or use RSD Lite.
Click to expand...
Click to collapse
THANK YOU SO MUCH for clearing that point 1 and 2. That is a relief!
Point #3 - "Your solution will be to manually flash the correct firmware or use RSD Lite."
What do I flash? OTA 5.1 (because my bootloader is from 5.1) or OTA 22.21.19.en.EU (because that is what I see in my phone's Software Update Available screen.
Where do I download those OTA files?
How do I flash using RSDLite? Any guide?
Thank you!
UPDATE:
Found the guide forum.xda-developers.com/showthread.php?t=2231249
I only need to know what I version I need to flash AND where can I download it from. Please?
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Nek0x90 said:
Best option is flashing the entire firmware of your phone variant using RSDLite. The firmware you're looking for (based on what Google says) is VICTARA_RETEU_XT1092_5.1_LPE23.32-25.3
Can you confirm this? If it's correct, then the firmware is in this folder (Firmwares 5.1 stagefright solved): https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Click to expand...
Click to collapse
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Flower07 said:
My recovery screen showed LPE23.32-25.1
So there is just the last number change... the download link you gave is for the version ending with .3 where my recovery shows .1
That should not be a problem, or should it?
Click to expand...
Click to collapse
No it's not a problem. This will give you the latest version with the stagefright patch.
Sent from my XT1095 using Tapatalk
It is .3 because it has the stagefright patch, the .1 version doesn't have that patch but both of them are basically the same, so there's no problem if you flash one or another.
"dm_verity not in restart mode" warning during boot (stock phone, update August 2018)
Hi all!
I am new to this forum and I have a question for you all. I am getting headaches trying to get a solution for the following warning.
During boot, after 2-3 seconds the following warning is displayed:
"the dm-verity is not started in restart mode. Wait for 3 seconds before proceeding."
The phone is at stock Android 8.1.0 with security patch August 2018. The phone is very unstable, it is restarting randomly and I think it has something to do with this warning?
Any ideas to solve this issue?
(Luckily it is my wife's phone , my 7+ is OK)
Thanks in advance!
Can you say, if the problem started out after updating to august? In any case, official Pie is near, so hopefully it should solve your issue. Dm-verity is a system level issue I think, and Pie update should completely overwrite the existing oreo; just make sure to factory reset afterwards.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Can you say, if the problem started out after updating to august? In any case, official Pie is near, so hopefully it should solve your issue. Dm-verity is a system level issue I think, and Pie update should completely overwrite the existing oreo; just make sure to factory reset afterwards.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Thanks for your reply.
The warning started to display after the July patch (I think). I believe it to be a kernel warning, but I don't know how to reset the restart mode. I tried to disable dm_verity using ADB, but it won;t turn off, because it is (or is not) a user build.
I am trying to flash the phone with te QFIL WW image, but with no success so far (The Qualcomm driver will not install automatically and I don't know which Qualcomm driver to choose (QLoader 9008?). Perhaps I'll open a niew tread about this question.
sbsoft said:
Thanks for your reply.
The warning started to display after the July patch (I think). I believe it to be a kernel warning, but I don't know how to reset the restart mode. I tried to disable dm_verity using ADB, but it won;t turn off, because it is (or is not) a user build.
I am trying to flash the phone with te QFIL WW image, but with no success so far (The Qualcomm driver will not install automatically and I don't know which Qualcomm driver to choose (QLoader 9008?). Perhaps I'll open a niew tread about this question.
Click to expand...
Click to collapse
Sorry I'm not much familiar with QFIL. But the unavailability of fastboot flashable firmwares is a real issue I think. Anyway, I hope you find a workaround for this [emoji106]
Broadcasted from Zeta Reticuli
sbsoft said:
Thanks for your reply.
The warning started to display after the July patch (I think). I believe it to be a kernel warning, but I don't know how to reset the restart mode. I tried to disable dm_verity using ADB, but it won;t turn off, because it is (or is not) a user build.
I am trying to flash the phone with te QFIL WW image, but with no success so far (The Qualcomm driver will not install automatically and I don't know which Qualcomm driver to choose (QLoader 9008?). Perhaps I'll open a niew tread about this question.
Click to expand...
Click to collapse
Sideload recent OTA zip from adb. may be it will help you or else in fastboot try following commands.
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
fastboot reboot
sarath medithi said:
Sideload recent OTA zip from adb. may be it will help you or else in fastboot try following commands.
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
fastboot reboot
Click to expand...
Click to collapse
Thanks Sarath for your awesome replies, help and understanding. You are helping me very much (even on the other thread "Which Qualcomm interface driver"...
Sideloading is not working because there is a version mismatch. It is already installed and it will not be loaded again.
Headaches again...!
It's a bit hard to make a screenshot...
I am totally stuck on this putting new flash roms/OTA/QFIL on my (wife's) phone...
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
FIXED
@RomLover1999: gave the tip to reboot without a sim card, and that seemed to have fixed the problem!
seend said:
Tried several times to do the update through the settings menu.
Everytime it reboots the screen stays black.
I can turn it on, it vibrates for half a second. I see the Android one screen and the screen turns black. So i tried holding the volume up button and power button but no Dev menu.
So I thought it was bricked but after a few tries it rebooted and says it can't install the update.
I've attached the screenshot of the issue. I've tried it 3 times. It redownloaded the update and failed again.
Any ideas?
Click to expand...
Click to collapse
did you tried a factory reset before updating
galardo_2 said:
did you tried a factory reset before updating
Click to expand...
Click to collapse
Nope, but just tried it and it didnt work.
Try booting without sim card
Same and via fastboot method same. Any solution? We need help its a one mi a2 more????
Unfortunately the error is not informative. I had this error when installing November update. The only way I found to see what went wrong is to check logcat during upgrade, but I think it requires root. In the end I flashed the OTA using fastboot. Still didn't get this update. Try opening shell from adb and reading logcat. I don't think anyone can help you unless we know what is 5he reason for failure
RomLover1999 said:
Try booting without sim card
Click to expand...
Click to collapse
Oh my, that worked! :highfive:
Why would something like that even work?
seend said:
Oh my, that worked! :highfive:
Why would something like that even work?
Click to expand...
Click to collapse
The november update has a bug in it that it only boots in english with a simcard inserted , other languages make the screen bug out ( at least that's what I had ) and only boot without a simcard
Worked greatly
Hey folks, just reinforcing the answer: removing the sim card before restart did the trick, the update went smooth.
Thanks @RomLover1999 and @seend
January update failed
Help! My phone is Mi A2 lite. I can't install January update. My phone is rooted and unlocked.
Thank you!
The same problem....
The same problem....anyone help?
nedjog said:
The same problem....anyone help?
Click to expand...
Click to collapse
did you unlock ? ever run TWRP/Magisk or similiar?
luminoso said:
did you unlock ? ever run TWRP/Magisk or similiar?
Click to expand...
Click to collapse
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
nedjog said:
Yes..it is unlock and never use TWRP/Magisk.. any sugestion please?
Click to expand...
Click to collapse
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
luminoso said:
I don't know, by I have the exact same issue, I've unlocked to enable camera2api and left it unlocked.
I'll take a look this weekend
Click to expand...
Click to collapse
Ok, my phone is not rooted.
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
luminoso said:
I was having the same issue. In the past I've unlocked in order to enable camera2api.
December/2018 (V10.0.2.0.PDIMIFJ) to January/2019 (V10.0.3.0) was failing via OTA.
This is how I solved it:
Download V10.0.2.0.PDIMIFJ dump from this thread
Reboot phone to Fastboot mode (vol down+power)
Run flash_all_except_data.sh or if you're in windowsflash_all_except_data.bat
In my case my environment is:
Linux Fedora 29
fastboot version c7815d675 from android-tools package (just make sure you have the latest fastboot)
Using original USB-C cable
After flashing and reboot the OTA update installed normally without any issues
Click to expand...
Click to collapse
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Mr.Krulez said:
When i try this it return me an erro rcho missmatching image and device what does it mean?
Thanks
Click to expand...
Click to collapse
I´m assuming you have xiaomi a2? it must match codename "jasmine"
luminoso said:
I´m assuming you have xiaomi a2? it must match codename "jasmine"
Click to expand...
Click to collapse
fastboot does say that my product is jasmine
Hello!
I just got this phone today and tried to update (8.0 November security update) and keep getting the same error!
I've tried with and without sim card, tried with and without my google acc, and tried with full battery!
Do not really want to unlock/install rom again... Any ideas?
I can not install the official standing rom.
I tried Fastboot, without a SIM card, flash everything in EDL mode and when I rebooted it vibrated 0.5 seconds, it stay on the logo, and it restarted, as well as again until it stayed in the logo.
I do not know what else to do.
The steps of the OTA with VPN don't work, bootlop and "couldn't update"
Factory reset too.
What else can I do?
It's Mi A2
Model: M1804D2SG
8.1.0
V9.6.17.0.0DIMIFE - 5 november patch
Hex Kernel installed, without root, and bootloader/critical unlocked.
Same here
Does anyone have a solution? Please?!? I've got the exact same problem.
8.1 works, but upgrade to 9 fails. I tried flashing 9 via fastboot, fails also.
Help!
Hello,
my mother came by today because her Xiaomi A2 doesn't work anymore. The smartphone doesn't start anymore. She put it in her pocket and when she took it out again, only the Fastboot logo came. I've restarted the smartphone now and it doesn't go any further than the white "Android One" screen. On the internet I read that this problem can occur with the January Security Patch or if you have a Micron DDR installed. The device still worked today at noon. Maybe the February Security Update was installed automatically.
Unfortunately my mother didn't make a backup of her pictures. Is there any way to get the pictures back or that the smartphone can start normally again? Possibly about fastboot?
The smartphone is not rooted and no bootloader (TWRP,...) was installed. This means that the device still has warranty. I know that I can send the device back to the seller, but I absolutely need the pictures.
I hope you can help me.
I dont think there is way to get the pictures but you can fix the phone tho
_matze__ said:
Hello,
my mother came by today because her Xiaomi A2 doesn't work anymore. The smartphone doesn't start anymore. She put it in her pocket and when she took it out again, only the Fastboot logo came. I've restarted the smartphone now and it doesn't go any further than the white "Android One" screen. On the internet I read that this problem can occur with the January Security Patch or if you have a Micron DDR installed. The device still worked today at noon. Maybe the February Security Update was installed automatically.
Unfortunately my mother didn't make a backup of her pictures. Is there any way to get the pictures back or that the smartphone can start normally again? Possibly about fastboot?
The smartphone is not rooted and no bootloader (TWRP,...) was installed. This means that the device still has warranty. I know that I can send the device back to the seller, but I absolutely need the pictures.
I hope you can help me.
Click to expand...
Click to collapse
the photos has not synchronized with the google account?
maybe you can try with some tool like this
https://www.wondershare.net/ad/dr-fone/dr-fone-android.html
(it is difficult but you can try)
to reset the device in stock etc you can try with test points & edl mode ...If you have guarantee, send it to service but the photos will be lost of course...
Thank you for your prompt reply. I looked at the dr. fon under Supported Devices. Unfortunately the Xiaomi mi a2 is not listed here. Could it still work?
_matze__ said:
Thank you for your prompt reply. I looked at the dr. fon under Supported Devices. Unfortunately the Xiaomi mi a2 is not listed here. Could it still work?
Click to expand...
Click to collapse
Really IDK....Can work may or may not.Not all devices in the list,the list is updated but many users do not add their devices
there are other such applications.hit on google search for example : "recovery data from android phone"
and you will see and others like that
I don't think I can save the dates anymore. At least not in this state. Maybe I still have a possibility afterwards. But I don't think so...
Now I want to restore the device. Unfortunately, this is not possible, because I do not come into the recovery mode. I keep Volume Up + Power Button pressed when starting the smartphone. Unfortunately absolutely nothing happens, except the white "Android One" screen. Am I doing something wrong? Is the recovery mode possibly broken? However, I come to the Fastboot mode. Unfortunately you can't get into recovery mode from here, right? The command "Fastboot reboot recovery" does not work.
_matze__ said:
I don't think I can save the dates anymore. At least not in this state. Maybe I still have a possibility afterwards. But I don't think so...
Now I want to restore the device. Unfortunately, this is not possible, because I do not come into the recovery mode. I keep Volume Up + Power Button pressed when starting the smartphone. Unfortunately absolutely nothing happens, except the white "Android One" screen. Am I doing something wrong? Is the recovery mode possibly broken? However, I come to the Fastboot mode. Unfortunately you can't get into recovery mode from here, right? The command "Fastboot reboot recovery" does not work.
Click to expand...
Click to collapse
Reboot on edl mode & flash stock rom via miflash tool
if your device can boot on fastboot
"fastboot reboot edl" (need unlocked BT)
https://forum.xda-developers.com/showpost.php?p=78963902&postcount=6
from test points > edl > miflash tool (not needs unlocked BT)
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
(the better solution? If you have a warranty send it to service...All this needs some experience)