Related
First of I take no credit for the software used. All goes to AndroidRoot.Mobi!
First of I have:
Windows 7 32BIT
wheelie.zip from - androidroot.mobi/?p=367
WW_epaduser9_2_1_24UpdateLauncher.zip - Original ASUS Firmware from site
Step1:
Extract the wheelie.zip to folder
Extract the WW_epaduser9_2_1_24UpdateLauncher.zip to folder
Step2:
Go into the extracted firmware folder and extract WW_epad-user-9.2.1.24.zip.
You will now see an file called blob in that same folder depending on how you extracted.
Step3:
Copy the blob file into your extracted wheelie.zip folder, into the root directory of it.
Step4:
Open windows command line and cd to the extracted wheelie folder
Example:
cd C:\Users\myName\Desktop\Wheelie
Step5:
If you are now in the root directory of your wheelie folder where all the other files nvflash etc are you can go forward.
Type: "blobunpack blob" in the command line without ""
Now in the wheelie folder you will see 4 new files named:blob.SOS,blob.LNX etc.
Step6:
Connect tablet to pc and put your tablet into APX mode. Volume UP and Power button.
Your computer should make an sound to confirm that it is connected.
Step7:
Check in device manager, under Universal Serial Bus Controller for the Nvidia Recovery something something device. I am not going to explain how to install the APX Drivers or how to put it in APX further. Search the forum.
Step8:
If you can confirm the drivers are correct and connected now in the command line type: "reflash_sbkv2.bat" without the "".
Wait for the process to complete if all the steps was followed correctly it should work out fine.
Again thanks to all the developers whom made the recovery possible:
Bumble-Bee, IEF, kmdm, lilstevie & RaYmAn
As kenshin1388 mentioned, THIS WILL WIPE EVERYTHING!
Some NVFlash information:
Nvflash started
nvflash action [options]
action (one or more) =
--help (or -h)
displays this page
--cmdhelp cmd(or -ch)
displays command help
--resume (or -r)
send the following commands to an already-running bootloader
--quiet (or -q)
surpress excessive console output
--wait (or -w)
waits for a device connection (currently a USB cable)
--create
full initialization of the target device using the config file
--download N filename
download partition filename to N
--setboot N
sets the boot partition to partition N
--format_partition N
formats contents of partition N
--read N filename
reads back partition N into filename
--getpartitiontable filename
reads back the partition table into filename
--getbit filename
reads back BIT into filename
--getbct
reads back the BCT from mass storage
--odm C Data
ODM custom 32bit command 'C' with associated 32bit data
--go
continues normal execution of the downloaded bootloader
options =
--configfile filename
indicates the configuration file used with the following commands:
--create, --format_all
--bct filename
indicates the file containing the BCT
--sbk 0x00000000 00000000 00000000 00000000
indicates the secure boot key for the target device
--bl filename
downloads and runs the bootloader specified by filename
--odmdata N
sets 32bit customer data into a field in the BCT, either hex or
decimal
--diskimgopt N
sets 32bit data required for disk image convertion tool
--format_all
formats all existing partitions on the target device using the config file,
including partitions and the bct
--setbootdevtype S
sets the boot device type fuse value for the device name.
allowed device name string mentioned below:
emmc, nand_x8, nand_x16, nor, spi
--setbootdevconfig N
sets the boot device config fuse value either hex or decimal
--verifypart N
verifies data for partition id = N specified. N=-1
indicates all partitions
Intended to be used with --create command only.
--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
--sync
issues force sync commad
--rawdeviceread S N filename
reads back N sectors starting from sector S into filename
--rawdevicewrite S N filename
writes back N sectors from filename to device starting from sector S
The reference to your partitions all depend on the flash.cfg file located in the folder.
Extraction from wheelie's flash.cfg
[partition]
name=EBT
id=4
type=bootloader
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.EBT
[partition]
name=SOS
id=5
type=data
allocation_policy=sequential
filesystem_type=basic
size=5242880
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=blob.SOS
In order to create your own script:
Step1:
Create a new text file and rename it to .bat. script.txt -> script.bat.
Step2:
Now edit it, include the first two lines required to prepare for nvflash commands
cd %~dp0
"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
Step3:
Now lets add anything extra we want the script to do.
cd %~dp0
"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
"nvflash.exe" -r --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
"nvflash.exe" -r --bct transformer.bct --download 5 recovery.img --sync
This script will only reflash your recovery with another recovery image. I used this just to explain the relation between the config.cfg file and your partitions, the script should also work but I have not tested it.
Another method that should be useful is just modifying the flash.cfg file to only include the partitions we want flashed. Then running the original script that uses --create. Can somebody confirm this?
THIS IS AT YOUR OWN RISKS!
Great first post, thanks!
So these steps should be the solution if your Transformer doesn't boot anymore for whatever reason (probably after installing some ROM)?
Very detailed description, I think now I can root my TF 101 sbk v2 to install CM9 or something else, if there is this not too difficult way to get it back to life if something goes wrong.
Thanks for this, like a fool I was using the renamed blob files from the original nvflash and not the original blob file names.
Thanks, I can confirm that it does recover your tablet. Recovered mine from an soft brick. Also had a pretty bad moment where not even the phone will start\boot up only APX mode.
To root the tablet just use [GUIDE/TOOL] [EASY] PERI-V0.3: One click root+recovery! (Works with .24!).
I cant post links yet.
I recovered my tablet, root, and then flashed latest HD Revolution Rom. Everything working perfectly!
I would definitely warn everybody that this is not a recommended method to return to stock as it wipes internal storage. I did that a couple days after a soft brick and was disappointed to find all my movies missing. Gotta go find all my DVDs again.
Sent from my Transformer TF101 using xda premium
kenshin1388 said:
I would definitely warn everybody that this is not a recommended method to return to stock as it wipes internal storage. I did that a couple days after a soft brick and was disappointed to find all my movies missing. Gotta go find all my DVDs again.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Thread Updated. Any other method then that will work better and not have data loss?
Franz.Hendrik said:
Thread Updated. Any other method then that will work better and not have data loss?
Click to expand...
Click to collapse
Ill do some looking and see if I can figure out what partition the internal storage is. I believe there is an nvflash command to format a specific partition, so it shouldn't be hard to make an script to format manually and then flash. I'm still new to nvflash though lol.
Sent from my Transformer TF101 using xda premium
NvFlash just the EBT and SOS partitions (Bootloader and Recovery) and you'll save your internal storage. mmcblk0p4 is the partition I believe. I'll make a video guide sometime today to recover from soft-bricks.
looking for this
I looking for this in a few days. Thanks man.
Thing O Doom said:
NvFlash just the EBT and SOS partitions (Bootloader and Recovery) and you'll save your internal storage. mmcblk0p4 is the partition I believe. I'll make a video guide sometime today to recover from soft-bricks.
Click to expand...
Click to collapse
I'm on Revolver 4.0.3 RC3, I would like to flash ubuntu on dual boot, but I don't want to loose any data from Android. If only someona could point out a small how to would be very nice. nvflash rules
Got up to the command to flash SBKV2 and I get "connection failed nv error 0x30011"
Make sure the tablet is in APX mode power + volume up
pkfox said:
Make sure the tablet is in APX mode power + volume up
Click to expand...
Click to collapse
It was definitely in APX mode. heard the PC connect. shows its connected as an APX device.
Am I supposed to flash the sbkv2 no matter what? or is my problem I need to flash sbkv1?
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>reflash_sbkv2.bat
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>cd C:\Users\Spoo\Desktop\Desktop folder\TF101\whe
elie\
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl boot
loader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x252309624468846103
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct -
-configfile flash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
connection failed NvError 0x30011
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
connection failed NvError 0x30011
C:\Users\Spoo\Desktop\Desktop folder\TF101\wheelie>
Click to expand...
Click to collapse
---------- Post added at 02:57 PM ---------- Previous post was at 02:51 PM ----------
Well I feel dumb. I needed to flash SBKV1 it seems. looks like its working.
see what happens when you try to gain root late at night?
Glad you sorted it, I think I read that some B70 models have sbk1 that would explain things
Hi,
I have a TF101G B80. It doesn't matter which version I try to flash. Either SBK1 or SBK2. I always get
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199388248982231
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Unfortunately my device is bricked. So Wheelie was my last hope...
Does anyone have an idea? Thank you very much.
Steve
sscde said:
I have a TF101G
Click to expand...
Click to collapse
Wheelie does not support TF101G units, they have yet another Secure Boot Key.
first time I've had hope in a while...
so a family member, on recommendation of mine, bought a Transformer around Christmas for his wife. They hardly used it, know nothing about tablets or android, and have managed to brick it. Since I'm the family tech guy (only because I am the youngest member of the family) I am stuck figuring out how to fix this. I'm fairly competent working through Windows, but hardly any with Linux.
They upgraded to the latest version of android around mid-May and have been stuck in boot-loop hell since, occasionally turning on and off on its own. After hours and hours of searching, I found this thread and thought I found my solution...but I'm still stuck in boot loop.
The serial sticker is not on the tablet, so I can not confirm what version it is, however I have tried to flash both sbkv1 and 2 and it will ONLY flash sbkv2. Using the tutorial here, everything seemed to work fine, but I am still stuck on the boot screen. I've copied the log here and any assistance would be greatly appreciated.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Anthony>cd c:\asus\wheelie
c:\ASUS\wheelie>blobunpack blob
Header size: 60
4 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: EBT
Offset: 124 (0x7C)
Size: 1454712 (0x163278)
Writing file blob.EBT (1454712 bytes)
Partition 1
Name: SOS
Offset: 1454836 (0x1632F4)
Size: 4284416 (0x416000)
Writing file blob.SOS (4284416 bytes)
Partition 2
Name: LNX
Offset: 5739252 (0x5792F4)
Size: 4151296 (0x3F5800)
Writing file blob.LNX (4151296 bytes)
Partition 3
Name: APP
Offset: 9890548 (0x96EAF4)
Size: 536870912 (0x20000000)
Writing file blob.APP (536870912 bytes)
c:\ASUS\wheelie>reflash_sbkv1.bat
c:\ASUS\wheelie>cd c:\ASUS\wheelie\
c:\ASUS\wheelie>"wheelie.exe" -1 --bct transformer.bct --bl bootloader.bin --od
m 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199401146529303
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
c:\ASUS\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fla
sh.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
c:\ASUS\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
c:\ASUS\wheelie>reflash_sbkv2.bat
c:\ASUS\wheelie>cd c:\ASUS\wheelie\
c:\ASUS\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --od
m 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x251199401146529303
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
c:\ASUS\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fla
sh.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
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 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
c:\ASUS\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
c:\ASUS\wheelie>
Click to expand...
Click to collapse
I am sorry for being offline a while now , thank you vodascum for my bad data connections.
Did you check that the files (image files) you are flashing is the correct files?
Can you enter recovery?
Franz.Hendrik said:
I am sorry for being offline a while now , thank you vodascum for my bad data connections.
Did you check that the files (image files) you are flashing is the correct files?
Can you enter recovery?
Click to expand...
Click to collapse
I downloaded the image files directly from the Asus site, so I would hope they're correct, but I don't know how to check.
I can not enter recovery
Any help? I'd really appreciate it
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!
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.
Hello.
Since I dont have 10 posts, I am forced to post here. I hope this is ok.
I already asked in a german forum, but I didnt get an answer there.
I have an Acer A501 Tablet.
Bootloader is HC 3.01.
Recovery is Touch Recovery 1.8.1 by Thor
ROM is 4.2.2 by TegraOwners
Since I want to try out the new 4.3 ROMs my bootloader must be upgraded to ICS Bootloader.
I am using Linux. And I want to use nvflash to replace the HC 3.01 bootloader with ICS v9.
I download the "Patched ICS bootloader V9" bootloader which contains 3 files:
bootloader_apx.bin
bootloader_v9.bin
bootloader_v9.blob
After studying the tutorials
for flashing:
http://forum.xda-developers.com/showthread.php?t=1622425
and linux:
http://forum.xda-developers.com/showpost.php?p=26372919&postcount=460
I still have a question. So forgive me to post here.
I have written an sh script which should do the flashing.
Code:
#!/bin/sh
./nvflash --bl bootloader_apx.bin --sbk 0x12345678 0x12345678 0x12345678 0x12345678
./nvflash -r --format_partition 4
./nvflash -r --download 4 bootloader_v9.bin
bootloader_apx.bin should load the bootloader.
bootloader_v9.bin is the bootloader itself.
bootloader_v9.blob I dont know what this file is good for.
So my question. Is this script right? I only want to replace the bootloader. Recovery and ROM is already installed.
I really need to know this exactly, since I dont want to brick my tablet.
Oberkellner said:
Hello.
Since I dont have 10 posts, I am forced to post here. I hope this is ok.
I already asked in a german forum, but I didnt get an answer there.
I have an Acer A501 Tablet.
Bootloader is HC 3.01.
Recovery is Touch Recovery 1.8.1 by Thor
ROM is 4.2.2 by TegraOwners
Since I want to try out the new 4.3 ROMs my bootloader must be upgraded to ICS Bootloader.
I am using Linux. And I want to use nvflash to replace the HC 3.01 bootloader with ICS v9.
I download the "Patched ICS bootloader V9" bootloader which contains 3 files:
bootloader_apx.bin
bootloader_v9.bin
bootloader_v9.blob
After studying the tutorials
for flashing:
http://forum.xda-developers.com/showthread.php?t=1622425
and linux:
http://forum.xda-developers.com/showpost.php?p=26372919&postcount=460
I still have a question. So forgive me to post here.
I have written an sh script which should do the flashing.
Code:
#!/bin/sh
./nvflash --bl bootloader_apx.bin --sbk 0x12345678 0x12345678 0x12345678 0x12345678
./nvflash -r --format_partition 4
./nvflash -r --download 4 bootloader_v9.bin
bootloader_apx.bin should load the bootloader.
bootloader_v9.bin is the bootloader itself.
bootloader_v9.blob I dont know what this file is good for.
So my question. Is this script right? I only want to replace the bootloader. Recovery and ROM is already installed.
I really need to know this exactly, since I dont want to brick my tablet.
Click to expand...
Click to collapse
Judging by the post u linked the script looks like this:
Code:
#!/bin/sh
./nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xXXXXX 0xXXXXX 0xXXXXX 0xXXXXXX --sync
./nvflash -r --format_partition 4
./nvflash -r --download 4 ics_boot_unlk_V3.bin
./nvflash -r --format_partition 6
./nvflash -r --download 6 recovery_thor17_403.img
./nvflash -r --go
Yr script is missing:
--sync command after the sbk and
./nvflash -r--go command after the v9.bin seeing as you aren't flashing a recovery.img. ...
I am linux illiterate! ! So cannot help you much, if at all but I think you'd be best to follow the post you linked to....hopefully someone else, (like @Moscow Desire, lol) can help you out a bit more!
Good luck
dibb
Sent from my GT-I9300 using Tapatalk 4
Thread can be closed.
I figured it out myself.
I have written a German tutorial. If there is interest I will translate it to English.
:fingers-crossed:
Oberkellner said:
Thread can be closed.
I figured it out myself.
I have written a German tutorial. If there is interest I will translate it to English.
:fingers-crossed:
Click to expand...
Click to collapse
Sorry am late to the party, but happy you figured it out. Am on vacation this month.
If you want to write a guide for linux, then you can create a new thread in general forum.
@Oberkellner - a guide would be great, as Moscow suggested start a new thread for it and I will add a link to it in the root guide, thanks
@Moscow Desire - good to see you M, have a gr8 vacation
dibb_nz said:
@Oberkellner - a guide would be great, as Moscow suggested start a new thread for it and I will add a link to it in the root guide, thanks
Click to expand...
Click to collapse
I have written to tutorial and saved it, but I cant post it.
Error:
After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
My tutorial needs outside links which contain the files.
Correct me if I'm wrong but u should be able to upload the files via attachments here on xda, unless the 10 post rule applies to attachments as well...
Sent from my GT-I9300 using Tapatalk 4
Oberkellner said:
I have written to tutorial and saved it, but I cant post it.
Error:
After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
My tutorial needs outside links which contain the files.
Click to expand...
Click to collapse
I am pretty desperate for a linux nvflash tutorial, as I'm getting write errors in Windows and there's some evidence linux may be the answer. If there's any way for you to PM me the tutorial with links, etc. I'd be hugely appreciative. Thanks.
mylacuna said:
I am pretty desperate for a linux nvflash tutorial, as I'm getting write errors in Windows and there's some evidence linux may be the answer. If there's any way for you to PM me the tutorial with links, etc. I'd be hugely appreciative. Thanks.
Click to expand...
Click to collapse
Wot sort of write errors? If you've run babsector pls post output.
As far as linux is concerned u just need to pop yr tab in apx mode and run the command, see the 3rd post in the root guide in my sig
Sent from my GT-I9300 using Tapatalk
The errors always involve an inability to write to or partition the BCT partition. I've seen a few others users stuck in that dead end and a handful of them found success with this operation in linux.
(I'm such a newb I don't know how to properly post the output (in the gray box), but here it is)
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Press any key to continue . . .
---------- Post added at 01:06 PM ---------- Previous post was at 12:38 PM ----------
@Oberkellner, I'm very sorry to threadjack. Just haven't received much help in my own thread and I know dibb_nz is very knowledgeable about this particular issue.
@dibb_nz, running nvflash from command line, using the code in the post you mentioned returns this
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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.bin
| 714385/714385 bytes sent
bootloader.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 (cod
e: 14) message: nverror:0x5 (0x1000005) flags: 0
Click to expand...
Click to collapse
mylacuna said:
The errors always involve an inability to write to or partition the BCT partition. I've seen a few others users stuck in that dead end and a handful of them found success with this operation in linux.
(I'm such a newb I don't know how to properly post the output (in the gray box), but here it is)
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Press any key to continue . . .
---------- Post added at 01:06 PM ---------- Previous post was at 12:38 PM ----------
@Oberkellner, I'm very sorry to threadjack. Just haven't received much help in my own thread and I know dibb_nz is very knowledgeable about this particular issue.
@dibb_nz, running nvflash from command line, using the code in the post you mentioned returns this
Click to expand...
Click to collapse
The code you ran, can be run with linux.
can you try it again please but replace the following:
odmdata 0x300d8011
with this:
odmdata 0xb00d8011
at the very end of the code replace --sync with --go
I've never tried doing it this way so you can play guinea pig, lol...don't worry it won't break anything thats not already broken
If that doesn't do it, then you will need to run the babsector.rar file, this will reset your partitions, if you get the bct error head over to this thread http://forum.xda-developers.com/showthread.php?p=47871344#post47871344from post#27. these guys are having issues too, u may be able to help each other
Pls post the outcome of the change in code here though, cheers dibb
Thank you kindly for your continued attempt to help. Your new code returned this:
c:\nvflash>nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash
.cfg --odmdata 0xb00d8011 --sbk 0x417D4C00 0x932F1700 0xDB65F302 0xA4082103 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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: 0xb00d8011
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
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information (cod
e: 14) message: nverror:0x5 (0x1000005) flags: 0
Click to expand...
Click to collapse
FWIW, I was able to muddle my way through an attempt to use NvFlash in Linux (Ubuntu). Took a while to get everything set up correctly, but once I did, even trying to get the partition table failed :crying:
I think I'm screwed
Lol no u not m8...babsector.rar file will repartition download in post 2 in the root guide....
Sent from my GT-I9300 using Tapatalk
dibb_nz said:
Lol no u not m8...babsector.rar file will repartition download in post 2 in the root guide....
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
While I greatly appreciate the ray of hope you're giving me, I've run BabSector dozens of times and it always fails at creating the BCT partition (or anything after that).
Edit: here's the result of the A.bat file:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0388924541a01297
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
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
5 (0x1000005) flags: 0
Press any key to continue . . .
Click to expand...
Click to collapse
dibb_nz said:
Judging by the post u linked the script looks like this:
Code:
#!/bin/sh
./nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xXXXXX 0xXXXXX 0xXXXXX 0xXXXXXX --sync
./nvflash -r --format_partition 4
./nvflash -r --download 4 ics_boot_unlk_V3.bin
./nvflash -r --format_partition 6
./nvflash -r --download 6 recovery_thor17_403.img
./nvflash -r --go
Yr script is missing:
--sync command after the sbk and
./nvflash -r--go command after the v9.bin seeing as you aren't flashing a recovery.img. ...
I am linux illiterate! ! So cannot help you much, if at all but I think you'd be best to follow the post you linked to....hopefully someone else, (like @Moscow Desire, lol) can help you out a bit more!
Good luck
dibb
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
mylacuna said:
While I greatly appreciate the ray of hope you're giving me, I've run BabSector dozens of times and it always fails at creating the BCT partition (or anything after that).
Edit: here's the result of the A.bat file:
Click to expand...
Click to collapse
Well thankx for posting that...bct errors are difficult to fix, not impossible, just difficult. .
Blackthund3rs apxflash tool is the only tool I know of that can fix and sometimes even that tool can have probs too...
I dont know why this happens, but it does seem strange alot of peeps lately have struck this error.
As I stated in the other thread...nvflash requires the bct from your own tab...apxflash tool uses a default bct which in most cases works...but if it does not then you must dump yr tabs bct and use that. The tool provides an option to do this...as long as u are on Ics, rooted, have busybox installed and usb debugging enabled!!!
So, can u still boot?
Which rom were u running?
Can u boot to recovery?
Sent from my GT-I9300 using Tapatalk
Can't boot, to Android or Recovery, was running a custom HC 3.1 ROM called Minimalist because anything after 3.1 broke the app needed to stream from Hava Monsoon (slingbox-like device). Was rooted, had CWM installed, and I do have a backup with a mmcblk0_start.img, which supposedly can be used to decrypt and recreate a .bct file but I'm not sure how that can help seeing as how my partition table is fubar'd and I can't write to partition 2. Needless to say, I wasn't on ICS, don't have busybox installed (not even sure what it is) but I do (or at least did) have USB debugging enabled.
Was the first part of your last reply directed at me? The part about stuff missing from the script?
At this point, I'm back to working in Windows. Tried linux and it didn't help or change the errors.
---------- Post added at 09:55 PM ---------- Previous post was at 09:41 PM ----------
Hmmm... just contacted ACER for an out-of-warranty repair and they created an RMA and sent me a pre-paid FedEx label. I have my fingers crossed that they are getting a lot of bad memory/motherboard repairs and are willing to do it for free, as suggested in this post:
http://forum.tegraowners.com/viewtopic.php?f=8&t=1249#p39164
Was the first part of your last reply directed at me? The part about stuff missing from the script?
Click to expand...
Click to collapse
sorry no it wasn't posting from my ph so not sure wot happened there lol
mylacuna said:
Can't boot, to Android or Recovery, was running a custom HC 3.1 ROM
Click to expand...
Click to collapse
ahhhh ok you're on the HC bootloader, different kettle of fish!!!
Its a shame the OP never posted his tutorial or told us how he got round the problem...ggrrrr
You have 2 choices from here:
1) run an update.zip from your ext sd card, altho with all the mucking about we've done I'm not sure how that will go...theres a link for a HC3.1 here. Put it on yr ext sd. Then power/vol down and it should boot into stock recovery and flash.
If all is well, you should be able to OTA all the way to ICS
2) The other way is to use timmydeans v4 - its nvflash EUU which will upgrade you to HC 3.2.1 pre-rooted and cwm installed. You say that anything above 3.1 breaks an app you want, but gosh, 3.1 is Gingerbread, its ancient Surely there must be another way to stream???
Anyway the main thing is to get you up and running, see how you go with these 2 methods.
If the upate.zip works and you intend staying on 3.1, you will need root again, see the root guide for the iconiaroot file, then Acer Recovery Installer file to flash a custom recovery.
---------- Post added at 11:12 AM ---------- Previous post was at 11:07 AM ----------
@mylacuna OMG True....Good on Acer, I can see them getting a few more requests too...pls let us know how you get on with it
Thanks again. Think I'm going to go with the RMA.
FWIW, neither update.zip on ext. sd card, nor timmy dean's method would work, unfortunately. Stock recovery never boots (not sure if it's because something's cooked, or because I had CWM installed) and Timmy Dean's never shows a connection using the test.cmd script. I think that's because it's requires an ICS bootloader or something.
In any case, have a nice one, mate. You went above and beyond :good:
FWIW, as outlined in the previous posts, my Iconia was fully bricked... absolutely none of the tools available were able to re-format a corrupted BCT partition, whether due to hardware/memory error or what, I can't say, but I initiated a repair ticket and Acer repaired my out-of-warranty A500 for free, including shipping both ways.
So that might be an option for anyone who's having no luck with these other methods.
Kewlies good on Acer
Sent from my GT-I9300 using Tapatalk
Hi, everybody!
I'm posting here my solution, which describes how to unbrick Asus Transformer TF101.
The solution is based on bigwheelie from this post. You can download the scripts from here (I'll provide the attachments) or from that post.
Despite, that post is about repartitioning, it perferctly fits for unbricking Transformer TF101 tablets!
First of all, despite there are a lot of topics on this forum, I didn't manage to unbrick my device using instructions from that posts.
My case was quite complicated: I broke a partition table. The second problem are links to the scripts. Almost all the links do not work (Oct 2018). The links from the thread I provided do open.
The solution is for Linux only. If you are a Windows guy, you can use VirtualBox or create a bootable USB flash of a Linux disto.
So, here's the instruction of how to unbrick your Asus Transformer TF101 tablet:
Boot up Linux.
Download & unpack the scripts (I use bash version for example)
Open console/terminal. Go to the script folder: cd ~/scripts_folder
Go to root (it's required). For Ubuntu-like distros you can type sudo -s or add sudo before every command, e.g. sudo ./nvflash ...
Next, we need to go to APX mode. To reach there, connect a USB cable to your PC and press & hold Volume Up and Power buttons simultaneously
Open another console. lsusb command shows all the USB devices. Run it and you must see the line containing "Nvidia".
Alternatively, you can run command watch -n 1 lsusb, which will every second run lsusb without a need to call it every time.
OK, on this stage you must see "Nvidia" among your USB devices. Let's do unbrick. All you need to do is to call
Code:
reflash_sbkv1.sh
or
Code:
reflash_sbkv2.sh
depending on your tablet type.
Or, if something goes wrong, you can open the script, copy and run commands step-by-step (sbk v1):
Code:
./wheelie -1 --bl bootloader.bin --bct transformer.bct --odm 0x300d8011 || break
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync || break
./nvflash -r --go || break
If everything is fine, you the device must reboot and you will have vanilla Android 4.0.3 with TWRP recovery.
I hope, it was helpful to somebody.
Good luck!
Attachments:
bigwheelie-bash.zip
bigwheelie-python2.zip
Exterminator13 said:
Hi, everybody!
I'm posting here my solution, which describes how to unbrick Asus Transformer TF101.
The solution is based on bigwheelie from this post. You can download the scripts from here (I'll provide the attachments) or from that post.
Despite, that post is about repartitioning, it perferctly fits for unbricking Transformer TF101 tablets!
First of all, despite there are a lot of topics on this forum, I didn't manage to unbrick my device using instructions from that posts.
My case was quite complicated: I broke a partition table. The second problem are links to the scripts. Almost all the links do not work (Oct 2018). The links from the thread I provided do open.
The solution is for Linux only. If you are a Windows guy, you can use VirtualBox or create a bootable USB flash of a Linux disto.
So, here's the instruction of how to unbrick your Asus Transformer TF101 tablet:
Boot up Linux.
Download & unpack the scripts (I use bash version for example)
Open console/terminal. Go to the script folder: cd ~/scripts_folder
Go to root (it's required). For Ubuntu-like distros you can type sudo -s or add sudo before every command, e.g. sudo ./nvflash ...
Next, we need to go to APX mode. To reach there, connect a USB cable to your PC and press & hold Volume Up and Power buttons simultaneously
Open another console. lsusb command shows all the USB devices. Run it and you must see the line containing "Nvidia".
Alternatively, you can run command watch -n 1 lsusb, which will every second run lsusb without a need to call it every time.
OK, on this stage you must see "Nvidia" among your USB devices. Let's do unbrick. All you need to do is to call
Code:
reflash_sbkv1.sh
or
Code:
reflash_sbkv2.sh
depending on your tablet type.
Or, if something goes wrong, you can open the script, copy and run commands step-by-step (sbk v1):
Code:
./wheelie -1 --bl bootloader.bin --bct transformer.bct --odm 0x300d8011 || break
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync || break
./nvflash -r --go || break
If everything is fine, you the device must reboot and you will have vanilla Android 4.0.3 with TWRP recovery.
I hope, it was helpful to somebody.
Good luck!
Attachments:
bigwheelie-bash.zip
bigwheelie-python2.zip
Click to expand...
Click to collapse
Bummer. I've tried just about everything to unbrick my POS and this looked like another opportunity to try again, but alas I am an idiot and have no idea what you are talking about. I loaded linux on a bootable usb. Got into it. Typed around. kept getting invalid command and gave up. Who am I kidding. I have no idea what im doing. thats what I get for only using windows and not taking time to understand any other OS. Thank for the info though.