Related
I've spent hours trying to workout how to use adb
I'm using Amon_RA's recovery image and want to run a BART backup but it forces you to use adb, which i can't workout
help please!!!
Did you download the Android SDK for OS X?
Please give us some more information, such as the steps you've taken and any errors or other information you get from the Terminal.
yes i have downloaded the sdk from the website
but everytime i even check what devices are connected etc it fails
i open terminal, drag the tools folder into it, it then ses its created a directory
when i try to put in the commands "adb devices" or "bart" however, it ses there is no such command
do i need to put my phone into recovery, or mass storage or something
im stumped
You need to add the tools directory to PATH variable on your computer
Here's how you do it (the alternative way is easier):
Run this in Terminal
Code:
cd
nano .bash_profile
a text editor will open. add this:
Code:
export PATH=${PATH}:/path-to-android-sdk/tools
where you replace "path-to-android-sdk" with the real path.
Alternatively you could run this command in the terminal:
Code:
echo -e "\nexport PATH=${PATH}:/path-to-android-sdk/tools" >> .bash_profile
What you have done is to tell the shell to also look inside the tools directory when entering a command
Oh, in addition to Repp's suggestions, I know in Linux (and I dunno about everyone else) I need to be root to run adb properly. So maybe become root on the Mac. To do so, you need to be an Admin user, not a regular user, and at the Terminal, type
Code:
sudo -s
and then enter your user password when prompted.
okay ive done that, i dont know if it came back with the right response tho
i tried the first method and got into the text editor, i then typed what you said and it returned no response, i dont know if this is correct?
if so what do i do next?
Rather than altering your path, you can also navigate to the sdk/tools directory and run adb like so:
Code:
./adb devices
But you have to be inside the directory where the "adb" command lies.
Also, see my note above regarding root users.
Aah sorry. Just save and exit (press Ctrl+X and answer yes to whether or not you want to save). You could also try the alternative way.
craig0r said:
Oh, in addition to Repp's suggestions, I know in Linux (and I dunno about everyone else) I need to be root to run adb properly. So maybe become root on the Mac. To do so, you need to be an Admin user, not a regular user, and at the Terminal, type
Code:
sudo -s
and then enter your user password when prompted.
Click to expand...
Click to collapse
I have always used it as normal user and it has worked. Don't know why you would need to be root
how dyou get into the directory?
i usually just drag the tools folder into terminal.
is this correct?
DaNiEl FrEnCh said:
how dyou get into the directory?
i usually just drag the tools folder into terminal.
is this correct?
Click to expand...
Click to collapse
At the Terminal type
Code:
cd /Users/YourUserName/path/to/android_sdk/tools/
./adb devices
Repp said:
I have always used it as normal user and it has worked. Don't know why you would need to be root
Click to expand...
Click to collapse
Yeah, it's weird, but it works for me.
You change directory in the terminal with the command cd. So if I wanted to go to the Desktop directory I would write:
Code:
cd ~/Desktop
(~ is like a shortcut for your home directory which is the same as the directory /Users/your-username)
Did any of the methods work (they should )?
to repp, ive done that, all i need to know now is how to use the bart backup function from Amon_RA's recovery image, in adb
craig0r said:
Yeah, it's weird, but it works for me.
Click to expand...
Click to collapse
And it doesn't if you're not root?
DaNiEl FrEnCh said:
to repp, ive done that, all i need to know now is how to use the bart backup function from Amon_RA's recovery image, in adb
Click to expand...
Click to collapse
And it worked?
Unfortunately I have never done that so I can't help you there
how can i check if it worked?
Just run adb from any directory which is not the tools directory.
For example:
Code:
cd
adb devices
where the first line (cd) changes directory to your home directory (the command cd without a path does that) and the other one should list connected devices. As long as it doesn't say
Code:
-bash: adb: command not found
or anything like that, you should be fine
EDIT: If you want to use adb, you don't have to do the "cd" part first. This time only
its working now i can seee what devices i have
Code:
Dans-MacBook:tools Dan$ ./adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT98DL900002 device
but the main reason i want to use it, is to use it with Amon_RA's recovery
i neeed to do a BART backup so i can switch from the 2.1 rom from lox too 3.0 from modaco
I have never used BART, but unless I'm mistaken, it does almost the same thing as a nandroid backup (?). You could try that instead. Don't know about Amon_RA, but it's possible from MoDaCo's fastboot (linked to and explained how to install here)
other than that, there's nothing I can do
Repp said:
And it doesn't if you're not root?
Click to expand...
Click to collapse
That's right. Probably something to do with permissions in /dev/. It doesn't bother me enough to go hunting the problem down.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
originally,we used a zip file flashable in recovery. i have found it to work on gsm devices with 1.44 hboot and CW recovery. it did not work with twrp. if the following is too scary,feel free to test the zip files. that thread,info,and downloads can be found here. since not all recoverys are working,these values can be changed with simple adb commands.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed(see this thread if you need help installing superuser. use the keep bootloader locked directions)
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for giving me the echo comand,so yall didnt need to dump,edit with a hex editor,and copy back
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-kdj67f for fearlessly testing and putting up some screenshots in post 5. thanks!
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
*i have tested this on my gsm htc one. if someone wants to test on vzw,ill add you to the credits
mine!
So, this will work with hboot 1.54? And are you sure the memory blocks are correct for Verizon? I will test...
I'm s-off, stock Rom, cwm recovery and rooted.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
So, this will work with hboot 1.54? And are you sure the memory blocks are correct for Verizon? I will test...
I'm s-off, stock Rom, cwm recovery and rooted.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
99% sure we can certainly dump p3 and have a look-see first,if you'd like. We woukd need a dump from someone whose unlocked or relocked
Sent from my HTC One using Tapatalk 2
99% is good enough for me haha! Phone just hut 50% charged, give me a minute. Will post back with pictures.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 08:56 PM ---------- Previous post was at 08:41 PM ----------
Confirmed, code working. Flags set/reset. Phone even reboots and works will upload pics/screenshots.
Thanks!
Starting out unlocked:
Locking:
Locked:
Unlocking:
Re-unlocked:
Very good work!
Awesome! Thanks for confirming
Sent from my HTC One using Tapatalk 2
That was super easy... great write up! This will save so much time getting an unlocktoken and running through HTCdev. Many thanks!
scotty1223 said:
99% sure we can certainly dump p3 and have a look-see first,if you'd like. We woukd need a dump from someone whose unlocked or relocked
Click to expand...
Click to collapse
Verizon HTC One here, S-Off with SuperSU but otherwise stock, locked bootloader, hboot 1.54. I just did
Code:
dd if=/dev/block/mmcblk0p3 of=orig bs=1 seek=33796 count=4
and looked at the resulting dump and it has "PGFS" not nulls at that offset. I'm wondering if we should write "PGFS" back on Verizon/hboot 1.54 and not nulls?
bjorheden said:
Verizon HTC One here, S-Off with SuperSU but otherwise stock, locked bootloader, hboot 1.54. I just did
Code:
dd if=/dev/block/mmcblk0p3 of=orig bs=1 seek=33796 count=4
and looked at the resulting dump and it has "PGFS" not nulls at that offset. I'm wondering if we should write "PGFS" back on Verizon/hboot 1.54 and not nulls?
Click to expand...
Click to collapse
sounds like youre looking at offsets 00 01 02 03. every device ive looked at so far has the PGFS at that location. i havent looked ata vzw p3,but t mobile follows that. youll find the HTCU,HTCL,or nulls at 8404 8505 8406 8407.
im not sure your command is showing you the correct location. id dump and look at the whole thing.
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3
Hey Scotty,
I can't thank you enough for this info. I really didn't want to unlock via htcdev and it's been getting tiring making zips for everything I want to flash. This solved my problem and is reversible without record. You are the man and thanks for putting in the time.
isdnmatt said:
Hey Scotty,
I can't thank you enough for this info. I really didn't want to unlock via htcdev and it's been getting tiring making zips for everything I want to flash. This solved my problem and is reversible without record. You are the man and thanks for putting in the time.
Click to expand...
Click to collapse
glad to help
Can someone explain the benefits to me of being able to change between locked/unlocked? If not.... That's cool.
Sent from my HTC6500LVW using Tapatalk now Free
BaBnkr said:
Can someone explain the benefits to me of being able to change between locked/unlocked? If not.... That's cool.
Sent from my HTC6500LVW using Tapatalk now Free
Click to expand...
Click to collapse
For this thread and most people's needs, unlocking this way after s-off saves time. Re-locking just proved it was reversible in case someone did want to be locked again. Another way to get back to stock for warranty purposes, etc...
Most importantly, to prove it can be done!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Fantastic, can this work for HTC One S too?
maybe needs finding correct blocks?
what it is unclear to me is that:
your method to unlock bootloader needs S-OFF, but S-OFF needs Unlocked bootloader and SuperCID, so maybe for HTC One S it's different
thanks for clarification
icest0rm said:
Fantastic, can this work for HTC One S too?
maybe needs finding correct blocks?
what it is unclear to me is that:
your method to unlock bootloader needs S-OFF, but S-OFF needs Unlocked bootloader and SuperCID, so maybe for HTC One S it's different
thanks for clarification
Click to expand...
Click to collapse
blocks are the same for one s.
method does indeed need s off. most common way to achieve s off for devices on the unlock program is via intial unlock thru htcdev to install root and recovery. at this point the commands are useful to get back to locked,and if one needs unlock after being locked for some reason. vzw is a bit different in that they cannot use htcdev,so a hack is needed to temproot,then s off. this does give them the luxury of being able to unlock without htcdev alltogether.
its also possible to s off via a java card,or be lucky enuff to find a user trial device that came that way. in this situation htcdev can be left out of the picture entirely.
hope that clarifes it
scotty1223 said:
blocks are the same for one s.
Click to expand...
Click to collapse
ok!
scotty1223 said:
method does indeed need s off. most common way to achieve s off for devices on the unlock program is via intial unlock thru htcdev to install root and recovery. at this point the commands are useful to get back to locked,and if one needs unlock after being locked for some reason.
Click to expand...
Click to collapse
ok...clear
scotty1223 said:
vzw is a bit different in that they cannot use htcdev,so a hack is needed to temproot,then s off. this does give them the luxury of being able to unlock without htcdev alltogether.
Click to expand...
Click to collapse
ehm...sorry...what is vzw?
its also possible to s off via a java card,or be lucky enuff to find a user trial device that came that way. in this situation htcdev can be left out of the picture entirely.
hope that clarifes it
Click to expand...
Click to collapse
thanks :good:
vzw=Verizon wireless
Sent from my HTC One VX using Tapatalk
scotty1223 said:
vzw=Verizon wireless
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
ah ok...
but since they need a temproot to get unlock without htcdev, wouldn't this be possible for all htc one (s)?
why is it limited to vzw?
icest0rm said:
ah ok...
but since they need a temproot to get unlock without htcdev, wouldn't this be possible for all htc one (s)?
why is it limited to vzw?
Click to expand...
Click to collapse
technically,yes. you could use a temp root and make a tool for any other carriers device so you would not have to unlock.
however, temp root exploits are typically patched quickly. htcdev is a reliable means of root to make other tools/exploits work. its much,much easier to simply unlock and install root and recovery than to keep looking for softwate temp root exploits.
with verizon you have no choice,since they do not allow official unlock.
Hello, can you please tell me why do i get this error ?
I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.
mrrflagg said:
I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.
Click to expand...
Click to collapse
Try creating a new fastboot folders and updating your HTC drivers. If the need arise, I can share with you my fastboot files
mrrflagg said:
I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.
Click to expand...
Click to collapse
It's probably that the folder is under admin previlage protection.
Try moving fastboot folder.
Didn't work:
-Try extracting fastboot to a new directory again.
Didn't work:
-Run cmd as admin, then use cd command to navigate into fastboot folder
ex: cd c:\fastboot\
convict_moody said:
It's probably that the folder is under admin previlage protection.
Try moving fastboot folder.
Didn't work:
-Try extracting fastboot to a new directory again.
Didn't work:
-Run cmd as admin, then use cd command to navigate into fastboot folder
ex: cd c:\fastboot\
Click to expand...
Click to collapse
Hi convict_moody, I have tried all that you suggested and went as far as removing all traces of my HTC drivers and
fastboot folders from my computer and tried it all from scratch and still no luck.
I recently did a HTC update to 4.2.2 and the Hboot is 1.73 with S on just if that info is of help?
Are the drivers properly installed, you see MYHTC in the windows device manager. If so that's fine.
Maybe download the android sdk bundle and open the command window in the platform tools folder.
Then put there the unlock code.bin file too and flash it
Fastboot flash unlocktoken unlock_code.bin
Mr Hofs said:
Are the drivers properly installed, you see MYHTC in the windows device manager. If so that's fine.
Maybe download the android sdk bundle and open the command window in the platform tools folder.
Then put there the unlock code.bin file too and flash it
Fastboot flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Drivers are up to date and I have tried with the sdk bundle, it seems to be so simple and not getting it to work is rather frustrating.
Starting to wonder if it's worth the hassle
mrrflagg said:
Drivers are up to date and I have tried with the sdk bundle, it seems to be so simple and not getting it to work is rather frustrating.
Starting to wonder if it's worth the hassle
Click to expand...
Click to collapse
Sure you logged in as admin on the pc ?
I'm the only user of this computer, got me stumped.
Yeah but when it's not setup as admin you can have trouble
Just want to thank you all for your advice, I tried the process on a different PC and it worked perfectly. Was my laptop the whole time.
Again a big thanks to you all
Dear Exprts
Kindly check this how to fix this problem
when i give a command in CMD (c:\fastboot is not recognized as an internal or external command, oparebale program or batch file)
please give me the procedure as soon as possible ...
i cant unlock the boothloader
Thnks
Deep
I dont get your question. What command u typed? Check if your cmd console working directory is the same as fastboot localization.
Just ctrl rght click in folder where fastboot is and click open command window.
Sent from my One V using xda app-developers app
dipusmart said:
Dear Exprts
Kindly check this how to fix this problem
when i give a command in CMD (c:\fastboot is not recognized as an internal or external command, oparebale program or batch file)
please give me the procedure as soon as possible ...
i cant unlock the boothloader
Thnks
Deep
Click to expand...
Click to collapse
You must have fastboot.exe and the 2 dlls at the same directori, where you are at the moment at console (e.g. you wrote c:\fatsboot, so you need to have fastboot.exe and the 2 dlls at c:\ root to run them.)
I recommend to run fastboot and/or adb from a subdirectory from root, e.g. c:\htc\
I havehave fastboot.exe and the 2 dlls at the same directori (I rote c:\fastboot....but the same result ...
I don't have any root file in c drive
i am attaching the file ...
Ken-Shi_Kun said:
You must have fastboot.exe and the 2 dlls at the same directori, where you are at the moment at console (e.g. you wrote c:\fatsboot, so you need to have fastboot.exe and the 2 dlls at c:\ root to run them.)
I recommend to run fastboot and/or adb from a subdirectory from root, e.g. c:\htc\
Click to expand...
Click to collapse
Check this command in attach file
& told me , whats the problem in command
dipusmart said:
Check this command in attach file
& told me , whats the problem in command
Click to expand...
Click to collapse
don't know what the problem here, but I had errors like this on windows 8.1 and win8, which based on the poor command-line support...
try to move to the folder itself first with cd command, then fastboot as command.
dipusmart said:
Check this command in attach file
& told me , whats the problem in command
Click to expand...
Click to collapse
First, do not place files in the root (system could have some restrictions to run files from here). Place them in any folder and run from there (e.g. c:\fb\fastboot.exe)
Second, usualy you must be in the folder where the running file is. So do this:
cd c:\fb
fastboot ...
---------- Post added at 03:07 PM ---------- Previous post was at 02:59 PM ----------
Btw, are you really sure you want to take the risk with unlocking/rooting/flashing? If you are not quite familiar with a simple computer tasks there is a big chance you will go wrong and the phone will become unuseful. Unless you have many of them and just playing around. =)
Have you tried using the windows AIO tool?
http://forum.xda-developers.com/showthread.php?t=1676686
you may find it easier, but please do read all the instructions carefully especially about making a backup.
thnks guys....
now i don't have warranty ...so i want to upgrade my phone
urgents.....!!!!!
i am already done unlocking/rooting
but i have to install titanium kiss kernal i just stuck in command prompt ..its just waiting for device
what can i do ,,,
dipusmart said:
urgents.....!!!!!
i am already done unlocking/rooting
but i have to install titanium kiss kernal i just stuck in command prompt ..its just waiting for device
what can i do ,,,
Click to expand...
Click to collapse
What exactly the command prompt says?
You have to start your phone in the fastboot mode to accept external commands. So I guess the command prompt is waiting until the phone will get to that mode.
kvestas said:
What exactly the command prompt says?
You have to start your phone in the fastboot mode to accept external commands. So I guess the command prompt is waiting until the phone will get to that mode.
Click to expand...
Click to collapse
In command prompt with your phone connected, and USB debugging turned on in your developer options, and in the folder with your boot.img (you'll need to rename the hellboy kernel file to just boot.img)
type
<adb devices>
you should see a reply showing your phones ID if you get this go for
<adb reboot bootloader>
wait for the phone to reboot to your white bootloader screen then go for
<fastboot flash boot boot.img>
then once the kernel is in
<fastboot reboot>
Again I strongly recommend using an AIO program to make sure you haven't missed a step. Its great to learn all the ways to work with your phone, but its primary use is a phone, if it breaks it won't be able to do that.
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.