Database Info

fastboot driver for mac

for about two weeks, i've attempted to root the n5 using a mac. i have android sdk installed and fully updated. I've tried three different macs, one on mountain lion and two on mavericks. No matter what, adb can see the device when its fully booted. fastboot nor adb can see the device when it's in fastboot mode however.
i've mentioned this several times in the chainfire and chromium threads, but the only responses i get seem to be assumptions that every android device ever will work on mac without drivers, when clearly on 3 different macs i have fastboot not seeing the n5 in fastboot mode. when i ask if anyone has ever seen a mac see the device in fastboot mode there is nothing but silence. is it true this device has never been rooted on a mac? is it impossible (no assumptions please; if you haven't seen it work, don't spread the lie that it is possible)?
If the myth that this is possible stops getting spread, maybe i'll buy a windows pc solely to root. This is a cruel lie to spread that it's so simple when the poster has never seen it happen before though.

That's really strange. I rooted my old N4 on my mac mini at home, and my N5 on my iMac at the work.
What message do you see when you use ./fastboot devices?

@Blario i rooted it on a mac, no driver needed..you only need the sdk or fastboot and adb executable
post a screenshoot of the error, will make everything more easily to solve
also in fastboot mode, you can't use adb as you mentioned..in fastboot mode you can only use fastboot commands

Thanks so much for the replies! You're the first two people I've seen actually saw they've seen it work.
I went to get another failure result, so i could copy the screen exactly and paste it here, and omfg it worked.... After two weeks of fail, it finally worked. For hours I couldn't figure out why. Then when notifying another thread that it finally worked, it came to me. My Little Snitch was accidentally turned off this morning. I think that must have been it. I've noticed that adb uses network ports for communication... so much pain and finally success. Don't know whether to cry or jump for joy.

[Completed] Screen inaccessible(no display) usb debug disabled cmd help

