yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Android Development] drewski_1:
SuperPichu's kernel says it has the kexec hardboot patch. Has anyone tried that to sync w/ controller and/or with MultiRom?
[Shield Tablet Android Development] BitOBSessiOn:
I think that somebody has reported [MENTION=2672500]SuperPichu[/MENTION] kernel worked to sync controller, but this kernel has problems with multirom too... although [MENTION=1416222]Steel01[/MENTION] remarks that sometimes, about a TWRP bug, it's necessary flash second ROM twice...
[Shield Tablet Android Development] m666p:
i dont know what im doing wrong ,i followed aceclifts steps to install ubuntu but it will just get stuck at the nvidia logo i have the wifi only version and i just unlocked bootloader etc today on latest stock , any help appreciated
[Shield Tablet Android Development] wiQbold:
I would say you did not install the kexec-boot.img or forget to inject the boot sector
[Shield Tablet Android Development] m666p:
[MENTION=1312247]wiQbold[/MENTION]

i injected the current boot sector after installing the ubuntu mrom and before rebooting ,also should i install the kexec-boot.img again after installing ubuntu
[Shield Tablet Android Development] wiQbold:
what I did:

backup data

install of the stock 2.2.1 Update (clean)

install twrp

install kernel

install multirom

reboot recovery

install Linux4Tegra

inject boot sector

and rotate the multirom ui 180° that, but this is not important..

but if the nvidia logo will show up without that it reboots, the hardbootpatch will not work, for my understanding (?!)

that s what happen if I use another kernel, then Bogdacutus..

my device LTE EU
[Shield Tablet Android Development] Steel01:
[MENTION=4937137]Bogdacutu[/MENTION] hasn't had time to work on this project much lately, so he's passed maintainership on to me.

I've finally been able to replicate a working kexec patch and have it working on a CM kernel. I've built an aosp kernel, but haven't inserted it into a stock boot image to test yet. But it should fix several problems, a major one being broken controller support on the internal stock rom. I'm building twrp unmodified from Tassadar and all the secondary flash and update issues seem to be fixed. I'm trying to push all the changes needed to multirom and kexec-tools upstream, so no forks will be needed to maintain this.

Testing on the changes is still ongoing, but I hope to have builds of everything up this weekend or early next week. That will include boot images for stock wx_na_do, wx_un_do, wx_na_wf, and cm wx_na_do and wx_na_wf; multirom v32; and Tassadars TWRP 2.8.6.0.
[Shield Tablet Android Development] Steel01:
Well, I'm having issues finishing up TWRP and Multirom proper right now. But the boot images should work with what Bogdacutu already released and doesn't have the controller problem that I was seeing. Until I finish everything up, I'm not going to update the opening post. See my folder here for the stock boot images.

Edit:

A build of TWRP is now available in the folder linked above. It's marked experimental because in testing, the script to set the model didn't always run correctly. But, this should manage secondaries correctly. For those on wx_un_do and wx_na_wf, can you check the props ro.product.device and ro.product.model and verify they're set correctly? ro.product.device should be shieldtablet for all devices. This covers all ROMs I know of, they assert shieldtablet. Then ro.product.model should match your device. This should cover any future ROMs that want to install differently based on model.
[Shield Tablet Android Development] wiQbold:
many many thanks steel

Update:

Controller working.

at first Boot my Touchscreen and buttons won t recognized for a while.

but only a few seconds.

get error when I try to install stock or CM12.1

THANKS A LOT

but there are a login for your folder!? how can I access it?

"

access denied

looks like you don't have permission to access this folder. Make sure you are signed in to an account that has permission, or check with the developer to request access.

"
[Shield Tablet Android Development] Steel01:
Oops, I linked the upload page instead of the folder. Fixed... That's what I get for doing stuff that late at night.
[Shield Tablet Android Development] Steel01:
Okay, I think I have the opening posts updated with everything. Only known issue is the minor annoyance that touch takes two seconds to initialize for the boot selection screen. Everything else should work as intended. If it doesn't, please let me know. Installation should be all explained up front.

NOTE TO ROM PRODUCERS:

My unified TWRP only differentiates between WF and DO (it picks wx_un_do). There is no hardware difference between wx_na_do and wx_un_do. The props to note:

ro.product.device = shieldtablet (always)

