yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Original Android Development] bonny_k-9:
there is no decision?
[Shield Tablet Original Android Development] Steel01:
Well, since [MENTION=5123642]lj50036[/MENTION] now has a holey tablet, I finally bit the bullet and took maintainership. Got things sorted and we now have a new release. 3.0.2-1 has all the latest discoveries and changes merged in. It will boot on both bootloaders, all features should work, etc. We've requested the xda mods to transfer the thread to me. Once that happens, I'll get the OP updated with the new info. For now, just go to twrps website to pull the new release. And if there are any problems at all, please let me know.
[Shield Tablet Original Android Development] RBS01:
Big thanks for this, working very smooth.

Just noticed battery showing 100% all time

EDIT: battery reading moving but different of system read. What's wrong?

Enviado con Nvidia K1 via XDA
[Shield Tablet Original Android Development] Steel01:
That's not something I've seen before. I'll take a look. Does anyone else see a discrepancy?

Edit: Just checked on my daily driver tablet which is still on L/cm-12.1. I'll see what happens on my test tablet which is M later when I get back to it.
[Shield Tablet Original Android Development] RBS01:
Dunno really, I'm recharging to see what happens.

This tablet shipped with 50% battery read, yours too? This is just curiosity.

Let me know your tests when able

Enviado desde mi Moto G mediante Tapatalk
[Shield Tablet Original Android Development] RBS01:
Definitely bad readings in my case. Charged to 100%, rebooted to recovery and was 100% too, but won't update. After a while I've rebooted to system and was 95%.

Enviado con Nvidia K1 via XDA
[Shield Tablet Original Android Development] Steel01:
Odd... I just got back to my test tablet. Booted into the new release saw 20%. Rebooted into cm-13.0 and it also said 20%. I'll boot back into twrp and let it sit for a bit and see if it updates accordingly.

Now, the only model I have on hand is the wx_na_do and I've got two of them. I see you're on the K1. I really don't expect the charging circuit to be any different, but I guess there's a possibility. Can people on the wx_na_wf and possibly another sb_na_wf see if the battery indicator does odd things?

Edit: Mine is discharging and changing the number accordingly. Screen went to sleep, I woke it up a few minutes later, number had gone down. Without being able to hands on reproduce it, I don't know how much I can do. Although, I'm curious if this bug also occurs on multirom secondaries on an affected device. If it does, I might know exactly where the problem stems from.
[Shield Tablet Original Android Development] Sjamaan:
Thank you for your work Steel01, but unfortunately adopted storage won't work for me with this latest version.

It worked well on previous 3.0.2.0

Enviado desde mi ALE-L21 mediante Tapatalk
[Shield Tablet Original Android Development] Steel01:
The official 3.0.2-0 wouldn't boot on the M bootloader. Which build was it working on?

Iirc, someone reported it wasn't working on my multirom twrp build either. I haven't messed with adopted storage yet. Guess I need to grab a sd card to test with and see what's wrong. Probably just a fstab flag somewhere that I don't have set.
[Shield Tablet Original Android Development] Sjamaan:
Oh yeah, excuse me. It is romracer's build that works.

http://xdaforums.com/showthread.php?t=2877117

But it has the same screen issues as your old experimental build, that seems fixed in this new build.
[Shield Tablet Original Android Development] Steel01:
Ah, okay. Unfortunately, I haven't seen a line of code from him yet, so that doesn't help figure out the issue. I'll see if I can look into it tonight, but it might take a few days.
[Shield Tablet Original Android Development] Steel01:
Found the problem with adopted storage and it's been fixed. Just need to wait on 3.0.2-2 to be built. Hopefully that's the only show-stopping, needs rebuild bug that comes up. :nervous:
[Shield Tablet Original Android Development] Steel01:
The new version has been released with the adopted storage fix.
[Shield Tablet Original Android Development] RBS01:
Thanks, will test tonight

Enviado desde mi Moto G
[Shield Tablet Original Android Development] RBS01:
Please can anyone with K1 wifi using these lasts twrps confirm me if have the bad battery readings.

In twrp I see 10% more charged than in system.
[Shield Tablet Original Android Development] Sjamaan:
Working great so far and I haven't noticed anything wrong with battery readings yet. Thank you!
[Shield Tablet Original Android Development] Isira:
Same, original shield tablet, battery readings identical in TWRP and 4.1 ROM.

