Closed
Bug 1068687
Opened 10 years ago
Closed 10 years ago
b2g-22.2 is offline/ needs to be re-flashed in MV
Categories
(Firefox OS Graveyard :: Infrastructure, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zcampbell, Assigned: tchung)
Details
I accidentally flashed b2g-22.2 which had a JB base with a KK gecko/gaia build. It's active but offline so I cannot reach it remotely with adb. It needs to be reflashed with the v123 build and put back online.
Reporter | ||
Comment 1•10 years ago
|
||
Also b2g-16.2 and b2g-17.2 and b2g-18.1
Reporter | ||
Comment 2•10 years ago
|
||
actually, if you can just put v180 on it, make sure remote debugging is enabled then put it back on the grid that would be fine.
Reporter | ||
Updated•10 years ago
|
Assignee: nobody → tchung
Assignee | ||
Comment 4•10 years ago
|
||
I couldn't locate 22-2 in the lab. reflashed base v180 on 16.2, 17.2, and 18.1, with adb access enabled. Go for it.
Flags: needinfo?(tchung)
Reporter | ||
Comment 5•10 years ago
|
||
I checked and those 3 are back up and online. nvm about 22, we'll get that next time.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•