Database Users

[HOWTO] Backup data partition with dd and restore with nvflash

Hi,
I didn't want to use nandroid and titanium since I wanted all my /data partition saved (which includes /sdcard) exactly as it is (icons and widget location, sdcard content, etc.).
I finally managed to find a unix way to do it, using dd and nvflash.
I've used an usb external drive to store the data partition (around 14G), and you'll need to be root.
First, open a terminal, cd to your external drive and as root, type :
dd if=/dev/mmcblk0p7 of=data.img
It will save an ext4 image of all your datas.
You can loop mount it if you want to check :
/system/xbin/mount -o loop data.img
Then the script below will restore your entire partition, which is handy when you want to test a new rom without wiping your
data, and with the insurance that your system will be exactly the same (including the icons and widget location in
your home display) :
#!/bin/sh
./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A
43EA 0xA532EEB6 0xECFE1D98 --sync
sleep 1
./nvflash --resume --rawdevicewrite 821760 6728960 data.img
./nvflash --resume --sync
It works for me straightforward. However, if you come to play with this, and it doesn't work, just reflash your tf with a custom rom.
I never managed to brick my tf, thanks to the nvflash tools. Seems unbrickable.

why is your NumSectors=6728960? Mine is 7017728.
7017728 sectors is about 13.7GB,and 6728960 sectors is about 13.14GB.
I don't think it is machine specific.

I think it was the number buried in flash.cfg or transformer.bct

i
i think maybe someone used a format tool.. is my best guess

[Solved] Flash ICS BL stuck on NvError 0x120002

I am following Civato's guide to install ICS Boot Loader. I place the Acer tab in APX mode manually. I run the following.
./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x04DD1E00 0xA76D0000 0xE727E402 0xE8502103 --sync
And, I get stuck at "failed executing command 25 NvError 0x120002" etc. (I am using nvflash on Linux.) At that point: The Acer tablet screen is lit up with "acer" logo in yellow, "Acer Iconia APX mode" written in the top-left (landscape) corner in tiny font. On Linux PC, you see "Nvflash started\n[resume mode]\n" and then just hangs. Cannot even kill the process. Disconnecting the USB cable kills the nvflash process. Acer tablet remains in the same state (yellow logo, power led lit white). Here are the last few lines from the above cmd.
Code:
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (code: 14) message: nverror:0x4 (0x4) flags: 0
Luckily, the tablets boots as it did before this failed procedure. What is it that I am doing wrong?

It means your NAND has been hosed, and basically, she's a brick on life support (via the bootloader). Why are you installing manually, may I ask?
Sadly, it may be time to order a new one? Unless the bootloader has an option rewrite the partition table (and start fresh), I doubt she would be of much use.

Some other folks had the same issue in the past.
Basically most of them ran an EUU to stock 3x. It should reset the partitions. Believe they ran TimmyDeans tool which comes with the EUU.
Then they were able to update the bootloader as per the guides.
MD

There is no need to use whole EUU. But in this state you still need to run --create command to fix this, which will format whole internal storage. Copying all data from storage to PC and making nandroid backup is adviceable.
This could be an eMMC failure but also it could be just a messed up data in the partition table.

Hi I haved the same error like you and I used the TimmyDeans tool.
it seams we have some mestup partition sheme that is fixed only when the system is formated again.
So my recomendation is to folow the steps and Ihope soon to be runing ICS with new bootloader
http://forum.xda-developers.com/showthread.php?t=1723608

My A500 now has V8 BL
Thanks to the replies fromNIxana, yaworski, Moscow Desire, I was able to successfully flash V8. On the Linux PC, I was in the root-3.2.1/Image/ dir. Copied flash.cfg to flash8.cfg. Made the following changes to flash8.cfg: for partition 4, filename=bootloader_v8.bin, and for partition 6, filename=recovery_twrp_2.1.3-ICS.img . The shell line I succeeded with was
./nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash8.cfg --bl bootloader.bin --sbk 0xSBK0 0xSBK1 0xSBK2 0xSBK3--create --go
If I had system.img etc. for an ICS ROM I would have dared to replace their names also in flash.cfg. Without these, the above installs a ROM from the root-3.2.1 pkg of TimmyDean.
My experience differs quite a bit from what was reported in http://forum.xda-developers.com/showthread.php?t=1723608. Hence the changes to flash.cfg

@pmateti: you can also remove filename attribute from other partitions leaving only the changed ones for EBT and SOS partitions. Then you just enter recovery and flash any rom you want without the need to wipe anything.

