Database Develop

Help setting up adb on Ubuntu

So after getting a virus or something on my Windows drive and it not wanting to activate even after having my notebook for 3 years I am migrating over to Ubuntu. I have the android sdk setup and also edited my .bashrc file. Whenever I type adb devices it says
Code:
[email protected]:~$ adb devices
???????????? no permissions
[email protected]:~$ adb shell
error: insufficient permissions for device
What do I do to get it to work?

HELP!!!!!!!!!!!

Try sudo adb devices. You're not running adb as root
Sent from my HERO200 using XDA App

Indeed. You must use sudo.

Code:
[email protected]:~$ sudo adb devices
sudo: adb: command not found
This is what I get.

ah, sorry, try sudo ./adb devices

Try
Code:
cd ~/[COLOR="Sienna"]android_sdk_path[/COLOR]/tools/
su
./adb kill-server
./adb start-server
./adb remount
exit
or you can create a text file with:
Code:
#!/bin/bash
./adb kill-server
./adb start-server
./adb remount
and save it as remount.sh, or whatever you want, and place it in your tools folder then from the terminal cd to your tools folder and
Code:
sudo ./remount.sh
and it should work for you after that. That is what I do whenever I connect my hero

Russss said:
Try
Code:
cd ~/[COLOR="Sienna"]android_sdk_path[/COLOR]/tools/
su
./adb kill-server
./adb start-server
./adb remount
exit
or you can create a text file with:
Code:
#!/bin/bash
./adb kill-server
./adb start-server
./adb remount
and save it as remount.sh, or whatever you want, and place it in your tools folder then from the terminal cd to your tools folder and
Code:
sudo ./remount.sh
and it should work for you after that. That is what I do whenever I connect my hero
Click to expand...
Click to collapse
I'm still having some problems. I can type in kill server, start server, remount and it will work that way. But I can not get the script to work.

unCoRrUpTeD said:
I'm still having some problems. I can type in kill server, start server, remount and it will work that way. But I can not get the script to work.
Click to expand...
Click to collapse
I don't know why it isn't working. I attached the script i'm using (rename to remount.sh).
I just do
cd ~/android/tools/
sudo ./remount.sh
and it works, I don't know why it wouldn't unless the file properties are wrong(ownership,executable) I just started using linux about a month ago (linux mint)

I just installed Ubuntu last week, But I was having problems with my hard drive so I switched it out and loaded Windows and Ubuntu 10.04. I now I have to reload everything I had and I think it might have to do with permssions for the file, but I'm not sure. I am going to try that and also try the script again. Thanks for helping me get it to work at least one way.

i think i may be able to help you with this one
first you need to add the location of the sdk folder to your .bashrc file
open a terminal an enter
Code:
gedit /home/yourusername/.bashrc
replace yourusername with the one you use for ubuntu when the file opens up scroll all the way to the bottom and add this line to the bottom
Code:
export PATH=$PATH:/home/xx/Desktop/android-sdk-linux_86/tools
replace /home/xx/Destop/ with your username and where you have the sdk folder stored so for example, if you have it in your home folder and your user name in ubuntu is jo the string wold be
Code:
export PATH=$PATH:/home/jo/android-sdk-linux_86/tools
save the file, next to get adb to recognize your phone you need to create a udev rules file so open a terminal and enter
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
this will open up a blank text file copy and paste this in it
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
save the file and reboot now when you are back to the desktop you should be able to access your phone through adb.

If you still need help PM me and ill help u out on gtalk or aim

codejunkie78 said:
i think i may be able to help you with this one
first you need to add the location of the sdk folder to your .bashrc file
open a terminal an enter
Code:
gedit /home/yourusername/.bashrc
when the file opens up scroll all the way to the bottom and add this line to the bottom
Code:
export PATH=${PATH}:/home/xx/Desktop/android-sdk-linux_86/tools
replace /home/xx/Destop/ with your username and where you have the sdk folder stored so for example, if you have it in your home folder and your user name in ubuntu is jo the string wold be
Code:
export PATH=${PATH}:/home/jo/android-sdk-linux_86/tools
save the file, next to get adb to recognize your phone you need to create a udev rules file so open a terminal and enter
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
this will open up a blank text file copy and paste this in it
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
save the file and reboot now when you are back to the desktop you should be able to access your phone through adb.
Click to expand...
Click to collapse
Thanks. I had everything else setup. All I was missing was the udev rules. It works now. Just looked in the Wiki and the answer was there all along. i must have missed it before.

