Database Users

NVidia BCT File aka Binary Configuration Table.

Hi everyone,
I'm currently working with a Devboard NVidia Tegra 250 Harmony DevKit since about a year.
I've past my year to study Tegra's architecture and comportment on high level abstraction layers, using my GNU/Linux (Debian distrib) on it.
Now I'm working to understand this board a little more deeper, and now a day, I'm facing some problem with it.
Indeed, I'm currently trying to understand what it is this Binary Configuration Table binary.
About my research, it seems to be a Firmware like which is in charge of DDR Memory controller and Bootloader call.
So, my first question is: Am I on the right way with this definition?
Secondly, why did NVidia do this crappy thing??? I mean, there is no any other company working with ARM which choose to use this thing.
I also have a TI Omap based board, and there is no such thing on it.
Well, if anyone has informations/documentations/Links, I'll be happy to read them.
I've searched about this on Google, and for now, the only interesting things that I've found are coming from TrimSlice Wiki and xda-developers forums.

BCT is more commonly referred to as Boot Configuration Table.
It contains a large number of configuration options, among them location, size and load address of the boot loader.
Have a look at the bct_dump tool in the cbootimage repository.

Many thanks for this informations.
So, basically, I've download the L4T package, and just try to replace the default fastboot.bin with my cross-compiled u-boot for Tegra250.
Unfortunatly, it's not working at all :-(
My problem is the following one:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 2
chip sku: 0x8
chip uid: 0x097c81c641816097
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: static.bct
- 4080/4080 bytes sent
static.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: uboot.bin
| 173920/173920 bytes sent
uboot.bin sent successfully
waiting for bootloader to initialize
and then, I can wait for a looooonggg time for nothing, it seems that the uboot.bin doesn't do anything while the default fastboot.bin (900kb) correctly execute the next step on the script.
Is there any trick to do to be able to have a debug output?

eppeP said:
BCT is more commonly referred to as Boot Configuration Table.
It contains a large number of configuration options, among them location, size and load address of the boot loader.
Have a look at the bct_dump tool in the cbootimage repository.
Click to expand...
Click to collapse
If that is the case, OMAP4 does have something similar, the Configuration Header. http://nishanthmenon.blogspot.com/2009/05/configuration-header-no-more-x-loader.html

eppeP said:
BCT is more commonly referred to as Boot Configuration Table.
It contains a large number of configuration options, among them location, size and load address of the boot loader.
Have a look at the bct_dump tool in the cbootimage repository[/URL].
Click to expand...
Click to collapse
-MANY MANY MANY thanks for this URL, I was looking for this software for a long time.
I've been able to read and generate new BCT with it now
But, I'm still unable to boot on U-Boot :-(
Entropy512 said:
If that is the case, OMAP4 does have something similar, the Configuration Header.
Click to expand...
Click to collapse
Yep, exactly, but basically, NVidia is less complicate in the load process but the way they handle the ROM boot and bootloader call is really crappy
I'm still investigating on my board, I really want to replace the fastboot with U-boot and push my whole system on NAND.

DR I said:
-MANY MANY MANY thanks for this URL, I was looking for this software for a long time.
I've been able to read and generate new BCT with it now
But, I'm still unable to boot on U-Boot :-(
Yep, exactly, but basically, NVidia is less complicate in the load process but the way they handle the ROM boot and bootloader call is really crappy
I'm still investigating on my board, I really want to replace the fastboot with U-boot and push my whole system on NAND.
Click to expand...
Click to collapse
Any progress on it yet ?
Sent from my HTC One X

tids2k said:
Any progress on it yet ?
Click to expand...
Click to collapse
I've made some progress, but the way NV do not share at all this kind of informations is a little bit sad :-(
I go forward step by step, I currently trying to build my own BCT based on the one provided by NVidia on it's L4T and CBootImage, but it seems to have some tricky things to know with the default BCT.
Mine is not compiling, CBootImage do not want to eat it
I'll gonna do some test tonight.
I let you inform of any evolve.

