Database Info

[Help] Broke Eee Pad Transformer :(

Hi all.
I tried to install rom on my Eee Pad but i failed and my device is broke now
please help me.
that what i did..
- i installed Windows nvflash with APX drivers successfuly
- then i installed SU using Razorclaw_1.0.1.apk successfuly
- then start my device with APX mode with windows 7 on my kaptop
- then i start download.bat from nvflash folder, everything done
but the device just show me .. black screen with message
entering nvflash recvery mode / nv3p server
chip uid : .... some numbers i don't remember
my device info ..
kernal
2.6.36.3
build
HTK75.CN_epad-8.6.5.19-20111107
android
3.2.1
Please any help .. its first day with my Eee Pad Transformer
Thanks

You got an apx bootloop going on there. You need to nvflash your way out of there.

goodintentions said:
You got an apx bootloop going on there. You need to nvflash your way out of there.
Click to expand...
Click to collapse
How?
i know nothing about android at all, some details will help
please

First of all, what's your seriel number?

goodintentions said:
first of all, what's your seriel number?
Click to expand...
Click to collapse
s/n : B70kas151295

This is the log when run download.bat
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
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: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: 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: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed

Hang on, I'm confused about something. Why did you nvflash after you rooted?

goodintentions said:
Hang on, I'm confused about something. Why did you nvflash after you rooted?
Click to expand...
Click to collapse
i don't have any experiance with that, i did that to access the recovery options
i just tried to install rom from here http://forum.xda-developers.com/showthread.php?t=1245892

Why didn't you flash via cwm? Nvflash isn't exactly for those who are new to android, you know. What a mess...
It looks like the nvflash process went ok. The only thing that's missing is the recovery.
Do this for me. Press down and hold the power button for about 20 seconds. Then wait abou 20 seconds. Then press down and hold the power button for about 5 seconds. Tell me what you see.

goodintentions said:
Why didn't you flash via cwm? Nvflash isn't exactly for those who are new to android, you know. What a mess...
It looks like the nvflash process went ok. The only thing that's missing is the recovery.
Do this for me. Press down and hold the power button for about 20 seconds. Then wait abou 20 seconds. Then press down and hold the power button for about 5 seconds. Tell me what you see.
Click to expand...
Click to collapse
sorry i don't know about cwm
i did it, nothing happened
not turned on

CWM/ClockWorkMod is a common recovery tool. It is somewhat like booting into a recovery partiton that allows you to backup/restore using a MicroSD. Also whiping data.
Sent from my Transformer TF101 using Tapatalk

yes.
what should i do to get my device work again?

What ROM were you trying to flash? Also I noticed you're missing the recovery image so when you try and go through the process it crashes at flashing the recovery and everything after that doesn't get flashed so you don't have a system image either. This is why your TF won't boot.
fadiodeh said:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
Click to expand...
Click to collapse
What files did you download and from where?

brando56894 said:
What ROM were you trying to flash? Also I noticed you're missing the recovery image so when you try and go through the process it crashes at flashing the recovery and everything after that doesn't get flashed so you don't have a system image either. This is why your TF won't boot.
What files did you download and from where?
Click to expand...
Click to collapse
Hi,
thanks to reply,
i download this .. http://ff06d07.filefactory.com/dl/f...822c5b18bdf8d2e664f2b163ae76fff/n/nvflash.zip
then i tried to set Prime 1.4 files but i can't find boot.img and recovery.img on it, its just contain one file system.img, i download it from here http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
i want to install Android Revolution HD from this link http://forum.xda-developers.com/showthread.php?t=1245892
or back to stock os at least .
Thanks

how can i get the correct recovery.img and boot.img files for my device ?

IIRC you need to combine the files that came with NVflash with the files that came with Prime. You will flash Android Revolution later (you can actually do it without flashing Prime and just install CWM but I don't really remember the process, search for it) via clockwork mod recovery (CWM).
Here's a guide to read: Guide
I'm uploading the stock images for you.
You really should have read some more before you tried this.

brando56894 said:
IIRC you need to combine the files that came with NVflash with the files that came with Prime. You will flash Android Revolution later (you can actually do it without flashing Prime and just install CWM but I don't really remember the process, search for it) via clockwork mod recovery (CWM).
You really should have read some more before you tried this.
Click to expand...
Click to collapse
i did, but the files in Prime 1.4 is just one file system.img, i can't find recovery.img and boot.img
i got prime 1.4 from here http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
what should i do ?

I got this ..
ICS Themed Vanilla Release
Prime! v2.1.0
files .. system.img, boot.img and recovery.img
the issue is when start NVflash its disconnected USB automatically,
see the log please ..
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
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: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
and
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x03806209421fa5d7
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: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: 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!
failed executing command 14 NvError 0x30012
command failure: create failed
its not disconnected in specific step, its randomly

its working now with ICS Themed Vanilla Release
after a lot with tries using Brks_rootkit_v7
Thanks a lot for all there
have a great day

You're welcome and glad you got it fixed!

[Q] Installing ROM to save a bricked G2x

Spent the day bricking my G2x. The phone will not power up. I still have access to the phone using the vol up/down keys with no battery.
I am trying to use the method described here to recover the phone to a bootable state.
[ROM] ROM for recovery G2X under the NVFLASH
http://forum.xda-developers.com/showthread.php?t=1248644
The process starts fine, but always dies in the middle of updating the ext3_system.img. It dies around 30,000kb.
Here's the output of the process:
Code:
C:\CYANOGEN\V21>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --configfile android_fastboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x0288420641616317
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: UDA
creating partition: EB4
creating partition: UDB
-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 MBR please wait.. |/done!
Formatting partition 7 APP please wait.. --\|/--\|/--done!
Formatting partition 8 CAC please wait.. \|/--\|/-done!
Formatting partition 9 MSC please wait.. -\|/--done!
Formatting partition 10 EB1 please wait.. \|done!
Formatting partition 11 LNX please wait.. /--\|/--\|done!
Formatting partition 12 EB2 please wait.. /--\|/--done!
Formatting partition 13 DRM please wait.. \|/--done!
Formatting partition 14 EB3 please wait.. \|done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 EB4 please wait.. |/done!
Formatting partition 17 UDB please wait.. done!
done!
sending file: fastboot.bin
fastboot.bin sent successfully
sending file: recovery.img
recovery.img sent successfully
sending file: ext3_system.img
26148864/435200000 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
I'm using an XP machine, with Windows Essentials as the Antivirus.
I downloaded the files twice, and get the same results with both downloads.
Any help would be appreciated!

Your holding down the buttons the whole time correct? I dunno maybe try a different port or windows 7.
Sent from my LG-P999 using xda premium

d12unk13astard said:
Your holding down the buttons the whole time correct? I dunno maybe try a different port or windows 7.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Yeah I suggest try putting your files setup exactly as he says in the tutorial and as dru12k said make sure you hold the buttons the entire time. If that don't work I know it works on windows 7. I recovered mine several times using it.
Sent from my Galaxy Nexus using xda premium

Once the flashing starts, I have been releasing the buttons! I'll give this a try when I get home tonight. Thanks!

Giant Success!
From the great abyss, we have looked over the edge and laughed! The key was holding the buttons throughout the flashing process. Everything worked swimmingly, and the phone is back to tip-top shape - even better than before.
Thanks for the words of encouragement, and being here to help everyone out.

Help - Can not unbrick TF101 B70 with Wheelie

Hi, my wife's stock TF101 went into a boot loop last night that I can't get it to break out of after multiple cold boot attempts. I also tried doing a factory reset but that gives me the sad android guy on his back (same thing when I try to boot to recovery).
I've installed tons of custom roms over the years and am generally quite knowledgeable when it comes to android, but I'm stuck on this issue (and I'm starting to wonder if my eMMC is faulty or something).
The good news is that I can get into APX mode and use nvflash
I've downloaded both the .24 and .27 firmware updates from asus and tried to to a reflash using wheelie and I keep getting the same error (I've tried this via windows and linux)
My formats and downloads go through successfully each time but then I get these errors:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x14000
5) flags: 0
I've been googling them all morning with no luck and any help would be greatly appreciated
Here's the full output from reflash:
C:\Users\panderson\Desktop\wheelie>blobunpack.exe 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:\Users\panderson\Desktop\wheelie>reflash_sbkv2.bat
C:\Users\panderson\Desktop\wheelie>cd C:\Users\panderson\Desktop\wheelie\
C:\Users\panderson\Desktop\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl
bootloader.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: 0x252308533528241111
[=] 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:\Users\panderson\Desktop\wheelie>"nvflash.exe" -r --bct transformer.bct --setb
ct --configfile flash.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
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x14000
5) flags: 0
C:\Users\panderson\Desktop\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0

Encryption Unsucsessful - E:unable to mount /data - nothing works

Sorry for my bad English
A few weeks ago i installed TWRP 2.2.1.4 and flashed the eos4 JB4,2 rom
I created 3 User on Android and it worked fine with no problems.
After 2 weeks i used the keyboard-Dock and now it boots with
"Encryption Unsucsessful"
I used the wipe Button on recovery boot - no sucsess
Then I went into Recovery Menu and used Factory Reset - no sucsess
I reflashed the eos4 - rom - failure "E:unable to mount /data"
I read in different Forums and used different ways (Easy Flasher,Peri-Tool,Wheelie,NVFlash...)
to unbrick the Transformer but nothing works for me.
(E:unable to mount /data)
I can connected to the TF101(SBK1) under win8 and Ubuntu 12.10 in adb and apx Mode
and can use the sytem and sdcard folder to push or pull files to or from the TF101.
Is there any way to swap the internalSD to externalSD (vold.fstab) and flash a rom that can access it
or knows someone another way to fix my Problem?

What errors did NvFlash return and what files did you use?

Thing O Doom said:
What errors did NvFlash return and what files did you use?
Click to expand...
Click to collapse
Thank you for answer
I used so many different ways on windows and linux, i am not sure which software i used at first,
but i start from scratch.
use Ubuntu 12.10
- udev.rules created for user
Sorry cant post complete Links (min.10 posts)
- download wheelie - androidroot.mobi/download/wheelie.tar.bz2
- download recovery twrp - techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
- download recovery cwm - download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.3-tf101.img
- open terminal:# sudo ./blobunpack recovery-clockwork-6.0.1.3-tf101.img
=
Header size: 60
1 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: SOS
Offset: 76 (0x4C)
Size: 4628480 (0x46A000)
Writing file recovery-clockwork-6.0.1.3-tf101.img.SOS (4628480 bytes)
- same with trwp
- tablet in bootmode (power and vol + for 10sec.)
- terminal:# sudo ./nvflash -r --download 5 recovery-clockwork-6.0.1.3-tf101.img.SOS
=
Nvflash started
[resume mode]
(hang - 60min. - restart)
- tablet in bootmode (power and vol + for 10sec.)
- terminal:# sudo ./nvflash -r --download 5 openrecovery-twrp-2.3.2.3-tf101.blob.SOS
=
Nvflash started
[resume mode]
(hang - 120min. restart)
-download WW_epad-user-9.2.1.27 from asus.de/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
-unzip the file and copy the blob to the wheelie-folder
-use blobunpack and open a terminal
-terminal:# sudo ./reflash_sbkv1.sh
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: 0x33c208443603097
[=] 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
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
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0

Use these files: http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
Wheelie from androidroot.mobi
Unzip first link, then overwrite with wheelie.zip files. Run reflash_sbkv1.bat
See what that does.

Thing O Doom said:
Use these files: xdafileserver.nl/index.php?dir=Asus%2FAsus+Transformer+%28TF101%29%2FSTOCK+ROMS%2FICS+.27
Wheelie from androidroot.mobi
Unzip first link, then overwrite with wheelie.zip files. Run reflash_sbkv1.bat
See what that does.
Click to expand...
Click to collapse
Ok, i download and unzip the file in a new folder.
Then i copy all files from wheelie to the new folder and run "sudo ./reflash_sbkv1.sh"
Result: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: 0x33c208443603097
[=] 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
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
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bct Write Failed (code: 22) message: nverror:0x40005 (0x140005) flags: 0
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0

That error looks like it's with NvFlash, if possible can you try running the .bat in Widoze?
If not I don't think it's going to take anything you send at it, can you try just writing the Blob.SOS and Blob.EBT partitions, then try booting into the recovery, if that works you can pick up the TWRP or Rouge or whatever recovery blob file and rename to Blob.SOS , giving you back recovery that might work.
This is a very strange issue.

Thing O Doom said:
That error looks like it's with NvFlash, if possible can you try running the .bat in Widoze?
If not I don't think it's going to take anything you send at it, can you try just writing the Blob.SOS and Blob.EBT partitions, then try booting into the recovery, if that works you can pick up the TWRP or Rouge or whatever recovery blob file and rename to Blob.SOS , giving you back recovery that might work.
This is a very strange issue.
Click to expand...
Click to collapse
I reactivated my old PC with Windows XP and install the Software and Driver
Then I start "cmd" with admin rights and execute download.bat
C:\android\NVFLASH_ICS_9.2.1.27_WW_NOROOT\NVFLASH_ICS_9.2.1.27_WW_NOROOT>"nvflas
h.exe" --bct transformer.bct --setbct --configfile flash.cfg --create --bl blob.
EBT --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x033c208443603097
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: 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.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x2 (0x2) flags: 0
second
C:\android\NVFLASH_ICS_9.2.1.27_WW_NOROOT\NVFLASH_ICS_9.2.1.27_WW_NOROOT>nvflash
-r --download 5 openrecovery-twrp-2.3.2.3-tf101.blob.SOS
Nvflash started
[resume mode]
failed executing command 14 NvError 0x120002
command failure: partition download failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
third
C:\android\NVFLASH_ICS_9.2.1.27_WW_NOROOT\NVFLASH_ICS_9.2.1.27_WW_NOROOT>nvflash
-r --getpartitiontable partition_table.txt
Nvflash started
[resume mode]
I dont know what "partition 2 BCT" is ?
Is the Partitionstable completely damaged ?
and if its broken, is there a way to manually create new partitions?

same problem.
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %, but here my device hang ... -> this line not comming -> [!] Done - your device should now be ready for nvflash
what now? try with unix system or a hardfailure emmc problem?
only apx mode running, not adb possible or start recovery ...

I'm starting to think that the eMMC is bad/Faulty chip. Which would mean a hardware problem and almost nothing you can do.. :[:[
Is RMA an option or not at all?
I'm essentially out of Software related ideas tbh, and you've been wonderful about doing things right :/
Anyone else have any ideas?
EDIT: May want to do this just in case --
Lethe6 said:
The usual... uninstall and delete the drivers, reinstall the recommended one (the universal naked drivers), and try again. Do this even if everything appears ok, there still may be corruption of some sort, like chkdsk messing up a driver file or moving it, etc.
Click to expand...
Click to collapse

I had an issue like that but it turned out to be a faulty cord. Not saying that's your issue but it is a possibility.
Sent from my Transformer TF101 using xda premium

Thing O Doom said:
I'm starting to think that the eMMC is bad/Faulty chip. Which would mean a hardware problem and almost nothing you can do.. :[:[
Is RMA an option or not at all?
I'm essentially out of Software related ideas tbh, and you've been wonderful about doing things right :/
Anyone else have any ideas?
EDIT: May want to do this just in case --
Click to expand...
Click to collapse
Thank you for your help :highfive: but RMA is no option for me.
Either I find a way to install a rom and boot from the external SD card or I must take the tablet out of operation, the repertory is too expensive ...
Some time ago I read a post of Prime Transformer where the vold.fstab file was modified, and the system ran on the sd card
but I dont find the Post currently
I will post my next steps further and if you should still have an idea what I could do, I'm grateful for any tip

The thing about that is you would need to modify the bootflags to get it to do boot from the sd card, and I'm not sure you can do that with your tab in it's current state :c

Thing O Doom said:
The thing about that is you would need to modify the bootflags to get it to do boot from the sd card, and I'm not sure you can do that with your tab in it's current state :c
Click to expand...
Click to collapse
Can you specify how can I do that?
Meanwhile I started the Tablet in TWRP Recovery and use adb with folowing commands
C:\android\adb>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30203904 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 28563968 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
~ # ←[6nfdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT di
sklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
The number of cylinders for this disk is set to 943872.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 30.9 GB, 30928797696 bytes
4 heads, 16 sectors/track, 943872 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
~ # ←[6nfdisk -l -u /dev/block/mmcblk0
fdisk -l -u /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 30.9 GB, 30928797696 bytes
4 heads, 16 sectors/track, 943872 cylinders, total 60407808 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table ???
C:\android\adb>adb shell
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,
data=ordered)
/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,barrier=1,data=ordered)