I did notice a bug in TWRP. I have the brightness manually set to 25%, but when I use ADB Sideload, the brightness changes to 100%, and would have to restart the recovery or go back into settings to tweak it to get it back to 25%.
[Shield Tablet Original Android Development] Steel01:
Finally got the thread transfered last week, but didn't have time to update it until now. So, should point everyone directly to the official site to download now. Like always, if any problems are found, please let me know.
[Shield Tablet Original Android Development] shisui13:
Is there someone out there that can pull build.prop of this nvidia shield? Thanks coz I don't have this device.
[Shield Tablet Original Android Development] robgee789:
is there anyway to install this on my stock k1 without losing all my data?
[Shield Tablet Original Android Development] lafester:
Only if you are unlocked already
[Shield Tablet Original Android Development] robgee789:
I thought so mate cheers
[Shield Tablet Original Android Development] Sh0X31:
Do this work with the k1 Shield
[Shield Tablet Original Android Development] flastnoles11:
Yep
[Shield Tablet Original Android Development] robgee789:
so on the k1 you just boot to fastboot then oem unlock then flash this recovery?

and if yes do you have to let the tablet reboot after unlocking and before flashing the recovery?
[Shield Tablet Original Android Development] robgee789:
i flashed this on my k1 but i get a dead android image when i boot to recovery?
[Shield Tablet Original Android Development] lj50036:
Flash TWRP, then reboot to bootloader, enter TWRP, you have to mount system rw for TWRP to survive a reboot..

One can do this with something like.....

fastboot flash recovery foo.img

fastboot reboot-bootloader

Enter recovery

Mount system rw

Thx Josh
[Shield Tablet Original Android Development] robgee789:
what a legend mate you are a star :):highfive:

edit: i just flashed supersu and now im stuck on the nvidia bootscreen?

edit 2 : i sorted it i was using the wrong supersu lol
[Shield Tablet Original Android Development] m0nt3s:
I wish twrp would add f2fs format option to repair file system
[Shield Tablet Original Android Development] Steel01:
Does any of the custom ROMs even support f2fs now? I know [MENTION=6411851]BitOBSessiOn[/MENTION] worked on it a while back, but it doesn't look like it's in current Bliss. Iirc, there were non-trivial kernel patches needed to support f2fs and I really don't want to work on implementation and upkeep of those patches. The kernels I ship are very close to stock.
[Shield Tablet Original Android Development] m0nt3s:
f2fs supported kind of

First off, Thank you so much Steel101 for replying to me and for all your work to make the shield a better device. I've been messing around and have almost successfully converted the stock ota fully to f2fs, I can't the the mount point for /system to stick in the fstab. As for twrp, i'll attach the file but, adb push mkfs.f2fs /sbin/ while in twrp recovery and it will automatically add it to repair change file system options. I'm looking for a better way but i found an apk that convert ext4 to f2fs on the playstore and while it took 35 minutes for my shield to convert the mm image it almost works, the updater script is setting the wrong permission. Do you have any advice or wisdom you could give me on getting the fstab f2fs mount to stick? f2fs will work untill i reboot and then it resets and ruins my morning. I'm appending .txt to the end of mkf2.f2fs so I can attach it, just remove the .txt before you push it.
[Shield Tablet Original Android Development] Steel01:
The fstab is in the boot image. To modify anything there, you'll have to extract the LNX partition, modify it, and flash it back. There are explanations around if you don't already know how to do so.

