Database Develop

Stuck in Fastboot Flash Mode PLease Help

Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?

It's stock, locked and unrooted. All you did was try to install their OTA right? Sounds like their fault to me.

Calleja said:
Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
Click to expand...
Click to collapse
you are going to have to flash a factory image

simms22 said:
you are going to have to flash a factory image
Click to expand...
Click to collapse
But how if the Rootkit can't? I can't seem to be able to flash anything to the device :/

Calleja said:
But how if the Rootkit can't? I can't seem to be able to flash anything to the device :/
Click to expand...
Click to collapse
rootkit is nothing official and only has in it whatever the developer has in it, flashing a factory image is why we have fastboot. if the rootkit cant do it, fastboot can. anyways, new users, newbs, should never be using root toolkits.

simms22 said:
rootkit is nothing official and only has in it whatever the developer has in it, flashing a factory image is why we have fastboot. if the rootkit cant do it, fastboot can. anyways, new users, newbs, should never be using root toolkits.
Click to expand...
Click to collapse
I wouldn't consider myself a newb, I've used fastboot and adb to flash factory images before. I used the toolkit in this instance because googling around made the toolkit's Soft Brick option seem like my best bet. It did not work.
How do I do that if the Fastboot Flash Mode seems to be borked/soft bricked and I can't seem to unlock the bootloader?

Calleja said:
I wouldn't consider myself a newb, I've used fastboot and adb to flash factory images before. I used the toolkit in this instance because googling around made the toolkit's Soft Brick option seem like my best bet. It did not work.
How do I do that if the Fastboot Flash Mode seems to be borked/soft bricked and I can't seem to unlock the bootloader?
Click to expand...
Click to collapse
because before unlocking the bootloader, you have to enable the developer setting. if your bootloader is still locked, then there is nothing that you can do except try to get a rma, sorry.

simms22 said:
because before unlocking the bootloader, you have to enable the developer setting. if your bootloader is still locked, then there is nothing that you can do except try to get a rma, sorry.
Click to expand...
Click to collapse
The developer setting WAS unlocked before all this started.... the problem seems to be with the partition table? Does anyone have any ideas?

Calleja said:
The developer setting WAS unlocked before all this started.... the problem seems to be with the partition table? Does anyone have any ideas?
Click to expand...
Click to collapse
oh, it was unlocked? and you tried unlocking the bootloader?

simms22 said:
oh, it was unlocked? and you tried unlocking the bootloader?
Click to expand...
Click to collapse
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?

Calleja said:
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Click to expand...
Click to collapse
Have you tried doing fastboot oem unlock? The cammands you're using are for the 6P

nms247 said:
Have you tried doing fastboot oem unlock? The cammands you're using are for the 6P
Click to expand...
Click to collapse
Yeah, fastboot oem unlock brings up:
FAILED (command write failed (Unknown error))
The funny thing is I get the same exact error when I try "fastboot oem device-info", is that a driver/fastboot installed wrong thing, maybe? (I had only used fastboot from OSX before, now on Win10, although "fastboot devices" does seem to work)

Calleja said:
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Click to expand...
Click to collapse
you are missing the one and only command that you can unlock the bootloader with.. fastboot oem unlock. if it gets unlocked, then you can flash a factory image.

simms22 said:
you are missing the one and only command that you can unlock the bootloader with.. fastboot oem unlock. if it gets unlocked, then you can flash a factory image.
Click to expand...
Click to collapse
Ok, so if "fastboot oem unlock" returns "FAILED (remote failure) there's nothing whatsoever I can do? RMA is the only option?
The first android device I don't root and leave completely stock and it's the only one I've ever bricked..... sigh

No, Google bricked it, with his stupid OEM unlocking switch, which is totally stupid. But they'll give you a new one.

istperson said:
No, Google bricked it, with his stupid OEM unlocking switch, which is totally stupid. But they'll give you a new one.
Click to expand...
Click to collapse
Anyone know how trustworthy Motorola's RMA service is in Mexico? Bought the N6 through motorola.com.mx, kinda regretting that decision now.

help
Calleja said:
Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
Click to expand...
Click to collapse
How do you overcome? can show me the
thanks !

Messed up via oem lock command - can't access recovery - any help appreciated!

Hi all,
A few days ago I installed a custom ROM, which broke my android pay. I tried to re-lock the bootloader to fix this via the fastboot oem lock command, and i'm now stuck in a bootloop.
I can get the phone to boot into fastboot mode, and it shows up as such when checking via command prompt. I also have a backup of the phone I made a few days ago. I've tried to unlock the phone using the fastboot oem unlock command, but get the following error:
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.008s
I bought the phone second hand with an unlocked bootloader, if that makes a difference? I've set up a new Mi account and applied for an unlock code.
Does anyone have any tips on how to proceed? Thanks in advance!

