Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Dr_Raider said:
Hey guys, I have a A2017 axon 7, and I tried to upgrade from Marshmalow to nougat by flashing the B04 update from TWRP. I have now the factory recovery mode, and when I try to go in fastboot, it tries to launch the bootloader( which just tells me that my device software cannot be checked for corruption and that I need to lock my bootloader). When I try to boot normally it stays on the same "bootloader screen" and tells me to press the start button which makes the phone display the linux logo.... I'm a bit lost, I'm on ArchLinux could you pls help me ?
Thx !
Click to expand...
Click to collapse
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Choose an username... said:
Well, you should use MiFlash and install the stock system through EDL. The problem is that MiFlash is for Windows x64. if you could get a win10 x64 pc, you could fix it in a minute.
Or get to the recovery if you can, and flash Nougat again but via an SD card. But maybe you won't be able to get to the recovery mode
Click to expand...
Click to collapse
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Kantastisch said:
I need help! I wanted to relock the bootloader but then I coulnd't enter the recovery or fastboot anymore. When I press any combination it always turn on for 1 sec and then the screen turns off again but it still GOT recognized as QUSB Bulk. After I installed MiFlash the device is recognized as QDLOADER 9008. I didn't flash anything and I don't kno how to unbrick my device now .
I use the A2017G model btw.
Click to expand...
Click to collapse
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Choose an username... said:
How did you relock the bootloader? If you used a guide, you should have found a warning, and if you used axon7toolkit a message should've popped up.
You messed up. Real bad. You are probably on DFU mode, and the only ways to get out of there are:
-discharge the battery completely and try to enter FTM mode (i think you have to do that while it is connected to a PC), I think it was with volume down + power. this method works for very few people. If you enter ftm mode, issue 'adb reboot edl' and use MiFlash right away with a FULL_EDL package
-use the 4th category brick repair manual (disassemble the phone, short some pins)
Click to expand...
Click to collapse
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Kantastisch said:
I think DFU Mode is when I get recognized as ZTE Handset diagnostic .... according to this guide : https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898) It's a2017 but still.
"Axon 7 restore manual from bricked conditions when only ZTE Handset Diagnostic Interface(DFU) (COM...) mode is detected"
But I get recognized as QDloader 9008 and miflash also recognizes it as com10 or something.
Click to expand...
Click to collapse
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Choose an username... said:
it's not necessarily like that. DFU mode is just a mode in which the phone can be. Sometimes Windows just installs the QDLoader driver even though it's not EDL. and if you tried miflash and it didn't work, then it's most probably that.
There's a way to check. If you go to Properties, there should be a number that identifies the mode. if you google it and 'dfu interface' appears, then you are dfu-bricked
But if you locked the bootloader without being fully stock then it's most probably dfu bricked anyways
Again, how did you lock the bootloader?
Click to expand...
Click to collapse
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Kantastisch said:
I don't actually know if I really locked the bottloader.
So, I had unlocked bootloader and twrp. I just bootet into the bootloader, typed "fastboot oem lock" in adb and it said OK on the PC.
But on the phone it never asked me if I want to lock it or anything. And I never said MiFlash isn't working. It recognizes my phone but i judt didn't TRY to flash anything because I didn't want to make the situation even worse perhaps
Click to expand...
Click to collapse
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Choose an username... said:
Lol it doesn't ask you if you want to lock it, that's the point with bootloader mode. there's no system, no UI, and you make stuff via commands.
This is why you shouldn't even attempt this kind of stuff without knowing how it works. At least if you had used axon7toolkit, it would've told you not to.
Find a FULL_EDL package for your model. If you have an A2017, simply use this one:
https://androidfilehost.com/?fid=817550096634790942
or
https://mega.nz/#!JqwEUDCa!lW3NDaBNbmMxhtw6XajspHBJaaEmLC8uNvMZS5ww0EQ
(they are the same file)
Unzip it, leave the folder somewhere handy, put the phone in what you believe is EDL, open MiFlash and select the folder, and flash
Click to expand...
Click to collapse
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Kantastisch said:
Yeah, I screwed up, I know. But what is the point of flashing a full edl package for the phone if I have to put the phone in "what I believe id edl mode"?
And what shall I do if I succeed at something? Besided that, I can't find any EDL package for the A2017G?
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
This guide tells me NOT TO flash anything on a2017g...
Click to expand...
Click to collapse
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Choose an username... said:
Okay let me tell you this real straight. I have done this. I have the G packages, I just thought you were the op for some reason. Look at the back of the phone and confirm whether you have an A2017G or an A2017 just in case, or you might mess up even more, as hard as that can be.
at any rate, your fears are all dumbfounded, because in the situation that you are in, you have 3 options:
a) disregard all the help that i'm trying to give you, even though I have already done the process; and keep your brick on a shelf.
b) search on google or xda yourself, then do the process, without bothering here with your lack of trust
c) follow my advice and do the damn process
Whichever option you choose, I'm gonna leave the package here:
https://mega.nz/#!UrxCRCrQ!a4sXVFu5oqct2sWStfN_luGpN5HEGXxE4FcrRteagQ4
or
https://androidfilehost.com/?fid=961840155545591863
Again, I HAVE FOLLOWED THE 4TH CATEGORY BRICK REPAIR GUIDE AND FIXED MY G. I flashed stuff through EDL at least 10 times. And there wouldn't be a bunch of EDL packages for the G if they had a 100% chance of bricking your phone
So. If you decide to do this, turn your phone off. connect the USB cable to the PC but not the phone. Hold both volume buttons (but not the power button) and insert the USB cable at the same time. Then fire up MiFlash and try to flash the file (you have to unzip the folder, then select the folder on miflash, then flash. Here 2 things may happen:
a) it flashes and you can just go bother someone else
b) it doesn't and you have to follow the 4th category brick repair guide
Simple as that. if it fails, you might want to check if the 'Qualcomm HS-USB QDLoader 9008' is actually EDL mode or DFU mode, so you can do that by going to properties and checking some device identifier number on google (haven't done that, i just read that it can be done somewhere here).
Click to expand...
Click to collapse
THANKS SO MUCH , you saved my ass, it flashed without a problem and sorry for bothering you. Bootloader is locked now and it works fine. Thanks again!
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
I also faced this same problem in the past but i was able to recover my phone. Right now i don't remember how i did it but give me some time to think about it. I am sure someone else will help you just don't give up!!
Go to this link and try to follow their tutorial. It might help you.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42
ImSSin said:
I also faced this same problem in the past but i was able to recover my phone. Right now i don't remember how i did it but give me some time to think about it. I am sure someone else will help you just don't give up!!
Go to this link and try to follow their tutorial. It might help you.
https://firmwarefile.com/lenovo-vibe-k6-power-k33a42
Click to expand...
Click to collapse
Thank You ?
I am also trying my best to recover the phone and i will write here so that anyone who is facing this issue can recover his/her Phone.
No Solution found for this.
...
You have to send your Lenovo K6 Power to Lenovo Service Centre and get your Motherboard replaced.
If your phone is in guarantee then you will get free replacement no matter if your phone is rooted but please don't tell about root to them otherwise they will charge money for your small mistake.
what happened?
Do a new install
faizynadim said:
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
Click to expand...
Click to collapse
Boss it seems that you have hard bricked your phone so it means it's first boot has been corrupted there is no chance as first boot is mandatory to flash any file, there are some tools like octopus, or Medusa box, they can repair your boot then the phone can be used its just an outside chance 5o get it in workable condition look for some person or Repairing person have this boot repairing gadget,
If this fails too or you have messed up very badly then, last option is mother board replacement, there is no software option to repair by yourself
Help please..!!!!
:crying:
Even I face the same problem...
How do I go to download mode..???
It's stuck at Lenovo screen .... It just turn off on low battery and reboots on long press of power button.. Is it compulsory to have 80% of charge to get into download mode..???
i did the same. it switches on with lenovo logo , shows the os logo animation and its stuck there. when i tried connecting it to phone it showing unspecified device.
i could get into a fastboot mode . but nothing ahead to that. please find me a solution
Help me same issue
faizynadim said:
No Fastboot, No Recovery, No Download Mode, just a black screen. All Partitions of Phone got deleted. Pc is only detecting it as "Qualcomm HS-Usb Diagnostic 900E(Com10)" but unable to flash stock firmware. Getting the following error in Qfil.
...
"Download Fail:Switch To EDL FailFailed to Switch to Emergency Download mode".
Phone is also heating up as it have no OS installed.
Click to expand...
Click to collapse
Did you find any solution for this, present i'm facing same issue, please tell me if you have any solution for this...
Hello,
as per subject I need help rooting my device I tried all methods, @tdm method is using the US version and it is different from the EU one.
my spec:
7.1.1 (stock)
ZTE B2017GV1.2.0B13
Bootloader Locked
tulip is not working, I can't get the device to enter fastboot/EDL mode no matter how I tried.
please help guys :crying::crying::crying:
If you cannot get to EDL mode, try an EDL cable (aka. deep flash cable). Like this:
https://www.amazon.com/gp/aw/d/B0792YKWPZ
I bought one. It works great. But it takes a couple weeks to ship from China.
If you are impatient, you can try this method, but be very careful:
http://en.miui.com/thread-310325-1-1.html
I have also tried this method and it works.
Note, you can unplug the phone to retrieve the wire. Once in EDL mode, the phone will stay in EDL mode until it is reset.
axtenar said:
Hello,
as per subject I need help rooting my device I tried all methods, @tdm method is using the US version and it is different from the EU one.
my spec:
7.1.1 (stock)
ZTE B2017GV1.2.0B13
Bootloader Locked
tulip is not working, I can't get the device to enter fastboot/EDL mode no matter how I tried.
please help guys :crying::crying::crying:
Click to expand...
Click to collapse
Have you tried Axon 7 EDL tool? It forces the phone into EDL mode and works for the mini too.
donev_go said:
Have you tried Axon 7 EDL tool? It forces the phone into EDL mode and works for the mini too.
Click to expand...
Click to collapse
For mini is [Axon7 mini EDL Tool].
I cannot take my A2017U (DD) out-of-service to experiment with flashing and updating so I have been looking for a 'bricked' A7 to work with as I want to learn more about the DFU & EDL tools and ROM options.
With all of the reported "bricks" on the site I would have expected to see many listed on eBay, but not.
Any ideas where these guys might be lurking? The model suffix (U, G, or plain) is not particularly important. Thanks
I think Axon 7s should technically be unbrickable now. I've bricked mine to a point where I only had DFU mode and I managed to recover it pretty easily with the new DFU tool that puts your phone back in EDL mode and guide posted here in the forums.
I have a bricked redmi 3s prime. It is having locked bootloader.
First I had search for local repair center to fix it. But the shop guy said me to replace motherboard of device. But I'm not sure what is the exact issue with device, because I can still use recovery option as well fastboot.
I'm bit technical, so I thought it is software issue. So I thought to un-brick it myself. So I had tried almost many methods to un-brick it but not getting any success till yet.
The methods I have tried mentioned below.
1) From recovery, simply wipe data storage and try to turn on device. Waited for 20 mins on mi logo screen. No Success.?
2) Enter into fastboot mode (Device detected as some random string on PC) and simply try to flash both fastboot roms (Global and Developer) using MiFlash beta Tool. Even fastboot mode unable to flash those official roms. No Success.?
3) Enter into EDL mode using TestPoint method (Device detected as COM6 on PC). Again try with both roms MiFlash. After flashing each rom I had waited over 30 mins on MI logo screen, but nothing happens. No Success.?
One thing common while trying all above methods is that battery power less than 10%. I can not full charge device, because there is no way to turn off device if I'm not succeed with my steps.
So is there anything I'm still missing? Can someone help me with this?