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] ADB doesn't see MT4G in recovery/bootloader modes, bad eMMC, file system issues

First of all, hello. I'm new to tinkering with Android, but I've flashed firmware on dumbphones 68 ways to Sunday, so I'm not new to phone modding nor am I worried about technical answers, so fire away.
To start, this phone has not been rooted (yet) and has the stock 2.3.4 ROM.
I've screwed around for the last six hours or so in fear of bricking the phone only to realize I should have followed a different set of instructions after Step 1 of Downgrading in this guide, because now that I've read other guides, I find this one unnecessarily complicated compared to directly pushing PD15IMG.zip to sdcard.
Since I'm already calling it quits on going any farther with this tonight, I just need a few questions answered before I give this another shot.
1. Is ADB supposed to see the phone when it is in recovery or bootloader mode? When the phone is in recovery or bootloader, entering adb devices in the Windows Command Prompt returns an empty list of devices attached.
2. I have the bad eMMC in my phone. In addition, once in recovery mode and I press Vol Up+Power, I see an error message that says E:Can't open /cache/recovery/command. I also get additional "can't open" error messages when I select Wipe data/factory reset from the recovery menu:
Wiping data...
Formatting /data...
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Formatting /cache...
Data wipe complete...
Are those errors a concern? Are they a product of a failed eMMC or a corrupted file system? If they are because of the eMMC, would it be safe to say that I should leave this phone alone? If they are because of the file system, what I can do to fix these errors?
3. Now that I've read other, more MT4G-specific downgrading guides, will pushing PD15IMG.zip to sdcard and fastboot take care of the "can't open" errors in question 2 as well?

you need clockwork recovery if you want to flash.
You need to downgrade then root with s-off and have eng bootloader to attempt the wipes you've been trying. I just downgraded, last night, just follow the instructions. It's really easy. don't see how you can brick the phone while downgrading unless your phone dies during the flashing step.
Btw you shouldn't worry too much about the bad chip. Both good and bad have been known to brick. All bad chips aren't bad, it's only more susceptible to bricking. I have a bad chip and been flashing since forever
Sent from my HTC Glacier using XDA App

Snakecharmed said:
First of all, hello. I'm new to tinkering with Android, but I've flashed firmware on dumbphones 68 ways to Sunday, so I'm not new to phone modding nor am I worried about technical answers, so fire away.
To start, this phone has not been rooted (yet) and has the stock 2.3.4 ROM.
I've screwed around for the last six hours or so in fear of bricking the phone only to realize I should have followed a different set of instructions after Step 1 of Downgrading in this guide, because now that I've read other guides, I find this one unnecessarily complicated compared to directly pushing PD15IMG.zip to sdcard.
Since I'm already calling it quits on going any farther with this tonight, I just need a few questions answered before I give this another shot.
1. Is ADB supposed to see the phone when it is in recovery or bootloader mode? When the phone is in recovery or bootloader, entering adb devices in the Windows Command Prompt returns an empty list of devices attached.
2. I have the bad eMMC in my phone. In addition, once in recovery mode and I press Vol Up+Power, I see an error message that says E:Can't open /cache/recovery/command. I also get additional "can't open" error messages when I select Wipe data/factory reset from the recovery menu:
Wiping data...
Formatting /data...
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Formatting /cache...
Data wipe complete...
Are those errors a concern? Are they a product of a failed eMMC or a corrupted file system? If they are because of the eMMC, would it be safe to say that I should leave this phone alone? If they are because of the file system, what I can do to fix these errors?
3. Now that I've read other, more MT4G-specific downgrading guides, will pushing PD15IMG.zip to sdcard and fastboot take care of the "can't open" errors in question 2 as well?
Click to expand...
Click to collapse
are you talking about the stock recovery? because the stock recovery is supposed to say "E: can't open /cache/recovery/command". not sure why but it does. happened on every stock recovery i've seen.