I realized that I could have removed the filename=... line for any partition that did not need to be re-loaded. Thanks

[GUIDE] How to enter APX mode or Bootloader menu

When failing to get into APX mode or bootloader-recovery menu try the following suggestions.
Good Luck!
You will find the bootloader info below the apx section!
Special thanks to wha2do and daws for their input!
wha2do has posted a similar guide that provides detail not found here! Please see his guide and give proper thanks if you find his guide helpful!
http://forum.xda-developers.com/showthread.php?p=36159253#post36159253
How To Enter APX
1. To enter APX mode you either have to boot, choose reboot (if available) and hold volume up pressed until it reboots and then the screen should remain black. Or if that doesn't work, completely shutdown your tablet and wait a second or two and then hold volume up pressed while pressing power on and keep it pressed until screen is blank.
or
2. fastboot -i 0x0B05 reboot (hold volume up)
or
3. adb reboot (hold volume up)
or
4. with unit powered on hold volume up and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
or
5. su
reboot -hold volume up.
This is done using a terminal; Android terminal is free from the play store.You must be rooted for this to work.
or
Only 6. if there is no other resort!
6. remove cover from unit, disconnect battery, press and hold volume up, reconnect battery!
or
7. Another way:- Provided by daws
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.
You should now be in APX mode.
Works every time for me.
Thanks for the help daws.
Click to expand...
Click to collapse
How To Enter bootloader – recovery menu
1. To enter recovery menu you either have to boot, choose reboot (if available) and hold volume down for pressed until it reboots and then the recovery menu appears. Or if that doesn't work, completely shutdown your tablet and wait a second or two and then hold volume down pressed while pressing power on and keep it pressed until recovery menu.
or
2. fastboot -i 0x0B05 reboot hold volume down
or
3. adb reboot hold volume down
or
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
or
5. su
reboot -(hold volume down).
This is done using a terminal; Android terminal is free from the play store.You must be rooted for this to work.
or
Only 6. if there is no other resort!
6. remove cover from unit, disconnect battery, press and hold volume down, reconnect battery!
or
7. Another way:- Provided by daws
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume down and then connect USB cable to PC.
or - no need to hold volume with these
8. adb reboot bootloader
or
9. fastboot -i 0x0B05 reboot-bootloader
or
10. from terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
Note 1: If you are on ICS or have nvflash installed some of the commands presented in this post may not work; possibly 8, 9, and 10 - THANKS TO wha2do for this info!
Note 2: adb commands are available while in twrp 2.3+; if this fails update your version of adb and try again.
Note 3: as you go through different processes to recover you may gain or loose access to any of the suggestions in this post so try them again as you progress.

Another way:-
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.
You should now be in APX mode.
Works every time for me.

daws said:
Another way:-
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.
You should now be in APX mode.
Works every time for me.
Click to expand...
Click to collapse
Thanks for the info. I hadn't thought of that one. I'll add it to the guide.
:good:

daws said:
Another way:-
Power off the tablet and don't touch the power button again.
Connect USB cable to tablet but not to PC yet.
Press volume up and then connect USB cable to PC.
Wait a few seconds before releasing volume up button.
You should now be in APX mode.
Works every time for me.
Click to expand...
Click to collapse
Thanks for this. I spent hours trying to boot apx mode and this is the only way that worked. Thanks a million
Sent from my Nexus 7 using xda app-developers app

I've heard APX/NVFlash doesn't actually work in the most recent stock releases. Do you know what this actually works on and if you can actually do anything if you get into APX?

NeoMatrixJR said:
I've heard APX/NVFlash doesn't actually work in the most recent stock releases. Do you know what this actually works on and if you can actually do anything if you get into APX?
Click to expand...
Click to collapse
Nvflash can only be installed while on ICS and APX mode is useless unless you have installed Nvflash.
Once Nvflash is installed you can use ICS (android 4.0) or JB (android 4.1) rom.
I'm speaking of Nvflash and APX as they relate to the TF300T.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ASUS TF300T Bricked
Hello tobdaryl ,
For my bad luck i wiped everything on my ASUS TF300T (FastBoot --> FLash ALL).
I cant access the Recovery menu (Power + VOL Down), so no FastBoot commands,,,
I can access the APX mode (Power + VOL up)
The Tablet starts and shows the ASUS logo only.
I have searched the WEB but with no SUccess, any advices Please how to Flash a Recovery on it to UnBrick it?
Thank you,
Nader H.AL-Dirany