[Q] Problem flashing Elocity A7

Wanted to post this in the elocity section but not taking new threads. I have an elocity A7 (not plus). had it for a few years, always worked great, used
sparingly. from day one had it flashed to dexter's 1.41 rom. never had a problem. it has been sitting for a while
and I decided to break it out. charged it up and booted. nothing but force close errors. nothing really works.
tried to reflash with dexter and also with original rom. both go through the motions but after it reboots it's
exactly the same, no changes made. have gone into privacy menu and did a factory reset. same thing, goes through
the motions but after it reboots it's exactly the same. tried to uninstall programs using app manager. they
apprear to be gone but after a reboot they magically re-appear!! tried to use file manager to delete and same
thing. it's like it write protected or something. I used the elocty "restore from PC" batch file/imager and here
is what I get:
C:\Users\Snake\Documents\A7-restore-from-pc\A7 restore from PC\nvflash_windows_2
.2\image>..\nvflash.exe --bct flash.bct --setbct --configfile android_froyo_fas
tboot_emmc.cfg --create --odmdata 0xC0075 --bl bootloader.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x02804145445fa517
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xc0075
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 937544/937544 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: NVC
creating partition: SOS
creating partition: LNX
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: ER1
creating partition: UDA
creating partition: ER2
creating partition: SDC
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x2 (0x2) flags: 0
so I'm guessing that the "failed" part is the main problem, lol. anyone have ideas? I want get this going in a
big way. My thought after seeing that was the flash ram had gone bad, but it was literally just sitting unused...I
don't see how it could have gone bad from sitting. if it does have bad sectors say, is there any utility like they
have fro hard drives that can map those areas? looking for serious help here from real experts, I think I have
gone though all the basics. Help MUCH appreciated. Thanks in advance