Stupid thing to think relocking your bootloader would fix android pay while still on that custom rom, whe have hacks for that you know >> magisk14/15.2
Do you still have twrp? also try to flash stock images from xiaomi themselves, here.
that should at least get you booting again.

Hi,
Thanks for replying, i'll download the global stable version. Is it a case of sideloading this once complete? I still have TWRP installed if it makes a difference, I just can't reach it :/
Yes I do feel pretty stupid, and thanks for the link to magisk - hadn't heard of it until now but i'll definitely be using when/if I get my Mi back up and running. Is there anyway to unlock the bootloader other than the Mi Unlock app?
Thanks!
EDIT: Okay, so i tried flashing via the MiFlash tool and got the following error:
FAILED: Remote device is locked. Cannot erase.
Any idea of where to go from here?

So, I fixed it! In the off chance anyone is as unlucky/stupid/trigger happy as me, and finds themselves in teh same situation, here's the solution:
If you can't get it into EDL mode because you can't switch it off (mine kept rebooting), follow this video:
https://www.youtube.com/watch?v=ED96PJ-qYMM
It's in a foreign language but is clear enough - take the back off, unscrew the cover and short the pins he shows you after disconnecting the battery, then plug into your computer.
Your phone will pop up as a Qualcommdevice under the ports section of Device Manager. You should then be able to flash via MiFlash as per usual.
Phew, hairy there but sorted in the end. I'll now wait for the unlock code from Xiaomi, and do a bit more reading in future!

A much easier way to solve this problem
You don't have to follow any long tutorial. Nor do you have to open your phone up. Just power it into fastboot mode, download the mi unlock tool that you used the first time to unlock your bootloader and unlock your device once again. Then you can use miflash to flash the fastboot rom on your device and it won't throw up any errors. Once that's done, just reflash the custom recovery. Install the custom rom, use magisk for root and you're good to go. Safety net won't be tripped and android pay will still work. No need to rip your phone apart to fix it.

Mi A2 bootloader relock bootloop, need help ASAP!

Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!

You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.

Yepi69 said:
You should only lock the bootloader after installing the stock ROM, otherwise your device will be bricked and the only way you'll get it back working is by flashing the EDL test points near the phone's battery and reflashing the stock ROM back in EDL mode.
Try downloading this tool then try to unlock oem, flashing and flashing critical.
Click to expand...
Click to collapse
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.

NotCat_ said:
Noted. Thanks!
I really messed up here. The problem is i toggled allow oem unlocking off and to top it all off i did oem lock. Now its bootlooped (check the video). Does xiaomi fix this by warrenty? I really dont want to open the device up because i am afraid i will do more demage and void the warrenty and the device wont ever be fixed.
Click to expand...
Click to collapse
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.

Njaiker said:
I have seen another guy who did this. How is this possible that you turn off the unlock bootloader option when you've already unlocked it? The option gets greyed out and becomes non-functional.
Anyways I guess the best option is to give your phone to Xiaomi for the fix.
Click to expand...
Click to collapse
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.

NotCat_ said:
It wasn't grayed out for me. I'm thinking of test pointing the device because i dont really want to wait few months until i get my phone back from service. (There is no xiaomi service in my Country)
But i'm afraid if i open the device i will void my warrenty for future.
Click to expand...
Click to collapse
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery

Yepi69 said:
I don't think you will since you don't need to disassemble the device, all you need to do is remove the aluminum back cover carefully with damaging it and you'll find the test points right besides the battery
Click to expand...
Click to collapse
will try to do that. all tho i think screen goes off first thanks for your help and sparking some hope into me and my phone <3

It finally booted up! After having some hard time shorting test points i finally did and it booted up just fine! Big thanks to @Yepi69

use custom rom
NotCat_ said:
Hay soo i wanted to relock bootloader after failing to install custom recovery (both) i turned off oem unlocking in developer options and did fastboot oem lock. Now the phone is looping in "your device can't be checked for corruption. Please lock the bootloader" and it reboots and says the same again.
When i try to unlock the bootloader with fastboot oem unlock i get "FAILED (remote: Flashing Unlock is not allowed)
I really dont know what to do and i need a phone for comunication. Please help!
Click to expand...
Click to collapse
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01

honey ghumaan01 said:
since your device is already unlocked i recommend you using havoc os need instructions? instagram hsghumaan01
Click to expand...
Click to collapse
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.