NaderALDirany said:
Hello tobdaryl ,
For my bad luck i wiped everything on my ASUS TF300T (FastBoot --> FLash ALL).
I cant access the Recovery menu (Power + VOL Down), so no FastBoot commands,,,
I can access the APX mode (Power + VOL up)
The Tablet starts and shows the ASUS logo only.
I have searched the WEB but with no SUccess, any advices Please how to Flash a Recovery on it to UnBrick it?
Thank you,
Nader H.AL-Dirany
Click to expand...
Click to collapse
I flashed recovery on my tablet a few minutes ago.
I'm assuming here that you have nvflash installed.
wheelie -r --blob blob.bin
nvflash --resume --download 5 ProperRecoveryForYourBootloader.img - this file can also be blob.
nvflash --resume --go

not wokring
Hey,
I have the same exact problem as Nader H.AL-Dirany, when I try to run these commands I get the following message.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\1337>c;
'c' is not recognized as an internal or external command,
operable program or batch file.
C:\>cd wheelie
C:\wheelie>wheelie -r --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
unknown option -- r
Usage: wheelie [options] --bl <bootloader file> --bct <bct file>
Argument Description
-v or --version Display version information
-h or --help Display this menu
-1 or --sbkv1 Use wheelie for SBKv1 devices
-2 or --sbkv2 Use wheelie for SBKv2 devices
-s or --sbk Set SBK for devices not officially supported by wheelie
-o or --odm set the odmdata (Required for operation.) Example: 0x300
d8011
--bl or --bootloader Set the bootloader filename (required for operation)
-c or --bct Set the BCT filename (required for operation)
Please help, my tablet has been locked for 6 months ;(

boomingshot said:
Hey,
I have the same exact problem as Nader H.AL-Dirany, when I try to run these commands I get the following message.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\1337>c;
should be: C:\Users\1337>c:
just a typo - I increased the size of type to make obvious - my tired old eyes missed it the first time also
C:\wheelie>wheelie -r --blob blob.bin
should be: wheelie --blob blob.bin
wheelie does not use the -r option - nvflash uses either -r or --resume
unknown option -- r
Usage: wheelie [options] --bl <bootloader file> --bct <bct file>
Please help, my tablet has been locked for 6 months ;(
Click to expand...
Click to collapse
Good Luck!
I hope this helps.

Info:
I just realized something - 6 months - are you using flatline?
These instructions are for nvflash not flatline!
I have not yet investigated flatline.

Not to be a smartass, I'm a huge noob and appreciate all your help
But, when I try it I get the following error
I'm assuing that blob and bl are the same thing, I tried the following wheelie --bl blob.bin. is that the same thing
Thanks sooo much for your time:highfive:
-----
C:\>cd wheelie
C:\wheelie>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
unknown option -- blob
Usage: wheelie [options] --bl <bootloader file> --bct <bct file>
Argument Description
-v or --version Display version information
-h or --help Display this menu
-1 or --sbkv1 Use wheelie for SBKv1 devices
-2 or --sbkv2 Use wheelie for SBKv2 devices
-s or --sbk Set SBK for devices not officially supported by wheelie
-o or --odm set the odmdata (Required for operation.) Example: 0x300
d8011
--bl or --bootloader Set the bootloader filename (required for operation)
-c or --bct Set the BCT filename (required for operation)
-----
---------- Post added at 08:14 PM ---------- Previous post was at 08:10 PM ----------
tobdaryl said:
Info:
I just realized something - 6 months - are you using flatline?
These instructions are for nvflash not flatline!
I have not yet investigated flatline.
Click to expand...
Click to collapse
never heard of flatline, could that be another potential recovery option?
so far only APX mode works on my tablet, all the rest is inaccessible
I downloaded the latest firmware from asus and copied blob (no extension only called blob) file into the wheelie folder like instructed.
I tried the command I say I would in my last post and it didnt work. I tried the following wheelie -bl blob and got this prompt.
C:\wheelie>wheelie --bl blob
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using NO SBK.
Using bootloader: 'blob'.
Using BCT: '(null)'.
----------------------------------------
[=] Chip UID: 0x98254853062001158
[-] Incorrect SBK or SBK type selected. nverror: 0x4.

boomingshot said:
Not to be a smartass, I'm a huge noob and appreciate all your help
But, when I try it I get the following error
I'm assuing that blob and bl are the same thing, I tried the following wheelie --bl blob.bin. is that the same thing
Thanks sooo much for your time:highfive:
-----
C:\>cd wheelie
C:\wheelie>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
unknown option -- blob
Usage: wheelie [options] --bl <bootloader file> --bct <bct file>
Argument Description
-v or --version Display version information
-h or --help Display this menu
-1 or --sbkv1 Use wheelie for SBKv1 devices
-2 or --sbkv2 Use wheelie for SBKv2 devices
-s or --sbk Set SBK for devices not officially supported by wheelie
-o or --odm set the odmdata (Required for operation.) Example: 0x300
d8011
--bl or --bootloader Set the bootloader filename (required for operation)
-c or --bct Set the BCT filename (required for operation)
-----
---------- Post added at 08:14 PM ---------- Previous post was at 08:10 PM ----------
never heard of flatline, could that be another potential recovery option?
so far only APX mode works on my tablet, all the rest is inaccessible
I downloaded the latest firmware from asus and copied blob (no extension only called blob) file into the wheelie folder like instructed.
I tried the command I say I would in my last post and it didnt work. I tried the following wheelie -bl blob and got this prompt.
C:\wheelie>wheelie --bl blob
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using NO SBK.
Using bootloader: 'blob'.
Using BCT: '(null)'.
----------------------------------------
[=] Chip UID: 0x98254853062001158
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Click to expand...
Click to collapse
Everyone was new at some point. Not a problem except I'm not helping when I give a wrong answer.
wheelie -r --blob blob.bin - not wheelie --r --blob blob.bin
is the proper command; I just proved it on my own tablet.
blob.bin is one of the files generated by nvflash
your command C:\wheelie>wheelie --bl blob is flashing a complete blob - I don't know what blob file you had in the directory.
Contents of a blob:
blob.PT - partition table
blob.APP - system.img
blob.LNX - boot.img
blob.SOS - recovery.img
blob.EBT - bootloader.bin
It is probably best to stick to the commands as presented.
We are trying to flash the blob.bin file you saved from your nvflash install.
Formatting is not working properly on XDA at the moment so I have no idea how this will look or read.

tobdaryl said:
Everyone was new at some point. Not a problem except I'm not helping when I give a wrong answer.
wheelie -r --blob blob.bin - not wheelie --r --blob blob.bin
is the proper command; I just proved it on my own tablet.
blob.bin is one of the files generated by nvflash
your command C:\wheelie>wheelie --bl blob is flashing a complete blob - I don't know what blob file you had in the directory.
Contents of a blob:
blob.PT - partition table
blob.APP - system.img
blob.LNX - boot.img
blob.SOS - recovery.img
blob.EBT - bootloader.bin
It is probably best to stick to the commands as presented.
We are trying to flash the blob.bin file you saved from your nvflash install.
Formatting is not working properly on XDA at the moment so I have no idea how this will look or read.
Click to expand...
Click to collapse
What version of wheelie are you using? Would you mind putting it on mediafire or something? In my version, which I thought to be the latest, wheelie -r is not an available option
I only have these ones
Argument Description
-v or --version Display version information
-h or --help Display this menu
-1 or --sbkv1 Use wheelie for SBKv1 devices
-2 or --sbkv2 Use wheelie for SBKv2 devices
-s or --sbk Set SBK for devices not officially supported by wheel
-o or --odm set the odmdata (Required for operation.) Example: 0x
d8011
--bl or --bootloader Set the bootloader filename (required for operation)
-c or --bct Set the BCT filename (required for operation)

boomingshot said:
What version of wheelie are you using? Would you mind putting it on mediafire or something? In my version, which I thought to be the latest, wheelie -r is not an available option
I only have these ones
Argument Description
-v or --version Display version information
-h or --help Display this menu
-1 or --sbkv1 Use wheelie for SBKv1 devices
-2 or --sbkv2 Use wheelie for SBKv2 devices
-s or --sbk Set SBK for devices not officially supported by wheel
-o or --odm set the odmdata (Required for operation.) Example: 0x
d8011
--bl or --bootloader Set the bootloader filename (required for operation)
-c or --bct Set the BCT filename (required for operation)
Click to expand...
Click to collapse
My version is identical to yours.
[email protected]:~/Code/Nvflash-ICS$ ./wheelie -r --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
My tablet was not connected as it is in use.
Presently I have two pcs available - Ubuntu Linux and Mac OS X Lion - no windows.
Here is my list of options from Linux.
[email protected]:~/Code/Nvflash-ICS$ ./wheelie --h
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Usage: wheelie --blob <blob file>
Argument Description
-v or --version Display version information
-h or --help Display this menu
-b or --blob Specify blob file to use
As you see I have less listed than you have but the version is the same.
Some have had issues with certain usb ports and others with windows in general.

I followed every steps and this tablet is not working, I'm seriously thinking about using it as my new Frisbee.
I'll right down all the stuff I did, so you can point where what I did wrong
1- Download Firmware From Asus Website
2- Download Wheelie/NVFLASH from
androidroot.mobi/pages/guides/tegra3-guide-nvflash
For TF300:
androidroot.mobi/download/tf300_nvflashpack.zip
3- Then the NVFlash program dosent even show the same option, I tried a different version of NVFLash and it want working either

boomingshot said:
I followed every steps and this tablet is not working, I'm seriously thinking about using it as my new Frisbee.
I'll right down all the stuff I did, so you can point where what I did wrong
1- Download Firmware From Asus Website
2- Download Wheelie/NVFLASH from
androidroot.mobi/pages/guides/tegra3-guide-nvflash
For TF300:
androidroot.mobi/download/tf300_nvflashpack.zip
3- Then the NVFlash program dosent even show the same option, I tried a different version of NVFLash and it want working either
Click to expand...
Click to collapse
You left out blobtools to extract partitions from your stock blob. It is unimportant at this moment with your other issues.
It will be a while or maybe tomorrow but I think I can borrow a windows laptop. I'll give it a try and report back.
I have a neighbor who has been very helpful in this respect. I do provide some help with his androids and laptop.
windows compiled blobtools - http://forum.xda-developers.com/show...0&postcount=24

tobdaryl said:
You left out blobtools to extract partitions from your stock blob. It is unimportant at this moment with your other issues.
It will be a while or maybe tomorrow but I think I can borrow a windows laptop. I'll give it a try and report back.
I have a neighbor who has been very helpful in this respect. I do provide some help with his androids and laptop.
windows compiled blobtools - http://forum.xda-developers.com/show...0&postcount=24
Click to expand...
Click to collapse
Thank you very much, keep me updated, I'm going to start playing with blob tools.

boomingshot said:
Thank you very much, keep me updated, I'm going to start playing with blob tools.
Click to expand...
Click to collapse
Here are my results with windows.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
E:\Develop\Nvflash-ICS>wheelie --help
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Usage: wheelie --blob <blob file>
Argument Description
-v or --version Display version information
-h or --help Display this menu
-b or --blob Specify blob file to use
E:\Develop\Nvflash-ICS>wheelie -r --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
This time without the -r
E:\Develop\Nvflash-ICS>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
This is with windows 7 pro.
Both with the -r and without work on this pc.
There are three usb ports - one is usb2 and two are usb3 and all function the same.
I have used this laptop to restore my tf300t to stock ICS in the past. Tonight I just plugged in my usb drive and used the files left after my previous use.
Try all usb ports.

Hello!
A few days ago I tried to root my Asus TF300T because before that, I changed the lcd and the touchscreen from FPC-1 to G01 version. So I had to root and update touchscreen's firmware to 02-3011-4820.ekt. I already updated with last firmware from asus.com. First, I installed a TRWP recovery but was useless since the touchscreen doesn't worked. So I tried to rewrite CWM recovery. I reset it and I don't remember exactly if I begun to install or not CWM but when I tried to wipe data (Vol- + Power), the tablet has freezed. After a few minutes I did a hardware reset (pin hole). Since that, the tablet freeze with "Device Unlocked", Asus logo and nVidia. The device was already unlocked. I don't have any backup from it. No fastboot, no adb. Just APX mode. Is it possible to do something with it anymore? I tried BootTools2, extracted bloobs from last version of firmware, tryed to flash them with nvflash and wheelie but vainly. What is the next step? I'm a beginner!
Thank you in advance!

How to install recovery/bootloader/Linux

Thought that I had figured this out, but not quite I guess. I'm trying to flash a custom ROM. Running stock a500 with the ICS OTA update. Running Ubuntu 12.10 on my laptop. Didn't realize how difficult this would be. Despite a bunch of reading, I'm still confused as to what I should be doing. I think that my mixing and matching files is hurting me here...
It appears that the only way to do this is manually with NVFlash. I had a difficult time finding the appropriate file. For those wondering, it's an official nvidia file, and there is a linux specific version. Here's the link I used.
I followed a couple of different guides, none of which worked.
Started here. Couldn't get past the first nvflash command after realizing that I didn't have any of the bin files. OK, found this guide, which appears to have the most up to date bootloader, and I think all the other files I need--none of the other guides included bct.bct, and flash.cfg, which I think are necessary (someone please correct meif I'm wrong). The "V8-UNL-ICS-HC-bootloader-MULTI-cwm" package on the first page is what I used.
So this thread is windows-centric, but looking at the v8.bat file I think pointed me in the rightish direction.
I first ran this command:
Code:
sudo ./nvflash --bct bct.bct --setbct --bl bootloader_v8.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x59DBC201 0xDB60F601 0xDB0F1203 0xAE0A2103 --sync
and got this error:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0428000741ff3357
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_v8.bin
| 1191932/1191932 bytes sent
bootloader_1_v8.bin sent successfully
waiting for bootloader to initialize
bootloader status: success (code: 0) message: flags: 1073848316
bootloader failed NvError 0x0
command failure: bootloader download failed
Ok, an aside: what exactly am I doing in this step? I initially thought that I was flashing the bootloader, but that doesn't appear to be the case (looks like that's later). Tried finding out what the arguments meant for the nvflash command, but couldn't figure it out. Anyway, noticed another bootloader.bin file in the directory. Tried the above command using "bootloader_apx.bin" (Edit: Rereading the .bat file, looks like I was supposed to use the apx file initially anyway) Success, I think.
Code:
sudo ./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x59DBC201 0xDB60F601 0xDB0F1203 0xAE0A2103 --sync
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0428000741ff3357
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: bct.bct
- 4080/4080 bytes sent
bct.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader_apx.bin
| 714981/714981 bytes sent
bootloader_apx.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Next step:
Code:
sudo ./nvflash -r --format_partition 4
Nvflash started
[resume mode]
Formatting partition 4 please wait.. done!
So formatting partition 4, which is where the bootloader lives I guess.
Code:
sudo ./nvflash -r --download 4 ./bootloader_v8.bin
Nvflash started
[resume mode]
sending file: ./bootloader_v8.bin
| 1191932/1191932 bytes sent
./bootloader_v8.bin sent successfully
OK.
Code:
[CODE]sudo ./nvflash -r --format_partition 6
Nvflash started
[resume mode]
Formatting partition 6 please wait.. done!
OK again.
sudo ./nvflash -r --download 6 recovery_thor17_403.img
Nvflash started
[resume mode]
sending file: recovery_thor17_403.img
\ 5074944/5074944 bytes sent
recovery_thor17_403.img sent successfully[/CODE]
And,
Code:
sudo ./nvflash -r --go
Nvflash started
[resume mode]
At this point, I rebooted...and ended up stuck in apx mode.
So I d/l'd the package from Moscow Desire in this thread, repeated the steps, and my tab came back.
I don't remember if I tried getting directly into the bootloader, but I had the "rom manager" program on my desktop. I was able to boot into recovery and backup my ROM.
Next time I tried using vol down + power to get into bootloader (or using rom manager to get back into recovery) I ended up with a dead android image.
So while typing up this post, I redid the steps using v8. Everything appears to have went well. I get a "Skrilaz bootloader v8/booting primary kernel image" message, and it boots normally. I can enter recovery using vol + + power. Bootloader still gives me a dead android though.
I didn't do:
Erase boot.p file. Wasn't sure if this was necessary or not. Since I see the v8 bootloader message, I'm guessing not.
If nothing jumps out at anyone, could this be a hardware problem? Of note, before I started messing with this, I tried getting into the bootloader via vol -/pwr, and got the dead android there too.
EDIT: Oops, looks like I'm entering the bootloader menu after all by using vol +/pwr. So recovery is my problem now. Getting closer...

nola mike said:
I didn't do:
Erase boot.p file. Wasn't sure if this was necessary or not. Since I see the v8 bootloader message, I'm guessing not.
If nothing jumps out at anyone, could this be a hardware problem? Of note, before I started messing with this, I tried getting into the bootloader via vol -/pwr, and got the dead android there too.
EDIT: Oops, looks like I'm entering the bootloader menu after all by using vol +/pwr. So recovery is my problem now. Getting closer...
Click to expand...
Click to collapse
Wot rom did u start off with?
The boot.p file. If it's there u must rename or delete it, else it will just keep
Overwriting yr newly flashed custom cwm with the stock Acer recovery, this
is the dead android you mentioned.
No, u have no errors which point to the h/w fault.
The process is this...
Check boot.p file and rename - need root
1. Flash v8 and cwm
2. Boot directly to cwm
3. Flash rom
4. Full data wipe recommended
5. Reboot
So re flash cwm with nvflash again and flash yr rom...that should be it!!
Also, rom manager does not support our tab, would recommend not using it.
Once u have the v8 you can use Acer recovery installer instead.

Finally got it working.
I ended up getting the "acer recovery" program from the play store, which worked fine. My backup plan was to try to install one of the recovery zip files through the bootloader rather than through apx. I tried all 4 of the bootloaders through apx without success.
Another note: I ended up stuck in apx mode again, but was able to get out of it just by re-starting the process--I was able to just flash v8 rather than reverting back to the v3 packages. Hopefully this will help some of you linux folks. I guess I can summerize what actually worked for me (all the links are in the above post):
1. Download nvflash (linux version)--I don't remember if I needed to change permissions for this, but make sure it's executable
2. Find your CPUID and SBK (instructions for this are elsewhere; basically go to a terminal emulator, type dmesg | grep androidboot.serialno. On mine, grep wasnt recognized as a command, so I did dmesg>dmesg.txt, opened dmesg.txt with an editor and searched for androidboot.serialno)
3. Download V8-UNL-ICS-HC-bootloader-MULTI-cwm and unpack. Copy nvflash to this folder.
4. Place your tab in apx mode: Turn off, plug microusb port to computer, hold in reset button, press power x 3 sec, release power button, wait 1/2 sec, release reset button. dmesg on your computer should show something like this:
Code:
[146408.156075] usb 1-4: new high-speed USB device number 42 using ehci_hcd
[146408.288787] usb 1-4: New USB device found, idVendor=0955, idProduct=7820
[146408.288797] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[146408.288803] usb 1-4: Product: APX
[146408.288808] usb 1-4: Manufacturer: NVIDIA Corp.
5. Replace your sbk where indicated
Code:
sudo ./nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk YOURSBK --sync
6.
Code:
sudo ./nvflash -r --format_partition 4
7.
Code:
sudo ./nvflash -r --download 4 ./bootloader_v8.bin
YMMV on steps 8 and 9. Although everything said it worked on mine, it didn't. I'm thinking at this point that it's because I didn't delete the boot.p file, though I didn't think that was necessary using a patched bootloader.
8.
Code:
sudo ./nvflash -r --format_partition 6
9.
Code:
sudo ./nvflash -r --download 6 recovery_thor17_403.img
10.
Code:
sudo ./nvflash -r --go
Again, at this point I bailed somewhat and installed acer recovery from the play store, and it was able to install a recovery without me doing anything else. I'm now running CM 10.1/Jelly bean 4.2.1.
I actually forgot to do a system wipe (wiped dalvik though) before installing that ROM, but it's running great so far, and kept all my data. Sweet. Hopefully this will save somebody some time...

dibb_nz said:
Wot rom did u start off with?
The boot.p file. If it's there u must rename or delete it, else it will just keep
Overwriting yr newly flashed custom cwm with the stock Acer recovery, this
is the dead android you mentioned.
No, u have no errors which point to the h/w fault.
The process is this...
Check boot.p file and rename - need root
1. Flash v8 and cwm
2. Boot directly to cwm
3. Flash rom
4. Full data wipe recommended
5. Reboot
So re flash cwm with nvflash again and flash yr rom...that should be it!!
Also, rom manager does not support our tab, would recommend not using it.
Once u have the v8 you can use Acer recovery installer instead.
Click to expand...
Click to collapse
Thanks, the boot.p file was the conclusion that I eventually reached, but since I got it working through acer recovery I didn't try deleting/reflashing again. I don't remember which recovery loaded rom manager. Through acer recovery I flashed TWRP 2.1.3, which is a pretty slick program. BTW, I started with a completely stock tab running the ICS OTA update.

[Q] A500 bricked, tried update.zips, several EUUs, and using nvflash

Hey everyone,
It is important to note that my tablet is and always was stock, I never had any custom ROMs or root or anything, though I am not entirely sure what version of Android I was running (pretty sure it was Honeycomb, as I only upgraded the version once, a couple years ago).
So about a week ago my tablet would get stuck in the Acer logo screen when booting up, and I tried using my microSD card and recovering probably 10 different update.zip files, with no luck.
I then tried several EUU programs, after obtaining my CPUID / SBK through Ubuntu, but all of them have failed on me. They give the failure screen, and when I hit retry it just gets stuck at about 10% of the progress bar and doesn't move (for hours). See attached screenshots.
I have also tried using Nvflash, and several of the BAT files (root-3.2.1-v4 and V8-UNL-ICS-HC-bootloader-MULTI-cwm), as well as running the Nvflash commands that they use manually. And also tried running the command in Ubuntu.
The errors that I get using Nvflash: (note, though the screenshots attached are from using one of the bat files, I get the same errors when running the Nvflash commands manually)
1.) Even though the tablet succesfully boots into bootloader mode (green acer logo with some text in the upper left), I do get an error after running the following command:
nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x_my_sbk --sync
"bootloader downloaded succesfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0"
2.) When trying to format the partitions manually, after getting into the bootloader using the commands manually from that BAT file, I get:
nvflash -r --format_partition 4
"formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x120002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0"
Partition 6 doesn't work either
At this point, I can still get my tablet into APX mode (tempermentally), but it won't boot up normally anymore to the Acer logo, and none of the other button combinations work to boot into recovery (power button and volume), or erasing cache (volume button and other volume, letting go of volume and moving the lock back and forth).
Does anyone have any advice? I am tempted to just try the oven method and formatting the partitions again, as I feel like I have exhausted most of the software options. If anyone has access to the "badsector" program, that would be very helpful as well.
Thanks so much, I know its a long read!

