yashsingh1/xdaforums huggingface dataset:
[Nvidia Tegra Note 7] e8hffff:
nvflash aftermath. dmesg for crashing system + no wifi

http://pastebin.com/ak8EZx88

nvflash aftermath. logcat for crashing system + no wifi

http://pastebin.com/C5nDNnQP

The only thing I see odd are the broken pipe entries. Are the Android drivers supposed to be signed? Possibly the broken pipe is due to the driver not being loaded because it's not passed checksum to a non existing signature file?

Note the error logs are from a system with EVGA's boot.img replacing the Advent one since the former has the proper fastboot menu compared to the included nvflash package. Note, I also had no wifi and got crashing with the official nvflash swipe of the tablet.
[Nvidia Tegra Note 7] Shaky156:
When logging did you attempt switching on wi-fi?? If not please attempt switvhin wi-fi on the log

Also nice pc but need a dmesg of your device not pc lol, adb shell dmesg > dmesg.txt

Sdcards a read only f/s looks as if not everything flashed successfully, if you can copy the 4.4 EVGA OTA into the sdcard nvidia update folder then it will pop up under system updates, then update.

[MENTION=3399030]e8hffff[/MENTION]
[Nvidia Tegra Note 7] e8hffff:
Was I that complacent... I'll check it out and repost otherwise. Super busy.
[Nvidia Tegra Note 7] e8hffff:
Ok fixed the dmesg txt. The problem happened as the terminal exited with a usb decoupling. The logcat is with Wifi on and me pressing modes and what not, to see if I could trigger any responses in the log. The wifi is also on in the dmesg output.

nvflash aftermath. dmesg for crashing system + no wifi

http://pastebin.com/ak8EZx88

I haven't had time to read through the dmesg log.
[Nvidia Tegra Note 7] Shaky156:
I see whats happened, best thing to do is, put the android EVGA OTA 4.4 update into your sdcard nvidia folder. Boot your device and goto update section and it shall read, update your device and it shall function perfectly :D
[Nvidia Tegra Note 7] e8hffff:
Yeah tried that as you may have noticed in the previous somewhat broken dmesg output from my desktop. The OTA simply isn't being processed and not sure why. Possibly the Advent Tegra has a different layout? I also tried having the file titled update.zip, even though I think the file name doesn't matter as long as it's in the correct directory.
[Nvidia Tegra Note 7] fards:
The Vega will flash the evga fine . not sure why you're won't pick it up

I've not noticed anything different with the partitions between the versions.

The only difference I've seen is the boot screen
[Nvidia Tegra Note 7] astuermer:
When doing an OTA Update on my recently purchased EVGA Tegra Note from 4.2.2 to 4.3 MR2 the recovery halts with "error".

Any idea what could be the problem?

Also my device lacks a "real" bootloader as mentioned in the first post.

Is there an updated bootloader which can correct this?

If I do ADB REBOOT BOOTLOADER I only see a black screen - but I can do FASTBOOT commands.

Any help?

Thanks! :confused:
[Nvidia Tegra Note 7] e8hffff:
So you are placing each OTA in sequence in you OTA directory and restarting the device each time per OTA file? Other words don't put them all in at once!

Consider if you want to manually modify partitions you may need to 'fastboot oem unlock' the device. Warning, only do this if you know the ramifications and know what you're doing!

EDIT: If the OTA updates do not automatically detect, then you will need to install them manually using the recovery 'install zip' feature, otherwise you will need to trigger an Android update process somehow.
[Nvidia Tegra Note 7] szm:
I tried the "tegra_note_7_-_ota2_android_4.4.2_update__4.4.2.zip" update using CWM-recovery-6.0.4.5,

but I got an this package is for "tegranote" devices; this is a "tegratab" message

please advice

(my device is a "homecare fly one p1640 tegranote 7" device)
[Nvidia Tegra Note 7] e8hffff:
If you were desperate you could edit the /META-INF/com/google/android/updater-script file in the archive to remove the check.
[Nvidia Tegra Note 7] szm:
desperate ..I am ! because i like this device , but since my very simple done root was useless after OTA updates i ..unliked this device :) ;

