[NvFlash] [Recovery] With [Generated Blobs][TF-700-T]

Was this forum helpful

  • YES

    Votes: 16 94.1%

  • NO

    Votes: 1 5.9%
  • Total voters
    17
Status
Not open for further replies.
Search This thread
By:
Advanced…
H

hspowerz

New member
Jun 20, 2012
2
1
Successfully saved blob

With this guide and some real time help i successfully saved my blobs thank god now im good with my TF201 ;)
 
  • Like
Reactions: lj50036
H

Hanbal

New member
Dec 12, 2014
1
1
Thanks

Hi,

Thank you very much for the great tutorial and for the clear and easy to follow explanations.
The method is working like a charm for T201 as well.
:)

lj50036 said:
This is a general users guide to unbricking your tf700t...

This is only what I did, It was successfull for me.
I did this on linux mint 32 bit, so thats what I can help with. Im sure it can be done on windows but who would want to!!!!!!LOL
I will help anyone that needs it of course... No matter the os... Just let me know!!!!

What you need
Your device specific nvflash backup files generated while enabling nvflash.
!!!!!!!!If you dont have them there is no help for you!!!!!!
  • blob.bin
  • bootloader.ebt
  • unlock-token.img
  • factory-config.img
  • bricksafe.img

    Also needed
  • A tf700t (Its bad now, but all will be ok)
  • Fully charged tf700t (Just plug it in, it will charge no matter what...If not you dont need my help!!!!)
  • Asus data cable
  • Linux Mint 32bit PC
  • Super user permission
  • Stock firmware blob (from asus's web site, make sure you get the right one)
  • nvflash and wheelie
  • And fastboot for your PC

Downloads

nvflash/wheelie-Linux


nvflash/wheelie-Windows


Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR 700


INSTRUCTIONS
Extract wheelie and nvflash to your home folder...
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to your home folder...
Move the above mentioned device specific files to your home folder...

In your home folder you should have
  • blob.bin
  • unlock-token.img
  • factory-config.img
  • bricksafe.img
  • bootloader.ebt
  • nvflash
  • wheelie
  • boot.blob (we renamed it in the last step)

Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode....
Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie....
I am going to show you the outpus of my process

Code: 
sudo ./wheelie --blob blob.bin
lj50036@area51:~ > sudo ./wheelie --blob blob.bin
OUTPUT
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbce2501405
[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

It may shutdown after each command, get back into nvflash with the above steps.....

Code: 
sudo ./nvflash -r --download 7 unlock-token.img
lj50036@area51:~ > sudo ./nvflash -r --download 7 unlock-token.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: unlock-token.img
/ 8388608/8388608 bytes sent
unlock-token.img sent successfully

Code: 
sudo ./nvflash -r --download 14 factory-config.img
lj50036@area51:~ > sudo ./nvflash -r --download 14 factory-config.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: factory-config.img
/ 5242880/5242880 bytes sent
factory-config.img sent successfully

Code: 
sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
lj50036@area51:~ > sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: bricksafe.img
/ 12058624/12058624 bytes sent
bricksafe.img sent successfully

Code: 
sudo ./nvflash -r --go
lj50036@area51:~ > sudo ./nvflash -r --go
OUTPUT
Nvflash v1.13.87205 started
[resume mode]

At this point if it will not reboot or shut down do this
hold power button and volume down to boot into fastboot...You will now have fastboot.
We are not done yet!!! Getting close now!!!!!!

Run these command in fastboot in this order

The next command is to just verify your computer can see your device

Code: 
 fastboot devices
INPUT
lj50036@area51:~ > fastboot devices
OUTPUT
015d2bbce2501405 fastboot


Code: 
 fastboot erase system
INPUT
lj50036@area51:~ > fastboot erase system
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s

Code: 
 fastboot erase recovery
INPUT
lj50036@area51:~ > fastboot erase recovery
OUTPUT
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s

Code: 
 fastboot -w
INPUT
lj50036@area51:~ > fastboot -w
OUTPUT
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...

At this point it just hangs on erasing 'cache'
I just close terminal and open new one, and run the next command
If your tablet hangs just reboot back into fastboot again

Code: 
 fastboot erase boot
INPUT
lj50036@area51:~ > fastboot erase boot
OUTPUT
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s

Code: 
 fastboot erase misc
INPUT
lj50036@area51:~ > fastboot erase misc
OUTPUT
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s

Code: 
 fastboot erase cache
INPUT
lj50036@area51:~ > fastboot erase cache
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s

Code: 
 fastboot -i 0x0B05 flash system boot.blob

During the sending/writing process of this step you will get the blue bar on your screen.....

INPUT
lj50036@area51:~ > fastboot -i 0x0B05 flash system boot.blob
OUTPUT
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s

Code: 
 fastboot -i 0x0B05 reboot
lj50036@area51:~ > fastboot -i 0x0B05 reboot
OUTPUT
rebooting...

finished. total time: 0.020s

You will now be back to stock rom stock bootloader but still unlocked!!!!!!!!!!!!!
Boot fully into rom than you can do whatever you would like!!!!!!!!!!!
Click to expand...
Click to collapse
 
  • Like
Reactions: lj50036
thintin

thintin

Senior Member
Jun 14, 2007
187
6
Shropshire
Flashed first blob but unlock token doesn't do anything

Hi.

I'm restoring my TF201 to its original condition sing the files I saved from nvflash in 2012 when I first bought the tablet.

I've connected in APX mode and flashed the blob.bin, then the tablet rebooted. I went back into APX mode and entered 'nvflash -r --download 7 unlock-token.img' and I get the following:-

NvFlash v1.13.87205 started
[resume mode]

Then it just stays like that!

I've tried to find different versions of nvflash becasue some people report that it helps, but no luck (really hard to find newest Win 7 version for TF201).
I've tried running as administrator: same output.

I'm using Win 7 64bit.

Help?
 
L

lj50036

Senior Member
Feb 14, 2013
3,321
3,297
42
FUXDA
thintin said:
Hi.

I'm restoring my TF201 to its original condition sing the files I saved from nvflash in 2012 when I first bought the tablet.

I've connected in APX mode and flashed the blob.bin, then the tablet rebooted. I went back into APX mode and entered 'nvflash -r --download 7 unlock-token.img' and I get the following:-

NvFlash v1.13.87205 started
[resume mode]

Then it just stays like that!

I've tried to find different versions of nvflash becasue some people report that it helps, but no luck (really hard to find newest Win 7 version for TF201).
I've tried running as administrator: same output.

I'm using Win 7 64bit.

Help?
Click to expand...
Click to collapse

The tablet should not reboot after you run the blob.bin ?

What is the output of the command .....

Code: 
wheelie --blob blob.bin

Thx Josh
 
thintin

thintin

Senior Member
Jun 14, 2007
187
6
Shropshire
lj50036 said:
The tablet should not reboot after you run the blob.bin ?

What is the output of the command .....

Code: 
wheelie --blob blob.bin

Thx Josh
Click to expand...
Click to collapse

Hi Josh.

Firstly, thanks for your help with this. I've tried again and got another problem now.

I've just connected the TF201 in APX mode (universal naked driver) and entered

wheelie --blob blob.bin

the output is:-

Code: 
C:\flashing\nvflash>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x15d0787510fea11
[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

C:\flashing\nvflash>

The TF201 then reboots and on its screen it says:-

NvFlash recovery mode / NvSp Server
Chip UiD: (random string here)
!!!!!device update success!!!!!

Then I entered:

nvflash -r --download 7 unlock-token.img

that worked, so did:-

nvflash -r --download 14 factory-config.img
nvflash -r --rawdevicewrite 0 2944 bricksafe.img

but then when I entered:-

nvflash -r --go

nothing happened.

Following the OP I tried to enter fastboot mode but it doesn't seem to be working. When I hold volume down and power I get:-

OS will boot in 10 secs if the selected mode is not confirmed.

press <vol_down> to change mode,
press<vol_up> to confirm mode.
Platform Pre OS Boot configuration...

No matter which option I select I get:-

Cold-booting Linux

but nothing else happens. When I ask fastboot for devices it doesn't give any output.

???

Phil.
 
Last edited:
L

lj50036

Senior Member
Feb 14, 2013
3,321
3,297
42
FUXDA
thintin said:
Hi Josh.

Firstly, thanks for your help with this.

I've just connected the TF201 in APX mode (universal naked driver) and entered

wheelie --blob blob.bin

the output is:-

Code: 
C:\flashing\nvflash>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Waiting for device in APX mode...
[=] Chip UID: 0x15d0787510fea11
[=] RCM Version: 0x30001

[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

C:\flashing\nvflash>

Phil.
Click to expand...
Click to collapse

The tablet reboots after you run this command ?

Thx Josh
 
thintin

thintin

Senior Member
Jun 14, 2007
187
6
Shropshire
lj50036 said:
The tablet reboots after you run this command ?

Thx Josh
Click to expand...
Click to collapse

I'm assuming it was a reboot, the TF201 screen goes black and then it says:-

NvFlash recovery mode / NvSp Server
Chip UiD: (random string here)
!!!!!device update success!!!!!

but then all of the other nvflash commands worked so I'm guessing it was right?

I've just worked out that the screen with the three icons (wipe data, usb and android) is where you start fastboot (usb icon). the TF201 is now showing up in device manager as 'Asus Android Bootloader Interface', but every fastboot command returns 'access is denied' as the output...
 
L

lj50036

Senior Member
Feb 14, 2013
3,321
3,297
42
FUXDA
thintin said:
I'm assuming it was a reboot, the TF201 screen goes black and then it says:-

NvFlash recovery mode / NvSp Server
Chip UiD: (random string here)
!!!!!device update success!!!!!

but then all of the other nvflash commands worked so I'm guessing it was right?

I've just worked out that the screen with the three icons (wipe data, usb and android) is where you start fastboot (usb icon). the TF201 is now showing up in device manager as 'Asus Android Bootloader Interface', but every fastboot command returns 'access is denied' as the output...
Click to expand...
Click to collapse

Shoot me a hangouts or email at jl52741@gmail.com

When you get some time and if you would like any help looking into this issue ....

Thx Josh
 
thintin

thintin

Senior Member
Jun 14, 2007
187
6
Shropshire
lj50036 said:
Shoot me a hangouts or email at jl52741@gmail.com

When you get some time and if you would like any help looking into this issue ....

Thx Josh
Click to expand...
Click to collapse

Think I sorted it; I tried another version of fastboot I have and it worked! Just waiting for it to finish sending the boot.blob to the system partition...it's taking rather a long time...how long should I wait and what should I do if it's stuck?

It wasn't stuck :(

Code: 
C:\flashing\mini-sdk>fastboot devices
00000   fastboot

C:\flashing\mini-sdk>fastboot erase system
erasing 'system'... OKAY

C:\flashing\mini-sdk>fastboot erase recovery
erasing 'recovery'... OKAY

C:\flashing\mini-sdk>fastboot -w
erasing 'userdata'... OKAY
erasing 'cache'... OKAY

C:\flashing\mini-sdk>fastboot erase boot
erasing 'boot'... OKAY

C:\flashing\mini-sdk>fastboot erase misc
erasing 'misc'... OKAY

C:\flashing\mini-sdk>fastboot erase cache
erasing 'cache'... OKAY

C:\flashing\mini-sdk> fastboot -i 0x0B05 flash system boot.blob
error: cannot load 'boot.blob'


C:\flashing\mini-sdk> fastboot -i 0x0B05 flash system boot.blob
sending 'system' (537604 KB)... OKAY
writing 'system'... FAIL(InvalidSize)
FAILED (remote: (InvalidSize))

C:\flashing\mini-sdk>
 
Last edited:
L

lj50036

Senior Member
Feb 14, 2013
3,321
3,297
42
FUXDA
thintin said:
Think I sorted it; I tried another version of fastboot I have and it worked! Just waiting for it to finish sending the boot.blob to the system partition...it's taking rather a long time...how long should I wait and what should I do if it's stuck?
Click to expand...
Click to collapse

The time it took for mine are posted in the OP ....

Not sure why it would be stuck, I was not there for what you did .... :D

Thx Josh
 
thintin

thintin

Senior Member
Jun 14, 2007
187
6
Shropshire
lj50036 said:
The time it took for mine are posted in the OP ....

Not sure why it would be stuck, I was not there for what you did .... :D

Thx Josh
Click to expand...
Click to collapse

Sorry, edited last post before I noticed your reply.

It's saying that the blob is too big...

Code: 
C:\flashing\mini-sdk> fastboot -i 0x0B05 flash system boot.blob
sending 'system' (537604 KB)... OKAY
writing 'system'... FAIL(InvalidSize)
FAILED (remote: (InvalidSize))
 
thintin

thintin

Senior Member
Jun 14, 2007
187
6
Shropshire
thintin said:
Sorry, edited last post before I noticed your reply.

It's saying that the blob is too big...

Code: 
C:\flashing\mini-sdk> fastboot -i 0x0B05 flash system boot.blob
sending 'system' (537604 KB)... OKAY
writing 'system'... FAIL(InvalidSize)
FAILED (remote: (InvalidSize))
Click to expand...
Click to collapse

Okay. After many hours of googling and experimenting I'm almost there.

I had to unpack the blob file that I got from ASUS and write the individual partitions using nvflash. They're all done apart from the system image file blob.APP. This file starts copying but then the connection drops before it's finished writing. I've tried several times and each time it copies less before it disconnects. I think the battery on the TF201 may be flat so I've plugged it in and I'll wait 30 mins and try again.
 
O

orenwww

New member
May 29, 2015
2
0
need help I bricked my TF700

Tried to recover from brick, I don't get bootloadrer.
I reflashed the bootloder but nothing works so far

I got the files:
blob.bin
bootloader.ebt

I'm missing the files
unlock-token.img
factory-config.img
bricksafe.img

any chance to save my tablet ?
 
L

lj50036

Senior Member
Feb 14, 2013
3,321
3,297
42
FUXDA
orenwww said:
Tried to recover from brick, I don't get bootloadrer.
I reflashed the bootloder but nothing works so far

I got the files:
blob.bin
bootloader.ebt

I'm missing the files
unlock-token.img
factory-config.img
bricksafe.img

any chance to save my tablet ?
Click to expand...
Click to collapse

We may be able to do something, I will need a bit more ....

Send me a hangouts at jl52741@gmail.com

Thx Josh
 
  • Like
Reactions: Al-Man
Status
Not open for further replies.

Similar threads

workdowg
Kexecboot on the TF700t(TF700t-AKBI v2.6.8)
Replies
1K
Views
303K
gardiol
gardiol
rickymh19
ASUS TF700T unlock and root JB 4.2.1 stock
Replies
599
Views
325K
yongyek
yongyek
R
[TOOL][BRICKPROOF]TF700 NVFlash release!
Replies
418
Views
142K
berndblb
berndblb
sbdags
[ROM]&#9733;[TF700 LP 5.1.1/6.0.1][ZOMBi-POP OMNI KANG RC2][Mar 21]&#9733;
Replies
4K
Views
817K
yongyek
yongyek
Dees_Troy
[RECOVERY][TF700T] TWRP 3.1.1-0 touch recovery [2017-05-19]
Replies
682
Views
264K
yaseen.soror
yaseen.soror

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 23
    L
    lj50036
    This is a general users guide to unbricking your tf700t...

    This is only what I did, It was successfull for me.
    I did this on linux mint 32 bit, so thats what I can help with. Im sure it can be done on windows but who would want to!!!!!!LOL
    I will help anyone that needs it of course... No matter the os... Just let me know!!!!

    What you need
    Your device specific nvflash backup files generated while enabling nvflash.
    !!!!!!!!If you dont have them there is no help for you!!!!!!
    • blob.bin
    • bootloader.ebt
    • unlock-token.img
    • factory-config.img
    • bricksafe.img

      Also needed
    • A tf700t (Its bad now, but all will be ok)
    • Fully charged tf700t (Just plug it in, it will charge no matter what...If not you dont need my help!!!!)
    • Asus data cable
    • Linux Mint 32bit PC
    • Super user permission
    • Stock firmware blob (from asus's web site, make sure you get the right one)
    • nvflash and wheelie
    • And fastboot for your PC

    Downloads

    nvflash/wheelie-Linux
    click me

    nvflash/wheelie-Windows
    click me

    Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR 700
    click me

    INSTRUCTIONS
    Extract wheelie and nvflash to your home folder...
    Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to your home folder...
    Move the above mentioned device specific files to your home folder...

    In your home folder you should have
    • blob.bin
    • unlock-token.img
    • factory-config.img
    • bricksafe.img
    • bootloader.ebt
    • nvflash
    • wheelie
    • boot.blob (we renamed it in the last step)

    Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode....
    Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie....
    I am going to show you the outputs of my process ....
    If you are running windows drop the 'sudo ./' and make sure your CMD window is opened as admin

    Code: 
    sudo ./wheelie --blob blob.bin
    lj50036@area51:~ > sudo ./wheelie --blob blob.bin
    OUTPUT
    Wheelie 0.1 - Preflight for nvflash.
    Copyright (c) 2011-2012 androidroot.mobi
    ========================================

    Waiting for device in APX mode...
    [=] Chip UID: 0x15d2bbce2501405
    [=] RCM Version: 0x30001

    [=] CPU Model: Tegra 3
    [+] Sending bootloader...
    Sending file: 100 %
    [!] Done - your device should now be ready for nvflash

    It may shutdown after each command, get back into nvflash with the above steps.....

    Code: 
    sudo ./nvflash -r --download 7 unlock-token.img
    lj50036@area51:~ > sudo ./nvflash -r --download 7 unlock-token.img
    OUTPUT
    Nvflash v1.13.87205 started
    [resume mode]
    sending file: unlock-token.img
    / 8388608/8388608 bytes sent
    unlock-token.img sent successfully

    Code: 
    sudo ./nvflash -r --download 14 factory-config.img
    lj50036@area51:~ > sudo ./nvflash -r --download 14 factory-config.img
    OUTPUT
    Nvflash v1.13.87205 started
    [resume mode]
    sending file: factory-config.img
    / 5242880/5242880 bytes sent
    factory-config.img sent successfully

    Code: 
    sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
    lj50036@area51:~ > sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
    OUTPUT
    Nvflash v1.13.87205 started
    [resume mode]
    sending file: bricksafe.img
    / 12058624/12058624 bytes sent
    bricksafe.img sent successfully

    Code: 
    sudo ./nvflash -r --go
    lj50036@area51:~ > sudo ./nvflash -r --go
    OUTPUT
    Nvflash v1.13.87205 started
    [resume mode]

    At this point if it will not reboot or shut down do this
    hold power button and volume down to boot into fastboot...You will now have fastboot.
    We are not done yet!!! Getting close now!!!!!!

    Run these command in fastboot in this order

    The next command is to just verify your computer can see your device

    Code: 
     fastboot devices
    INPUT
    lj50036@area51:~ > fastboot devices
    OUTPUT
    015d2bbce2501405 fastboot


    Code: 
     fastboot erase system
    INPUT
    lj50036@area51:~ > fastboot erase system
    OUTPUT
    ******** Did you mean to fastboot format this partition?
    erasing 'system'...
    OKAY [ 2.954s]
    finished. total time: 2.954s

    Code: 
     fastboot erase recovery
    INPUT
    lj50036@area51:~ > fastboot erase recovery
    OUTPUT
    erasing 'recovery'...
    OKAY [ 1.945s]
    finished. total time: 1.945s

    Code: 
     fastboot -w
    INPUT
    lj50036@area51:~ > fastboot -w
    OUTPUT
    erasing 'userdata'...
    OKAY [ 23.188s]
    formatting 'userdata' partition...
    Creating filesystem with parameters:
    Size: 29618601984
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 7231104
    Block groups: 221
    Reserved block group size: 1024
    Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
    sending 'userdata' (139133 KB)...
    writing 'userdata'...
    OKAY [ 26.358s]
    erasing 'cache'...

    At this point it just hangs on erasing 'cache'
    I just close terminal and open new one, and run the next command
    If your tablet hangs just reboot back into fastboot again

    Code: 
     fastboot erase boot
    INPUT
    lj50036@area51:~ > fastboot erase boot
    OUTPUT
    erasing 'boot'...
    OKAY [ 1.209s]
    finished. total time: 1.209s

    Code: 
     fastboot erase misc
    INPUT
    lj50036@area51:~ > fastboot erase misc
    OUTPUT
    erasing 'misc'...
    OKAY [ 0.978s]
    finished. total time: 0.978s

    Code: 
     fastboot erase cache
    INPUT
    lj50036@area51:~ > fastboot erase cache
    OUTPUT
    ******** Did you mean to fastboot format this partition?
    erasing 'cache'...
    OKAY [ 2.843s]
    finished. total time: 2.843s

    Code: 
     fastboot -i 0x0b05 flash system boot.blob

    During the sending/writing process of this step you will get the blue bar on your screen.....

    INPUT
    lj50036@area51:~ > fastboot -i 0x0B05 flash system boot.blob
    OUTPUT
    erasing 'system'...
    OKAY [ 2.339s]
    sending 'system' (800927 KB)...
    OKAY [133.094s]
    writing 'system'...
    [OKAY [178.036s]
    finished. total time: 313.469s

    Code: 
     fastboot -i 0x0B05 reboot
    lj50036@area51:~ > fastboot -i 0x0B05 reboot
    OUTPUT
    rebooting...

    finished. total time: 0.020s

    You will now be back to stock rom stock bootloader but still unlocked!!!!!!!!!!!!!
    Boot fully into rom than you can do whatever you would like!!!!!!!!!!!
    View
    3
    C
    Chazzfazzle
    My problem ended up being the nvflash distro from androidroot.mobi. I don't know if it is broken or just incompatible with my system. I ended up finding a working (worked for me anyway) version from nvidia directly. It's part of the Linux Developer Kit.

    Get it here: https://developer.nvidia.com/linux-tegra

    Make sure you only, and I can't stress this enough, make doubly sure you only get the Cardhu Driver Pack. NvFlash is located in the bootloader folder of the archive. I replaced androidroot.mobi's version with this and the rest is history. Hope this helps.

    Also I did this on Ubuntu 12.04.3. I see you are on the latest release. I seriuosly doubt that makes any difference but, the more you know...
    View
    3
    L
    lj50036
    Mine
    View
    3
    das chaos
    das chaos
    SUCCESS!

    After about a hundred tries, bootloader was installed by nvflash again with
    Code: 
    nvflash --setbct --create --configfile flash.cfg --bl bootloader.ebt --bct recovery.bct --blob blob.bin

    Don' know what I did different this time, but tab is alive again.
    Everything in place as before: Recovery, kernel, everything! Seems that my nvflashing with several configurations did not change anything except fixing the bootloader.
    View
    2
    T
    _that
    Chazzfazzle said:
    So I got Ubuntu up and running and I have the adb and fastboot drivers installed. I also dl'ed the linux wheelie and nvflash files. The computer can see my device when I run fastboot devices command but it won't run wheelie from the directory I created for it. Where do I put my files so the terminal can run them?
    Click to expand...
    Click to collapse

    Linux does not run programs in your current directory by default, for security reasons. To run wheelie from your current directory, type "./wheelie".
    View

New posts