DR I said:
I've made some progress, but the way NV do not share at all this kind of informations is a little bit sad :-(
I go forward step by step, I currently trying to build my own BCT based on the one provided by NVidia on it's L4T and CBootImage, but it seems to have some tricky things to know with the default BCT.
Mine is not compiling, CBootImage do not want to eat it
I'll gonna do some test tonight.
I let you inform of any evolve.
Click to expand...
Click to collapse
thats good news, as far as with my understanding the tegra 3 follows the same chip architect and we would be able to debug with the same resources and might be able to induce a different BCT over the partial layer, thus giving access to an unsecured bootloader like UBOOT ?

tids2k said:
thats good news, as far as with my understanding the tegra 3 follows the same chip architect and we would be able to debug with the same resources and might be able to induce a different BCT over the partial layer, thus giving access to an unsecured bootloader like UBOOT ?
Click to expand...
Click to collapse
Yes, indeed, I should now be able to do that, BUT, keep in mind that you have to sign your bootloader with csign before loading it on the Tegra DevKit.
This sounds completly crazy for me because the purpose of this board, as it's named, should be to DEVEL on it and then, you need to sign your bootloader?? C'mon NVidia, this is completly nuts, I don't really know if I'll continu to support and use their DevKit, I don't have time to waste with those kind of proprietary things.
If you're also working on that kind of board, we probably should help each other

Hi everyone,
I've been granted by NVidia to access their TRM so now I should be able to perform everything I want on the board.
So, I'll retry to install the u-boot during the week-end and see what's going on when I try to load it into the board.
So far, I've not been able to put anyone of my baremetal programs into the board and u-boot neither.
Sent from my Galaxy Nexus using XDA

restore with nvflash in apx mode?

Hello,
I've done something very silly to my Nexus 7. I wanted to manually install a new boot.img via fastboot, but in haste i ran 'fastboot erase bootloader' and now it doesn't boot at all, not even the google logo.
I've read about NVflash but I don't have the partition information or other files to flash something working, though it does seem to detect the device.
Any help will be appreciated. It seems many nvidia devices have various custom tools to recover from apx mode, so hopefully something can be found for the Nexus 7 too.

You need the partitions for the 16gb or the 8gb version? I haven't done APX mode on the Nexus 7 but did on my old streak 7 and can probably pull off the files tomorrow (I have 16gb)

onilink67 said:
You need the partitions for the 16gb or the 8gb version? I haven't done APX mode on the Nexus 7 but did on my old streak 7 and can probably pull off the files tomorrow (I have 16gb)
Click to expand...
Click to collapse
That would be fantastic, I also have the 16 GB version!

So, would this mean that even when you completely kill the N7 by corrupting the bootloader, you can STILL recover?
That would be amazing.... something I'd wish my other Android devices would have, kill the bootloader on there and it's hard bricked, dead.
I'll keep an eye on this thread, this is something I am absolutely interested in as well
P.S.:
Is there a way to read / dump the required information from an N7 while it's OK and running?
Like a backup for later recovery.

If you want to try it on linux, grab the All-in-one package from here.
To get it to boot into APX mode i held all three buttons while plugging it in. To confirm it is in APX mode run lsusb and you'll see something like:
Code:
Bus 003 Device 005:[B] ID 0955:7330 NVidia Corp.[/B]
After that, assuming onilink67 can get the files, we can run something like:
Code:
./nvflash --bct nexus7.bct --setbct --bl bootloader.bin --configfile nexus7.cfg --create --go
And it may restore the bootloader.
hopefully on onilink67 can supply some better info since he already has experience with APX
Information taken from slatedroid.com, androidroot.mobi and androidroot.mobi

Subscribed! this is the exact problem i have run into. I cant get into my bootloader and device when connected.to the pc.installs a APX driver.by Nvidia
Sent from my HTC PH39100 using xda premium

OP and onilink would the files and partitions frim the 16gb be the same or would i need someone with a working 8gb to pull them for me?
Sent from my HTC PH39100 using xda premium

clago87 said:
OP and onilink would the files and partitions frim the 16gb be the same or would i need someone with a working 8gb to pull them for me?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
normally you want the one from your device since this actually copies partitions some will be different on the 8gb model