Nimbility said:
Hey everyone,
It is important to note that my tablet is and always was stock, I never had any custom ROMs or root or anything, though I am not entirely sure what version of Android I was running (pretty sure it was Honeycomb, as I only upgraded the version once, a couple years ago).
So about a week ago my tablet would get stuck in the Acer logo screen when booting up, and I tried using my microSD card and recovering probably 10 different update.zip files, with no luck.
I then tried several EUU programs, after obtaining my CPUID / SBK through Ubuntu, but all of them have failed on me. They give the failure screen, and when I hit retry it just gets stuck at about 10% of the progress bar and doesn't move (for hours). See attached screenshots.
I have also tried using Nvflash, and several of the BAT files (root-3.2.1-v4 and V8-UNL-ICS-HC-bootloader-MULTI-cwm), as well as running the Nvflash commands that they use manually. And also tried running the command in Ubuntu.
The errors that I get using Nvflash: (note, though the screenshots attached are from using one of the bat files, I get the same errors when running the Nvflash commands manually)
1.) Even though the tablet succesfully boots into bootloader mode (green acer logo with some text in the upper left), I do get an error after running the following command:
nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0x_my_sbk --sync
"bootloader downloaded succesfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x42008 (0x6042008) flags: 0"
2.) When trying to format the partitions manually, after getting into the bootloader using the commands manually from that BAT file, I get:
nvflash -r --format_partition 4
"formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x120002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0"
Partition 6 doesn't work either
At this point, I can still get my tablet into APX mode (tempermentally), but it won't boot up normally anymore to the Acer logo, and none of the other button combinations work to boot into recovery (power button and volume), or erasing cache (volume button and other volume, letting go of volume and moving the lock back and forth).
Does anyone have any advice? I am tempted to just try the oven method and formatting the partitions again, as I feel like I have exhausted most of the software options. If anyone has access to the "badsector" program, that would be very helpful as well.
Thanks so much, I know its a long read!
Click to expand...
Click to collapse
Update: I just ran a slightly different Nvflash command, as seen in this thread (http://forum.xda-developers.com/showthread.php?t=1691729&page=3), with --create and I got the following response:
nvflash --bct bct.bct --setbct --odmdata 0xXXXXXXXX --configfile flash.cfg --create --bl bootloader_apx.bin --sbk 0xmy_sbk
(note: I replaced flash.bct with bct.bct, which is the file in my folder that came with "V8-UNL-ICS-HC-bootloader-MULTI-cwm", as well as bootloader_apx.bin rather than bootloader.bin)
The error is "BCT is full; no more bootloaders can be added", see attached screenshot

Nimbility said:
Update: I just ran a slightly different Nvflash command, as seen in this thread (http://forum.xda-developers.com/showthread.php?t=1691729&page=3), with --create and I got the following response:
nvflash --bct bct.bct --setbct --odmdata 0xXXXXXXXX --configfile flash.cfg --create --bl bootloader_apx.bin --sbk 0xmy_sbk
(note: I replaced flash.bct with bct.bct, which is the file in my folder that came with "V8-UNL-ICS-HC-bootloader-MULTI-cwm", as well as bootloader_apx.bin rather than bootloader.bin)
The error is "BCT is full; no more bootloaders can be added", see attached screenshot
Click to expand...
Click to collapse
Update 2:
as of yesterday my device boots directly to APX only, without having to use the Reset button or anything, and none of the other button combinations change that.
So I tried running Babsector's "a501 A.bat" and got a "fatal failure", see attached screenshot.
And "a501 B.bat" fails on formatting partition 2 (BCT)..
"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
Press any key to continue..."