Hi folks.
I updated my mate 9 last night using firmware finder, phone rebooted, did the update thingy and then switched off. It didn't boot back up so tried turning on - nothing. Plugged in the charging cable, no light came on to indicate it was charging.
I have tried connecting to my computer using the USB 3 port and the computer does seem to recognise it as it makes that jungle sounds when connected (computer) and again when disconnected. I have tried doing the power vol down and that seems to create the PC to make the sounds again but there is nothing displaying on the phone itself. If you looked it at you'd think it was off.
So I guess it's a positive that the PC is getting some kind of response, and the phone must be working.
Can anybody suggest as to how I can get things back up and running? Remember the screen doesn't work on the phone since the update. I am on C636 converted from AL00 early last year.
Have tried HiSuite just in case but phone isn't recognised.
Thanks.
DT.
adb commands
Shooting from memory here...but have you tried any of the adb commands to see if the computer is seeing the phone?
adb kill-server
adb start-server
adb devices
If you get something from the devices command, then you should be able to
adb reboot
Also, if you are able, find another computer and install ADB as well has HiSuite software/drivers.
dwcasey said:
Shooting from memory here...but have you tried any of the adb commands to see if the computer is seeing the phone?
adb kill-server
adb start-server
adb devices
If you get something from the devices command, then you should be able to
adb reboot
Also, if you are able, find another computer and install ADB as well has HiSuite software/drivers.
Click to expand...
Click to collapse
Thanks for the reply.
Nope - doesn't seem to work. No idea what's happend but it appears to be kaput. Other than my PC recognising that I am connecting something when I plug it in to a USB socket, there is no other way of knowing if the device is even on. I've left it on charge over night, tried the power up/down (even though I can't see the screen) and have tried the appove. It did list a port that was open but no devices appeared as listed.
Will continue having a look to see if there are any other methods. Appreciate your help dwcasey.
DT
Totally at a loss as to what's happend. If I leave it plugged in to my PC it seems every 5 minutes the PC disconnects and reconnects to the phone (notifaction sounds). When plugged in, if I press the power button it gives the same notification sound to indicated disconnected and reconnected. Have tried updating drivers. Device is not listed under ADB when I type the command. It's a Chinese AL00 6/128gb so can't get it reparied locally (UK). Debating whether to bin it as I fear the worst. Will opening up and removing the battery do anything? A bit like removing the cmos battery from a motherboard and it resets?
Cheers for any help.
I've come to the conclusion that the phone is dead and that I have a few options.
1 hope for a repair but it'll cost a fair bit given it's a Chinese model and I'm in the UK.
2 sell it on fleabay, but it contains personal data.
3 stick it in a drawer and console myself with my Note 4, that's it originally replaced.
Phone is definitely toast. When I connect to a PC it loads as USB SER. It still makes some sort of connection but it's impossible to access the phone Absolutely no response from ADB/Fastboot.
Clearly an issue with the update using FF given It was this that caused things to go tits up.
Back to my Note 4. First time I've ever had this happen. Fingers burned, dammit.
btblue said:
3 stick it in a drawer and console myself with my Note 4, that's it originally replaced.
Click to expand...
Click to collapse
If you leave it long enough for the battery to go down (no idea how long that might be) then from a 'drained' phone state to plugging in, you might see a 'powered off charging' screen which would be nice. At least you might have a starting place once again.
Happened to me if you have no warranty ,then it will cost about 200-300 dollars to replace your motherboard.
btblue said:
Totally at a loss as to what's happend. If I leave it plugged in to my PC it seems every 5 minutes the PC disconnects and reconnects to the phone (notifaction sounds). When plugged in, if I press the power button it gives the same notification sound to indicated disconnected and reconnected. Have tried updating drivers. Device is not listed under ADB when I type the command. It's a Chinese AL00 6/128gb so can't get it reparied locally (UK). Debating whether to bin it as I fear the worst. Will opening up and removing the battery do anything? A bit like removing the cmos battery from a motherboard and it resets?
Cheers for any help.
Click to expand...
Click to collapse
Instead of binning it I suggest you disassemble your phone completely with the help of video guides and some fine screw drivers and replace the motherboard yourself. They shouldn't be too expensive on AliExpress. The phone and its components are quite easy to wrap ones head around. Just be wary of the glue they use to stick the battery to the case. It can be a bit of a bastard to get off, but it's worth trying for sure! I've opened it up for screen and camera replacement myself. And I don't count myself as a "phone repair geek" Best of luck on this endeavor!
Related
So my G8141 recently started rebooting whenever it would get disconnected from an audio out source via the headphone jack. That's been happening for about two days. Today, I had it plugged into my car, shut my car off, and my phone rebooted. And continued rebooting. Endlessly. Only way I managed to get it to shut off was Volume Up + Power + Camera (not sure what about that specific sequence did it, but I got one vibration followed by three vibrations, let go, and it was off). I got home, held Volume Down, plugged it into my Windows computer. The LED came on green, Windows found a new device...and nothing. Granted, I just wiped my desktop, so I don't have any of my android debug stuff installed, and I never got around to installing the drivers for this phone before now. So I downloaded the drivers from Sony, tried to install them, and...nothing. Windows says it can't find a driver for the device in the directory. Am I missing something, or is the phone FUBAR?
The phone already needs to go back to Sony for repair (the back cracked about a week after I got it)...do I have any shot of salvaging what's on it before sending it in? I don't think there's much if anything that's important, but I'd like to see what I can do before sending it in...because I bought the UK model from the UK and live in the US...so I have to ship it to the UK repair facility, per Sony help. Also, if I can get it working again, I'm not terribly worried about the back now that I have a case on the way, so I may just live with the cracked back, as long as the phone is stable.
Update: Plugged it into my work MacBook Pro, fastboot devices is giving me
Code:
???????????? fastboot
Same result whether sudo-ed or not.
---
Update 2: fastboot reboot-bootloader followed by fastboot devices lists an actual device. LED is blue. Progress?
Never unlocked the bootloader on this phone, so not sure what I can do from here...thoughts? I can't tell if it's a hardware issue or a software issue...device has updated a couple of times, so it's possible one of those updates introduced a bug. That said, the spontaneous reboot feels more hardware-y to me...reminds me of a PC with bad memory or something. If I could somehow get logs out of it, I suspect I'd find a kernel panic in there.
---
Update 3: Contacted Sony Support, they suggested using Xperia Companion to "repair" the phone. Currently doing what I believe is a stock reimage of the device using Companion. Next step is probably sending it to Sony UK :-/
Just a note for others that might be interested, green is download mode, blue is fastboot.
Well if you haven't unlocked bootloader just repair it? I don't really understand what the issue is about in your post.
So I was trying to just do a clean install. This phone had no mods installed.
I have done this many times and all went well. I am hoping that someone can help me understand what went wrong.
So working on linux, latest fastboot/adb (29.0.6-6198805) and the March image for blueline.
flashing radio and bootloader went fine. When I got to flashing the kernel it stopped after writing slot_a and rebooting into fastboot. I got the message "waiting for any device"
The phone displayed a warming (see pics) that the bootloader is unlocked and phone vulnerable and gave me an option to pause. after a few seconds it went into a "fastbootd" screen that I never saw before (see pic attached) which gave me options to restart or go back to bootloader. Either option breaks the flashing sequence which ends with error.
Re-flashing produces the same result.
Any suggestions what causes this?
Of course the phone does not boot anymore. But I can get to bootloader again using key sequence. Bootloader is unlocked.
Thank you!
Fastbootd happens part way through a flash-all beginning with Android 10. I assume you are using the flash-all script and now doing each command individually. If not, edit the flash-all to get rid of the -w to dirty flash and keep apps and user data. My guess though is that your path is referring to an older version of fastboot. If you have ever installed the apt version of fastboot, it becomes the first to load in your path. Instead, drop the March files into your updated platform-tools folder and ./ the flash-all command in terminal directly from that folder. In a pinch, you can also sideload the ota zip (which you will need to download separately of course) from fastbootd by entering recovery from there and sideloading. Fastbootd gets you into user space, so you should have adb sideload ability.
there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?
sliding_billy said:
Fastbootd happens part way through a flash-all beginning with Android 10.
Click to expand...
Click to collapse
I did not know that.
What is the "normal" sequence of events? In our case it got to fastbootd and the laptop seemed stuck into "waiting for any device" Am i supposed to press anything or it resumes on its own?
We tried choosing bootloader once and reboot another time but in both cases the process broke down. Are we supposed to wait longer or what?
metricusa said:
there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?
Click to expand...
Click to collapse
metricusa said:
I did not know that.
What is the "normal" sequence of events? In our case it got to fastbootd and the laptop seemed stuck into "waiting for any device" Am i supposed to press anything or it resumes on its own?
We tried choosing bootloader once and reboot another time but in both cases the process broke down. Are we supposed to wait longer or what?
Click to expand...
Click to collapse
I've never ran ChromeOS, but the reboot into fastbootd not retaining the connection would definitely be a problem. The sideload does no reboots until install is complete, so that would be a better way for sure. In reality the phone did at least one reboot into fastbootd. You'd need to try a flash-all with -w in place to see if it could pull off a clean install with the factory image and not lose track of the connection. No doubt it will lose track with individual commands . The normal sequence for factory flash now is just that... run the flash-all .sh it will go into fastbootd during install while terminal will continue to work. There are definitely some spots where nothing appears to be happening on the phone or terminal until reboot. Given the remote nature of your install, I do think a sideload (follow the directions on the pixel ota developers page where you DL the file) is the best option for you.
metricusa said:
there are no older fastboot/adb installed i checked. I did each command individually. Reason is long but the person with long nails in the pic is my daughter who is in Europe and I was trying to troubleshoot her pixel through WhatsApp .
I tried to do this flashing using her Chromebook and the stock linux emulation. This may be the problem i will come back to it.
So all files (images + fastboot/adb) were placed in one directory and I ran ./fastboot....
I can try and move fastboot/adb to a bin directory. i doubt this is the problem though. I ran them from home directory before.
I can try a sideload. never done it though.
Here's what i think happens and maybe you can tell me if sideload may avoid this situation:
ChromeOS has to give permission to Linux to use USB for a specified device. It does not remember that device after being disconnected though. Therefore I suspect that during the reboot into fastboot the phone looses USB permission for a second and hence breaks the process.
With all the covid thing all she has available is her Chromebook. I have a linux machine but it's here across the pond.
So does a sideload involve any intermittent re-boots where I may loose USB permissions?
Click to expand...
Click to collapse
I had the same problem with my PixelBook. My conclusion was ChromeOS does not forward the USB connection to the Linux container before the phone times out, but your theory about loosing USB permission may be correct. If you have developer mode enabled on the ChromeBook, try booting into Linux from a USB stick instead of running the Linux container. Unfortunately, I have no other solution.
dcarvil said:
If you have developer mode enabled on the ChromeBook, try booting into Linux from a USB stick instead of running the Linux container. Unfortunately, I have no other solution.
Click to expand...
Click to collapse
I agree but with my daughter abroad she can't do the USB stick thingy.
I'll explore the sideload. I'll have to test everything on my Pixel 3. I was trying to avoid that. I have both a Linux machine and a Chromebook here.
And yes, the permission is lost quite fast during a phone reboot. I tested it. I do however find it amazing that a Chromebook is capable of doing such advanced tasks.
I'll try again tomorrow and report back.
metricusa said:
I agree but with my daughter abroad she can't do the USB stick thingy.
I'll explore the sideload. I'll have to test everything on my Pixel 3. I was trying to avoid that. I have both a Linux machine and a Chromebook here.
And yes, the permission is lost quite fast during a phone reboot. I tested it. I do however find it amazing that a Chromebook is capable of doing such advanced tasks.
I'll try again tomorrow and report back.
Click to expand...
Click to collapse
What if you get phone into fastbootd, then plug in so the phone is recognized, then "fastboot update image-blueline-qq2a.200305.002.zip"
Or just unplug it once it gets to fastbootd and plug it back in...if it becomes unrecognized, unplug and plug it back in again when needed?
wangdaning said:
What if you get phone into fastbootd, then plug in so the phone is recognized, then "fastboot update image-blueline-qq2a.200305.002.zip"
Or just unplug it once it gets to fastbootd and plug it back in...if it becomes unrecognized, unplug and plug it back in again when needed?
Click to expand...
Click to collapse
I'll try that.
Unplugging opens another can of worms:
The reason we are doing this is bc the phone suddenly has a problem charging. Opening the battery setting shows a red battery with the message "can't charge now". Also if plugged in while turned off the little battery shows a question mark.
Google offered to exchange it but shipping it back and forth from Europe is 140$ each way and I got a new phone for less. On top of this I risk having to pay import taxes on it.
So in short, if unplugged the phone dies.
The intent of doing this burn was to see if this issue is software related. As I said it happened suddenly after a simple restart. Battey was fine and after restart was not.
I have a feeling it's not the software though.
Wow, that is really high for shipping. I mean, I ship from China to the US for like 20 USD, beside the point though really. She knows no one with an ordinary PC to test? Or a local cell phone service center in her area that could evaluate it? I mean the battery could be dead, or it could have, ehehe, been dropped and a connection loose or something. Not trying to imply anything there, just saying there are many variables at play. I would say if getting to fastbootd and trying the update does not work, then she should really look for a repair shop. Depending on where she is it should be fairly cheap or even free for them to look at it.
wangdaning said:
Wow, that is really high for shipping. I mean, I ship from China to the US for like 20 USD, beside the point though really. She knows no one with an ordinary PC to test? Or a local cell phone service center in her area that could evaluate it? I mean the battery could be dead, or it could have, ehehe, been dropped and a connection loose or something. Not trying to imply anything there, just saying there are many variables at play. I would say if getting to fastbootd and trying the update does not work, then she should really look for a repair shop. Depending on where she is it should be fairly cheap or even free for them to look at it.
Click to expand...
Click to collapse
Well the option is through fedex/ups. Shipping USPS has resulted many times in the package being stuck in customs for weeks. And the price is not necessarily much lower.
Yes we looked into having it seen by a repair shop but normally we should have been able to do flash it ourselves. Plus it's a good experience for her to be exposed to some linux and the basics of hacking a phone.
Another reason is that this has a high chance of being hardware related so whatever we spend on repair shop is wasted money.
I got her a Samsung A51 and she is out of trouble for now. I have had several bad experiences with pixels so this time I am officially done with spending a fortune on them.
Update as of this morning: It is clear that the USB permission is lost while fastboot performs a reboot during flashing. We tried to quickly re-allow the permission but while the terminal waits for a device patiently it looks that the loss of link is long enough for the phone to decide that something went wrong and goes into fastbootd.
We also tried to flash just the boot.img in both slots . that went well apparently but did not change anything and the phone is still unbootable. Tried recovery but it went back into bootloader with the error that it cannot boot boot.img.
So next step is sideload. i have to figure how that works
fastboot reboot fastboot, select recovery, apply update from ADB, adb sideload whatever.zip
Seems if there is no way to keep the phone on without it plugged in that is a problem. What about a cheap wifi charger, will that keep it on? I mean the phone will technically reboot going from bootloader to fastboot (fastbootd) and the permission will be lost. At least a repair shop could use a proper computer to test it.
wangdaning said:
Seems if there is no way to keep the phone on without it plugged in that is a problem. What about a cheap wifi charger, will that keep it on?
Click to expand...
Click to collapse
The phone stays on while it is connected to usb. Never died in this process. The connection loss is because of permissions not power.
Latest update: adb sideload worked just perfectly phone is back in running condition.
The bad news, which was expected, is that we did not solve the battery problem so it's hardware related. See attached pic.
In any case: A million thanks for the help. You guys rock!
At least we found out that a Chromebook can do some of these tasks but cannot do the flashing.
I placed a question on Chromebook community about a possible way to give Linux permanent permission to USB. If I find out any good news I'll report back.
Thank you and stay safe!
metricusa said:
Latest update: adb sideload worked just perfectly phone is back in running condition.
The bad news, which was expected, is that we did not solve the battery problem so it's hardware related. See attached pic.
In any case: A million thanks for the help. You guys rock!
At least we found out that a Chromebook can do some of these tasks but cannot do the flashing.
I placed a question on Chromebook community about a possible way to give Linux permanent permission to USB. If I find out any good news I'll report back.
Thank you and stay safe!
Click to expand...
Click to collapse
Glad you got the device up. As for the charging issue, have you tried a different wired charger or a wireless charger? I assume you are converting power somehow in Europe.
sliding_billy said:
have you tried a different wired charger or a wireless charger?
Click to expand...
Click to collapse
Yes. Tried different charger and a battery pack and also charging through USB from laptop. Did not try wireless. Before I bought the new phone she was using the phone connected to a battery pack.
As you can see in the pic the battery is red and it says "can't charge" while confirming that it does receive power.
I Googled the issue and there are several reports about same behavior. I also did talk to a repair shop over the phone and they said that the power module goes bad and it is a known problem with pixel 2 and 3. He also mentioned that there is a class action lawsuit but I cannot confirm the info.
It doesn't really matter at this point.
My aim was to eliminate the remote possibility this problem was due to some software issue. We solved this and from now on it's a google issue. As I mentioned Google offered to exchange the phone. But with COVID we had to postpone some flights when we could have made the exchange.
I will contact Google and ask for some workaround the COVID crisis. I hope they will be cooperative. I don't see why not.
Thank you all for your help!
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
Hi
I've been browsing the forum to find some help, but nothing matches exactly my situation and it is stumping me.
Have one plus 7 pro GM1913, attempted to install the latest update today that was pushed to my phone a few days back and set the phone down with charger cable attached and then look back at it and the screen is back at the security code entry tap my code and then back to booting, then black screen.
Attempted all manner of the key combos to get into the different reboot, fastboot modes, occasionally would get back to the loading screen which would then freeze with occasionally distorted graphics (one plus logo).
And now after a bit of charging (phone doesnt indicate it is charging at all) can't even get it back to the crashdump screen I could get to.
Crashdump screen didnt indicate any errors.
So i've been looking into possibly trying to trying to unbrick it with msmdownload tool. I have managed to install the qualcomm drivers, i believe i have the right version of the msmdownload tool.
However when i try attach my phone to the pc it keeps disconnecting all the time, my running theory is the phone is on and running through the boot sequence but I can't see it, but each time it disconnects then reconnects etc. Anyway I can't maintain a connection long enough to attempt msmdownload tool.
I also can't seem to boot my phone into EDL mode, following the below instructions:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
I am a complete beginner at this, but considered myself relatively tech savy enough to give things a go, but there is the old adage about knowing enough to be dangerous! Any help is appreciated.
Riverseo said:
Hi
I've been browsing the forum to find some help, but nothing matches exactly my situation and it is stumping me.
Have one plus 7 pro GM1913, attempted to install the latest update today that was pushed to my phone a few days back and set the phone down with charger cable attached and then look back at it and the screen is back at the security code entry tap my code and then back to booting, then black screen.
Attempted all manner of the key combos to get into the different reboot, fastboot modes, occasionally would get back to the loading screen which would then freeze with occasionally distorted graphics (one plus logo).
And now after a bit of charging (phone doesnt indicate it is charging at all) can't even get it back to the crashdump screen I could get to.
Crashdump screen didnt indicate any errors.
So i've been looking into possibly trying to trying to unbrick it with msmdownload tool. I have managed to install the qualcomm drivers, i believe i have the right version of the msmdownload tool.
However when i try attach my phone to the pc it keeps disconnecting all the time, my running theory is the phone is on and running through the boot sequence but I can't see it, but each time it disconnects then reconnects etc. Anyway I can't maintain a connection long enough to attempt msmdownload tool.
I also can't seem to boot my phone into EDL mode, following the below instructions:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
I am a complete beginner at this, but considered myself relatively tech savy enough to give things a go, but there is the old adage about knowing enough to be dangerous! Any help is appreciated.
Click to expand...
Click to collapse
I actually start the MSM tool ,wait until it boots up, position my cursor close to the start button on the tool, then I connect my phone to cable make sure it's attached to both PC and phone , put phone in edl ( hold power button and both vol up and vol down at same time) phone should go blank and you should see a connect on the MSM tool, hit start,,,, hth
My phone appears completely blank anyway, i've left it off charge overnight and then attempted to charge this morning, no real change. I've got no indication if the phone is charging or not or if it is even on.
When I connect via usb to my pc it is connecting and disconnecting constantly. I can't see anything via the screen.
What should edl mode on the phone look like?
Prior to this update there were never any issues with the phone, so im pretty sure it is connected to the update, just dont know how it has even wrecked the bootmodes etc
Riverseo said:
My phone appears completely blank anyway, i've left it off charge overnight and then attempted to charge this morning, no real change. I've got no indication if the phone is charging or not or if it is even on.
When I connect via usb to my pc it is connecting and disconnecting constantly. I can't see anything via the screen.
What should edl mode on the phone look like?
Prior to this update there were never any issues with the phone, so im pretty sure it is connected to the update, just dont know how it has even wrecked the bootmodes etc
Click to expand...
Click to collapse
When I go into edl it's a completely blank ,,,screen is black
Thanks for letting me know that!
I keep getting firehose communication handshake failed (i keep getting the disconnection sound from windows, like ive unplugged the usb, but it shows up in device manager) and then i do enum and it shows as connected in msm.
however if I hit start again I get sahara communication failed.
Riverseo said:
Thanks for letting me know that!
I keep getting firehose communication handshake failed (i keep getting the disconnection sound from windows, like ive unplugged the usb, but it shows up in device manager) and then i do enum and it shows as connected in msm.
however if I hit start again I get sahara communication failed.
Click to expand...
Click to collapse
I would just make sure you have all the correct drivers, especially l2, other than that iam out of ideas maybe someone with more experience will reply,, good luck
No worries cheers for the help though!
Hi to all,
how are you?
It's still a very long time i don't wirte here.
So i was a happy owner of a oneplus 6 from may 2019. I haven't problem and all works so well.
During a trip with fog and rain, the phone was wet and full of humidity, i had to use it during the rain 2 times to find the way to come back. When i was in home the display never respond. I tried to dry with a hairdryer but i won't go. In the meantime i buyeg a motog22 waiting to adjust my oneplus.
I'm using the original oneplus os, with last updates of august
So i remember i enabled the developers mode on my phone and i hoped also usb debugging and otg was enabled to cast the screen with this: https://plugable.com/products/uga-4khdmi (there are also the displaylink driver that tart at trhe phone startup), but i won't activate, don't no why.
Then i decided to try via adb to unblock wifi and other thing and make it usable with otg or thing like this: https://github.com/Genymobile/scrcpy
When i started abd i got this:
D:\myfolder\platform-tools>adb devices
List of devices attached
phonenumber unauthorized
I read some xda and stackoverflow posts but can't find a solution.
To authorize it i tried to delete adbkey inside .adroid folder, kill and start server but nothign working also cause the phone want an authorization that i can't give cause i can't see my display even if the display vibration is working and maybe also the touch.
Then i tried this:
adb reboot recovery
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
So i tried to restart the phone in boot recovery trying to see if the authoriaztion is enabled by default, but nothing happen.
I just wanted to push the keys to my phone and then using adb to reactivte wifi and something else almost to cast my phone or make a backup of some application (like google auth or microsoft auth...)
Are there an extreme solution or i have to wait the display and change it? I know this is the best solution but without this phone i have some activities...bloked It's incredible!
Thnks in advance for you help!
Bye