This would be great to get a working solution. I screwed mine by blowing up the bootloader on accident. Luckily I could return mine to staples. I had "some" experience with nvflash with my G2x but I couldn't get it to do much.

Yea i am unlock and on custom rom but i read somewhere asus doesnt void warranty for that. Since I'm completely bricked they shouldnt be able to see I'm on clean rom. Some wishful thinking but this does sound like something viable if i could get those filea and partitions I would definitely give it a shot before calling it quits
Sent from my HTC PH39100 using xda premium

So last time I used APX mode I had a bct file provided to me. IIRC if tegra 2 didn't like the bct file it would refuse to do anything so for the sake of my nexus I hope Tegra 3 is the same. I'm going to research this a little more and hopefully can get something to you guys soon. FYI these files are normally huge

onilink67 said:
So last time I used APX mode I had a bct file provided to me. IIRC if tegra 2 didn't like the bct file it would refuse to do anything so for the sake of my nexus I hope Tegra 3 is the same. I'm going to research this a little more and hopefully can get something to you guys soon. FYI these files are normally huge
Click to expand...
Click to collapse
Here is to Tegra 3 being a little more mature than T2 and it works for us. If not I guess I have a year to contact asus and send em my paper weight. Thanks for helping out

The commands to do the backup should be fairly easy once you're in APX mode, according to this post:
powerx86 said:
./nvflash --bl bootloader.bin --getbct --bct backup.bct --go
./nvflash -r --getpartitiontable partition.txt
./nvflash -r --read 2 part2.img
./nvflash -r --read 3 part3.img
./nvflash -r --read 4 part4.img
./nvflash -r --read 5 part5.img
./nvflash -r --read 6 part6.img
./nvflash -r --read 7 part7.img
./nvflash -r --read 8 part8.img
./nvflash -r --read 9 part9.img
./nvflash -r --read 10 part10.img
./nvflash -r --read 11 part11.img
./nvflash -r --read 12 part12.img
Click to expand...
Click to collapse
which will generate the necessary bct file, and partition info, and a backup of all the partitions.
The trouble is the bootloader.bin, I'm not sure where to get that for our device. perhaps we can back it up with adb/fastboot.

might be silly but im guessing the bootloader info isnt in the img file nakasi-jro03d-factory-e102ba72 that you can download from one of the many threads correct?

onilink67 said:
normally you want the one from your device since this actually copies partitions some will be different on the 8gb model
Click to expand...
Click to collapse
I have a (working) 8G model
adfad666 said:
The commands to do the backup should be fairly easy once you're in APX mode, according to this post:
which will generate the necessary bct file, and partition info, and a backup of all the partitions.
The trouble is the bootloader.bin, I'm not sure where to get that for our device. perhaps we can back it up with adb/fastboot.
Click to expand...
Click to collapse
Amazing, I am going to try that ASAP!
clago87 said:
might be silly but im guessing the bootloader info isnt in the img file nakasi-jro03d-factory-e102ba72 that you can download from one of the many threads correct?
Click to expand...
Click to collapse
There is a bootloader.img in that download, I am fairly sure that's the one - not to be confused with the boot.img, which is the kernel AFAIK.
// EDIT
Narf, don't have a proper USB cable with me (at work ATM) so I gotta wait till home in about 9 or 10 hours :-/
nvflash must be used in Linux, right? There is no Windows tool for that?

I did the same thing... don't know what i was thinking. Was trying to get back to stock rom and now this... *sigh. If you guys manage to find a way would be most appreciated. I'm new to this APX stuff so been randomly trying to backup and restore just the bootloader provided by google. Haven't had any luck. It's either unknown device errors, and i haven't been able to find out the SBK either. Total bummer... I'm assuming that we'll be in the clear after restoring the bootloader?
HellcatDroid said:
I have a (working) 8G model
Amazing, I am going to try that ASAP!
There is a bootloader.img in that download, I am fairly sure that's the one - not to be confused with the boot.img, which is the kernel AFAIK.
// EDIT
Narf, don't have a proper USB cable with me (at work ATM) so I gotta wait till home in about 9 or 10 hours :-/
nvflash must be used in Linux, right? There is no Windows tool for that?
Click to expand...
Click to collapse