try other slot
NotCat_ said:
Yes i do want to flash that rom, but i can't get twrp to boot on my unit. When i do fastboot boot "recovery name".img it says everything went fine, but i get black screen and thus can't get it to work nor install.
Click to expand...
Click to collapse
try on both slots

honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
Whats the fastboot command to change slots?
Mtp works fine tho.

NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot

the command to chang slot with fastboot is
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b
---------- Post added at 12:44 PM ---------- Previous post was at 12:41 PM ----------
NotCat_ said:
Whats the fastboot command to change slots?
Mtp works fine tho.
Click to expand...
Click to collapse
fastboot set_active a/b not sure can be fastboot set-actve a/b , you should use pitch black recovery instead of simple twrp
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
honey ghumaan01 said:
try on both slots
Click to expand...
Click to collapse
dm me on instagram hsghumaan01

honey ghumaan01 said:
fastboot set_active a/b
Click to expand...
Click to collapse
That command doesn't seem to work on my pc :/ cmd just gives out all commands when i type
fastboot set_active B (on pc)
And nothing happens :/
Are there any particular adb/fastboot files i need to download?

MarcusMario0605 said:
fastboot set-active {a or b}
To see what slot you current is on,
fastboot getvar current-slot
Click to expand...
Click to collapse
Took a screenshot of your comment for later, thanks!

Are there any particular adb/fastboot files i need to download?[/QUOTE]
use this tool; https://mega.nz/#!cr4SUIqY!Rzlftk2OFun8XIkNQb2aXRtP7-t3f4DB92vMIl90pgw
(this tool,can disable driver signature,Install all drivers,qcom,etc)
https://forum.xda-developers.com/showthread.php?t=2588979
Download SDK Platform-Tools for Windows ; https://developer.android.com/studio/releases/platform-tools
QDLoader HS-USB Driver ; https://mega.nz/#!EqJwTIzB!KJF3CldYq_u7KylaL0iO6rs05RWs2_dcUfaENjJcDpU
fastboot edl (useful) ; https://mega.nz/#!x6BkXY5A!hx8SXoBwd4-fW1UkZ1poHc7p-MFDaQ85FYH7Yk8bLZ8
See and here how to use adb & fastboot from any directory on pc ; https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
all of these are useful tools,that you must to have on pc
sry for english

don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)

daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
I already flashed the phone with edl test points. I'm running havoc os +hex

daitalos said:
don't use ''oem unlock'' on this device ...
try these commands : fastboot flashing unlock / fastboot flashing unlock_critical
__Test points-edl A2 see here : https://en.miui.com/thread-3524265-1-1.html (edl mode do not need unlocked bootloader)
Click to expand...
Click to collapse
Why not use oem unlock?

PLEASE HELP - Device Bricked - edl waiting for device

Hello I have a Mi A2 with ONE.
I tried to install Mi6X following this guide:
Guide
I got to step 9:
9- Click Refresh on Mi Flash Then choose Clean all and click flash
Then I got this error:
Error oem edl miflash tool, ACK count don't match
Then I tryed instead to install Jasmine again, and I started getting this error:
Cannot receive hello packet,MiFlash is trying to reset status
And then I was stupid enough to unplug my phone
THE ACTUAL PROBLEM (rigth now)
1. My phone will start, then stay at Mi(mi.com) logo indefinitely.
2. I can't enter download mode, Vol + and power will bring me the Mi logo again and again.
3. Can enter Fastboot mode... BUT...
-Mi flash don't detect it
-miflash_unlock don't detect it
-edl.cmd, unlock auto, and unlock critical say "< waiting for device >"
Edit: I solved the problem using test point to enter EDL mode, then It connected and I could flash it.

our phones (mia2) are weird devices to be honest, mine was recently bricked after choosing the "reboot to bootloader" option in twrp. id recommend you to go to mi service center if your phone is still in warranty

Stoopid Dickhead said:
our phones (mia2) are weird devices to be honest, mine was recently bricked after choosing the "reboot to bootloader" option in twrp. id recommend you to go to mi service center if your phone is still in warranty
Click to expand...
Click to collapse
Thanks for the reply. But unfortunately I can't
That would be my first solution, but my Mi A2 is not in warranty anymore...

have you tried to install stock rom with fastboot?

Maharram said:
have you tried to install stock rom with fastboot?
Click to expand...
Click to collapse
Miflash won't detect the phone, it's like is not connected at all...

puerco-potter said:
Miflash won't detect the phone, it's like is not connected at all...
Click to expand...
Click to collapse
No im not talking about miflash im saying fastboot u can install stock rom with fastboot too you need payload bin dumper and ota flasher for that

