yashsingh1/xdaforums huggingface dataset:
[Nvidia Tegra Note 7] e8hffff:
My bootloader does not allow power + down button to strap into recovery as it was the plain boot of first releases. Second the system fails to get into the desktop, and bombs without errors reported. No ADB service is started so I can't command the device to reboot to recovery. It's software bricked. The only buttons I can press is to get into APX mode, but then NvFlash fails to accept any commands.

As far as I know our devices don't have a secured APX mode so we should be able to perform commands with the correct file references, but no all issued commands simply fail and stalemate the process.

If I could format the system partition the device would automatically go to recover partition.

I'm thinking Nvidia may have done a deal with Microsoft to block Nvflash working due to Surface 2 RT using the Tegra 4 and Microsoft not wanting people replacing the OS on their hardware. Obviously NvFlash has secure mode to protect that, but they may have locked down the utility so as to hinder any tinkerers.

The other major concern is that if my device can't shutdown due to it auto starting for some reason when holding the power button for 12 second or when the screen goes blank, means my battery will be strained. Rechargeable batteries don't like being drained below 10%. It ruins their lifespan. What I do is keep my device in APX mode and USB hooked up to keep it powered. Waiting for the day someone discovers a NvFlash fix or I do.

Truly sucks.
[Nvidia Tegra Note 7] Tomsgt:
Ok this should help. Power off the device then hold volume up then power and you will see a black screen since you are on the old bootloader. Open a command window in android SDK and type fastboot devices and see if it can see your device. If it can we can fix it.

sent from my Galaxy Note 3 running HyperDrive.
[Nvidia Tegra Note 7] e8hffff:
I'm using Linux and got latest ADB and Fastboot installed. No devices are showing in either of those commands. I've used fastboot and adb heaps in past. It's simply the tablet is software bricked.
[Nvidia Tegra Note 7] Tomsgt:
Are you sure it is booting to bootloader black screen and not rebooting to apx mode black screen. It does work if you can get it into bootloader mode. It took me a bunch of try to get it there. On windows you can see in device manager if it's a apx device or a adb device. :)

sent from my Galaxy Note 3 running HyperDrive.
[Nvidia Tegra Note 7] e8hffff:
Man it does not recognise any button sequence other than holding the two volume buttons with power, to get into APX mode. Obviously the power button works by itself to start the tablet. I even put fastboot into "fastboot wait-for-device" mode to get immediate response. I've tried manually executing "fastboot devices" whilst attempting to get this that and everything to get recovery mode. Same with ADB, it's simply not loading the service and may be disabled in system level.

I've tried day upon day to repair this tablet. No safe mode, no getting bootloader screen, no recovery, etc. I'm locked out bar APX mode and booting into a endless loading of the system with no ADB service. Zero help from Nvidia and can't get RA for return as they wont return emails.

It's doing my head in and I'm considering giving up and getting another tablet. This has been a very bad experience.

I've even written a forum post on Nvidia Devs Forum telling them to F*** themselves.
[Nvidia Tegra Note 7] Tomsgt:
The only reason I am pushing so hard is that I was also stuck with this same problem and what I am telling you worked for me but took a lot of attempts. Had to unplug and turn it off then try it. If i remember right plugged it just keeps rebooting apx mode.

sent from my Galaxy Note 3 running HyperDrive.

---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
[Nvidia Tegra Note 7] Ouzo:
I'm finding a few problems with both Miracast and HDMI output. Under the original 4.2.2 firmware my films played smoothly, but now they jitter and hesitate as though the frame rate was dipping below 20fps or they were skipping frames or something. I'm trying to work out if it's just the way some of my films are encoded (high profile or something). I find EZCast is now a better way to wirelessly stream a film smoothly.

Also, with the original firmware you could zoom in on a film on the tablet (in MX Player for example) and on the TV it would bring the image to the edge of the screen so that you lose the black bars on the left and right caused by the Note's different aspect ratio. Unfortunately this trick no longer works on either Miracast or HDMI with either the main 4.3 update or the most recent patch. If you're having a different experience I'd love to know.

I wish Nvidia had squashed the USB OTG bug introduced in 4.3 that means you can't unmount an external drive without partially unmounting the MicroSD card, causing corruption in various apps and requiring a reboot.
[Nvidia Tegra Note 7] fards:
I didn't have the dongle when I had 4.2