unCoRrUpTeD said:
Thanks. I had everything else setup. All I was missing was the udev rules. It works now. Just looked in the Wiki and the answer was there all along. i must have missed it before.
Click to expand...
Click to collapse
happy to help!

ok so i am having some of the same problem but i am trying to build a kernel using ubuntu 10.04 and so far eveything was going goo until i had to enter the command adb push config...........and i get comand adb does not exsist and it gives me a list of commands that work. But I need to use adb because of the android and i have tried just about eveything on this forum and i am not getting anything to work. Its wired i was able to root my phone and it had adb commands but when building a kernel it wont work can someone please help me i really wanna try and bulid my own kernel/rom to my likings instead of downloading a bunch of different ones. CAN SOMEONE PLEASE PLEASE HELP

krysalicea said:
ok so i am having some of the same problem but i am trying to build a kernel using ubuntu 10.04 and so far eveything was going goo until i had to enter the command adb push config...........and i get comand adb does not exsist and it gives me a list of commands that work. But I need to use adb because of the android and i have tried just about eveything on this forum and i am not getting anything to work. Its wired i was able to root my phone and it had adb commands but when building a kernel it wont work can someone please help me i really wanna try and bulid my own kernel/rom to my likings instead of downloading a bunch of different ones. CAN SOMEONE PLEASE PLEASE HELP
Click to expand...
Click to collapse
To edit a kernel you will need to get the boot.img either from your phone or from a nandroid.
THIS will give you everything

[Q] HTC One M7 in boot loop, advice from other threads not helped.

Hi
I've been at this for a few hours now and I'm just getting nowhere. I know this is a common issue but I assure you I have read every other thread and tried everything I have seen.
I have a HTC One M7 on the UK network Three with CWM recovery. Previously it was running Android Revolution HD, I tried to install the other Android Revolution HD Google Edition and right at the very end when I was asked to install Superuser is where I started running into problems. As it stands, my device is in a bootloop. If I'm careful I can time it right and boot into bootloader. From here, trying to enter recovery just puts me back into a bootloop.
All my HTC Drivers are installed fresh as of today. If I run erase cache, get var or anything along those lines all I get is <waiting for device>. When plugged in the device displays in Device Manager with the following details. I'm on Windows 8.1.I can't post a screenshot so it's text.
Unknown USB device (device failed enumeration)
Device status: Windows stopped because this device has reported problems (code 43)
I can't even find a RUU for my device, if it would even help at this point. Here's a transcript of my bootloader info.
*** TAMPERED ***
*** RELOCKED ***
M7_ UL PVT SHIP S-OFF RH
CID-H3G_001
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Where do I go from here? Bootloader factory reset does nothing, trying to flash a ROM doesn't work because the device isn't recognised, etc. I'm totally lost. The only suggestion I've even found is that I might have more luck in Windows 7, but I only have one system which will take 8-9 hours to back up to an external HD and unless it was a 90%+ shot I want reinstalling Windows 7 to be an absolute last ditch attempt.
Is there anything I'm missing?

Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk

Harish_Kumar said:
Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've never used Linux but I'll make a live usb stick and try to work it out.

toyfights said:
I've never used Linux but I'll make a live usb stick and try to work it out.
Click to expand...
Click to collapse
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"

Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.

toyfights said:
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
Click to expand...
Click to collapse
Cool
Sent from my HTC One using Tapatalk

Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.

USB Device not recognized in fastboot

I get the error in the title over and over again. When my device is on normally, it is recognized fine. I have tried uninstalling the drivers in device manager, but even that doesn't work. Using Squabbi's toolkit crashes when I try to download the HTC drivers.
Any ideas on how to fix it? I have a 4.1.2 device with 1.44 hboot. Can/should this be updated?
Is it true that there are no drivers for Windows 8? If so, do you recommend a linux VM ?
Thanks

Ubuntu USB boot
Or a windows 7 machine.

SaHiLzZ said:
Ubuntu USB boot
Or a windows 7 machine.
Click to expand...
Click to collapse
To do what? Just whenever I need to use adb functions?