Yes, I'm on stock recovery, and that's good to know that it appears to be normal.
Currently, I have successfully downgraded to stock 2.2.1 with the .86 bootloader.
Now, in following this guide, I've gotten to the end of Step 10 and I get the following:
Code:
[B]# ./gfree -f[/B]
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g899d047
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a63a4, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a6000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a63a4 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-1319315128.bin
...
Error opening backup file.
What should I do with the backup not being written?
Upon rebooting into bootloader, it still says S-ON.
Also, to back up a bit, in Step 5, I was supposed to unplug the phone from the computer and use the Android Terminal Emulator. I didn't and executed the commands through ADB because the soft keyboard input wasn't working at all in Android Terminal Emulator.
EDIT: Fixed the problem with backup not working and I now have S-OFF. The microSD card in my phone wasn't being detected properly, so instead of seeing the correct permissions d---rwxr-x with ls -l for directory /mnt/sdcard, it was being seen as read-only. When gfree attempted to write the backup to /sdcard, it failed because the SD was read-only.
I took out my 16GB card and put in my 8GB and this time, the gfree backup saved. I can't recall if I had the phone plugged in when I rebooted the phone or plugged it in afterward, but I'm slowly realized that the SD card gets remounted when you plug and unplug the phone from the computer due to the different file systems. That's why I had issues saving files to /sdcard through ADB. Now I understand why the commands were supposed to be entered in Android Terminal Emulator, but I couldn't get the soft keyboard to function in it. Hopefully, that won't be a problem after flashing the new ROM, but that will be the next concern for me.
EDIT 2: I have now installed CWM Recovery 5.0.2.0. Also, it looks like the Android Terminal Emulator developer borked the keyboard input with today's update. Read comments from October 22, 2011:
https://market.android.com/details?id=jackpal.androidterm&hl=en

remember to perm root your phone and flash the engineering bootloader i think it was like .85 something

Thanks. I had it perm-rooted and installed the engineering bootloader by the end of the weekend. I'm looking forward to flashing VU after I get some more free time and take note of settings and apps I might want to keep from the stock ROM.

your apps should be restored by google
but just in case, use titanium backup or my backup. I personally prefer my backup to backup my sms/mms, apps and settings because its quicker when you restore.
I use titanium backup to backup and restore system apps.
Oh yeah you shouldn't try to backup your settings from your stock and restore it when you flash VU, they're different OS so might cause problems. BUT it's useful when you flash new updates.
Other than VU, you might want to try TDJ's Darkside if you want to test out sense 3.5. However, i might go back to virtuous once they release a final build for sense 3.5
happy flashing

I actually didn't have any settings to back up because I haven't been using the phone as my primary phone since I bought it, but I backed up the stock Froyo ROM and flashed to VU 2.39 two nights ago. Everything appears to be running well. I reinstalled Swype 3.7 from the stock Gingerbread ROM and I still need to reinstall Genius with Button Shortcut.
I don't really like the trouble of going back and forth between ROMs, so thankfully, I'm quite pleased with VU and Sense 3.0. The rest is just customization at this point. I may eventually take a look at Virtuous Trentacinque after it goes gold, but I didn't want to wait around for it nor run a beta ROM on what will soon become my main phone. I have no problem with flashing files and making tweaks all day, but it gets old after a while and I'd rather just use the equipment instead.
So far, battery life on VU seems to be pretty good and is much better than stock. I'm enjoying the new ROM so far as well as finally getting to use the phone rather than just backing up files and testing features.

fyi, Swype 3.25 beta is out. I think Swype 3.26 beta is out too. I think there was a thread with themed Swypes somewhere. But I forget.
Sent from my HTC Glacier using XDA App

Lenovo K1 ICS **Official Release** !no g-apps!

Lenovo has released ICS for the K1. Everyone was excited until they all realized it had no gapps and no root! Lenovo has now removed the link to the file, but I uploaded it and there is a link below. If anyone can use this to do some thing AWESOME ... or just get it rooted with google apps, you will be greatly appreciated. You guys rock, and if anyone can pull this off, you guys can.
Good Luck!!
.apk
Image:
http://BillionUploads.com/6755awen3dsw
Guide:
http://BillionUploads.com/6egcpwrflirs

GAPPS:
1. Download http://goo.im/gapps/gapps-ics-20120429-signed.zip
2. Copy the file to an sd card, and rename it to update.zip
3. Power off the K1 and insert the SD card.
4. Boot up into recovery mode (press and release power, then hold volume up, I think)
5. The tablet will boot into recovery mode - it should detect the update.zip and whilst it is installing, show a progress bar.
6. When the installation finishes, a green tick will be shown and the device will power off.
7. Remove the SD card and power on.

