Related
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/Nvflash_FAQ#Entering_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:
Code:
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/showpost.php?p=9564270&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.
flipper9 said:
Please, help me to understand the benefits of this new bootloader and ADB mounting?
Click to expand...
Click to collapse
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?
cahiatt said:
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?
Click to expand...
Click to collapse
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/wrcd87u1iy31u4e/nvflash_gtablet_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.
cahiatt said:
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.
Click to expand...
Click to collapse
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.
download.bat
thx69 said:
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?
Click to expand...
Click to collapse
Is this it... download.bat was inside the package ---> "nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go
catttman said:
Is this it... download.bat was inside the package ---> "nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0xbb0c0011 --create --go
Click to expand...
Click to collapse
That should work, but be very very careful.....
Any noob friendly windows instructions?
Hey Roeby, please do not ever forget about us common folks who can not get nvflash working on their pooters
Even worse case, I was able to put CW on a micro sd, remap command and get back up through interrupting the boot-loop and forcing isntall of CW.
Now have a full CW back up of current TnT Lite 2.0 and the Nvidia 2.03 patch .. all 900mb of it (lot of apps).
I'm not planning to go to nvflash online, anytime soon. This was just a restore point for myself that I wanted to pass on.
Already used it, this morning - I found out that clockworkmod .12 sometimes give you that mismatch error, so I had my nvflash restore image to fix it.
roebeet said:
That should work, but be very very careful.....
Click to expand...
Click to collapse
I will report back tonite after I flash it
I like useing Nvflash ...saved me a lot
and shooting my apk,s back on with adb... fast and clean
Ok, I used windows to flash roebeet's backup. It was scary at first but then got better.
I initially blindly used the Download.bat file, just because it looked good. It finished successfully but I couldn't get the device to boot past the "Malata" screen. I couldn't get into recovery mode either. I was a little scared.
I put the device back into apx mode and then edited the Download.bat file so that it was just this...
"nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go"
I removed this piece " --odmdata 0xbb0c0011" Not sure what exactly it does but it wasn't in the linux command roebeet posted.
After that it worked and everything booted up normally. I'm still testing but it is looking good.
Going to have a 1.01 version of this, soon. The VOLD issue I found affects this, as well.
EDIT: Uploaded. VOLD issue fixed, and downleveled cwm back to .08 due to the "Mismatch errors" when flashing boot.img files that are not padded.
all went well
working as told... Nice
flashed 1.01 version s
Is the Camera fixed yet
Can not get into APX mode. Tried vol -/pwr, then vol + and wait for the droid with !, then vol+/pwr. Never brings up APX in device manager.
Same problem here. I have used NVflash a few weeks ago, so it did work at that moment, and I saw it in the Device Manager. But now I can't get my Transformer in APX anymore, nothing to see in the Device Manager. Somebody can help me with that?
Update :
- Find the Nvidia USB APX drivers (Google it!)
- Hold Volume+ AND Volume- AND Power at the same time.
This will bring the Transformer in APX mode.
It worked for me!
Pierre118 said:
Same problem here. I have used NVflash a few weeks ago, so it did work at that moment, and I saw it in the Device Manager. But now I can't get my Transformer in APX anymore, nothing to see in the Device Manager. Somebody can help me with that?
Update :
- Find the Nvidia USB APX drivers (Google it!)
- Hold Volume+ AND Volume- AND Power at the same time.
This will bring the Transformer in APX mode.
It worked for me!
Click to expand...
Click to collapse
how exactly did u install the apx drivers? sorry im a noob
NoctMonster said:
how exactly did u install the apx drivers? sorry im a noob
Click to expand...
Click to collapse
1. Plug the device on the computer
2. Put the device in APX
3. Go into device manager, find the NVIDIA thing
4. Manually install drivers with the nvflash.zip package
5. done.
i try to put the device in apx but nothing appears on the computer.
I had the same problem as you and all, but now i try to unbrick it and as soon as i connect the device to the computer, it turns on and stays stuck on the boot screen unless i turn it off. and if i try to turn it on in APX mode, nothing seems to happen, the device doesnt turn on and nothing appears on the computer.
After your TF is plugged into the PC...just keep holding down the power button until you are sure the TF is off....it took a LOOOONNNGGG time when mine was bootlooped and I had to try it several times but finally it happened.
then on your PC; open up device manager and tree-out the USB part to see if the NVidia drivers are showing...if not....no problem.
Hold down the power button and the volume+ button for at least 5 or 6 seconds...you should see your device manager refresh with the information.
When that happens; you are now in APX mode. if you accidentally hit the power/volume+ again...it will toggle you OUT of APX mode. No problem, just hit the buttons again and you are toggled back in.
Have patience...it will work.
i jusr got into apx mode thi morning you just need toue device manager and force install the usb drivers u download.
This post is really jst a testfor Tapa.
Sent from my Transformer TF101 using Tapatalk
detects usb and i can see it in device manager.
but when i go to start a download.bat file i get error
"failed exectuing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition <code:10> message: 0x3 <0x3>flags:0"
anyone else get this?
detects usb and i can see it in device manager.
but when i go to start a download.bat file i get error
"failed exectuing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition <code:10> message: 0x3 <0x3>flags:0"
anyone else get this?
Click to expand...
Click to collapse
Are you in apx mode with the nvidia apx drivers?
AustinMartin said:
Are you in apx mode with the nvidia apx drivers?
Click to expand...
Click to collapse
thats where im unsure. i use to get a little window pop-up saying im in boot mode.
now once i plug in the usb and the TF , i can see the "Nvidia boot.." in the device manager pop up. but when i go to my cmd prompt and start download.bat i get the errors, it looks like its gonna start but then the error pops up.
I've flashed twice before no problems, this time ...problems, the unit won't power on, or reboot.
did i brick it??
C:\tf101\nvflashtf>download
C:\tf101\nvflashtf>cd C:\tf101\nvflashtf\
C:\tf101\nvflashtf>"nvflash.exe" --bct transformer.bct --setbct --configfile fla
sh.cfg --create --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A
43EA 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: 0x027c1000419f6517
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: bootloader.bin
| 943193/943193 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
3 (0x3) flags: 0
Well, putting wthe firmware flash on me sd card and flashing the zip tseemed to work
Im trying to revert to stock recovery so i can fully revert to stock and take the 4.1.1 OTA. For some reason when i try to flash the stock recovery img from fastboot using adb, the task never completes. I know it should take less than 10 seconds for it to flash but it doesnt. I let the fastboot flash recovery recovery.img file command run for an hour but it doesnt complete. Im pretty seasoned with adb so I know all my files are where they should be. can anyone give me the exact commands for terminal emulator to flash a recovery for the ns4g? I've searched but cant seem to find them. I know ive used them ages ago but cant remember where. Thanks in advance.
this is what i get <<
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Rocky>cd c:\android\platform-tools
c:\android\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (3144 KB)...
>>but it doesnt finish
I have an ancient stock HC 3.2 and decided it would be nice to update. Forgetting completely about the fact that I had the ancient honeycomb bootloader as well, I loaded up an ICS update.zip and flashed. Now I'm stuck with a broken tab that displays Boot verification failed on startup. I have access to APX mode, but my computer does not seem to be cooperating with the drivers.
What to do?
Same kind of Problem
I have an A500 with OTA 4.01 o it.
I rooted it successively
Added bootloader ICS - worked fine - could see loader on reboot - used afterOTA
Backuped rom onto SD
Went in to recovery mode and installed JellyBean X rom - I wiped every thing including cache's
Installed fine, went to reboot and nothing.
Power light goes on and that's it.
I have tried several utilties but most need the computer to see A500 as a device or say failed, or do nothing
The "ejectAPX" shows on the eject hardware ion, and ACER USB drivers show up in device manager
I have tried resets, volume buttons etc - no go
The A500 screen did come up with "Acer Download Mode", but that as far as I get.
Any detailed help would be appreciated!
Win7 computer
David
Update
I do have mu cpuid and SBK #
I tried Blackthund3r APX flash tool, using A500_A501_ICS_V7_bootloader
BThdr says APX detected
Tab enters in to download mode with ACER logo on screen,
stage one ok
stage 2 just hangs at 3 quaters the way - I waited over 5 minutes
I have tried the following command with theresults after:
nvflash --bct flash.bct --setbct --odm
data 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0x04FF
1E00 0xABE0D706 0xEBAA3304 0x20502103 --go
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:0x5 (0x1000005) flags: 0
used babsector and it worked
got back into recovery mode
Been there
Been there (I think I have a messed up reset button actually), but the only thing I can get my tablet back to life on is timmyDean´s root-3.2.1-V4.7z find in the forums extract the files then in the image folder you will find nvflash run the flash.bat but it reformats your flash etc. and brings you back to HC 3.2.1.
I have been through all of the tools and this was the only one that boots to android when its finish, which I need since I think my reset is stuck.
I needed to create ubuntu usb stick and run eppe's code to get my CPUID might help with usb connection issues to use similar too.
Then I was working with nvflash --read and the v8 bootloader stuff (since before my tablet soft bricked I was OTA ICS full stock), and was able to read off my user data with nvflash partition before I did the flashing. That way I saved all of my tablet pictures and video etc. (loop mounted the image read from that partition in ubuntu and was able to pull out any of my user data).
To get my data I used V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip see more at http://forum.xda-developers.com/showthread.php?t=1622425
Then I did:
nvflash --bct bct.bct --setbct --bl bootloader_apx.bin --configfile flash.cfg --odmdata --sbk %MYSBK% --sync
nvflash --resume --read 2 mybct.bct
nvflash --resume --getbct
nvflash --resume --getpartitiontable mypartitiontable.txt
nvflash --resume --read 13 UDA_raw3.img
I wish I would have backed up all of my partitions that way but I think I will get the replacement part first and then rebuilt the tablet.
Hope that helps
Thanks
What I ended up doing was creating and formatting partitions with Babsector - as opposed to Badsector, which didn't work
The used A500 APXflash
Then installed Jellytime X
The Jellytime was not working properly so I used root-3.2.1 V4 to take it back to 3.21, then OTA to 4.0.1
Root it again and then I stopped.. think I will stay with this rom, until 4.2 is super stable.
I think I did this procedure about 4 times in 2 days, as every rom that I tried either trashed the partition or boot loader, or didn't run properly.
I was lucky as I used afterOTA as part of flash the bootloader, and it saved a txt file with all my cpu info...
David_h99 said:
Thanks
What I ended up doing was creating and formatting partitions with Babsector - as opposed to Badsector, which didn't work
Click to expand...
Click to collapse
What do you means by that? what is this babsector?
HOw do you creating and formatting partitions with Babsector?
I had try badsector and it doesn't work so if you have another way to do it i am very interested!
thanks
you can get babsector here
narod.ru/disk/53919831001.a235ea2225f319015f30c009629d2075/BabSector.rar.html
Make sure your computer sees tablet in APX mode, and the driver in device manager is the ACER USB driver
Then read info on how to run babsector
Hi all,
I was planning to downgrade the Lollipop to Kitkat (or maybe a ROM away from Google) and now that I have had the time to try it out, I'm running into issues regarding trying to unlock the bootloader.
I've read the article here: https://developer.nvidia.com/sites/.../docs/HowTo-Flash-TN7-WiFi-Recovery-Image.txt
and also downloaded the WHQL Shield USB driver from nvidia's website (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) though it doesn't seem to be doing much here.
I ran
Code:
adb reboot bootloader
and I have this:
Code:
[bootloader] (built on Apr 24 2015, 02:51:15)
Device - locked
Serial Number XXXXX
Press <Power> to select, <Volume Up/Down> for selection move
Continue
Fastboot Protocol
Recovery Kernel
Reboot
Poweroff
I then tried to run
Code:
fastboot oem unlock
and it says:
Code:
< waiting for device >
On the tablet, I select Fastboot Protocol, but all it does is go back to the bootloader.
I tried running
Code:
fastboot devices
and no device is appearing. Running:
Code:
fastboot device
or
Code:
fastboot oem unlock
still says:
Code:
< waiting for device >
Can anyone help me? The issues with Lollipop from the touch screen craziness, and the heat and tablet slow downs are well documented on Lollipop so I want to make this tablet usable again. Please let me know what I'm missing here.
Apparently, I wasn't missing anything. I switched to my Linux laptop where fastboot and ADB were installed via Android SDK.
I ran fastboot devices which picked up the tablet. Then I could run OEM unlock command. Off to the ROM flashing adventure!
Just flashed using OTA 2.5 from Nvidia's website and that seems to have ruined the install. It now only goes into APX mode. I read somewhere that the links Nvidia put for the P1988W were actually for the P1640. That's not good.
I wonder if there's a significance with the flash_tegratab_p1988.bct file that I found on another firmware website. Cannot seem to download it though.
EDIT: Found a firmware and will need to study the differences of this APX image to the Advent one.
EDIT2: Alternatively, as I have another Cherry Mobile tablet as backup, if I can use this to dump the image: https://forum.xda-developers.com/t/...d-partition-with-nvflash-on-the-gtab.1010659/
Been tinkering with the flash.sh script to see what it does and on an interactive shell, this seems to be the command:
Code:
sudo nvflash --bct flash_tegratab_p1988.bct --setbct --odmdata 0x4069C000 --configfile flash.cfg --create --bl bootloader.bin --reset normal 0
I'll continue to poke around. Strange that the script doesn't ask for p1988 if there's a secure boot (it only does for p1640).
Hey niniendowarrior,
I fell down the same rabbit hole around a year ago after doing the exact same thing as you, installing the 2.5 OTA from the NVidia site.
I've mostly given up. But, I got thinking that the NVidia sources available from their site might compile a compatible nvflash. The issue there is that compiling it requires a lot of outdated libs. I don't know when I'll have the time to try it out, but it might be a possible avenue for you to explore!
Best of luck.