Bilge656 said:
To do what? Just whenever I need to use adb functions?
Click to expand...
Click to collapse
yup, HBOOT 1.44 doesn't work in Windows 8 or above.

Bilge656 said:
To do what? Just whenever I need to use adb functions?
Click to expand...
Click to collapse
ADB should still work. It works in recovery or OS.
Fastboot is what you won't be working on windows 8 and 1.44 hboot

Oh ok. Is there any toolkit for Linux? Any guides?

Bilge656 said:
Oh ok. Is there any toolkit for Linux? Any guides?
Click to expand...
Click to collapse
Here use this guide:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219​Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
If you get "no permissions ?????????" when trying to use adb, type:
Code:
killall adb
Disconnect the phone for a few seconds, then reconnect and type:
Code:
sudo adb devices
adb should now work as normal without the sudo prefix.
Click to expand...
Click to collapse

majmoz said:
Here use this guide:
​
Click to expand...
Click to collapse
Ok so I did all of that, but my device still is not recognized. It is not detected at all in my Windows 8 build as well as my virtual machine of Ubuntu.

Bilge656 said:
Ok so I did all of that, but my device still is not recognized. It is not detected at all in my Windows 8 build as well as my virtual machine of Ubuntu.
Click to expand...
Click to collapse
you have to boot linux from a usb drive or from a live cd, not like a virtual machine like virtualbox or anything similar.

alray said:
you have to boot linux from a usb drive or from a live cd, not like a virtual machine like virtualbox or anything similar.
Click to expand...
Click to collapse
I did that, and at first I plugged it in and it was recognized. Then after awhile, it stopped being recognized all together after some reboots.

[Q] help rooting nexus 6 using crunchbang linux

I've got java and SDK tools properly installed. I've tried several methods. Always gives error command fastboot not found. I'm on crunchbang Linux

If you go to general > sticky roll-up thread....
You'll find my fastboot thread which tells you how to use fastboot correctly.

@NiNJAwitaRaZR,
Did you type ./ before the fastboot command?

cam30era said:
@NiNJAwitaRaZR,
try using sudo ./ before the fastboot command.
Click to expand...
Click to collapse
You don't need sudo for fastboot. But you do need to know where the fastboot binary is.
Or he can use an adb and fastboot installer script which should put it in a known PATH

rootSU said:
You don't need sudo for fastboot. But you do need to know where the fastboot binary is.
Or he can use an adb and fastboot installer script which should put it in a known PATH
Click to expand...
Click to collapse
Aahh, OK.
I still prefer to do things manually, so that I understand how it works.

cam30era said:
Aahh, OK.
I still prefer to do things manually, so that I understand how it works.
Click to expand...
Click to collapse
Me too. Personally I just drop them directly in /usr/bin

Help flashing stock rom to Pixel 4 XL with Pixelbook?

Hello folks!
Its been a while since i posted here - i havent been flashing roms for an age (kids etc got in the way!)
Anyway, i've picked up a Pixel 4 XL, and it was running a custom ROM, i'm trying to move back to stock and have been able to follow all the guides i've found up to using the 'fastboot flashall' in shell.
The command works and delivers the
Bootloader Version...:
Baseband Version.....:
Serial Number........:
values, but then errors out with the following error "fastboot: error: ANDROID_PRODUCT_OUT not set"
I'm stumped what that means and how to fix. I'm doing all of this on my Pixelbook, and have updated fastboot and adb as per the initial steps for flashing.
Can anyone shed any light on what i still need to do to get flashall to work as expected?
Thanks in advance if you are able to help out!
ptm

Welcome Back
Could you post the exact command you are using for fastboot flash please? It sounds like fastboot is not finding the files to flash. Usually, depending on the configuration of the fastboot install, it's easier to place the firmware in the same directory as the fastboot binary.

Thanks! It turns out i've missed this place!
So the firmware files are all on the chromebook and I've used 'shell' to navigate to where I've unzipped. Here's the command line with the command i'm using: "[email protected] ~/Downloads/ota_file $ fastboot flashall"
Before trying a full flash, i was trying to sideload the OTA as per instructions here https://developers.google.com/android/ota#instructions but moving the file from my pixelbook to the 4XL fails at 47% every time.
So i reverted to a full flash as per these instructions - https://developers.google.com/android/images and that is where i'm coming a cropper with the 'not set' error.
Thanks for your help!
ktmom said:
Welcome Back
Could you post the exact command you are using for fastboot flash please? It sounds like fastboot is not finding the files to flash. Usually, depending on the configuration of the fastboot install, it's easier to place the firmware in the same directory as the fastboot binary.
Click to expand...
Click to collapse

