[BOOTLOADER][MULTIBOOT + RECOVERY][BOOTMENU] Patched ICS bootloader V9 (19/07/2013)
- Thread starter Skrilax_CZ
- Start date
-
- Tags
- development
In this case I'm only the messenger , the people making this possible are the man.!!
okay im thoroughly confused....I am running Taboonay 3.0.1 right now....I want to flash flexreaper and update to ics bootloader. I am confused bc I see guides if you are on the leaked ICS but I don't think I am right? I think I am still on HC bootloader.
Help please!
Thanks!
Help please!
Thanks!
You don't need ICS bootloader to run FLEXREAPER-R12.5 , but I do recommend it.
FLEXREAPER got auto detection for what booloader you got , so it installs the correct kernel.
What exactly are the advantages to upgrading from the HC bootloader? I'm trying to weigh the balance since I only run flex reaper and don't need the bl to run it, kinda the same dilemma I have with doing that stupid "wire trick" to s-off my rezound when everything is fine without s-off
Main advantage is that you no longer have to worry about ending up in unrecoverable state, such as when on HC bootloader you corrupt both boot / recovery partitions (such as not running itsmagic etc.) - you can recover with fastboot easily.
Can only confirm this as I flashed and kinda bricked my tablet twice today (testing this rom I made for easy installing the ICS bootloader) but was able to recover it with fastboot.
I agree. Now that ICS is out, I think it's time to leave HC behind. I've been using the leaked version of ICS for weeks (months?) and have been very happy with it. Personally, I don't see much of a need for HC anymore. And with the new bootloader, like Skrilax and civato said, It's SUPER easy to recovery from a general uh oh.
I flashed this using civato's guide, and now I can't load any ROM whatsoever. I've flashed several through CWM (which does boot), but every one I've flashed hangs at the bootloader screen without proceeding to boot a kernel. Thoughts?
You'll need to flash the ICS kernel for whichever ROM your trying to load. Civato has his in his OP. The bootloader detection in his rom may not work with this bootloader. IIRC, it looks specifically for the 0.03.11-ICS version.
That did it. I'm guessing that installing Flexreaper added something that was missing from CM9, since I was able to get CM9 working again by flashing that over Flexreaper. Strange, but whatever works...
Next issue: I can't seem to get fastboot on OSX or Linux to see the tablet when the bootloader is in fastboot mode. Both work with my Galaxy Nexus. I'd like to be able to get another recovery installed other than CWM - I'd been using RA before this, then TWRP, but neither load through Acer Recovery Installer, so that only leaves fastboot as an option.
Edit: OK, so it would appear that TWRP and presumably RA don't work with the new bootloader. Still bugs me that "fastboot devices" turns up nothing, though...
Last edited:
Okay - I hope I'm not the only one ignorant of this. Everyone mentions the fastboot capability of this bootloader and how it is now impossible to brick the device. But no one has explained exactly how fastboot is used in the real world. Do you have to be running ADB on the PC, or some other app? Having the command list is great, but how do you use it? Any real examples of how to unbrick, for instance?
Thanks,
Thanks,
Added small info to first post. Fastboot is part of Android SDK, just like ADB. To unbrick (assuming both recovery / kernel screwed up), flash recovery with fastboot, then back backup using the recovery.
I still have problems getting this bootloader to be recognized in Windows. Perhaps I need an other fastboot build than I'm currently using, I don't know I'm not much of a Windows person.
I couldn't get fastboot to connect on Linux until I tried a newer binary which was shared here.
As a test I've now rebuild fastboot on my own Linux desktop, but I can't try that version until later when I'm home.
Could you do a small writeup on how to go about using fastboot....? im fricking clueless sorry to say 
Could you do a small writeup on how to go about using fastboot....? im fricking clueless sorry to say
Here is a good place to start
This link yielded a working fastboot binary for Linux. Now if only there was something to do with this tablet in fastboot mode other than brick and unbrick my tablet...
Thanks for the help, Maldune.
Similar threads
- Sticky
Top Liked Posts
-
There are no posts matching your filters.
-
81Allright, final ICS is out, but the stock bootloader still doesn't have fastboot oem unlock working. So, it's either HC bootloader or patched ICS bootloader. Please note that installing custom kernel / recovery on unpatched ICS bootloader will require recovering your device only with nvflash!
This bootloader can only be flashed using nvflash. You can use the guide here http://xdaforums.com/showthread.php?t=1622425. There is also a post explaining nvflash in here: http://xdaforums.com/showpost.php?p=22923662&postcount=9
YOU DO EVERYTHING AT YOUR OWN RISK!!!
Patched Bootloader V9 (V9-gbc410d4): (19/07/2013)
- based on latest Acer BL 0.03.14-ICS, it will pass 0.03.14-EXT to command line, along with V9-ga81f36b for revision
- booting from ext4 filesystem (see further for howto)
- grub style selection screen if multiple images are installed
- added font outline & kerning, uses updated skin application (by yaworski)
- GUI improvements
- haptic feedback
- OpenSuse 12.3 theme
- expanded fastboot commands
- fixed debug mode cmdline
Patched Bootloader V8: (07/06/2012)
- based on latest Acer BL 0.03.14-ICS, it will pass 0.03.14-MUL to command line
- fastboot handler is completely build from source code
- fastboot:
- A) download command will no longer write downloaded data to cache,
this means that on using flash and boot command, cache won't be wiped
- B) more convenient bootloader flashing (reboots right away to new BL)
- C) you won't have to have cache partition sized larger than other partitions,
in order to flash them
- D) maximum data size that can be send with fastboot is 700 MiB
- revamped GUI, now with fullscreen bootsplash and custom font, and themable
- added fastboot oem sbk command, which will print sbk on the tablet
- several small changes
Patched Bootloader V7: (31/05/2012)
- based on latest Acer BL 0.03.14-ICS, it will pass 0.03.14-MUL to command line
- one bootloader for both A500 / A501
- expanded bootmenu application (built from source) with handling several fastboot commands
- fastboot getvar serialno will return real serial number
- bootmenu has options to boot primary / secondary image on current boot
- attempting to boot invalid kernel image will result in being stuck in bootmenu
Patched Bootloader V6: (20/05/2012)
- based on latest Acer BL 0.03.14-ICS, it will pass 0.03.14-MUL to command line
- added simple boot menu (built from source)
Patched Bootloader V5: (18/05/2012)
- based on latest Acer BL 0.03.14-ICS, it will pass 0.03.14-MUL to command line
- dualboot (read lower for more information)
- added "fastboot flash bootloader bootloader.blob" command
Patched Bootloader V4: (13/05/2012)
- based on latest Acer BL 0.03.14-ICS, it will pass 0.03.14-UNL to command line
- allow bootlogo change (scroll down)
- allow unsigned update via bootloader.blob using CWM
- fixed: AKB partition is no longer used
- fixed: debug on / off works correctly
- fixed: bootloader will now boot to recovery if you erase boot (LNX) partition
- change: bootloader won't pass vmalloc parameter to cmdline
Patched Bootloader V3: (26/04/2012)
- no signature checks
- no "itsmagic" check
- based on latest Acer BL 0.03.12-ICS, it will pass 0.03.12-UNL to command line
- enabled fastboot (details lower)
- replaced bootlogo (moreover just testing that, need to allow bigger image)
FASTBOOT & BOOTMENU (since V6):
POWER + VOLUME DOWN will boot to recovery (won't erase cache).
POWER + VOLUME UP will boot to bootmenu.
In bootmenu, you can do:
A) Reboot
B) Go to fastboot mode
C) Toggle boot mode and set default kernel image on the selection screen
D) Toggle debug mode (modifies cmdline), forbid EXT4 boot in case of a bug in fs
E) Make selection screen include recovery and fastboot
E) Wipe cache (in case you get bad bootloader update and tablet won't boot)
To check for fastboot commands, see the README on the Github.
Here is CWM for ICS bootloader: http://xdaforums.com/showthread.php?t=1654476 , you can flash it from fastboot after you flash the bootloader.
Do NOT run itsmagic on V5+ if you use dualboot, it will corrupt the secondary boot image.
BOOTLOGO CHANGE:
Changelog:
1.06 (19/07/2013)
- updated for V9
1.05 (07/06/2012)
- new application for V8
- customizes bootsplash and the colors
1.04 (31/05/2012)
- updated to support V7
1.03 (19/05/2012)
- updated to support coming V6
1.02 (18/05/2012)
- updated to support V5 as well
1.01 (14/05/2012)
- fixed blob loading & generation
- fix: require only .NET 2.0
1.00 (13/05/2012)
- Initial release
Download the tool from here:
Windows: http://skrilax.droid-developers.org/a500/nvflash/tools/A500BootLogo_106_v9_win.zip
Other OS (Mono): http://skrilax.droid-developers.org/a500/nvflash/tools/A500BootLogo_106_v9_mono.zip
Steps to change bootlogo:
(V4 - V7, applcation version 1.00 - 1.04)
A) Open the bootloader using File menu.
B) Open the image you want using Image menu (the image size must be 268x72)
C) Save the bootloader as *.blob
D) Flash it with a fastboot
(V8, applcation version 1.05)
(V9, applcation version 1.06)
A) Open the bootloader using File menu.
B) Open the image you want using Image menu (the image size must be 1280x800), note file limit max is 200 kB
C) If you wish, tick the checkbox for color customization and set the colors at your wish
D) Save the bootloader as *.blob
E) Flash it with a fastboot
Stock bootlogo is in attachment.
If you want to flash as *.blob, you have to create an update.zip for CWM and flash using this update script:
Code:mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system"); package_extract_file("bootloader.blob","/tmp/bootloader.blob"); unmount("/cache"); format("ext4","EMMC","/dev/block/mmcblk0p4","0"); run_program("/system/bin/dd","if=/tmp/bootloader.blob","of=/dev/block/mmcblk0p4"); unmount("/system");
mmcblk0p4 is cache partition. Please note that flashing a nonworking bootloader via *.blob will require recovery using nvflash.
MULTILBOOT:
Before I start, the bootloader will work correctly if you just use single kernel image as you were used to on previous versions. You can just use it the very same as the older versions.
In other words, you can just install it and not have to bother about this at all.
Allright, new feature of V5 is dualboot, i.e toggling to boot two different images and keeping the recovery intact, it is primarily intended to run both Android & Native Linux ported by sp3dev. In V9 this was extended with booting from EXT4 filesytem.
First, basic information:
Multiboot sets the booting partition with "permament effect" (i.e not like holding down a button to boot secondary partition, nothing like that). It is the parition that is highlighted by default on the selection screen.
Primary kernel image is LNX partition (/dev/block/mmcblk0p2, size 8 MB), or "boot" when using fastboot flash / erase command. This is the default partition, used by older bootloaders as well.
Secondary kernel image is AKB partition (/dev/block/mmcblk0p7, size 10 MB), or "secboot" when using fastboot flash / erase command. This parition used for storing checksums on HC bootloader. If this partition doesn't contain Android boot image, it will not show.
Further kernel images can be specified in the menu file for the bootloader.
Now, how to toggle between booting images:
A) Using bootloaderctl
B) Using fastboot:
- "fastboot oem set-boot-image 0" - sets to boot first kernel image
- "fastboot oem set-boot-image 1" - sets to boot second kernel image
- etc.
C) Using bootmenu GUI
Now, how to flash the secondary kernel image:
Either use "dd if=secboot.img of=/dev/block/mmcblk0p7" from within android or recovery, or in fastboot, you can use:
Code:fastboot flash secboot secboot.img <- to flash fastboot erase secboot <- to erase
DEV:
A) Dualboot
bootloaderctl can be used to modify bootloader settings. Source is in github, or use precompiled version for Android: http://skrilax.droid-developers.org/a500/nvflash/images/bootloaderctl
B) EXT4 FS boot
Since V9, there is also support for EXT4FS boot. Here is example menu.skrilax file for setting it up:
Code:================================================================================ Example menu.skrilax file: ================================================================================ ; commentary is prefixed with ';' ; .ini file structure ; First, three possibilities to boot from partitions ; LNX - primary image (always present, can specify title only) [LNX] title=Android ; AKB - secondary image (will not show if property AKB partition doesn't hold android image) [AKB] title=LUbuntu ; SOS - recovery image (will show if it's set by user) title=CWM ; Properties for EXTFS booting ; ; title - text to show in menu ; cmdline - override cmdline (prefixing with @ will make the bootloader append the cmdline to the default one) ; ; Then there are two possibilities: ; ; A) boot android image ; android - path to android image (will be used if present) ; ; B) boot zImage with ramdisk (optional) ; zImage - path to zImage ; ramdisk - path to ramdisk (optional) ; First entry [BOOT1] title=EXT4FS Boot 1 android=APP:/boot/boot.img ; Second entry [BOOT2] title=EXT4FS Boot 2 zImage=APP:/boot/zImage ramdisk=APP:/boot/ramdisk
Important to note is that path is in bootloader format i.e PARTITION:file_path_in_partition. For instance APP:/boot/boot.img would be for /system/boot/boot.img when mounted in Android. To see the partition list, see the readme on github.
Lastly you have to tell the bootloader the location of the file. Either boot to android and use bootloaderctl under root user (assuming that the file is under /system/boot/menu.skrilax):
or use fastbootCode:bootloaderctl --set-boot-file APP:/boot/menu.skrilax
Code:fastboot oem set-boot-file APP:/boot/menu.skrilax
If you have problems with booting (stuck on BL screen w/o text showing anything) and have EXT4 FS boot setup, reboot to bootmenu and forbid EXT4 FS boot (it may get stuck if FS is corrupted).
C) Bootmenu
Bootmenu part of the bootloader is open source, with basic functions of the bootloader map. This includes full framebuffer access (hacked a bit as of V9), some standard library functions (you can use your own of course), partition handling, gpio (key handling), fastboot, reboot. Bootmenu currently acts as sub-bootloader, as it passes control back to the bootloader for booting the actual image.
Bootmenu is licensed GPL V3, you can find repository here: https://github.com/SkrilaxCZ/a500_bootmenu
Compile it by making "make", with CROSS_COMPILE set. You can also use "O=../obj" if you prefer obj folder like I do. Also for bootloaderctl either set NO_BOOTLOADERCTL=1 or LINUX_COMPILE and ANDROID_COMPILE for cross-compilers for Linux or Android.
FAQ:
Q: What are the main advantages over HC bootloader?
A: Mainly fastboot. Then more comfort, but for running a custom ROM, HC bootloader is just as fine. And since V5, the possibility of dualboot.
Q: Can I unbrick my A500 with nvflash?
A: Provided, that you saved CPUID to generate SBK and have mmcblk0_start backup, yes. You can recover by installing this bootloader over HC bootloader should you have SOS and LNX image checksum failure.
Q: What is the best way to install ICS bootloader?
A: First install the bootloader with nvflash. Then using fastboot (POWER + VOLUME UP) flash recovery. From there flash ROM for ICS bootloader. You can however install the recovery with nvflash too.
Q: How do I use fastboot?
A: Fastboot is part of Android SDK, you get it just as you get adb. To recover with fastboot, reset the tablet and hold POWER + VOLUME_UP, the tablet will say "Fastboot Mode". Open up command line in the directory where you have fastboot, and use:
Basically, to unbrick it, use the one to flash recovery. Then boot to the recovery, and flash working backup / ROM, whatever you like.Code:fastboot flash boot boot.img <- flashes boot.img (to kernel partition - LNX) fastboot flash recovery recovery.img <- flashes recovery.img (to recovery partition - SOS)
Q: Fastboot oem debug on / off:
A: This has use only for kernel developers. Fastboot oem debug on / off will only change the cmdline to serial console (on) or null console (off). The console parameter can be edited on offset 0x87638, by default it is "console=ttyS0,115200n8".
Q: Updating BL via recovery:
A: Since V4 supports flashing custom bootloader.blobs. Trying to flash custom bootloader.blob on any other bootloader will result in update failed and bootloader not modified (so this part is safe). Flashing a bad bootloader via bootloader.blob will require recovering with nvflash.
Q: Factory reset:
A: Factory reset (Vol UP and switching the rot. lock) is not supported on patched bootloader, use recovery or "fastboot erase userdata".
Q: The tablet won't boot secondary kernel image, but I have working kernel image. What should I do?
Toggle boot partition in boot menu back to primary.
Q: The tablet doesn't boot after bootloader install.
Boot to bootmenu and wipe cache.
INSTALL:
There are four methods of installing:
A) Flashing the *.bin file using nvflash manually, providing as the bootloader_apx.bin to "-bl" argument
B) Using blackthund3r's tool, see guide here: (guide here: http://xdaforums.com/showthread.php?t=1622425
C) If you have V4+ installed (or newer), you can flash the update.zip for CWM
D) If you have V5+ installed, then you can also use fastboot: "fastboot flash bootloader bootloader.blob". Please note that if you supply invalid block image, then you have to use "fastboot erase cache".
CREDITS:
Bootmenu uses code from following applications:
GRUB: jpg loading
SUSE: V8, V9 Splash screen image
yaworski: font outline / kerning
DOWNLOAD:
There are zip files with bootloaders for a500 / a501 - containing three files:
bootloader_apx.bin - this is bootloader binary to be booted when flashing via nvflash (use with -bl argument)
bootloader_hc.bin - this is HC bootloader, w/o signature and itsmagic checks
bootloader_ics_vx.bin - this is the ICS bootloader file
Please note that using old bootloader_apx.bin (from pre-V5 package) when updating manually will corrupt your secondary kernel image.
Alternatively, you can find there a500apx images for blackthund3r's tool (http://d-h.st/Fkt), there is also repository for the tool on this URL "http://skrilax.droid-developers.org/a500/nvflash", contains only bootloaders. They can be downloaded manually as well.
Download page: http://skrilax.droid-developers.org/a500/nvflash/images/
A500 / A501 ICS V9 BL:
Zip: http://skrilax.droid-developers.org/a500/nvflash/images/a500_a501_bootloaders_apx_ics_v9.zip
blackthund3r's tool package: http://skrilax.droid-developers.org/a500/nvflash/images/A500_A501_ICS_V9_bootloader.a500apx
Update.zip for CWM: http://skrilax.droid-developers.org/a500/nvflash/images/a500_a501_cwm_update_v9.zip11Allright, V8 released, changelog in OP.
There is new tool to be used for changing bootsplash / colors of the bootloader.10V7 in OP (differs from all prereleases). This time one bootloader for both A500 / A501, changelog in OP.
PS: Yeah reacts on oem lock too8I've updated the repository, for those who are playing with the bootmenu source.
Several simple "proprietary" functions are now using source code.
Newly, bootmenu application parses key input and misc partition command and decides which mode to boot (BootMenu / Fastboot / Recovery / Factory Reset / Normal).
In the bootmenu, you can also select to boot from primary and secondary kernel image. Attempting to boot invalid image will cause you to be stuck in bootmenu.
Fastboot has been partially hacked, "fastboot getvar" response is built from source now.
Lastly, bootmenu main function either returns (and goes to fastboot mode), or loads android image from partition (proprietary function atm.) and passes it directly to booting function (pointer to the image and offset of entry point in the image). So first step to boot any kernel image.
PS: Do not use "fastboot continue"7Updated to V4:
- based on latest Acer BL 0.03.14-ICS, it will pass 0.03.14-UNL to command line
- allow bootlogo change (see OP)
- allow unsigned update via bootloader.blob using CWM
- fixed: AKB partition is no longer used
- fixed: debug on / off works correctly
- fixed: bootloader will now boot to recovery if you erase boot (LNX) partition
- change: bootloader won't pass vmalloc parameter to cmdline
