Database Users

[GUIDE] Backup of your BCT AND Partition with NVFLASH on the gtab

** UPDATED WITH .BCT saving, include USB as well as NVFLASH just copy in
** 1 dir, run the batch and keep those you may need them one day
** Read the batch file for more info
It is clear for me is that it is not a perfect solution to use nvflash with images that you do not know the source.
The tegra S.O.C. use the information from a file stored in partition#2 to configure some low level setting like flash memory chip speed, total memory installed, video memory installed, flash type etc. As an example, if for some reason a batch of tablet is built with more memory then the .bct files will need to be changed accordingly
It is already confirmed that there's at least 2 different type of hardware. (2 different images by bekit do not use the same .bct configuration)
When flashing after a full wipe after using the create command, nvflash read the .bct configuration files and store it in the partition #2 on the tablet, bct files are created by the manufacturer using a tool from nvdia called buildbct. They are not writen during regular nvflash (where the partition are not re-created)
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched).
This batch files will work under windows and will not modify your tablet in anyway
please make sure you use the nvflash tools that is 151K there's an older and smaller one in some package, it will output binary inside the partition.txt instead of plain text. The version 2 include everything you need to backup the device under windows
Thanks to the various poster of thread about nvflash for the correct command THEY did the hard work not me !
To Restore individual partition the command is
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
this will not work for partition below 4
P.S.
I am not trying to start a debate on the validity of the current recovery (thumb-up to the guy who offered those!) They are valid for MOST device however
if you do have a different device this will alleviate any issue that may happen with nvflash restore.
see 2 post below for full restore info

Hi,
I know that the partitiontable shows a partition named "BCT", but is there also something else, perhaps flashed into the SOC itself that is referred to as "the BCT"?
The reason for the question is that nvflash has a setbct and a getbct command, separate from the read and download commands, which work with the partitions.
Jim

Reserved
(will be completed a bit later)

so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??

10roller said:
so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??
Click to expand...
Click to collapse
My guess is yes, the platform of the ac100 laptop by toshiba is tegra based and they do it!

P00r said:
The set bct command probably write the 4080 byte to the partition named bct in the cfg, I have yet to test flashing a dummy FF filled partition with the command to confirm the flash.bct get writen there
So in fact when you restore with the nvflash restore images from bekit I think you are actually writing it twice... (it is in the image and you telling the nvflash to create it) but I have not confirmed this yet
Once the bct info is there, the SOC read his configuration there, as well as the ODM info, I have not found a way to use --getbct that reads back the BCT from mass storage yet...
I am not sure either why there's so many section being flashed it should work with only a few of those (I plan to test this) since nvflash is simply puting those one after the other. It make sense only sense for a dual booting unit
Click to expand...
Click to collapse
Hi,
I was able to get --getbct to output a 2048 byte file awhile ago. I think I had posted about it, but, sorry, I don't remember which thread. The only thing I vaguely remember was that I had to use some unobvious combination of parameters. Also, I think that it only worked right after pushing the bootloader.bin. If I find my post, I'll provide a link.
Jim

Thanks OP, I like the idea of being able to back up the partitions directly from my tablet so I know I'm restoring the proper thing should I ever have to resort to that.
Just starting to get into modding this thing after it showed up from Woot yesterday, been planning on buying one for quite some time to compliment my Epic 4g and when the woot sale dropped I had to jump on it. So far all I have done is flash clockwork, and make a nandroid backup with that. Also doing this backup method now.
So have you actually done a successful restore using this method?

so is it possible to back up your original hardware configuration and restore it when you got problems???

Yes and NO, I have error reading partition #11 (system) on my tablet (bad block)
if I use it as is for restore, it doesn't restore and boot, however replacing this partition with clockwork system.img backup give me back a full working tablet.
I can also reboot into recovery and restore from there.

Letters and numbers oh my
I ran the backup on my new replacement GTab yesterday. I had a size mismatch on partition 5, everything else backed up properly. Also, my partition 7 is BLO and partition 6 is MSC. Thanks for the script and capability.
Mike

P00r said:
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched). I will post later on how to flash back those if someone request it...
Click to expand...
Click to collapse
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.

iamchocho said:
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.
Click to expand...
Click to collapse
You can flash back the partition using
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
If needed you can use the nvflash format kit prior to restoring however it would be better to use your own .bct with that option

Getting stuck at partition 7.

xkwwwx said:
Getting stuck at partition 7.
Click to expand...
Click to collapse
What is the error you are getting ?

stock recovery image
Thank you very much for the sharing this.
Now I have 10 img files (part-2 to part-11)... wich one is the stock recovery image? I did this before installing clockwork mod...
Thanks!

