Open alphaonex86 opened 9 years ago
No plans for that. Personally like to keep Android on my NAND.
But I have burn my android on nand, how? Just booting on ubuntu SD card... I presume is modify the uboot, exactly the env variable into uboot... then now I can boot only on SD card :(
Simply remove the SD card if you want to boot Android that is on NAND.
Again no! Blocked into uboot, I access to uboot via TTL cable.
Sorry, do not understand what you mean.
What device does it concern? If it's Allwinner based you can install Android to NAND by connecting the device with USB cable to your computer, and using livesuit tools.
Berryboot does not support the NAND. If you want to boot the OS installed on NAND, just remove SD card.
I use cubieboard2, after have booted the ubuntu SD card, and removed the card I have: U-Boot 2011.09-rc1-00003-ge89ab14-dirty (Jan 03 2014 - 12:57:33) Allwinner Technology
[ 0.141]version: 1.1.0 [ 0.144]pmbus: ready [ 0.248]PMU: AXP209 [ 0.251]PMU: AXP20x found [ 0.254]PMU: bat ratio = 100 [ 0.257]after set, dcdc2 =1400mv [ 0.261]PMU: dcdc2 1400 [ 0.263]PMU: pll1 912 Mhz boot_clock = 912 dcdc2_vol = 1400 [ 0.271]after set, dcdc2 =1400mv dcdc3_vol = 1250 ldo2_vol = 3000 ldo3_vol = 2800 ldo4_vol = 2800 power_start = 0 storage_type = -1 usb_recovery = 1 find power_sply to end fel key old mode run key detect no key found no key input dram_para_set start dram_para_set end [ 0.307]DRAM: 1 GiB relocation Offset is: 35b23000 donn't initialize ther user_gpio (main_key:boot_init_gpio) DRV_DISP_Init: opened [ 0.521]boot_disp.output_type=4 [ 0.525]boot_disp.output_mode=4 [ 0.528]boot_disp.auto_hpd=1 workmode = 0 [ 1.832]NAND: NAND_UbootInit NB1 : enter NAND_LogicInit nand : get id_number_ctl from script, 3 not burn nand partition table! NB1 : nand_info_init fail [ 3.854]nand init fail set to recovery try sprite_led_gpio config sprite_led_gpio start sunxi sprite begin screen_width = 800 screen_height = 480 bar x1: 200 y1: 200 bar x2: 600 y2: 280 read mbr failed sprite update error: no data part found read mbr failed sprite update error: read image start error sprite update error: current card sprite failed now hold the machine fail to find part named env Using default environment
In: serial Out: serial Err: serial --------fastboot partitions-------- mbr not exist base bootcmd=run setargs_nand boot_normal bootcmd set setargs_nand key 0 recovery key high 6, low 4 cant find fstbt value no misc partition is found to be run cmd=run setargs_nand boot_normal the part isn't exist WORK_MODE_BOOT WORK_MODE_BOOT [ 3.947]Hit any key to stop autoboot: 0 cant find part named boot sunxi_flash - sunxi_flash sub-system
Usage: sunxi_flash read command parmeters : parmeters 0 : addr to load(hex only) parmeters 1 : the name of the part to be load [parmeters 2] : the number of bytes to be load(hex only) if [parmeters 2] not exist, the number of bytes to be load is the size of the part indecated on partemeter 1 boota: bad boot image magic, maybe not a boot.img?
Then allow boot berryboot from SD card but install OS on NAND will be usefull.
If your NAND is corrupted, and you are unable to boot, you can reinstall Android by connection an USB cable to the mini USB OTG port on your Cubie, and using livesuit: http://docs.cubieboard.org/tutorials/cb2/installation/cb2_android_4.2.2_nand_install This is not related to Berryboot.
Berryboot does not support the NAND, as most users want to keep Android there, and we currently do not support booting Android.
I know, but for my, and user here, boot on berryboot on SD card and install OS like ubuntu on NAND is very useful.
+1 need some short instruction how to move system to NAND if it possible
Hello,
Can you support boot on nand and have the OS on the nand?
Cheers,