I really think we should try to do it without using sudo.
I don't know enough of MacOS X to know how to make it see the device,
but I'm sure there is a solution like udev on LInux.
How does it work for other devices?
Le 07/08/2014 09:29, Chris Mills a écrit :
Hi there!
I’ve now investigated the supplied instructions in the Flame article[1], tested
them thoroughly, and updated them to make them clearer and more complete.
Josh was right about needing to mention sudo: when I didn’t run flash.sh with
sudo, the flash script seemed to fail to see the device, so it didn’t work; it
just sat there saying “waiting for device”. When I did use sudo, it worked fine.
Then when I ran shallow_flash.sh without using sudo, it gave me a “permission
denied” error. When I did use use sudo, that error went away.
However, I am still stuck on that bit. The current text includes the following
instruction:
"5. To install the build on your phone download the shallow flash script and
run it like this:
sudo ./shallow_flash.sh -g/path/to/gaia.zip
-G/path/to/b2g-XX.XX.en-US.android-arm.tar.gz”
I’ve got shallow_flash.sh, gaia.zip and b2g-34.0a1.en-US.android-arm.tar.gz
downloaded into the same directory. I then go into that directory in terminal and
run the above command, and it gives me the message "sudo: ./shallow_flash.sh:
command not found”.
How do I fix this? ;-)
Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
cmi...@mozilla.com || @chrisdavidmills
[1] https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame
On 6 Aug 2014, at 20:34, Dave Hylands <dhyla...@mozilla.com> wrote:
I'm a little confused by some of your statments.
Whether you flash the base image as the root user or as a regular user will
have NO impact on how adbd runs on the phone.
Running commands using sudo on the build machine only affects access to the
devices on the build machine.
"adb root" relaunches the adbd on the phone under the root user (if the phone
is configured to allow it).
Dave Hylands
From: "Josh Aas" <josh...@gmail.com>
To: dev-b2g@lists.mozilla.org
Sent: Wednesday, August 6, 2014 9:15:36 AM
Subject: [b2g] Flame phone documentation, running adb as root
I got a Flame phone and wanted to update it to 2.0 nightly so I could
test/dogfood. Last week I couldn't figure out how to do that via the Flame home
page, but someone has since added instructions. Thanks to whoever did that!
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame
One issue with the instructions, though, at least on OS X - they only really work if both flash
steps are run as root (sudo). Flashing the base doesn't require root, but the flash to 2.0 nightly
requires the adb daemon to be running as root, and if you didn't flash the base as root adb will
not be running as root. You'll need to do "adb kill-server", which most people won't know
how to do. If you didn't run the base flash as root, and you figured out how to kill the adb
server, you then need to run the second flash as root to get adb to start as root. We should either
recommend that people run the flash commands as root (prefix "sudo"), or explain how to
get adb running as root first.
Other than this, the page's information is much better than before. Still could
be better organized, though.
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
dev-b2g@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g