But I don't know how good the stock f2fs support is. There is experimental support, but I recall BitO pulling in the later stable support for his test. Dunno what the difference would be.
[Shield Tablet Original Android Development] BitOBSessiOn:
Stock kernel, when I worked on this, did not fully support F2FS. I patched BitO-K to support full F2FS and I was able to mount some parts... I had some experimental TWRP but all this work would need revision to work in latest kernel/system versions. Last time I revised, updating was not trivial... I also would have to revise actual stock F2FS support (if it's valid or not)... I would like, but ATM I'm very busy in other stuff... If I have time I will try, at least, to revise actual status, and how complex would be... but I'm not sure if F2FS provides so much difference in a practical scenario...
[Shield Tablet Original Android Development] BitOBSessiOn:
Experimental kernel for more complete and updated F2FS support available here.

Code in github, revised por OTA 4.3, available here.
[Shield Tablet Original Android Development] mrmathematica:
Please bring F2FS support if it is possible. Many thanks.
[Shield Tablet Original Android Development] BitOBSessiOn:
[EXPERIMENTAL] TWRP 3.0.2 F2FS modded

Download available for testing here.

This TWRP is based on [MENTION=2605798]nkk71[/MENTION] work (Thx!), and his MultiROM NO_KEXEC version, totally experimental, so you can expect any issue booting secondary ROMs. MultiROM support for installing, deleting, etc... in TWRP seems to be ok + F2FS support.

Main goal of this TWRP version was initially only proper F2FS support.

Github repositories

Kernel source, with full F2FS support (based on [MENTION=1416222]Steel01[/MENTION] and [MENTION=4937137]Bogdacutu[/MENTION] work, thx! ) here.

Modified device tree source code for TWRP, adding MultiROM + F2FS support here.

EDIT:

Updates:

MultiROM support to flash secondary Android N ROMs seems to be ok in 002 version, but N as sec doesn NOT seem to boot (probably MultiROM needs revision).

Booting MM secondary ROMs seems to be ok using latest [MENTION=1416222]Steel01[/MENTION] MultiROM ZIP
[Shield Tablet Original Android Development] Steel01:
Why wouldn't it? The official TWRP builds support all variants. Fairly certain all unofficial builds do as well, but I can't guarantee that myself.
[Shield Tablet Original Android Development] primaleph:
I just tried to use the new version of TWRP to flash /data to F2FS. Now /data is inaccessible in TWRP and I can't format it back to EXT4 either.

Going to try to reflash my Shield from a computer, but I could use a little guidance if anyone else has had this issue.
[Shield Tablet Original Android Development] BitOBSessiOn:
Ok, I will revise TWRP fstab... Thx
[Shield Tablet Original Android Development] BitOBSessiOn:
TWRP 003 version should fix this...
[Shield Tablet Original Android Development] m0nt3s:
This is the recovery that I've been using, I added a couple extra's into sbin such as nano, the newest libf2fs.so, an updated e2fsck, fibmap.f2fs, make_f2fs, and updated tune2fs and the updated fstab
[Shield Tablet Original Android Development] m0nt3s:
It's your fstab file, your missing /dev, I uploaded my twrp, flash it and try, let me know if you have any problems
[Shield Tablet Original Android Development] lmulli:
Why only version 3.0.2.0 when 3.0.2.2 has been out for ages?
[Shield Tablet Original Android Development] drewski_1:
The last digit is for device specific fixes, not a main TWRP code change. Maybe when an official F2FS versionn is released¿

https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
[Shield Tablet Original Android Development] hulkamaphone:
This is working well, thanks!
[Shield Tablet Original Android Development] TCGUK:
I don't know if it's officially supported but I just install the official update, flashed twrp-3.0.2-0 in fastboot, reboot to recovery to flash magisk, and booted the system with success.

One thing I did notice, though, was that there's something I can only describe as input lag (although I don't think it is). What I mean is you'll make a selection on the screen but nothing will happen until you touch or swipe the screen again. But hey, it works!
[Shield Tablet Original Android Development] gqukyo:
Is that lag only after it boots up or is always there?
[Shield Tablet Original Android Development] Steel01:
Use the latest official twrp 3.0.2-2, it works fine. The lag hasn't existed in the official builds in a long time.
[Shield Tablet Original Android Development] sky.walker:
Flashed the latest twrp via the Google play twrp app, then I updated to nougat via twrp and the file that was downloaded to my tablet located at /data/data/com.Nvidia.ota

