[FYI] nandroid on XT720 does not restore boot.img - Milestone XT720 Android Development

Nandroid is unable to restore boot.img in bootstrapped OpenRecovery because the kernel command line sets the boot partition read only. You can verify this by trying a nandroid restore followed immediately by a nandroid backup of boot and comparing the *.md5.
The kernel boot command line used for normal boot and bootstrap recovery includes:
mtdparts=omap2-nand.0:[email protected](pds),[email protected](cid),[email protected](logo),384k(misc),3584k(boot)ro,[email protected](recovery),8960k(cdrom),[email protected](system),[email protected](cache),177280k(userdata),1536k(cust),[email protected](kpanic)
Note: boot is the only one marked read only here, so this does not affect the others and there are additional partitions that are not visible for normal boot that don't work in bootstrap recovery (bpsw, etc)
This explains some things:
Back in the fastboot thread where a modified stock boot.img was used to comfirm resar's discovery that "fastboot boot boot.img" works on XT720 without signature checks, I once wrote what we can now see is quite wrong:
Mioze7Ae said:
DON'T BOTHER TRYING TO NANDROID THE MODIFIED BOOT.IMG, I'VE CONFIRMED THAT THE BOOTLOADER WILL REJECT IT AND FALLBACK TO A PREVIOUS BOOT.IMG. I'm not yet sure if it fallsback to the last bootloader-verified boot.img or to the sbf-flashed boot.img. If you try nandroid anyway (perhaps because you think I'm not technically competent to test nandroid) I recommend immediately reflashing a known good kernel in OpenRecovery and rebooting between each attempt. The phone has two boot.img. I'm not sure if the backup one comes from the sbf or if somehow the active one is alternated by the bootloader after each successful validation. My superstition is to let the bootloader see two known good kernels between each attempt. BE VERY CAREFUL. fastboot boot boot.img doesn't flash anything--that should be safe.
Click to expand...
Click to collapse
It didn't occur to me at the time but there's a pretty big discrepancy between what proposed was happening and what happens when you use fastboot to flash the boot.img (which causes an immediate signature error on next boot). Well, guess what? The easiest solution is nothing happened when I used nandroid (and I've just gone back and confirmed that). Nandroid failed to write the modified boot.img to the read-only boot partition so nothing changed next boot. The phone does not have two copies of boot.img.
I think this also resolves the disagreement back in the xda-special era about whether to flash the whole Singapore sbf or just the boot.img to enable TV out via the headphone jack. I still believe the only change needed is to replace the kernel (boot.img) with the older since newer kernels disabled the functionality (as seen in Motorola's git commit logs). I insisted that nandroid restore of boot.img was sufficient, even though everyone actually testing TV out on the audio jack insisted that flashing sbf was necessary.
Another strangeness is that I prefer to run the CBW sbf, but put in the UK kernel to bump the clock speeds. The CBW is clocked at 550MHz, and the UK is clocked at 720MHz (and the graphics core is faster on the UK one too). But whenever I would go into Milestone Overclock it would say 550MHz. Given the other troubles we have with Milestone Overclock, I had just assumed it was a bug. But this explains that as well.
FYI2: as an interesting aside, when I was rereading resar's thread this evening, resar also originally reported that fastboot mode can be used to flash /system and /data directly without signature checks. We get access to fastboot immediately on a stock ROM after enabling USB debugging. So this could be a different vector for installing custom ROMs or restoring a nandroid without bothering to first root or install openrecovery. Now if we could just get into fastboot from a power off state...

An interesting corollary: do either of the two boot.img packaged by ultimobile for CBW do anything?

what device did you mean in "UK is clocked at 720MHz"? is that the korean motoroi?
if so, one thing I have observe in motoroi is that, whenever i overclocked it the battery temperature goes over 40 degrees Celsius even if i set it only at 600Mhz using the ONDEMAND governor. if i disable the overclock and leave it to 550MHz, my phone goes well staying at 33 degrees Celsius.
I also observe during charging at "OFF state". Whenever a charger is plugged in, XT720 automatically turns on and goes on to the "Normal ON State" (i.e. the home screen). While in SAMSUNG Android phones, they have there own
"Charge state/Charge Mode", where there's only a battery animation shown while charging.
My conclusion is that, if our XT720 can do a charge state without fully turned on. then maybe we can use fastboot just like in recovery mode. You can use fast boot in recovery mode.

There are two versions of the Milestone XT720 kernel. The earliest ones are 550MHz. The later ones are 720MHz. The UK sbf is one example of the 720MHz era kernels that has been used a lot. From what I know, Motoroi uses OMAP3430 which is officially rated at 600MHz by TI. Milestone XT720 has OMAP3440, which is officially rated at 800MHz by TI.
Milestone XT720 does have a charge only mode, but the battery has to be really, really low (like below 5%) at boot and plugged in to a charger for that to kick in. Otherwise if it figures it has enough stored charge to boot up for a while (and possibly charge while running) it will, otherwise it shuts off is USB isn't attached. During normal boot a program called mot_boot_mode is run that checks the battery state and decides whether boot should continue to full Android UI or to instead go to the minimal charge_only_mode to charge as quickly as possible or shut down and wait for a power cable to be attached. So, unfortunately, it runs after the stock kernel is already loaded.
The phone also doesn't always power on when plugged in. The phone keeps track of "why" it's turned off. If you explicitly power off, it remembers that you told it to be off and won't auto boot until you turn it on. If you yank the battery or if it shuts off because the battery is too low, it will auto boot. It also stores a "reboot reason", that's how it knows to go automatically to android/recovery/bootloader/fastboot on next boot. Button chords can override the defaults, but we don't know how to set the fastboot boot reason with buttons (or if that is even possible). We can only reboot into fastboot.

My Motoroi always go charge only mode if I turn phone off then plug it in wall charger, it never wake up with USB charger. I think the thing made this available is have charge_only_mode in /system/bin since init script defined that binary as service and it will automatically boot into that mode when it have triggered by USB wall charger from full off state. This should fired by bootloader I think.
Sent from my XT720 CM9-t2w

i think it doesn't need
sorry for my comment for you
but i think we don't need it
say (in develoid cafe in korea) edit sbf and success to replace recovery partition
it will allow to recovery from OTA(from milestone's update.zip type)
also it allow to replace boot, bpsw and other partition (already tested by me)
i don't know how can do it but i already has modded korea 50R SBF
and i already made recovery.img flasher using flash_image binary (but it has big problem for safe so i not spread it)

Hi dateno1!
The problem we've had with the vulnerable recovery on Milestone XT720 is currently we have to choose either vulnerable recovery *or* working sensors. Somehow replacing devtree.img with a Milestone XT720 version fixes sensors, but it also breaks recovery (recovery won't boot -- stuck at (M) -- regular boot will continue working though).
MilestoneXT720 phone: MilestoneXT720 kernel + MilestoneXT720 devtree + Motoroi recovery:
(-) vulnerable recovery doesn't boot
(+) sensors are correct
MilestoneXT720 phone: MilestoneXT720 kernel + Motoroi devtree + Motoroi recovery:
(+) vulnerable recovery boots
(-) rotation sensor always off by 90 degrees
MilestoneXT720 phone: Motoroi kernel + Motoroi devtree + Motoroi recovery:
(+) vulnerable recovery boots
(--) no rotation sensor at all, problems with leds
One way to fix this is to fully port over to the Motoroi kernel (by creating a new sensor module for the MilestoneXT720's kxtf9). The changes between Motoroi and Milestone XT720 in the core omap driver seem pretty extensive, though. The other option is if I can figure out what's wrong with the devtree, I could also just use the Motoroi devtree and patch the Milestone XT720 kernel using symsearch.ko. Either way I fear it's going to be quite a bit of symsearch hacking.
http://forum.xda-developers.com/showpost.php?p=21220676&postcount=48

Mioze7Ae said:
Hi dateno1!
The problem we've had with the vulnerable recovery on Milestone XT720 is currently we have to choose either vulnerable recovery *or* working sensors. Somehow replacing devtree.img with a Milestone XT720 version fixes sensors, but it also breaks recovery (recovery won't boot -- stuck at (M) -- regular boot will continue working though).
MilestoneXT720 phone: MilestoneXT720 kernel + MilestoneXT720 devtree + Motoroi recovery:
(-) vulnerable recovery doesn't boot
(+) sensors are correct
MilestoneXT720 phone: MilestoneXT720 kernel + Motoroi devtree + Motoroi recovery:
(+) vulnerable recovery boots
(-) rotation sensor always off by 90 degrees
MilestoneXT720 phone: Motoroi kernel + Motoroi devtree + Motoroi recovery:
(+) vulnerable recovery boots
(--) no rotation sensor at all, problems with leds
One way to fix this is to fully port over to the Motoroi kernel (by creating a new sensor module for the MilestoneXT720's kxtf9). The changes between Motoroi and Milestone XT720 in the core omap driver seem pretty extensive, though. The other option is if I can figure out what's wrong with the devtree, I could also just use the Motoroi devtree and patch the Milestone XT720 kernel using symsearch.ko. Either way I fear it's going to be quite a bit of symsearch hacking.
http://forum.xda-developers.com/showpost.php?p=21220676&postcount=48
Click to expand...
Click to collapse
oh sorry i forgot that between xt720 and motoroi

Related

Help! Can't boot / cant get into recovery. ..

I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
jimjenkins said:
I was unlocked and rooted and ready to install CM7. I followed all the instructions in the Official Atrix CM7 OP to the T, but when it rebooted, I got stuck on the boot screen with "unlocked" and the red M logo.
I tried to repeat the process several times and ended kind of giving up, factory wiping, and then trying to restore my backup. It appeared to restore successfully, but when I rebooted the phone now wont boot at all. I can't even get it into recovery. No combination or order of button presses or battery pulls / usb plugins will turn it on. I just have a green light like it's charging but nothing is working.
Is it possible to brick your phone even after you have been successfully unlocked and rooted just while you are trying to install CM7?
Please help. I am really desperate here. . .
Click to expand...
Click to collapse
are you using the right recovery? romracer or rom manager!
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
jimjenkins said:
i am using the tenfar CWM included in the Atrix 4G Automatic Unlock script package. will this not work?
if not, how do I replace it with the right recovery if I cant even get into the phone?
Click to expand...
Click to collapse
no, that the old recovery you can use the rom manager if you have , or romracer latest recovery you can find that in the development section, also ther was instruction in the cm7 thread.
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Yeah youre going to have to fastboot wipe recovery then fastboot flash recovery recovery.img
Just download rom racers and rename it..recovery.img
Sent from my GT-I9100 using xda premium
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
jimjenkins said:
Great. Sorry to be such a noob, but do I decompress the CWM-recovery-atrix5.zip file and push the recovery.img file that's inside it? or push the CWM-recovery-atrix5.zip itself?
Also - every time I am able to get my phone into fastboot mode, it says my battery is too weak to flash anything. I cant seem to get the battery to charge enough to execute any fastboot commands. Any way around this? a powered usb hub?
Click to expand...
Click to collapse
If you can borrow another Atrix user's battery, or take yours to an AT&T store and see if they can charge it for you.
If you're able to get back into recovery then you can just flash the zip.
If not, you'll need to extract the recovery.img to use it with fastboot, or just download it directly from the OP in romracer's thread. (The left hand link is just the .img, the right hand side is the CWM .zip) Then place it in the same directory as fastboot.
So I can literally flash a different recovery from within another?
jimjenkins said:
So I can literally flash a different recovery from within another?
Click to expand...
Click to collapse
yes but it MUST be working proper first ! its ok to use rom managers cwm but i just prefer the otherone alawys have but n e way there are only 2 that are current (uptodate )
thoughs 2 and with romracers you can. chose
a color that you like not just blue
Sent from my MB860 using xda premium
Its the recovery from tenfar CWM. When I can get it into recovery it seems to be working - with the obvious exception of successfully installing CM7
So I can flash romracer recovery from inside tenfar recovery?
sorry if im being redundant - just dont want to screw it up!
thanks
Just download rom racers cwm. Img, head into fastboot and then fastboot flash recovery recovery-****** (whatever yer recovery image color u chose is)
Sent from my MB860 using Tapatalk
I was able after a full day of leaving the phone plugged in, to charge it up. Then I flashed the rom racer recovery, rebooted into recovery (new version), installed CM7, installed gapps, and voila! A working CM7 Atrix. thank you soo soo much guys.
Can't boot android/recovery
ClearFire said:
you should have left it alone at the M boot screen because it takes about 5-10min to boot after unlock and flash...
everything you do now will have to be through fastboot DO NOT SBF FLASH ANYTHING!!!
Go here to use Fastboot
then download the system.img and boot.img from here
use fastboot to push the boot.img and system.img to your phone
if it gets stuck at the M boot screen let it sit for at least 10min
EDIT: get Romracer recovery from here and push that through to your phone through fastboot
Click to expand...
Click to collapse
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
firecode95 said:
Please help!!!
The phone stuck in boot screen and overheat, then restart.
In recovery mode is just black screen.
Phone has Neutrino 2.6GT+ ROM whit Clemsyn's OC kernel 1.6GHz and it has unlocked bootloader.
Can I change the kernel without booting in os or recovery?
This problem show after I was extracting very big zip file and phone overheat.
Click to expand...
Click to collapse
I am actually having this same problem.
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Just one word: Fastboot. See if Fastboot works and flash everything from there. Or, as Alterna suggested, flash through RSDLite, but that a little dangerous and can brick your phone if you don't know what you are doing. Hope it helps.
Problem sloved!!!
Alterna said:
My warranty-replacement (unrelated ear-piece failure) had 2.3.6 pre-installed. Thinking little of it, I unlocked the BL and rooted the phone as usual. After this, I tried to install a couple of the ROM's (Neutrino and Morrisoft) which I was most happy with on my previous Atrix.
After flashing either Neutrino or Morrislee's ROM, the phone hung on the M screen. Waiting approximately 30 minutes with no change, I pulled the battery.
When trying to enter recovery mode, the phone would state, "entering recovery mode..." Then go black.
I ended up using RSDLite and sbf flashing the stock 2.3.6 sbf file back to the phone. Then, I had to re-unlock the bootloader and re-root.
This never happened up to, and including 2.3.4, but did twice last night on these ROM's using 2.3.6, and I've flashed many ROM's and Kernels.
It happened to a lesser extent when trying to flash Clemsyn's stock enhanced kernel to the stock ROM, as I was able to enter recovery mode. Entering recovery mode, it would give errors: mounting cache, mounting system errors, and errors to accessing recovery and recovery log files.
Restore recovery would fail in this state, giving me the above errors as well.
Trying to mount the cache and system in recovery would fail. Trying to format cache and system then mounting these could occur temporarily, but would revert back to unmounted when a restore was attempted.
For these problems I pushed a recovery through fastboot.
Click to expand...
Click to collapse
My problem like that and I use automated unlock tool to recover recovery, this recovery show some errors but I successfully flash cwm touch and reinstall Nutrition 2.6GT+

[BOOTLOADER][MULTIBOOT + RECOVERY][BOOTMENU] Patched ICS bootloader V9 (19/07/2013)

Allright, 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://forum.xda-developers.com/showthread.php?t=1622425. There is also a post explaining nvflash in here: http://forum.xda-developers.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://forum.xda-developers.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):
Code:
bootloaderctl --set-boot-file APP:/boot/menu.skrilax
or use fastboot
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:
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)
Basically, to unbrick it, use the one to flash recovery. Then boot to the recovery, and flash working backup / ROM, whatever you like.
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://forum.xda-developers.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.zip
Wow, you found a way to boot into fastboot directly . Thank you. As for bigger logo I think that it would require to extend the space where the logo resides in bootloader file and that would require to recalculate all addresses after that area. I don't have sufficient knowledge in this area to even guess if this is possible .
This with strra , bat makes it so easy .
Thanks !!!!!!!!!!!
EDIT:
Maybe and I think it is a stupid question but anyway gonnan ask it.
I installed this and it runs fine , I can go into recovery and all but not into to fastboot ,( it says fastboot starting..............) = STUPID me need to type commands so it does sommething
And if I check my bootloader it still shows 3.01 HC ?
Do I need to flash the official leak first and then run this unlocked patch ?
I will try some different stuff , new to this nvflashing things on a tab , did it 100+ times on GPU's but never on my tab.
It pass the flash thing but then I get in red : secure boot : image LNX checksum fail !
EDIT2:
After flashing some more all is well , but still want to know what the following line means after I installed the V3 bootloader : secure boot : image LNX checksum fail !
If I check my bootloader version now it is 0.03.12-UNL and I got the Thor 1.7 recovery for ICS bootloader users running.
I can flash custom roms and all so no problems here.
Again thanks for the work !! Just a nvflash noob asking some side info !
EDIT3: Question
If I make a update .zip with only bootloader.blob and then the user runs this with the strra packages will that do the trick to make it easy to update to unlocked bootloader and custom recovery?
What I did:
See attachment ; you find what I used and your V3 is in the package , I followed the guide and links by jm77 but I used the stuff in the attachments.
Make sure you got your uid (CPUuid) so you can get your SBK. (you find this in your cwm backup folder or follow instructions from jm77 guide)
Going back to HC roms is not possible just so you know.
yaworski said:
Wow, you found a way to boot into fastboot directly . Thank you. As for bigger logo I think that it would require to extend the space where the logo resides in bootloader file and that would require to recalculate all addresses after that area. I don't have sufficient knowledge in this area to even guess if this is possible .
Click to expand...
Click to collapse
Yeah, I rewrote the fuction setting the boot mode. Well, I wasn't thinking of full screen bootlogo, just purging the other unused images and using the space for a single logo. Full logo is over 4 M.
civato said:
Do I need to flash the official leak first and then run this unlocked patch ?
I will try some different stuff , new to this nvflashing things on a tab , did it 100+ times on GPU's but never on my tab.
It pass the flash thing but then I get in red : secure boot : image LNX checksum fail !
Click to expand...
Click to collapse
We're using the HC bootloader when you communicate with nvflash (for some reason, ICS will not work). This means that after flashing, don't continue booting, just power off the tablet (as HC bootloader will fail booting on the checksums) and then power it back on.
To upgrade:
1) flash the bootloader with nvflash
2) boot to fastboot (POWER + VOLUME UP), flash CWM via fastboot
3) flash ROM via CWM
civato said:
If I make a update .zip with only bootloader.blob and then the user runs this with the strra packages will that do the trick to make it easy to update to unlocked bootloader and custom recovery?
Click to expand...
Click to collapse
No, that can't be used to install unlocked bootloader. The bootloader is checked for signature that way. Only nvflash.
Ignore this post. Quoted myself by accident.
Skrilax_CZ said:
We're using the HC bootloader when you communicate with nvflash (for some reason, ICS will not work). This means that after flashing, don't continue booting, just power off the tablet (as HC bootloader will fail booting on the checksums) and then power it back on.
To upgrade:
1) flash the bootloader with nvflash
2) boot to fastboot (POWER + VOLUME UP), flash CWM via fastboot
3) flash ROM via CWM
No, that can't be used to install unlocked bootloader. The bootloader is checked for signature that way.
Click to expand...
Click to collapse
Thanks , m8 , all went OK and works so no problems , got your V3 running and I got custom cwm .
Was just looking if it was possible to make the steps even more simple to the new users.
Can't we flash the bootloader ànd the cwm through nvflash anymore? I use a modified script from strra to flash back and forward between hc bootloader icw twrp and bootloader V2 icw the corresponding cwm.
Taptalked u see
Zatta said:
Can't we flash the bootloader ànd the cwm through nvflash anymore? I use a modified script from strra to flash back and forward between hc bootloader icw twrp and bootloader V2 icw the corresponding cwm.
Taptalked u see
Click to expand...
Click to collapse
Yes you can , I did it that way with the package I uploaded , it is strra package with this V3 in it.
Can you upload the HC bootloader for me so I can go back and fort if I want.
Skrilax_CZ said:
We're using the HC bootloader when you communicate with nvflash (for some reason, ICS will not work).
No, that can't be used to install unlocked bootloader. The bootloader is checked for signature that way. Only nvflash.
Click to expand...
Click to collapse
Could it be if we use the USB driver from the a200 ICS from Acer that is will work , communication with nvflash.
And not asking if it is possible to flash the patched bootloader with cwm.
Just a update zip with the original bootloader.blob flash it with cwm and then run nvflash to install the patched boot loader and custom recovery.
That way user won't have to download and install the whole original rom .
No, the error is in the nvflash interface in ICS bootloader itself. However it's pretty much irrelevant which bootloader you use to communicate with nvflash, if they all were working.
civato said:
And not asking if it is possible to flash the patched bootloader with cwm.
Just a update zip with the original bootloader.blob flash it with cwm and then run nvflash to install the patched boot loader and custom recovery.
That way user won't have to download and install the whole original rom .
Click to expand...
Click to collapse
Not entirely sure if I understand what you mean. If you flash original bootloader.blob with ICS, you have to have signed kernel / recovery flashed on the device. Otherwise the only way to recover from that is using nvflash. Easiest way is as I said in 1st post:
1) patched BL using nvflash
2) custom recovery with fastboot
3) ROM (or fixed boot.img for ICS bootloader)
Keep in mind, that in V2, you could only boot to fastboot via "adb reboot bootloader", POWER + VOL_UP to boot to fastboot is new in V3.
I wonder why they didn't enable OEM UNLOCK in this? Even he A510 has that capability. oh well. I'll be flashing this tonight.
THANKS!
PS. Good call on the 0.03.12-UNL version#. Thanks again!
civato said:
Yes you can , I did it that way with the package I uploaded , it is strra package with this V3 in it.
Can you upload the HC bootloader for me so I can go back and fort if I want.
Click to expand...
Click to collapse
See this post, I was looking for the same a week ago :http://forum.xda-developers.com/showthread.php?p=25175512
But I believe the bootloader.bin that is in strra's package is also the 3.01 bootloader, at least the size of the same.
Taptalked u see
Skrilax, did you check the BL in A501 latest leaks ?
Version is more recent than A500's (0.03.14-ICS), wondering what might have changed.
Oh didn't know. Rough checking by hex editor: don't see that oem unlock is enabled, and sending it through nvflash is still throwing error (just an annoyance moreless).
Skrilax_CZ said:
No, the error is in the nvflash interface in ICS bootloader itself. However it's pretty much irrelevant which bootloader you use to communicate with nvflash, if they all were working.
Not entirely sure if I understand what you mean. If you flash original bootloader.blob with ICS, you have to have signed kernel / recovery flashed on the device. Otherwise the only way to recover from that is using nvflash. Easiest way is as I said in 1st post:
1) patched BL using nvflash
2) custom recovery with fastboot
3) ROM (or fixed boot.img for ICS bootloader)
Keep in mind, that in V2, you could only boot to fastboot via "adb reboot bootloader", POWER + VOL_UP to boot to fastboot is new in V3.
Click to expand...
Click to collapse
OK thanks , didn't know about v2 as I never flashed that one.
V3 is running and doing his thing just fine .
And flashing with nvflash isn't that hard.
What I did wrong? I followed instruction and got new ICS boot v3 with fastboot, but when i try to enter into fastboot i only get text "fastboot starting ..." and nothing else.
Kh_Shad said:
What I did wrong? I followed instruction and got new ICS boot v3 with fastboot, but when i try to enter into fastboot i only get text "fastboot starting ..." and nothing else.
Click to expand...
Click to collapse
You gotta type in commands in cmd. First type fasboot devices, you will get a number or a "?" That is fine. Then you type in the commands.
Kh_Shad said:
What I did wrong? I followed instruction and got new ICS boot v3 with fastboot, but when i try to enter into fastboot i only get text "fastboot starting ..." and nothing else.
Click to expand...
Click to collapse
It doesn't print anything else (in the morning I revised it to rather say "Fastboot Mode"). Just connect it to PC and use fastboot.
civato said:
You gotta type in commands in cmd. First type fasboot devices, you will get a number or a "?" That is fine. Then you type in the commands.
Click to expand...
Click to collapse
OK so I'm pretty tech say. Lol but I'm kinda confused as to how to get to is bootloader. I don't know what nvflash is or where to find it as I have been through the links and can't find it. And just confusing with all the links and such. Could anyone PLEASE pm what I need to do exactly and links to exactly what I need. I would be forever greatful. Thank you one and all for whatever help you give me
Sent from my A500 using Tapatalk 2
warfenix said:
OK so I'm pretty tech say. Lol but I'm kinda confused as to how to get to is bootloader. I don't know what nvflash is or where to find it as I have been through the links and can't find it. And just confusing with all the links and such. Could anyone PLEASE pm what I need to do exactly and links to exactly what I need. I would be forever greatful. Thank you one and all for whatever help you give me
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
If I got time I do a wright up on the steps how I did it and with the test rom I used .
Only tip I want to give is ,if you flash the full leaked rom 1.031.00 ( same as what Acer is rolling out as ICS release now so it seems ) is to open it with winrar or 7 zip ( don't unpack ) and delete the recovery folder in it. Makes it easier on the recovery part.
And that is how I did I it.
But again I will do wright up as I understand that for some it is kinda scary to do this.

dual boot help plz'ings

Hi guys thanks again for the help with changing my boot splash that thread went epic due to that guide posted
ok so now im still on flexreaper 5.1 EX, BOOTLOADER: V7 ics
v7 supports dual boot right? i know, i know, i have read the thread but i cant actually see much info on this,
I basically want to have 2 roms , my current flex reaper and now to add the jellybean port from randomblame,.
can i do this? and how would i;
A. do this
B. select the rom i wanna use on each startup
C. would i have any prob with the itsmagic bug thing?
thanks again
You can't
I am on v8 boot loader. Dual boot is for kernels not whole roms atleast sofar
leonardtj said:
I am on v8 boot loader. Dual boot is for kernels not whole roms atleast sofar
Click to expand...
Click to collapse
damn that sucks,.... am i missing something? why would i want 2 kernals for one rom? lol cheers for reply anyways.
i think thats what us flashers "hehe" would love the most, able to try new roms without overwriting the current.
chismay said:
[...]why would i want 2 kernals for one rom?[...]
Click to expand...
Click to collapse
You could use it for custom kernel testing if you were a kernel developer (but this can be done even without flashing the kernel at all with fastboot boot command).
The main reason for dualboot in Skrillax_CZ's bootloaders, at least for now, is to allow to boot into Linux distro instead of Android without sacrificing the recovery, as earlier method for dualbooting Linux was to replace recovery image with second OS kernel. With dualboot bootloader you still have recovery and you can select the OS you want to boot.
yaworski said:
You could use it for custom kernel testing if you were a kernel developer (but this can be done even without flashing the kernel at all with fastboot boot command).
The main reason for dualboot in Skrillax_CZ's bootloaders, at least for now, is to allow to boot into Linux distro instead of Android without sacrificing the recovery, as earlier method for dualbooting Linux was to replace recovery image with second OS kernel. With dualboot bootloader you still have recovery and you can select the OS you want to boot.
Click to expand...
Click to collapse
gotchya i actually yeah see the point test a kernal without making the device unusable unless you nvflash...... im a big duuuh sometimes
@chismay: with modified bootloader you actually can do anything to boot partition without worying that you won't be able to restore it later without nvflash. Modified bootloader gives you fully usable fastboot where you can do some cool operations (all based on latest v8):
To flash any kernel to boot partition (primary kernel - usually for android):
Code:
fastboot flash boot boot.img
where boot.img is a file with kernel image with initrd.
To flash secondary kernel you can do
Code:
fastboot flash secboot kernel.img
You can of course flash new recovery with:
Code:
fastboot flash recovery recovery.img
But most of all, for testing new kernels and recoveries, you can boot any image without flashing into tab:
Code:
fastboot boot boot.img
where boot.img is any bootable image in Android format (Android kernel image, Linux kernel image or recovery image). This works by downloading the image into tablet's RAM and the booting it from there.

Windows A500 NVfash Bootloader Script

Hi Everyone
A while back I was having all sorts of problems trying to flash a patched bootloader to my Acer A500 So that I could install a custom recovery, Custom ROMS , etc...
Well thanks to some help from this awesome site, and a member here that pointed me to an NVFlash archive (Bab-Sector) with a script in it and it worked perfect. The Script however was using the V8 bootloader instead of V9, and I wanted to go with the V9 Bootloader 03.14-EXT So I updated the scripts to install the bootloader to SkrilaxCZ v9 Patched for Acer A500, and I also added Thor2002ro CWM 1.7.3 touch, instead of 1.7. 1.7.3 works a whole lot better
*****************************IMPORTANT**************************
Before using these tools make sure to back up your tablet first, and have a good ROM ready to install once you have your patched bootloader installed. Using this tool to Install the patched bootloader will render your current ROM unusable. You will have to install a new ROM as soon as your finished. This will also fix all the partitions on your tablet, so that they are all correct, but in doing it destroys your current install.
So any way here is a quick guide to flash the patched V9 bootloader file on your Acer A500:
Before you Continue:
You will need to know your SBK
And you need to have all the proper Acer USB drivers installed.
Plus you will need this file: A500-Bootloader-V9_Babsector
Extract the contents to some folder, and open the folder.
Now power off the tablet, and while it is connected to your PC via USB take a paperclip and press the reset button (located on the side next to the full size USB port, a small hole) and the power button, slowly count to 3 then release the power button, count one more to 4 and then release the reset button. Now your tablet is in APX download mode.
Open the folder where you extracted the bootloader and tools. Double click the file a501 A.bat. Enter your SBK.
The bootloader will be flashed, and Thor2002ro CWM 1.7.3 Custom Recovery will be installed, upon completion the screen will say PASS.
Now hold down the power button until the tab turns off, then hold the vol down button along with the power button to boot into CWM. Once in CWM navigate to the mounts and storage menu, then format system partition twice. Now go back to the power menu, and power off the tablet.
Now you need to boot APX download mode again, take a paperclip and press the reset button and the power button, slowly count to 3 then release the power button, count one more to 4 and release the reset button. Now your tablet is in APX download mode again.
Back to the folder where you extracted the bootloader and tools again. Now double click the file a501 B.bat.
The bootloader will be flashed again, and Thor2002ro CWM 1.7.3 Custom Recovery will be reinstalled, upon completion the screen will once again display PASS. You are finished, and you have a good custom recovery, along with the best patched bootloader for the A500.
Now you are ready to install custom ROMS from Thor2002ro CWM Touch.
If you decide that you no longer want to have the patched bootloader you can restore your A500 to complete stock ICS4.0.3 with this ROM: Stock ROM Acer_AV041_A500_1.033.00_PA_CUS1
You can flash this ROM with CWM or rename it to update.zip and place on root of external SD and the stock recovery will install it also. after the ROM has installed the tablet needs to reboot and the bootloader will be installed, then the tab will reboot, and you are back to 100% stock Acer_AV041_A500_1.033.00_PA_CUS1. You will not have root, and the bootloader will also be stock. This is the file you need if for some reason you should ever need to have your tablet sent to Acer, to be worked on. under warranty for example, or if you just want to have the tablet returned to stock.
I really hope this little guide helps someone, I know that a few months ago this would have helped me out when I could not flash my bootloader from windows with either the Black Thund3rAPX tool or AfterOTA, both of which are excellent tools, but for some reason they just would not work with my tab until after I had flashed my bootloader with NVFlash the way I explain here.
Also I need to point out that the scripts and tools included in the bootloader archive are originally the Bab-Sector tools. I just updated the bootloader files to SkrilaxCZ V9 Bootloader, with the green Acer logo, and the Custom Recovery to Thor2002ro CWM Touch 1.7.3
Thanks
- Kaiji
Omg! Thank you!
Thank you, thank you, thank you. I've been trying for two days to get a custom recovery to install. I too used Blackthund3r's tools, but nothing was working. I think my partition table was screwed. It took me forever just to get the drivers to recognize APX mode. Google's generic driver's > Acers! Again thank you so much.
KaijiKun said:
Hi Everyone
A while back I was having all sorts of problems trying to flash a patched bootloader to my Acer A500 So that I could install a custom recovery, Custom ROMS , etc...
Well thanks to some help from this awesome site, and a member here that pointed me to an NVFlash archive (Bab-Sector) with a script in it and it worked perfect. The Script however was using the V8 bootloader instead of V9, and I wanted to go with the V9 Bootloader 03.14-EXT So I updated the scripts to install the bootloader to SkrilaxCZ v9 Patched for Acer A500, and I also added Thor2002ro CWM 1.7.3 touch, instead of 1.7. 1.7.3 works a whole lot better
*****************************IMPORTANT**************************
Before using these tools make sure to back up your tablet first, and have a good ROM ready to install once you have your patched bootloader installed. Using this tool to Install the patched bootloader will render your current ROM unusable. You will have to install a new ROM as soon as your finished. This will also fix all the partitions on your tablet, so that they are all correct, but in doing it destroys your current install.
So any way here is a quick guide to flash the patched V9 bootloader file on your Acer A500:
Code:
Before you Continue:
You will need to know your SBK
And you need to have all the proper Acer USB drivers installed.
Plus you will need this file: http://www.4shared.com/zip/dbt1DsjT/A500-Bootloader-V9-Nvflash.html
Extract the contents to some folder, and open the folder.
Now power off the tablet, and while it is connected to your PC via USB take a paperclip and press the reset button (located on the side next to the full size USB port, a small hole) and the power button, slowly count to 3 then release the power button, count one more to 4 and then release the reset button. Now your tablet is in APX download mode.
Open the folder where you extracted the bootloader and tools. Double click the file a501 A.bat. Enter your SBK.
The bootloader will be flashed, and Thor2002ro CWM 1.7.3 Custom Recovery will be installed, upon completion the screen will say PASS.
Now hold down the power button until the tab turns off, then hold the vol down button along with the power button to boot into CWM. Once in CWM navigate to the mounts and storage menu, then format system partition twice. Now go back to the power menu, and power off the tablet.
Now you need to boot APX download mode again, take a paperclip and press the reset button and the power button, slowly count to 3 then release the power button, count one more to 4 and release the reset button. Now your tablet is in APX download mode again.
Back to the folder where you extracted the bootloader and tools again. Now double click the file a501 B.bat.
The bootloader will be flashed again, and Thor2002ro CWM 1.7.3 Custom Recovery will be reinstalled, upon completion the screen will once again display PASS. You are finished, and you have a good custom recovery, along with the best patched bootloader for the A500.
Now you are ready to install custom ROMS from Thor2002ro CWM Touch.
If you decide that you no longer want to have the patched bootloader you can restore your A500 to complete stock ICS4.0.3 with this ROM
Code:
Stock ROM Acer_AV041_A500_1.033.00_PA_CUS1
http://www.4shared.com/zip/R6Wn2rFJ/A500-Stock.html
You can flash this ROM with CWM or rename it to update.zip and place on root of external SD and the stock recovery will install it also. after the ROM has installed the tablet needs to reboot and the bootloader will be installed, then the tab will reboot, and you are back to 100% stock Acer_AV041_A500_1.033.00_PA_CUS1. You will not have root, and the bootloader will also be stock. This is the file you need if for some reason you should ever need to have your tablet sent to Acer, to be worked on. under warranty for example, or if you just want to have the tablet returned to stock.
I really hope this little guide helps someone, I know that a few months ago this would have helped me out when I could not flash my bootloader from windows with either the Black Thund3rAPX tool or AfterOTA, both of which are excellent tools, but for some reason they just would not work with my tab until after I had flashed my bootloader with NVFlash the way I explain here.
Also I need to point out that the scripts and tools included in the bootloader archive are originally the Bab-Sector tools. I just updated the bootloader files to SkrilaxCZ V9 Bootloader, with the green Acer logo, and the Custom Recovery to Thor2002ro CWM Touch 1.7.3
Thanks
- Kaiji
Click to expand...
Click to collapse
Nice guide Kaiji...a quick question. Do u know why babsector requires u to run both bat files. A few folks have just run the first one, done the formats then flashed their rom. Seems no one had any problems. Could u explain ( to a noob like me how babsector actually works? ??
rgds dibb
Sent from my GT-I9300 using Tapatalk 4
dibb_nz said:
Nice guide Kaiji...a quick question. Do u know why babsector requires u to run both bat files. A few folks have just run the first one, done the formats then flashed their rom. Seems no one had any problems. Could u explain ( to a noob like me how babsector actually works? ??
rgds dibb
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thanks
Actually both of those batch files are identical, I believe that the original writer wanted to be sure that any corrupted data, and or partitions were repaired. And that is exactly what they do.What happens is after the tab is in apx mode a temporary rw bootloader image is uploaded, and then the file correctly maps out and create the partitions needed for you tablet, then it uploads the bootloader, and recovery images. now with your new patched bootloader you can boot to custom recovery, install custom ROM's, and you could even install a second OS and set up a dual boot scenario, Skrilax_CZ has some really great tutorials on this here. You will also find that Blackthund3r's tools will also work now too.
- Kaiji
dibb_nz said:
; Nice guide Kaiji...a quick question....... Could u explain ( to a noob like me how babsector actually works? ??
rgds dibb
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Thank you
I am very happy that you, a senior member, actually thinks the guide is good. It really does mean a lot ( to a noob like me
I have actually just been poking around, and learning alI I can. I have always been a big fan of the Linux system, and the fact that it is now, in its Android form so huge world wide, on smartphones, and tablets everywhere is awesome!!
Any way I do really love that Android is based on the open source Linux code, and since it is, it's 100% customizable, hackable, & rewritable, sweet!!.
Oh yeah, To continue on a bit more about babsector, from my last post. The way that babsector actually works is this, while the tablet is is the NVidia APX download mode, the program NVFlash can then upload the special temporary APX mode bootloader image with rw abilities so that NVFlash can then set the partitions, and upload you patched bootloader. At least I believe that is how it all works. As I said I am just poking around, hehehe, an old linux user trying to learn all I can and then pass it on so everyone can enjoy the full potential of their devices.
- Kaiji
Not Working
KaijiKun said:
Hi Everyone
A while back I was having all sorts of problems trying to flash a patched bootloader to my Acer A500 So that I could install a custom recovery, Custom ROMS , etc...
Well thanks to some help from this awesome site, and a member here that pointed me to an NVFlash archive (Bab-Sector) with a script in it and it worked perfect. The Script however was using the V8 bootloader instead of V9, and I wanted to go with the V9 Bootloader 03.14-EXT So I updated the scripts to install the bootloader to SkrilaxCZ v9 Patched for Acer A500, and I also added Thor2002ro CWM 1.7.3 touch, instead of 1.7. 1.7.3 works a whole lot better
*****************************IMPORTANT**************************
Before using these tools make sure to back up your tablet first, and have a good ROM ready to install once you have your patched bootloader installed. Using this tool to Install the patched bootloader will render your current ROM unusable. You will have to install a new ROM as soon as your finished. This will also fix all the partitions on your tablet, so that they are all correct, but in doing it destroys your current install.
So any way here is a quick guide to flash the patched V9 bootloader file on your Acer A500:
Before you Continue:
You will need to know your SBK
And you need to have all the proper Acer USB drivers installed.
Plus you will need this file: A500-Bootloader-V9_Babsector
Extract the contents to some folder, and open the folder.
Now power off the tablet, and while it is connected to your PC via USB take a paperclip and press the reset button (located on the side next to the full size USB port, a small hole) and the power button, slowly count to 3 then release the power button, count one more to 4 and then release the reset button. Now your tablet is in APX download mode.
Open the folder where you extracted the bootloader and tools. Double click the file a501 A.bat. Enter your SBK.
The bootloader will be flashed, and Thor2002ro CWM 1.7.3 Custom Recovery will be installed, upon completion the screen will say PASS.
Now hold down the power button until the tab turns off, then hold the vol down button along with the power button to boot into CWM. Once in CWM navigate to the mounts and storage menu, then format system partition twice. Now go back to the power menu, and power off the tablet.
Now you need to boot APX download mode again, take a paperclip and press the reset button and the power button, slowly count to 3 then release the power button, count one more to 4 and release the reset button. Now your tablet is in APX download mode again.
Back to the folder where you extracted the bootloader and tools again. Now double click the file a501 B.bat.
The bootloader will be flashed again, and Thor2002ro CWM 1.7.3 Custom Recovery will be reinstalled, upon completion the screen will once again display PASS. You are finished, and you have a good custom recovery, along with the best patched bootloader for the A500.
Now you are ready to install custom ROMS from Thor2002ro CWM Touch.
If you decide that you no longer want to have the patched bootloader you can restore your A500 to complete stock ICS4.0.3 with this ROM: Stock ROM Acer_AV041_A500_1.033.00_PA_CUS1
You can flash this ROM with CWM or rename it to update.zip and place on root of external SD and the stock recovery will install it also. after the ROM has installed the tablet needs to reboot and the bootloader will be installed, then the tab will reboot, and you are back to 100% stock Acer_AV041_A500_1.033.00_PA_CUS1. You will not have root, and the bootloader will also be stock. This is the file you need if for some reason you should ever need to have your tablet sent to Acer, to be worked on. under warranty for example, or if you just want to have the tablet returned to stock.
I really hope this little guide helps someone, I know that a few months ago this would have helped me out when I could not flash my bootloader from windows with either the Black Thund3rAPX tool or AfterOTA, both of which are excellent tools, but for some reason they just would not work with my tab until after I had flashed my bootloader with NVFlash the way I explain here.
Also I need to point out that the scripts and tools included in the bootloader archive are originally the Bab-Sector tools. I just updated the bootloader files to SkrilaxCZ V9 Bootloader, with the green Acer logo, and the Custom Recovery to Thor2002ro CWM Touch 1.7.3
Thanks
- Kaiji
Click to expand...
Click to collapse
Hi Kaiji,
I tried your trick but it is not working for me. Could you please help me to solve this issue?
When i run first a501A file my tablet vibrate and went to download mode. I have attached file what exactly i get (file no. 1) and when i try to run the batch file again while tablet in download mode i get result (file no. 2). Please direct me what exactly i need to do?
Thanks
jd4r said:
Hi Kaiji,
I tried your trick but it is not working for me. Could you please help me to solve this issue?
When i run first a501A file my tablet vibrate and went to download mode. I have attached file what exactly i get (file no. 1) and when i try to run the batch file again while tablet in download mode i get result (file no. 2). Please direct me what exactly i need to do?
Thanks
Click to expand...
Click to collapse
Hmm, I wonder what the problem could be.... I would say for starters, try reinstalling the drivers, reboot, and try the script again. making sure to runit as Administrator. Also do you have AfterOTA? send me a PM after you try reinstalling your drivers, and if you are still having trouble tomorow, I will PM you my phone # and I will do my best to help you solve this over the phone.
I will be online tomorow around 12:00 noon EDT and will look for your PM and/or a reply
- Kaiji
Thanks.
KaijiKun said:
Hmm, I wonder what the problem could be.... I would say for starters, try reinstalling the drivers, reboot, and try the script again. making sure to runit as Administrator. Also do you have AfterOTA? send me a PM after you try reinstalling your drivers, and if you are still having trouble tomorow, I will PM you my phone # and I will do my best to help you solve this over the phone.
I will be online tomorow around 12:00 noon EDT and will look for your PM and/or a reply
- Kaiji
Click to expand...
Click to collapse
Thanks for your response. I appreciate it. My problem got resolved after running Acera500 flash tool.
Thanks again for your help.
jd4r said:
Thanks for your response. I appreciate it. My problem got resolved after running Acera500 flash tool.
Thanks again for your help.
Click to expand...
Click to collapse
No problem , I am very glad your problems were resolved. And, if you don't mind, I have a few questions for you.
1. What exactly went wrong in your situation?
2. Which tablet are you using?
3. And, how did you solve your problems exactly?
The reason I ask is that each tablet/software combination may each be a little unique, and the details of your experience can be very helpful to others as they encounter their own situation, and most of all we can always learn more from everyones different case, and apply that knowledge to improving the ability to help in the next case. Also, please try to be as detailed as possible, if you decide to answer the questionsI asked.
Thank you very much for your input
- Kaiji
KaijiKun said:
Hi Everyone
I really hope this little guide helps someone, I know that a few months ago this would have helped me out when I could not flash my bootloader from windows with either the Black Thund3rAPX tool or AfterOTA, both of which are excellent tools, but for some reason they just would not work with my tab until after I had flashed my bootloader with NVFlash the way I explain here.
Also I need to point out that the scripts and tools included in the bootloader archive are originally the Bab-Sector tools. I just updated the bootloader files to SkrilaxCZ V9 Bootloader, with the green Acer logo, and the Custom Recovery to Thor2002ro CWM Touch 1.7.3
Thanks
- Kaiji
Click to expand...
Click to collapse
Well it got me from only booting to APX mode to having a bootloader, but I'm still having problems. I ran the script and got the PASS screen. Now it boots to the bootloader but I'm no longer able to use the reset button to get to the APX mode. Even when I hold the reset button while powering on, it just goes to the bootloader. It also does this just powering on without press the -vol button. I'm assuming this was because I was also getting an error message say the Lnx kernel was invalid.
So I went ahead and flashed the A500-stock.zip and no longer get the invalid kernel message but it still boots to the loader menu with the options Primary (LNX), Recovery and Fastboot. But when I choose the first option it hangs on the first screen saying "Booting Android Image from LNX partition..." Revovery takes me to the recovery menu and Fastboot connect me to my PC in ADB mode.
Any suggestion about where I go from here?
4929york said:
Well it got me from only booting to APX mode to having a bootloader, but I'm still having problems. I ran the script and got the PASS screen. Now it boots to the bootloader but I'm no longer able to use the reset button to get to the APX mode. Even when I hold the reset button while powering on, it just goes to the bootloader. It also does this just powering on without press the -vol button. I'm assuming this was because I was also getting an error message say the Lnx kernel was invalid.
So I went ahead and flashed the A500-stock.zip and no longer get the invalid kernel message but it still boots to the loader menu with the options Primary (LNX), Recovery and Fastboot. But when I choose the first option it hangs on the first screen saying "Booting Android Image from LNX partition..." Revovery takes me to the recovery menu and Fastboot connect me to my PC in ADB mode.
Any suggestion about where I go from here?
Click to expand...
Click to collapse
I got APX mode working again. I had to fall back to Win 7. In Win 8 it couldn't find tthe APX driver.
So, I started from scratch and ran the A501.A bat, then formatted the /system twice. Then rebooted into APX and ran the a501.B script and got this error. "Formatting partition 2 BCT please wait... FAILED!" What now????? PLEASE HELP!!!!!
jd4r said:
Hi Kaiji,
I tried your trick but it is not working for me. Could you please help me to solve this issue?
When i run first a501A file my tablet vibrate and went to download mode. I have attached file what exactly i get (file no. 1) and when i try to run the batch file again while tablet in download mode i get result (file no. 2). Please direct me what exactly i need to do?
Thanks
Click to expand...
Click to collapse
im having the same problem as u were having with the attachments on the error codes u got can u share some light to me on the solution u was told to use
Im about at my wits end and gonna make a paper weight out of this thing I guess. I had recovered it with the Timmy Dean tool once already, and was on HC for about a week. I wanted to upgrade to ICS. So I tried to flash to bootloader but somehow got to where I can only boot into APX mode. I keep hanging on every tool I use. Here is a screen shot of the error when using the babsector in this thread. As far as I know I have the correct drivers from Acers site, but not sure about the adb drivers. I have them, but they don't "install" like the acer drivers did. How do I know they are correct? See my error attached photo. Is it possible to have something so messed up that even though apx mode works, it still wont flash itself out of the problem?
Need help with running A501 A.bat
Hi there. I put my tablet into APX mode by following the instructions above. However, when I run the A501 A.bat script, it reports that "USB device not found"
I have my tablet connected to my desktop via a USB-miniUSB cable. The connection works fine when the tablet is on, but it doesn't register it when the tablet is in APX mode
Any suggestions? Thanks!
romUser1365 said:
Hi there. I put my tablet into APX mode by following the instructions above. However, when I run the A501 A.bat script, it reports that "USB device not found"
I have my tablet connected to my desktop via a USB-miniUSB cable. The connection works fine when the tablet is on, but it doesn't register it when the tablet is in APX mode
Any suggestions? Thanks!
Click to expand...
Click to collapse
Just a couple suggestions, I would start by making sure you have a known good micro USB cable, make sure it's plugged into a USB 2.0 port directly connected to you motherboard and not a USB hub or a USB 3.0 port as those can cause problems. The last thing I would recommend is to use Windows 7. Windows 10 may or may not work with this method as this tablet is pretty old. You can use a virtual machine to run Windows 7 and it should work fine. Hopefully this helps a bit.
turnert said:
Just a couple suggestions, I would start by making sure you have a known good micro USB cable, make sure it's plugged into a USB 2.0 port directly connected to you motherboard and not a USB hub or a USB 3.0 port as those can cause problems. The last thing I would recommend is to use Windows 7. Windows 10 may or may not work with this method as this tablet is pretty old. You can use a virtual machine to run Windows 7 and it should work fine. Hopefully this helps a bit.
Click to expand...
Click to collapse
I am unable to connect directly to the motherboard, as my PC is actually a laptop, and I don't really want to try and open it up. I did manage to use a vm and try this on Windows 7 with no luck . If anyone has any other suggestions I'm all ears. The only thing that I think might be causing these issues is that I'm using a USB 3.0 port (My laptop doesn't have 2.0 ports), so I'll update this reply once I find a computer that has usb 2.0 ports.
Also, do I need to install a custom recovery before running the A500 A and A500 B scripts? Are there tutorials on how to do that? I think I ran into issues last time I tried because I hadn't unlocked my bootloader (tablet wouldn't enter recovery mode). But, if I understand it correctly, the instructions for this thread tell you how to unlock the bootloader, but it also requires the custom recovery or else you lose your stock rom. It's quite a catch 22
romUser1365 said:
I am unable to connect directly to the motherboard, as my PC is actually a laptop, and I don't really want to try and open it up. I did manage to use a vm and try this on Windows 7 with no luck . If anyone has any other suggestions I'm all ears. The only thing that I think might be causing these issues is that I'm using a USB 3.0 port (My laptop doesn't have 2.0 ports), so I'll update this reply once I find a computer that has usb 2.0 ports.
Also, do I need to install a custom recovery before running the A500 A and A500 B scripts? Are there tutorials on how to do that? I think I ran into issues last time I tried because I hadn't unlocked my bootloader (tablet wouldn't enter recovery mode). But, if I understand it correctly, the instructions for this thread tell you how to unlock the bootloader, but it also requires the custom recovery or else you lose your stock rom. It's quite a catch 22
Click to expand...
Click to collapse
Yes you need to unlock your bootloader before you can get a custom rom or a custom recovery. But to do that you need root first. Also when I said connect your USB cable directly to your mother board I meant just any USB port on your motherboard.
turnert said:
Yes you need to unlock your bootloader before you can get a custom rom or a custom recovery. But to do that you need root first. Also when I said connect your USB cable directly to your mother board I meant just any USB port on your motherboard.
Click to expand...
Click to collapse
That would still involve opening up my laptop, no? Also, I don't think that the USB cable is the issue, as I am able to connect just fine when the tablet is powered on, but not in APX mode. Also, I have tried rooting it before with a couple methods, both of which failed in one way or another. I'm open to trying out some other method(s) if you have a suggestion
Hi!
I have a similar problem like other users. Ive try many metods and I cant unbrik my A500. I dont know witch BL etc it has. Ive tried many update.zips but always without result. I can enter in apx mode but no more...
When I run A501A the I have this problem.
* Reboot your tablet into APX mode *
Generate your SBK with your CPUID from here :
Enter your SBK:0x58244C00 0x6309C006 0x2B432404 0xB0512103
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x038892484340e057
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) message: nverror:0x8 (0x19000008) flags: 0
Presione una tecla para continuar . . .
-------------------------------------------------------
I cant solve it. Can you help me please.

