The bug that affected the original Nexus 10 JOP40C factory images did
not affect other devices (it was related to the number of files in the
system). Furthermore, that bug doesn't cause any problems while
booting, it only prevents later OTA from applying.
JBQ
On Thu, Dec 6, 2012 at 5:43 AM, boy3dfx <
valyvoi...@gmail.com> wrote:
> Hello.
>
> I have recently acquired a Nexus 4 phone. It came with JVP15Q on it.
>
> As I intend to do some development on it I upgraded it via OTA to JOP40C,
> JOP40D, fastboot oem unlocked it, then tried using Factory image flashing
> using your jop40c (it was on
>
https://developers.google.com/android/nexus/images up until a few days ago).
> The phone stopped booting completely (I see the Google logo, then the
> bootanimation, and it gets stuck there). So I said to myself, hmmm, maybe
> downgrading caused this issue, so I used the latest factory images
>
https://developers.google.com/android/nexus/images#occamjop40d to try to fix
> the problem. The problem remained.
>
>
> I am wondering if there is something missing by accident with the Nexus 4
> factory images you have online (either as missing files in the factory image
> or if the problem comes from the fact the factory images are using fastboot
> -w as part of the factory image flashing sequence). I know that support for
> Nexus 4 in AOSP is not complete, but I really hope factory image flashing
> can work, as I rely on it to return the phone to a (working) stock state, on
> all my google devices.
>
>
> The reason I asked the above is I was able to built a custom boot image with
> adb enabled, and run it (in my opinion) successfully on the phone. I did
> this after the initial factory image flashing with jop40c, and again after
> trying factory image jop40d.
>
> I took the kernel signature via cat /proc/version (both JOP40C and JOP40D
> seem to share the kernel), and after seeing the phone gets stuck, I used
> AOSP 4.2_r1 / 4.2.1_r1 to generate boot.img. Fastboot booting this image
> gives me a shell into the phone, without affecting the phone flash.
>
> When booting with adb enabled, I did a comparision between what's mounted
> and the content of /fstab.mako. I can see as a symptoms for the phone not
> booting that a few things (including /firmware, /data) seem not to
> automount on startup. I can manually mount into /firmware, but am not sure
> why it does not happen automatically.
>
>
> Do you think it may be related to the bug you discovered on the Nexus 10?
>
>
> Thank you in advance,
> Gabi Voiculescu