[TOOL]TF201 NVFLash [Updated 21. July]

---

After much hard work and scary semi-bricks, we are proud to finally provide nvflash to the masses!

This release allows unlocked devices to create a set of device-specific files that lets you access nvflash.

Once the procedure is done, you will always be able to recover any software brick (even bootloader!) as long as you keep your files safe!

NOTE: THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES

More details at http://androidroot.mobi/?p=452

Important note: We kind of forgot to clarify what the license for wheelie was so here goes. Due to the nature of wheelie and the importance of people always using the latest version, Wheelie is NOT redistributable! You are allowed to download it and use it, but you are not allowed to redistribute it in any way - this means no GUI's including it, no reposting zips/tar.gz's and similar! At a later date, we will be releasing our source code and relicense it as GPL.

Update log:

1. 18. July: Added windows version!
2. 21. July: Clarify License

Enjoy
- AndroidRoot.Mobi Team

NOTE: If anyone wishes to donate, http://androidroot.mobi/donations/ is place to do it! DO NOT DONATE DIRECTLY TO ME.

Dude... exactly what I need. You are awesome.

I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.

Originally Posted by williemeiser

I already bricked my TF201, stucked at eepad screen. =(
Can this method be used to recover? ex: anybody providing their blob and other necessary files so i can nvflash it? pleasee?? T_T
I can access fastboot though.

Nobody else can provide their blobs to other users, Each device has a different SBK making them incompatible with other devices.

however, you are not "bricked" if you can access fastboot, you have enough access to perform what is required

Originally Posted by lilstevie

Nobody else can provide their blobs to other users, Each device has a different SBK making them incompatible with other devices.

however, you are not "bricked" if you can access fastboot, you have enough access to perform what is required

Is it? Maybe Im just too nervous. but I cant access recovery. Even when i flashed it in fastboot,still i cannot access it. N im running out of ideas,

Originally Posted by williemeiser

Is it? Maybe Im just too nervous. but I cant access recovery. Even when i flashed it in fastboot,still i cannot access it. N im running out of ideas,

you could try fastboot boot recovery.img (where you have a cwm image named recovery.img) and see if that boots, if that doesn't work it is probably a hardware issue.

are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?

Originally Posted by demandarin

are there any plans to make this more automated in a form of something like Vipercontrol exe. or something?

Tbh... If you don't have the ability to follow the simple instructions then you have no business attempting this process at all...

Originally Posted by kmdm

Tbh... If you don't have the ability to follow the simple instructions then you have no business attempting this process at all...

good one.

I knew someone was going to say that..lol. just like rooting methods and other tweaks, a more simpler automated way usually arrives. I have no problem with this but I'm sure alot of others might.

time will tell. I'm sure this will be cooked up into an app/exe.

its all good though

Originally Posted by demandarin

good one.

I knew someone was going to say that..lol. just like rooting methods and other tweaks, a more simpler automated way usually arrives. I have no problem with this but I'm sure alot of others might.

time will tell. I'm sure this will be cooked up into an app/exe.

its all good though

I cannot speak for the others but I personally would not be impressed with this outcome. It is not like other rooting methods and other tweaks, this carries a high brick risk. One-clicks and all those types of installers trivialize the risk that we are trying to make users aware of. Making someone read the instructions gives us the opportunity to really reinforce the risk that you are undertaking.