Related
Hi,
I have a Vodafone (UK) branded Desire Z which today froze whilst I was using it. This left me no option to remove the battery and re-insert it to clear the phone.
Unfortunately the phone will not fully boot now - all I get is the standard HTC screen, followed by the Vodafone logo screen. It then goes black and restarts.
I have tried removing the battery and leaving it for a while before reinserting. I have also removed and replaced the sim and the SD card, but still no joy.
Is there a 'safe mode' way of booting the Desire Z that I could try or has my phone just died?
Any help gratefully received.
http://forum.xda-developers.com/showthread.php?t=842495
Hi again,
Thanks for that link - I have read and re-read as suggested and attempted to follow the instructions but the second link (cwm recovery) is dead - it takes you to a 'removed by mod' post, so I didn't get far!
Just to give a bit further info, I took my device into a local 'fone doctor' shop, where they managed to fix it (or so I thought! - cost me £22 as well! ). The phone was back with the stock HTC Sense on it.
Anyway, within about three hours of the phone working, it froze again - and is now back to being stuck on the White HTC boot screen (rather than the looping it was doing previously). I have a feeling that my phone may just be knackered!
If I do the hold volume and switch on thing, I get the following:-
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
Apr 11 2011,23:36:27
....plus the usual HBOOT, FASTBOOT, RECOVERY options etc.
To confirm, I have NEVER rooted my phone. Up to the point it originally froze it had only had the official over the air updates.
I do have HTC Sync installed on my PC, so all of the required USB drivers should be available.
I also have the Android SDK installed (I have dabbled in development) so have adb.
I have read many posts over the last couple of days, but the majority seem to say that if you have "S-ON" you could well be screwed.
Also, adb does not seem to recognise my phone - I have no idea if I had "enable USB debugging" checked or not - again, if this was not the case then I fear I could be screwed!
If anyone has any further idea's of how I could possibly bring my phone back to life it would be hugely appreciated.............or should I just give up and look to get my old G1 unlocked?!
Many thanks.
ok ...you can´t reach your phone with adb if your are not booted into a rom.
do you have fastboot installed on your pc?
if yes then enter fastboot menu (power & tp) and then type fastboot devices on your pc...
your device should be listed.
then type fastboot oem boot and if you are lucky your phone boots again
EDIT: or push power & volume+ to enter recovery and wipe cache or do a factory reset... and do some researching about emmc chip
Many thanks hoffmas. I managed to run the fastboot commands you mentioned which did indeed force a reboot, but unfortunately only back to the white HTC splash screen.
The output from the commands was:-
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot devices
XXXXXXXXXXX fastboot
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is VODAP001
(bootloader) setting->cid::VODAP001
(bootloader) serial number: XXXXXXXXXXX
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =497
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.04.03_M androidboot
(bootloader) .cid=VODAP001 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=VODA-UK androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0BERT06529 androidboot.bootloader=0.85.0013 zygote_oneshot=o
(bootloader) ff kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:66802 msec
FAILED (status read failed (Too many links))
finished. total time: 8.078s
I am guessing that the "FAILED" line at the bottom is another way of saying "Sorry Mate, your phone is knackered!".
I also tried selecting "Recovery" from the menu - that brought up a black screen with the two green arrows around the device picture. This lasted for about 10 seconds, then the phone vibrated about 6 times and went totally blank again - no reboot, no splash screen nothing.
When I try and select the "Factory Reset" option, nothing happens at all. I can move up and down to it using the vol keys, but when I click the power button to select it, nothing happens.
Thanks for all the suggestions anyway - I guess I'll have to get the trusty old G1 unlocked.
I don't think I'll ever tie myself into a two year contract again - bit annoying to be paying for two years when you only get 13months out of the phone!
sry to hear that it didn´t work... but delete the serial number of your phone in your posting.
maybe there is a way to use fastboot for factory reset... but i don´t know how :S
ok... this should be the commands:
fastboot erase userdata
fastboot erase data
fastboot erase cache
Thanks again hoffmas - unfortunately when I run those commands I get this:-
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.016s
Not looking good.
I'm guessing the "FAILED (remote: not allowed)" means pretty much nothing will work.
Thanks again for your help - it is much appreciated.
yes you are right... looks like you need eng hboot to do this
sry, but i have no idea what else you could try... maybe someone else knows better
Hi,
Earlier on today I was trying to root my phone (Well at least put TWRP on so I could mount a rom) and somehow the bootloader got locked during the process this has prevented me to install any roms....
I know it's locked because of -
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.079s]
finished. total time: 0.080s
I've tried to recover it back to normal during the "Fastboot Mode" state but not had any luck I believe the phones bricked? -
C:\Users\Liam\Desktop\One Plus Recovery\A2001_14_A.03_150805>fastboot flash user
data userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
I need this sorting as I don't have a phone to use, and would really apreiciate if someone could help me as i've spent like 8 hours today trying to sort it but not had any luck i've downloaded drivers (Qualcom), Android SDK, this Qualcom-download-tool for recovery and nothing seems to work
It will only boot into "Fastboot Mode"
i recommand you to ask this on OnePlus forums there is more people that answer
otherwize did you tried fastboot oem unlock and is your phone recognize by your computer ?
Use the Qualcomm recover method mentioned many times over in this forum.
try fastboot oem unlock.
did u enabled oem unlock option in dev settings while unlocking bl?
what exactly steps you followed?
Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you
adavies said:
Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you
Click to expand...
Click to collapse
First of all, "adb devices" doesn't work on the bootloader. The adb app only works in recovery or while booted into the system. Secondly, is your bootloader unlocked? How you proceed depends on that. If you still want to install Nougat there are a couple of options. Let me know your current bootloader status. Above all, don't panic and do something rash.
Here is a link to your phone's stock firmware" https://www.filefactory.com/file/5c...24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip
Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.
Also thank you for the link to the firmware, I just checked and this is the same file that I already downloaded so I do at least have peace of mind that I selected the right one.
Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.
_wyrm said:
Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.
Click to expand...
Click to collapse
Hi, thanks for your reply, sadly I have tried all the options from the bootloader with no success, they do the following:
START - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
RESTART BOOTLOADER - Just takes me back to the same bootloader screen immediately
RECOVERY MODE - Takes me back to android man fallen over with 'No command' underneath
POWER OFF - turns it off (obviously lol)
FACTORY MODE - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BARCODES - displays white screen with four barcodes relating to IMEI, SKU, DATE and SERIAL NUMBER
BP TOOLS - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
QCOM - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BOOTLOADER LOGS - Doesn't do anything when I click the power button on this option but shows some yellow text on the screen that says 'Fastboot reason: Volume down key pressed'
That is all the options I have then, none seem to resolve the problem.
Thank you
Also, I'm not sure if this is relevant but when I ran the flashstock.bat file to try and install the files from XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml, I noticed as the text scrolled up the CMD window that there was several mentions of:
slot count not found
slot suffixes not found
has-slot system not found
invalid signed image
These lines appear several times, I'm not sure if this is part of the problem or not. If the CMD window didn't automatically close I would have copied and pasted exactly what it says.
Thanks again
Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.
adavies said:
Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.
Click to expand...
Click to collapse
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
_wyrm said:
Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.
Click to expand...
Click to collapse
Hi, thank you for your reply, I just downloaded and tried the RSD Lite software. It detected my phone on Port number 1 as 'Fastboot athene_13mp S' and I selected the 'flashfile.xml' and pressed start. Unfortunately it stopped with the status 'Failed flashing process. 3/27 flash partition "gpt.bin" -> Phone returned FAIL.' Does anyone know how to get round this?
Thank you
pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
]
Click to expand...
Click to collapse
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.
adavies said:
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.
Click to expand...
Click to collapse
Did you manually flash the fastboot images in the sequence provided?
If that doesn't work, I would send it back to Motorola. If it isn't in warranty, well, rip.
pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
I do still get the serial number when running 'fastboot devices', do you think unlocking the bootloader might be the answer? I went through te steps yesterday to get the code, was a little put off by voiding the warranty though. With regards to running the commands one at a time, I think I am now getting a bit confused on the correct procedure of where to run the commands from. I have tried running it from the folder for 'Minimal ADB and fastboot' (this folder contains all the files from the stock firmware folder as well which I copied and pasted in there) and also directly from the stock firmware folder itself. I will paste the results of each below (sorry to confuse the issue, my head is fried now, lol).
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.049s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I stopped after the second line as the text above suggests to me that part has failed so no point continuing. When running directly from the firmware folder I get the following :
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot devices
ZY223H6QF4 fastboot
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.062s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>
Again this seems to fail also but with some slightly different messages. Interesting that it failed on the gpt.bin part as this was also mentioned when it failed on RSD Lite.
If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.
_wyrm said:
If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.
Click to expand...
Click to collapse
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.
adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
AFAIK, this one isnt safe to skip.. Im out of ideas, sorry. Try another usb cable just in case.. but if it keeps failing at the same point you will probably need to send it to motorola service.
pastorbob62 said:
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.
Click to expand...
Click to collapse
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.
negusp said:
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.
Click to expand...
Click to collapse
You may be right. He has not successfully unlocked the phone so therefore his warranty should still be good.
---------- Post added at 04:18 PM ---------- Previous post was at 03:51 PM ----------
adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
I don't understand why you can't flash the stock ROM. Your baseband version is still on stock. That said if you want to continue trying give this a shot: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943 This will bring you up to Nougat the latest release. It does not require an unlocked bootloader and has been used on your model.
Or here: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
Otherwise I would go ahead and do a warranty return. Your warranty should still be okay since you did not go through with unlocking the bootloader.
Click to expand...
Click to collapse
So here's my story.
V20 Bootloader unlocked via LG's web site.
US996 version 10f
DEveloper and usb debugging enabled also side load usb.
USB set to photo transfer.
This one setting has me wonder under getvar all (bootloader) secure:yes
I boot into fast boot by plugging in usb cable while holding volume -
Issue the following commands below first to verify device then to flash .(Basically I renamed twrp-3.0.2-1-us996.img to recovery.img)
It then says finished after flashing recovery, I unplug the usb cable and pull the battery.
Put battery back in, hold down volume - and power button. LG splash comes up, I release then
press the power button.
From there I get a white factory reset data sreen.
I feel like I'm missing a step yet I don't.
All suggestions welcome.
My goal is to flash TWRP then Magisk.
c:\adb1>fastboot devices
LGUS99636487ef4 fastboot
c:\adb1>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4d000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xced000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x180000000
(bootloader) serialno:LGUS99636487ef4
(bootloader) kernel:lk
(bootloader) product:MSM8996
(bootloader) unlocked:yes
all:
finished. total time: 0.200s
c:\adb1>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (24076 KB)...
OKAY [ 0.588s]
writing 'recovery'...
OKAY [ 0.251s]
finished. total time: 0.839s
If you have flashed TWRP onto the recovery partition you can go ahead and continue with the "factory reset". Typically this would issue a factory reset using the stock recovery image, but if you have TWRP it'll just take you to TWRP instead.
Just be sure to flash TWRP in fastboot and then immediately factory reset to enter TWRP. Once in TWRP make sure to "allow modifications". This will prevent the stock recovery from returning. If you boot into the system without allowing TWRP to "modify" the system (remove the stock recovery restoration) it will reset your recovery back to the stock on system boot. If the stock recovery ends up restored and you issue a "factory reset", it'll actually factory reset.
Nut, you effin rock.
That was it, Twrp and rooted woo-oo!!
Was there another step for safety net to work?
landude said:
Nut, you effin rock.
That was it, Twrp and rooted woo-oo!!
Was there another step for safety net to work?
Click to expand...
Click to collapse
You're welcome! Great to hear it all worked out.
No extra steps for safety net. Just install the latest Magisk (14.0) and you should pass safety net without issue. The magisk manager application can do a check for you to verify you pass.
And it did! Thanks again!
landude said:
And it did! Thanks again!
Click to expand...
Click to collapse
I'll be receiving a US996usatn by the weekend and I'm trying to get the process down. I'm getting confused with all the dirty santa, dirty elf, and recowvery stuff.
In my case, I believe none of that is needed, correct?
Did you flash the "no-verity" zip at all in your unlock and root process? I'm not sure what it is or if it's needed with the US996.
What I think should be done (please correct if I'm wrong):
Unlock BL thru LG dev site instructions
Flash twrp
Boot twrp with button combo
Factory reset white screen>yes
Swipe to Allow modification
Wipe data
Flash Magisk or SU
Done?
From all that I've read, your original post made the most sense to me and hopefully is the only method I need to know to root.
Old thread: Unrooting gives me bootloop?
Hi there everyone,
After upgrading to Oreo, I unlocked my bootloader, flashed TWRP and Magisk. After that I did a backup of my System and Boot partitions on my currently active slot B. For some reason Slot A doesn't really boot up, so I don't really know what's up with that.
The problem is, before rooting everything was perfect and after the root I feel the instability. I've been using rooted devices for years now and I've never really had problems with the stock ROM being rooted.
So how do I unroot? Well, it's as simple as clicking Complete Unroot in Magisk. Yeah, that bootloops. Trying to flash MagiskUninstaller zip? That bootloops too. The only thing that saved me from those bootloops was that backup I did with TWRP. Yeah, that was after Magisk already had take a crap on my boot image.
Any suggestions that don't involve me losing my 30 Gigs of precious data? I would like to try with Mi Flash Tool but I'm scared from bootlooping for long periods of time (I don't have all day, after all).
New question: How to lock bootloader without wiping?
Hi there again!
I tried flashing the original system.img and boot.img from a fastboot Oreo ROM I found online. I just wanted to lock my bootloader, since currently I don't really need Root access anymore and I don't want this poor security a phone with an unlocked bootloader brings. The problem is, when I type fastboot oem lock it doesn't want to boot anymore, even without Magisk.
Does anybody know a fastboot ROM out there that can be locked? At the official MIUI.com website the fastboot ROM hasn't been updated for a very long time and I don't want to wipe my data. Does anybody have a perfectly working Oreo image that can be locked?
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
_mysiak_ said:
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
Click to expand...
Click to collapse
Thank you very much for the help! I'm gonna try this now. I'm pretty new to this A/B partitioning scheme, I knew that there isn't a recovery partition but I didn't know that TWRP is stored in Boot.img
Thanks again! Have a wonderful day/night!
_mysiak_ said:
It bootloops, because you:
1. installed TWRP (first mod of boot.img)
2. installed Magisk (it backed up your boot.img with TWRP already installed)
3. when you uninstalled Magisk, you effectively restored boot image with TWRP, which as far as I know doesn't disable dm-verity which in turn doesn't allow boot of modified system/boot image
The safest method of unrooting is to flash stock Oreo boot.img directly via fastboot. Next time try to avoid installing TWRP (it's not needed for installing Magisk). Don't try to flash Nougat system, your data can't be read by old system anymore.
For a quick solution it should be enough to install Magisk again.
Click to expand...
Click to collapse
Hey there again!
I tried to boot from the stock boot.img but it bootloops again! The backup from before is, again, what saved me.
Am I stuck now? Is there something wrong with my system.img? Or my /data partition? I'm scared of even reflashing clean.
nicolasmart said:
Hey there again!
I tried to boot from the stock boot.img but it bootloops again! The backup from before is, again, what saved me.
Am I stuck now? Is there something wrong with my system.img? Or my /data partition? I'm scared of even reflashing clean.
Click to expand...
Click to collapse
Which stock boot.img exactly did you use?
_mysiak_ said:
Which stock boot.img exactly did you use?
Click to expand...
Click to collapse
The one from the Oreo fastboot ROM. Got it from here.
nicolasmart said:
The one from the Oreo fastboot ROM. Got it from here.
Click to expand...
Click to collapse
When you ran TWRP for the first time, it asked you if you want to allow system modification (mount as R/W) - did you allow it? If yes, it has tampered your system partition and you won't be able to boot with stock boot.img due to dm-verity. Either install Magisk again or reflash stock Oreo system.img (from the link you provided).
_mysiak_ said:
When you ran TWRP for the first time, it asked you if you want to allow system modification (mount as R/W) - did you allow it? If yes, it has tampered your system partition and you won't be able to boot with stock boot.img due to dm-verity. Either install Magisk again or reflash stock Oreo system.img (from the link you provided).
Click to expand...
Click to collapse
OK, I can reinstall the system.img and boot.img via Fastboot. It won't delete any data, right?
Edit: Thanks for all your support again! You're the saviour of my Mi!
nicolasmart said:
OK, I can reinstall the system.img and boot.img via Fastboot. It won't delete any data, right?
Edit: Thanks for all your support again! You're the saviour of my Mi!
Click to expand...
Click to collapse
Your data is safe as long as you don't run incorrect command (DON'T flash userdata.img and DON'T run fastboot command with "-w" switch)
fastboot flash boot boot.img
fastboot flash system_a (and/or system_b) system.img
and you are good to go. Don't panic when system flashing will appear as stuck, it takes some time while it splits 3gb file into 6 smaller ones and starts the actual flashing.
_mysiak_ said:
Your data is safe as long as you don't run incorrect command (DON'T flash userdata.img and DON'T run fastboot command with "-w" switch)
fastboot flash boot boot.img
fastboot flash system_a (and/or system_b) system.img
and you are good to go. Don't panic when system flashing will appear as stuck, it takes some time while it splits 3gb file into 6 smaller ones and starts the actual flashing.
Click to expand...
Click to collapse
Thank you! But why should I run fastboot flash boot boot.img?? Isn't it fastboot flash boot_b boot.img? I'm on slot B currently.
nicolasmart said:
Thank you! But why should I run fastboot flash boot boot.img?? Isn't it fastboot flash boot_b boot.img? I'm on slot B currently.
Click to expand...
Click to collapse
You are right, for restore you should "fastboot flash boot_b boot.img". I was probably thinking about rooting procedure where you should use "fastboot boot boot.img"
_mysiak_ said:
You are right, for restore you should "fastboot flash boot_b boot.img". I was probably thinking about rooting procedure where you should use "fastboot boot boot.img"
Click to expand...
Click to collapse
Well, I did all that and I now have a perfectly working system with stock recovery and I think it doesn't boot loop anymore with a stock boot image. Thank you!
However, I tried to lock my bootloader via fastboot oem lock, the first time I was using some shady boot image which should be "stock" but it really wasn't, and it said "The system has been destroyed." I really laughed at this label and went into fastboot to unlock my bootloader again. I switched the boot image to a legit one which has Magisk installed, tried to lock again but this time it flashed the Mi logo for a split second and then a dark screen appeared (can somebody please explain this weird behaviour?). I really scared because the PC wasn't detecting the phone but I held the Volume Down + Power buttons for 10 seconds hoping I will see the Mi Bunny on the Fastboot. Yeah, it worked. I unlocked the bootloader again (lol) and my phone was working again!
Don't worry! My phone's still OK and 100% functioning.
The only reason I tried to lock my bootloader with Magisk installed is because somebody said it worked for them. However, now I realize how risky would that be. Whenever an OTA appears you should hope you don't get locked out of your phone.
So, people with a rooted Mi A1 - don't lock your bootloader unless you fully unroot and revert to stock!!!
How can I lock my bootloader again without wiping? (See the updated first post for more information)
nicolasmart said:
How can I lock my bootloader again without wiping? (See the updated first post for more information)
Click to expand...
Click to collapse
Just wait for an official Xiaomi fastboot Oreo ROM and either use MiFlash or included script "flash_all_except_storage.bat". It will lock bootloader at the end of flashing procedure. Though you probably won't gain much added security as you can unlock the bootloader without data wipe at any time (some reports say that you even don't need "allow oem unlock" in developer settings, but I haven't tried that).
nicolasmart said:
How can I lock my bootloader again without wiping? (See the updated first post for more information)
Click to expand...
Click to collapse
For more detailed instructions have a look over here: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
flash_all_except_storage = Keep your data, bootloader gets re-locked is the variant you are looking for.
Please keep in mind, that downgrading is not recommended. So this solution is absolutely fine when you are at 7.12.19 or below.
If you are not, you have to wait for the next fastboot update package to become available (like me)
It’s better to do a clean flash using the ROM and MiFlash provided on Xiaomi Website to ensure that the system is unmodified and you won’t get errors or bricks during a future OTA.
I don't want to clean flash. It will take forever for Xiaomi to release the new fastboot ROM
nicolasmart said:
I don't want to clean flash. It will take forever for Xiaomi to release the new fastboot ROM
Click to expand...
Click to collapse
Fastboot ROM should be out in a couple of days, usually it's released one week after first OTA update (the one from 19th December was online on 26th or 27th if I remember correctly).
Edit: Clean flash is not necessary, only full flash of all stock images, except user data.
_mysiak_ said:
Though you probably won't gain much added security as you can unlock the bootloader without data wipe at any time
Click to expand...
Click to collapse
As an old Nexus user (Nexus 7, Nexus 7 2013, Nexus 5X) I was shocked when I have found this.
_mysiak_ said:
(some reports say that you even don't need "allow oem unlock" in developer settings, but I haven't tried that).
Click to expand...
Click to collapse
Even this is true for Mi A1 in Nougat and Oreo too. So two critical security omissions by XIAOMI. One must ask himself if it is bug or strange feature
Code:
Developer options / OEM unlocking
Alow the bootloader to be unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.073s
C:\>fastboot oem unlock
...
OKAY [ 0.153s]
finished. total time: 0.158s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.073s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
Developer options / OEM unlocking
Bootloader is already unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot oem lock
...
OKAY [ 0.088s]
finished. total time: 0.091s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\>
_jis_ said:
As an old Nexus user (Nexus 7, Nexus 7 2013, Nexus 5X) I was shocked when I have found this.
Even this is true for Mi A1 in Nougat and Oreo too. So two critical security omissions by XIAOMI. One must ask himself if it is bug or strange feature
Code:
Developer options / OEM unlocking
Alow the bootloader to be unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.073s
C:\>fastboot oem unlock
...
OKAY [ 0.153s]
finished. total time: 0.158s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.069s]
finished. total time: 0.073s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
Developer options / OEM unlocking
Bootloader is already unlocked - option is switched off
C:\>adb devices
List of devices attached
******** device
C:\>adb reboot bootloader
C:\>fastboot devices
******** fastboot
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot oem lock
...
OKAY [ 0.088s]
finished. total time: 0.091s
C:\>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.070s]
finished. total time: 0.074s
C:\>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\>
Click to expand...
Click to collapse
Thanks for the confirmation. I consider it as a serious security flaw and was really surprised as well. I would like to know Xiaomi's reason to do it this way.. Users should be aware that they have to keep data encrypted with good PIN/pattern and request it on each boot to keep information secure.