i'm also new to this stuff (android flashing insides) ; thank you for advice , I will try

edit: done, it went to the next step "installing update..." but ended with "set_metadata_recursive: some changes failed" ...installation aborted

any advice please ?
[Nvidia Tegra Note 7] prichm1992:
Is this still for discoveries..? Well, I found something. I was playing a game today, and the screen was a bit fuzzy to me when I tilted the device. Inspected it very closely, thinking it was some eye problem. But when I tilted the device a handful of degrees to the left or right I confirmed that there ARE two images. They are about, ehh, 1mm apart? As if there are two displays set right on top of one another.

Sent from my O-Geeb
[Nvidia Tegra Note 7] astuermer:
That's because the display and the glass are 1mm apart.

The TegraNotehas no hapless display design as the Nexus 7 2013 for example...
[Nvidia Tegra Note 7] prichm1992:
The bottom image appears rather dull. That makes me think that the glass simply amplifies colors. Could be, too, that's how they compensated for how much battery the stylus digitizer uses. And also why they couldn't have used corning gorrila glass. I've noticed that in games, the dual image effect helps smooth out some of the 720p screen's pixelated edges. Neat!

Sent from my Wayne
[Nvidia Tegra Note 7] Tomsgt:
Super Tool Has Been updated to new ota 2.3
[Nvidia Tegra Note 7] e8hffff:
Great work Tom.

I had trouble patching (May 2014 OTA 4.4.2 KitKat Patch 2.3 Update. EVGA Version) 78MB

