Database Users

[Help!] EDL Doesn't work

Hi everyone, i cant enter to EDL mode, i need it because my stock rom is unstable(All start with OTA update), after update it show me "unfortunately android.... has stopped " every 3-5 seconds. EDL works fine yesterday and i try to install fastboot rom, but since MiFlash get error when i install fastboot rom i cant reboot in EDL. Hope you can help me.
note: I try reboot trough fastboot and do same thing as the video.
youtube. com/watch?v=gPh1yE3or8g&feature=youtu. be
(Sorry for the video post, but i cant find something like this case in web and i really need help)

You can try load in fastboot, connect to pc and run edl.cmd from archive.
www28.zippyshare.com/v/sKankJGd/file.html

go to fastboot and type "Fastboot oem edl" then enter and you will find the device got into the EDL mode

Unlock your bootloader and flash a custom recovery is the best way

I have the same problem
Hi! I have the same problem! I can´t get to EDL mode, also I cant update with MiFlash anymore.
I´ve been searching for over a week for a solution but I can´t fix the phone.
I´ve done the following.
1. Bought the Redmi 3S phone from Gearbest, came with a rom with adware, I was unable to update the rom from the updater.
2. I downloaded an Official Fastboot ROM from the XIaomi website, then updated to latest version MIUI Official TeamVersion Stable ROM: V8.1.1.0.MALMIDI (MIUI8), without unlocking bootloader.
3. After succesfully updating the phone, Android starts but then I get a continuos error message and I cant do anything. Now I can only get to Fastboot Mode (EDL does not work anymore, even using Fastboot EDL mode). If I try to flash it again with Mi Flash I get Flash tz error.
4. I applied for unlocking, received the message after 48 hours but I am stuck on 50% with the error -current account is different from account info on the device xiaomi-
5. I am unable to update the firmware using fastboot mode, recovery mode or EDL mode, Unable to unlock the bootloader. Already tried several methods with no results.
Please help!
Thank you very much.

If your issue is just to go to EDL mode and get back Qualcomm 9008 port com why not to try the "cable trick" found for the redmi note3.
https://xiaomi.eu/community/threads...-edl-no-fastboot-no-logo-no-led-solved.34113/
See post n°22 and it is no risk to try it. The cable would be reusable.
You have also many other posts on the subject, just goole it.

Here's a really easy way to make a deep flash cable http://forum.xda-developers.com/xiaomi-redmi-3s/help/help-bricked-phone-t3510277/post70029683#post70029683

julianpaul said:
Here's a really easy way to make a deep flash cable http://forum.xda-developers.com/xiaomi-redmi-3s/help/help-bricked-phone-t3510277/post70029683#post70029683
Click to expand...
Click to collapse
Thanks! I will give it a try!

D3VI0US said:
go to fastboot and type "Fastboot oem edl" then enter and you will find the device got into the EDL mode
Click to expand...
Click to collapse
it reboots the device , unable to boot to edl mode

tetsumo said:
Hi! I have the same problem! I can´t get to EDL mode, also I cant update with MiFlash anymore.
I´ve been searching for over a week for a solution but I can´t fix the phone.
I´ve done the following.
1. Bought the Redmi 3S phone from Gearbest, came with a rom with adware, I was unable to update the rom from the updater.
2. I downloaded an Official Fastboot ROM from the XIaomi website, then updated to latest version MIUI Official TeamVersion Stable ROM: V8.1.1.0.MALMIDI (MIUI8), without unlocking bootloader.
3. After succesfully updating the phone, Android starts but then I get a continuos error message and I cant do anything. Now I can only get to Fastboot Mode (EDL does not work anymore, even using Fastboot EDL mode). If I try to flash it again with Mi Flash I get Flash tz error.
4. I applied for unlocking, received the message after 48 hours but I am stuck on 50% with the error -current account is different from account info on the device xiaomi-
5. I am unable to update the firmware using fastboot mode, recovery mode or EDL mode, Unable to unlock the bootloader. Already tried several methods with no results.
Please help!
Thank you very much.
Click to expand...
Click to collapse
I got same problem.. But I'am not yet get permision to unlock bootloader.. Please help me.. What can i do to flash my redmi 3s..

My lenovo a6000 is hard bricked. PC not detecting it.

Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?

arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method

JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc

arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.

I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected

sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.

arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.

sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference

One update. I can get into the fastboot mode. But the bootloader is locked. What to do?

arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.

sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"

arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.

sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight

sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".

arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?

sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed

arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.

sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.

arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock

arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".

Sudden Boot-loops

Hi,
Just got an ZUK Z1 from one of my clients and the problem with the device is bootloops when trying to reach OS.
this issue came all of a sudden.
I managed to get into recovery and fastboot modes successfully but cmd won't show any serial after "fastboot devices" command but adb devices (while i'm in recovery mode via Aplly update from adb") showing serial accordingly and identify device.
when trying to push twrp or an update to CM OS in order to fix probable system files cmd replied
error: locked
i assuming it's the locked boot-loader.
even in wondershare mobilego the process stuck in 50%
i just need to backup client data.
Thanks for your kindly help,
- Oria, Israel.

Oria Maymon said:
Hi,
Just got an ZUK Z1 from one of my clients and the problem with the device is bootloops when trying to reach OS.
this issue came all of a sudden.
I managed to get into recovery and fastboot modes successfully but cmd won't show any serial after "fastboot devices" command but adb devices (while i'm in recovery mode via Aplly update from adb") showing serial accordingly and identify device.
when trying to push twrp or an update to CM OS in order to fix probable system files cmd replied
error: locked
i assuming it's the locked boot-loader.
even in wondershare mobilego the process stuck in 50%
i just need to backup client data.
Thanks for your kindly help,
- Oria, Israel.
Click to expand...
Click to collapse
I had the same problem..just reinstall twrp throw your computer ..and install the ROM you like

zukcyprus said:
I had the same problem..just reinstall twrp throw your computer ..and install the ROM you like
Click to expand...
Click to collapse
I can't because device is not recognized via fastboot and I have to save user data
Sent from my Robin using Tapatalk

In my case I erased everything...and throw my gmail I recovered everything..and don't install after cyanogen ROM ...if you can install zui xosp hexagon viper mokee or nuclearom .

Try this: https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056

your device is corrupted and cannot be trusted and may not work properly

Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command

amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely

As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?

amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done

If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214

Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images

For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.

Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?

Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)

Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted

Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time

amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.

Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also

amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!

I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...

Axon 7 bricked after installing TWRP

Hi! I am following this guide: https://www.droidviews.com/unlock-bootloader-install-twrp-and-root-zte-axon-7-a2017g/, and after using the axon7tool to install TWRP my device seems to be bricked and only shows up as QUSB_BULK in device manager - as if its in EDL mode. Adb doesn't recognize it - and the axon7tool throws a runtime error, I have seen previously when it couldn't detect the device
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
Click to expand...
Click to collapse
. I have tried using the MiFlashtool but I can't seem to find the right ROM - it always gives me a couldn't find flash script error. I have tried using both the Qualcomm and both ADB axon7 USB drivers (https://androidfilehost.com/?w=file...2ca06f4305d7074d4465bc289db2d49d5f99cdde608bf) and both of them yield the exact same result. What should be my next step of action, should I try to save the current firmware or get MiFlashTool working?

Update: let the phone die, then I booted into android, used abd to get into EDl which again showed a blackscreen and the edl tool nor miflash seem to be able to work as if its not in edl but in DFU and the DFU multitool cant get it out of there. Booting by pressing the volume up button and power button, causes a blackscreen with the same problem.