Destr0y3r said:
Hello again! , this is just feedback of my experience the method to restore the phone to stock via ubuntu's terminal , if people are having some trouble with this , here i have a small tutorial on how to do it without a hitch.
SETTING UP FOR FASTBOOT
Open terminal and type in the following commands:
sudo apt-get install android-tools-fastboot
sudo apt-get install android-tools-adb
after this type in:
sudo apt-get update
Then here comes something a little bit complicated
you have to type : sudo apt-get install gksu (if i remember)
then after installing "gksu" type in
"gksu gedit /etc/udev/rules.d/51-android.rules"
this command will open a windows with a blank text file , in the text file type in:
# Motorola Moto G SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="2e80", MODE="0666", OWNER="plugdev" SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="2e76", MODE="0666", OWNER="plugdev"
after doing all this work if you guys didn't get confused simply reboot and just in case enable USB Debugging on the proggramer settings (to enable Developer settings go to About phone --> tap 7 times the Build number box and it will say "You are now a proggramer! that's it.
After rebooting your PC/Laptop , plug in your device and your device should have Moto G or "XT1032" as a name.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you want to check if you succesfully did the proccess , open terminal and type
sudo adb devices
It should show some sort of model name , that means everything is ok , now to continue with all this proccess just type in "sudo adb reboot-bootloader and it should get you to Fastboot , on fastboot type in "sudo fastboot" and then type in just like the thread says
example:
"sudo fastboot flash recovery recovery.img"
OPTIONAL
If you want to open terminal from your folder where you have everything just go to terminal and type the command
sudo apt-get install nautilus-open-terminal
Once it installs, type "nautilus -q && nautilus" & to quit and reopen nautilus, and check the right click option. <------ IF THIS LAST COMMAND DOESN'T WORK TYPE IN "sudo nautilus -q && nautilus" , It should open the File
Explorer , close the terminal and now an option "Open with terminal" will appear when right
clicking.
Click to expand...
Click to collapse
Hope my new first thread helped you out! , i copied this from a previous comment i made on the thread "http://forum.xda-developers.com/showthread.php?t=2542219"
Ubuntu 15.04 for XT1033 ?
Destr0y3r said:
Hope my new first thread helped you out! , i copied this from a previous comment i made on the thread "http://forum.xda-developers.com/showthread.php?t=2542219"
Click to expand...
Click to collapse
I want to use fastboot on a Moto G (XT1033) on an Ubuntu 15.04 64 bit. However, I am not showing USB connected on the device in fastboot mode, and fastboot devices gives blank output (i.e. no devices detected).
I have already installed fastboot using sudo apt-get install android-tools-fastboot
Created an anroid.rules file named ##-android.rules in /etc/udev/rules.d/. A persistent.rules file already existed with ##=70, so I used the same number for the android.rules file first. I also tried with ##=91, ##=50 and ##=51 after deleting the old files. None worked.
Tried all these variants in the android.rules file
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666", OWNER="plugdev"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="2e76", MODE="0666", OWNER="plugdev"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
Restarted udev using service udev restart. Rebooting yeilded same effect.
using mfastboot v2 (found on xda forums) didn't help. Device was still undetected
How do I get fastboot working with my XT1033 on Ubuntu?
Try: sudo fastboot devices
No use
All that extra stuff is not necessary. Start again, just install fastboot.
lost101 said:
All that extra stuff is not necessary. Start again, just install fastboot.
Click to expand...
Click to collapse
I'm sorry but I don't understand what you want me to do. Real noob here.
You want me to uninstall the android-tools-fastboot package, delete the rules files and simply reinstall the package?
e14ng said:
I'm sorry but I don't understand what you want me to do. Real noob here.
You want me to uninstall the android-tools-fastboot package, delete the rules files and simply reinstall the package?
Click to expand...
Click to collapse
Yes.
That did the trick. Thanks !!
Related
Forgive my noobness, but can domeone explain step by step how to install an app on the Android sdk? For example, I want to test doing this with launcherpro, so please explain how.
Sent from my always stock, EB13 Epic, awaiting EC05.
Two things first.
Your thread title, well sorry to say it sucks . Thread titles should give information about thread. Every second thread is called "please help" people get bored by that and don't even look into them anymore. A good title enables people to take one look and know wether they can help or not.
This should probably go to Questions&Answers too .
Now that i ranted a bit lets get to your question.
You can't install anything on the android sdk.
You can install something on the emulator provided by the sdk.
I guess thats what you meant?
typing "adb -help" into the console gives us this:
Code:
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
You could try that command to install LauncherPro on the emulator.
Is this what you wanted to know?
Dark3n said:
Two things first.
Your thread title, well sorry to say it sucks . Thread titles should give information about thread. Every second thread is called "please help" people get bored by that and don't even look into them anymore. A good title enables people to take one look and know wether they can help or not.
This should probably go to Questions&Answers too .
Now that i ranted a bit lets get to your question.
You can't install anything on the android sdk.
You can install something on the emulator provided by the sdk.
I guess thats what you meant?
typing "adb -help" into the console gives us this:
Code:
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
You could try that command to install LauncherPro on the emulator.
Is this what you wanted to know?
Click to expand...
Click to collapse
Yes, I meant the emulator, and where do I type this exactly? Thanks for the help.
Sent from my always stock, EB13 Epic, awaiting EC05.
try command prompt
johnston9234 said:
try command prompt
Click to expand...
Click to collapse
Wow, I didn't realize how much I didn't know about windows. Command promt?
Sent from my always stock, EB13 Epic, awaiting EC05.
Alright do this:
Windows Key + R
type cmd
press enter
navigate to your android sdk directory for example on my computer c:\android\
here is an extract from my cmd:
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\darken>cd c:\android\platform-tools
c:\android\platform-tools>adb install
Android Debug Bridge version 1.0.26
/... here goes some information .../
Any questions left ?
Dont think so, will try this later. Thanks guys.
Sent from my always stock, EB13 Epic, awaiting EC05.
K I typed this minus the quotes
"C:\users\(user name retracted)>c:\android\platform-tools\adb install [-l] [-r] [-s] c:\android\launcherpro-0.8.3.apk"
It says; "* daemon not running. Starting it now on port 5037 *
* daemon started successfully*
Error: device offline"
What should I do?
Sent from my always stock, EB13 Epic, awaiting EC05.
--creating a virtual devices (recommended froyo) and enter the following commands in sequence
CD C:\android-sdk-windows\tools--> go to directory and check here .apk file
Code:
adb start-server
android list avd
emulator -avd [emu name]
--refresh command window and enter the following command
Code:
adb install [apk name].apk
--or
CD C:\android-sdk-windows\tools--> go to directory
following command
Code:
adb start-server
adb devices
adb remount
adb install [.apk name].apk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sorry bad english...
ALPTEKÄ°N_ said:
--creating a virtual devices (recommended froyo) and enter the following commands in sequence
CD C:\android-sdk-windows\tools--> go to directory and check here .apk file
Code:
adb start-server
android list avd
emulator -avd [emu name]
--refresh command window and enter the following command
Code:
adb install [apk name].apk
--or
CD C:\android-sdk-windows\tools--> go to directory
following command
Code:
adb start-server
adb devices
adb remount
adb install [.apk name].apk
sorry bad english...
Click to expand...
Click to collapse
Edit: it didn't work, the list of devices won't show, its just an empty space.
Its ok about the English, I'm pretty sure I can do what you said, I just have to replace the names of your folders with mine.
Sent from my always stock, EC05 Epic 4G
Add the first post if you can get a positive result
ALPTEKÄ°N_ said:
Add the first post if you can get a positive result
Click to expand...
Click to collapse
Will do. I figured out I could just use the android browser within the emulator to download apps and I can install them just like on my phone. I still want to know how to do this.
Sent from my always stock, EC05 Epic 4G
Hello everyone,
I hope you can help me in my journey to downgrade HTC P510e flyer is in HC official to turn on the GB-S to put off then install rom more stable and http://forum phone activation. xda-developers.com/showthread.php t = 1314334
My HTC flyer is in S and not be naked and Roote of any operator.
But when I downgrade to GB method according http://forum.xda-developers.com/showthread.php?t=1428104
I created a folder on my PC and put the UCP selected and android-win-tools.zip and unzipped misc_version_universal.zip tacorot.bin
If error, let me know!
How to debug USB?
When I want to run the following commands via CMD / windows: adb push tacoroot.bin / data / local / adb push misc_version / data / local / adb shell chmod 755 / data / local / tacoroot.bin adb shell chmod 755 / data / local / misc_version adb shell / data / local / tacoroot.bin - setup
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url][/IMG]
it tells me: adb is not recognized as internal or external command, operable program or batch file.
Can you tell me how to run this operation until the end.
@ + Kacaouet ...
Try adb.exe then, adb devices.
Oh and, start command line from c: promt! There are different places to begin the command line, Google itS
The above possibly won't help but, you never know
Sent from my HTC Flyer P510e using xda premium
Kacaouet said:
it tells me: adb is not recognized as internal or external command, operable program or batch file.
Can you tell me how to run this operation until the end.
@ + Kacaouet ...
Click to expand...
Click to collapse
install Android SDK if you already have it add SDK folder to system path
or just start working from adb.exe folder -open cmd.exe in this folder usually ~\android-sdk\platform-tools\ don't forget to enable usb debugging on your phone
i.e.
I installed sdk in C:\Android so output from adb devices is something like that (look at the picture)
also check in Device Manager (start/run/devmgmt.msc) if you see ADB Interface when connected if not something is wrong make sure when phone is connected you see something like that in attached pict. (if not install HTC sync to get phone drivers )
adb devices is a vital check to see if pc connection is working well don't do anything until you get output from adb !
Get fastboot and adb tool for windows here OK
Download my universal misc_version and unzip to obtain the misc_version file. OK
Download tacoroot OK
Place both the misc_version and tacoroot.bin files in the same directory as adb OK
Procedure
Check the version number for your gingerbread RUU
my example : RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC. OK
Run the following adb commands
Code:
adb push tacoroot.bin /data/local/
adb push misc_version /data/local/
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup So far so good
At this point your device will reboot to recovery
Simultaneously press Volume Up, Volume Down and Power
Reboot your device
Run the following command OK
Code:
adb shell /data/local/tacoroot.bin --root
Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
For my part, nothing happens at this time when I made...
Run the following command:
Code:
adb shell /data/local/misc_version -s 2.23.405.3
Reboot to fastboot:
Code:
adb reboot bootloader OK
Relock the bootloader:
Code:
fastboot oem lock OK
Go back to fastboot mode ( lock causes the device to reboot )
Run your RUU The progress bar appears but stops and says "error 140"...
What shall I do to solve this problem?
May be a concern of the RUU!
How to execute the command to see if adb is well connected with flyer
If android sdk installation that I have updated to ensure proper operation?...
Seems some of the user unable to get the ADB working on Android 4.2.2 as the command prompt always stated that the device is offline so now I open my first thread after I found out the solution
What is ADB?
ADB, or the Android Debug Bridge, is a development tool included with the Android SDK (Software Developer Kit), which allows for communication from an Android device (such as a phone or tablet) to a personal computer, and vice-versa. This communication can be made over a wifi connection. However more commonly, it is made via a USB cable. adb can also be used by developers for communicating from a computer to a virtual android machine that is also running on the computer.
Click to expand...
Click to collapse
Android 4.2.2 now enforces RSA authentication via ADB and this is only supported in the latest versions of ADB.
In Android 4.2.2 (which corresponds to CyanogenMod 10.1), Google implemented some new security features for using ADB. The new "secure debugging" feature requires that you manually approve your computer for an ADB connection. This approval must be done from within the device, and only after any screen lock has been bypassed.
To access your 4.2.2 or higher device via ADB, you MUST ensure you are using a recently-updated Android SDK. Once the SDK (and therefore ADB) has been updated, you must ADB kill-server and ADB start-server any existing ADB daemon running on your computer. The first time you try to connect via ADB, you should receive a prompt on your device to Allow USB debugging? for this device (along with an RSA fingerprint identifying the computer). You may select the Always allow from this computer check box if you want the device to remember this computer, in which case you will not be prompted again when connecting your device to that specific PC.
Click to expand...
Click to collapse
Information from GitHub
ADB with version of 1.0.31 or later will works for Android 4.2.2
In order to use ADB :
Go to the ADB directory. Example C:\android-sdk-windows\platform-tools
Shift + Right click and then click "Open command window here"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OR use the command in command prompt
Code:
cd C:\android-sdk-windows\platform-tools
NOTE : You can change the directory based on where you placed the ADB files in your computer by simply changing the command to :
Code:
cd <your directory>
To check for ADB version :
Code:
adb version
There are two ways of upgrading your ADB version
Upgrade through Android SDK Manager
Extract the ZIP file that I attached below to the directory you want (example C:\ drive) and redirect your command prompt to the specific directory using "Shift + Right click" or by using the command in command prompt :
Code:
cd <your directory>
Before upgrading your ADB :
After upgraded ADB :
If your ADB is working correctly, you will see this when you plug in for the first time.
NOTE : Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb: Settings >> Developer Options >> Root access >> select "Apps and ADB"
NOTE : The RSA key for the host computer is stored in directory /data/misc/adb/adb_keys
After you press the OK button, in command prompt :
Code:
adb devices
NOTE : Some user reported that the ADB over network doesn't works if the option "Always allow from this computer" is not checked. So make sure you select the option if you want to use ADB over network
now you will get something like this and you are done...ENJOY
Some useful ADB command
Code:
adb shell
Code:
adb logcat
To get a normal logcat
Code:
adb logcat -v long > logcat.txt
OR
Code:
adb logcat -v time -d > logcat.txt
OR
Code:
adb logcat > logcat.txt
To get a radio logcat
Code:
adb logcat -b radio -v time -d > logcat_radio.txt
To get a kernel log
Code:
adb shell su -c dmesg > dmesg.txt
To get a last_kmsg
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.txt
Reserved
ADB over network
Thank you for this great tutorial.
I've got ADB saying device is offline with ADB over network even with the latest version of ADB. See my post
In fact, if you try to connect over network for the first time, you won't get the popup.
So, make sure you connect with USB and check "Always allow from this computer" before connecting over network.
And if you are using Ubuntu you can get the latest adb via:
Code:
sudo apt-get install android-tools-adb
I am trying to unlock the bootloader on my US Moto G 16 G. I have followed the instructions provided in Unlock Youe Device and Android Pit. I have followed the instructions in the FAQ as well.
After I input "$ fastboot oem get_unlock_code" i get the following reply " '$' is not recognized as an internal or external command, operable program, or batch file."
I have searched for the reply in Google, but I cannot come across another user who has documented this issue and how to resolve it. Any help would be greatly appreciated.
You are not supposed to write the $ symbol, start with "fastboot..."
Sent from my XT1032 using xda app-developers app
kafepuya said:
I am trying to unlock the bootloader on my US Moto G 16 G. I have followed the instructions provided in Unlock Youe Device and Android Pit. I have followed the instructions in the FAQ as well.
After I input "$ fastboot oem get_unlock_code" i get the following reply " '$' is not recognized as an internal or external command, operable program, or batch file."
I have searched for the reply in Google, but I cannot come across another user who has documented this issue and how to resolve it. Any help would be greatly appreciated.
Click to expand...
Click to collapse
The $`s are not to be typed bro and the correct cmd command afaik is : fastboot oem get_unlock_data
Thanks for pointing out the mistake on the command. I tried the correct way of doing it, and I still get essentially the same reply. Here is a screenshot to illustrate my situation.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I got the same, when you paste the code into the box click and delete all spaces and make sure there are no spaces at the beggining of the code also.
kieranc88 said:
I got the same, when you paste the code into the box click and delete all spaces and make sure there are no spaces at the beggining of the code also.
Click to expand...
Click to collapse
No dice bro. No matter what I type, I get back "[whatever the first word in the command I type] is not recognized as an internal or external command, operable program or batch file.
I don't even know what to try next.
Oh I get you now, have you got fastboot and adb installed? If so point it to the folder that contains fastboot and adb iI usually place it on c drive in a folder called android so in command prompt to point it adb I would type cd c:/android then execute your commands
kieranc88 said:
Oh I get you now, have you got fastboot and adb installed? If so point it to the folder that contains fastboot and adb iI usually place it on c drive in a folder called android so in command prompt to point it adb I would type cd c:/android then execute your commands
Click to expand...
Click to collapse
Well, I don't know if I have adb installed. I only downloaded and installed the 2 files mentioned in the Motorola page. Android SDK and the latest Motorola drivers. I can navigate to any folder in terminal (all I do is Shift+Right click on a folder and select open command window here...)
If you haven't got adb and fastboot installed look here http://forum.xda-developers.com/showthread.php?p=42407269
kieranc88 said:
If you haven't got adb and fastboot installed look here http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
Well, that sure is quite more than was in the Motorola website. Ill read up on that and figure out how to do it. Thanks a lot. I'll keep you posted.
You don't actually need the android SDK ,install adb and fastboot from the previous link I posted above
Install drivers point cmd to folder containing adb and fast boot type in cmd "adb devices" if your phone is recognised it will show a serial number,if so continue with the unlock process,
If its not recognised the drivers aren't installed properly if so download pdanet for windows and set it up ( its a tethering app but it installs drivers) get it here http://pdanet.co/bin/PdaNetA4126.exe
Check again if device is recognised and if so continue with rest of process
---------- Post added at 12:59 AM ---------- Previous post was at 12:51 AM ----------
For an easier way to install adb check this out http://forum.xda-developers.com/showthread.php?t=2588979
kieranc88 said:
You don't actually need the android SDK ,install adb and fastboot from the previous link I posted above
Install drivers point cmd to folder containing adb and fast boot type in cmd "adb devices" if your phone is recognised it will show a serial number,if so continue with the unlock process,
If its not recognised the drivers aren't installed properly if so download pdanet for windows and set it up ( its a tethering app but it installs drivers) get it here http://pdanet.co/bin/PdaNetA4126.exe
Check again if device is recognised and if so continue with rest of process
---------- Post added at 12:59 AM ---------- Previous post was at 12:51 AM ----------
For an easier way to install adb check this out http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I did it! Thanks for all the great help, specially kieranc88. Xposed here I come!!!
I am using 'fastboot oem unlock' but
Erorr shows me
'fastboot (remote : unknown command)
How to solve this problem
???
Please help me
Download the latest version of fastboot & ADB.
You can see what version adb and fastboot you have installed, just open a command window and type: sudo adb --version (then hit enter) sudo fastboot --version (hit enter key) that will show your installed version of those tools. I believe right now the latest is 31.02 but I could be wrong. It is updated often and using an older release of adb and fastboot can and will cause issues..
Go here to download adb and fastboot. https://developer.android.com/studio/releases/platform-tools
Just download the android sdk for whatever OS you use on your computer, unzip...
What is the device you are trying to unlock? Have you enabled developer options on the phone and changed usb settings to file transfer instead of the default which is charging? Also have if that was done did you keep a close eye on your device because there will be a small box that pops up that must be immediately checkmarked so that your computer can communicate with your device. Have you selected "allow oem unlock"Also in the developer options? it might be good idea to set your lock screen to "none" instead of having a lock set for it. Any time anything is installed on a computer it almost always needs to be rebooted. If you have not done any of that I would suggest doing it all.
Also depending on what device you are attempting to unlock the bootloader on, the wording could be slightly different. My Pixel 4XL uses: fastboot flashing unlock , to unlock bootloader. So keep that in mind as well. If you use Windows OS on your computer some day when you have a minute check out Linux. You can make a "live USB" burn a copy of a Linux distro to a USB drive and boot from it and or install it along with your Windows OS, aka dual boot... The very first time I used Linux, it was Ubuntu and quite a few years ago and I would never return to Windows!! Can't stand it! Linux is made for doing what we do to our phones.
If you need more any help with this some other time and still cannot get it installed message me on here or should I say "start a conversation" with me here on xda. Same thing with the new layout.. My user name is the same here on XDA as it is on telegram. Feel free to shoot me a message any time. It may take a some time to respond depending on what day it is and what time and all that but I will respond.
Here is one of the best guides in my opinion on how to get and setup adb and fastboot tools on MAC, Linux and Windows OS. https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
(Edited)
flash713 said:
it is not working, same error after update.............
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MBF_9802 said:
View attachment 5323891
Click to expand...
Click to collapse
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast...
Okay idk how you installed adb & fastboot but this guide in my opinion is the best!!! https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Try using different ports, reboot your computer..
Did you already have the pop up on your device once connected to computer or no? If not your it won't work at all.
Enable developer options
USB debugging
Now plug in to a different USB port.
Now scroll down on phone to default USB configuration and change it from the default which is "charging" to "file transfer" but keep your eyes on your device screen because the pops up will only show itself for a few seconds. When it does checkmark the box. You should be good then. Windows has driver issues alot of the time!! I switched to Linux years ago and I have no driver issues. Or anything else far as that goes.
flash713 said:
Try typing: sudo fastboot --version & sudo adb --version and make 100/% that they are most current and up to date. I'll go grab a link really fast. Brb
Click to expand...
Click to collapse
MBF_9802 said:
View attachment 5323897
Click to expand...
Click to collapse
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
All try but reason only command not found
Please help......
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
How to solve
MBF_9802 said:
Same error in updated version
How to solve
Click to expand...
Click to collapse
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
flash713 said:
Looks like that's not latest. Go here and download latest and install on your computer. See if that helps. Directions in the op of link I pasted in my last post for all OS, Mac, Windows, and Linux.
Type sudo adb devices
What does that do when you are plugged in to pc with phone?
Click to expand...
Click to collapse
Same error in updated version
flash713 said:
Did you ever onstll universal usb drivers for adb? If not install them and afterwards reboot your computer and then try.
Click to expand...
Click to collapse
yes but same problem in universal usb drivers