I had to manually do it using recovery sideload and editing the update script to remove the blob copying to staging.
[Nvidia Tegra Note 7] Tomsgt:
Nice that works but just a pain to do.
[Nvidia Tegra Note 7] e8hffff:
Has anyone got a On-The-Go (OTG) hub or cable, working? I got a OTG USB hub and card-reader but nothing seems to work bar charging power.
[Nvidia Tegra Note 7] ggs2:
I am using OTG cable, works fine.. (tried pen drive and use PS3 Dualshock controller as it doesn't work wit bluetooth stack :( )
[Nvidia Tegra Note 7] e8hffff:
Ok cool man. I wasn't sure if the protocol was supported or not or if it's broken with modification of the system.
[Nvidia Tegra Note 7] 6stringandy:
Are the 3 thick black strips on the big white piece in pic 3 the magnetic strips? If so, can the be removed without damaging the integrity of the unit or software? I have a theory I'd like to try out.
[Nvidia Tegra Note 7] e8hffff:
I think they are just electrical insulation tape, but I haven't tested the magnetic effect. The tape is to isolate the copper chassis sheet from the battery.
[Nvidia Tegra Note 7] 6stringandy:
My intention is to find and remove all magnetic strips in the unit. I know the cover that was made for it wont work anymore, but I want to see if removing the magnetic will improve GPS lock. The magnets aren't really all that strong, but there's enough of them to impact the signal. That's the theory I'm trying to work out.
[Nvidia Tegra Note 7] hacktrix2006:
Well it seems it is a hardware fault burning smell and then it failed to even access APX so its return it for a replacement.

Edit: Got a new Tablet under replacement, So now its time to find away to kill the OTA updater.

I suggest if your still on 4.2.2 is for now to stay there as 4.2.2 has a unlocked Bootloader by default and is not SBK signed.

SBK Signed is the reason for some of us are getting bricks when using the likes of super tools to update to 4.4.2. SBK signing came with the OTA 4.3 which is why when on 4.3 we do a fastboot oem unlock why we get the red text about Warrenty. Once SBK signing is on thats it Nvflash then talks when flashing in a encrypted format and without the SBK AES128bit keys nvflashing the wrong APX will result in SBK and DK showing fused which then bricks the tablet, this intern causes the reboot loop brick.

So if you on 4.3 and want to go back to 4.2.2 you can't and its the same with 4.4.2 to 4.3 it will brick your device if your blob.bin and the sbk is not correct.

Also in 4.2.2 /System partition there is 178mb free space yet on 4.3 and 4.4.2 there is only 17.8mb free space after OS install.

Now to disable OTA's on 4.2.2 we need to find away to disable out right com.nvidia.ota.GCMintentService and com.nvidia.ota.DownoadService as that on 4.2.2 is the OTA updater.

Now i have tried FOTAKill.apk but that doesn't cover the com.nvidia.ota parts at all and using Disable Service.apk doesn't do anything it still runs.

As for the SBK signing which was used in Tegra 2 and 3 products we need to dump the sbk key in a decrypted format so when using nvflash we can use the --sbk <SBK CODE> to flash with.

Now the SBK is unique to each tablet i would think but i will look into that, when i have the time. If your already bricked then the only other thing you can do with your warrenty being void is talk to nvidia like ehfff did.

Now i am going to sign up to Nvidia's Dev area and have a look at https://developer.nvidia.com/tegra-4-technical-reference-manual see if that sheds some light.

Edit: 2 (Should go Directly to OP first post!!!!!)

To kill the OTA on Android 4.2.2 on the Tegra Note 7 you must chmod the following file TegraOTA.apk .

to do this you must have root which if you have 4.2.2 you should be rooted already by now using the Root_n7.img with the fastboot boot root_n7.img from fastboot.

type the following in order and exactly like this.

$su

# mount -o rw,remount /system

# cd system/app

# chmod 000 TegraOTA.apk

# reboot (if it quits you out of ADB then just use adb reboot)

System Updates is now disabled on your device!
[Nvidia Tegra Note 7] e8hffff:
So the bootloader_signed.bin is used to talk to the signed core on the device, and the bootloader.bin on those with older images that aren't signed.

Other means could be to iptable the ip.

I used to get this piped out to the console when using an old nvflash in experiments.

"chip uid from BR is: 0x600000015c4192010c0000000ffe0400"

Unique, or of use?
[Nvidia Tegra Note 7] hacktrix2006:
0x600000015c4192010c0000000ffe0400 is not the SBK if we are going by tegra 2 and 3 standard as it was in groups like 0x0000 0x0000 0x0000 0x0000 and its not enough for a SBK. thats why i am after a DEV image with the APX that way its not signed and maybe able to push it to the device to get it going again but i am now waiting on a reply from the mobile team.
[Nvidia Tegra Note 7] e8hffff:
Yeah I wasn't implying it was the skey. It may have something to do with interfacing an encrypted tunnel, though.

To tell you the truth I haven't spent enough time researching the APX protocol, or what's been documented on it. I'm fairly new to Android hacking, even though I flashed and done basics for past few years.
[Nvidia Tegra Note 7] e8hffff:
I could probably help with a 4.4 scan. My tablet is EVGA and I have a Homecare Flyone that is failing due to incompatible core files. At the moment I'm a little busy but I will do the scan outs asap when I get time.

Thumbs up,
[Nvidia Tegra Note 7] hacktrix2006:
Thanks mate. I downloaded the 4.3 OTA via the OTA updater on tablet but was unable to even open it up. If we can a way to do what they did withe the Nexus 7 2012 then it would make life a lot easier. Still looking for CPU UID though. I have found some files in 4.2.2 and still checking them for relevance to what I am trying to achieve. Thanks for you reply though.

Edit(PC):

I have now OTA updated to 4.3, unlocked the bootloader and rooted. Certain apps have forced me to update to 4.3 so i can now at least start making some progress again on finding the SBK.

Hopefully i don't get issues don't want to be getting another one LOL. Lets just hope i can keep my 11 hours battery life total on this version of android.
[Nvidia Tegra Note 7] hacktrix2006:
OK I need some people to test something for me. Based on the TEGRA 2&3 where the CPU ID was used for SBK, I downloaded a CPU Info app which gave me a CPU serial. So I need some volunteers to download either a CPU Info or Quadrant Standard to get their CPU Serial so I can check to see if its the same as mine or different.

Here is mine as a screenshot. If you could PM me or Attach your serial if possible we might be one step from a total unbrickable tablet via APX.

I will also try and find a way of getting a working blob and bootloader as well.
[Nvidia Tegra Note 7] chaps:
I'm guessing I need root to view the serial number? It isn't displayed on mine. I won't have time to gain root for a few days, but I'll report back once I do.
[Nvidia Tegra Note 7] hacktrix2006:
nope just quadrant standard or any cpu info app.

CPU Serial: 066803e804000000

SBK possibility: 0x6C210000 0x406F0700 0xF0D1E302 0x306EE402
[Nvidia Tegra Note 7] chaps:
Got it;

066803e804000000
[Nvidia Tegra Note 7] hacktrix2006:
So that is the same as mine so it might no be a SBK... Need some with a bricked tablet in APX mode to send it nvflash --SBK just to check if it works.
[Nvidia Tegra Note 7] Tomsgt:
Super Tool Has Been Updated to 2.4 OTA Enjoy

Stock rom based on OTA 2.4 can be found here http://rootjunkysdl.com/?device=Tegra%20Note%207&folder=Rom%20Stock%204.4.2-2.4
[Nvidia Tegra Note 7] hacktrix2006:
Tomsgt Nice one mate!
[Nvidia Tegra Note 7] e8hffff:
Bump. Added latest OTA update; tegra_note_7_-_ota_2.4.1__4.4.2.zip
[Nvidia Tegra Note 7] chp2:
Any news on a modded kernel available for our device ?
[Nvidia Tegra Note 7] Shaky156:
Hi I have developed a modified kernel for the tegra note 7 a few times, but the device seems to not like modified kernels for some reasons other areas of the device act up, e.g. cpu cores 1-3 not reading while cpu0 works etc

Ill attempt a modified kernel one last time, if successfull then i shall release :)

