Related
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
GloryNation said:
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
Click to expand...
Click to collapse
tried to enter recovery, still not work. can't go to developer options because phone is stuck on logo, can't power off. couldn't find any solution that works anywhere, been searching for more than 6 hours, still no use. phone model is VNS-L21 forgot to mention earlier
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
GloryNation said:
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
Click to expand...
Click to collapse
I tried to install nougat update, computer recognizes it only in fastboot. holding volume buttons haven't changed anything still no progress. the thing is i had installed nougat a moth or so ago and it worked fine, then rolled back to marshmallow and now this. i'm pretty sure i tried to install correct package, because it was the same i had installed earlier
Did you download a adb tool on your computer that have the 'fastboot.exe' file? If so open that folder,
Have the mouse curser hover in that folder, hold down shift & right click the mouse
Open command prompt
Connect phone as is in fastboot mode
Type adb devices & press enter
Type adb continue & press enter
Hi,
I have the same issue as ellanyx.
my phone can only be stucked while booting or if I connect my phone to a computer, I'm able to boot it in fastboot.
as ellanyx, I didn't enable usb-debug nor OEM unlock option...
so when I'm in fastboot, I type the command "fastboot oem unlock xxxxxx" (hopefully the different data needed are the correct ones mentioned on the box of the phone) I get this error message:
C:\Users\Dieu\Downloads\SRKToolHuawei-STABLE-V1.3-20160619>fastboot oem unlock xxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
and off course the other options like "fastboot flash recovery recovery.img "... doesn't work.
I can't use the adb commands neither.
when I type the commande, as mentioned above, "adb devices" or "adb continue", nothing works.
So I'm a bit desesperate
do you have any solution for this kind of issue?
thanks
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
pyromana said:
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
Click to expand...
Click to collapse
Probably you didnt have correct Oeminfo for MM if dload method didnt work....Try to conect phone with Toolkit and follow procedure for flashing oeminfo and custombin, after that flash stock recovrry and b161 via dload metod. You will find it on forum here.
Regards
the procedure from SRK toolkit?
would it be possible to provide it? because I can't unlock the OEM and I didn't tick the USB debug think.
Maybe problem with the ps not phone so u can not connect with adb
Try with different pc you must have flash oem with fast boot without enable adb from phone if u in fastboot
I can only boot my phone in fastboot (vol- + power) and not in recovery (vol+ + power).
also when using the SRK toolkit, the first screen tells me to be sure that the usb debugging is enable, which I haven't done...
if I'm not mistaken, fastboot is to use the fastboot command and recovery the adb commands
the connection with fastboot works on my computer, the link is made. however when I type the command to unlock the OEM, I get an error stating that the command is not allowed.
when I use the SRK toolkit, with the different questions, he tries to connect the phone with adb and waiting.... waiting...
is there a command to reboot in recovery but from fastboot? in the otherway around it exists but it doesn't seem that from fastboot to recovery it exists.
thanks.
Alexxxx1 said:
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Click to expand...
Click to collapse
dload method works on N. I downgraded my phone from unofficial N update back to official MM update using this method yesterday. You just have to enable OEM at developer options on settings.
It looks like people can't be bothered to read the 1st post properly before they reply.
HE CAN NOT BOOT TO ANDROID SO HE CAN NOT ENABLE OEM OR ACTIVATE USB DEBUGGING!!!!
What he CAN do, is go into eRecovery and Fastboot.
With that in mind, I would suggest using the dload method through fastboot.
Also, make sure it is Huawei SRK Tools 2.0 that is used, as it actually asks if you are in debug mode or fastboot.
Note that there is a few bugs in SRK 2.0:
The TWRP recovery file has the wrong filename in the package, so it WILL fail unless you name it correctly.
Also, when trying to root, do NOT use the "P9 Lite" method as that WILL fail too. Use the "P9/P9 Plus" method.
I am trying to set up a complete guide that can restore the phone when it is stuck in fastboot, however I apparently went a step too far...
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken[/QUOTE
Do you have TWRP recovery ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
Click to expand...
Click to collapse
Boot into fastboot mode and flash a custom recovery by meticulus. Link : meticulus.co.vu
Then whenyou get stuck hold power and vol down button for 2 minutes the phone will reboot and then when it says that your device has been unlocked and cant be trusted then only press vol up key ( dont press power button then). The u get into huawei recovery. From that u should power off the phone. Now get a custom rom by meticulus into your device sd card ( Cyanogenmod 13 is recommended ). Then insert sd card in a powered off phone. Now press vol up and power key and flash gapps and custom rom and you are good to go.
Click to expand...
Click to collapse
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
SnowmanDK said:
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
Click to expand...
Click to collapse
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Arsaam said:
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Click to expand...
Click to collapse
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
SnowmanDK said:
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
Click to expand...
Click to collapse
Go to fast boot mode and from their try to flash meticulus recovery.
You can also try the adb method as well.
Visit meticulus.co.vu
Hello,
I have a Huawei P8 Lite (ALE-L21) phone with this error: FUNC 8 : HIFI Image, Error 1 Security Verify failed. I think I have tried everything to fix it but had no success, hence why I have decided to create this thread.
As you can figure out, the phone does not turn on, it only shows the huawei logo and shuts down. When pressing VOLUME UP + DOWN and POWER button, it used to show the HIFI image error screen, however when I press the key combination now, it only shows a red screen and turns off. I am able to enter fastboot and rescue mode by holding down the VOLUME DOWN button and plugging in a USB cable to the phone from a computer. Apart from that, I can't do anything else with the phone. (I do not have any software related to the phone installed (HiSuite), no backups, no nothing because the phone actually isn't mine and I have never actually played with it and androids in general.)
There are some similar threads and videos here:
https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-fastbootrescue-mode-t3648105
https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
https://forum.xda-developers.com/honor-5c/help/writing-recovery-failed-remote-command-t3584208
https://forum.xda-developers.com/p8lite/help/huawei-p8-blinks-red-green-green-red-t3546038
https://youtu.be/UYmDBD7t1iM
I have tried a lot of things to make the phone work again but nothing worked.
Recovery mode using HiSuite - "Your device is not supported for system recovery"
I have tried flashing different ROM's using fastboot - when I try flashing it says "FAILED - command not allowed", which I assume is beacuse the bootloader is locked?
installing a ROM using a SD card (Force update or something) - the red screen shows and the phone shuts down
Huawei Update Extractor - updating specific files e.g. boot.img, still not allowed to flash
TWRP - the same error ( not allowed )
Rollback to the previous versions using fastboot - not allowed
At some point I was able to wipe the cache on the phone, not sure if that matters anyhow.
When I am in the fastboot & rescue mode, there is a text in green saying "Phone LOCKED", which I assume means that the bootloader is locked? So, I was trying to get the bootloader unlocked, however found no success. I have also tried emailing Huawei support to get the bootloader code, however as you may know, they did not want to provide the code.
I was able to extract some information from the phone though, using these commands: https://forum.xda-developers.com/showpost.php?p=70483520&postcount=2
To get the bootloader code I have tried:
dc-unlocker - I think you need a working phone and have usb drivers installed for this to work and also I think you have to pay for this service
Kingroot + fastboot - https://forum.xda-developers.com/p8lite/general/alternative-method-unlocking-bootloader-t3799294
Emailing Huawei support for the code - they don't want to provide one
https://forum.xda-developers.com/huawei-p8/help/bootloader-unlock-unlock-code-huawei-t3792987
Does anyone have any suggestions on how to resolve the problem, or is it unsolvable? I would prefer to do it myself and not send the phone to Huawei or whoever as I would like to spend the least money possible. Also the warranty is long gone, since the phone has been bought in 2015.
Cheers
have you found any solution, i have same problem
Most likely the phone showning this kinds of errors is broken and can not be fixed by simple flashing operations.
Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).
Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?
So, basically I will make this short as possible
Due to some problems I had to sell my G6 Plus (Brazilian -8 model) but it was on a custom rom, and did the most dumb thing that I could do: Reflashing pure stock and locking it, I've used the LMSA tool then relocked in Fastboot, the thing is some files were corrupt and when locked, it doesn't boot up anymore, as i still had hope for it, I tried to LSMA again, but it doesnt recognize anymore, as the lock flag is now "Flashing_Locked", flashing manually via Fastboot gives a error related to the lock flag (also LSMA resets the device, so using my unlock key asks to enable OEM Unlock at settings, a impossible thing when OS is broken) , then searched for some solutions, first it was booting a Boot.img file from the last stock, which was the flashed one, it bootloops, then tried something on the recovery that works, but is the stock one and pretty limited, so the logical thing to do is flashing a OTA file, but only works for old versions that requires one version before the target one, so its a no go. The last thing i tried to do is booting TWRP, but it gets stuck on a red warning that indicates that system is corrupt. Then the last hope was EDL Mode, and thats the point where i want to go, i've bought a EDL Cable that's basically a green and black wire thing used on most Qualcomm based Redmi/Xiaomi devices, but it automatically boots to fastboot, so I need help to get EDL Test Points for this device, im with access to the board, i just need the right Pads to short-circuit it and blankflash it, so i can finally get it to work like normal again.
Schematics (for people who understands): https://androidfilehost.com/?fid=4349826312261726244
Any help is important, I'm sorry for some typos, english isnt my main language considering i didnt use translate
and please don't come with instructions like "have you tried LSMA?, try booting up the device and select oem unlock" because its clear that it doesnt work.
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Is there anyone on the platform who knows on this issue?
Or it's just a platform of Ads?
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
found some fix on a russian website, gonna translate it:
im gonna make a warning there off-script of the russian website, this is NOT guaranteed to work. if it doesnt, send it off for repairs.
what do you need to do this:
1 - fully charge the phone
2 - a working usb cable
3 - a computer with wifi on it (i can tell you have it since you likely posted it on the computer)
4 -you should have Mi flash pro
5 - a recovery image on chinese (WARNING: 1.9 GB, BE PATIENT)
6 - actually working braincells and hands ( you guaranteedly have em)
THE STEPS:
1 - Load in mi flash pro and register in it under your name (not always under your name)
2 - press recovery
3 - you should see a lightning bolt icon along with the IMEI of your device
4 - type in the path of the firmware
even if your device shows your system has been destroyed you can still boot into recovery.
5 - in your device boot into recovery
6 - you see connect with mi assistant? choose that option and confirm it
your device should direct you to connect the usb from your computer to your device
7 - After you setup everything you should see your device, if not, press refresh device, then you should see the flash button, press it
8 - and there begins the magic - wait 5-10 mins for the firmware to initialise, DO NOT DISCONNECT THE USB FROM YOUR DEVICE AT THIS POINT, IF YOU DO, YOU WILL SCREW IT UP AND HAVE TO DO IT ALL OVER AGAIN!
if you dont screw up and your device actually boots congratualtions! the power of xi jing ping has restored your phone to normal with a small drawback - its all in chinese
worry not, it doesnt end here:
9 - Unlock the bootloader AKA Unlock OEM (This is important, because otherwise you will brick yourself again and will have to do it all over again)
10 - boot your device into fast boot and flash the global firmware onto your device (the global firmware can be found on the same xiaomiui website you got the chinese firmware from)
i hope this lengthy guide helps
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
crud, i forgot the critical part:
it doesnt boot you to the average xiaomi screen, its the A1 model
at this point you need to use the ADB to flash the chinese firmware and unlock the bootloader on the chinese firmware, then flash the global one
though you can still use the same method i typed above
How's the progress so far?
Lamntox said:
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
Click to expand...
Click to collapse
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
arshad4u said:
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
Click to expand...
Click to collapse
Yup, the device is probs bricked
Have you tried the other methods i described?
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
Hi i dont have that kind of a problem!
my problem is when i try to do oem unlock it says error 0x1002 and idk what to do (i have same phone btw) i tried anything but nothing works!