Root oppo A83 CPH1729 [Magisk or SuperSU]

*I am so crazy with this phone but still have a hope that one day it will be rooted
Here are the things that I have done to my phone:
Unlocked bootloader using this tool: MTKClient (it needs testpoint so almost every people cannot get through this step)
Got stock boot image
- used MTKClient to dump boot partition (need testpoint)
- or download OTA update containing image file then this tool to decrypt that OTA file oppo_decrypt_ozip by bkerler (dont need testpoint)
*Both these stock boots worked (I've tested them)
Patched stock boot.img file (because the phone has ramdisk) by Magisk with these options enabled
- Preserve AVB 2.0/dm-verity
- Preserve enforced encryption
- Patch vbmeta in boot image (because there is no vbmeta partition in this device)
Flash patched boot img
- used MTK META Ultility to enter fastboot (no need testpoint. Power the phone off. Press and hold Volume Down button, when holding that button plug in USB cable)
+ In fastboot, enter this command : fastboot flash boot after that, drop patched boot.img file into cmd console.
+ Turn on the phone again -> bootloop in orange state -> flashed stock rom then it backed to normal
- used MTKClient to write boot (needtestpoint) (but still bootloop in orange state) -> wrote stock boot.img then it backed to normal
*I have tried unticking the first 2 options (in step 3) but bootloop still existed
Hope someone can help me get over this
[Self-Solved]
This device works with SuperSU 2.78. SuperSU can be installed in newer versions but there is no root installed
Also, it works with Magisk v14.0 and Magisk Manager v5.8.2. Newer versions cause bootloop )
Now, newer versions of Magisk is under development for supporting some old devices like this device. Waiting for changes ...
Lunarx said:
Now, newer versions of Magisk is under development for supporting some old devices like this device. Waiting for changes ...
Click to expand...
Click to collapse
From this commit, I can confirm that now you can use latest Magisk version for this device. You can download this artifacts from Github Actions for experience. (It is not stable so wait for official release if you're not sure this will work)

Categories

Resources