Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not familiar with netbooks running android so here's my experience with embedded devices. </p> <p>To my best knowledge there is no "android-internal" way. Android takes over after u-boot and rarely(read never) does it modify to u-boot environment partition. </p> <p>To cut the long story short it's nearly impossible and it's too much effort for nothing. Also for starters You'll need a debug serial console attached to the board or an ADB shell. It's just guess work without a shell. </p> <p>For a general algorithm:</p> <ol> <li>get a shell working</li> <li>Get to know the system( cpu type, partition table, ...)</li> <li>Now just research what you can do with the things you know.</li> </ol> <p>Or the 'all or nothing' - reverse engineer the firmware upgrade and the firmware images and try to boot with your own. </p> <p>Long story:</p> <p>For sd_card boot you have 2 options:</p> <ol> <li>use the bootloaders on the board and load the kernel and the rootfs from the sdcard</li> <li>boot from sd_card</li> </ol> <p>Load kernel and fs from sd_card:</p> <p>There is no general u-boot way to change the boot device without changing the u-boot environment . The u-boot environment most of the time resides in a nand partition. There may be some way coded by the manufacturer, which may be guessed by the offline firmware upgrade procedure. This is probably your best bet for a quick solution. Try to reverse engineer that. </p> <p>Boot From sd_card:</p> <p>Most platforms have SYSCONFIG registers or hardware pins, operated by jumpers on development platforms and mostly hardwired on production ones. SYSCONFIG controls the boot devices. It can be configured for NAND only or SD_CARD only, etc... </p> <p>If the system is indeed configured to load from an sd_card there are a few more problems:</p> <ul> <li>Some of the times the SD card has to be formated in a specific way(for ex: <a href="http://www.omappedia.org/wiki/SD_Configuration" rel="nofollow">http://www.omappedia.org/wiki/SD_Configuration</a> ). </li> <li>Other times the first stage loader has to be signed. And it's hard figuring out what the first stage bootloader is (x-loader, or something other) and the signing part is kind of tricky :) </li> <li>you have to know the exact platform configuration to build u-boot and x-loader </li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POhowto replace android with another distribution
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USnvloff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POhowto replace android with another distribution
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload