yashsingh1/xdaforums huggingface dataset:
[Shield Tablet Original Android Development] xaxxelous:
I've spent all day with it and can't get tr to work either. Same error about ensuring I'm connected to the internet, but I'm also having some WiFi issues. I can connect to the internet and do a speed test most times, log into Google and open the play store, but anytime I try to download an app my WiFi symbol disappears and I get a no connection error.

Might not want to troubleshoot that since I don't need persist images, but if I did I would go to LOS 14.1 with TWRP 3.2.1 and Magisk. From there I'd follow the LOS 16 wiki. Thats how I got both my Tangos to 16 in the first place.

Edit, update: I connected a USB ethernet adapter to my dock, turned off Wi-Fi, and made sure I was connected to the internet by downloading a large file. While the file was downloading I tried towelroot and still got the same error, fwiw.
[Shield Tablet Original Android Development] jjmcousineau:
Is LOS 14 good enough to get GApps working? I just want to use this as a stationary clock/media device as I have a few docks also.
[Shield Tablet Original Android Development] xaxxelous:
I wouldn't recommend it. It wasn't stable for me. It would randomly reboot all the time, etc. 16 is solid and well worth the update.
[Shield Tablet Original Android Development] akw701:
I think the SU is the solution. If the Super User is installed Here is how it worked for me:

I had TWRP installed first. From there I followed the thread instructions. Worked like charm. With TWRP I installed the the 14.1 rom from highwaystar_ru. No problems so far. Then I saw npjohnsons Lineage 16 and wanted to Upgrade. But being a beginner I stumbled into several pitfalls with ADB (Tablett was in recovery, but it needs to be booted into the normal system) The towelroot Su from the instructions did not work. Thought I had to roll back to kitkat. Got the Rom from the link in the TWRP thread. But next pitfall, I installed it into micro sd card folder. Did work when I shifted everything to the internal memory Backup folder. Being back on kitkat I tried towelroot again to gain SU access. No success either. But I got lucky with "SupersSU v2.82 SR5 Beta" from droidfilehost.com page.

With SU applied, knowledge that for Adb commands the tablet had to be normally booted, I followed the instructions for Lineage OS and succeeded in installing.
[Shield Tablet Original Android Development] drarbo1:
Hey y'all. Admittedly, I'm not the sharpest knife in the drawer, but I have rooted my Shield tablet and re-imaged them, took Unix for the NAS class for FAA, so I may be knowledgeable enough to be dangerous. I wanted to make double sure reading the wiki instructions. My Yellowstone tablets are still Kitkat and I'm going to follow the "Update to a newer vendor firmware version" instructions first, then proceed to the "Installation" instructions, and ignore the "build yourself" and "update to newer and higher version" instructions. Am I correct in my assumption? Thank you
[Shield Tablet Original Android Development] npjohnson:
yes
[Shield Tablet Original Android Development] drarbo1:
Thank you, thank you.
[Shield Tablet Original Android Development] drarbo1:
Forgot to ask, I had seen where putting my tablet in “Dalvik” cleared up and issue wit google play continuously crashing, which it did. Would the installation of this rom be affected by being in Dalvik as opposed to ARM? Do I need to put it in ARM before upgrading? And does this new OS automatically update or would I need to install an updater app?

Thanks yet again
[Shield Tablet Original Android Development] npjohnson:
Nope - follow the firmware upgrade guide, then install guide. That simple.
[Shield Tablet Original Android Development] alefoi:
I tried to enforce selinux by setenforce 1 --- it works but the touchscreen is not responding (it starts responding again once one issues setenforce 0 via adb). Is there any way to fix this?
[Shield Tablet Original Android Development] npjohnson:
Lol - it's permissive because sepolicy hasn't been written.

Of course it's not gonna work. Unless you wanna write sepolicy from scratch for this device? lol
[Shield Tablet Original Android Development] _shagohod_:
Somebody tested the 18.1 ?
[Shield Tablet Original Android Development] npjohnson:
Not ready yet. Did not intend to publish that.
[Shield Tablet Original Android Development] drarbo1:
I need to ask possibly a stupid question. Is there a list maintained on here, XDA, or another related site, of folks who could or would be willing and/or able to do these things for us less experienced for a fee? Sure would save me headaches. Different things I’d have done, rooting devices, different roms, etc.
[Shield Tablet Original Android Development] eekcat:
Can I get "persist.img and persistbk.img" ?

I foolishly ran "flash.bat" without checking the backup.

So my tango is brick.

Please help me.
[Shield Tablet Original Android Development] npjohnson:
meh, here: https://download.ods.ninja/Android/lineage/yellowstone/

