Database Users

Sos! Help: Broken download mode

Hi guys, so I flshed a wrong kdz file on my D801 wind canadian variant, no my phone stuck on LG logo boot screen with green led, i have no fastboot mode, no twrp recovery, I can just access default recovery to hard reset, when i try to enter download mode by pressing volume+ while pluging the phone to pc, it goes just to frst screen, i mean the download mode logo with blue dots!!!!
Please any help would be appreciated, I'm ready to pay for fixing it as i live in a country where my phone won't be fixed otherwise. please please.

Helppppppppppppppppppp Please please just answer me

Up up up up up up up up up up

devdassi said:
Up up up up up up up up up up
Click to expand...
Click to collapse
bud same thing happened to me. and unfortunatly there is no fix for this. everytime i turned my phone on i got the little android guy then it would stay on lg screen with blue and green LED. try download mode it goesto the first screen of little blue dots.
since warrenty should not be able to tell anything about root or etc. i sent it in. in the mean time i called my carrier company and they sent me out a new phone for 35$. but i have to send old one back wether it ges fixed or not.
sorry bud but there is no way back from that. even tho your computer gives it a port its not fully booting so you cant flash anything..... here is one last thing you can try................ this could be your only hope.......it didnt help me but it might work for you...
good luck
http://forum.xda-developers.com/showthread.php?t=2582142

jester12345 said:
bud same thing happened to me. and unfortunatly there is no fix for this. everytime i turned my phone on i got the little android guy then it would stay on lg screen with blue and green LED. try download mode it goesto the first screen of little blue dots.
since warrenty should not be able to tell anything about root or etc. i sent it in. in the mean time i called my carrier company and they sent me out a new phone for 35$. but i have to send old one back wether it ges fixed or not.
sorry bud but there is no way back from that. even tho your computer gives it a port its not fully booting so you cant flash anything..... here is one last thing you can try................ this could be your only hope.......it didnt help me but it might work for you...
good luck
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
thank you so much sir for replying, what is really wierd is that when i connect it to my pc, kingo root detects it, and gives me the option to root, then the rootin process stops at fetching scripts.

I cannot read.

Gnarfsan said:
If you can do that, you should be able to fix it via that Ubuntu guide to restore the partitions I think...?
Link: http://forum.xda-developers.com/showthread.php?t=2582142
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
I was able to connect to pc like he was. And kingo saw it but about 2 mins everything failed. No matter what port name i gave is. Any flash tool as well. And ubuntu did not work for me. Altho i did suggest that ubuntu method just incase it does work for you. Exhaust all options before giving it up for repair or warrenty exchange good luck and i hope you are more secessful then i was. Altho rogers did send me out a new phone good luck

thank you guys , my phone when on lg logo, and connected to pc, i can see it in device manager under modem as LGE android net usb modem,
and under ports as LGE android serial port com 8, any chance or sign of live to my phone, as mentionned before, there is no waranty services in our country.

@ jester12345 Did ubuntu read your phone when you tried the method of flashing partitions?

devdassi said:
@ jester12345 Did ubuntu read your phone when you tried the method of flashing partitions?
Click to expand...
Click to collapse
No ubuntu did not see my phone. Only my pc did even tho my phone wouldnt finish booting.

Could there be a paid fix? I'm ready to pay to bring my phone to life again.

Lg g2 stuck in boot loop, vzw i have tried everything need serious help!!!!!!!!!!!

Been running pac rom, tried installing a custom ROM that was almost stock kitkat for Verizon. Forgot to wipe i think, and now i have been screwed since. Stuck in boot loop. Factory reset can be reached, but screen goes black everytime and doesnt allow me to get into TWRP. Only thing accessiable is download mode. But device is not recongized in adb, only when its bootlooping. But it is recognized in devices and printers in bootloop. New computer also, no RSA authentication, while in bootloop ive tried to adb boot recovery commands, but no authorization. Im completly stuck and have been for days, ive read so many posts but everything i have found doesnt match all my problems. and most people dont read the entire post or problem before submitting a dumb answer, which is a duh i tried that kind of thing thanks for nothing. SO PLEASE HELP IF YOU CAN THINK OF ANYTHING ELSE. IM GOING CRAZY OVER HERE AND LOOSING MY MIND> WHO EVER CAN HELP ME, IS GOD AND SHOULD BE CONSIDERED TOP DOG GENIOUS>

When you get to the white Factory Reset screen, pressing the power button 3 or 4 times won't get you back into TWRP?

