Closed
Bug 1028019
Opened 10 years ago
Closed 10 years ago
[Flatfish] The issue of script for flashing image onto flatfish device
Categories
(Firefox OS Graveyard :: General, defect)
Firefox OS Graveyard
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: neopleo, Unassigned)
References
Details
Attachments
(1 file)
6.50 KB,
application/x-shellscript
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140428194215 Steps to reproduce: Execute flash-flatfish.sh with flatfish device attached. Actual results: --- Image files checking --- Error: 'out/target/product/flatfish' is not a directory! === Usage === Usage: flash-flatfish.sh [-h] [<path_to_images> [<path_to_b2g_root>]] Options: -h: help <path_to_images>: default to ./out/target/product/flatfish/ <path_to_b2g_root>: path to the root of the B2G source, for using 'adb' only. If 'adb' can be found in $PATH, this option can be ignored. Example: 1. Run in B2G root directory. $ flash-flatfish.sh 2. flash images in the current directory $ flash-flatfish.sh . 3. flash images in ~/flatfish-images $ flash-flatfish.sh ~/flatfish-images 3. flash images in ~/flatfish-images, and specify the source path of B2G for using 'adb' $ flash-flatfish.sh ~/flatfish-images ~/dev_fxos/a31-b2g Expected results: It should start flashing images (system image, userdata image and etc.) onto flatfish device.
Reporter | ||
Comment 1•10 years ago
|
||
Hi William, please revise the script to check the following conditions: 1. Is root needed to flash the device 2. Help check the image path. Thanks : )
Flags: needinfo?(william.wyliang)
Comment 2•10 years ago
|
||
Hi, Sam, The script is not for solving the brick problem, which is solved by the bare boot image provided in Bug 10269633. The script is used to flash images to Flatfish when it's good or has been recovered by the bare boI t image. I suggest that you change the subject of this bug a bit, to 'The issues of the script for flashing images to Flatfish.' Since I don't have the device on my hand right now, could you help provide me the log for executing the 'fastboot devices' command when the device is not well configured in the udev rule file under the /etc/udev/rules.d/ directory? I think the sudo command may need to be used in this case. Thanks.
Flags: needinfo?(william.wyliang) → needinfo?(ckjboy2003)
Comment 3•10 years ago
|
||
Sorry, fix a typo in the previous comment. I meant the bug 1026963, for the brick solution.
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(ckjboy2003)
Summary: [Flatfish] The issue of script for solving the brick problem → [Flatfish] The issue of script for flashing image onto flatfish device
Reporter | ||
Comment 4•10 years ago
|
||
Hi William, Yea, you are right. The subject of this bug has been changed. : )
Comment 5•10 years ago
|
||
The above bug fixed. 1. The bug of wrong B2G source path detection has been fixed. 2. The script now detects the case when the udev rule is not well set in /etc/udev/rule.d/. In this case, it request the user to run fastboot by the sudo method. Sam, please help verify the fix, as in the attached file.
Updated•10 years ago
|
Flags: needinfo?(ckjboy2003)
Reporter | ||
Comment 6•10 years ago
|
||
Hi Wiliiam, Thanks. The script works for me.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ckjboy2003)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•