Tell me when you have it so I can remove it.
[Shield Tablet Original Android Development] muellerm30:
I've just flashed the 09/08 OTA update and now will not boot the OS. Stuck on the Nvidia logo. I've reflashed the image in recovery and the recovery in fastboot. Wiped cache in recovery. Are there any recommendations to fix this without wiping?
[Shield Tablet Original Android Development] xaxxelous:
Will you let us know how that works for you? I'm about 99% sure I flashed one of my Tangos persist image to another Tango and it messed up the Wi-Fi.

You did this on a Google Project Tango tablet and not an Nvidia Shield, right?
[Shield Tablet Original Android Development] muellerm30:
on a shield using odd's builds from https://updater.oddsolutions.us/yellowstone#/devices/shieldtablet/builds
[Shield Tablet Original Android Development] xaxxelous:
Not sure why that's under yellowstone since those look like Shield builds, but I think you're in the wrong thread. This is for the Project Tango, which is close to the Shield but different.

Maybe use these:

Odd Solutions Downloads

updater.oddsolutions.us
[Shield Tablet Original Android Development] npjohnson:
It isn't under it, # resets the path, someone made a janky URL for no reason.
[Shield Tablet Original Android Development] npjohnson:
See above
[Shield Tablet Original Android Development] muellerm30:
same builds or just a borked URL?
[Shield Tablet Original Android Development] npjohnson:
Borked URL.

There are different links for both devices.
[Shield Tablet Original Android Development] muellerm30:
Oh ok awesome. I was able to fix it by flashing the previous build. I might try the OTA again.
[Shield Tablet Original Android Development] nunitofiman:
22/08?
[Shield Tablet Original Android Development] muellerm30:
Yes that's correct.
[Shield Tablet Original Android Development] eekcat:
It works. Thank you very much.
[Shield Tablet Original Android Development] eekcat:
Wi-Fi works fine.
[Shield Tablet Original Android Development] eekcat:
"lineage-16.0-20220908-UNOFFICIAL-yellowstone.zip" seems to be the problem.

Only the Tango logo is displayed and the reboot continues.

I am currently using "lineage-16.0-20220810-UNOFFICIAL-yellowstone.zip".

It is the same both in "System" -> "Updater" and in recovery sideload.
[Shield Tablet Original Android Development] npjohnson:
I'll take a look.
[Shield Tablet Original Android Development] xaxxelous:
Darn, shoulda grabbed it to try.

I wiped and redid both of mine last week. I could only get 20220717 to work.
[Shield Tablet Original Android Development] akw701:
I am having the same problem. But I have not tried to wipe the system. Is there a chance to apply an update via recovery? Where are the Images stored on the yellowstone tablet to use the July update?
[Shield Tablet Original Android Development] npjohnson:
I'll fix this tomorrow. Next build will work fine.
[Shield Tablet Original Android Development] gumbyx84:
Not to be a pain, but has the issue mentioned above been fixed? I'm planning on using my Shield K1 for game streaming and wouldn't mind trying the Project Tango image so it can run the latest version of Android it can.

3 related questions:

Is this more stable than the unofficial LineageOS 14.1 image (https://xdaforums.com/t/rom-unofficial-lineageos-14-1-lineageos-15-1.3950786/)?

Does it run better than the unofficial LineageOS 14.1 image (https://xdaforums.com/t/rom-unofficial-lineageos-14-1-lineageos-15-1.3950786/

Can I use the latest Official Shield Tablet TWRP image (twrp-3.6.1_9-0-shieldtablet.img) or the unofficial Project Tango K1 ATAP TWRP from highwaystar_ru (https://xdaforums.com/t/recovery-twrp-project-tango-k1-atap-twrp-3-2-1.3901519/)?
[Shield Tablet Original Android Development] xaxxelous:
You don't need to wait or be a pain. The July 17 build works. Its the best there is for the Tango.

I can't speak for using a Shield recovery on a Tango, but doubt it'll be good. Use a recovery for the same version of Android you're running. I think this speaks to it:

https://xdaforums.com/t/recovery-twrp-project-tango-k1-atap-twrp-3-2-1.3901519/post-83728333
[Shield Tablet Original Android Development] Rob2too:
I am also having no luck with towelroot on my Tango stuck at 4.4.2 and owned since unboxing! Any ideas would be most welcome. :)
[Shield Tablet Original Android Development] akw701:
I don't want to push, but.....

I am running the July build until there is a new one..... tomorrow :-))
[Shield Tablet Original Android Development] npjohnson:
building right now, but Yellowstone is last in the list - so maybe 20 hours?
[Shield Tablet Original Android Development] akw701:
Many thanks, the November Version works again very well!!!

