I've been having issues with the make_ota_from_target script. I built AOSP
4.1.1_r4 for toro using "make otapackage -j4", which completed successfully
and created img files and a .zip file as expected. However, weird things
happen when I flash the zip. It flashes ok, but then WiFi will never
connect and all superuser apps fail to get root.
This made me think I was missing a vendor lib or something, but I flashed
the boot.img and system.img (and wiped data) just for the heck of it, and
everything works great. I've compared the files and directory structure in
both (by extracting the img), and everything looks the same to me. I'm
honestly at a loss on this.
Does this ring any bells for anyone? Is there any additional information I
can provide? I also took a look at the boot.img, and they look the same to
me as well. Thanks in advance!

--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-building@googlegroups.com
To unsubscribe from this group, send email to
android-building+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

Search Discussions

  • WeldFire at Aug 27, 2012 at 9:28 pm
    Did you flash this in a custom recovery?
    On Monday, August 27, 2012 12:22:56 PM UTC-5, fairct wrote:

    I've been having issues with the make_ota_from_target script. I built AOSP
    4.1.1_r4 for toro using "make otapackage -j4", which completed successfully
    and created img files and a .zip file as expected. However, weird things
    happen when I flash the zip. It flashes ok, but then WiFi will never
    connect and all superuser apps fail to get root.
    This made me think I was missing a vendor lib or something, but I flashed
    the boot.img and system.img (and wiped data) just for the heck of it, and
    everything works great. I've compared the files and directory structure in
    both (by extracting the img), and everything looks the same to me. I'm
    honestly at a loss on this.
    Does this ring any bells for anyone? Is there any additional information I
    can provide? I also took a look at the boot.img, and they look the same to
    me as well. Thanks in advance!
    --
    You received this message because you are subscribed to the "Android Building" mailing list.
    To post to this group, send email to android-building@googlegroups.com
    To unsubscribe from this group, send email to
    android-building+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/android-building?hl=en
  • Fairct at Aug 28, 2012 at 4:37 pm
    Yes, TWRP 2.2.0.

    --
    You received this message because you are subscribed to the "Android Building" mailing list.
    To post to this group, send email to android-building@googlegroups.com
    To unsubscribe from this group, send email to
    android-building+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/android-building?hl=en
  • Fairct at Aug 28, 2012 at 4:37 pm
    I apologize if this is a duplicate post; I can't see the one I tried from
    my phone. Yes, I used a custom recovery. TWRP 2.2.0. I also stripped the
    addition of recovery to the OTA from the make_ota script.
    On Monday, August 27, 2012 4:58:19 PM UTC-4, WeldFire wrote:

    Did you flash this in a custom recovery?
    On Monday, August 27, 2012 12:22:56 PM UTC-5, fairct wrote:

    I've been having issues with the make_ota_from_target script. I built
    AOSP 4.1.1_r4 for toro using "make otapackage -j4", which completed
    successfully and created img files and a .zip file as expected. However,
    weird things happen when I flash the zip. It flashes ok, but then WiFi will
    never connect and all superuser apps fail to get root.
    This made me think I was missing a vendor lib or something, but I flashed
    the boot.img and system.img (and wiped data) just for the heck of it, and
    everything works great. I've compared the files and directory structure in
    both (by extracting the img), and everything looks the same to me. I'm
    honestly at a loss on this.
    Does this ring any bells for anyone? Is there any additional information
    I can provide? I also took a look at the boot.img, and they look the same
    to me as well. Thanks in advance!
    --
    You received this message because you are subscribed to the "Android Building" mailing list.
    To post to this group, send email to android-building@googlegroups.com
    To unsubscribe from this group, send email to
    android-building+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/android-building?hl=en
  • Fairct at Aug 28, 2012 at 5:41 pm
    I tried reverting the make_ota script and running it again, with the
    inclusion of recovery. It led to the same results (no WiFi).

    I'm building on Mac OSX 10.7, if that info helps. At this point, my only
    edits to the source are the inclusion of the toro vendor libs, mods to the
    build.prop for Verizon, and the deletion of duplicate ringtones and
    notifications.
    On Monday, August 27, 2012 11:58:28 PM UTC-4, fairct wrote:

    I apologize if this is a duplicate post; I can't see the one I tried from
    my phone. Yes, I used a custom recovery. TWRP 2.2.0. I also stripped the
    addition of recovery to the OTA from the make_ota script.
    On Monday, August 27, 2012 4:58:19 PM UTC-4, WeldFire wrote:

    Did you flash this in a custom recovery?
    On Monday, August 27, 2012 12:22:56 PM UTC-5, fairct wrote:

    I've been having issues with the make_ota_from_target script. I built
    AOSP 4.1.1_r4 for toro using "make otapackage -j4", which completed
    successfully and created img files and a .zip file as expected. However,
    weird things happen when I flash the zip. It flashes ok, but then WiFi will
    never connect and all superuser apps fail to get root.
    This made me think I was missing a vendor lib or something, but I
    flashed the boot.img and system.img (and wiped data) just for the heck of
    it, and everything works great. I've compared the files and directory
    structure in both (by extracting the img), and everything looks the same to
    me. I'm honestly at a loss on this.
    Does this ring any bells for anyone? Is there any additional information
    I can provide? I also took a look at the boot.img, and they look the same
    to me as well. Thanks in advance!
    --
    You received this message because you are subscribed to the "Android Building" mailing list.
    To post to this group, send email to android-building@googlegroups.com
    To unsubscribe from this group, send email to
    android-building+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/android-building?hl=en
  • WeldFire at Aug 28, 2012 at 9:13 pm
    TWRP is a newer Recovery that doesn't abide by all of the standards. I
    would suggest that you try flashing the zip in a Clockwork Mod recovery, or
    another standardized recovery image.
    On Monday, August 27, 2012 10:58:28 PM UTC-5, fairct wrote:

    I apologize if this is a duplicate post; I can't see the one I tried from
    my phone. Yes, I used a custom recovery. TWRP 2.2.0. I also stripped the
    addition of recovery to the OTA from the make_ota script.
    On Monday, August 27, 2012 4:58:19 PM UTC-4, WeldFire wrote:

    Did you flash this in a custom recovery?
    On Monday, August 27, 2012 12:22:56 PM UTC-5, fairct wrote:

    I've been having issues with the make_ota_from_target script. I built
    AOSP 4.1.1_r4 for toro using "make otapackage -j4", which completed
    successfully and created img files and a .zip file as expected. However,
    weird things happen when I flash the zip. It flashes ok, but then WiFi will
    never connect and all superuser apps fail to get root.
    This made me think I was missing a vendor lib or something, but I
    flashed the boot.img and system.img (and wiped data) just for the heck of
    it, and everything works great. I've compared the files and directory
    structure in both (by extracting the img), and everything looks the same to
    me. I'm honestly at a loss on this.
    Does this ring any bells for anyone? Is there any additional information
    I can provide? I also took a look at the boot.img, and they look the same
    to me as well. Thanks in advance!
    --
    You received this message because you are subscribed to the "Android Building" mailing list.
    To post to this group, send email to android-building@googlegroups.com
    To unsubscribe from this group, send email to
    android-building+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/android-building?hl=en
  • Weston Weems at Sep 13, 2012 at 2:34 pm
    hmm...

    Does the wifi work if you just use fastboot to flash boot/system/userdata?
    AFAIK, if wifi isnt coming up after you restore your otapackage, its a
    problem with your build. That would likely be related to kernel drivers and
    vendor files.

    I havent rebuilt roms for my toro device, but I know at least for the
    panda, you need to run scripts out of vendor/ti/panda on build which copies
    files into their appropriate places on the filesystem.

    Hope I understood your question ok...

    Weston Weems
    On Monday, August 27, 2012 10:22:56 AM UTC-7, fairct wrote:

    I've been having issues with the make_ota_from_target script. I built AOSP
    4.1.1_r4 for toro using "make otapackage -j4", which completed successfully
    and created img files and a .zip file as expected. However, weird things
    happen when I flash the zip. It flashes ok, but then WiFi will never
    connect and all superuser apps fail to get root.
    This made me think I was missing a vendor lib or something, but I flashed
    the boot.img and system.img (and wiped data) just for the heck of it, and
    everything works great. I've compared the files and directory structure in
    both (by extracting the img), and everything looks the same to me. I'm
    honestly at a loss on this.
    Does this ring any bells for anyone? Is there any additional information I
    can provide? I also took a look at the boot.img, and they look the same to
    me as well. Thanks in advance!
    --
    You received this message because you are subscribed to the "Android Building" mailing list.
    To post to this group, send email to android-building@googlegroups.com
    To unsubscribe from this group, send email to
    android-building+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/android-building?hl=en
  • Fairct at Oct 10, 2012 at 2:29 pm
    As it turns out, this appears to be related to a prior question. When I
    moved over to a Linux build host, rather than a Mac OS (darwin), the ota
    zip works as expected. Someone prior to this question (maybe in July?)
    asked about the ota zip process not working for him/her on darwin... so it
    appears to be an issue there.

    Thanks for the replies, though.
    On Thursday, September 13, 2012 10:28:42 AM UTC-4, Weston Weems wrote:

    hmm...

    Does the wifi work if you just use fastboot to flash boot/system/userdata?
    AFAIK, if wifi isnt coming up after you restore your otapackage, its a
    problem with your build. That would likely be related to kernel drivers and
    vendor files.

    I havent rebuilt roms for my toro device, but I know at least for the
    panda, you need to run scripts out of vendor/ti/panda on build which copies
    files into their appropriate places on the filesystem.

    Hope I understood your question ok...

    Weston Weems
    On Monday, August 27, 2012 10:22:56 AM UTC-7, fairct wrote:

    I've been having issues with the make_ota_from_target script. I built
    AOSP 4.1.1_r4 for toro using "make otapackage -j4", which completed
    successfully and created img files and a .zip file as expected. However,
    weird things happen when I flash the zip. It flashes ok, but then WiFi will
    never connect and all superuser apps fail to get root.
    This made me think I was missing a vendor lib or something, but I flashed
    the boot.img and system.img (and wiped data) just for the heck of it, and
    everything works great. I've compared the files and directory structure in
    both (by extracting the img), and everything looks the same to me. I'm
    honestly at a loss on this.
    Does this ring any bells for anyone? Is there any additional information
    I can provide? I also took a look at the boot.img, and they look the same
    to me as well. Thanks in advance!
    --
    You received this message because you are subscribed to the "Android Building" mailing list.
    To post to this group, send email to android-building@googlegroups.com
    To unsubscribe from this group, send email to
    android-building+unsubscribe@googlegroups.com
    For more options, visit this group at
    http://groups.google.com/group/android-building?hl=en

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupandroid-building @
categoriesandroid
postedAug 27, '12 at 5:36p
activeOct 10, '12 at 2:29p
posts8
users3
websiteandroid.com

3 users in discussion

Fairct: 5 posts WeldFire: 2 posts Weston Weems: 1 post

People

Translate

site design / logo © 2017 Grokbase