Then flashed super.su and I have root and no problems so far (but play store isn't loading...) all done via twrp no pc
[Shield Tablet Original Android Development] gqukyo:
You can try to reflash again or do a clean flash to see if that worked. If the clean flash worked then it's probably not the file and something else is wrong with your upgrade.
[Shield Tablet Original Android Development] suicyko:
ahah sorry ! wrong command in fastboot !!

i used fastboot boot instead of fastboot flash ... shame on me !!!
[Shield Tablet Original Android Development] Exile1975:
Is there any chance of us getting the newest version (3.1.0.0?) It sounds like it might allow us to mount encrypted storage.

Thanks
[Shield Tablet Original Android Development] Steel01:
3.1 was built and released today.

What's wrong with encrypted storage? I fought for a while to get that working... Guess I'll add that to my list of things to recheck now. That list is growing.
[Shield Tablet Original Android Development] snebojsa:
So, when you used fastboot boot recovery, is it worked?

I'm completely stock, no root, no unlocked bootloader, and I want to do factory reset,

but want to save progress in some games, in /data/data folder.

To do that, I must root, to root I must unlock bootloader, when unlock bootloader tablet will reset and everything will erase,

so gamedata will be lost.

I think, If boot to recovery work, I will be able to copy/pull data from custom recovery.

Am I wrong?
[Shield Tablet Original Android Development] Exile1975:
Maybe someone else could confirm that TWRP is able to decrypt adopted storage, but it's unable to mount? If you tell me where or how I'll pull logs. This includes the 3.1 update unfortunately.

Edit:

It's kinda weird actually, there is a TWRP directory in the adopted storage that is accessible from recovery.
[Shield Tablet Original Android Development] suicyko:
Your logic is good but i think that the locked bootloader will surely block the action.

it's the purpose of the bootloader when it is locked.

All the actions must be done on unlocked bootloader.

You can try to reboot in TWRP recovery with "fastboot boot" command , but probably the bootloader will intercept this action and will refused it.

I don't know if the tablet will brick this way .. maybe u need to inform first.
[Shield Tablet Original Android Development] snebojsa:
You are wright, I just tried it, not working:

"FAILED, bootloader is locked"

Boot normally in system after.

I tried "adb pull" command, but it's not working either.

I can pull some files, like /system/build.prop but cannot /data/data/com.nvidia.valvesoftware.halflife2

Tried Helium Backup, it can backup apps and data even on non rooted devices,

backup was made successfully, but I will see how the restore will go.

EDIT

I unlocked bootloader, flashed twrp 3.1.0.0, supersu, boot ok.

Tried to restore Half Life 2 with Helium, completed successfully, but there is no option to load game, just new, so that didn't worked.

Restored Shadow Fighter 2, cannot complete the process, around 80% there is some error, but all progress was saved successfully.

Weird.

Will try further.
[Shield Tablet Original Android Development] Calystos:
Anyone have any issues with TWRP and SD cards with multiple partitions? Does it support multi-partitioned SD cards?

EG: Partition 1 is adoptive/internal storage, 2 is ext4/portable.

Tried this but it ignored adoptive storage and only used device internal storage. Seemed to only accept adoptive/internal storage if the whole of the sd card was partitioned as such. So can either be entirely adoptive/internal, or entirely portable. Haven't yet tried with two ext4/portable (or two fat32/ntfs/etc, or mix of different).

Is this right or is there a way of getting TWRP to work with multiple partitioned sd cards?
[Shield Tablet Original Android Development] SdtBarbarossa:
According to your fstab here:

https://github.com/TeamWin/android_device_nvidia_shieldtablet/blob/android-5.1/rootdir/etc/fstab.tn8

Its true that you only accept one partition on external sdcard. So if you want to accept more you need to add them
[Shield Tablet Original Android Development] Calystos:
Thanks an aye, that's what I figured too but was hoping there was an easier way rather than messing about with editing files/etc.

Shame doesn't have a built-in feature for stuff like multiple partitions, especially in regards to situations like migrated internal formatted partitions along with standard external formatted partitions on sd cards. Who knows, maybe they'll add a feature like that in the future, can hope, hehe. :)
[Shield Tablet Original Android Development] Steel01:
Do any twrp devices support multiple SD partitions? This may be more of an issue to bring up on IRC with the main developers.
[Shield Tablet Original Android Development] TotallyAnxious:
I think the HTC 10 just had this fixed and it's waiting to be merged in.
[Shield Tablet Original Android Development] NinjaCoool:
Anyone else having issues with AROMA installers? I'm trying to install A.R.I.S.E. Sound Systems but touch is not working in AROMA (hw keys are not working correctly too).
[Shield Tablet Original Android Development] OverBit:
For me touch input is rotated 180°.

