Say hi to "CyanoBoot" -- a 2nd bootloader/w menu aka "ub2" - (WIP)

Search This thread

lillo95

Member
Sep 5, 2011
45
1
How do you expect to enter cwm without cyanoboot? And why would you want to remove it in the first place? It adds options to boot into emmc and sdcard Rom and recovery and alternate recovery also.

If you really really don't want it, flash stock image again root it, then use indirect's nook recovery flasher (an older version, not sure of the newer one's stability)

Sent from my ST27i

i tried this awesome bootloader
but isn't useful for me
sorry
but how i can flash stock image back??

i've used this metod
http://forum.xda-developers.com/showthread.php?t=1402190
several times
but cyano still remain y.y
 
Last edited:

DanGeorges

Senior Member
Apr 14, 2009
717
86
Cleveland
i tried this awesome bootloader
but isn't useful for me
sorry
but how i can flash stock image back??

i've used this metod
http://forum.xda-developers.com/showthread.php?t=1402190
several times
but cyano still remain y.y

Try this method: http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
This will get your nook back to the stock configuration.

Here is my recommendation on how you can preserve what you have:

1. Load Titanium Backup and back up all your apps that you'd like to keep
2. Using the unbrick method above, restore the Nook back to factory state
3. Root using this method: http://forum.xda-developers.com/showthread.php?t=1529553
4. Load Nook Tab Recovery Flasher if you'd like to get CWM recovery: http://forum.xda-developers.com/showthread.php?t=1650927
5. Check out this link for blocking OTA updates and for loading a new launcher: http://forum.xda-developers.com/showthread.php?p=24843139

I did this, and now my nook is rooted with ADW EX launcher. No problems that I can find.

And no Cyanoboot - so you're good to go!
 
  • Like
Reactions: lillo95

lillo95

Member
Sep 5, 2011
45
1
How do you expect to enter cwm without cyanoboot? And why would you want to remove it in the first place? It adds options to boot into emmc and sdcard Rom and recovery and alternate recovery also.

If you really really don't want it, flash stock image again root it, then use indirect's nook recovery flasher (an older version, not sure of the newer one's stability)

Sent from my ST27i

Try this method: http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
This will get your nook back to the stock configuration.

Here is my recommendation on how you can preserve what you have:

1. Load Titanium Backup and back up all your apps that you'd like to keep
2. Using the unbrick method above, restore the Nook back to factory state
3. Root using this method: http://forum.xda-developers.com/showthread.php?t=1529553
4. Load Nook Tab Recovery Flasher if you'd like to get CWM recovery: http://forum.xda-developers.com/showthread.php?t=1650927
5. Check out this link for blocking OTA updates and for loading a new launcher: http://forum.xda-developers.com/showthread.php?p=24843139

I did this, and now my nook is rooted with ADW EX launcher. No problems that I can find.

And no Cyanoboot - so you're good to go!

alredy followed
doesn't work
when i install a custom rom this cyanoboot still appear
it's really hard to remove
 

fattire

Inactive Recognized Developer
Oct 11, 2010
2,280
6,473
www.eff.org
As explained numerous times in this thread, you need a second boot loader such as cyanoboot to run any non-barnes and noble third party ROM. The nook tablet has a locked bootloader which prevents a non-stock, unsigned operating system from loading, and cyanoboot fixes this. The menu stuff and other features are all extras.

The claim above that cb "bricked" a device is highly suspect on numerous counts.

I recommend reading this thread where I and others explain what the second bootloader is for, and why it is a requirement on the nook tablet as well as nook HD and the new kindle fire HDs, all of which have locked bootloaders that required fixes.
 

DanGeorges

Senior Member
Apr 14, 2009
717
86
Cleveland
alredy followed
doesn't work
when i install a custom rom this cyanoboot still appear
it's really hard to remove

I thought you wanted it back to stock...

If you want to load a custom ROM, the only way to do it, as I understand, is to boot via the SD card or internally via Cyanoboot, which is typically included in Nook custom ROMs.

So my instructions work, but only to the point where you loaded a custom ROM - which itself included Cyanoboot.

If you don't want Cyanoboot, please don't load a custom ROM.

PM me for more information.
 

lillo95

Member
Sep 5, 2011
45
1
yes yes yes
it's necessary
but before installing this cyanoboot i was able to load any custom rom
so, how i can remove it and replace??
and cyano give me an error every time: Normal SD boot overriden. Alt boot from EMMC...
booti: bad boot image magic (in memory)
how can i resolve that??
if i can't remove this **** bootloader at least i want to make work properly
 

digixmax

Senior Member
Jan 17, 2011
2,083
665
yes yes yes
it's necessary
but before installing this cyanoboot i was able to load any custom rom
so, how i can remove it and replace??
and cyano give me an error every time: Normal SD boot overriden. Alt boot from EMMC...
booti: bad boot image magic (in memory)
how can i resolve that??
if i can't remove this **** bootloader at least i want to make work properly
It's hard for folks to help when it's not clear what it is that you're looking to achieve -- keep the NT emmc on stock or rooted stock, and run a custom ROM on SD?
 

DanGeorges

Senior Member
Apr 14, 2009
717
86
Cleveland
It's hard for folks to help when it's not clear what it is that you're looking to achieve -- keep the NT emmc on stock or rooted stock, and run a custom ROM on SD?

If I understand correctly, this person wants the ability to load custom ROMs without replacing the Nook bootloader with Cyanoboot. The result would be to use the SD card as storage and NOT run a ROM from the card.
 
Last edited:

RhinoNelson

Senior Member
Apr 26, 2012
102
24
Puyallup, WA
making Cyanoboot work

yes yes yes
it's necessary
but before installing this cyanoboot i was able to load any custom rom
so, how i can remove it and replace??
and cyano give me an error every time: Normal SD boot overriden. Alt boot from EMMC...
booti: bad boot image magic (in memory)
how can i resolve that??
if i can't remove this **** bootloader at least i want to make work properly

Quick 'fix' is to hold the 'n' key when the Boot Menu screen comes up during the boot process. This gives the ability, using the sound UP and DOWN keys to scroll through the options and select which you prefer. Select Internal Boot (EMMC?) and hit 'n' again and your ROM will boot.

The longer term fix is to go to your /bootdata folder (assuming you are rooted to this level) and in the U-boot.altboot file, use a text editor and change the 1 to 0 and you are good to go. The 'problem' you are experiencing is because Cyanoboot sees the Alt-Boot file before the Boot file, acts on what is there, and tries to boot from the AltBoot image which probably doesn't exist.

Once you sort the Alt-Boot issue booting becomes seamless and you will hardly know Cyanoboot exists -- until you want to take advantage of its many uses.
 
Last edited:

lillo95

Member
Sep 5, 2011
45
1
Quick 'fix' is to hold the 'n' key when the Boot Menu screen comes up during the boot process. This gives the ability, using the sound UP and DOWN keys to scroll through the options and select which you prefer. Select Internal Boot (EMMC?) and hit 'n' again and your ROM will boot.

The longer term fix is to go to your /bootdata folder (assuming you are rooted to this level) and in the U-boot.altboot file, use a text editor and change the 1 to 0 and you are good to go. The 'problem' you are experiencing is because Cyanoboot sees the Alt-Boot file before the Boot file, acts on what is there, and tries to boot from the AltBoot image which probably doesn't exist.

Once you sort the Alt-Boot issue booting becomes seamless and you will hardly know Cyanoboot exists -- until you want to take advantage of its many uses.

wow, the long term solution work good for me =D
i've tried several times the "quick fix" but it's boring and annoying to do every times
well thank's dude =D u re the best
 

sailerph

Senior Member
Feb 5, 2012
83
3
Running CM 10.1 RC4 Clockwork mod 6.029 internal

Cyanoboot starts up, Hold N for menu, but then "Boot Menu" shows with no options below (no greyed out options either-nothing at all). Frozen here.I then have to power down and restart, it then loads to emmc fine Any ideas ? Thanks
 

oneway2k

Member
Nov 16, 2005
17
3
No Fastboot option from CyanoBoot menu

Fastboot (used for development)

For those familiar with “fastboot”, you can select the fastboot option from the CyanoBoot menu to go into fastboot mode. You can then (hopefully) flash to the boot or recovery partitions via USB cable using a command such as:

$ fastboot flash boot boot.img

I seem to be missing something here. I don't see a fastboot option in the menu. I'm running CM 11 nightly with CWM 6.0.4.8.

Thanks!
 

digixmax

Senior Member
Jan 17, 2011
2,083
665
Fastboot (used for development)

For those familiar with “fastboot”, you can select the fastboot option from the CyanoBoot menu to go into fastboot mode. You can then (hopefully) flash to the boot or recovery partitions via USB cable using a command such as:

$ fastboot flash boot boot.img

I seem to be missing something here. I don't see a fastboot option in the menu. I'm running CM 11 nightly with CWM 6.0.4.8.

Thanks!

To access Cyanoboot's "Boot Menu", hold down the N button as soon as the Cyanoboot boots up. "Start Fastboot" should be the last item on the menu.
 
Last edited:

J.Michael

Senior Member
Jan 20, 2018
613
387
I was unable to boot to stock without removing the SD-card. An older version of flashing_boot.img on the SD-card allows me to boot to stock.

I made a bootable SD-card using Succulent's cm_acclaim_11.0_01OCT2014_HD_SDC.zip. I used the MLO, u-boot.bin, and flashing_boot.img from the zip's root directory in the boot partition of my SD-card. My Nook Tablet would boot from the SD-card, I would get Cyanoboot, and I was able to SDC boot into Kitkat. When I tried to "INT boot" to the stock system, the screen would hang on "Read Forever" (never gets to "nook by Barnes & Noble").

The flashing_boot.img from post 100 of this thread, and the one from succulent_boot.zip, both allow me to boot to stock without removing the SD-card. They both display dates (at the bottom of the Cyanoboot screen) earlier than that displayed by the one from the CM11 zip.

I don't see any mention in this thread of a bug that was introduced and later fixed.

Code:
flashing_boot.img

from cm_acclaim_11.0_01OCT2014_HD_SDC.zip
      Thu Feb 6 19:43:36 2014
     boot to stock hangs on "Read Forever"
     (never gets to "nook by Barnes & Noble")
     boots to SD

from XDA thread   Say hi to "CyanoBoot"  post 100
  https://forum.xda-developers.com/showthread.php?t=1522226&page=10
  link https://dl.xda-developers.com/1/2/9/1/1/7/1/flashing_boot.img?key=Uh_dTxbbaqL03aFHh5rICw&ts=1516415905
ALPHA Sat Feb 18 07:51:59 2012
     boots to stock
     boots to SD

from succulent_boot.zip
      Wed Jan 9 16:53:13 2013
     boots to stock
     boots to SD
 

Top Liked Posts

  • There are no posts matching your filters.
  • 56
    Say hi to "CyanoBoot" -- a 2nd bootloader/w menu aka "ub2" - (WIP)

    “CyanoBoot”
    (aka a "second bootloader")
    Quick Guide
    by fattire
    (@fat__tire on Twitter)

    Alpha 0: "I don't have a NT" Edition​

    jFMQO13t3Gbub.jpg

    (Thanks to indirect for the image.)

    What is CyanoBoot?

    CyanoBoot (working title) is a “second bootloader” in early development, which is based on the open-source “u-boot” project, as further customized by BN & Bauwks. It is similar to the bootloader provided by Bauwks but has additional enhancements to make booting unsigned partitions easier and to generally enhance the booting experience on the Nook Tablet (aka “acclaim”) device.

    CyanoBoot is intended for use with the forthcoming CyanogenMod 9, but it can also be used to boot CM7 or Ubuntu Linux or even the stock firmware (provided of course you are not legally or contractually bound from doing so. I haven’t read or agreed to any BN user agreements, so can’t speak to this.)

    CyanoBoot includes an on-screen menu system, the ability to boot into three basic modes (normal, recovery, and “altboot”), configuration options, fastboot, and more.

    The same version of CyanoBoot should start from both SD card and emmc (although it must be packaged and installed differently for each.) It should work on both the 1gb and 512mb RAM models. NOTE: It has been reported that some devices may require a USB cable to be plugged in to boot from SD Card. If true, this issue is not understood and is not addressed, nor is it likely to be.

    NOTICE: CYANOBOOT (WORKING TITLE) IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND/OR THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES OF USING (OR ATTEMPTING TO USE) THE SOFTWARE. ALL SUCH ACTIVITY MUST OCCUR *ENTIRELY AT YOUR OWN RISK* AND YOU ACCEPT ALL CONSEQUENCES FOR DOING SO. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED RESULTS, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. CYANOBOOT IS NOT ENDORSED, AFFILIATED, SPONSORED, NOR ASSOCIATED WITH THE "DAS U-BOOT" PROJECT, GOOGLE, BARNES AND NOBLE LLC, TEXAS INSTRUMENTS, DENX., NOR ANY OF THEIR PARTNERS, OWNERS, EMPLOYERS, AFFILIATES, CLIENTS, SUBCONTRACTORS, OFFICERS, DIRECTORS, ADMINSTRATORS, INFORMATION PROVIDERS, ETC. EXCEPT INSOFAR AS THEY HAVE PROVIDED AND LICENSED SOURCE CODE TO BE FURTHER MODIFIED AND DISTRIBUTED. SEE THE RELEVANT GNU PUBLIC LICENSE FOR LICENSING DETAILS AND OTHER DISCLAIMERS. THIS SOFTWARE IS OBVIOUSLY INTENDED FOR USE ONLY BY THOSE WHO ARE AUTHORIZED TO DO SO.

    Whew!


    LIST OF THINGS


    • Started with “UB1” (aka u-boot, “first boot”) source code
    • Includes changes to support new 512MB model
    • Includes Bauwks’ repairs to fix “locked bootloader” malware
    • Many duplicate UB1 functions removed
    • One-build-boots-all (emmc or SD card, custom OS or stock)
    • Boot device indicator (top-left corner)
    • Bootcount indicator (top-left corner)
    • On-screen feedback to let you know what it’s loading.
    • Console-based boot menu
    • Support for key-combo shortcuts for menu/recovery
    • Alternate “Altboot” multiboot support allows 2nd OS.
    • Emmc setting for default boot profile (normal/altboot)
    • Emmc setting for default boot device (emmc or sd)
    • Emmc setting for automatic bootcount clearing
    • Boot fallback for stock firmware (0 bytes + sec. header)
    • Boot fallback for bauwks’ uboot (256 bytes)
    • Numerous visual enhancements
    • Unused bulky images removed (smaller file)
    • FASTBOOT support (w/menu selection)
    • On-screen build timestamp so you know version
    • Perhaps much more, or maybe not

    There are likely bugs all over the place, but this is how it's supposed to work:


    Key Shortcuts

    Hold down home (“n”) key for the menu.

    Hold down home (“n”) + “power” to have UB1 start recovery. If UB2 is also installed, it should respect this key combo and continue to load recovery.

    The default behavior if no keys are pressed is to boot “normally”-- if booting from emmc, the boot partition (p4) from emmc will be booted. If booting from SD the boot.img on SD file will be booted.


    The Boot Menu

    Use the Home (“n”) key to navigate through the menu options. You can select an option with the power key.

    The option you choose will override any other configuration you have made.

    NOTE: Just so you don’t ask-- the reason the home and power keys are used to navigate through the menu rather than the volume up and down keys is due to a required driver not being included with u-boot 1. While the home and power keys use a very simple “gpio” method to detect if they are pressed, the volume keys are more like keyboard keys and thus are more difficult to detect. (The Nook Color bootloader, in contrast, did have the appropriate driver, so volume key detection was possible.)


    Boot Indicators

    Since you can boot from either SD or EMMC, it may be difficult to ascertain which version you are starting from.

    Never again. You can now see whether you have loaded CyanoBoot from EMMC or SD by lookin at the top left corner:

    E” -> CyanoBoot is starting from emmc
    S” -> CyanoBoot is starting from SDCard

    The # that follows this indicator is the current “bootcount”. After 8 unsuccessful boots or so, stock behavior is to run recovery with a reflash instruction. See below for instructions on clearing the bootcount at every boot automatically.


    Fastboot (used for development)

    For those familiar with “fastboot”, you can select the fastboot option from the CyanoBoot menu to go into fastboot mode. You can then (hopefully) flash to the boot or recovery partitions via USB cable using a command such as:

    $ fastboot flash boot boot.img


    Installation (SD Card boot)

    (If you are preparing your own SD card for booting, you should be aware that for OMAP devices such as the acclaim, the SDcard must be formatted using a very specific configuration, which is detailed elsewhere.)

    For SD Card, CyanoBoot is packaged inside a “flashing_boot.img” file to be placed in the first vfat partition of the SD-card along with the signed “mlo” and “u-boot.bin” files from the 1.4.2 update.zip.

    (I'm told the mlo file may be called called MLO_es2.3_BN in the BN update.zip and should be renamed to “mlo”.)

    Next, the boot (“boot.img”), recovery (“recovery.img”) and/or alternate boot (“altboot.img”) image files may optionally be placed in this partition.


    Installation (EMMC boot)

    To boot from emmc, the “flashing_boot_emmc.img” file, which contains a packaged version of CyanoBoot, should be put at byte 0 of the third partition (recovery) and ALSO at byte 0 of the fourth partition (boot). Then, the boot/recovery partitions must be shifted “to the right” (to make room for Cyanoboot) so that it starts 512Kb in from the start of the file. Use a padding of zeros so that the boot image contents begin exactly at 512Kb.

    The boot and recovery partitions are expected to use this offset. For the alternate boot from emmc, the “altboot.img” may be the identical file used in an SD-boot, placed into the /bootdata vfat partition without any offset.

    NOTE: Again, use the flashing_boot_emmc.img file for emmc boot partitions, *not* flashing_boot.img, which is for SD card boot.


    Offset Info

    Again, when used on the emmc, CyanoBoot must be placed at byte 0, at both the boot and recovery partitions. The “actual” boot.img and recovery.img that would normally be at byte 0 of those partitions should be moved so that it starts 512Kb in.

    Always use this offset in recovery (p3) and boot (p4) partitions. In other words, put CyanoBoot at offset 0 and then pad with zeros, then put the normal boot.img or recovery.img at offset 512.)

    On SD Card, the “boot.img” and “recovery.img” files should have no padding or offset or anything. Use as normal. This is similar to how “uImage” and “uRamdisk” files are used on the NookColor, only use a single file for both with a header in front.


    Installation Summary

    One more time. Here are the locations for the boot images:

    SDCARD

    (p1-vfat)/boot.img file (no offset/padding)
    (p1-vfat)/recovery.img file (no offset/padding)
    (p1-vfat)/altboot.img file (no offset/padding)

    EMMC

    (p4-/boot partition)<- CyanoBoot at byte 0, boot.img contents at 512.
    (p3-/recovery partition)<- CyanoBoot at byte 0, recovery.img contents at 512.
    (p6-vfat)/bootdata/altboot.img (no offset/padding, same as SDCard)


    Configuration

    You can control the "default boot" behavior (ie, what happens when you don’t hold down any keys). If you are a developer that does not want to constantly clear the bootcnt, you can also cause CyanoBoot to clear the bootcount automatically at every boot. To do this, three configuration files may be added to /bootdata (partition 6) on the emmc.

    CONFIG #1: BOOT DEVICE

    This will cause CyanoBoot to always boot from the emmc boot partition rather than SD. In this way, you can boot “through” a bootable SD card to whatever is on the emmc.

    To Make Default Always Boot To EMMC

    $ echo -n “1” > /bootdata/u-boot.device

    CONFIG #2: ALTBOOT

    Aside from the normal boot and recovery boot, a third boot option is available, called “altboot” (alternate boot). This is a kernel/ramdisk pair that can be used for a third firmware, an overclocked kernel, or whatever you like. If you choose the “altboot” as a default and it does not exist, your boot will fail.

    As discussed above, the altboot.img file goes in the following location:

    SDCard: file on p1 called “altboot.img” (no special padding or offset)

    EMMC: file at /bootdata/altboot.img (no special padding or offset)

    To Make Default Always Boot to “altboot”

    echo -n “1” > /bootdata/u-boot.altboot

    CONFIG #3: CLEAR BOOTCOUNT -- You can automatically zero out the bootcount with every boot. To set this:

    To Make Default Automatically Clear BootCount

    echo -n “1” > /bootdata/u-boot.clearbc

    NOTE: A version of “Nook Tablet Tweaks” is planned to automate the above options much as Nook Color Tweaks does for the encore device in CM7.


    Thanks/Credits

    Thanks to chrmhoffman, nemith, xindirect, Celtic, and loglud for testing, as I don’t have a device and have never actually run this. Thanks to j4mm3r for the first encore menu code. It was pretty much rewritten for acclaim, but the first menu was invaluable in showing me how to add the code for the console. Thx to pokey9000 for stuff that helped get fastboot working.

    Also thanks to BN as well as all the talented u-boot developers at Denx and elsewhere for the GPL’d code upon which this was based.

    http://www.denx.de/wiki/U-Boot is where you can find the main u-boot project.

    Also, a huge thanks to Bauwks for his code contribution as well as for making this possible in the first place!

    Remember, this is all experimental. I'll try to update this post if there's something that needs to be updated.

    (source)

    If you have an issue, be sure to mention the timestamp at the bottom so everyone knows which version you're using. There will be bugs.
    11
    Okay...

    Wrong. I know what I'm talking about.

    Really? You're really going to double-down on this?

    ROMs don't overwrite bootloaders in my experience.

    Glad you qualified it with "in my experience". Your limited experience obviously doesn't include the Nook Color, which does replace uboot. And your experience clearly doesn't including careful reading of threads relating to the Nook Tablet's locked bootloader, otherwise you'd understand why the second bootloader is necessary. You'd understand that is does NOT replace the original stock bootloader, but suppliments it in a way that is absolutely necessary.

    I've flashed custom bootloaders via ADB, but I've NEVER seen a ROM (at least for my device) actually include a bootloader.

    So none out of all the your device(s) had to deal with a locked bootloader. So?

    It's just not necessary. Once you've rooted your device and installed CWM recovery (or an equivalent), you just flash the ROM's zip file.

    A lot of "devs" have a reputation for delivering the smackdown on people who drop into a forum throwing around attitude without knowing what they're talking about.. and believe me, I'm trying hard really to be polite and not condescend here... So yeah, I get it- you've installed CWM on a device or two and you think you understand the process. But not every device is the same. I'm about to jump on a plane, so I'll try to make this as simple as I can:

    Unlike many devices that work exactly how you describe (root, install a recovery, and flash the rom), the Nook Tablet has extra security-- a design flaw from Barnes and Noble-- that has to be fixed/circumvented. That is, there is a signed booting process where once the power turns on, the pre-bootloader (aka "x-loader" aka "mlo") will not run unless it is signed by Barnes and Noble, and contains a digital signature that can be verified as authentic. The pre-bootloader then loads the bootloader (u-boot) which also has a digital signature which is checked. The bootloader and pre-bootloader can not be replaced-- the hardware will not run unsigned or improperly signed files. The signed bootloader (u-boot, remember), then loads the boot.img (or recovery.img) file which ALSO has a digitial signature that is ALSO signed by barnes and noble. (If you are booting from SD card, there is a FAT file called flashing_boot.img that works the same way).

    So there is a boot chain: hardware->mlo->uboot->kernel/ramdisk (aka boot.img/recovery.img) and every step of it is signed. If you replace any of these parts with a custom version, the boot stops.

    Without going into technical detail, CyanoBoot implements Bauwks' fix for this. The technical detalis as far as implementation go are in the first post, which you should read. The menu stuff is just extra.

    Crap. Plane is leaving.

    So you're saying that with CWM recovery installed on the device, I can't install a ROM via the typical zip file method? This is a complete surprise.

    Surprise! (You can of course flash via the typical zip menu as the zip will install everything for you. The second bootloader is part of boot.img/system.img/flashing_boot.img, but this is described in detail in my previous posts and in the original post which you claim to have read, so you know this already)

    See this article: http://raywaldo.com/2012/09/root-for-nook-tablet-1-4-3/ and jump to the section "Flash Jelly Bean Android 4.1.1". Looks like you can flash a ROM here via the way I've always done it.
    I
    I did read it. Clearly you didn't read my post completely. You may have read the words, but you don't seem to have actually thought about my questions...

    Yeah, I guess you're right and I don't know what I'm talking about. You put me in my place and shut me down.

    I have learned a lot here. You have learned nothing.

    Damn. Gotta shut off electronic devices.
    10
    https://github.com/Rebell/acclaim_cyanoboot/commit/33228462ece75fe8274f76ad368c333130c02174
    Added some more things I just remind:
    Added primitive VOLUP/VOLDOWN driver.
    Ported .img detection from Encore - unavailable booting modes are greyed out, EMMC normal and EMMC recovery are always ON.
    Added battery level & board rev info. Enabling battery charging in case of level < 30 - doesn't seem to work on my board (FIXME).
    Lowered brightness to drain less battery power.
    Turned off BN board charging procedure.
    Change default booting source from Encore - still untested/unfinished.
    Added OMAP4 IRQ header just in case.
    Added Bauwks image generation script.

    Please check it out.
    8
    Commited patch. Together with fix for fastboot screen corruption during loading big files (moved framebuffer far away from it).
    Binaries are already in ics and jb branch. :)
    6
    Thanks meghd00t. Guess something with loading is broken so it cant handle 0x200 offset. We don't need it for now anyway I guess.

    Oh yes. List of expected files it's looking for is of course:
    /emmc/altboot.img
    /sdcard/boot.img
    /sdcard/recovery.img
    /sdcard/altboot.img
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone