Great, thanks!

Chris Mills
   Senior tech writer || Mozilla
developer.mozilla.org || MDN
   [email protected] || @chrisdavidmills



On 11 Aug 2014, at 16:51, Jason Weathersby <[email protected]> wrote:

> Chris 
> 
> I tried the windows install on July 31 and it all worked.  I do not think the 
> files have updated since then.
> 
> --
> Jason Weathersby
> 
> 
> ----- Original Message -----
> From: "Chris Mills" <[email protected]>
> To: "J. Ryan Stinnett" <[email protected]>
> Cc: "Julien Wajsberg" <[email protected]>, [email protected], 
> "Jason Weathersby" <[email protected]>
> Sent: Thursday, August 7, 2014 1:02:02 PM
> Subject: Re: [b2g] Flame phone documentation, running adb as root
> 
> Ok, instructions now updated and polished:
> 
> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame
> 
> This now works really nicely on Mac and Linux. Although I have to ask, will 
> this work on Windows?
> 
> cc’ing Jason, as I know he has tested most of this stuff on Windows. Jason - 
> have you tested the most recent Flame nightly update instructions on Windows?
> 
> Chris Mills
>   Senior tech writer || Mozilla
> developer.mozilla.org || MDN
>   [email protected] || @chrisdavidmills
> 
> 
> 
> On 7 Aug 2014, at 20:43, Chris Mills <[email protected]> wrote:
> 
>> Heh - now I feel silly. You are right Ryan, it was a permissions issue. 
>> chmod 777 on the shallow_flash.sh file made it work without needing 
>> sudo…phew!
>> 
>> Ok, back to the article to do some more updates.
>> 
>> Chris Mills
>>  Senior tech writer || Mozilla
>> developer.mozilla.org || MDN
>>  [email protected] || @chrisdavidmills
>> 
>> 
>> 
>> On 7 Aug 2014, at 19:22, J. Ryan Stinnett <[email protected]> wrote:
>> 
>>> I don't recall ever having to use "sudo" when flashing a device from
>>> OS X, so I am a bit unsure why a few people have found that they need
>>> it suddenly.
>>> 
>>> Chris, perhaps the permissions on those scripts aren't set correctly?
>>> If you do "ls -l shallow_flash.sh", what do you get back?
>>> 
>>> - Ryan
>>> 
>>> On Thu, Aug 7, 2014 at 3:16 AM, Julien Wajsberg <[email protected]> 
>>> wrote:
>>>> 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
>>>>>  [email protected] || @chrisdavidmills
>>>>> 
>>>>> 
>>>>> [1]
>>>>> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame
>>>>> 
>>>>> On 6 Aug 2014, at 20:34, Dave Hylands <[email protected]> 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" <[email protected]>
>>>>>> To: [email protected]
>>>>>> 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
>>>>>> [email protected]
>>>>>> https://lists.mozilla.org/listinfo/dev-b2g
>>>>>> 
>>>>>> _______________________________________________
>>>>>> dev-b2g mailing list
>>>>>> [email protected]
>>>>>> https://lists.mozilla.org/listinfo/dev-b2g
>>>>> 
>>>>> _______________________________________________
>>>>> dev-b2g mailing list
>>>>> [email protected]
>>>>> https://lists.mozilla.org/listinfo/dev-b2g
>>>> 
>>>> 
>>>> _______________________________________________
>>>> dev-b2g mailing list
>>>> [email protected]
>>>> https://lists.mozilla.org/listinfo/dev-b2g
>>> _______________________________________________
>>> dev-b2g mailing list
>>> [email protected]
>>> https://lists.mozilla.org/listinfo/dev-b2g
>> 
>> _______________________________________________
>> dev-b2g mailing list
>> [email protected]
>> https://lists.mozilla.org/listinfo/dev-b2g
> 

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to