I think this is fantastic. Gives us a chance to backup our gtab before deciding to try a new rom. I tried this today in the hopes to backup and then install the flashback HC rom. But unfortuntaly it stopped on image 7, as xkwwwx has also mentioned. The message seemed to be a issue with the size expected of the image as to what was received. Ill try and copy the message.
"nvflash.exe" -r --read 7 part-7.img
nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
At that point it stops, and i have to control c to exit the batch file. Id love to be able to backup with this pls, so i can try another rom, and know i can use this to return to this rom if i dont like the new one, any chance this can be resolved pls ?
Was also wondering if some form of GUI maybe of benifit, i know alot of people feel wary of NVFlash, perhaps with a GUI people would feel more comfortable using it. Maybe a simple screen with a backup and restore set of buttons ?

P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.

Icedvoco said:
P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.
Click to expand...
Click to collapse
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)

P00r said:
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)
Click to expand...
Click to collapse
Bad blocks may be common, but bad blocks in the exact same spot probably not. I get the exact same thing:
"nvflash.exe" -r --read 7 part-7.img
Nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
Any other thoughts on this?

Maybe someone here knows,
So with NVflashing, I've found only one file that has the alternative BCT (it's a tnt1.0 rom on BL1.1) and no other NVflash file sets work without causing a APX bootloop.
This is the NVflash file set that works for me http://db.tt/FvSeAZj
Ive read it was made when someone was trying to configure for the hardware variations.
Now is it possible to take my backup and insert just the files needed into another NVflash file set?

[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?

Iconia Tab Update Enhancement APK

Heya, I have an engineering sample A500 with 2.2 froyo installed and am trying to update it. Putting a decrypted update.zip on an sd card and booting into recovery doesn't work. It shows a progress bar for a few secs and then nothing else. Can someone with the Application.apk send it my way or post it here? I can't find it anywhere and 2.2 doesn't have the Play store. I'm also unable to install it to another device as they are unsupported devices. I'm hoping this will allow me to upgrade to something usable and then go from there. Thanks for the help.
Android Build : Acer_Picasso_0.008.01_EMEA_GEN1_DEMO
Bootloader : 0.03.01-HC
-iNT0XiC8D

Well after a couple days of trying everything I enabled USB mounting with windows and it said the volume needed formatted. Let it format and then had an 8GB volume. After coping some apk's to try I rebooted and now it seems Android 2.2 is gone and there is a blank screen after the acer boot logo. Any ideas? Can I nvflash a full rom directly as a block device or something? JTAG/ISP, SPI, I2C, ect?

I dnt understand smthing ... 5 hrs ago u asked for apk and 1 hr ago u had your tab formated and thres nutting?
sent from sgs3 -stock 4.3 open europe rom
---------- Post added at 07:46 AM ---------- Previous post was at 07:42 AM ----------
Imo you shoud download EUU package and try to unbrick your tab.
sent from sgs3 -stock 4.3 open europe rom

uglyjohny said:
I dnt understand smthing ... 5 hrs ago u asked for apk and 1 hr ago u had your tab formated and thres nutting?
sent from sgs3 -stock 4.3 open europe rom
---------- Post added at 07:46 AM ---------- Previous post was at 07:42 AM ----------
Imo you shoud download EUU package and try to unbrick your tab.
sent from sgs3 -stock 4.3 open europe rom
Click to expand...
Click to collapse
They'll be nutting after I get this thing fixed. I don't understand that there are 127 views and no one can share an apk from their tablet. That apk probably wouldn't have helped anyway. Am I supposed to wait around for it to magically fix/hack itself or keep trying things? I tend to keep trying things and I thought I explained in enough detail what I was doing. Never would have thought that enabling usb sharing would have caused it to wipe out the OS too.

In two posts you stated two diferent things. If you cnt boot up your tab no apk will help you. If you can boot download aptoide apk and install playstore and google services and ill send you enhecment apk. If you cnt boot up as your internal memory was wiped out as stated by you than try EUU package.
sent from sgs3 -stock 4.3 open europe rom

uglyjohny said:
In two posts you stated two diferent things. If you cnt boot up your tab no apk will help you. If you can boot download aptoide apk and install playstore and google services and ill send you enhecment apk. If you cnt boot up as your internal memory was wiped out as stated by you than try EUU package.
sent from sgs3 -stock 4.3 open europe rom
Click to expand...
Click to collapse
Yes I thought updating the original thread was better than starting a new one.
EUU and nvflash got me in the right direction. Flashing EUU didn't unbrick (still at Acer logo). I was able to find a procedure that worked though and can create a guide if anyone is interested. Engineering samples seem to be different than retail units. CPUID and SBK are completely unneeded and will cause current (retail) utils to fail.
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0XXXXXXXXXXXXX (masked my info)(this was the same ID AfterOTA captured from 2.2 froyo)
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 1
-iNT0XiC8D

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.