ro.product.model = wx_na_wf or wx_un_do (based on bootloader parameters)

So, assert shieldtablet to allow installation on any model. Assert wx_na_wf to lock to wifi only. Assert wx_un_do to lock to lte models. Or parse ro.product.model for a fancy install script. My new CM builds assert as shieldtablet and autodetect model on boot using the same init code the TWRP build does. Multirom only asserts shieldtablet, so any recoveries that want to support this should set ro.product.device to shieldtablet.
[Shield Tablet Android Development] lowsum:
Thank you so much Steel, TWRP with usb-otg support is a god-send... I've been waiting this for months. Keep up the good work! Everything works well so far!

Edit: After installing newest multirom and twrp, I successfully booted my previously installed rom so I decided to give your newest cm12.1 a shot. I installed it as a 3rd rom (secondary) but it installed it over my primary stock rom. Hopefully I did a backup prior this glitch. While restoring I encounter another little bug, during the restore process I tapped the screen several time without unlocking just to check the progress. At the end I had multiple unlock slider stacked so I had to unlock 4 consecutive slider lol. Just a little annoyance. Otherwise usb-otg backup works very well!
[Shield Tablet Android Development] berryman13:
So the torch has been passed, eh?

Grats man :P

I guess it's time to finish transitioning over, i admire your work and am using your kexec-tools to help me in my own!
[Shield Tablet Android Development] vincentjuanFR:
double kernel possible ?

Hey guys !

Does this allow the use of stock plus superpichu kernel and switch to bito-r cm plus klx kernel ? I would really love to get the very best of both worlds.

Thanks in advance ! If there is another way to get my shield to have gamestream and console mode operable and a flying daily driver aside please enlighten me about your personal setups. :fingers-crossed:
[Shield Tablet Android Development] BitOBSessiOn:
You can use MultiROM with stock as primary and whatever you want as secondary, but you have to install on primary a compatible kernel like one attached in this thread or any BitO-*** (my actual conf). Superpichu's is patched originally but I don't know if is updated enough to work fine. You always can try...

Let us know ;)
[Shield Tablet Android Development] vincentjuanFR:
Thanks a lot bito! Will try that as soon as i get home !
[Shield Tablet Android Development] ailima:
I'm cross posting this here because I'm not sure that anybody reads the Q/A section anymore...

Is anybody else having a hard time using the external_sd in twrp to install roms on? Twrp seems to only mount my 64gb ntfs drive in ro mode and multi boot won't even mount it at all. :(

Any help would be much appreciated! :)
[Shield Tablet Android Development] koop1955:
Have you tried running SDFix, https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en

That might solve your problem.
[Shield Tablet Android Development] ailima:
Thanks, but the issue is from within twrp itself. I already ran sdfix from all my roms. I just want to be able to mount external_ad in twrp so I can put a large rom on the sd card. :)

Thanks!
[Shield Tablet Android Development] aceclift:
hi,

i have a bug where i cant use touch in multi rom even with the touch support installed, can someone tell me what i might be doing wrong.

The previous versions of multirom i could use touch

aceclift
[Shield Tablet Android Development] gavin-phelan:
I just get a hang on factory resetting using your twrp
[Shield Tablet Android Development] BitOBSessiOn:
Sometimes touch takes about 3 or 4 seconds to work... Keep cancel button pressed during default boot and it should work.
[Shield Tablet Android Development] xanthrax:
yes , the touch screen responds after 2 seconds , not a biggie , I set up the timeout boot to 10 seconds
[Shield Tablet Android Development] aceclift:
it never responded for me at all the though, no matter how long i waited and even when i reinstalled it it still had the issue for me. i had to use hardware keys to navigate it (massive annoyence).

it isnt how im installing it either as i have used the last one and it worked fully
[Shield Tablet Android Development] Steel01:
Does touch work in TWRP? The touch support is nigh identical between the two, though pulled from different locations (TWRP has it baked in, multirom has to pull it from the /data partition). I haven't personally tested a clean install for a while (haven't wanted to wipe my internal sd to do so), but I probably should test that again. Has anyone else done a clean install recently and confirmed it working. Flashing TWRP, installing the multirom zip, then the touch support zip?