yes I agree ezcast seems to be better at the moment, I'd not tried it with the tegra note till just, having used it on a laptop and thought it was awful compared to miracast.

not tried anything other than gamecontrollers with the otg yet.

have you tried enabling the game mode in the build.prop for miracast?
[Nvidia Tegra Note 7] Ouzo:
No, I haven't tried that yet. I get about a quarter of a second lag over both EZCast and Miracast so I think I'd get frustrated with games. The other factor is that frame rates suffer too. If you try Epic Citadel in benchmark mode when connected wirelessly to a TV and just on the Note itself, there's a big difference in frame rates. The good news is that via HDMI there is no drop in frame rate at all in games, so that's the method I prefer. That's also why I can't understand how the 4.3 update manages to make films over HDMI jerky, especially as it was fine under 4.2.2 - this thing has plenty of horsepower.

I haven't actually rooted yet. The only reason I have left to do it now would be to get my PS3 to work with Six Axis if it ever becomes compatible with the Note. Still, my better half bought me a Moga Pro for Christmas so that works well for games that support it.

Yes, EZCast was awful for me too at first, even from about six centimetres. My dongle got a firmware update a day or so ago and that improved performance quite a bit. I managed to watch a whole film using that method last night with no stuttering at all (though the connection did drop twice). There appears to be a number of different hardware versions available for wireless dongles and I suspect that one with 256MB RAM and a faster chip would provide a better experience - mine is much slower than some I've seen available online from China.

Should you try a hard drive via an OTG adapter cable, the only workaround I find when unmounting was to have the Google Music app open in the background (my music is on the MicroSD card) when unmounting the USB drive. If not the microSD card suddenly shows zero size and zero free space, in which case you have to reboot. If the gallery app and music app are corrupted, I found I had to clear data on both those apps plus the Media Storage app. Either way my Google playlists were blank afterwards. Bit annoying as it worked perfectly under 4.2.2.
[Nvidia Tegra Note 7] Tomsgt:
you may want to check this out since XDA hasnt given us our own forum this is where we are going

http://droid-hive.com/index.php?/forum/578-the-batcave/
[Nvidia Tegra Note 7] e8hffff:
Got some good news in that Nvidia is handling my case. Hopefully I will get a replacement tablet and remedy the bad luck I've had, like a tablet with so much wrong with it out of the factory. Redeeming my faith in Nvidia.
[Nvidia Tegra Note 7] NCSUZoSo:
I don't know what is going on ever since that small OTA update post 4.3 update. I was rooted before that update, but now it refuses to download the img file and root the device. I am in dev mode with USB Debugging on with it connected as a media device (I also tried as camera). I have tried it with the normal Fastboot Files and the program, neither works. With the files it just says "waiting for device" and never does anything. If I put the .img file in the directory of the program then the below events occur. I have tried turning debugging on and off and re-downloading Fastboot files and the image itself. Nothing is working and I can't root my device even though I am unlocked, as the boot loader tells me in red (and right above it). I think I am going to try relocking and the unlocking it again, that is about the only thing I haven't tried. I don't see why this small OTA incremental update is causing me such a pain...
[Nvidia Tegra Note 7] mattlgroff:
Try another USB cable and port. And if you have CWM then you can install my pre-rooted 4.3 updated system flashable zips found on droid-hive.com under The Batcave -> Tegra Note 7 Development
[Nvidia Tegra Note 7] NCSUZoSo:
I've tried probably 5 ports including USB 3.0 and 2.0 + a USB 3.0 hub, none of them worked. Also I am using the "official" USB cable that goes with the charger from EVGA.
[Nvidia Tegra Note 7] mattlgroff:
Well that's strange! Let me know if you find out what the fix is, if there is one. Good luck.
[Nvidia Tegra Note 7] NCSUZoSo:
What in the hell, I went and got my GPS cable (also Micro USB) and it worked perfectly fine... hmmmm

So if anyone has trouble with this try using another Micro USB cable you have around the house, I got a 2nd error when using the SDK pack which said "NV3BadReceiveLength" and I read about people using different cables. I used my primary USB 3.0 port where the tablet rooted the first time, but the cable is what changed the outcome now with the 4.3.1 update for some weird reason.
[Nvidia Tegra Note 7] NCSUZoSo:
Are there any compatible Kernels for TN7 yet? Franco for example?
[Nvidia Tegra Note 7] e8hffff:
http://nv-tegra.nvidia.com/gitweb/
[Nvidia Tegra Note 7] Rmdatsikk:
I've never owned a drawing tablet or any sort of stylus, do you think this is okay for a starter?
[Nvidia Tegra Note 7] Ouzo:
Yes. I'm using the stylus on this more than I used to on my Galaxy Note 2, although I use it for taking screenshots and making notes on them rather than for drawing.
[Nvidia Tegra Note 7] e8hffff:
Back on the scene guys after getting a replacement Tegra Note 7 since my first one had quality control issues. The new unit is 'proper' without any problems so far bar the GPS isn't working straight up. More testing needed.