Well u press it once to give conform option, and the second time, turn it black

lg flash tool

that doesnt work because it thinks its got the latest version. I need some real help bad, its so hard not having my phone. This would be easy if my laptop didnt get stolen that had authorization to do cmd commands. Anyways, really need some brain power put togeaher on this on and \fast. Is anyone down with maybe skyping with me, to visually see whats going on and troubleshoot it as if you were remoting into a computer. Just tell me what to do!!!> Please you have no idea how much I would love someone if they did. Its been driving me balls for weeks now. I NEED SOMEONES HELP

seriously, no one can help?

millzdog said:
seriously, no one can help?
Click to expand...
Click to collapse
lg tool works.. can u go into download mode?? just need to tweak lg tool with offline script

33709
Croize said:
lg tool works.. can u go into download mode?? just need to tweak lg tool with offline script
Click to expand...
Click to collapse
Yes i can go into download mode, please show me how to tweak

millzdog said:
Yes i can go into download mode, please show me how to tweak
Click to expand...
Click to collapse
Use the official lg support tool to restore it if you can enter downloadmode!!!!

http://forum.xda-developers.com/showthread.php?t=2432476
vs98010b stock rooted

LG G2 Bricked, Need urgent assistance.

I need some serious help guys. Phone is stuck at boot logo and wont turn on. IT wont enter recovery mode. it wont hard reset. It wont enter download mode.
The phone was completely stock originally. So i rooted using towelroot and ran the 'AutoREC' program. That did its thing and restarted and got stuck in fastboot mode. couldnt get out of it. Eventually managed to reflash all the original stock ROM partitions and it started to boot again... only to get stuck at the LG logo. I need some serious help.
PC wont detect the phone at all and its as if there is no OS on the phone. I have the D802 variant 32gb.

which kdz variant did you flash.

v.konvict said:
which kdz variant did you flash.
Click to expand...
Click to collapse
D80220C_00
got it from "lg-firmware-rom" after entering my imei

spookyleaf said:
D80220C_00
got it from "lg-firmware-rom" after entering my imei
Click to expand...
Click to collapse
same thing happened to a d802 of a friend of mine. but he flashed the d802h variant. will keep you posted if i find a way out.

I am in the same position. Except I tried to flashify stock recovery on d800 at&t variant. I wanted to install the stock update because I was still stock. Just root with twrp before...I had the sprint variant before the ls980 and it never screwed me over like this. I'll post if I figure anything out... I got to get ahold of shellnutt... He's the g2's god.

Dam. Leme me know what happens
Sent from my Nexus 5 using XDA Free mobile app

spookyleaf said:
Dam. Leme me know what happens
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Have you tried both ways to enter recovery?
Push PWR + Vol Down till you see the LG Logo then release and press both again
Push PWR + Vol Down till you see the LG logo then release and press and hold the volume up and volume down buttons until reset screen appears.
If you can see the LG logo I think you are not Hard Bricked

I haven't tried that exactly. I'll give it a shot when I get a chance
Sent from my Nexus 5 using XDA Free mobile app

You may want to check your internal hardware to be sure it's marked as a D802. Typically the feint white stamp in the lower center/left of the phone with rear cover removed is the true model number. It's also stamped on the board and on the ribbon cables going up eithe side. Your device is showing the signs of a false d802 which has become sadly common in recent months.

If it's legit d802 then flash aboot, boot, laf and power it off.
Then hold voume up and connect to pc while still holding volume up.
Make sure you have the drivers installed, fire up lg mobile support tool or the lg flash tool 2014 (you need your kdz file now - find it using your imei and lg-firmware site)

Okay so I found this: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 to get it to come up as a device in Windows and Linux. And this: http://forum.xda-developers.com/showthread.php?t=2582142 I'm sure you read this but you need to do it after following the first guide. I already have a Linux installed and I'm going to try today. I'll update with a guide for you only if you need it and if I succeed. I just need to remind you. You CANNOT mess up on the second guide... Well as far I can tell. But if the first guides label is actually true then maybe I'm wrong.

ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!

darkpower_4 said:
Okay so I found this: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 to get it to come up as a device in Windows and Linux. And this: http://forum.xda-developers.com/showthread.php?t=2582142 I'm sure you read this but you need to do it after following the first guide. I already have a Linux installed and I'm going to try today. I'll update with a guide for you only if you need it and if I succeed. I just need to remind you. You CANNOT mess up on the second guide... Well as far I can tell. But if the first guides label is actually true then maybe I'm wrong.
Click to expand...
Click to collapse
thanks i appreciate that very much. Keep me informed on how it goes. Fingers crossed!