As a side note, you want to talk about annoyance... I still can't get touch to work correctly on the Portable. And for a while, I couldn't get the hardware keys to work either. I had to change the autoboot default through TWRP to change ROMs. :P
[Shield Tablet Android Development] aceclift:
yeah my touch works fully in twrp
[Shield Tablet Android Development] xanthrax:
I would suggest you then a clean flash of the multirom and twrp multirom

Also, use the kexec patched stock kernel from the OP if you're using stock as primary, as I do and it works perfectly

Sent from my Darkside of 1+1
[Shield Tablet Android Development] BitOBSessiOn:
Any of BitO-K kernels can work fine on Stock too with MultiROM. I invite to test them (I recommend latest KL-021). Thnx.
[Shield Tablet Android Development] xanthrax:
I'll try it [emoji57]

Sent from my Darkside of 1+1
[Shield Tablet Android Development] aceclift:
ok, thanks I will give it a go when I next install multirom (probably when 5.1.1 is out officially from NVidia)
[Shield Tablet Android Development] Primetime_de:
Same problem, nothing fixed it for me so far. Tried it with patched Stock Kernel from page 1 and with KL-020 and KL-021.

In TWRP touch is working.
[Shield Tablet Android Development] aceclift:
Yeah, good to know that I'm not the only one and that this issue can be replicated. so that the devs know it is something to look at and fix for the next version.
[Shield Tablet Android Development] ailima:
I'm still having difficulty mounting my sdcard in twrp in order to put roms on it. I can install to internal no problem ... But I'm out of space on internal. Has anybody been able to install roms onto the sdcard?
[Shield Tablet Android Development] xanthrax:
Nope, I didn't, in which format is your SD card? I have 64 gb ntfs

Sent from my Darkside of 1+1
[Shield Tablet Android Development] Steel01:
I'll try a couple things today to see if I can reproduce the touch failure. But if I can't reproduce, I don't know what I can do. Either of you with the problem, are you comfortable with adb and the Unix command line? Debugging on the install with the problem might shed some light on it.

I don't have an SD card to test with right now (Ubuntu is installed on mine), so I can't verify installing ROMs there. But xanthrax is way ahead of me. I'd only add that ext2/3/4 have the best support, though fat, exfat, and ntfs should work as well.
[Shield Tablet Android Development] xanthrax:
I may try later other formats, I have some spare SD cards somewhere in my drawers but on this one that I use, 64 gb Samsung sdcard, ntfs format, when trying to flash a second RoM it fails, fail to mount external SD card

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] Steel01:
Oh, I misread what you said. I thought you said it worked for you. Okay, I'll see if I can't dig out one of the little 4GB cards I've got floating around (dev boards used to ship with several of them, not really generically useable for a tablet with 32GB internal) and see if I can't make it work. For the portable, I have to remove NTFS and exfat to make twrp fit. I might have accidently left that patch in when I built for the tablet, but I don't think I did.
[Shield Tablet Android Development] xanthrax:
Ohh, sorry for misunderstanding... I'll try in a few minutes, if you have a test build just pm me if you feel like

Sent from my Darkside of 1+1
[Shield Tablet Android Development] Steel01:
Try this:

https://www.androidfilehost.com/?fid=23991606952608116

Shouldn't be any different from the last build, but ya never know. I do know this one was made correctly from my build scripts.

I found the problem with the touch support zip. For some reason, the app I used to create the zip didn't preserve the permissions, so the two executables aren't marked as executable. As soon as I figure out how to modifiy and repackage the zip, I'll reupload it and fix the link in the install instructions.
[Shield Tablet Android Development] xanthrax:
nope it couldn't mount the sdcard...

I don't have the touch problems, it works fine

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] Steel01:
To those with touch problems in the boot manager, please redownload the touch support zip in the second post. It should work correctly now. Sorry for the trouble, I must not have tested a clean install.

New one still doesn't mount the external sd? This may be a worse problem. I wonder if it will mount anything in any part of recovery. I'll have to do some research to see if this is my problem or upstream. Unfortunately, my officially supported Nexus 5 doesn't have an external sd slot for me to test upstream...

Edit:

Well, my Ubuntu root automounts in twrp. I can go to Advanced->File Manager and browse to /external_sd and it's mounted. Does any ntfs formated cards show up like that? I can't try for several hours yet.
[Shield Tablet Android Development] xanthrax:
weird things happened...

I unmounted the SD card, well, it doesn't make sense of course but then I tried to flash on my 64gb ntfs SD card and... the flashing process started.

