Nvflash-based recovery based on TnT Lite 2.2.0

---

As always, USE AT YOUR OWN RISK. You should a fundamental understanding of how nvflash functions - if you do not, I would not recommend attempting this!

1.0.2 Link (based on TnT Lite 2.2.0): http://www.mediafire.com/?5c7is1eld6j9i6d#1
Alternative link: http://www.megaupload.com/?d=7ROU81O0
md5sum : ee3f346e602437b6a1be2336acb0b3ae

References: http://wiki.tegratab.com/index.php/N...ering_APX_Mode
http://forum.tegratab.com/viewtopic.php?f=6&t=8

So Why Did You Do This?

My reason for building this out was to have a newer baseline in case I needed to wipe the device using nvflash - I was just sick of seeing the TnT homescreen each time.

So What's Different in This?

- Malata bootloader with a Tegra boot image (you'll see that on bootup). Thanks to rothnic for the pic!
- Clockworkmod .08.
- Changes to ramdisk to allow adb remount to work.
- TnT Lite 2.2.0 baseline.
- NOT an update.zip. this is a compressed nvflash folder with the Windows DLL's and Linux .so's added. I have tested this on Linux only, the Windows stuff I grabbed from Malata.


So How Do I Use This?

You should have a fundamental understanding of how nvflash works, and how it could bork your system if you're not careful. I've run this several times today, but there is speculation that some devices may have a different partition structure. I'm just releasing this as an option to you, if you choose to use. But it's at your own risk!!!!!!!! Bekit has actually suggeted that you just flash things like boot and system manually (and as seen in the the tegratab link) and that might not be a bad idea. But, that would not inlude the bootloader changes.

USE AT YOUR OWN RISK, YOU HAVE BEEN WARNED
For Linux users (which is how I tested): Expand this out, open up a terminal session as root to that folder. Connect your device in APX mode. Then, run this command:

LD_LIBRARY_PATH=. ./nvflash --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go

This will wipe the bootloader, kernel and system, and then reboot. It will not wipe data.

Once it reboots, you might get a UID error - if so, reboot into clockworkmod and then fix permissions. That should correct it.

EDIT: A post that might help out Windows users: http://forum.xda-developers.com/show...0&postcount=28


Again, be very very careful with this - if I'm being redundant it's because it's important to understand what you are doing.

EDIT: 1.0.1+ versions downlevel clockworkmod back to .08, and fixes the VOLD issue. Two annoyances that I felt required a new version.

----------------------------------------------------

Archives:

1.0.1 Link: no longer needed
1.0.0 Link (based of of TnT Lite 2.0.2 + performance pack): http://www.mediafire.com/?hd6aal4857h567h
md5sum: e127b529021c4479bae5c6170c73dbd9

Soooo...
Let me see if I understood.
Compared to the previous post on TegraTab adding both folders together and then runing the bat file to the bootloader I can substitute the content of the zip instead and have TnT2.0.2 with Vega x-pack?
Also I noticed that there were 2 folders for USB Drive including one x64. Do I keep on the original format outside the folders? Or leave as it is when extracted?

Thanks

PS. Dude the moment I get the "how to install " this image this is gold in my hands
Thank you sooo much for your work bro

Edit: Just noticed the lack of a nvflash bat file. Can I use the original one?

Please, help me to understand the benefits of this new bootloader and ADB mounting?

Honestly, I have no clue how to run this in Windows. It's probably similar syntax to what I posted for Linux.

I'm not sure if previous batch files would work, as the syntax is actually different, I believe. Look at the bct and cfg file, for example - those are different than what bekit used.

This is actually 95% Malata, I just replaced the system.img and boot.img files.

Originally Posted by flipper9

Please, help me to understand the benefits of this new bootloader and ADB mounting?

bootloader has no real benefit, other than having a different boot image.

adb remount is nice because it makes things easier if you are using ADB to make changes to /system. It's like full su acess wihout all the workarounds.

I'm having a problem on mine getting stuck in APX mode after doing the full recovery. Was trying this file you just put up and it gets stuck at;

flash.bct sent successfully

Never goes any further.

How did you ultimately unbrick yours? Anyone have an original image I can push?

Originally Posted by cahiatt

I'm having a problem on mine getting stuck in APX mode after doing the full recovery. Was trying this file you just put up and it gets stuck at;

flash.bct sent successfully

Never goes any further.

How did you ultimately unbrick yours? Anyone have an original image I can push?

I've been using the original Bekit nvflash recovery, which is very similar to this one except it's vanilla 1.0.0 stock (mostly). His dump always worked for me -- https://www.dropbox.com/s/wrcd87u1iy...2010110500.zip

Have actually done both of them (but which is the proper one). They will flash correctly and the system will boot. But when I turn it off it goes into APX mode and will not turn back on again. Have to reflash again. If I turn it off it is back in APX.

I've been following along with the TnT Lite adventures. I did this and it worked fine. Thanks for making the gtablet a very usable device. I'm not sure I will keep the performance pack, but there's a tremendous difference.

Originally Posted by cahiatt

Have actually done both of them (but which is the proper one). They will flash correctly and the system will boot. But when I turn it off it goes into APX mode and will not turn back on again. Have to reflash again. If I turn it off it is back in APX.

Try unplugging the tablet and power cycling a few times. Once you're in APX mode, the device will go back to APX mode just from doing a recovery reboot as long as the power supply remains plugged in.

I'm not 100% sure if this is what is happening in your case since it still really shouldn't happen unless you specificially request a recovery reboot, but try unplugging the tablet after the APX flash if you haven't tried that yet.