Just try to touch in the upper left corner to hit next in Aroma installer.
[Shield Tablet Original Android Development] kepaware:
Same here
[Shield Tablet Original Android Development] Jintoki:
in my twrp 3.1 touch wont work. am i the only who have this problem?
[Shield Tablet Original Android Development] D-m-x:
Anyone know what to do when the adopted storage is unmountable? I keep getting "failed to mount decrypted adoptable storage device". I just flashed a Kernel.

Somehow whatever I do I can`t get in working, I even installed the Factory Image and wiped dozens of times.
[Shield Tablet Original Android Development] Sjamaan:
Try out TWRP builds from bitobsession. They are multirom and f2fs oriented, but adopted storage seems to work with them, at least for me.

https://www.androidfilehost.com/?w=files&flid=125651

Enviado desde mi shieldtablet mediante Tapatalk
[Shield Tablet Original Android Development] D-m-x:
You were right, coincidentally I tried that a few minutes before you wrote that and it fixed my issue ☺️

Thank you.

Gesendet von meinem Nexus 6P mit Tapatalk
[Shield Tablet Original Android Development] Steel01:
Finally got around to updating the TWRP official device trees. If you had a problem in the past, please try again and see if it's still there. Now that everything is updated, it should be easier for me to test and fix any problems.

NOTE: I've started using the newer kernel for twrp. That means the method to make twrp work on all bootloaders no longer works. I tried to port it over, but didn't have much luck. I'll try again sometime in the future, but for now, note that the latest build will only work on the M and N bootloaders.
[Shield Tablet Original Android Development] flatratte82:
I just tried 3.1.1-1 and got stuck in bootloop. It doesn't come beyond the nvidia logo.

I'm on 7.1.2 DU 11.5.

Did i do anything wrong ?
[Shield Tablet Original Android Development] Steel01:
Hmmm... Boots fine for me. Which bootloader are you on? My fastboot screen lists 4.00.2016.04-8b2413b7. That should be the one I posted with my Lineage 14.1 builds, available on my AFH account.
[Shield Tablet Original Android Development] flatratte82:
my fastboot screnn says:

[bootloader] (version UNDEF_BUILD)

Seems like I need a bootloader update. Could you point me into the right direction for this? :)

Edit:

I found the firmware update here: https://www.androidfilehost.com/?a=show&w=files&flid=27599

I installed 'shieldtablet-firmware-50-update.zip' and now my bootloader version is the same as yours.

twrp 3.1.1-1 is booting and working fine. Thanks :)

Maybe it would be helpfull for others if you could add these hints to the 1st post ;)
[Shield Tablet Original Android Development] Steel01:
Hmmm... That sounds like you had one of the M bootloaders which *should* have worked. When I have a bit of time, I'll have to test against the different bootloader zips I've got available.

I have a note on the TWRP sites device page about bootloader. ;) And there's a blurb on the download page about 'if this doesn't work, update your bootloader'.

Edit: Once Lineage 14.1 goes official (hopefully this week), I'll have a link to the latest bootloader in the OP over there.
[Shield Tablet Original Android Development] Luca-91:
[MENTION=1416222]Steel01[/MENTION] thank you very much for your work! However the latest TWRP release (3.1.1-1) have a bug that prevent me from browsing my internal memory (I've an unified internal+SD). Can you give it a look please? Thank you so much!

PS: I know that at least another guy had this issue (from reddit).
[Shield Tablet Original Android Development] aury92:
same problem with the SD card here. Also, how did you update the bootloader?´with the .zip? I seem to have the exact same issue.
[Shield Tablet Original Android Development] drewski_1:
looks like its a TWRP flashable zip.

or extract the blob from the zip and flash it with Fastboot
[Shield Tablet Original Android Development] grimreaper1014:
Will this work on the Nvidia Shield tablet that's rooted with Lineage OS 7.12? I seen people got it running on older versions. I tried flashing the framework and installing the app. I am getting this message though.

Xposed is not yet compatible with Android SDK 25 or your processor archetype.

Cannot link executable
[Shield Tablet Original Android Development] PlasmaPump:
[MENTION=1416222]Steel01[/MENTION] Will you be releasing an update to TWRP for shieldtablet? All my other devices got Official TWRP 3.2.1.

Thanks
[Shield Tablet Original Android Development] Steel01:
New builds are up as of a few hours ago. And some issues should be fixed finally. Like, adopted storage should actually work. If any issues are found, new or old, please report them. I'm more easily able to push in updates and fixes now.