I thinnk you may be merging several approaches.
You are using the full factory image downloaded from the https://developers.google.com/android/images page, right? Then, once downloaded, you are unzipping the file and cd into the new directory (from the unzip). The command then should be
Code:
./flash-all.sh
As far as the OTA install is concerned, you are using the command
Code:
adb sideload "ota_file.zip"
, and at 47%, what happens that it appears to fail? My memory on my P3XL is at that point it takes awhile.

If you are using a C to C switch to an A to C cable and try it. You'll want to remove the wipe from the flash-all before you flash the full image and it's the flash all you should be using to flash.

Yeah i think you're right - so now just concentrating on the Full Flash method shown on the Google Developers page, and yes doing it exactly as you'd described.
Ok - using
Code:
./flash-all.sh
now returns the error
Code:
bash: ./flash-all.sh: Permission denied
I have tried to prefix './flash-all.sh' with 'Fastboot' but no dice here either. Is that required at all?
ktmom said:
I thinnk you may be merging several approaches.
You are using the full factory image downloaded from the https://developers.google.com/android/images page, right? Then, once downloaded, you are unzipping the file and cd into the new directory (from the unzip). The command then should be
Code:
./flash-all.sh
As far as the OTA install is concerned, you are using the command
Code:
adb sideload "ota_file.zip"
, and at 47%, what happens that it appears to fail? My memory on my P3XL is at that point it takes awhile.
Click to expand...
Click to collapse

ptm said:
Yeah i think you're right - so now just concentrating on the Full Flash method shown on the Google Developers page, and yes doing it exactly as you'd described.
Ok - using
Code:
./flash-all.sh
now returns the error
Code:
bash: ./flash-all.sh: Permission denied
I have tried to prefix './flash-all.sh' with 'Fastboot' but no dice here either. Is that required at all?
Click to expand...
Click to collapse
You need to give the "flash-all.sh" script execution rights (that is why the permission denied error). Use this code:
Code:
chmod +x ./flash-all.sh
You may need super user/root rights:
Code:
sudo chmod +x ./flash-all.sh
The "flash-all.sh" script is a stand-alone script that sequentially flashes the entire factory package. As was mentioned in another repsonse in this thread, in cases where you want to update, but not lose your installed user apps and data, you would edit the script and remove the "-w" augment. In this case, you are returning to stock and you should perform the wipe (-w).
The dot slash (./) that preceeds the flash-all.sh tells the bash interpreter (what runs commands you give) that the file is right here, in this directory.
The flash-all.sh is a standalone script (series of written instructions) and calls fastboot from within it.

Thanks for sticking with me on this ktmom!
OK, i've used both
Code:
chmod +x ./flash-all.sh
and
Code:
sudo chmod +x ./flash-all.sh
but still getting the permission denied error when i launch ./flash-all.sh
I'll do a screencast vid walking through the entire process i'm following, so that you can see what i'm up too and in case it gives any further clues for a solution.
Thanks again!
ktmom said:
You need to give the "flash-all.sh" script execution rights (that is why the permission denied error). Use this code:
Code:
chmod +x ./flash-all.sh
You may need super user/root rights:
Code:
sudo chmod +x ./flash-all.sh
The "flash-all.sh" script is a stand-alone script that sequentially flashes the entire factory package. As was mentioned in another repsonse in this thread, in cases where you want to update, but not lose your installed user apps and data, you would edit the script and remove the "-w" augment. In this case, you are returning to stock and you should perform the wipe (-w).
The dot slash (./) that preceeds the flash-all.sh tells the bash interpreter (what runs commands you give) that the file is right here, in this directory.
The flash-all.sh is a standalone script (series of written instructions) and calls fastboot from within it.
Click to expand...
Click to collapse

