Develop Bugs

ADB not seeing Evo

Sorry if this is a repost. But hopefully someone can help me out. I'm fully rooted, full nandroid unlock.full 100 yeards. Now this morning I was going to do the process for "Permanently replacing your recovery with ClockworkMod Recovery Image"
But for some strange reason, ADB doesn't see my Evo. I tried running "Command prompt" as administrator also and it wasa no go. I typed "adb devices" and my device wasn't listed like it was yesterday before I did a full nandroid Unlock.
Do anyone have any tips on how I can resolve this issue?
If this helps, I running the Bugless Beast Rom.
Thanks

You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.

thanks. I'll give that a try and reply back

Strange thing....before I rooted/flashed a rom I created a Nandroid backup (I think it was stock. It doesn't have Superuser Permission in my list of Apps). Well I reverted back to that nandroid backup and now ADB sees my Evo.
I will flash back to my previous rom and trywhat you posted. Hopefully tat'll work

phatalboom said:
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
Click to expand...
Click to collapse
Yeah, I tried what you suggested and itstill didn't see my Evo. I guess my only option is to revert back, then do the process.

Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.

I'm having same issues and it's not working. My device is not being seen. Do you I have to have the Evo in charging mode or Disk Mode?

chuckhriczko said:
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
Click to expand...
Click to collapse
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.

Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc

timothydonohue said:
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Click to expand...
Click to collapse
Thanks for trying to help me out. But it still didn't work.
toastcfh said:
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
Click to expand...
Click to collapse
What do you mean that I must run adb as root on my pc, i don't know what that mean. Do you mean run it by using the "Command prompt" program?
Also this only happens to me on the Bugless Beast Roms. When I revert back to my 1st nandroid backup that I was using before I flashed any rom, everything worked fine.

Is USB debugging enabled?

CentroniX said:
Is USB debugging enabled?
Click to expand...
Click to collapse
Thanks ...that fixed it! I enabled it typed "adb devices" and it showed up. thanks again!

No problem, glad you got it working! When I first started out I ran in to that trap over-and-over. Now I just make it a rule of thumb to turn it on after flashing and leave it on.
Have fun!

I would have started another thread, but this is basically a similar problem to the one I had at first with adb.
Ok...I was trying to install a rosie.apk that was in a zip format. Long story short, the OP informed me that he made a mistake and provided me the wrong information as to reinstalling the rosie.apk. He was giving me steps to "push it" via adb, instead of flashing it.
No problem to Poster and thanks for help if you reading this . But anyways after all that, When I open up "Cmd" and type anything with adb in front of it...adb devices, adb shell..., i get the message that adb is not recognized as a internal or external command. Before this incident happened i was able to just type "adb devices" and my Evo would show.
Do anyone know how to fix this?
By the way I also tried typing all the commands in the previous posts...and I get the same error message.
**Update** I got it working I had to redo the path. All is good now.
Thanks much!

You need to be in the tools directory of the sdk so cmd can find the adb command.

[Q] rooting slide in ubuntu

Hey If anyone can help i have a few questions about rooting the slide in ubuntu
the "loop" script will not run regardless of what i do....also i can't seem to get the phone to show up with adb devices when i am in the bootloader
i can see the phone when it is in the rom but for some reason it won't show in the bootloader
thanks in advance

just type
Code:
adb devices
in terminal, and then when you select recovery and press enter, press "ENTER, UP, ENTER, UP, ENTER, UP...) really fast...and hope it works! if not lather, rinse, repeat...

There are instructions in the rooting thread on making an equivalent script for MacOS (which should work under Linux as well.) If you tried to run a DOS batch file under Linux thinking it would work...well, that's a judgment for another day
-------------------------------------
Sent via the XDA Tapatalk App

The Mac script does not run as a sh script on linux.
(PS: don't for the ./ before adb on a linux term. (./adb etc...))
beartard said:
There are instructions in the rooting thread on making an equivalent script for MacOS (which should work under Linux as well.) If you tried to run a DOS batch file under Linux thinking it would work...well, that's a judgment for another day
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using Tapatalk

Ive got a loop script for linux that I can send you when I get home. And like Indikut said, don't forget to add "./" before adb.

chrisinaz said:
Ive got a loop script for linux that I can send you when I get home. And like Indikut said, don't forget to add "./" before adb.
Click to expand...
Click to collapse
No need for the ./ if you added the sdk tools folder to your PATH.

Why that MacOS script doesn't work in bash on Ubuntu is beyond me. It looks to be formatted correctly.
Code:
#!/bin/sh
while [ 1 ]; do
adb devices;
sleep .25;
done
You could always use the following equivalent:
Code:
#!/bin/sh
watch -n .25 adb devices;
done
Assuming adb is in your path, this would run it every 1/4 second. You could, of course, change it to suit your location for adb (/usr/local/bin/adb or other location).

Cool thanks ..I will try that for the loop script
The other issue I have is that I can't see my phone as a device when I type adb devices in the bootloader ...it works fine when the phone is in the rom tho....I tried searching for the problem but I can't seem to find a solution ....I may just have overlooked it tho

beartard said:
Why that MacOS script doesn't work in bash on Ubuntu is beyond me. It looks to be formatted correctly.
Code:
#!/bin/sh
while [ 1 ]; do
adb devices;
sleep .25;
done
You could always use the following equivalent:
Code:
#!/bin/sh
watch -n .25 adb devices;
done
Assuming adb is in your path, this would run it every 1/4 second. You could, of course, change it to suit your location for adb (/usr/local/bin/adb or other location).
Click to expand...
Click to collapse
thanks again for the help with my problem i have a feeling the macos script would of worked i was using the wrong command i ended up typing "sh loop.sh" and it ran the script ....alltho i don't see it spamming adb devices ...it seems to just output it one time ....
now all i have to do is get the phone to show up when its in the bootloader....off to the search button i go

newspeak said:
thanks again for the help with my problem i have a feeling the macos script would of worked i was using the wrong command i ended up typing "sh loop.sh" and it ran the script ....alltho i don't see it spamming adb devices ...it seems to just output it one time ....
now all i have to do is get the phone to show up when its in the bootloader....off to the search button i go
Click to expand...
Click to collapse
As soon as you hit power to go to recovery either A) Activate the stupid script or B) mash ENTER+UP+ENTER+UP+ENTER until your keys fall off. I only got it to work the latter way.
Also, in Linux I've found that you'll get ???????? NO PERMISSIONS unless you do sudo ./adb devices.