Not working
gilberthcordova said:
GAPPS:
1. Download http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip
2. Copy the file to an sd card, and rename it to update.zip
3. Power off the K1 and insert the SD card.
4. Boot up into recovery mode (press and release power, then hold volume up, I think)
5. The tablet will boot into recovery mode - it should detect the update.zip and whilst it is installing, show a progress bar.
6. When the installation finishes, a green tick will be shown and the device will power off.
7. Remove the SD card and power on.
Click to expand...
Click to collapse
I did these steps. The K1 turns on with both LEDs on the home button lit. But then it just hangs there -- no sign of activity --- no progress bar.
BTW, to put the K1 into recovery mode you hold down the Vol Dn, Vol Up buttons and the power button until the 2 LEDs on the Home button illluminate. Note, I tried this with two different gapps-ics files (I found another one dated 20120429) here (http://goo.im/gapps/gapps-ics-20120429-signed.zip)
Ideas?

The file you are linking to is OUTDATED... there is a newer release of ICS GAPPS
http://goo.im/gapps/gapps-ics-20120429-signed.zip
gilberthcordova said:
GAPPS:
1. Download http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip
2. Copy the file to an sd card, and rename it to update.zip
3. Power off the K1 and insert the SD card.
4. Boot up into recovery mode (press and release power, then hold volume up, I think)
5. The tablet will boot into recovery mode - it should detect the update.zip and whilst it is installing, show a progress bar.
6. When the installation finishes, a green tick will be shown and the device will power off.
7. Remove the SD card and power on.
Click to expand...
Click to collapse

mjb32803 said:
The file you are linking to is OUTDATED... there is a newer release of ICS GAPPS
http://goo.im/gapps/gapps-ics-20120429-signed.zip
Click to expand...
Click to collapse
Edited, thanks!
---------- Post added at 08:14 PM ---------- Previous post was at 07:40 PM ----------
I cant flash de GAPPS, anyone can flash?

gilberthcordova said:
Edited, thanks!
---------- Post added at 08:14 PM ---------- Previous post was at 07:40 PM ----------
I cant flash de GAPPS, anyone can flash?
Click to expand...
Click to collapse
I dont Know who posted those instructions but it will never work ever. First you don't have clock work recovery on the new ics kernel it's not there. you can boot to APX and maybe work from there but don't waste your time following those instructions there garbage.

Don't get me wrong.. I'm a fan of Android!
Google OS (Android)+ Installing Google OS Major Tools (Android Market/Gmail) == FAIL!
You shouldn't need root or be a developer to install those apps!
It should be as simple as downloading and installing for the Google Play/Market. It's a simple thing like this that makes Android fail. If you're going to make it tough to do things, people will walk away. Hence, the reason it's taking hard-core developers forever to make OTA/Non-OTA releases of ICS to their devices (Not just Lenovo)...
-Cybie

I have an application that MIGHT work if I updated the gapps in it... It requires root.
Would anybody be interested in beta testing this app? My bosses boss has one of these devices, and before I muck around on his device, I want to make sure the solution works
I can probably have the app ready by tomorrow evening, if it all works out properly, again; I would require root and busybox to be installed in order for my app to work, but no recovery required. *crosses fingers*

I think that Lenovo was totally wrong in leaving all their users this way regarding the upgrade to ICS. The owe us a full upgrade with all gapps and third party.

Hi there, so I seem to have similar issues to what some have posted. I used these instructions:
//forums.lenovo.com/lnv/attachments/lnv/[email protected]/81/1/K1%20-%20Vanilla%20ICS%20Image%20Installation%20Guide.pdf
Now it just hangs when i enter recovery mode, just black screen and the two white lights on by home button.
Can anyone get me in the right direction to get this K! back to latest honeycomb? I would love ICS but the support on the web is limited and my experience so far has been bad. I am quite technical too, so this is aggravating...lol or if someone has a new Lenovo K1 ICS file with good directions, maybe i will try again. I guess before i get to that i need to get back to be able to use the thing. Its a brick right now. Win 7 does not show APX device in manager after you update the driver originally. Anyone know how i can at least get the PC to show that APX device like it originally did when i first plugged it on? Hopefully someone can help me here. I really appreciate any assistance. thank you

kaboominator said:
Hi there, so I seem to have similar issues to what some have posted. I used these instructions:
//forums.lenovo.com/lnv/attachments/lnv/[email protected]/81/1/K1%20-%20Vanilla%20ICS%20Image%20Installation%20Guide.pdf
Now it just hangs when i enter recovery mode, just black screen and the two white lights on by home button.
Can anyone get me in the right direction to get this K! back to latest honeycomb? I would love ICS but the support on the web is limited and my experience so far has been bad. I am quite technical too, so this is aggravating...lol or if someone has a new Lenovo K1 ICS file with good directions, maybe i will try again. I guess before i get to that i need to get back to be able to use the thing. Its a brick right now. Win 7 does not show APX device in manager after you update the driver originally. Anyone know how i can at least get the PC to show that APX device like it originally did when i first plugged it on? Hopefully someone can help me here. I really appreciate any assistance. thank you
Click to expand...
Click to collapse
Have you tried the AOSP build from khanning88 available here. I've been using it since its release and now updated to his R2 and it works great. You can try to re-install the APX driver. I used the one that came in the image I just pointed you to.

rurocking said:
Have you tried the AOSP build from khanning88 available here. I've been using it since its release and now updated to his R2 and it works great. You can try to re-install the APX driver. I used the one that came in the image I just pointed you to.
Click to expand...
Click to collapse
Thank you for your reply. I have yet to try that. will do so right now and give you a progress update. Below is where I am hanging:
C:\K1Image\K1_WIFI3G_ K1_A301_21_03_120607_ICS_Image\image>nvflash.exe --blob bl
ob_old.bin --bct flash_encrypt_old.bct --setbct --odmdata 0x300c0011 --configfil
e flash.cfg --create --bl bootloader_encrypt_old.bin --go
Nvflash v1.8.90246 started
Using blob v1.1.57813midt\AD8ò╔p²
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x042890804320f097
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_encrypt_old.bct
- 4080/4080 bytes sent
flash_encrypt_old.bct sent successfully
odm data: 0x300c0011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_encrypt_old.bin
\ 1393296/1393296 bytes sent
bootloader_encrypt_old.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: USP
creating partition: UDA
creating partition: TMP
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 GP1 please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 MSC please wait.. done!
Formatting partition 11 USP please wait.. done!
Formatting partition 12 UDA please wait.. done!
---------- Post added at 01:42 PM ---------- Previous post was at 01:17 PM ----------
Wow, thank you so much. I am up and running. I am so thankful. If only i could figure out these stupid image verification things. Takes me like 12 tries before i can find one that i can even read and i am pretty sure I am human...lol

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.

Boot troubleshooting

After working without a glitch for four years, my Nexus 7 (grouper) got stuck in a bootloop after I started it today. Thinking that something is probably wrong with cashe or dalvik cache I've cleared them. Now the bootloop is gone, but the device gets stuck on "Starting apps" after it finishes "optimizing" (filling in the dalvik cache). I would like to see what's going on but I have a problem doing that.
The problem is that I can't get the logcat to do the job. I've tried two "solutions" that seemed obvious, but (for some reason), none of them works.
First "solution": make a simple script and put it in /system/etc/init.d/:
#!/system/bin/sh
logcat > /sdcard/log.txt (set to 755)
I get the file, but even if I leave "Starting apps" to run for some time, when I turn off the tablet and look at the file it only has 65 lines and it still didn't finish initializing the hardware part. No information about started apps or anything. I can retrieve dmesg log from recovery but nothing interesting there as well.
Second "solution": I've tried to make it work trough init.rc, by following this https://stackoverflow.com/questions/17406209/enabling-logcat-in-init-rc (switched /cache/ to /sdcard/). But this also produces no results. Txt file is not generated at all
I don't know what I'm doing wrong.
I don't want to do a factory reset unless absolutely necessary (bunch of games with save files and other apps as well).
I can't do logcat trough adb since device is "unauthorized".
Any help is appreciated.
Thx in advance!
P.S. Using OmniROM (4.4.4)

Boot into TWRP and see if you can create or edit a text file. Reboot back into TWRP again and see if the change you made is still there. If it isn't, your flash memory has gone bad and you are in read only mode. This cant be fixed without a new motherboard. Hopefully this is not your issue.
Sent from my LGLS992 using Tapatalk

Sorry for the late reply, I was on vacation and I left the tablet at home.
The script I've mentioned was inserted trough TWRP so I think this confirms that you can write.
Also there is a log file created, as I've mentioned, it's just super short (I guess if it's in read-only mode there would be no output).