There were 2 lines where "failed to mount data" appeared but the flashing process has been completed

then I mounted again the SD card but the rom doesn't show on the list

I then saved the recovery log but after reboot I just can't find it even though "log successful copied to internal storage"

I'm in the primary RoM and using solid Explorer guess what? on the sdcard there is a folder with the RoM I flashed but incomplete, there's no data files

And yes, when in recovery, the SD card it's visible and also I can copy /paste files from and to it without problems

I'll try a different format, fat 32 and then ext 4

sent from my Darkside of SHIELD Tablet
[Shield Tablet Android Development] Steel01:
So... If you unmount it, it half works? It might be trying to mount irregardless of if it's already mounted.

I've seen that data problem before. Right before it completely nuked the internal data partition on my portable... Hope you have a good backup. I'm guessing it fails to unmount the internal data partition before it tries to mount the multirom version. But, I have a place to start looking now.
[Shield Tablet Android Development] xanthrax:
Fat32... Same 4gb sdcard that I've already tried once but with ntfs and it failed to mount upon flashing , now successful flash!

Unfortunately when booting into multirom menu the ROM I've installed doesn't show up on the internal section, which shouldn't be the case but not even on the second section where is searching for USB storage so there's apparently no way to boot into it

The ROM shows though in the recovery multirom

Sent from my Darkside of 1+1
[Shield Tablet Android Development] ailima:
Thank you for all the support, guys! I am in the exact same boat as Xanthrax. Samsung 64GB ("Pro") formatted with NTFS. Mounts in the TWRP File Manager just fine but won't mount for a ROM slot.

Also same behavior ... it tries to mount and install but it gives the error message.

Just to be clear, it mounts and works just fine from any of my actual ROMs.

Thank you again!

---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------

Thank you for this. I have experience with both of those things. I'll look into it when I get to a pc. Won't be for at least a day though.
[Shield Tablet Android Development] xanthrax:
I want to mention that the ROM I flashed works perfectly on the internal storage though

Sent from my Darkside of 1+1
[Shield Tablet Android Development] Steel01:
How is that external sd partitioned? Here only checks partition 1, it would miss anything on a card that didn't use partitions. As opossed to the S4 port which checks both no partition and partition 1. I wonder if that has something to do with the boot menu missing your install, xanthrax.
[Shield Tablet Android Development] xanthrax:
I don`t know how to check that , it`s only NTFS without any other partitions
[Shield Tablet Android Development] Steel01:
Ummmm... One way: when the card is mounted in twrp, go to the command line and run 'mount'. Find external_sd in the list, and see what device is associated with it.

Edit: this is for the fat32 card that installed, but didn't show up in the boot list.
[Shield Tablet Android Development] xanthrax:
Here's what is showing for my 64gb ntfs sdcard that it failed to flash

Sent from my Darkside of 1+1
[Shield Tablet Android Development] xanthrax:
And this is for the 4gb fat32 sdcard where the flash went fine but the gapps failed, maybe bad zip, error Executing binary zip, and the ROM doesn't show up in the boot menu to chose it to boot

Sent from my Darkside of 1+1

---------- Post added at 11:23 PM ---------- Previous post was at 11:21 PM ----------

Sent from my Darkside of 1+1
[Shield Tablet Android Development] ailima:
Both of those use Partition 1. I didn't know you could create an NTFS without a partition...

The VFAT one mounts to /mnt and the NTFS one mounts to /external_sd ... hmm

Furthermore, the NTFS partition is mounted read only while the VFAT partition is mounted read/write
[Shield Tablet Android Development] Pariahnoble:
I don't know if it helps. But I had some issues with twrp not mounting my system partition recently. I switched from cwm to your patched twrp build using flashify, I rebooted to twrp and fully wiped everything, flashed a rom but I didn't do the multirom install. I'm not really using that feature yet but want to be ready to once I get a pc handy for Ubuntu (going to attempt to get skyrim or fallout new Vegas running locally on the tablet, not streamed) so I didn't flash the multirom install, anyhow, it seemed to flash OK, then went to flash gapps and it couldn't mount /system. Tried to reboot, and go back into twrp, twrp failed, got the bug droid where u can press volume up and power to get to nvidia recovery, no rom on internal, I got lucky and flashed the 2.2.1 ota in that recovery, reinstalled twrp and flashed the multirom install, I still don't use it but, twrp worked fine this time. Dunno if that helps, I obviously don't have logs lol, but I did notice a problem with mounting...
[Shield Tablet Android Development] xanthrax:
You think I should have create a ntfs partition on the sdcard and then formate it?

