[Q] Installing ROM to save a bricked G2x - T-Mobile LG 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.

Related

[Q] nvflash_gtablet, cannot start

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.

[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] TF101 Beyond Bricked?

Here's the situation:
TF101
B70
SBK- Unknown, seems to be 2 based on results
Android Version- 4.0.3
I decided that I wanted to install Ubuntu as a dual boot option. Gathered all of the materials as described in http://forum.xda-developers.com/showthread.php?t=1364095. After about 45 minutes on the "uploading Ubuntu" screen, I hit the install button again as it seemed to not be having any effect. Now, although the computer can tell that a usb device is plugged in, my TF101 will not boot or even show any light from the screen. On canceling, I got the following output.
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: UBT
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 UBT please wait.. done!
Formatting partition 17 GPT please wait.. done!
done!
sending file: bootloader.bin
bootloader.bin sent successfully
sending file: linux.img
linux.img sent successfully
sending file: boot.img
boot.img sent successfully
sending file: system.img
system.img sent successfully
sending file: ubuntu.img
data send failed NvError 0x30012
command failure: create failed
What can I do? Really feeling bad about this one.
Any ideas?
Run it again, this time leave it alone...if it was SBK2 it would have failed much earlier in the process.
luna_c666 said:
Run it again, this time leave it alone...if it was SBK2 it would have failed much earlier in the process.
Click to expand...
Click to collapse
Just tried again and got this output:
"Command send failed (usb write failed)
rcm version 0X0"
XslayaX said:
Just tried again and got this output:
"Command send failed (usb write failed)
rcm version 0X0"
Click to expand...
Click to collapse
Ran again with a different, apparently NVFlashable ROM and succeeded. Thanks for the help!

[Help Please] :(

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

[Solved]New to tinkering and already bricked

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.

Categories

Resources