Maybe we need a nvflash version that supports the N7 or something.... where did the nvflash that's been linked to above come from?
We could ask nVidia for one.
Then again, I think this nvflash thing work with/for the Tegra CPU, so as long as it's provided with the proper input files it shouldn't be device specific - altough on that linked to page they had to use a custom binary to get things started....

Use the nvflash from the nvidia driver package, found here:
The ones floating around for various devices don't work, but I was able to get some responses from my device with that one.
Now I've hit another problem: I've been trying various things on my device, and now I can't get it into APX mode. In Windows the device connected sound constantly repeats, so I think I've drained the battery, and plugging it into the charger doesn't seem to charge it :/
Looks like I'll have to send it back...

Reading through this it seems there is a great deal of more information / data / files we need before we actually can use nvflash in PAX mode....
In order to get a working (e.g. --create) nvflash, we need a few bits of information as well as some files:
Secure Boot Key
BCT file (boot device setup, ram configuration and a bit more)
ODM data (board-specific bit-field specifying various board settings. *Needs* to be correct
flash.cfg (e.g. list of settings and names/identifiers of partitions.
Click to expand...
Click to collapse
The last thing ("flash.cfg") should be easy, I think it can be extracted / generated from a working device ("./nvflash -r --getpartitiontable partition.txt" should/could be it), but as for the rest....
adfad666 said:
Use the nvflash from the nvidia driver package, found here:
The ones floating around for various devices don't work, but I was able to get some responses from my device with that one.
Click to expand...
Click to collapse
Cool, thanks for that link, going to check it.
adfad666 said:
Now I've hit another problem: I've been trying various things on my device, and now I can't get it into APX mode. In Windows the device connected sound constantly repeats, so I think I've drained the battery, and plugging it into the charger doesn't seem to charge it :/
Click to expand...
Click to collapse
Yeah, the actual charging is handled by the kernel in LPM (low power mode), and it obviously needs a workgin bootloader to boot the kernel into LPM :-/

Here's a good description of the BCT/ODM, http://projects.pappkartong.se/a500/
Secure Boot Key - I don't think we need that as our bootloader is not locked / encrypted like other devices, though I could be wrong.
BCT file can be pulled from the device
ODM data can be pulled from the BCT
flash.cfg can be generated with ABX once you have the BCT.

[Q] TF101 has 16GB after flashing instead of 32GB

Hi Everyone,
after experiencing the reboot problem and then acceidentaly bricking the tablet I managed to unbrick my tablet (or better a friend managed).
Now though, the storage is 16GB instead of 32GB
My question now: how can I get the tablet back to 32GB?
Thanks for the help

I think you probably need to update either the transformer.bct file or odmdata for the 32gb version. I *believe* that these set things like memory size and other hardware parameters, although I'm not sure which one controls what. Unfortunately, I don't know where you would find these either. Maybe if you ask nicely and ask the right people at ASUS, they might send it to you.
EDIT- It's probably the bct. I forgot there is a getbct command in nvflash- you could ask someone who has a working 32gb version to extract theirs and see if it works for you. Note there are no guarantees that this will work since nvflash might not be fully implemented on the tf. You'll probably need to get comfortable with the command line. Prepackages scripts and one click solutions will probably not work in this case.
Code:
--getbct
reads back the BCT from mass storage
--setbct
updates the chip specific settings of the BCT in mass storage to
the bct supplied,used with --create, should not be with --read,and
--format(delete)_all,format(delete)_partition,--download, and--read
http://androidroot.mobi/technical/tf-secure-boot-key/
Code:
In order to get a working (e.g. --create) nvflash, we need a few bits of information as well as some files:
Secure Boot Key
[B] BCT file (boot device setup, ram configuration and a bit more)[/B]
ODM data (board-specific bit-field specifying various board settings. *Needs* to be correct
flash.cfg (e.g. list of settings and names/identifiers of partitions.

So I can't just re-flash nvflash with the proper settings? just seems a bit easier
On another note, does anybody have a working bct file? :fingers-crossed:

I think the proper settings are in the bct file.

Thanks for the help. I have found in other sources that it seems to be indeed in the bct file, so that is confirmed
Unfortunatly, that is all I could find out till now
I am sort of stuck on now getting a bct file for a TF101 with 32GB. Either that, or I am not copying it over properly. I am sort of at a lost here. I would appreciate any help

[Q] A500 will not Factory Reset

I'm having an odd problem with my A500, and while I've seen people with some of the symptoms I'm having, I haven't yet found anyone with all of them. I would appreciate any advice you all may have.
I purchased my A500 on the day it came out, so it's long out of warranty. Everything has been fine with it until two nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts, usually starting with Watchdog (the app killer I use), followed by calendar storage, and then a number of others. At that point, any app I opened would crash. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. I tried to factory reset but holding volume up, holding the power button, and continuing to hold volume up while switching the screen lock. The screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", nothing happens. The button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice?

Princepapa said:
I'm having an odd problem with my A500, and while I've seen people with some of the symptoms I'm having, I haven't yet found anyone with all of them. I would appreciate any advice you all may have.
I purchased my A500 on the day it came out, so it's long out of warranty. Everything has been fine with it until two nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts, usually starting with Watchdog (the app killer I use), followed by calendar storage, and then a number of others. At that point, any app I opened would crash. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. I tried to factory reset but holding volume up, holding the power button, and continuing to hold volume up while switching the screen lock. The screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", nothing happens. The button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice?
Click to expand...
Click to collapse
Well, first guess, you have corrupted data somewhere in one of the partitions (/System or /Data). I'm guessing /System as the issue continues after a factory reset, which is "supposed" to wipe the /Data partition.
I'll assume you are stock and un-rooted? Running stock ICS?
The first thing I would do, is while the tab is still running, get your UID number.
First goto Settings/Developer Options, and turn on USB Debugging.
Then go to the Development forum, and check the sticky about how to get your UID number. Should be a simple app you run from your PC while tab is connected. Write it down and save it somewhere (just in case)

Moscow Desire said:
Well, first guess, you have corrupted data somewhere in one of the partitions (/System or /Data). I'm guessing /System as the issue continues after a factory reset, which is "supposed" to wipe the /Data partition.
I'll assume you are stock and un-rooted? Running stock ICS?
The first thing I would do, is while the tab is still running, get your UID number.
First goto Settings/Developer Options, and turn on USB Debugging.
Then go to the Development forum, and check the sticky about how to get your UID number. Should be a simple app you run from your PC while tab is connected. Write it down and save it somewhere (just in case)
Click to expand...
Click to collapse
Thanks for the help!
Yes, I'm running stock, unrooted Android version 4.03.
I've installed blackthund3r's A500 Manager, and it detects my tablet, but it when I try to get my CUPID I get the error "system/bin/sh: su: not found".
I've downloaded "Afterota lite", but hesitate to use it because it says "USE WITH OTA ANDROID SYSTEMS ONLY" and I have no idea if that applies to me or not.
I'm assuming I'm ok to use it, but I don't want to take any chances.

Princepapa said:
Thanks for the help!
Yes, I'm running stock, unrooted Android version 4.03.
I've installed blackthund3r's A500 Manager, and it detects my tablet, but it when I try to get my CUPID I get the error "system/bin/sh: su: not found".
I've downloaded "Afterota lite", but hesitate to use it because it says "USE WITH OTA ANDROID SYSTEMS ONLY" and I have no idea if that applies to me or not.
I'm assuming I'm ok to use it, but I don't want to take any chances.
Click to expand...
Click to collapse
Since the 17th I have exactly all the same problems that you describe!!! I also have the same configuration. Did you may have also the following:
Current Image Version:
Acer_AV041_A500_1.062.00.EMEA_DE?
I did not find a solution so far. But I was able to recover the CUPID - not with the A500 Manager (A500Manager1.1.1) - that did not work. But by retrieving the acer_cpu_id from a file. I did it with adb tools and found it here:
/sys/firmware/fuse/acer_cpu_id
I have been able to get into APX mode (with blackthund3r_A500_APX_Flash_Tool_v0.4.1), but could not flash a new image. I could not get root (with ICS Root 7.2.0), by any method that I tried.
By every operation that I do - it always starts with the same app's and version that I had before. It seems like an "read only" system.
Hope you could solve that problem in the mean time.
Mratlan

Mratlan said:
Since the 17th I have exactly all the same problems that you describe!!! I also have the same configuration. Did you may have also the following:
Current Image Version:
Acer_AV041_A500_1.062.00.EMEA_DE?
I did not find a solution so far. But I was able to recover the CUPID - not with the A500 Manager (A500Manager1.1.1) - that did not work. But by retrieving the acer_cpu_id from a file. I did it with adb tools and found it here:
/sys/firmware/fuse/acer_cpu_id
I have been able to get into APX mode (with blackthund3r_A500_APX_Flash_Tool_v0.4.1), but could not flash a new image. I could not get root (with ICS Root 7.2.0), by any method that I tried.
By every operation that I do - it always starts with the same app's and version that I had before. It seems like an "read only" system.
Hope you could solve that problem in the mean time.
Mratlan
Click to expand...
Click to collapse
I'm sorry to hear that you have the same problem, though I'm kind of glad I'm not alone here.
My Image Version is: Acer_AV041_AA500_RV05RC01_PA_CUS1
"Read only" is a great description of this, in fact, I'm received errors indicating that it's a read only file when trying to resume my previous place in a video that I have saved on my SD card.
So you have not been able to get it to factory reset using external tools either?

Princepapa said:
I'm sorry to hear that you have the same problem, though I'm kind of glad I'm not alone here.
My Image Version is: Acer_AV041_AA500_RV05RC01_PA_CUS1
"Read only" is a great description of this, in fact, I'm received errors indicating that it's a read only file when trying to resume my previous place in a video that I have saved on my SD card.
So you have not been able to get it to factory reset using external tools either?
Click to expand...
Click to collapse
Correct. I could not do:
- a factory reset
- root the tablet
- use recover to make a downgrade
I try to write a new image with blackthund3r_A500_APX_Flash_Tool_v0.4.1. But it is very slow.
Hope we get some good idea's what else we could try.
Mratlan

Mratlan said:
Correct. I could not do:
- a factory reset
- root the tablet
- use recover to make a downgrade
I try to write a new image with blackthund3r_A500_APX_Flash_Tool_v0.4.1. But it is very slow.
Hope we get some good idea's what else we could try.
Mratlan
Click to expand...
Click to collapse
How slow is "very slow"? If it works, I'd be willing for it to take a long time...unless "very slow" means a few percent per day.

Princepapa said:
How slow is "very slow"? If it works, I'd be willing for it to take a long time...unless "very slow" means a few percent per day.
Click to expand...
Click to collapse
Well, I do not know. I had to start again, because I forgot to disable energy saver. Hence during the process there was a stop and I was forced to start again. So my estimation would be several hours (4-8h?).But I’m not sure if it will work.

If you try it again, please let me know how it goes. I probably won't be able to work on mine again until this weekend. I'm also going to continue to research other solutions, though it seems not many people have had this problem, and not many people have ideas for solutions...

Princepapa said:
If you try it again, please let me know how it goes. I probably won't be able to work on mine again until this weekend. I'm also going to continue to research other solutions, though it seems not many people have had this problem, and not many people have ideas for solutions...
Click to expand...
Click to collapse
The flash process (with blackthund3r_A500_APX_Flash_Tool_v0.4.1) did not come to an end.
I tried the following method as descriped here:
http://forum.xda-developers.com/showthread.php?t=2450119&highlight=formatting+partition+bct+failed
But without sucess - but at least I know now a bit more detail about the problem:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0xCFA21E00 0xA8838901 0x47CA6D03 0xXXXXXXX
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c6187426094d7
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
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x4 (0x4) flags: 0
Drücken Sie eine beliebige Taste . . .
Maybe you check this on your tablet as well.

HI all,
Sorry to hear that you have problem with your tab!!
happy to hear that you have exactly the same problem than me and others (see this http://forum.xda-developers.com/showthread.php?t=1790958)
I had made all possible test that i can
AFterota, Blackthun3er ,method, badsectros,fastboot, nvflash command......all failed to write the tab!!!!

gerardpuducul said:
HI all,
Sorry to hear that you have problem with your tab!!
happy to hear that you have exactly the same problem than me and others (see this http://forum.xda-developers.com/showthread.php?t=1790958)
I had made all possible test that i can
AFterota, Blackthun3er ,method, badsectros,fastboot, nvflash command......all failed to write the tab!!!!
Click to expand...
Click to collapse
Uhhh, that sounds not very good. At the moment I try EUU tool, but it seems also not working. So, did you give up on the tablet?

a500 nvflash formatting partition error - solution

I created an account here just to post this.
For a long time I have been try to fix my a500. About a year ago it was attached to my wall. One day I turned it on after having been away for a while and it was broke. I tried to reset it, but saw the dead droid, then got stuck at the acer screen.
For 2 straight days I tried to fix the issue. I learned more than I care to know about nvflash, "babsector", blackthunder, and jimmydean or whoever. I had lots of nvflash issues. Everyone said you could just solve all your problems with it but I kept getting
Code:
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 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: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: specified partition is invalid or does not exist (code: 7) message: nverror:0x42008 (0x6042008) flags: 0
...or some other similar nvflash error. I put the tablet away (as I began to go crazy) for about 4 months. 3 days ago I took it out again. Again I tried messing with nvflash ... I got very close to loading an ICS ROM on but it would never boot. At some point I got stuck in APX mode and nvflash wasn't working... again same error.
Today I had a breakthrough
I was searching through results for the BCT error in Google that I had not clicked before when I came across a Russian site with the following comment:
"There was a problem:
"Formatting partition 2 BCT please wait ... FAILED!!!
Replies (except carry screenplay) is not found, he decided to try it myself.
turned to revive in the following way:
make out about 24 hours warmed hairdryer (took my wife) motherboard within 30 minutes, collected and made ​​UnBrick. All went well until the works)) I do not know what helped warm or disable the battery on the day.
luck and ATP for UnBrick."
Fortunately Google translate provided me with this translation, as my Russian isn't very good. The post made me remember putting hard drives in the freezer to make them work just long enough to get data off them.
I took my a500 and put it in the freezer. After a few hours I tried nvflash again... same issue. So I figured cold didn't work I should try heat like my Russian comrade. I turned my oven to 200 degrees (F). I put the tablet in for 20 minutes. When I took it out I could barely hold it due to the heat. I plugged it in and ran nvflash... IT WORKED!
...at least long enough to get past the BCT partition. Then it gave another error. I restarted into recovery (which now worked) and loaded my ROM. (twrp couldn't load my sdcard so I had to load the ROM from USB mounted as sdcard). The rom installed went through and booted into ICS!
tl;dr; - If you are having trouble with nvflash and you suspect hardware failure put your a500 in the oven @ 200 deg F for 20 minutes. I call this the Russian sauna technique.

Oven method works also for me!!
Just to confirm that I had exactly the same problem, my A500 was stuck in APW mode and I have tried during hours all the methods (babsector, blackthunder), and I get all the time ' FAILED msg because of bad data' At the end, I put desesperatly the A500 in oven for 20 minutes (90 degres Celcius (or 200 ° F) and tried again the flashing and it's works! (Actually, I tested the 'Russian method' twice because one day after I wanted to upgrade in Ice Cream and brick again the device (the first time of brick was for an unknow reason (no root, no play with it before)

What facing?
83li190 said:
Just to confirm that I had exactly the same problem, my A500 was stuck in APW mode and I have tried during hours all the methods (babsector, blackthunder), and I get all the time ' FAILED msg because of bad data' At the end, I put desesperatly the A500 in oven for 20 minutes (90 degres Celcius (or 200 ° F) and tried again the flashing and it's works! (Actually, I tested the 'Russian method' twice because one day after I wanted to upgrade in Ice Cream and brick again the device (the first time of brick was for an unknow reason (no root, no play with it before)
Click to expand...
Click to collapse
As I am having this exact same error, I thought I'd ask, before trying so resolder the entire thing in an oven... were you screen-up or screen-down?

Hi,
I also have same issue. Tried almost all method. None of them working. I am trying since long time. I just read this article. Its sounds like odd to putting tablet in microwave for 20 minutes. Are you guys kidding or it really works? How to put tablet in oven up side or down side?

Heat to reflow the solder
jd4r said:
Hi,
I also have same issue. Tried almost all method. None of them working. I am trying since long time. I just read this article. Its sounds like odd to putting tablet in microwave for 20 minutes. Are you guys kidding or it really works? How to put tablet in oven up side or down side?
Click to expand...
Click to collapse
No no no! Not a microwave, that will just make a mess of everything! A conventional oven, so that the heat softens the old (presumably poorly done) solder points, fixing broken connections,

eldarion27 said:
No no no! Not a microwave, that will just make a mess of everything! A conventional oven, so that the heat softens the old (presumably poorly done) solder points, fixing broken connections,
Click to expand...
Click to collapse
Thanks for your reply. Can you please send me any photos or stuff which shows me that what needs to be taken off after open up the tablet. i mean which parts need to be foiled and put in oven. That would be great and it will help me to get this done. Again i really appreciate your respond.
Thanks.

Successfully Baked! (No, in the oven)
jd4r said:
Thanks for your reply. Can you please send me any photos or stuff which shows me that what needs to be taken off after open up the tablet. i mean which parts need to be foiled and put in oven. That would be great and it will help me to get this done. Again i really appreciate your respond.
Thanks.
Click to expand...
Click to collapse
As per the earlier comments in this thread, 200 degrees for 20 minutes. Pre-heating is advised, so that you don't overshoot-then-cool. I baked it in the case, screen down, on something that would stay flat and not get too hot itself (I used a wooden cutting board). There are threads talking about higher temps and shorter times, but you'd have to remove the mobo and only bake that piece, or the heat would destroy several other components.
I went ahead and baked mine last night. Due to some futzing around, and fat-fingering Linux commands, it was several minutes before I got the flash started... the flash got through the BCT formatting, but failed when installing into the BCT a couple of minutes later (by which time the device had noticeably cooled).
I re-baked it tonight, got the flash running considerably quicker afterwards, and it successfully completed and launched into Android. How long that'll last I can't say, but for now I'm going to let it cool and see what comes of it.

eldarion27 said:
As per the earlier comments in this thread, 200 degrees for 20 minutes. Pre-heating is advised, so that you don't overshoot-then-cool. I baked it in the case, screen down, on something that would stay flat and not get too hot itself (I used a wooden cutting board). There are threads talking about higher temps and shorter times, but you'd have to remove the mobo and only bake that piece, or the heat would destroy several other components.
I went ahead and baked mine last night. Due to some futzing around, and fat-fingering Linux commands, it was several minutes before I got the flash started... the flash got through the BCT formatting, but failed when installing into the BCT a couple of minutes later (by which time the device had noticeably cooled).
I re-baked it tonight, got the flash running considerably quicker afterwards, and it successfully completed and launched into Android. How long that'll last I can't say, but for now I'm going to let it cool and see what comes of it.
Click to expand...
Click to collapse
Thanks for your respond. You put in oven about 20 minute with 200 degree temperature? You said you put on wooden board with case. Do we just put without removing any part? I am confusing that what part should remove from tablet and than put or just put it without removing cover and anything.

Same problem no recovery....NV Flash?
Thanks for the Hot Russian tip.
Where did you download nvflash from because I tried to get t from an XDA thread but the given nflash HTML & the vache for cpu ID converter sites did not appear to work. I was only able to download the Batch.RAR file. Or do I need all these files? Perhaps NVFLASH is all that is required to unbrick my A500 tablet.