The first time you run adb in a session, it should be started with sudo, since that starts the adb daemon. After that, any normal user's permissions (like running the script) should be ok. Make it easy on yourself and copy the adb executable to some place in your path (I use /usr/local/bin/). That way, you can delete the entire SDK unless you have plans for developing apps for Android.
I tried using my second code snippet above as loop.sh. I didn't go any higher, but it really doesn't have to work really quickly. I went up to .5 (executing "adb devices" twice a second) and it worked fine. You won't see a scrolling output like you would in DOS. The screen just updates if/when new info comes up (like showing the phone offline or in recovery.) When you get to the phone icon with the red triangle, hit VolUp and Power at the same time to get the recovery menu. The rest of the normal root tutorial should work for you.

ok thanks again for the help so far....here is where i am at ...i put adb in /usr/local/bin ...i can use adb devices ....the script is working for me but now when i get to the point where i push over the first file it says permission denied
i make sure to start adb with sudo ....i even tried running everything from a root terminal but i still get the same thing....i have already tried killing the adb server and restarting it with root permissions ...i have tried pushing the file with devices still listed as offline
kind of at a loss
here is what i get btw
"[email protected]:~/androidsdk/tools$ adb push ota.zip /sdcard/update.zip
failed to copy 'ota.zip' to '/sdcard/update.zip': Permission denied
[email protected]:~/androidsdk/tools$
"