I'm going to hold off with alpha testing of partition images, but I want to get into development.
[Nvidia Tegra Note 7] Ouzo:
I found using GPS Test from the Play store helped get a lock. Initially, within a few seconds the Note sees up to a dozen satellites but takes ages to lock. In GPS Test's settings, check the option that keeps the screen turned on. Stay in the app and don't do anything else. Don't rotate the Note. Wait until it eventually gets a lock. After that, subsequent locks should be much quicker though general performance is way behind current Qualcomm devices.
[Nvidia Tegra Note 7] e8hffff:
Thanks. I got it working once patched.
[Nvidia Tegra Note 7] cars10k:
compass is not working even close for me. known problem?
[Nvidia Tegra Note 7] e8hffff:
This is a far shot, but sometimes turning on all networking hardware thrn turning off, and then turning back on what's needed can sometimes set values correctly. Example turn on Bluetooth, then turn it back off. The reason behind this is multifunctional chips and configuration of android out of the factory is sometimes not geared properly.
[Nvidia Tegra Note 7] Pacattack:
Bootanimation
[Nvidia Tegra Note 7] e8hffff:
HEhehe Ok PacAttack, dish it up...
[Nvidia Tegra Note 7] Pacattack:
Emailed to you mate :)
[Nvidia Tegra Note 7] fards:
You've got decent nvflash working? Nice!
[Nvidia Tegra Note 7] e8hffff:
Thanks.

1. Ok the files in the executable (compressed package) are fairly old, 2011 to be correct. Other words pre-dating TN7. They extract to users/USERNAME-DOMAIN/appdata/local/temp

2. I couldn't get the package to work on the TN7 with tests carried out.

3. First problem was NvFlash reported it couldn't find the device. I fixed that using the shared Nvidia USB driver here on this thread. Also needed to change the 'odmdata' field in the batch file to 0x09557535. Discovery; the importance of using Nvidia's USB drivers for recovery. Not sure what makes them special at this point. I had to force the Nvidia drivers to overwrite the Google based ones in Window's Device Manager. Doing this all in VirtualBox as my base system is Linux.

4. I now know that the NVFlash I share here is missing dll's for Window Users. Will fix asap with latest dll's from other source.

5. I did a quick test using TN7 specific bct and boot.img, but no luck.

6. The included BCT file is filenamed after a memory chip, a 512MB DDR2 item, so maybe BCT files are memory layout compatible. The file name had H5PS1G83EFR-S2 in it...

7. Tomorrow will try using all latest files, and same configuration and see if that works to unbrick