Nexus 5 running 5.1 stock
I had recently and sadly had an accident with my phone where the screen is completely useless. Shattered is a harsh word, but it's sitting in that condition. It does however still turn on. There are parts of the screen that display, but for some odd reason, its completely mirrored and upside down.
I have Android tools and drivers installed. And knowing something like this might happen, I had USB debugging enabled. BUT, for even stranger reasons, I'm guessing it's disabled because through cmd on platform-tools, it says it's unauthorized. Though the little window of display my phone pushes, I'm guessing I'm getting a dialog asking for USB debugging to be enabled. I'm not too sure how I got to this window, but it randomly appears on restarts of the device, and half the time, it just restarts normally like any restart.
I was wondering if there was a way I can push a command line using cmd on my PC to accept or continue from the dialog box that I literally can't see.
I looked far and wide on Google and this beloved website, but am having a hard time finding a solution.
The device is bootload unlocked, running stock on Lollipop.
I do not know if rooting and installing TWP will affect my data, as it is the only thing I really don't want to lose. I wish to keep stock as I am completely fine with it and I have tried custom Roms, but I still wish to continue using stock.
I'm not too familiar with some words used in explanations on this site, so please respond as if I'm 7 years old :silly:
My initial goal was to (while having usb debug enabled) fastboot (i think i'm using the right term) Mobizen, then mirror the screen on my pc, and control the device to upload everything to my cloud storage.

momostarz said:
Nexus 5 running 5.1 stock
I had recently and sadly had an accident with my phone where the screen is completely useless. Shattered is a harsh word, but it's sitting in that condition. It does however still turn on. There are parts of the screen that display, but for some odd reason, its completely mirrored and upside down.
I have Android tools and drivers installed. And knowing something like this might happen, I had USB debugging enabled. BUT, for even stranger reasons, I'm guessing it's disabled because through cmd on platform-tools, it says it's unauthorized. Though the little window of display my phone pushes, I'm guessing I'm getting a dialog asking for USB debugging to be enabled. I'm not too sure how I got to this window, but it randomly appears on restarts of the device, and half the time, it just restarts normally like any restart.
I was wondering if there was a way I can push a command line using cmd on my PC to accept or continue from the dialog box that I literally can't see.
I looked far and wide on Google and this beloved website, but am having a hard time finding a solution.
The device is bootload unlocked, running stock on Lollipop.
I do not know if rooting and installing TWP will affect my data, as it is the only thing I really don't want to lose. I wish to keep stock as I am completely fine with it and I have tried custom Roms, but I still wish to continue using stock.
I'm not too familiar with some words used in explanations on this site, so please respond as if I'm 7 years old :silly:
My initial goal was to (while having usb debug enabled) fastboot (i think i'm using the right term) Mobizen, then mirror the screen on my pc, and control the device to upload everything to my cloud storage.
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
Please direct your question here for further assistance:
http://forum.xda-developers.com/google-nexus-5/help/help-thread-nexus-5-question-t2496506
Good luck!

[Completed] Need to recover files from (mostly) dead Motorola XT901

I am a PC technician and don't know much about phones. A customer brought me in a mostly dead phone and wants pictures of his kids recovered. I believe this is probably possible given the state. I want to give enough information without overloading anyone looking to help, so I will put it in sections.
What I know about the phone:
I never saw it working and I'm not a phone guy. The back says the model is XT901. This customer is not a tech, so only push updates would have likely been done., if even those were done. It came in roughly 2 weeks ago. That is pretty much the extent of what I know about the phone and its OS.
What the problem is:
When booting normally the Motorola logo comes up with the swirling blue around it. It stays on that screen forever.
What the phone can do:
I can get into a couple different menu systems with different key presses (which I don't exactly remember right now. It's kind of trial and error to get into the one I want). The less helpful menu has a "Recovery" option which just makes the phone boot to the swirling logo again. By retrying with different keypress combinations I can get it to show the android on his back with the exclamation mark. From there I can reboot into a different menu, where I found QC Diag, among other things.
What I need to do:
I need to connect the phone to a Windows 7 Professional 64 bit computer to recover, especially, pictures of his kid that he didn't have backed up.
The problem I ran into:
Four devices do show up in the device manager as "Unknown device". I did manage to get the QC Diag port set up following the instructions here:
googlebought.blogspot.com
/2014/12/motorola-qc-diagnostic-driver.html (separated because I can't post links, but the information might be important)
I used the PID listed on the page since I have no idea what to change it to or even if I need to change it, but it did seem to work for one unknown device. I then right-clicked on each of the 4 "Unknown" devices and browsed to that folder. One was detected and updated, the Motorola QC Diag Port on COM3. This did not make a drive letter show up as I had hoped.
What I have tried:
Downloading a few dozen drivers to get all 4 of these devices detected, starting with the latest standard drivers for the phone, Motorola Device Manager 2.5.4 and Motorola Mobile Drivers Installation 6.4.0. This is how I got to just 4 devices listed as "Unknown". Of course, there are currently only 3 unknown since getting the QC Diag port going.
My technical abilities:
I have been a PC tech for about 15 years and am pretty good at it. I have rooted Android devices before, but frankly that's just "download a program, push a button". I am utterly unskilled in Android, but I can follow even complicated instructions.
I am hoping that there is a mode I can go into (I believe I've tried all I can get into) or a driver I can install which will allow me to browse the directories on the phone. I realize this is more complicated than it sounds because of the difference in file systems. I would imagine that since I can see these devices in certain modes this is probably possible.
Thank you in advance for any help you can offer. I'm sorry it's long-winded, but I wanted to be thorough. Hopefully it's organized enough that you can skip over any information you don't need.

XDA Visitor said:
I am a PC technician and don't know much about phones. A customer brought me in a mostly dead phone and wants pictures of his kids recovered. I believe this is probably possible given the state. I want to give enough information without overloading anyone looking to help, so I will put it in sections.
What I know about the phone:
I never saw it working and I'm not a phone guy. The back says the model is XT901. This customer is not a tech, so only push updates would have likely been done., if even those were done. It came in roughly 2 weeks ago. That is pretty much the extent of what I know about the phone and its OS.
What the problem is:
When booting normally the Motorola logo comes up with the swirling blue around it. It stays on that screen forever.
What the phone can do:
I can get into a couple different menu systems with different key presses (which I don't exactly remember right now. It's kind of trial and error to get into the one I want). The less helpful menu has a "Recovery" option which just makes the phone boot to the swirling logo again. By retrying with different keypress combinations I can get it to show the android on his back with the exclamation mark. From there I can reboot into a different menu, where I found QC Diag, among other things.
What I need to do:
I need to connect the phone to a Windows 7 Professional 64 bit computer to recover, especially, pictures of his kid that he didn't have backed up.
The problem I ran into:
Four devices do show up in the device manager as "Unknown device". I did manage to get the QC Diag port set up following the instructions here:
googlebought.blogspot.com
/2014/12/motorola-qc-diagnostic-driver.html (separated because I can't post links, but the information might be important)
I used the PID listed on the page since I have no idea what to change it to or even if I need to change it, but it did seem to work for one unknown device. I then right-clicked on each of the 4 "Unknown" devices and browsed to that folder. One was detected and updated, the Motorola QC Diag Port on COM3. This did not make a drive letter show up as I had hoped.
What I have tried:
Downloading a few dozen drivers to get all 4 of these devices detected, starting with the latest standard drivers for the phone, Motorola Device Manager 2.5.4 and Motorola Mobile Drivers Installation 6.4.0. This is how I got to just 4 devices listed as "Unknown". Of course, there are currently only 3 unknown since getting the QC Diag port going.
My technical abilities:
I have been a PC tech for about 15 years and am pretty good at it. I have rooted Android devices before, but frankly that's just "download a program, push a button". I am utterly unskilled in Android, but I can follow even complicated instructions.
I am hoping that there is a mode I can go into (I believe I've tried all I can get into) or a driver I can install which will allow me to browse the directories on the phone. I realize this is more complicated than it sounds because of the difference in file systems. I would imagine that since I can see these devices in certain modes this is probably possible.
Thank you in advance for any help you can offer. I'm sorry it's long-winded, but I wanted to be thorough. Hopefully it's organized enough that you can skip over any information you don't need.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here but it's very quiet as it isn't the most popular phonein the world.
You can try posting your query there or in: Android Q&A,Help and Troubleshooting.
You'll have to create an account to post in the main forums.
Good luck

Shield Tablet Bug Fix "missing home button, recent tabs, notification centre" Nougat

Shield Tablet Bug Fix "missing home button, recent tabs, notification centre" Nougat
Hello Everybody. I have a Shield Tablet running Nougat. I have been experiencing the bug described in the Title a few times, and I finally found a way to solve such bug, at least in my specific scenario. It might not work for everybody but, as I have seen a lot of Users experiencing such bug and being forced to deal with it through a factory reset, I thought posting an easy guide might be helfpful to some. It is not rocket science, but for me it does the trick well. Should you feel there is an easier way to solve the same issue, please, do not hesitate to add it to this post.
I already posted this guide on the official Shield Tablet forum, but I cannot add the link because I am a new User (c'mon dudes, I am not spamming.. just trying to help ). Therefore, I am just gonna copy paste the guide. I apologise if the formatting is not ideal.
Hello Everybody, I know that there is an Android bug that has been creating issues for many years, also on shield tablets. When the bug starts, the home button disappears, it is impossible to open the "recent app" tab, the notification centre cannot be pulled down, and there are many other side effects. Since I started having this issue, I did quite a lot of research. Apparently, all I could find were information regarding how to solve the bug on Lollipop and Marshmallow, but nothing regarding Nougat. The way this bug is usually fixed is by starting the Setup Wizard on the device. Unfortunately though, I was not able to open it due to permission restrictions. Some guides mentioned installing Nova from the appstore, and setting up an action Widget in order to start the Setup Wizard. This did not work for me as well. What I was able to do, instead, was creating and setting up a new User profile, which then fixed the bug on my main User.
I am sure people more experienced and talented than me probably would have been able to find a neater way to make this happen. However, as I am quite a noob with these kind of things, I thought that writing a basic guide might be helpful for others as well.
Before going on, you should know that in my case, the only way to fix the problem is to have "debug settings" enabled on your device BEFORE the bug starts. When I first got the bug, I had not unlocked "debug settings" and I could not do it afterward, as tapping 7 times on the build number did nothing. You also need to have Android Debug Bridge (adb) installed on your computer and configured with the tablet.
Also, the process I will describing now creates a new User and switches to it by using terminal commands and Adb. I am aware that there would be an easier way to achieve the same result by going on "settings>Users" on the tablet. However, if you experience the same bug I was having, you will find out that clicking on the "Users" tab does nothing.
Here is a step by step guide of what I did:
1
Normally boot your tablet and connect it to the computer via usb cable
2
Run a command prompt windows on the computer and run Adb. Even if, due to the bug, you won’t be able to transfer files to the tablet via USB, adb should be able to interact with the shield anyway. To double check this, type the command: adb devices . You should be able to see your device listed.
3
It is now time to create a new User through the command prompt. You can do that by typing the command:
adb shell pm create-user User_Name
Once the new user has been created, the prompt will show you the respective User_ID. You will need to type such number in order to switch to that user, by typing the command:
adb shell am switch-user User_ID
eg. adb shell pm create-user Charlie
Success: created user id 11
adb shell am switch-user 11
4
Your shield should have now switched to the new user just created. At this stage, finish the new user configuration stage on the tablet. Skip all the google services related options, as you do not need them. When the configuration process is finished, the home button, the notification centre, the recent app, etc. should be back. Now that the bug is fixed, it should be possible to go back to your main User profile by simply switching User from the settings menu on the shield: settings>Users. At this stage, if everything went well, you should be logged with your main User, and the bug should have been fixed. It is now possible to go again on settings>Users and delete the new User created on step 3.
This is it. It works well for me and, even if I do not exclude that the bug will present itself again at some point, this is a 5 minutes solution to fix it. I apologise for any english mistake, as English is not by main language. Also, somebody might know of an easier way to solve the issue on Nougat, although I was not able to find any online, and that is why I wrote this short guide. I hope it will be able to help some of you!
Have a nice day!
Alberto

Please help - flashing incomplete

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!