I'm using a pretty fresh install of Ubuntu Lucid. I haven't messed with my user's groups or anything, so it's still fairly stock.
All I've done is copied adb to /usr/local/bin. The first run of adb (adb devices) is done as root using sudo. You could try running "sudo adb root" to begin with, and see if that makes a difference. After that, I can run any adb push commands as the normal user in GNOME's terminal.
Assuming you're set up like I am, if you're getting a permissions error after doing that, I'd hazard a guess and say the problem is on the phone's side rather than the computer.
Check and make sure USB debugging is checked in your settings. Beyond that, I'm stumped.

[GUIDE][US WIFI & 3G] How To Root Your Xoom From 3.2 Stock [PC & Mac]

**THIS IS FOR US WIFI & 3G XOOM**​
This guide in no way implies or expresses any warranties.
What you choose to do with your equipment is your sole responsibilty.​
________________________________________________________________________________________​
SUMMARY
You must already be running Honeycomb 3.2 on your Xoom **DO NOT USE WITH HC 3.2.1. IT HAS BEEN REPORTED TO CAUSE WIFI FAILURES** USE THIS TO ROOT HC 3.2 AND THEN UPDATE TO 3.2.1 USING THIS METHOD.​
You will be unlocking your Xoom, if you have not already. This will wipe data so make sure to back everything up that you would like to keep.
You will be performing steps in ADB. If you are not familiar with this, read HERE first.​
You will need Xoom USB drivers and Fastboot​
You will need the WIFI boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)​
OR You will need the 3G Verizon boot (kernel) partition with rooted stock 3.2 kernel (thanks & credit to, solarnz)​
You will need Superuser.apk and su binary to enable functioning root​
**Before you get started, make sure the USB Debugging option is enabled in the Settings. Go to Settings --> Applications --> Development -->USB Debugging**​
PROCEDURE
Download and unzip files. Place rootboot.img, superuser.apk & su binary in the same place you will open your command window.
Open command window:
Type; adb devices - you should see a long serial number on the screen. If no serial number appears, recheck your adb, sdk & moto usb driver files.​
Type; adb reboot bootloader​
Type; fastboot oem unlock - and follow the steps on your xoom's screen (You have to accept the terms by pressing the volume down key, and then select 'accept' by pressing the volume up key.)​
Allow the xoom to boot up completely and go back into settings and enable USB debugging again.​
In the command window on your PC type; adb reboot bootloader - (if xoom does not respond, disconnect from pc and reboot manually by holding vol up + power. then reconnect after fully rebooted)​
Type; fastboot flash boot rootboot.img (for WiFi)​
OR Type; fastboot flash boot 3Grootboot.img (for 3G Verizon)​
Type; fastboot reboot ​
Allow the xoom to boot completely - your xoom should be in normal operating mode for the remainder of the process.​
In the command window on your PC type; adb remount​
Type; adb push su /system/bin​
Type; adb shell​
Type; ln -s /system/bin/su /system/xbin/su (this line starts with lower case "L", like llama)​
Type; chmod 4755 /system/bin/su ​
Type; exit​
Type; adb push Superuser.apk /system/app​
Thats it...your done!! Unplug the xoom and reboot. Your xoom is now stock rooted. You can now flash ClockworkMod, other kernels and roms. To verify root, download a root user app from the market and run it. You should be prompted to allow superuser permissions.​
Mac Only Procedure​
You will need fastboot for mac - download HERE​
Open a terminal (located in the utilities folder)
Navigate to your sdk/platform-tools folder
Type; ./adb devices - (look for the xoom serial number to show its connected.)
Type; ./adb reboot bootloader
Type; chmod 755 fastboot
Type; ./fastboot oem unlock
Type; adb reboot bootloader
Type; ./fastboot flash boot rootboot.img
Type; ./fastboot reboot
Type; ./adb remount
Type; ./adb push su /system/bin
Type; ./adb shell
Type; chmod 4755 /system/bin/su
Type; exit
Type; ./adb push Superuser.apk /system/app
Disconnect and reboot xoom. Download a root app and test.​
If you found this helpfull press the THANKS button.​