Regarding ROM, I have developed a custom ROM, compile cyanogenmod, paranoid android and SOKP, one major issue remains, I have spent the past days attempting to get audio working but audio fails no matter what. Now I have audio working but system wont boot past boot animation. Nvidia isnt fully open source which is why there are issues with this.

Once the ROM boots expect a release

I have ROM booting without audio ofcourse
[Nvidia Tegra Note 7] chp2:
LOL,

It remind me the old time whan I was on LG Optimus 2X (Tegra2 based) and HP Slate 7+ (Tegra 3). That's the bad with NVidia, they are making one of the best product but they can't do (or don't want to do) anything open source.

Else, for sure we are interested in a new moded kernels and ROMs. In my case I'm dreaming in a light (without any bloatware) ROM with a OC/UC capable kernel for our device.

I don't know how I can help cause I'm not a dev. But I can be a betatester if you want?

In any circumstances, we appreciate all the work you spend for us.
[Nvidia Tegra Note 7] fards:
Drop me pm with some details and I'll have a look and see if I can help fix it.

Had fair bit of experience with tegras in there last although I don't have a build box up at the moment.
[Nvidia Tegra Note 7] emerich46:
Since the OTA zips are here:

My stock EVGA Tegra 7 has the "turning wi-fi on" issue. As in: No connection at all.

Since the necessary files are here. Can I in any way start the OTA update without connectivity? Right now when i hit the "system update" button in the settings it just goes like " I can nae connect! " and gives me a helpful exit button.

Also, I would prefer not voiding my warranty, since the device is fresh out of the box and not really mine. Considering OTA works without root or such, I sincerely hope there's a way to kickstart the update process.

Some more input:

Model : TegraNote-P1640

Android: 4.2.2

Kernel: 3.4.35-g21b2d5b \\ buildbrain@mobile-u64-511 #1 \\ Tue Nov 12 03:14:05 PST 2013

Build: JDQ39.13155_268.1942

Thanks in advance <3
[Nvidia Tegra Note 7] ToJa92:
I think you should be able to get an OTA zip and apply it using the stock recovery, since the stock recovery should check for signatures (and the official OTA zip files should obviously be signed correctly).
[Nvidia Tegra Note 7] fards:
Needs to be a newer date. Then just put it in the correct nvidia app folder on the sdcard
[Nvidia Tegra Note 7] emerich46:
So i downloaded the 4.3, renamed it ota.zip and put it in the folder:

/sdcard/nvidia/app/ota/download/ROM/

Do I need to unzip it there or something? When I go to about phone and System Update I get the same old fancy message telling me there's an Error since it can't start a connection.

Now as far as the recovery goes, I can't get in a recovery mode. I checked the instruction videos and tried the different keypress combinations.

I DO get into APX but not into stock android recovery.

When I do "adb reboot recovery" I end up at a screen with a dead Android - All nice and stuff, however I can't get past that with neither of the button combinations (vol up+ power, vol down + power . starting with either of the combinations).

Would taking an image from a working tablet and installing it on the broken one void the warranty?
[Nvidia Tegra Note 7] e8hffff:
Sorry the OTA will not automatically update unless you can trigger an update process. The OTA files are referenced for those researching and coding. Origianlly it was beleived the OTA will trigger automatically based on HP brand devices having a sdcard update mechanism, but this proved to not be true.

If you need to update a device, attempt to flash the system partition. If you need greater changers then attempt to nvflash, but do this as a last resort.
[Nvidia Tegra Note 7] jskandhari:
Ubuntu Touch

I'm looking forward to getting Ubuntu on TegraNote7 ... Big Ubuntu Fan and I need it to work on my Tegra...

Or has anyone been able to install via modifying these commands

https://wiki.ubuntu.com/ARM/TEGRA/AC100#Installation_requirements
[Nvidia Tegra Note 7] Somcom3X:
So, I'm going to focus on the regular slate 7 extreme for a proper bring up. No nvidia funny business involved. I'm sure I'll eventually get these tablets unified.

Ubuntu for mobile is currently in limbo. Not worthwhile to port.
[Nvidia Tegra Note 7] Somcom3X:
To all you lurkers, I got recovery booting. Currently compiling a Rom atm. Do you guys like cm?

Sent from my HP Slate7 Extreme
[Nvidia Tegra Note 7] hacktrix2006:
Hi mate, nice one BTW. CM, OMNIROM, ASOP+ either is good. Which recovery have you got working? Also have you managed to get sound working too with the custom rom ?
[Nvidia Tegra Note 7] nelsonw:
Great!
[Nvidia Tegra Note 7] Somcom3X:
I got cwm working but it's flipped. A custom graphics.c came to no avail.

I'm currently having issues with the kernel. I've disabled wifi and all of the other drivers (except for display of course) until I get it booting.

So far I'm focused on the recovery.

Give me a few weeks and I might have a buggy zip out.
[Nvidia Tegra Note 7] nelsonw:
Ok! Keeps us posted here.
[Nvidia Tegra Note 7] tomgus1:
I'd love some Carbon on my Note 7 :D
[Nvidia Tegra Note 7] Somcom3X:
Built a ROM, currently have issues with the mounts.

Using the tn7 recoveries, did anyone brick their hp slate 7?

By the way, I grabbed the HP source code from their os team.
[Nvidia Tegra Note 7] hacktrix2006:
Nice one mate.
[Nvidia Tegra Note 7] Somcom3X:
This tablet has the world's tiniest partition layout I've ever seen... I had touch working in Philz recovery but I'm honestly stupidified about the recovery size. The kernel is too big and the boot partition is small. Stripping all of the fat inside it will take time. I'll play with this around Christmas time.

Sent from my HP Slate7 Extreme
[Nvidia Tegra Note 7] hacktrix2006:
It sure does have a very thin partition layout. Take your time though mate.
[Nvidia Tegra Note 7] e8hffff:
Updated details to suit Lollipop Rom.
[Nvidia Tegra Note 7] e8hffff:
I'm finding the latest official Lollipop Update fast but the device is much hotter. I'm trying to clean up including my apps to see if I can correct any problems. Optimising which apps can start-up is probably a good move and I'm doing that with root mode ES Task Manager.
[Nvidia Tegra Note 7] hacktrix2006:
[MENTION=3399030]e8hffff[/MENTION] is the OTA for P1640 an SOAK version or the Public official as mine not showing the update and as Nvidia controls the OTA that seems strange like.
[Nvidia Tegra Note 7] e8hffff:
Going by past experience they stagger the updates to different zones/devices to help bandwidth. I have shared the update zip. I will test on my older tablet which is classed as a P1640 and get back to you.
[Nvidia Tegra Note 7] hacktrix2006:
Just flashed it on my Advent Tegra Note 7 (P1640) its working fine with no issues (I have only done this because i have APX images that are custom made so i can unbrick myself).

However i though the EVGA's was also a P1640
[Nvidia Tegra Note 7] e8hffff:
Ok cheers Hacktrix. Keep everyone up to date on any issues you have!
[Nvidia Tegra Note 7] hacktrix2006:
Will do, However i shouldn't have any issues per say as its a nvidia OTA.

I might not got the OTA Update due to my LBH partition being completely custom and there for not digitally signed. Will at some stage update the APX images to the new Android 5.0 when my internet connection will allow me.

http://xdaforums.com/nvidia-tegra-note-7/general/nvidia-tegra-note-7-apx-images-t3149839
[Nvidia Tegra Note 7] funb0b:
Update done now won't charge past 22% !!
[Nvidia Tegra Note 7] hacktrix2006:
Are you charging and using the device at the same time. If so turn the Device off and let it charge that way, not only will it be quicker it will charge it to 100% Battery.
[Nvidia Tegra Note 7] e8hffff:
Go into your settings>battery and without a charge cable in, turn on battery saver. Then plug back in the charger and restart.

Also check if your device is really hot and if there are any temperature changes after modifying settings or what apps start.
[Nvidia Tegra Note 7] nelsonw:
Yup battery drain faster... But stopped after steps above. Thanks!
[Nvidia Tegra Note 7] e8hffff:
Nvidia have rammed the system partition, like 2mb left, so there maybe extraordinary storage/memory movements happening to keep the system up. I haven't had time to research.

One can remove some of the GAPPS like Newstand, G+, etc and installed them later into the userdata area as normal. Chrome maybe needed as there is no basic browser. The system moestlikely has its own webkit though.
[Nvidia Tegra Note 7] funb0b:
Why is charging so slow? Has anyone done a full reset? If so did it help? Tried the battery saver option.
[Nvidia Tegra Note 7] Quistnix:
You can turn most google apps into user apps using Titanium Backup. This opens up almost half of the System partition.
[Nvidia Tegra Note 7] e8hffff:
I decided the reinstall the 5.1 restore image available from Tom. Much the same issues.

The heating problem could be from a lack of resources when running system apps, a int her eis not enough storage left to write down their own files if they need it, so maybe one or more apps are in loops waiting for storage to come available. This is a guess though as I haven't researched any failing apps. There is definitely a lack of storage though in the system partition.

There a lot of junk apps int he system partition, that are nice to have there if your do a -system-restore wipe, but many of the apps are the type that Google regularly update and therefore will be linked to current versions on userdata partition anyway. Example Google Plus, Youtube App, Chrome, ES Explorer, even Nvidia's TegraZone2.

After you do clean up of apps and various settings the tablet does seem to work properly, but at this point in time I can't say exactly what's fixing the heat issue.
[Nvidia Tegra Note 7] e8hffff:
Ok that's good to know as Link2D only has one way to make apps system type. Also Link2SD is now crashing when starting. It starts then Google Play Services crashes then it pulls down Link2SD.