Database Info

Recover Data from (unrooted)Nexus 5 with broken screen without UBS-Debuging turned on

Hello,
as u can read in the title the screen of my (unrooted!) Nexus 5 is broken due to a bicycle accident. The phones flashes if I receive a new message but the screen just dont turn on. Unfortunately I have USB-Debugging disabled...
Now my question is, how can I recover my data? I really need it and ofc have no backup
I read a lot but I still have no idea...
I think, because USB-Debugging is disabled, it will be a lot harder.
(Note: Because I am new, I can't post links, so I replaced "www" with "[worldwideweb.]", sorry )
I found the following tutorial on YT:
[worldwideweb.]youtube.com/watch?v=B7Z_r0Z0CEo
The problem is ofc, that the Nexus hasn't got two charging ports...
Also I found this:
[worldwideweb.]androidphonesoft.com/resources/enable-usb-debugging-android-broken-screen.html (search for "Method 2")
but there is the problem, that this tool is only available for Samsung-Devices...
Now my last hope is, that I can recover my data with adb, but also there I got the problem, that I have USB-Debugging disabled...
(And I dont know, if I have to root my phone? (and if it is even possible without working screen?...)
So my Problems are:
- No USB-Debugging enabled
- No Root
- PC recognizes my phone but not more... (in CMD: "adb devices" doesnt list any device...)
So is there a way of recover my data? It's very important for me and I would be very grateful, if anyone could help me and accompany me through the process with instructions!

I had the same problem and couldn't find a solution. I tried for 3 entire days with any method found or that came to mind. Finally I decided to change the screen with one from eBay ,the cheapest one . If you find a solution let me know. The closer I could get was using an app that was supposed to let you control and see your nexus 5 screen on your PC screen. This app of which I can't remember the name had some bugs,maybe was an old not updated app,because I could see my nexus 5 lockscreen and an arrow controlled by the PC touchpad to simulate the touch, but sadly nexus 5 couldn't react to the arrow movement,a and nexus 5 screen was not full but only a part

Axel85 said:
I had the same problem and couldn't find a solution. I tried for 3 entire days with any method found or that came to mind. Finally I decided to change the screen with one from eBay ,the cheapest one . If you find a solution let me know. The closer I could get was using an app that was supposed to let you control and see your nexus 5 screen on your PC screen. This app of which I can't remember the name had some bugs,maybe was an old not updated app,because I could see my nexus 5 lockscreen and an arrow controlled by the PC touchpad to simulate the touch, but sadly nexus 5 couldn't react to the arrow movement,a and nexus 5 screen was not full but only a part
Click to expand...
Click to collapse
But I think, that ur USB-Debugging was activated, wasn't it? Because I don't think, that this would work without USB-Debugging activated...
And then it would be easy, with USB-Debugging enabled there would be like 100 ways

I found no way to retrieve data . How would you do with Usb debugging? Or maybe I don't remember correctly and was for the fact that I had a lockscreen pattern and so Usb debugging is useless... Sadly I have a lg g watch that was not settled as a trusted device to disable the security or had home wifi area to do the same. Maybe there was even the fact that after a reboot you have to put the screen pattern the first time before the automatic unlock. I even tried to recover the partition from bootloader , but if I remember correctly it was hanging after some minutes. Don't ask me why emmc was god on nexus 5, I use the PC to do phone repair,and I'm a technician. I had the same trouble copying the full sdcard partition from recovery, and even restoring it to a new nexus 5 .Because the LCD was not as the original one and I sold the repaired for the same price of another not repaired n5. In the process of copying sd card partition content , it hangs another time. Seems to not digest the copying of some files under android subwoofers. Sorry for the confusion but I don't remember correctly, it was a nightmare. I had 2 infernal weeks because N5 is my first device even to work and I had to use my second phone , a really ultra cheap and underpowered Deco 77x(dual core1ghz with 512mb of ram) which has an M and even an N ROMs that works better than the stock 4.4... Slow as hell but the only way to save my work since my mother steel my galaxy Nexus. Try only to think I had to do some tries for 2 days, order the new screen, change it at a level that was invisible and good for the new user, wait for the new, try to restore a tarp backup to a different phone,find a way because it's not possible, copy sdcard partition , copy manually all the files which broke the full automatic copy process, compare all the folders files ... It was a PITA. Now I backup every month to a Usb otg Kingston key, at least I have only to restore it to a different device and do the sdcard things.... It's slow to create a backup but I can do it when is in charge,because the USB key do charge pass through and this is greaatttt even to watch movies (don't do that always, Usb key reach a really hot temperature, but case ,Usb port or phone shell reported not even a minimal sign)
The copy stopping could be a windows 10 bug ,never had that in 7 ... This new os is s*** ,has many small fu****g bugs... I wish I never updated ,I found those bugs after 1 month so I can't go back.

Axel85 said:
I found no way to retrieve data . How would you do with Usb debugging? Or maybe I don't remember correctly and was for the fact that I had a lockscreen pattern and so Usb debugging is useless... Sadly I have a lg g watch that was not settled as a trusted device to disable the security or had home wifi area to do the same. Maybe there was even the fact that after a reboot you have to put the screen pattern the first time before the automatic unlock. I even tried to recover the partition from bootloader , but if I remember correctly it was hanging after some minutes. Don't ask me why emmc was god on nexus 5, I use the PC to do phone repair,and I'm a technician. I had the same trouble copying the full sdcard partition from recovery, and even restoring it to a new nexus 5 .Because the LCD was not as the original one and I sold the repaired for the same price of another not repaired n5. In the process of copying sd card partition content , it hangs another time. Seems to not digest the copying of some files under android subwoofers. Sorry for the confusion but I don't remember correctly, it was a nightmare. I had 2 infernal weeks because N5 is my first device even to work and I had to use my second phone , a really ultra cheap and underpowered Deco 77x(dual core1ghz with 512mb of ram) which has an M and even an N ROMs that works better than the stock 4.4... Slow as hell but the only way to save my work since my mother steel my galaxy Nexus. Try only to think I had to do some tries for 2 days, order the new screen, change it at a level that was invisible and good for the new user, wait for the new, try to restore a tarp backup to a different phone,find a way because it's not possible, copy sdcard partition , copy manually all the files which broke the full automatic copy process, compare all the folders files ... It was a PITA. Now I backup every month to a Usb otg Kingston key, at least I have only to restore it to a different device and do the sdcard things.... It's slow to create a backup but I can do it when is in charge,because the USB key do charge pass through and this is greaatttt even to watch movies (don't do that always, Usb key reach a really hot temperature, but case ,Usb port or phone shell reported not even a minimal sign)
The copy stopping could be a windows 10 bug ,never had that in 7 ... This new os is s*** ,has many small fu****g bugs... I wish I never updated ,I found those bugs after 1 month so I can't go back.
Click to expand...
Click to collapse
Ok, so there is no good solution? :/
Can I just replace the screen with a cheap one from ebay and then use it again? This should work, shouldn't it?

You can try yourself, but I found no way, I don't want to discourage you, but I tried all comes to mind and all gone wrong,and I'm an average user. Yea you can get a pretty cheap display... I tell you the truth, I didn't changed it for a new one after the repair because the display was not good, but because I was in warranty and here in europe Google gives you a refurbished unit if you have problems with a warranty of 2 years. So because my phone repaired was 90% the same as a new phone but battery starts to degrade I took the chance to request a refurbished unit because of the battery and to reset my warranty to two years. Mine was a 2013 unit, and I asked for a change other 2 times... I m in warranty til 2018 now . Going back to the display, from a technician examination, I can tell you that all the display I bought to repair my customers units seems to be original displays with original touchscreens, only slightly variations in colours calibration like on preassembled units. Only the plastic frame sometimes seems not legit, because 2 times I found it a deeper black and more rough (like sandstone of one plus one)

So I simply buy myself a new display and replace it and then I should (ofc) be able to backup it, right?
Is there a difference between like 30$ screens to 60$ screens on ebay for example?

Gykonik said:
Hello,
as u can read in the title the screen of my (unrooted!) Nexus 5 is broken due to a bicycle accident. The phones flashes if I receive a new message but the screen just dont turn on. Unfortunately I have USB-Debugging disabled...
Now my question is, how can I recover my data? I really need it and ofc have no backup
I read a lot but I still have no idea...
I think, because USB-Debugging is disabled, it will be a lot harder.
(Note: Because I am new, I can't post links, so I replaced "www" with "[worldwideweb.]", sorry )
I found the following tutorial on YT:
[worldwideweb.]youtube.com/watch?v=B7Z_r0Z0CEo
The problem is ofc, that the Nexus hasn't got two charging ports...
Also I found this:
[worldwideweb.]androidphonesoft.com/resources/enable-usb-debugging-android-broken-screen.html (search for "Method 2")
but there is the problem, that this tool is only available for Samsung-Devices...
Now my last hope is, that I can recover my data with adb, but also there I got the problem, that I have USB-Debugging disabled...
(And I dont know, if I have to root my phone? (and if it is even possible without working screen?...)
So my Problems are:
- No USB-Debugging enabled
- No Root
- PC recognizes my phone but not more... (in CMD: "adb devices" doesnt list any device...)
So is there a way of recover my data? It's very important for me and I would be very grateful, if anyone could help me and accompany me through the process with instructions!
Click to expand...
Click to collapse
Have access to the Linux PC? Just give it a try.
Connect to Linux PC , re-start the device in recovery mode.
And now it be displayed on your Linux PC

mjp93 said:
Have access to the Linux PC? Just give it a try.
Connect to Linux PC , re-start the device in recovery mode.
And now it be displayed on your Linux PC
Click to expand...
Click to collapse
With "the Linux PC" u mean if I have PC with Linux? I only have Linux VM on my Windows Laptop and I dont think, that this will help..
But why should it work with an Linux PC?

Gykonik said:
With "the Linux PC" u mean if I have PC with Linux? I only have Linux VM on my Windows Laptop and I dont think, that this will help..
But why should it work with an Linux PC?
Click to expand...
Click to collapse
To be frank, I had experienced that on my linux pc all my phones shows internal memory when booted into recovery. Hope it shows for you.

mjp93 said:
To be frank, I had experienced that on my linux pc all my phones shows internal memory when booted into recovery. Hope it shows for you.
Click to expand...
Click to collapse
Then first how do I boot the Nexus in Recovery, volume up+down and power on?
And then I have to get an Linux-PC...

Gykonik said:
Then first how do I boot the Nexus in Recovery, volume up+down and power on?
And then I have to get an Linux-PC...
Click to expand...
Click to collapse
power + vol down
this will be the bootloader
then using volume button select recovery
Can u see the options? screen is working?
press volume up button twice to get into recovery if u cannot see

mjp93 said:
power + vol down
this will be the bootloader
then using volume button select recovery
Can u see the options? screen is working?
press volume up button twice to get into recovery if u cannot see
Click to expand...
Click to collapse
No screen is not working...
otherwise I wouldnt have this problem

Gykonik said:
No screen is not working...
otherwise I wouldnt have this problem
Click to expand...
Click to collapse
What I describe was irrespective of your screen working you can enter into the recovery mode

mjp93 said:
What I describe was irrespective of your screen working you can enter into the recovery mode
Click to expand...
Click to collapse
Yeah but I think, that I have to know what I should press after Volume down + Power on (for 10secs I guess)...
Which Linux version should I use?
Then I would create an bootable usb-stick with Linux and would try it

;69785694 said:
Yeah but I think, that I have to know what I should press after Volume down + Power on (for 10secs I guess)...
Which Linux version should I use?
Then I would create an bootable usb-stick with Linux and would try it
Click to expand...
Click to collapse
Try Ubuntu, First try with windows

mjp93 said:
Try Ubuntu, First try with windows
Click to expand...
Click to collapse
Dude, I already tried with windows
Now I'll try it with Ubuntu

;69787619 said:
Try Ubuntu, First try with windows
Click to expand...
Click to collapse
Wait wait
Turn the Nexus 5 ON , and other android phone with OTG SUPPORT.
Connect OTG cable to Other Android device.
Now connect your Nexus 5 to the Android device via USB cable.
Connection goes like this:
android device - otg - usb - Nexus 5
Now you can see contents of NEXUS 5 ON *other* Android device.
Hope it helps.

mjp93 said:
Wait wait
Turn the Nexus 5 ON , and other android phone with OTG SUPPORT.
Connect OTG cable to Other Android device.
Now connect your Nexus 5 to the Android device via USB cable.
Connection goes like this:
android device - otg - usb - Nexus 5
Now you can see contents of NEXUS 5 ON *other* Android device.
Hope it helps.
Click to expand...
Click to collapse
Wait, what should I do?
And where do I have to enter "android device - otg - usb - Nexus 5"?

Gykonik said:
Wait, what should I do?
And where do I have to enter "android device - otg - usb - Nexus 5"?
Click to expand...
Click to collapse
No.
You take Another Nexus 5 or any other device from a friend.
Connect OTG cable to the friend's device then connect ur Nexus 5 to your friend's.
Then your files will appear in ur friend's device.

Recover files from bootlooping Zenfone6

Dear all,
from the occasional reboot my Zenfone performed every now in a while (which didn't bother me too much) it now reboots so fast that it usually has not yet booted to the point where I could get data off the device before it reboots again.
As always, the backup is too old and I want to extract some data off the device. Most important are a few KBs worth of text notes. Here come some questions:
- It seems to be a hardware fault. Are there educated guesses what may give me a few last moments with the device to extract data? Heat? Freezing?
- Are there professional data recovery companies dealing with smartphones such that they can extract data from the chips without the phone working?
- As it is a Qualcomm device: Would any access via QDLoader work or would it be as unstable as the rest of the phone?
I appreciate any input. And yes, I know that I didn't backup often enough.
Thanks,
weaker

which rom are you on?

Sorry for the late reply.
I'm on stock ROM with Magisk. In the end when it became worse, I let Magisk restore the images but this definitely seems to be hardware-related. I also did no overclocking and I don't use games on the phone so I think that it is also not a thermal issue.
To keep the interested ones updated how it evolved: The situation is now as follows:
I tried to boot into recovery via fastbooting the TWRP (the one I used many times successfully for my phone) after one of the phone bootings was stable for enough seconds so have ADB contact and go to fastboot mode. I hoped to be able to interact more stabily in the recovery. However, the result was that the phone rebooted (I am unsure if the TWRP transfer was finished before that) and then the charging screen appeared and the charging screen remained constantly on, even when pulling the cable. It didn't react to any keypresses in that state.
I let it drain the battery (which was only a few hours as the screen was always on). Then, I plugged the phone in and it booted normally and was stable for 15 minutes or so, which gave me enough time to save the most important data. Phew.
This session however seemed to be the last farewell. The phone started to bootloop and I switched it off*. Now the phone has always a black off screen and doesn't respond to anything: Pressing (and holding) the power button, also in combination with Vol+ or Vol-. Also plugging a cable to charge doesn't create any reaction.
* switching it off worked the following way: The unlocked bootloader shows that one could press the power button to pause the boot. I can't think of why this might be a useful function in a normal situation. However, in my situation I could pause the boot and after some time it would switch off. That way I could at least break the bootloop.

you will have to boot into qloader to be able to recover your phone...
follow step by step exactly what is mentioned in the below link, ypu should be able to recover your phone :
Here’s how to unbrick Asus ZenFone 6 (Asus 6z) from QDLOADER 9008 mode - PiunikaWeb
Is your Asus ZenFone 6 (Asus 6z) hard-bricked? You can use still flash via QDLOADER 9008 mode to give a new life to your dead handset.
piunikaweb.com

Sorry to be the prick here, but next time post this in Q&A section. This one is for posting development (Kernels and ROMs)

OK, no offense taken. I thought that I would need to resort to some TWRP magic to get data off my device.
@MOD: Feel free to move thread where it fits best.

For the sake of completeness:
The phone is back from RMA. According to the sparse documentation they exchanged the mainboard and battery and some connector. Some firmwares are now newer than on the old mainboard (little surprise here). Bootloader unlock worked also on the new phone (some report that this would not work by default after an RMA, for me it did).
So, ASUS did a great job dealing with the issue.

Data recov - Hard-bricked Phone - Qualcomm

My wife's Pixel 3 XL hard-bricked a couple of nights ago. This seems to be a fairly common issue possibly related to recent updates to the phone. Here are a couple of example forum posts on the same issue:
https://www.reddit.com/r/GooglePixel/comments/miltpe
[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx
Hi, I have a Pixel 3 that won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK_CID:xxxx_SN:xxxxxxxx when connected to a pc. I am an ignorant regarding phones, flashing, etc... Is there any way of getting...
forum.xda-developers.com
Pixel is not working. qusb__bulk - Google Pixel Community
Honestly, there are many more posts, but they're all pretty similar. From reading many MANY topics over the last 48 hours ago, I've been able to figure this much out: There is a potential way of un-bricking the phone using Qualcomm's QFIL tool with the proper files for the Pixel 3 XL (.mbn and a couple of .xml). HOWEVER, these files are very specific to the phone and are nowhere to be found, and even if I could find them, I can't actually get the phone to connect to QFIL (or to the QPST Configurator). It detects the chip on a COM port, but then just stays stuck at "downloading" (the loading bar under state stays stuck at about 1/5 way).
Both adb and fastboot don't recognize the device, and neither does QFIL. So at this point, I'm pretty well ready to say that I'm SOL. So I'm pretty well giving up on the idea that I'll be able to bring the phone back to life, but I'm still wondering if there's some way that I can recover the data from the phone when it's this far gone. None of the usual methods work since the phone would need to be recognized in a higher-level state than just recognizing the Qualcomm chip. And since the screen doesn't react, I have no idea if the button combinations I'm pressing are actually getting me into the bootloader menu or not. Heck, maybe it's so far gone that I can't even get that far.
So my question is this. Is there some low-level method I could try to recover the data off the phone when it's in this state? Any input is appreciated!

If USB MTP Mode was enabled on bricked phone it may possible to access the phone's data you are interested in to recover: This requires an USB-connection via USB-C cable what Pixel 3 phones support by default.

jwoegerbauer said:
If USB MTP Mode was enabled on bricked phone it may possible to access the phone's data you are interested in to recover: This requires an USB-connection via USB-C cable what Pixel 3 phones support by default.
Click to expand...
Click to collapse
Thanks for the reply, but MTP is not possible in this state. The phone would need to be functional for MTP to be enabled.

I'm in the same situation, need .mbn file so I can use the Qualcomm EDL mode to try and bring the thing back to life.

Unable to enter EDL

xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do something.

kaleamity said:
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do something.
Click to expand...
Click to collapse
Download Qualcomm qloader drivers....see if device shows up as Qualcomm 9008 In Windows Device manager or maybe it says Qualcomm bulk hub...if it is you are in edl mode and you need to download blank flash file from the rom archive on lionnet moto firmware under our device...unzip the file and run the .bat file with admin privileges it will run the file and reload the critical bootloader files to get you to bootloader screen ...then reflash STOCK...I did this last week because I rebooted to edl from TWRP...

Nothing shows up. I get a few led blinks but nothing in device manager or otherwise.

Anyone found the answer to this? Im having the same issue

kaleamity said:
xt2043-4 unable to get into EDL mode. It died during a restore with the Lenovo "smart" software.
When plugged in I something's get a single led blink. Nothing however when I plug it into my PC. I have an edl cable that doesn't seem to do anything either. Are there test points/jtag? I don't want to open it up unless I can actually do som
Shane8705 said:
Anyone found the answer to this? Im having the same issue
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hi there! I myself have a hard-bricked G Stylus (US model). After reading this and related threads, as well as doing a LOT of independent research on this. I have a feeling that the only hope lies in potential EDL test points located on the motherboard. I've looked at a teardown video on Youtube, and I see several sets of potential test points. From further research, it appears that test points for EDL are always located right next to each other.
I'm purchasing some iFixit tools this month, which include the required T3 driver bit. Once I get access to the motherboard, I fully intend to test every possible set of EDL points. I'll post my findings on this and any related thread in the G Stylus forums here on XDA. If I'm successful in restoring the phone, I will post a photo of the points that need to be bridged to enter EDL mode.
Wish me luck!

Have you had any luck with this? And I'm wondering if you mind describing how you got into this situation.
On my phone (I think it's a Moto G Stylus, XT2043-4, that I got through Google Fi in the US), I was trying to modify an app on the phone. So I used "adb pull" to get the APK. Then I extracted, edited, and recompiled it with apkeasytool, but then I couldn't write it back to the proper directory because the filesystem was read only. At that point I went through the process of unlocking the bootloader via the Motorola website, and then tried to root the phone. That's where my problems started.
I can go through the details if anyone thinks it would matter, but essentially, I wasn't paying attention and flashed the incorrect files... multiple times... I ended up with a phone that appeared to be dead (nothing on the screen no matter what I did). However, I noticed that when I plugged it in it popped up as the "Qualcomm 9008 Port" thing in Windows Device Manager. After reading up on that I realized that it was in EDL mode and I tried to run the blank-flash.bat file I found. After some trial and error, it appeared to work, however, I was holding the power button at the time and the phone may have restarted in the middle of the script. At that point, it stopped appearing in Device Manager and I haven't gotten it back, except that after disconnecting the battery, I get an LED flash when it's plugged in as well as some other strange behavior that I'll describe below.
Anyway, after all the previous catastrophes, I decided to open it up and look for these mythical test points. I'm attaching some pictures in case they help anyone. One after exposing the mainboard, another after lifting the obvious cables, and finally one with the obvious test point candidates numbered.
I'll describe what I've figured out so far:
- When I disconnect the ribbon that covers 6, 7, 8, and 9, I don't even get the LED flash when connecting/disconnecting the phone to the computer. So I don't think those are likely to be test points, but I don't know what that cable is for.
- The middle ribbon appears to connect the battery, and I don't get the LED flash when that is connected. It doesn't happen when I connect the USB to the computer OR when I hold the power button. I don't understand why this happens.
- The rightmost ribbon doesn't cover anything. So I leave it connected.
- When USB is connected and not the middle ribbon, all the points seem to show 0V except 3 (0.417V) and 5 (1.803V). 6 is 1.792V when the middle ribbon is connected, but dissipates during measuring when the middle ribbon is disconnected. 10 also seems to dissipate when the middle ribbon is disconnected, and I can't measure it when connected because it gets covered up.
- If I short or ground 10 or 12 while plugging in, the LED flashes until I remove the short or ground.
Anyone have any thoughts? Anything else I can check?

moorevineyard said:
Have you had any luck with this? And I'm wondering if you mind describing how you got into this situation.
On my phone (I think it's a Moto G Stylus, XT2043-4, that I got through Google Fi in the US), I was trying to modify an app on the phone. So I used "adb pull" to get the APK. Then I extracted, edited, and recompiled it with apkeasytool, but then I couldn't write it back to the proper directory because the filesystem was read only. At that point I went through the process of unlocking the bootloader via the Motorola website, and then tried to root the phone. That's where my problems started.
I can go through the details if anyone thinks it would matter, but essentially, I wasn't paying attention and flashed the incorrect files... multiple times... I ended up with a phone that appeared to be dead (nothing on the screen no matter what I did). However, I noticed that when I plugged it in it popped up as the "Qualcomm 9008 Port" thing in Windows Device Manager. After reading up on that I realized that it was in EDL mode and I tried to run the blank-flash.bat file I found. After some trial and error, it appeared to work, however, I was holding the power button at the time and the phone may have restarted in the middle of the script. At that point, it stopped appearing in Device Manager and I haven't gotten it back, except that after disconnecting the battery, I get an LED flash when it's plugged in as well as some other strange behavior that I'll describe below.
Anyway, after all the previous catastrophes, I decided to open it up and look for these mythical test points. I'm attaching some pictures in case they help anyone. One after exposing the mainboard, another after lifting the obvious cables, and finally one with the obvious test point candidates numbered.
I'll describe what I've figured out so far:
- When I disconnect the ribbon that covers 6, 7, 8, and 9, I don't even get the LED flash when connecting/disconnecting the phone to the computer. So I don't think those are likely to be test points, but I don't know what that cable is for.
- The middle ribbon appears to connect the battery, and I don't get the LED flash when that is connected. It doesn't happen when I connect the USB to the computer OR when I hold the power button. I don't understand why this happens.
- The rightmost ribbon doesn't cover anything. So I leave it connected.
- When USB is connected and not the middle ribbon, all the points seem to show 0V except 3 (0.417V) and 5 (1.803V). 6 is 1.792V when the middle ribbon is connected, but dissipates during measuring when the middle ribbon is disconnected. 10 also seems to dissipate when the middle ribbon is disconnected, and I can't measure it when connected because it gets covered up.
- If I short or ground 10 or 12 while plugging in, the LED flashes until I remove the short or ground.
Anyone have any thoughts? Anything else I can check?
Click to expand...
Click to collapse
Hi there! I actually did find some more potential EDL points underneath the speaker grill (underneath the black plastic piece below the battery).
I've tested them all... and no luck so far... The only reproducible result I can share is:
When the battery is unplugged, attempting to use any two points results in an LED flash every 15 seconds or so. No other behaviors.
Motorola came so close to having a perfectly repairable phone... What a disappointment.

This seems strange to me. Most of what I've read about other phones with the EDL mode and test point access seems to indicate that it's not possible to mess it up with any of the normal tools (adb, fastboot, recovery, blank-flash, etc.). Is that incorrect?
Basically, I had the impression that the Qualcomm EDL mode was provided by a more segregated component on the board that could reprogram the rest of the system, but not incorrectly reprogram itself the way you can incorrectly reprogram the bootloader.

moorevineyard said:
This seems strange to me. Most of what I've read about other phones with the EDL mode and test point access seems to indicate that it's not possible to mess it up with any of the normal tools (adb, fastboot, recovery, blank-flash, etc.). Is that incorrect?
Basically, I had the impression that the Qualcomm EDL mode was provided by a more segregated component on the board that could reprogram the rest of the system, but not incorrectly reprogram itself the way you can incorrectly reprogram the bootloader.
Click to expand...
Click to collapse
It appears that certain models aren't failproof. Similar situation with a mislabled black-flash. Flashed it multiple times and ended up unable to do anything going forward. I saw the edl points on a similar phone the moto g power on youtube and hoped that they were somewhat easily identified. Unfortunately doesn't seem to be the case, I too have tried every combo that I saw on the board. Same blinking lights as described, but nothing shows on the PC. I am able to get it working on other devices however as I have two.

Today I started researching repairing a hard brick of a moto g stylus after letting it sit around for a couple months. I came across the android doctor video that shows how to do this on a g8+ but unfortunately I found out that the mobos aren't laid out similarly. Subsequently found this thread. Bummed to find out the EDL points haven't been discovered. Hopefully someone does find them and posts here. I guess I'll do a little more research but otherwise I guess it's back to the shelf this phone goes.

FWIW I found this thread, but the points illustrated here don't seem to work for me: https://forum.xda-developers.com/t/sofia-edl-points-found.4457105/

Well I tried most points on the board. I was cycling through when I hit either I-J or J-K and my pc said there was a short on a USB port. I removed the ribbon cable to reveal that the jumper I made had melted. The led no longer flashes and the phone is now totally dead jim. Charging for a while doesn't seem to have any effect, nor letting it sit. Whatever shorted killed it. I was incredibly careful but clearly not careful enough.
That said I have another 2020 stylus (bootlocked unfortunately). So I'll be part harvesting as my current phone degrades. Thank you all for your help and good luck to you on this phone! Shame on Moto for really trying to keep people out of it... The glue, the edl cable not working, the points being potentially behind the battery ribbon. Just unnecessary nonsense imo.

EDL es el 10 y 12 me pasa que no se mantiene se desconecta despues de 5 segundos

Question Cannot get into EDL mode...

OK, so not happy. After failing to flash the new MIUI 14, then could not go back to the original 13, could not flash via fastboot at all, kept failing. Modified the flash_all.bat thinking that would fix the phone (was stuck with red fastboot logo on phone perpetually), only to find the phone screen now appears to stay completely off. PC no longer recognizes the phone when trying to enter fastboot mode (tried all the hold volume and power combinations). Only sign of life for the phone is holding down the power and volume + for maybe 40 second there's a brief green flicker. All this said, also can't get the PC to recognize it in EDL mode. This may in part be a lack of a USB 2.0 port, gonna try and get a hub to test it. BUt otherwise, really hard bricked Mix Fold 2 here, gents. This thing doeesn't have easily accessible touch points. And those aren't indicated online anyway. Wondering if a deep flash cable might be worth an $10 investment? Anybody have any suggestions? If I can get it in EDL mode I'll pay somebody to restore it but as it stands, its a $1500 brick.
Good news is my Fold 4 is my daily driver and even have a Flip 4 for fun. Still...

johnnobts said:
OK, so not happy. After failing to flash the new MIUI 14, then could not go back to the original 13, could not flash via fastboot at all, kept failing. Modified the flash_all.bat thinking that would fix the phone (was stuck with red fastboot logo on phone perpetually), only to find the phone screen now appears to stay completely off. PC no longer recognizes the phone when trying to enter fastboot mode (tried all the hold volume and power combinations). Only sign of life for the phone is holding down the power and volume + for maybe 40 second there's a brief green flicker. All this said, also can't get the PC to recognize it in EDL mode. This may in part be a lack of a USB 2.0 port, gonna try and get a hub to test it. BUt otherwise, really hard bricked Mix Fold 2 here, gents. This thing doeesn't have easily accessible touch points. And those aren't indicated online anyway. Wondering if a deep flash cable might be worth an $10 investment? Anybody have any suggestions? If I can get it in EDL mode I'll pay somebody to restore it but as it stands, its a $1500 brick.
Good news is my Fold 4 is my daily driver and even have a Flip 4 for fun. Still...
Click to expand...
Click to collapse
I sent you a P.M.

johnnobts said:
OK, so not happy. After failing to flash the new MIUI 14, then could not go back to the original 13, could not flash via fastboot at all, kept failing. Modified the flash_all.bat thinking that would fix the phone (was stuck with red fastboot logo on phone perpetually), only to find the phone screen now appears to stay completely off. PC no longer recognizes the phone when trying to enter fastboot mode (tried all the hold volume and power combinations). Only sign of life for the phone is holding down the power and volume + for maybe 40 second there's a brief green flicker. All this said, also can't get the PC to recognize it in EDL mode. This may in part be a lack of a USB 2.0 port, gonna try and get a hub to test it. BUt otherwise, really hard bricked Mix Fold 2 here, gents. This thing doeesn't have easily accessible touch points. And those aren't indicated online anyway. Wondering if a deep flash cable might be worth an $10 investment? Anybody have any suggestions? If I can get it in EDL mode I'll pay somebody to restore it but as it stands, its a $1500 brick.
Good news is my Fold 4 is my daily driver and even have a Flip 4 for fun. Still...
Click to expand...
Click to collapse
Sorry about that. I was the same situation two days ago. Please use the "fastboot enhance" program and get into the "fastbootD" mode via this program. Then you will see your phone partitions and logical parts. Erase and resize each part as 1000 bytes. But do not touch the phone's "... _b" parts. Then switch again from fastbootd to fastboot mode into the program but never reboot the device or unplug the cable. Leave the program open background. And then download the Mi flash tool (vers. 2021.2.26.0) and do not use any other or newer version. Into the Mi flash configuration, delete checkpoint writings and leave it blank. Then tick "Erase all" box. After that, download this: https://hugeota.d.miui.com/V14.0.22...2.0000.00_13.0_cn_chinatelecom_f79146cd66.tgz
Flash the image via mi flash program. That s it.

okanaltan said:
Sorry about that. I was the same situation two days ago. Please use the "fastboot enhance" program and get into the "fastbootD" mode via this program. Then you will see your phone partitions and logical parts. Erase and resize each part as 1000 bytes. But do not touch the phone's "... _b" parts. Then switch again from fastbootd to fastboot mode into the program but never reboot the device or unplug the cable. Leave the program open background. And then download the Mi flash tool (vers. 2021.2.26.0) and do not use any other or newer version. Into the Mi flash configuration, delete checkpoint writings and leave it blank. Then tick "Erase all" box. After that, download this: https://hugeota.d.miui.com/V14.0.22...2.0000.00_13.0_cn_chinatelecom_f79146cd66.tgz
Flash the image via mi flash program. That s it.
Click to expand...
Click to collapse
so again, i only have all black screen, can't tell when or if its even on. any button combinations when plugging phone into usb cable? screen doesn't even give me fastboot or anything....

johnnobts said:
so again, i only have all black screen, can't tell when or if its even on. any button combinations when plugging phone into usb cable? screen doesn't even give me fastboot or anything....
Click to expand...
Click to collapse
Do you see the blank screen on only front screen or both screens are blank?

okanaltan said:
Do you see the blank screen on only front screen or both screens are blank?
Click to expand...
Click to collapse
Both sadly

johnnobts said:
Both sadly
Click to expand...
Click to collapse
Although there is no image, try to enter fastboot mode with the cable plugged in. In the meantime, keep the "fastboot enhance" program open. Because the program is showing the connections moment by moment. In case of you see any port connection, you can immediately start the recovery.

Well appreciate the instructions but can't seem to find any button combo to get into fb mode. I'll try the deep flash cable I bought later but really not looking good.

Do connect with pc?
Wich mode detect by pc if pc detect EDL mode then try EDL flash
This is link how to flash in EDL mode:
https://www.google.com/url?sa=t&sou...4QFnoECBcQAQ&usg=AOvVaw3ERwG52pReMOqt59rsB1q6

Using a PC, with a USB 2.0 port. As I said only sign of life phone gives me is a slight green quick flash after holding vol up and power for 30 seconds or so. But no combination when plugged into PC will make the PC recognize the phone as anything, PC doesn't detect the phone at all.... I have a deep flash cable coming and hoping it may kick the phone into edl mode, but doubting it will work. Telegram help so far hasn't given any advice, there are no touchdowns listed for the fold 2 yet, and even if there were, I'd be reluctant to try and open this phone up.

Try to get a edl cable, compare the cost of your device vs the cabale. I just did a quick Google search, and I see there is no firehose fil, so what are you expecting to do when in edl

Arealhooman said:
Try to get a edl cable, compare the cost of your device vs the cabale. I just did a quick Google search, and I see there is no firehose fil, so what are you expecting to do when in edl
Click to expand...
Click to collapse
sigh, I don't know. I may end up storing the fold 2 in my drawer in hopes there's a solution one day. again, not my daily driver so not desparate to fix it, but still.
like your quote there, btw...

I'd try one of the groups on telegram miui edl groups, explain the situation and see if they can fix it remotely. at worst it costs you $40 and if they can't fix it they'll give it back. I think they'll be able to fix it remotely though

knives of ice said:
I'd try one of the groups on telegram miui edl groups, explain the situation and see if they can fix it remotely. at worst it costs you $40 and if they can't fix it they'll give it back. I think they'll be able to fix it remotely though
Click to expand...
Click to collapse
Couple guys tell me I need to have the PC detect the phone in edl mode first.

johnnobts said:
Couple guys tell me I need to have the PC detect the phone in edl mode first.
Click to expand...
Click to collapse
Yes, it needs to be detected. First step is to boot into edl.

johnnobts said:
Couple guys tell me I need to have the PC detect the phone in edl mode first.
Click to expand...
Click to collapse
With mi 11 ultra I had only to install drivers
And connect phone to PC
It automatically goes to edl
Try that

rowihel2012 said:
With mi 11 ultra I had only to install drivers
And connect phone to PC
It automatically goes to edl
Try that
Click to expand...
Click to collapse
no luck

well, had a guy try walking me through it, even took over with teamviwer and can't get the Mix Fold 2 to be detected when connecting to my PC at all. Other than cracking it open and touching the EDL points together, looks hopeless. I'm not planning on trying to open this up. Know any trustworthy repair guys?

Ok, took off the back panel, have no idea if the touch points are here. With my luck they will be on the inside underneath the main display. Really just need to wait for a diagram marking the mix fold 2 touch points I guess...