Excellent write-up, I'll try this when I get a chance.
Been trying to downgrade and then get to the rooted, stock 3.2 using a couple routes shown here. They seem to create an issue with CWM not sticking...

Works great!
I just flashed back to 3.01, re-locked the WiFi Xoom (USA), OTA'd to 3.1 and followed that with the OTA to 3.2. I then unlocked and went thru your rooting procedure and it worked great. All tests indicate a successful root. Thanks for the practical guide!

thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?

_delice_doluca_ said:
thanks for the easiest way (i dont have an sd card) ..
one Q; why is this boot file about only 2 mb? the original one is aprx. 8 mb.. are we missing some features by replacing the boot files? or is it completely "stock+root" only ?
Click to expand...
Click to collapse
It is only a boot partition with rooted stock 3.2 kernel.
Sent from my HD2

[*]In the command window on your PC type; adb remount​[*]Type; adb push su /system/bin​[*]Type; adb shell​[*]Type; ln -s /system/bin/su /system/xbin/su ​[*]Type; chmod 4755 /system/bin/su ​[*]Type; exit​[*]Type; adb push Superuser.apk /system/app​
Click to expand...
Click to collapse
when I type adb remount after completely boot, I've got error device not found !!! any idea??

Hussain Isa said:
when I type adb remount after completely boot, I've got error device not found !!! any idea??
Click to expand...
Click to collapse
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.

Wow that was easy... Why cant all android devices be this open and straightforward? Im sooo pissed at HTC with the EVO 3D. Cant wait for the Galaxy S2 to come out
Mad respect to Motorola for getting this one right
And last but not least, Thanks so much to the OP for the great writeup!

jase33 said:
Are you in fastboot or is your Xoom booted normally? If you are in fastboot, reboot and let the Xoom load normally.
Click to expand...
Click to collapse
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App

Hussain Isa said:
I tried both, enabled USB debugging.
After the xoom load or in fastboot I get the same error! !!!
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Are you certain you have unlocked the bootloader?
Sent from my HD2

jase33 said:
Are you certain you have unlocked the bootloader?
Click to expand...
Click to collapse
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App

Hussain Isa said:
Its already unlocked, so I skipped the unlocking steps.
I will take another try from the beginning
Sent from my X10i using XDA App
Click to expand...
Click to collapse
If you get an error please post exactly what it says.
Sent from my Xoom

Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.

droidx1978z4 said:
Thanks for the write up. Just got my xoom today and right after I updated to 3.2 I thought that I may have a problem trying to root. Your guide worked perfectly for me. The only issue that I had was reading "ln -s," as "In -s." Yeah that was stupid of me.
Click to expand...
Click to collapse
Glad to here it! And thanks for pointing that out....I will clarify that in the op for others.
Sent from my HD2

thanks jase33 my problem was with the driver, I re-install it & now rooted

Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock

WOW! Thanks jase33 that was painless.
Everything worked great, just as you said it would.

fwempa said:
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like you worked it out.
Sent from my HD2

Where did you get fastboot for Linux. I just get my self a xoom today, I'm planning to root it but my laptop is running ubuntu
Sent from my Nexus One using XDA App

fwempa said:
Help... I have been having this same problem with multiple procedures. I have everything as instructed. USB debugging ON, SDK installed on Fedora 15, fastboot in /platform-tools folder. I type the first command (and this is the part that keeps happening despite the method used) "adb reboot bootloader" -- the Xoom reboots to screen desscribed as Motorola logo, centered, with "Starting Fastboot protocol support." in the top left corner. Also, in the terminal I get the message < waiting for device > after typing "fastboot oem unlock" That's it.. That's where I always get stuck. I am able to press power button and vol up to reboot normally. But, I can let it sit here like this with logo showing forever. Am I missing any drivers? As I said I am running Linux (Fedora). When I type "adb shell", I can successfully browse the Xoom filesystem.
SOLUTION: Ran fastboot command as root.
su
fastboot oem unlock
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Reinstall the driver, that will solve your problem
Sent from my Xoom using XDA Premium App