Maharram said:
No im not talking about miflash im saying fastboot u can install stock rom with fastboot too you need payload bin dumper and ota flasher for that
Click to expand...
Click to collapse
Sorry, can you help me unsderstand a little.
I found this guide:
Guide
But none of my Roms (Jasmine or Wayne) have a file that's named payload.bin
I feel like I am missing something
Edit:
I found that ota updates are the ones with the payload.bin file followed the guide and everything, but fastboot bring almost the same error that EDL brings:
< Waiting for any device >
Can it be that my cable somehow magically from one conection to another stoped working or something? I asked a friend for his cable... Cs are not as common in this country yet.

puerco-potter said:
Sorry, can you help me unsderstand a little.
I found this guide:
Guide
But none of my Roms (Jasmine or Wayne) have a file that's named payload.bin
I feel like I am missing something
Edit:
I found that ota updates are the ones with the payload.bin file followed the guide and everything, but fastboot bring almost the same error that EDL brings:
< Waiting for any device >
Can it be that my cable somehow magically from one conection to another stoped working or something? I asked a friend for his cable... Cs are not as common in this country yet.
Click to expand...
Click to collapse
Have you enabled oem unlock ?

puerco-potter said:
Hello I have a Mi A2 with ONE.
I tried to install Mi6X following this guide:
Guide
I got to step 9:
9- Click Refresh on Mi Flash Then choose Clean all and click flash
Then I got this error:
Error oem edl miflash tool, ACK count don't match
Then I tryed instead to install Jasmine again, and I started getting this error:
Cannot receive hello packet,MiFlash is trying to reset status
And then I was stupid enough to unplug my phone
THE ACTUAL PROBLEM (rigth now)
1. My phone will start, then stay at Mi(mi.com) logo indefinitely.
2. I can't enter download mode, Vol + and power will bring me the Mi logo again and again.
3. Can enter Fastboot mode... BUT...
-Mi flash don't detect it
-miflash_unlock don't detect it
-edl.cmd, unlock auto, and unlock critical say "< waiting for device >"
Please help, I am really afraid my phone will die permanetly as I can't turn it off and I don't know if it will charge in it's current state.
Click to expand...
Click to collapse
Did you flash hex kernel? You know that phone on 6x miui rom will not boot if you havent flash custom kernel after miui?

Mi flash tool won't work with locked bootloader
Install adb drivers and write command
' abd oem edl '
If ur phones connects
Than u can use mi flash tool

Maharram said:
Have you enabled oem unlock ?
Click to expand...
Click to collapse
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >

Amnvlad said:
Mi flash tool won't work with locked bootloader
Install adb drivers and write command
' abd oem edl '
If ur phones connects
Than u can use mi flash tool
Click to expand...
Click to collapse
"adb oem edl" brings this error:
adb.exe: unknown command oem
"fastboot oem edl" brings this error:
< waiting for any device >
and
"adb reboot bootloader" brings this error:
error: no devices/emulators found
(tested everything with the phone in fastboot or the Mi logo)

mariosenta said:
Did you flash hex kernel? You know that phone on 6x miui rom will not boot if you havent flash custom kernel after miui?
Click to expand...
Click to collapse
I didn't, because I got an error when flashing Miui, never got to follow the rest of the guide because my phone won't be recognised by any program it seems...
Thanks you all for the help, I will try with another cable, and if that don't work I will test point this little one. I really don't want to open it... but It seems like fastboot won't connect no matter what...

puerco-potter said:
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >
Click to expand...
Click to collapse
Did you execute this line "fastboot flashing unlock_critical" after fastboot oem unlock?

mariosenta said:
Did you execute this line "fastboot flashing unlock_critical" after fastboot oem unlock?
Click to expand...
Click to collapse
Originally yes, after oem unlock, I ran flashing unlock_critical

puerco-potter said:
I followed this guide to unlock bootloader previous to the guide on flashing of the first post:
GUIDE
The .bat that you run there actually executes "fastboot oem unlock". I did that part without any problem, the phone screen asked for confirmation and everything fine. After succefully unlocking bootloader I followed the guide on flashing Miui 10.
Now even that "fastboot oem unlock" will show this message:
< waiting for any device >
Click to expand...
Click to collapse
You installed oreo on pie? Because Mi A2 has antiroll back projection if you downgrade your Android version then you lost your imei code