Regards

Send from my freshly updated Project Tango Tablet
[Shield Tablet Original Android Development] LiarOnce:
The updater is broken or removed?
[Shield Tablet Original Android Development] npjohnson:
under repairs.
[Shield Tablet Original Android Development] jemail:
Can these builds be flashed on the OG nvidia shield tablet?

I see you have stopped publishing nvidia shield tablet versions, was that due to instability of those builds?
[Shield Tablet Original Android Development] npjohnson:
No they can't.

And yes.
[Shield Tablet Original Android Development] neveroddoreven:
Hi, just getting started, not new to Lineage or ADB, but new to wrangling a Project Tango tablet development kit (NX-74751) that I saved from being trashed. The first stage of the oddsolutions.us Install page linked in this thread's first post has a prerequisite in the second red-banged box, saying that my device needs to be running Android 9 (PCSI) firmware. I also see in this thread some references to "yellowstone_pie_psci.zip", but there is no link or mention on how I should get/install it. Is this link the PCSI firmware that I should use, and if so, how should I apply it? I cannot find any other file by this name, anywhere that's readily found on Google or Bing.

https://download.ods.ninja/Android/firmware/yellowstone/yellowstone_pie_psci.zip

My device is running 4.4.2 with kernel string Tango@Atap #1, build number KOT49H.161129. Using fastboot recovery flash, it refuses to flash the recovery-yellowstone image in the same folder as the pcsi zip link I pasted above, returning an InvalidSize error.
[Shield Tablet Original Android Development] jponasgoldbaum:
Hi,

having problems returning to stock rom.

when moving to PowerShell and entering the command for moving persist.img the following error appears:

+ adb shell su -c dd if=/dev/block/platform/sdhci-tegra.3/by-name/PES o ...

+ ~~~

+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

adb shell su -c dd if=/dev/block/platform/sdhci-tegra.3/by-name/PES of=/sdcard/persist.img

using win 11.

someone can help?
[Shield Tablet Original Android Development] npjohnson:
you need root access
[Shield Tablet Original Android Development] jponasgoldbaum:
how to?

towelroot does not work and devweloper options it already says root acces on adb..
[Shield Tablet Original Android Development] npjohnson:
then just run adb root and do it from there
[Shield Tablet Original Android Development] jponasgoldbaum:
now this error shows up:

/system/bin/sh: su: not found
[Shield Tablet Original Android Development] npjohnson:
Because you don't need to use su. Just run the quoted command after su
[Shield Tablet Original Android Development] neveroddoreven:
Towelroot v3 doesn't work for me either. Here are the steps I used to root and install.

Ensure you can connect to your Project Tango tablet running stock KitKat 4.4.2 on ADB. Image is here, instructions mentioned at start of this thread.

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

download.ods.ninja

Ensure the bootloader is unlocked.

adb reboot bootloader
fastboot oem unlock

Use the tablet buttons to reboot back to normal.

On your PC, download twrp-3.2.1-yellowstone.img for Project Tango K1 ATAP.

https://xdaforums.com/t/recovery-twrp-project-tango-k1-atap-twrp-3-2-1.3901519/post-78936790

On your PC, download SR5-SuperSU-v2.82-SR5-20171001224502.zip from Chainfire's personal website.

SuperSU Download

Push the SuperSU zip file to your tablet, and in the process rename it to easier-looking supersu.zip.

adb push C:\Users\YOURUSERNAME\Downloads\supersu.zip /storage/sdcard0/supersu.zip

Switch to bootloader mode.

adb reboot bootloader

Do a one-time boot of TWRP (without flashing it!).

fastboot boot C:\Users\YOURUSERNAME\Downloads\twrp-3.2.1-yellowstone.img

Once TWRP loads on the tablet screen, touch the Install button.

Scroll down to find "supersu.zip" and select it.

Slide the swipey-thing to install SuperSU.

When it succeeds, it offers a Reboot button. Use it to reboot.

After the tablet boots back to normal mode in stock KitKat, unlock the screen.

Use ADB to see if your su is installed

adb shell
su

You should see root running:

root@yellowstone:/ #

NOTE: upon unlocking the tablet screen, the tablet will re-optimize its apps for awhile. It's fine.

NOTE2: if you close and re-execute su in adb shell, for now you will have to ensure your screen is unlocked so you can accept the SuperSU popup UI.

Now you can start with step 3 in this firmware update guide. But you'll change up the steps 6 and 7.