spookyleaf said:
ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!
Click to expand...
Click to collapse
Plug it into a windows machine, open device manager and look for Qualcomm qhsusb_bulk. If you get that, you're already in bulk and don't need to worry about shorting capacitors. If it's not being recognized in any way, you may be forced into that as a last resort.

spookyleaf said:
ok so ive ordered some tools to open up the phone and check the internals. Hopefully its a legit G2. Meanwhile every single possible combination of the power and volume keys does absolutely nothing. If all else fails ill try shorting the capacitors as ive seen on a guide from here and hopefully that will be the end of it. Thanks for all the input guys. Ill keep you posted!
Click to expand...
Click to collapse
All you really need to open it up is a guitar pick. It pries apart make sure you take the sim card out. After that it's going to take a little swipe around the edge and it'll pop open no problem.

iowabowtech said:
Plug it into a windows machine, open device manager and look for Qualcomm qhsusb_bulk. If you get that, you're already in bulk and don't need to worry about shorting capacitors. If it's not being recognized in any way, you may be forced into that as a last resort.
Click to expand...
Click to collapse
I checked that already. Not going into bulk mode. Seems like the capacitors are my last resort

so ive poped the phone open and guess what... its not a D802.. its a D800.. the at&t version... wtf.. no wonder i bricked it. gonna see if i can use the unbrickable method

did you checked the IMEI?

nope its says on the speaker grille after you remove the back cover. "D800"

how is that possible? did phone information apps showed your device as 802 aswell? did kernel info and phone info in system settings lied too?

Qualcomm hs-usb qdloader 9008 nexus 6P (HELP!)

Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?

attempted to apply for heat some to the device then re flash ?

blackcell1 said:
attempted to apply for heat to the device then re flash ?
Click to expand...
Click to collapse
Sorry, I don't quite understand what you mean?

Clarkeofcurtis said:
Sorry, I don't quite understand what you mean?
Click to expand...
Click to collapse
Use a hairdryer to warm up the back of the phone.

Are you pulling my leg? Warm it up then reflash?

nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method

blackcell1 said:
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
Click to expand...
Click to collapse
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice

Clarkeofcurtis said:
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Click to expand...
Click to collapse
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.

blackcell1 said:
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
Click to expand...
Click to collapse
thank you so much that worked, it has said flash successful, first time I got a google logo but now nothing, what would be my next step please?

if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------
but from my personal experience with having to heat a phone up to restore factory images, it kinda means the phone is nearing the end of its life and id start thinking about buying your next phone before it sh*ts the bed.

blackcell1 said:
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
Click to expand...
Click to collapse
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc

Clarkeofcurtis said:
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Click to expand...
Click to collapse
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.

blackcell1 said:
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
Click to expand...
Click to collapse
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?

Clarkeofcurtis said:
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Click to expand...
Click to collapse
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply

blackcell1 said:
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
Click to expand...
Click to collapse
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay

Clarkeofcurtis said:
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Click to expand...
Click to collapse
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:

Is it possible to send me the guide you used? Thanks.
Clarkeofcurtis said:
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
Click to expand...
Click to collapse

Hey there sorry for slow replies, will be back on my desktop in an hour I'll send you links for what I followed and such, I think the only reason my device was in EDL mode was due to a hardware fault? As my device is faulty indefinitely as I had to use a hairdryer to warm it up while flashing this then allowed it to enter firehose state which a lot of people seem to error with - after all my attempts and research I'm to velieve there's a fault with the phone itself the only way I could get it to even power up was applying heat to it after removing the back panel
As blackcell said deballing or something? Worked a treat!
Furthest I've managed to get now is into my boot loader however everything is locked - when I press enter recovery my handset just freezes ?

5.1 said:
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Click to expand...
Click to collapse
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader

Clarkeofcurtis said:
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Click to expand...
Click to collapse
Light usually a red LED blink while in proper EDL state as far as I know. Could be something else on the N6P. Well, it looks like you are SOL. Sorry, I don't know what else to say, since you exhausted all possibilities...
Good luck...

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.

Ouh....DFU? I think this thing is totally bricked.

I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?

Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !

raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.

Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.

stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!

Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....

stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!

Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable

Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!

Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...

twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.