@ptm, No worries, I'll do my best to help. I'm typing this on a chromebook that I also use to fastboot to a P3XL.
Edit 1:
Just to make sure:
1) The bootloader is unlocked?
2) "fastboot devices" returns the serial number of your device?
3) you are running ./flash-all.sh command as root or as the default user? In other words, the same way that fastboot devices returns the serial number. Either sudo fastboot devices or just fastboot devices.
4) if you enter the linux command: ls -al flash-all.sh do you get something like:
-rwxr-xr-x. 1 chronos chronos 957 Jul 18 2019 flash-all.sh
In this example -rwxr-xr-x is depicting the file permissions where there are three groupings; owner group everyone else. The first rwx means read, write and execute permissions for the file owner. Others in the same group and everyone else has read and execute permissions. Execute (x) is required in order for a script to run. If your file does not have three x so that all three groups have permission to execute it, then we need to revisit that.
Edit 2:
Another thought that could be affecting you is ADB and Fastboot are old. in your crosh shell, type:
Code:
[email protected] ~ $ adb --version
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
[email protected] ~ $ fastboot --version
fastboot version 29.0.5-5949299
Installed as /usr/local/bin/fastboot
If either returns a version older than the output above, then the easy way to update these is to use the script on Nathan Chance's Githuib. This might look a little overwhelming but it's pretty easy. I suggest you read the page, but the operative information is in section 4. Run the setup script:
To install, run
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
in your shell prompt.
This script very nicely updates your ADB/Fastboot to the newest version which will be required for your P4XL

Are you guys sure you aren't making it too hard? You don't have to give any commands to install the full image. Download the full image and put it into an empty folder, go ahead and extract it in that folder. Create another new folder, Copy everything into it so you still have the full image in the first folder. Now download the tools and put those into a folder and extract them in that folder. Take the entire contents of that folder and add it to the folder you copied the extracted image into. What you should have now is one folder that still has the full extracted image, one that has the full extracted tools, and one that has both. If you have not already done so the phone should have debugging enabled and oem should be on. Go ahead and put it into bootloader mode and plug it in, type cmd in the path bar of the folder with both tools and image and check devices which will tell you if the tools can see the phone. If you get your serial the tools can see the phone. If you're going to wipe you can go ahead and click the flash-all and it will start the process, you do not give any commands. If you don't want to wipe the edit the flash-all to remove the-w, save it, and click on it. Again, no command is given, you just click and the flash-all does the rest.
Edit... And dont forget, A to C, not the provided C to C.

krabman said:
Are you guys sure you aren't making it too hard? You don't have to give any commands to install the full image. Download the full image and put it into an empty folder, go ahead and extract it in that folder. Create another new folder, Copy everything into it so you still have the full image in the first folder. Now download the tools and put those into a folder and extract them in that folder. Take the entire contents of that folder and add it to the folder you copied the extracted image into. What you should have now is one folder that still has the full extracted image, one that has the full extracted tools, and one that has both. If you have not already done so the phone should have debugging enabled and oem should be on. Go ahead and put it into bootloader mode and plug it in, type cmd in the path bar of the folder with both tools and image and check devices which will tell you if the tools can see the phone. If you get your serial the tools can see the phone. If you're going to wipe you can go ahead and click the flash-all and it will start the process, you do not give any commands. If you don't want to wipe the edit the flash-all to remove the-w, save it, and click on it. Again, no command is given, you just click and the flash-all does the rest.
Edit... And dont forget, A to C, not the provided C to C.
Click to expand...
Click to collapse
What Tools do you need to do this?

Same page as the images, scroll up from them and in the description of the process they have a link to the platform tools.

@krabman, Since this is using a chromebook, not a PC, things are flakier than normal. I just replicated the problems experienced by @ptm and some of it is due to old ADB/Fastboot as described in my previous post. Some is because ChromeOS made a change in an update that mounts nearly all of the partitions noexec, which means scripts can not execute and give the reported, "no permissions" error. There is a workaround since /usr/local is mounted executable. It's also possible to remount a partition with exec permissions.
@ptm, as the easiest route, I suggest making sure the ABD is current using the script I linked yesterday, and then going back to the OTA sideload method. I tanked my phone for a few hours yesterday trying to make fastboot get through the entire system image. I finally resorted to my full ubuntu install on my chromebook.

airmaxx23 said:
What Tools do you need to do this?
Click to expand...
Click to collapse
A general Fastboot/ADB tutorial is available here. If you are not using a chromebook, this thread's discussion will just add confusion.
If you are using a chromebook, then you need to enter a crosh shell, make sure adb and fastboot are updated as described in an earlier post and read the rest of the information I posted about the associated problems.

My understanding is the sh should flash on chrome with the latest tools as I described and you use the bat for PC. If the device is down he would have nothing to lose trying, if not I'd be leery of trying it since a partial flash will definitely result in a softie. Of course the possibility that I don't fully understand it may explain my puzzlement.

ktmom said:
A general Fastboot/ADB tutorial is available here. If you are not using a chromebook, this thread's discussion will just add confusion.
If you are using a chromebook, then you need to enter a crosh shell, make sure adb and fastboot are updated as described in an earlier post and read the rest of the information I posted about the associated problems.
Click to expand...
Click to collapse
Thanks, I know how to use ADB on the PC but I have a ChromeBook that I'd like to use as well. I already have it in Developer Mode.
I got it working, I just to run the script to update ADB and Fastboot.

airmaxx23 said:
Thanks, I know how to use ADB on the PC but I have a ChromeBook that I'd like to use as well. I already have it in Developer Mode.
When I open a Crosh Window, type shell, then adb devices my Pixel 4 XL shows up but I get: no permissions; see [http://developer.android.com/tools/device.html]
Click to expand...
Click to collapse
My bet is your ADB/fastboot are to old. Go back to post 9 and read the lower portion under edit2. You should also read forward from that point as there are additional issues that ChromeOS introduced with the noexec mounting of partitions. It will mean that without a workaround, you can not execute the flash-all.sh.

ktmom said:
My bet is your ADB/fastboot are to old. Go back to post 9 and read the lower portion under edit2. You should also read forward from that point as there are additional issues that ChromeOS introduced with the noexec mounting of partitions. It will mean that without a workaround, you can not execute the flash-all.sh.
Click to expand...
Click to collapse
Hey there,
SO i decided to try the OTA sideload method on a friends PC - i got the following response through CMD prompt
Code:
C:\Users\LYALL\Downloads>adb sideload ota-file.zip
Total xfer: 1.00x 1
However the phone is reporting a failure verifying the file signature and giving
Code:
E: Error code: 21
What do you think is causing that? I saw that Google has a new browser based flash tool to allow for AOSP builds to flash - would using that work better for me do you think?
ptm

ptm said:
Hey there,
SO i decided to try the OTA sideload method on a friends PC - i got the following response through CMD prompt
Code:
C:\Users\LYALL\Downloads>adb sideload ota-file.zip
Total xfer: 1.00x 1
However the phone is reporting a failure verifying the file signature and giving
Code:
E: Error code: 21
What do you think is causing that? I saw that Google has a new browser based flash tool to allow for AOSP builds to flash - would using that work better for me do you think?
ptm
Click to expand...
Click to collapse
Make sure you have downloaded the correct OTA and for crosshatch coral. Use the sha256 checksum provided in the download page and ensure the file is not corrupted. I check the integrity of the file before using it especially if I've moved it since the last verification.
You are rebooting to recovery (not rescue mode) and using the OTA sideload action from *within* recovery, before using the adb command, right?
The Google update and repair tool is an option.

ktmom said:
Make sure you have downloaded the correct OTA and for crosshatch. Use the sha256 checksum provided in the download page and ensure the file is not corrupted. I check the integrity of the file before using it especially if I've moved it since the last verification.
You are rebooting to recovery (not rescue mode) and using the OTA sideload action from *within* recovery, before using the adb command, right?
The Google update and repair tool is an option.
Click to expand...
Click to collapse
I think Pixel 4 XL is Coral, not Crosshatch.
I have downloaded the OTA file thats third from the bottom on this page (https://developers.google.com/android/ota) which is the rom number - 10.0.0 (QQ1B.200105.004, Jan 2020).
Yes, followed the instructions and booted to recovery, selected 'update from adb' from within recovery and then checked
Code:
adb devices
to ensure it showed 'sideload'. I then ran the command
Code:
adb sideload ota_file.zip
The transfer seemed to work fine, but then i got the error above showing on the device.
I cant seem to use the Google update and repair tool, as I'm in the UK and it says its not supported.
I can get it working with a VPN but the carrier i'm on doesnt show, although i do have the option of selecting 'other' as the carrier - I'm happy to give that a go, but wanted to get your thoughts on it first. Will selecting carrier as 'other' work ok for a UK based phone?
ptm