Pixel 3XL adb works, fastboot not seeing phone?

I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?

CruelSun said:
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
Click to expand...
Click to collapse
This happens because the device drivers are not completely installed.

CruelSun said:
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
Click to expand...
Click to collapse
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS)
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
then: chmod 644 51-android.rules
and: chown root: 51-android.rules

Thank you for the replies.
I tried to use adb/fastboot on a Win7 desktop after I posted the above, and I cannot get the phone and win7 to see each other at all.
I have since tried to get into recovery mode but get "No Command".
What can I do to move forward? Phone boots and works fine once I get out of recovery.
This phone is fresh from Google, never had a sim in it.

Thank you for the detailed answer. I am having difficulty implementing the mods you listed. I have been a Linux user on and off for several years but I do not have deep knowledge of the inner workings.
uicnren said:
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS) This returns "permission denied"
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev" <-- I have no rules.d file, just an empty folder named rules.d in that location
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Click to expand...
Click to collapse

Make sure you are using the latest ADB download files.
Sent from my Pixel 3 XL

Eudeferrer said:
Make sure you are using the latest ADB download files.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Yes, r28.0.3.

Update:
CruelSun said:
Thank you for the replies.
I have since tried to get into recovery mode but get "No Command". I found out how t get past this, I'm going to do a factory reset and start over.
This phone is fresh from Google, never had a sim in it.
Click to expand...
Click to collapse

Success!
After factory reset, stepped through process again, but still no joy on Linux (Certainly still the above mentioned group permissions issue which I failed to figure out how to fix).
Win7 did not seem to be working for a long time (got no popup on phone asking for debugging authorization), after a half hour of attempts I walked away for 15+ minutes and when I looked back at the phone the Debug auth popup was finally there...
Booted to fastboot, did $ fastboot flashing unlock <= Returned: "Finished. Total time: 0.356s" LOL, yeah, with me struggling since yesterday...
Now fastboot screen says Device status: Unlocked
Thanks to everyone here at XDA!

CruelSun said:
Success!
After factory reset, stepped through process again, but still no joy on Linux (Certainly still the above mentioned group permissions issue which I failed to figure out how to fix).
Win7 did not seem to be working for a long time (got no popup on phone asking for debugging authorization), after a half hour of attempts I walked away for 15+ minutes and when I looked back at the phone the Debug auth popup was finally there...
Booted to fastboot, did $ fastboot flashing unlock <= Returned: "Finished. Total time: 0.356s" LOL, yeah, with me struggling since yesterday...
Now fastboot screen says Device status: Unlocked
Thanks to everyone here at XDA!
Click to expand...
Click to collapse
Glad you figured it out.
Sent from my Pixel 3 XL

Hi !
I had the same issue here, new pixel 3 XL owner
win 10 home.
debugging mode active (allowed PC), OEM unlock checked.
searching for devices using : .\adb devices while the phone is on results : 89EY06JQW device
while phone Off : empty list.
trying to unlock using : .\adb fastboot flash unlock .
wont do nothing.
I did a factory reset, still the same results :/
any idea ?
done.
re-installing the drivers, reboot Pc, and using cmd without administration did it. lol

STALKER18 said:
Hi !
I had the same issue here, new pixel 3 XL owner
win 10 home.
debugging mode active (allowed PC), OEM unlock checked.
searching for devices using : .\adb devices while the phone is on results : 89EY06JQW device
while phone Off : empty list.
trying to unlock using : .\adb fastboot flash unlock .
wont do nothing.
I did a factory reset, still the same results :/
any idea ?
done.
re-installing the drivers, reboot Pc, and using cmd without administration did it. lol
Click to expand...
Click to collapse
Glad you got it sorted out.
Frankly I expected to have smooth sailing on my Linux PC, but had to resort to win7.
Sent from my Pixel 3 XL using Tapatalk

