After running sh ./nvflash_gtablet.sh I get this message
Flashing G Tablet with base images...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17141188423f3217
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. /usb read error (71): Protocol error
done!
failed executing command 14 NvError 0x8
command failure: create failed
Done!
Please help, what do I do next!
Thanks
hguled
hguled said:
After running sh ./nvflash_gtablet.sh I get this message
Flashing G Tablet with base images...
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17141188423f3217
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. /usb read error (71): Protocol error
done!
failed executing command 14 NvError 0x8
command failure: create failed
Done!
Please help, what do I do next!
Thanks
hguled
Click to expand...
Click to collapse
try using the other recovery , the one named nvflash_gtablet_2010110500
nvflash_gtablet_2010110500 Failing
I downloaded nvflash_gtablet_2010110500.zip from dropbox , after unzip all I get is 'nvflash_gtablet.sh'. I Am downloading a wrong version.
I Appreciate your reply
hguled,
What operating system are you using?
The nvflash_gtablet_2010110500.zip is for Windows.
The file nvflash_linux_2010110500.tar.gz is for Linux.
If you have questions, check out the "NVFlash" STICKY thread near the
start of the Developer forum.
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.
Hey guys, Thanks for any help you can provide in advanced.
Here is the status of my transformer:
It wont do anything except go into apx mode. If i try to go to recovery, It simply goes to apx instead. I can't get it to do anything else. The screen is always black except when i try to fix with nvflash in which case text appears on the upper left that says :
"Entering NvFlash recovery node/nv3p Server
Chip Uid : [some random numbers]
!!!!!phone update succes!!!!!"
I tried following ThingODoom's instructions here
transformerforums[dotcom]/forum/asus-transformer-development/24512-solved-oh-gawd-i-think-ive-bricked-my-tf-2.html#post203094
to recover with nvflash, but it always gets stack at "Formatting Partition 15 UDA." no progress after that.
Here is the output
Code:
"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: 0x251199401177940311
[=] 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\Alan Castro\AppData\Local\Temp\Rar$EXa0.402\tmpboot>"nvflash.exe" -r --
bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d801
1 --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.. \
Am I screwed? Any help would be appreciated
Well. It turns out I didn't wait long enough at the "Formatting partition 15 UDA" step. Since all the other ones took under 15 seconds, it worried me when #15 was taking longer than 10 minutes, so I always stopped it at that point. Turns out I had to wait 15+ minutes. Everything worked out.
Thank you
Patience is a virtue...
Sent from my Transformer TF101 using xda app-developers app
Hey guys, I'll try to keep it short and get to the parts that really matter, but any help would really be appreciated.
Long story short, wanted to get onto Jellybean with my B60 TF101.
Started with easyflasher since that seemed like the quickest way to get setup. Couldn't get it working because I had not yet installed APX drivers, but not knowing that yet I moved on to 1 Click transformer root. At this point I discovered the APX drivers were not installed and installed the Universal Naked drivers. Still could not get 1 Click transformer root to work and so I returned to easy flasher. Tried to flash recovery to Roach CWM, but did not work. I figured alright, at this point I will just flash to stock to see if working with a clean slate would help. Flashed to stock using easyflasher and the latest firmware off ASUS website, but it failed. I now am only able to get into APX mode and after running easyflasher a number of times hoping it would fix it to no avail I did some searching and found a few similar threads.
This seemed closest to what I was experiencing, but after going through the thread I could not get anything to work. And that's where I am. I ran Brk's ASUS transformer root, installed the drivers from that thinking maybe the ones I had installed weren't the best and ran the stock flashing section and I still end up in the same place. I'm entirely new to this so pardon my ignorance, but any help would be greatly appreciated.
Thanks in advance.
Here's the log from the last run of Brk's Root Toolkit
Code:
C:\Users\User\Desktop\BRK_RootKit_v8.0_final\tmpboot>cd C:\Users\User\Desktop\BR
K_RootKit_v8.0_final\tmpboot\
C:\Users\User\Desktop\BRK_RootKit_v8.0_final\tmpboot>"wheelie.exe" -1 --bct tran
sformer.bct --bl bootloader.bin --odm 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: 0x252308537800151895
[=] 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\User\Desktop\BRK_RootKit_v8.0_final\tmpboot>"nvflash.exe" -r --bct tran
sformer.bct --setbct --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
| 983040/1454712 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
C:\Users\User\Desktop\BRK_RootKit_v8.0_final\tmpboot>"nvflash.exe" -r --go
Nvflash started
[resume mode]
At that point what is on the screen is:
Chip UID: Numbers
!!! Phone update succeeded !!!
!!! Phone update failed!!!
EDIT: Problem solved. Switched to USB port on back of computer and ran reflash_sbkv1.bat included with brk's root toolkit and it worked. After that just started up the toolkit and reflashed the firmware from the GUI and i'm back in business. Not sure which part was the important one, but maybe this will help someone else.
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)