## Environment : Otoro phone, build 2012-11-09 Build info: * gaia master: revision= a9e28710cb2f1f68576986c5e348d990a2514ee0 * gecko aurora revision= 6735d6d13751 ## Repro : 1. In Settings -> Device Information -> More Information 2. Mark the gaia revision and then press Reset Phone button 3. After reboot, check the gaia revision again ## Expected: * Get the same revision ## Actual: * Got a different revision
In this scenario I would expect that after reset the phone is back at the revision that shipped with the device. If the user has the ability to run updates to get back to the current revision after resetting I don't think this blocks. If they're left in a limbo state with different versions of Gonk, Gecko, and Gaia then we have a more serious issue.
(In reply to Lawrence Mandel [:lmandel] from comment #1) > In this scenario I would expect that after reset the phone is back at the > revision that shipped with the device. Nope, Reset phone will only remove user data, configuration, and user-installed apps. Therefore, the version of gecko and pre-installed apps will not be affected.
Assignee: nobody → fabrice
blocking-basecamp: ? → +
Blocking to figure out if this is just the UI that's wrong, or if we're actually ending up with the wrong, or corrupted, gaia.
I tested that on two devices, one with a stable build and one with a custom build (~ nightly). In both cases this worked as expected, I got the same gaia revision. In the custom build that has the FTU app, I went through the FTU again also, which looks totally ok.
I found the device will reset to the more recent production build instead of custom build. For example: You first flash with a production build (named V1) and then flash with a custom build (named V2). Now if you reset the phone, it will return to V1 instead of V2.  flash gaia with make production  flash gaia with make reset-gaia
according to the find above, this isn't a bug closing
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
It's because reset phone will clean the data under /data/local and loading the data under /system/b2g the custom build will install gaia under /data/local by default, while production build will install gaia under /system/b2g
You need to log in before you can comment on or make changes to this bug.