Thanks again Pac.
[Nvidia Tegra Note 7] Pacattack:
Yes, sorry, old, tegra 2 tablet, in wrong folder on there server :(

But maybe a help in some-way :laugh:

I downloaded the old nvidia 2 drivers and that gave me apx/nvflash, that's more then the new ones did :laugh:
[Nvidia Tegra Note 7] Tomsgt:
so do you have the tool and the files to flash to restore it?
[Nvidia Tegra Note 7] ickk:
https://developer.nvidia.com/linux-tegra-rel-17

Nvidia has released tegra 4 linux utilities, maybe these drivers are useful?
[Nvidia Tegra Note 7] cars10k:
"Tegra Linux Driver Package providing a kernel image, bootloader, NVIDIA drivers, and flashing utilities"

I think this could be awesome!
[Nvidia Tegra Note 7] fards:
That's for the dalmore developer tablet. Not our tablet, but I haven't looked at it in depth to see what's the difference

There's the android kit that now supports tegra7.

Haven't grabbed it yet to see what's new https://developer.nvidia.com/content/tegra-android-development-pack-20r7-released-latest-sdks
[Nvidia Tegra Note 7] e8hffff:
Bump. Updated NvFlash tool package.

NVFLASH/APX

NvFlash_v3p08p1700_RipV2 (Executables for; Linux, Mac, Microsoft)
[Nvidia Tegra Note 7] e8hffff:
As far as my research goes, it's a 10inch development tablet.

Regarding hacking the tablets to get nvFlash or a true recovery, is to help people who have bricked their units, namely Shaky at the moment. My bricked tablet got replaced by Nvidia so I'm happy as Larry. It was replaced on the manufacturing quality not so much the bricking.
[Nvidia Tegra Note 7] Shaky156:
What date was this nvflash released?

And what version is this??

Hi thanks for the help, ive talked to the nvidia guy, they do have nvflash but they will not release it.

Ive also talked to place i purchased and i should have the note 7 back on next wednesday... Which means if i have time development will continue on note 7 including custom kernel and ROM (Android 4.4 KitKat)

If anyone hacks or manages to get a hold of the correct nvflash tool please do get in contact, as I have the correct files and setup required to factory reset a tegra note 7
[Nvidia Tegra Note 7] e8hffff:
It's the same version I was sharing before but it's got extra files. The version is NvFlash_v3p08p1700_RipV2. I've also added a 'lite' version of nvflash which was apart of another tools set and the file size is smaller, which may be specific to a development device, but may allow for modding to make it a TN7 version.

Shakey did you read my previous post where I discovered you need the Nvidia USB drivers for NvFlash to work at one impasse. I share those drivers in OP and they need to be force added to Windows device table to replace Google's Android version.

I use Linux but have a VirtualBox image of Vista for programming testing.

Great to hear Shakey. If you don't mod your bootloader and it's one you can get to with button sequence on starting the device then it should be near impossible to brick, much like the Google Nexus 7 was. Many people got TN7 that had a basic bootloader and this is what caused some to brick their units when trying to repair or tinker the system. Now with official patches these problems have been improved.

My theory is that since Microsoft uses the Tegra 4 in their Surface 2 Tablets, I think they have contracted with Nvidia to never allow NvFlash to go public, since it would be a big threat if people could buying their tablets and put another operating system on them. Example the Surface is such a bad seller they are discounting the hardware from approximately $1000USD to $500 in deals to bolster use, a tablet they weren't making money on to start with, but a worse situation if people get them and say run Linux.

Btw I'm loving my Tegra Note 7. Definitely an upgrade on Goggle Nexus 7 I had. The sound is great that I haven't even tried headphones yet.
[Nvidia Tegra Note 7] Shaky156:
Replied to this yesterday guess it sidnt go through...

I did get the device to read successfully with modifying the drivers, reading on computer has never been an issue its only the nvflash compatibility issue
[Nvidia Tegra Note 7] Macfionn:
Slate 7 extreme...

Wondering.. Is this forum relevant for us HP slate 7 extreme users, since we are running nvidia tegra OEMS?

There is no slate 7 extreme forum, and knowing xda, may not ever have one as its essentially a rebranded nvidia.
[Nvidia Tegra Note 7] cars10k:
afaik yes. Already Advent & EVGA users here, welcome :P

Every tool and update zip provided so far here was told to be only for the evga version, but worked fine for me on my advent.

E: btw, i made a "discovery": if you are not using the slide cover, means the back of your tn7 is free, you can attach the stylus to the magnets if you are to lazy to put it into the hole and just want to put it away for a moment. there are 2 relevant magnets for this, one under the left speaker, and one under the right one. i think this is awesome! although i guess it was not meant to be used like this.

pic: http://i.imgur.com/QWEWvUL.jpg
[Nvidia Tegra Note 7] e8hffff:
They maybe using the same OEM MoBo but the chips have identity. You also would need to check if there is a difference in partition layout too. Sadly there isn't enough research to make clear what the differences are.
[Nvidia Tegra Note 7] rchrdcrg:
All of these tablets get their OTA updates direct from Nvidia, and the same update file works across all TN7 tablets, including the HP one. Nvidia requires the OEMs to follow certain guidelines in order to license the TN7 design, not the least of which is for them all to be compatible with Nvidia's updates. It's the same as with graphics cards; OEMs make them, but they all have to work with Nvidia's drivers, and in the case of the TN7 even the hardware specs are locked down and cannot be altered by the OEMs (beyond cosmetic changes like the HP). It's actually a really smart idea, the more I think about it. It would be interesting to see if with future generations of Tegra Notes they allow the OEMs to make changes to the specs, such as RAM, screen resolution/size, physical design, etc, though I'm sure they would place limitations on what could be changed and how.
[Nvidia Tegra Note 7] e8hffff:
Why I said what I did was with small amounts of checks I considered the boot.img to be different between the devices. I will better check in future!

Example some of the updates/images replace the whole partitions of boot, recovery and system, therefore HP would loose their branding if all images were the same.
[Nvidia Tegra Note 7] rchrdcrg:
Hmm, that hadn't occurred to me, although the only branding I'm aware of is during the boot animation, and that may not be part of any OTA updates, meaning it would stay the same unless the user specifically changed it... but that's just an assumption since I'm no developer and haven't delved into the files myself.
[Nvidia Tegra Note 7] e8hffff:
You could be correct though. I deleted older HP image I had but one I have now has a uncompressed system directory so that would indicate you're correct.
[Nvidia Tegra Note 7] Deepak Vishnu:
I can't get a GPS lock what to do
[Nvidia Tegra Note 7] cars10k:
Keep trying, maybe outside. Works faster after you got the first one
[Nvidia Tegra Note 7] Shaky156:
Not sure why this is in android development?!? And not in general section. If you send out a log instead of complaints maybe someone can look at it and solve the issue for you
[Nvidia Tegra Note 7] rchrdcrg:
Well that's good! If all of these things can work with the same recoveries/ROMs/etc then we have a much better chance at seeing some serious development on this thing.

---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------

I believe the point of the thread is to discuss discoveries that can help with development (which apparently we need since there's still not a single aftermarket ROM available for this thing).
[Nvidia Tegra Note 7] Shaky156:
Discoveries such as??... All I'm seeing is speculation and complaints IMO not really development neither does it help developing an aftermarket ROM :s

Edit: I see why this is here, OP has changed since last time I read

Edit 2: I already have a custom kernel working just waiting to receive my device to get Kitkat running then shall release
[Nvidia Tegra Note 7] rchrdcrg:
Well that will definitely be awesome! I'd love to see some overclocking on this thing on top of the memory improvements of KK. I'm also dying for Nvidia's next update to see if Console Mode has made it in... I want to properly use this thing for console-style gaming, but the 720p output and weird pillarboxing due to the 16:10 aspect ratio is driving me nuts.
[Nvidia Tegra Note 7] e8hffff:
This thread is supposed to be for reporting technical discoveries. At most times people wont need to report a debug-log unless they start chatting about a specific installation or application.

This was the first thread to bring together information about the Tegra Note and list resources for flashing and hacking.

Sometime in the future someone may want to copy over the details here to the XDA Wiki and then this thread could be deleted.

Currently I can't change the thread's title so I can't define the purpose with [] tags.

It's hoped then when someone needs some quick information about the Tegra Note that they can come here and find it.
[Nvidia Tegra Note 7] Shaky156:
Hi I editee my post, re read OP n it has changed since last time I read it... This should be a sticky thread
[Nvidia Tegra Note 7] ickk:
I will port AOSPA to this device, the device tree needs to be pulled, but aside from that most of the groundwork has been laid with unlockable bootloaders and recoveries for the device.

I am hesistant to begin working on building paranoid until we have a 4.4 OEM release.
[Nvidia Tegra Note 7] rchrdcrg:
I may have to eat a few of my words... was just reading over at http://www.androidpolice.com/2014/0...not-all-tegra-note-devices-are-created-equal/ ...HP is pushing their own updates and not Nvidia, and apparently they're not doing a good job of keeping up. They added a little bloatware and some other system-level tweaks (apparently they found a way to make the display look better?). I'm still confident it would be easy-peasy to port Nvidia's ROM over to the HP S7E, but it's not as cut-and-dry as I thought it was, and apparently Nvidia will indeed license this design to companies without requiring them to use Nvidia's OTA updates. Kinda seems stupid on one hand, but then again being open to more options gets more Tegra 4 chips out there, which was kinda the whole point of them going about it this way since they were having such a rough time getting manufacturers to use their chips. It is rather enticing to manufacturers to be able to skip 99% of the R&D process and just use someone else's reference design.
[Nvidia Tegra Note 7] e8hffff:
Cool. More options the better.

I see Tegra Note as a series rather than just this first tablet. We will see the iteration of devices, like those coming with K1 Tegra chipsets. This means any development will have future use.
[Nvidia Tegra Note 7] e8hffff:
You've already got respect in just saying that.