CruelSun said:
Glad you got it sorted out.
Frankly I expected to have smooth sailing on my Linux PC, but had to resort to win7.
Click to expand...
Click to collapse
Windows has to update. The 30 minutes was probably the update in the background. My windows 10 did the same thing. Linux doesnt work anymore. I used ubuntu with latest adb and fastboot packages. Manually installed newest tools zip. Nothing. I got it to work a few times. Windows 10 is a little buggy too. Only fastboot I found to work on the pixel 3 xl without and or little errors was my MacBook. Which I have dual booted to chromeos and Ubuntu in chromeos. Also restarting on windows anything puts it into the loop of things. You can install adb and fastboot on windows but they need a restart to work. Unless just mounting the file folder and using it that way.

I am still trying to get adb/fastboot to work on my Linux Mint 19.1 laptop so that I don't have to rely on an old Win7 machine to sideload monthly updates. I have been a Linux user on and off for several years, but I have no deep knowledge of what goes on 'under the hood'...
Can anyone here with a deeper knowledge of Linux and/or Mint 19 help me implement the mods that uicnren outlined, or otherwise help me get adb/fastboot to work?
uicnren said:
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS)
Click to expand...
Click to collapse
I think I succeeded in adding myself to the plugdev group with this command:
Code:
sudo usermod -aG plugdev cruelsun
uicnren said:
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
Click to expand...
Click to collapse
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
uicnren said:
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Click to expand...
Click to collapse
I Have not run these commands yet, as I am trying to do this in the order that uicnren specified...

CruelSun said:
I am still trying to get adb/fastboot to work on my Linux Mint 19.1 laptop so that I don't have to rely on an old Win7 machine to sideload monthly updates. I have been a Linux user on and off for several years, but I have no deep knowledge of what goes on 'under the hood'...
Can anyone here with a deeper knowledge of Linux and/or Mint 19 help me implement the mods that uicnren outlined, or otherwise help me get adb/fastboot to work?
I think I succeeded in adding myself to the plugdev group with this command:
Code:
sudo usermod -aG plugdev cruelsun
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
I Have not run these commands yet, as I am trying to do this in the order that uicnren specified...
Click to expand...
Click to collapse
Simplest method: https://github.com/corbindavenport/nexus-tools

CruelSun said:
...
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
...
Click to expand...
Click to collapse
I realize this is a bit old now, but, in case it's helpful for someone in the future...
Often the /etc/used/rules.d directory is empty. You just need to add the file 51-android.rules into that directory.
Code:
sudo touch /etc/used/rules.d/51-android.rules
You need to run that command as root which is why it's prefaced with sudo.
Then you can edit the file as described in the first post. As stated earlier, much better to type into your editor rather than cut and paste because you want to make sure no weird html characters get introduced.

Nexus 7 (2013) Stuck on boot loop: Android is starting - Optimizing apps.

I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.

corabict said:
I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.
Click to expand...
Click to collapse
if ok connect to computer then you can move files to computer

jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.

corabict said:
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.
Click to expand...
Click to collapse
reboot recovery and adb pull sdcard

corabict said:
No root or custom recovery.
Click to expand...
Click to collapse
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."

jjgvv said:
reboot recovery and adb pull sdcard
Click to expand...
Click to collapse
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
k23m said:
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."
Click to expand...
Click to collapse
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.

corabict said:
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.
Click to expand...
Click to collapse
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course

jjgvv said:
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course
Click to expand...
Click to collapse
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.

corabict said:
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.
Click to expand...
Click to collapse
adb pull /
and see What happened
avoid adb shell as it needs root.

jjgvv said:
adb pull /
and see What happened
avoid adb shell as it needs root.
Click to expand...
Click to collapse
Yes I tried that and returns this
>>c:\Adb>adb pull /
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: warning: stat failed for path /proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/222/task/1208/fd/15: Protocol not available