Maharram said:
You installed oreo on pie? Because Mi A2 has antiroll back projection if you downgrade your Android version then you lost your imei code
Click to expand...
Click to collapse
6x has antiroll back, a2 does not.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
[/COLOR]
puerco-potter said:
I didn't, because I got an error when flashing Miui, never got to follow the rest of the guide because my phone won't be recognised by any program it seems...
Thanks you all for the help, I will try with another cable, and if that don't work I will test point this little one. I really don't want to open it... but It seems like fastboot won't connect no matter what...
Click to expand...
Click to collapse
Please, keep us updated.

I had the same issues like you months ago. The only solution you buy a pentalobe 0.8mm for iphone, a small philips screw driver, and a tweezer. Flash your phone in EDL mode. You need to contact 2 pins. You can search the location of the pins, how to disassemble the phone by googling it. then just flash Mi A2 stock ROM first, then convert it to Mi 6X again. I

hasel17 said:
I had the same issues like you months ago. The only solution you buy a pentalobe 0.8mm for iphone, a small philips screw driver, and a tweezer. Flash your phone in EDL mode. You need to contact 2 pins. You can search the location of the pins, how to disassemble the phone by googling it. then just flash Mi A2 stock ROM first, then convert it to Mi 6X again. I
Click to expand...
Click to collapse
No need to convert, now we have miui for a2.

mariosenta said:
No need to convert, now we have miui for a2.
Click to expand...
Click to collapse
Where can I take a look at this? I am really interested.
The cable wasn't the issue, I am getting the tools to open it tonight.

Bypass Pattern Lock in Honor 9 Lite without Data Loss

Dear friends,
my android device is Honor 9 Lite. Since I bought this phone, I was always able to get into the phone and access my data by using the touch sensor.
But nevertheless, I was forced to add a pattern lock as surrogate solution in case the touch sensor does not work for any reason.
Anyway, last week I hit on a serious problem! I did not know why the device dose not accept the first way (gaining access through fingerprint using the touch sensor) anymore.
It asks me all the time to enter the right pattern lock I set up 6 about months ago. And since I was not asked to enter the pattern lock before, unfortunately I just forgot it :crying:
Therefore, I cant access my device now and I do really have very important files and documents stored on the internal memory, which I do not want to lose by reset my device to factory settings and wiping all the data stored in the internal memory...
So I have searched the Internet - for long hours - for a proper solution that helps me to bypass the pattern lock without being forced to wipe my data.
But unfortunately, I could not find any effective way to gain access again to the internal storage of my phone.
One of the most important problems I hit on while searching the Internet was that there I could not find any way to enable USB Debugging in my locked device since I cannot access the settings....
Unlike some Samsung devices, it seems that there is no way to enter the known Download Mode in new honor devices. When I get to the Recovery Mode, I can see only three options, which are:
Reboot System now
Wipe data / factory reset
Wipe cache partition
The phone is still connected to my home network and my Gmail Account is still working on it. But I also could not find any way where my Gmail Account could be helpful in this case...
Is there any way to bypass the lock screen without losing data on this Honor device?
I hope you can help me to solve my problem and rescue my files...
Waiting for your suggestions :fingers-crossed:
Thank you very much in advance!
Kind regards

Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59187
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59184
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse
Dear Sparkrite,
thank you for your fast response !
I have attached two pictures which show both the EMUI Mode in addition to the Fastboot Mode on my Honor 9 Lite device...
I don´t quite know how to flash TWRP to e-recovery partition, since I cannot reach the device settings and thus I am not able to enable USB Debugging, which seems to be a necessary step to install or flash a new recovery environment on the device!
I also cannot enter the known recovery mode which we know on Samsung devices. I suppose that this has something to do with the operating system (EMUI) the phone is running.
Furthermore, I assume that the EMUI version which is installed on the device is EMUI 8.
I also would like to point out that the known Hisuite Software could´t connect to the device when I tried to connect the device to my Laptop using a USB cable.
Could you perhaps provide me with further information regarding flashing TWRP and gaining access to the data stored on the internal memory.
And is it possible to decrypt the internal data after extracting them from the internal memory?
A possible solution to my dilemma might be that I factory reset the phone and then try to recover the lost data using an Android Data Recovery Software. What would you say about following such a method?
I know that this will be very risky, but do you think that this would be a more effective and guaranteed way to rescue my data?
Thank you very much for your support!
Waiting for your response :good:
Sorry I could not upload the picture direclty from my computer, therefore I add here the links to the images in my album again:
Honor Lite 9 - EMUI Mode:
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59184
Honor Lite 9 - Fastboot Mode:
https://forum.xda-developers.com/picture.php?albumid=15704&pictureid=59187
I don´t know why the images cannot be opened here. Sorry, this is my first experience on XDA-Developers
The EMUI Version is 8.
And on the fastboot screen there are two lines written in green:
The first line says: PHONE Locked
The second line says: FRP Lock
At the top of the screen I can see the following text:
Fastboot and Rescure Mode
Please connect USB cable to your computer and open HiSuite
Android reboot reason:
AP_S_COLDBOOT 0
NA
volumekey_down_press_process_func

Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse

[/IMG]
Sparkrite said:
Perhaps you could help us to help you by telling us what version EMUI the phone is running?
Also can you enter fastboot mode and tell us what it says on that screen regarding lock(s) status?
If EMUI 8 you could probably flash TWRP to e-recovery partition, boot to it and use it to copy all internal data out and then reset the phone. But remember that the 9Lite employs encryption so even though you may get the data it will be of no use to you.
Click to expand...
Click to collapse

Ok, download and unzip the attached file.
Navigate to the directory 'platform-tools' where you have unzipped the downloaded file.
Open a command (DOS) window within that folder.
Make sure you are in the dir. 'platform-tools.
Enter fastboot mode on the phone and connect to PC,
Type :- fastboot oem get-build-number [ENTER]
Send me the result here and I'll tell you the best method..................

Sparkrite said:
Ok, download and unzip the attached file.
Navigate to the directory 'platform-tools' where you have unzipped the downloaded file.
Open a command (DOS) window within that folder.
Make sure you are in the dir. 'platform-tools.
Enter fastboot mode on the phone and connect to PC,
Type :- fastboot oem get-build-number [ENTER]
Send me the result here and I'll tell you the best method..................
Click to expand...
Click to collapse
Thank you for your support!
I followed the instructions and came to the following result about the build number:
(bootloader) :LLD-L31 8.0.0.144(C432)
OKAY [ 0.006s]
finished. total time: 0.007s
Waiting for your advice
Thank you!

golden.hunter said:
Thank you for your support!
I followed the instructions and came to the following result about the build number:
(bootloader) :LLD-L31 8.0.0.144(C432)
OKAY [ 0.006s]
finished. total time: 0.007s
Waiting for your advice
Thank you!
Click to expand...
Click to collapse
Ok, good, I'll get back to you shortly................
Do you know how to downgrade ?
Do you know how to flash a TWRP and boot to E-recovery ?
NB: e-recovery is a non protected partition and can be flashed with a locked bootloader.

Sparkrite said:
Ok, good, I'll get back to you shortly................
Do you know how to downgrade ?
Do you know how to flash a TWRP and boot to E-recovery ?
NB: e-recovery is a non protected partition and can be flashed with a locked bootloader.
Click to expand...
Click to collapse
Dear Sparkrite,
I have just searched the internet using the key words you have given to me.
It seems that the so called e-recovery is not a common issue for android users. I could barely find anything helpful in this field.
5 years ago, I was thrilled by working and solving problems of android devices. However, in the last 4 years time has changed and I have nearly stopped informing about such issues, since I had too much to do and I have forced too many obstacles with forced me to change my way of life.....
Moreover, my experiences with android devices were also done with Samsung devices. Except from this problem now, I had not worked with Honor devices in the past at all...
Anyway, I have just tried to flash a TWRP file on my Honor 9 Lite device using the known command window after entering the fastboot mode (of course without enabled USB Debugging). But it didn´t work and I have got the following error message:
PS D:\Android files\Honor 9 Lite\platform-tools>fastboot devices
FPMNW18924010946 fastboot
PS D:\Android files\Honor 9 Lite\platform-tools> fastboot flash recovery twrp_honor9_lite_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.650s
How can I flash TWRP on E-recovery without accessing the device settings? and what is the function of downgrading in this context?
What would you advice me to do?
I would be very thankful if you could make me aware on a good video or a helpful article for example, which can help me to get to my aim...
Thank you!

