Okay so after I was getting off work last night, I went to pull my keys out of my hoodie and my lanyard evidently caught the corner of my phone and it belly flopped straight onto the front screen. I've never broken a phone before so this is a pretty traumatic experience for me. But anyway I want to take it back to T-Mobile and get it replaced (it's insured) but it was rooted and ROM'd. Using the Nexus 4 Toolkit I was able to flash stock and unroot, but now I'm stuck on the setup screen with no way to get to the settings to re-enable ADB to do the OEM relock. The digitizer is completely screwed, It kinda worked for like 15 mins and then it started freaking out like someone was touching everywhere on the screen at the same time, after that finally stopped it became totally useless. The lcd is completely fine so I can still see my screen but it's essentially useless. If anyone could tell me if there's a way to remotely activate ADB or possibly some super easy way of relocking it that uses only buttons or something, that'd be awesome.
Just go to bootloader ( volume up + volume down + power)
Then type, " fastboot oem lock", without the quotes. Good luck
Then type, " fastboot oem lock"
Click to expand...
Click to collapse
I'm assuming you're meaning in cmd, so I tried that and I cant get my phone to show up as a fastboot device. And of course the list for adb devices is blank :/
RomminNudels said:
I'm assuming you're meaning in cmd, so I tried that and I cant get my phone to show up as a fastboot device. And of course the list for adb devices is blank :/
Click to expand...
Click to collapse
Install drivers.
Okay so I installed the drivers and I still am having no luck. I don't know if you would know but since it's going to be replaced through Asurion insurance and not T-Mobile's warranty service, does it really matter if it's just unlocked? No root or rom, just unlocked. I'm thinking since it's obviously not a software issue then they won't care if it's unlocked.
*** Scratch that, my adb folder got messed up or something and it didn't have fastboot in it. A thousand times thank you! The universal drivers totally worked and everything went great once I realized that I overlooked something so simple. Now I won't have to worry about T-Mobile giving me any problems!
Related
Hi guys,
I recently dropped my Nexus 4 on the floor today and the screen cracked. As a result, the screen is completely unresponsive now but I am able to see its display when I press the power button. Could you guys help me/point me in the right direction regarding how to get the data I have on the phone (music, photos etc.) please.
My Nexus is unrooted/stock version. I tried connected it to my laptop via USB, but all it does it charge. I think I might have the USB debugging option enabled (as I remember enabling it before sometime ago). I'm running the latest firmware (5.0.1 I believe). Also the bootloader is locked.
Any help would be much appreciated.
Thanks
EDIT: I should note that I have a Password (PIN) for the lock screen.
I installed android sdk and tried to enter commands, but it didn't work. When I typed in 'adb devices', no serial came up (I checked sdk manager for the google usb driver, and it says it's installed). Also, when I tried typing in anything i.e. 'adb shell' it said error no devices found. I was attempting to follow a guide to set up adb for any other steps required to get my data from the internal storage. Bear in mind, I don't have much knowledge on these tools, all I'm doing is following any guides. Please can you help me how to get my photos or the contents of the sdcard.
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
oracle93 said:
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
Click to expand...
Click to collapse
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
jd1639 said:
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
Click to expand...
Click to collapse
Ah that was what I feared ... I'm running the latest firmware (5.0.1). I wouldn't really care about the phone if it weren't for a few images (should have had it backed up!).
Now I need to decide whether or not to change the screen etc. for £35 or just look in the market for a new phone. If I did buy a new screen/digitiser/frame thing, would these be suitable (where I won't need to use heat guns or glue and stuff)?
ebay (dot) co.uk/itm/LCD-Screen-Display-Touch-Digitizer-for-LG-E960-Google-Nexus-4-Frame-Replacement-/331224787829?pt=UK_Replacement_Parts_Tools&hash=item4d1e892b75
OR
ebay (dot) co.uk/itm/For-LG-E960-Google-Nexus-4-LCD-Display-Digitizer-Touch-Screen-Frame-in-Black-/331227949021?pt=UK_Replacement_Parts_Tools&hash=item4d1eb967dd
Also, if I did change it using the above, would dissembling the phone and reassembling it cause my data to be lost?
Thank you for your help
Edit: I managed to save about 80 photos which were probably in the default images folder in the SD card using AndroidLost. I'm guessing the other images which were in other folders i.e. WhatsApp Images etc. aren't recoverable using the site
My phone wont boot back up because i interrupted the download by holding down the power button during install...it just keeps flashing google !!!
Help only had for 1 hour !!
Don't panic, flash a factory image and everything will be fine again
Gorgtech said:
Don't panic, flash a factory image and everything will be fine again
Click to expand...
Click to collapse
how do i do that ?
please tell me you enabled adb debugging and oem unlock (in developer settings)
and why? why did you power down during the update?
I am not sure if I debugged anything ....all I did was unlock the system Ui or something like that by tapping on something 7 times to unlock some hidden features !
I was paying attention to the phone and had the buttons held down while holding
On the screen when I try to recover in the bottom left it says device is locked along with a bunch of stuff and then the last line says connect USB CABLE .
akoda said:
I am not sure if I debugged anything ....all I did was unlock the system Ui or something like that by tapping on something 7 times to unlock some hidden features !
I was paying attention to the phone and had the buttons held down while holding
Click to expand...
Click to collapse
if you didn't alter anything within those "hidden features" you're almost certainly out of luck.
you need to have enabled "adb debugging" to likely get yourself out of this jam... plus you didnt unlock your device
try some of the things listed in this thread: http://forum.xda-developers.com/nexus-6p/help/mess-locked-bootloader-os-t3316463
if they dont work, im sorry to day, you pooched your device. will need repairs.
There's probably nothing you can do. Your bootloader is locked so you can't use fastboot to flash anything. If the stock recovery supports adb sideload you could try that, otherwise you're fresh out of luck and need it to be repaired.
WOW ...i cant believe this .....what should i say when i return it ?
You could say it powered off during the update.
akoda said:
WOW ...i cant believe this .....what should i say when i return it ?
Click to expand...
Click to collapse
well.. if nothing else, a hard lesson to NOT touch the phone at all when it's updating.
really sucks, and clearly just a mistake. hopefully they take pity on you
dratsablive said:
You could say it powered off during the update.
Click to expand...
Click to collapse
thanks ...i appreciate all you guys help !!!
So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!
Galrash said:
So tonight my phone randomly froze and restarted itself, and is now perpetually stuck on the black screen with the white Google text. Every so often it restarts itself back to that point and stops. I was running Nougat from the beta program workaround.
I have done tons of research and am at a loss. So far I have:
-Booted into fastboot mode and attempted Recovery Mode. I can navigate using the volume keys until Recovery Mode shows up in red, but when I hit the Power button to select it the phone immediately boots back to the normal Google logo loop.
-Tried to flash a stock image via command line, no luck because of bootloader I think.
I might not be using all the right terminology, but it seems to me that I am stuck because I never enabled USB Debugging or Unlocked my Bootloader while the phone was working?
-If I go to CMD and type 'ADB devices' I just get a message saying "List of devices attached" and nothing else.
-If I type 'Fastboot Devices' then my phones serial number appears and it says fastboot next to it.
-If I type 'fastboot flashing unlock' it says "FAILED (remote: oem unlock is not allowed)
Does anyone have any ideas on how to fix this and get my phone working again?
Thanks in advance!
Click to expand...
Click to collapse
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?
Heisenberg said:
Lesson #1: always keep your bootloader unlocked.
Don't bother trying any fastboot commands, they will never work because your bootloader is locked. Don't bother trying any adb commands either, they won't work in fastboot/bootloader mode (they only work while booted into Android and in recovery). I hate to say it but you're basically screwed. With no access to fastboot, no access to recovery, and no access to there's literally zero you can do. This should be covered under warranty, though. When you say the Nougat "beta program workaround" what exactly do you mean?
Click to expand...
Click to collapse
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
I'm not entirely sure how it works but I believe you'll need to contact Best Buy. Even so it should be covered by warranty.
Galrash said:
Where if you got impatient for an OTA you could sign up for the android beta program to get Nougat (once it was officially released) and then opt out of the program without having to downgrade back to Marshmallow.
I was worried I might be screwed. I will call google tomorrow and see what can be done, although I am a little worried since I bought the phone from Best Buy instead of from the Google Play store
Click to expand...
Click to collapse
In my experience, Best Buy will not honor manufacturer warranties on smartphones; So unless you bought their Geek Squad coverage, they will tell you to contact Huawei for a warranty RMA.
Contact Info for Warranty RMA:
Huawei Device USA
1-888-548-2934 (1-888-5HUAWEI)
Got ahold of Huawei and it was surprisingly easy and fast. They emailed me a shipping label I just have to drop my phone in the mail and send it to them and it will be covered under warranty. Luckily I have my old Nexus 6 to use until they get it back to me
Long shot as this shouldn't be possible, but I figured I'd try asking here anyways. Is there any way to unlock a 6P that's pin-locked by Android's Device Manager?
The goal is to get the pictures off this phone. It was my brother's phone before he passed away and I've been holding on to it for the past few months - just haven't had the energy to try to deal with it...
-I have access to the gmail account.
-I tried changing the pin through Google's device manager, but since the phone was already locked, the new pin did not take. I get the message on the phone about the new pin, but it doesn't unlock it.
-Developer mode is not enabled (i.e. USB debugging).
-Not rooted or anything like that and most likely has the latest updates (t-mobile). As a matter of fact, the lock screen says that a new system update has been downloaded.
Thanks.
Try putting twrp in your adb folder, boot into fastboot and use "fastboot boot twrp.img"
clappe said:
Long shot as this shouldn't be possible, but I figured I'd try asking here anyways. Is there any way to unlock a 6P that's pin-locked by Android's Device Manager?
The goal is to get the pictures off this phone. It was my brother's phone before he passed away and I've been holding on to it for the past few months - just haven't had the energy to try to deal with it...
-I have access to the gmail account.
-I tried changing the pin through Google's device manager, but since the phone was already locked, the new pin did not take. I get the message on the phone about the new pin, but it doesn't unlock it.
-Developer mode is not enabled.
-Not rooted or anything like that and most likely has the latest updates (t-mobile). As a matter of fact, the lock screen says that a new system update has been downloaded.
Thanks.
Click to expand...
Click to collapse
The only way I can think of is by installing twrp on the phone. The only way it wouldn't work would be if he didn't have USB debugging enabled, which if he didn't then you might be out of luck... I'm so sorry.
Ghstudent said:
The only way I can think of is by installing twrp on the phone. The only way it wouldn't work would be if he didn't have USB debugging enabled, which if he didn't then you might be out of luck... I'm so sorry.
Click to expand...
Click to collapse
Unfortunately, I am pretty sure USB debugging is not enabled...sorry that's what I meant when I wrote developer mode (I've tinkered with making apps, so I know what it is).
Thanks.
Same situation here and I try to figure a solution for many days.In my opinia the only way to bypass is a modified google account manager ! Could anybody help?
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
RoyJ said:
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
Click to expand...
Click to collapse
Connecting the device to a Windows 10 PC, it will recognize the 6P, but using Windows Explorer will show no files.
Running 'adb devices' lists no devices.
When I power on the 6P, first I get the 'Google' text logo, then the colorful 'spinny' android logo, then the 'android' text logo. Then it goes to the usual lock screen (shows the time, background, etc). On this screen are the normal shortcut buttons on the bottom - microphone, padlock, camera. After a few seconds it shows the 'Locked by Android Device Manager' screen, this has a padlock symbol in the middle along with the pin code that I set online through Google's device manager.
Thanks.
Might be worth a shot to try to contact Google. You'll need proof of your identity, and the passing of your brother though. Best of luck. Sorry about your loss.
If you end up not being able to get a rep that can help via email or phone calls; you might have to do a hardmod.
tr4nqui1i7y said:
Might be worth a shot to try to contact Google. You'll need proof of your identity, and the passing of your brother though. Best of luck. Sorry about your loss.
If you end up not being able to get a rep that can help via email or phone calls; you might have to do a hardmod.
Click to expand...
Click to collapse
Hardmod? I did a quick search and the only hardmod I found was to deal with temperature.
Thanks.
RoyJ said:
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
Click to expand...
Click to collapse
Did you have a chance to try it?
Thanks.
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.