Update firmware on yellowstone | Odd Solutions Wiki

wiki.oddsolutions.us

In Steps 6 and 7, you can just reuse the root shell that you already opened earlier. Run these two commands:

dd if=/dev/block/platform/sdhci-tegra.3/by-name/PES of=/sdcard/persist.img
dd if=/dev/block/platform/sdhci-tegra.3/by-name/PEK of=/sdcard/persistbk.img

Each of them will hang like they aren't doing anything for at least a minute. Just wait patiently.

After you've run them both, type "exit" and Enter, twice, to quit ADB. Continue the firmware update guide at step 8.

One exception: in step 12, the instructions call for running flash.bat as Administrator. This did not work for me.

Instead, I reused my existing command prompt that is already changed directory to the yellowstone_pie_pcsi subdirectory.

I ran flash.bat from there, which identified the chip uid and then started flashing partitions without throwing an error.

After this step, the PCSI image was installed and I proceeded to install LineageOS 16.0 provided by @npjohnson in the first post on this thread.
[Shield Tablet Original Android Development] neveroddoreven:
Like the others, in stock KitKat and also in the PSCI image, I could charge over USB. In my case, either with desktop PC USB, or about 995mW @ 5V from an older 12W Apple iPad charger. After moving to this thread's 20230111 unofficial build, I can no longer charge from USB in most cases. It now draws:

Various while normally booting and then cuts to 0 mA in mid-boot to OS, shortly before the three-chime boot sound

7 mA powered off, even if un/re-plug USB

988 mA in three-button boot to bootloader, but eventually reboots on its own to OS and 0 mA

740 mA if booted to recovery from bootloader, then if rebooted to OS again goes to 0 mA

1.68 A --WHILE POWERED OFF-- if starting from off state, press and hold power and keep holding it even after the screen turns on. In a few seconds, it will be forced to power off, but the charging circuits will still be enabled and will draw about 375 mA. Let go of the power button, then unplug and replug the USB in this powered-off state, and it'll start drawing 1 A, and ramp up higher to 1.7 A or thereabouts. During the replug event, you'll see the "dead battery" graphic on the screen briefly, even though your battery may not be actually dead.

Also, hey, just noticed if I disable Bluetooth with the OS booted, it starts drawing about an amp, then jumps up and down between 500 to 1300 mA. Toggling WiFi and Airplane mode (to disable the WWAN SIM) has no effect. The workaround continues working even through a reboot as long as Bluetooth stays disabled. I do not have a SIM or MicroSD card inserted.

So my workaround will be to keep Bluetooth disabled. I don't have a dock so it's the only way I can keep the tablet alive while being used.
[Shield Tablet Original Android Development] neveroddoreven:
Couple more interesting tells about the Bluetooth integration. I tried toggling all that is available, none of them improved the mutual exclusivity of having to choose between Bluetooth on or USB charging working.

In Developer settings:

The following settings:

Show Bluetooth devices without names

Disable absolute volume

Bluetooth AVRCP Version

Maximum connected Bluetooth audio devices

Changing all these above to various settings didn't get charging to work while Bluetooth is on, even if I toggled Bluetooth off and back on again.

Disable Bluetooth A2DP hardware offload

Is grayed out and set to enabled in the background, so it can't be changed

All other Bluetooth Developer settings (related to A2DP codecs, rate, bits)

Changing any of them from their System Default values is not persisted. Once you leave and re-enter Developer settings, your changes are lost and they're back to defaults.
[Shield Tablet Original Android Development] highwaystar_ru:
I can confirm charging working on my yellowstone only when bluetooth disabled.
[Shield Tablet Original Android Development] npjohnson:
Hey all, I am moving and therefore the unofficial update server/wiki will be down for a few days. Likely Wednesday, Friday at the worst.

Don’t panic when links in the OP don’t work, and your Updater app says something like “Can’t connect to server”. It is planned outage.

Thanks, see you on the other side!
[Shield Tablet Original Android Development] npjohnson:
Hey y'all - Unofficial build server/download portal is back up.

It may be hit and miss tomorrow as I rewire everything, but everything /should/ be functional for now.

Thanks!
[Shield Tablet Original Android Development] wiQbold:
Hello.

Is this also for the original Shield Tablet? is 'foster' not shield tv? or which are the lineage builds to use for?

Is there any kind of similar project for the nexus 9?
[Shield Tablet Original Android Development] npjohnson:
no - there are no builds for OG shield tablet, and foster is not shileld tablet, it Is shield TV.

And no, nothing like this for Nexus 9.
[Shield Tablet Original Android Development] wiQbold:
Yes, sorry.