golden.hunter said:
Dear Sparkrite,
Anyway, I have just tried to flash a TWRP file on my Honor 9 Lite device using the known command window after entering the fastboot mode (of course without enabled USB Debugging). But it didn´t work and I have got the following error message:
PS D:\Android files\Honor 9 Lite\platform-tools>fastboot devices
FPMNW18924010946 fastboot
PS D:\Android files\Honor 9 Lite\platform-tools> fastboot flash recovery twrp_honor9_lite_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery' (24954 KB)...
OKAY [ 0.640s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.650s
How can I flash TWRP on E-recovery without accessing the device settings? and what is the function of downgrading in this context?
Thank you!
Click to expand...
Click to collapse
Well that command is doomed to fail for two very good reasons:-
1. Locked Bootloader.
2. The H9L using Oreo doe NOT have a 'recovery' partition as such.
The command to flash a custom recovery is :- 'fastboot flash recovery_ramdisk twrp.img'.
But as your BL is locked this will not work, however you can flash it to e-recovery using :-
'fastboot flash erecovery_ramdisk twrp.img'.
The advantage of downgrading (to at least B132 you have b144) is twofold:-
1. You could use HCU to get your BL code to unlock. (€4
1a. Or you could get your 'Slock' code to flash to 'unlock' your BL for free.
But unfortunately this would also wipe your phone.
2. Downgrading, using the Dload (Google it) method may well bypass the pattern unlock screen and/or fingerprint working again.
Edit:
Flash a working TWRP and come back to me when you can boot to it.
I may just have a workaround for you.

Sparkrite said:
Well that command is doomed to fail for two very good reasons:-
1. Locked Bootloader.
2. The H9L using Oreo doe NOT have a 'recovery' partition as such.
The command to flash a custom recovery is :- 'fastboot flash recovery_ramdisk twrp.img'.
But as your BL is locked this will not work, however you can flash it to e-recovery using :-
'fastboot flash erecovery_ramdisk twrp.img'.
The advantage of downgrading (to at least B132 you have b144) is twofold:-
1. You could use HCU to get your BL code to unlock. (€4
1a. Or you could get your 'Slock' code to flash to 'unlock' your BL for free.
But unfortunately this would also wipe your phone.
2. Downgrading, using the Dload (Google it) method may well bypass the pattern unlock screen and/or fingerprint working again.
Edit:
Flash a working TWRP and come back to me when you can boot to it.
I may just have a workaround for you.
Click to expand...
Click to collapse
Well thank you for your response!
The locked bootloader on my phone seems to be the most important obstacle which prevents me from installing anything on the device
I have tried to flash the TWRP file to E-recovery using the command window in the file of platform-tools and a custom recovery for Honor 9 Lite. But this didn´t work either...
I always got the error message:
FAILED (remote: Command not allowed)
I know that this error occurs due to the locked bootloader, but I could not find any proper and effective way to unlock the bootloader on my honor device without access to my device settings....
I have also found out that my device belongs to the supported models on HCU-Client-Website. But as I have seen, the process of unlocking the bootloader using this method requires also a certain interaction with the device, which means that the internal files and settings of the phone must be accessible in order to get the code to unlock the bootloader...
Therefore, being unable to unlock the bootloader prevents me from flashing a TWRP. And being unable to unlock the bootloader prevents me also from downgrading the software and installing a custom rom on the device (see for example: https://forum.xda-developers.com/9-lite/development/kangvip-rom-emui-8-0-t3775904)
It is completely OK for me to buy HCU-tool to get the code to unlock the bootloader, if this can help me to gain access to the internal memory without data loss. But does this work in my case, without the ability to open the device.?! And if yes, how does this go or where can I find near instructions to achieve this mission?
And is there any way to downgrade the phone without unlocking the bootloader or flashing a custom recovery? If this was possible, then I would try to flash a custom recovery and delete the password file through a special file called aromafm and with the help of my SD-Card, which was a successful way five years ago when I was able to bypass the pattern lock on the device of my cousin without any data loss....
In the worst case, I would simply factory reset the phone and try to recover the important files using a good recovery software.....
I think, this may be the most appropriate method with minimal time exposure, since I must gird myself to start the new semester at the university...:good:
Waiting for your advice
Thank you once again :fingers-crossed::good:

As I said it is possible to flash TWRP to E-recovery even with a locked bootloader !!!
I have done it many times.
You will NOT unlock BL while on B144, without code.
HCU will NOT work with build numbers above 132.
ALL BL unlocking WILL re-set and wipe phone.
Downgrading using Dload method is possible with locked bootloader !!!
Search here:- https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=lld-l31&firmware_page=0
Make sure it is a Dload ROM, it will say so within instructions in zip.
If you re-set phone, data WILL be gone, remember it is encrypted so no recovery.
My Advice is:-
Persevere with flashing TWRP to Erecovery.
Erecovery_ramdisk is NOT protected.
" fastboot flash erecovery_ramdisk twrp.img "

Sparkrite said:
As I said it is possible to flash TWRP to E-recovery even with a locked bootloader !!!
I have done it many times.
You will NOT unlock BL while on B144, without code.
HCU will NOT work with build numbers above 132.
ALL BL unlocking WILL re-set and wipe phone.
Downgrading using Dload method is possible with locked bootloader !!!
Search here:- https://pro-teammt.ru/online-firmware-database-ru/?firmware_model=lld-l31&firmware_page=0
Make sure it is a Dload ROM, it will say so within instructions in zip.
If you re-set phone, data WILL be gone, remember it is encrypted so no recovery.
My Advice is:-
Persevere with flashing TWRP to Erecovery.
Erecovery_ramdisk is NOT protected.
" fastboot flash erecovery_ramdisk twrp.img "
Click to expand...
Click to collapse
Dear Sparkite,
Thank you for your fast response!
I have been trying to downgrade and install TWRP Recovery on my device for almost three hours now, however, unfortunately without success
I have tried many times to flash TWRP to E-Recovery-Partition exactly as your have described in the last post, but I always got the same error message:
FAILED (remote: Command not allowed)
I have also tried to do the installation using different platforms and different TWRP files and sometimes with light changes in the code, but all my attempts failed...
My trials to downgrade the device to a version under 132 using my SD Card were also frustrating. I always got the same error, after the installation process reached 5%:
Software install failed!
Get help from: http://www.emui.com/emotiondownload.php?mod=restore
I tried to downgrade the device to the versions 8.0.0.0.127 and 8.0.0.0.131 and 8.0.0.0.129, which I downloaded from the website you have given to me. Also without success....
By the way, I could not find any instruction files in the zipped update files which I have downloaded from the website, therefore it was impossible for me to find out whether the downloaded Rom was compatible with the dload-method or not.
Also the program called "HuaweiUpdateExtractor", which I tried to use as an auxiliary means didn´t accept the UPDATE.APP and I always got the following error message:
ERECOVERY_VBMET.img: Invalid header crc - Expected: 33542 Got: 25244
It seems that there is no way out, right?
If there is a certain custom rom you can suggest for me, I would be very grateful.
Maybe I can succeed in flashing TWRP after downgrading the software installed. But I do not know if there is still a method that I didn´t try on this immune system....
Thank you in advanced!

I don't know what you are doing wrong.
It IS possible to flash TWRP to Erecovery as I have said many times before.
Try a different USB lead.
Try a different USB Port.
Try a different 'fastboot'/'ADB' version.
Try a different TWRP. (https://mega.nz/#!wotVWBQZ!ZO9DHD-HBMj-5LCxxW_74IYsDoSrVDeZsaQgMyIvuGQ)
Send me a screen shot of your command(s)
Send me a screenshot of your phone when you are trying to flash.

Sparkrite said:
I don't know what you are doing wrong.
It IS possible to flash TWRP to Erecovery as I have said many times before.
Try a different USB lead.
Try a different USB Port.
Try a different 'fastboot'/'ADB' version.
Try a different TWRP. (https://mega.nz/#!wotVWBQZ!ZO9DHD-HBMj-5LCxxW_74IYsDoSrVDeZsaQgMyIvuGQ)
Send me a screen shot of your command(s)
Send me a screenshot of your phone when you are trying to flash.
Click to expand...
Click to collapse
Dear Sparkite,
I have just tried all the alternative ways you suggested, unfortunately without success and I don´t know where the mistake in hiding
Again and again I hit on the same problem and I always got the same error message:
Command not allowed...
I have attached two pictures that show the fastboot screen of the device in addition to the commands I gave in the command window...
Thank you for your support!
View attachment 4806745
View attachment 4806753
View attachment 4806760

golden.hunter said:
Dear Sparkite,
I have just tried all the alternative ways you suggested, unfortunately without success and I don´t know where the mistake in hiding
Again and again I hit on the same problem and I always got the same error message:
Command not allowed...
I have attached two pictures that show the fastboot screen of the device in addition to the commands I gave in the command window...
Thank you for your support!
View attachment 4806745
View attachment 4806753
View attachment 4806760
Click to expand...
Click to collapse
Here the screenshot of the command window:
View attachment 4806761

golden.hunter said:
Here the screenshot of the command window:
View attachment 4806761
Click to expand...
Click to collapse
My bad, I'm so sorry to have put you through all this, I forgot that I had previously flashed 'slock' to any H9L to enable flashing to Erecovery. Apologies.
However in order to obtain a slock file for your phone you will HAVE to downgrade to at least B132.
Get a Dload firmware from here:- https://androidhost.ru/
When you have successfully downgraded we can go about getting a 'slock' file for you.
Or if you like you could go here on Telegram and join up to get your 'slock' :-
https://t.me/joinchat/I0ghclds9xtiC-5XLKIQrw
NB: Read the welcome message very carefully and follow it to the letter or you WILL get banned.