I only formated it to ntfs using partition tool in Windows

Sent from my Darkside of 1+1
[Shield Tablet Android Development] ailima:
You partitioned it the correct way.

I wonder what would happen if we created a second ntfs partition and tried to use that. The first would go to /external_sd and maybe the second would go to /mnt

...also, I seem to recall the early days of this tablet, the recoveries were having a hard time with the external sd. I wonder if this build use an older code base with those bugs?
[Shield Tablet Android Development] xanthrax:
Yes, I remember that though I'm not so deep into shield stuffs, just started my researches...

So, sdcard fat32 flashes well but doesn't show up in the boot menu

I'll give a try to a otg ntfs as fat32 format didn't work, flashed but failed to write data partition "not enough space" though there was more than 25 gb... [emoji19]

Sent from my Darkside of 1+1
[Shield Tablet Android Development] ailima:
I suspect, TWRP might be looking in the wrong place for the external_sd.
[Shield Tablet Android Development] joethc:
will this work for the latest 3.0 (5.1) update?... not askin eta just curious if this is planned?? ubuntu on shield is amazing... thanks again everyone!!
[Shield Tablet Android Development] geotherm:
No. The kernels are not yet compatible.
[Shield Tablet Android Development] Steel01:
I've been without decent internet for the last 24 hours, so I'm just now starting to look at this. Booting into 3.0 for the first time. I'm going to try using the kernel from 2.2.1 in a 3.0 boot.img. If that works reasonably well, I'll release a *temporary* image until Nvidia decides to release the sources where I can do it right.

Edit:

Well, it boots when I do that. It is a different kernel revision though, so who knows what is different. It's the same major.minor.build (3.10.33), though. It shouldn't be horridly different. I'm pulling all variants of the ota's to repackage the boot images. I'll upload and post links here when done. I won't update the opening post however, since these will not match upstream. And getting that will be dependent on Nvidia as mentioned above.
[Shield Tablet Android Development] Steel01:
DISCLAIMER:
USE AT YOUR OWN RISK.
These have not been thoroughly tested and do not use the same code as Nvidia's stock 3.0 kernel.

kexec_boot_stock_na_do_30_wip.img

kexec_boot_stock_na_wf_30_wip.img

kexec_boot_stock_un_do_30_wip.img

That being said, I doubt any real problems will arise from using these. But when I do get the code from Nvidia to do this properly, you will want to update.
[Shield Tablet Android Development] Steel01:
Update for those interested in booting from an external sd. Apparently I did my job too well when I was cleaning up the init devices code. I wasn't initializing the external sd for the boot selection. I've added that and was able to select CM from my extremely slow 4 GB sd card. Something is failing on boot, though. I don't know what yet, though. I formatted mine ext4 and was able to install the rom, then flash gapps on top of it. Word of caution to those playing around with this: somehow I confused the multirom system and ended up flashing over my internal rom instead of to the external sd. I have no idea how I did this, only that I did not leave the multirom section of TWRP. So as always, keep a good backup of your internal rom around just in case the worst happens (like I failed to...). The updated multirom zip is in the second post. Let us know if you get something to boot. And if you have any success with other partition types.

Edit:

I deleted and reinstalled the secondary on the external sd and it booted correctly.

Edit 2:

But oh my goodness... If anyone wants it to be usable, use a much higher class card than I'm testing on. Took a good 10 minutes to finish booting and 10+ second lag between pressing next and the next setup wizard page coming up.
[Shield Tablet Android Development] xanthrax:
I think I know what happened when you lol flashed on top of your main RoM... you haven't selected the sdcard partition when choosing the RoM I suppose

have you tried to flash as secondary as secondary the same RoM that you have had as primary?

I'll give a try asap, sounds great but yes, a. slow sdcard may make this feature useless, let's see

The 3.0 patched kernel for the WiFi version boot fine, I haven't noticed any problems

-=-=-=

my 64gb ntfs sdcard failed to mount again, I'll try more later, I'm at work atm [emoji41]

sent from my Darkside of SHIELD Tablet