It is like a rebranding from wx_un_do to yellowstone, right? I thought I had flash the firmware with the script and have to look for the builds and flash them afterward.

thx
[Shield Tablet Original Android Development] npjohnson:
Uh, no not at all.

Don't flash this, or the firmware on shield tablet.

This is for the Google Project Tango Tablet, not shield tablet.

This will brick the shield tablet.
[Shield Tablet Original Android Development] Math67:
hello friends. aid! I need to go from OS 14.1 lineage to OS 16 lineage.

How can I do it? I tried many ways but I can't migrate.

What steps should I follow to achieve it? Thank you for your answers
[Shield Tablet Original Android Development] npjohnson:
the wiki install guide details it all. Just follow it.

You need to follow the firmware update guide on the wiki first, tho.
[Huawei Mate 10  Questions & Answers] tkalfaoglu:
I download some firmware, ALP-LGRP2-OVS-9.0.0.221.zip, on my ALP-L09, extracted all from the zip, did a flashboot flash of every img that came out of the update.app. many of them finish successfully, some say forbidden, but when the machine restarts, I get 9.0.0.47 again! Any ideas why?

Thanks, -t
[Samsung Galaxy Note 20 Ultra Questions & Answers] WangLung:
Wow it has been a long time XDA, how is everyone?!

Anyways...last night as I was reading a text message my screen suddenly turned off and won't turn back on. Before this the screen showed no signs of damage, no artifacts and no tinting issues. The phone has never been wet and never been dropped. It is an unlocked Snapdragon model purchased directly from Samsung the day it was released.

The screen seems to still respond to certain things:

-Battery charge sound plays when plugging the phone in

-Holding power down seems to lightly vibrate the phone

-Putting S pen back into place vibrates the phone

-Calling my phone works (ringtone plays) but nothing appears on the screen

-Randomly tapping the screen like a mad man will make the texting noise

I've tried every button combo (felt like I was playing a **** flute) and I have tried plugging it into my PC but it does not recognize it.

Anyone else hear of issues like this?

Any recommendations before it goes back to Samsung?

Thank you for your time :eek:
[Samsung Galaxy Note 20 Ultra Questions & Answers] blackhawk:
Try a hard reboot with the control keys.
[Samsung Galaxy Note 20 Ultra Questions & Answers] WangLung:
Unfortunately nothing seems to work
[Samsung Galaxy Note 20 Ultra Questions & Answers] blackhawk:
Sounds DOA, sorry to hear that:(

Try a full charge. Pull the SD and Sim cards too.

Don't think it will help but nothing to lose.

Probably a failed soldier joint, connector or a solid state component that wasn't that solid.
[Samsung Galaxy Note 20 Ultra Questions & Answers] WangLung:
I tried that as well but nothing helped. Thanks for your suggestions, I understand these things happen but I really need my phone for work.

Any idea if they will repair it or replace it?
[Samsung Galaxy Note 20 Ultra Questions & Answers] MrMike2182:
Send it back to Samsung they'll either fully replace it or just replace the screen, one or the other but it won't make any difference the phone will still be fine after it's fixed. As long as you didn't do anything to cause it then it'll be taken care of free of charge.
[Samsung Galaxy Note 20 Ultra Questions & Answers] WangLung:
Thank you, I'll be sending it out today.
[Samsung Galaxy Note 20 Ultra Questions & Answers] blackhawk:
You're welcome, wish I could of helped. Sounds like you tried all that could be done.

If you're stateside see if you can get it done here.

Talk to Samsung US tech support. Philippines and SK tech support suck so keep trying until you get US if stateside.

No idea what they will do... lean on them if need be.

They'll first want to inspect it most likely.

Maybe they own up to it... that's the right thing to do.

If not, teach them some lessons. The screechy wheel gets the grease. Don't settle for anything less than that phone repaired or a new one.

Let us know what happens...
[Samsung Galaxy Note 20 Ultra Questions & Answers] WangLung:
Quick update

Sending the phone in was not too bad, just log in to Samsung and go to your list of products and select warranty (My 2 factor authentication was enabled and it was texting the code to my broken phone, Luckily I had a backup phone)

It will give you the option of scheduling a timeslot with a Samsung Experience store if you have one near you or mailing it in (I'm in Hawaii and there are no Samsung Experience stores here so I had to mail it)

They pay for postage just make sure to follow the instructions (They ask you to disable some sort of Google security thing before sending it in and to include the power cable and charging brick)

Print out the label they provide to you then pack up your items nicely and drop it off to UPS

I'll continue to update for those who may have the same issue or for those who need to send their phone in.