yashsingh1/xdaforums huggingface dataset:
[P3600 General] Andych:
Radio 1.50.08.11 works like a charm for me....full 3G and HSDPA so I am not sure what the problem is on your P3600i.

I have found that GPS Quick Position is useful (even if just for the Placebo effect). Time to first fix is not an issue for me....lots of people complain about it on the Trinity and compare it to the PNA GPS units...but really there has to be something of a compromise on a phone/GPS/PDA otherwise the thing would be a Laptop.
[P3600 General] desolateone:
I'm trialling 1.56.70.11 now, but again it has switched me to EGDE.

http://xdaforums.com/showthread.php?p=2396785#post2396785
[Shield Android TV Android Development] iLLNiSS:
Thanks for the info.
[Shield Android TV Android Development] Downunder35m:
Edit: Will use this post to list options to recover the Shield is all seems lost.

As a result of far too much rom cooking and mods I needed a 100% working way to recover the Shield in case things turn very ugly.

So lets sum up what I define as very ugly when playing with firmwares:

1. Firmware installed but the Shield just hangs on the logo.

2. Firmware installed and now the system is corrupt and even it is boots it takes forever to get around the nag screens.

3. Firmware downgrade attempted but now the Shield won't even boot anymore.

4. Anything that would qualify for a soft brick.

My worst case when I only got a flashing white screen after trying to restore a TWRP backup under 7.2.

There any many way that work for a variety of boot problems but it takes too long to list all cases I encountered with a list of fixes that work or a comment that only the below way works.

So just to be clear here: This is not for any recovery purpose other than fixing what can't be fixed through a factory reset or fresh flashing of the firmware!

1. Get the Shield into Fastboot mode: Connect wired controller and male to male USB cable.

2. Power the Shield up while holding A and B on the controller.

Keep holding until you see the fastboot menu on the screen.

3. Install the 7.1 recovery firmware for your Shield type after unpacking it.

With Fastboot connection working type: flash-all.bat and hit enter.

4. Keep an eye on the progess!

5. Once the Shield is finnished and reboots, hold the A and B buttons on the controller again to enter fastboot mode!

Do not let the Shield boot up other than into the fastboot mode!

6. Lock the bootloader! Fastboot oem lock

Confirm with the controller, then go down and select the recovery kernel.

7. Once the dead droid is on the screen press B on the controller to enter the real recovery.

If B does not work try A ;)

8. Select the factory reset option to wipe all!

9. Once the wipe is done you can boot into 7.1 as normal again.

10. With a bit of chance you might even get directly to the homescreen if the previous setup was completed.

If you need the full seup wizard again and are forced to update to 7.2 then at least the update will work fine this time around. ;)

In case you desire to go back to the 7.1:

If you just finnished the above only to end with the 7.2 then set it up and flash the 7.1 - you won't get the setup wizard again and can skip the update.

If you are on a working 7.2 that was update the OTA way but want to go back:

1. Install the 7.1 firmware.

2. Lock the bootloader.

3. Boot and then skip the update to 7.2.
[Shield Android TV Android Development] psycho_asylum:
Any idea what to do if the Shield sticks at the NVidia logo when you select Recovery from Fastboot? I reflashed boot and got the same result.
[Shield Android TV Android Development] Downunder35m:
It won't work from fastboot.

Fastboot operates on a different level and calling the recovery from there lets it end up in nowhere with no access to the system.

You need to boot into recovery through ADB as (for the new model) without a power button and usable hardware buttons we can't get into it otherwise.

Having said that, the fastboot way should still work with an unmodified bootloader.

When the dead droid is on the screen the recovery should be available after pressing the A button on the wired up controller.

But during my tests on 7.2 it did not always work, so you might have to try a few times and also try the B button.
[Shield Android TV Android Development] psycho_asylum:
I have not been able to get to the dead droid screen.
[Shield Android TV Android Development] Mogster2K:
Thanks for posting this, but please note that this firmware is only for the 2017 16GB model and cannot be used with a 2015 or Pro model.
[Shield Android TV Android Development] AthieN:
I just got a 7.2.1 update that forced me to update. Wouldn't give me an option to skip it... As soon as I turned on my Shield, it said something about the 7.2.1 update and then rebooted and installed.

I was holding off on updating too so I didn't lose root. Now I'm unrooted and am unable to get Magisk working again until I can get my hands on a 7.2.1 bootloader... Bleh.
[Shield Android TV Android Development] Downunder35m:
Weird, I am not getting the 7.2.1 at all here.

And since yesterday the OTA only tries the block based but not the full image.
[Shield Android TV Android Development] SyberHexen:
I was able to downgrade using the 7.2 image after setting up the device on 7.2.1 OTA just make sure you disable automatic updates
[Shield Android TV Android Development] banderos101:
Thanks downunder this kind of in-depth info is always appriciated man........i like to learn these kind of things, having bits here and bits there gives a better picture of the whole, while also giving us upto date current info.

Thanks for taking the time to write this :good:

---------- Post added at 07:35 AM ---------- Previous post was at 07:27 AM ----------

Edit

Hi downunder, could you confirm i have this correctly

With no access to fastboot thus no twrp or root, are you implying, assuming your able to inject root into stock firmware, that, i'd be able to flash this stock+root rom in STOCK recovery, which i do have access to?

Edit: im under the impression that stock firmware zips are checked by stock recoveries, so modifying a stock firmware zip tends to fail this check and thus wont install/flash.......which makes me think im misunderstanding here......or just hoping im not

If so, im interested

Edit

i just read your second post which near enought answers my curiousity, so that'll teach me to read beyond the first post before asking answered questions :)........even if the post excites me............ahhh, who am i kidding, ill probabably do it again........the equivelancy of a mental post boner........not controllable

Sorry for the disgusting analogy :)
[Shield Android TV Android Development] ErAzOr2k:
Did I understand it correctly? You successfully downgraded from 7.2.1 to 7.2?
[Shield Android TV Android Development] SyberHexen:
Yes,

Just ran flash all from the bootloader. For the newly released 7.2 developer_rooted factory image.
[Shield Android TV Android Development] Downunder35m:
As long as we don't jump to Android 9 we should always be able to downgrade through a full factory firmware.

Once Android 9 comes this might not work anymore due to the massive changes involved for the boot and system checks.

[MENTION=3385762]banderos101[/MENTION]: Unless you really did something bad you should always be able to enter the fastboot mode to flash a full firmware.

If I have some time after xmas I will have another look on the options of signing the zip properly or simply to fake it.

Biggest problem will be to generate the corret SHA checksums ince all is installed so I can use the same checksums in the check files.

The bootloader needs them to identify the system and vendor as genuine.

The system needs them to confirm all is actually unmodified as otherwise all fails to boot at some stage.

Modding a proper userdebug firmware is not really that hard, but converting a release version that also is a true and secure user release...

Lets just say that it won't be an easy task.

As it looks like the kernel is a keeper I might have to figure something out unless TopJohnWu won't enjoy a break after his exams and works on a way to get Magisk working with out kernel.

At least I figured out why the recovery trick isn't working for me.

The system partition is not mounted for the sideload mode.

To apply an update the stuff is written directly onto the partition, so no file level access left to play with and break things :(

In comparison you could say the shield is now like a modern car with keyless operation only.

You know you can start it with ease, if you only could the remote that you left in the drivers seat when you locked the door ;)
[Shield Android TV Android Development] bp328i:
Just wondering what is achieved by going back to 7.2?
[Shield Android TV Android Development] tman777:
Shield Tv 16 2017 - OTA update 7.2.1 Ready for updating

Im on 7.1. I have been waiting for 7.2 developer image, which is now out and just noticed 7.2.1 is available OTA. I'm really confused what to do. I want to keep root without bricking my Shield. Should I Stay with what I have as it is running well.

I am not even sure if it is safe trying to update to dev 7.2 image (or if I would want to) by hooking to computer and using ADB Fastboot tools.

Is there any good reason to update to 7.2 or 7.21? and if so how would I go about doing it? Which program is good for flashing developer images or OTA updates. I used to use flash-fire, which seems to be obsolete now and have heard TWRP is incompatible rooting with SU with OREO updates????

Should I play it safe and stay with what I have rather than experiment and end up with a brick? (wouldn't be the first time)

Anyone know if 7.21 is some-kind of bug fix?

Alot of questions but hope someone has some answers.

Thanks for any info.
[Shield Android TV Android Development] banderos101:
:)

"You know you can start it with ease, if you only could the remote that you left in the drivers seat when you locked the door "

My fastboot issue

Yeah, i think i busted the microusb somehow with a faulty usb hub, whenever i plug the usb to my raspberrypi/windows box(for adb/fastboot) now, it turns off all usb ports on the pi aswell as the windows box, even when the shield is unplugged, some sort of earth problem maybe

......all i have is adb over network, adb reboot bootloader simply reboots back to system, adb reboot recovery works though.

ive read that fastboot over tcp(ethernet) had been introduced a couple of android versions ago, but i dont think its been implemented in our shields

infact heres a link

https://www.androidpolice.com/2016/...-capabilities-wireless-flashing-isnt-far-off/

Looks like it needs to be specifically added onto a build

As far as you making a stock root build, if you can, that would awesome, more then awesome, but if it becomes more work then you thought dont worry about it, its not like their making it easy

Also, sounds like 4.9/future android is gonna be a nightmare for root......... having the ability to root so that the option is there to see whats going on in the background of these devices, these devices posessing cameras/microphones/old+latest sensors/personal files/personal info, which reside on our personal beings or in our homes........is just one reason why i dont want to see root go away
[Shield Android TV Android Development] snakec:
So what is the purpose of the developer image of 7.2?

Rather, I know the stated purpose of the developer image, but if it is locked in the way described it sounds like the benefit is negated for typical developers.

(e.g. sometimes I debug an application without permissions in order to benchmark or debug a problem).

For casual users of the shield, using ad blockers and whatnot, is there any benefit to derive from installing the developer rom over stock? Does "adb root" still work?

What is left as the difference. It doesn't sound like they produced a userdebug build of the OS.

Thanks
[Shield Android TV Android Development] unibomber:
The 2 new updates are horrible. I have gone back to 7.1. They have crippled my shield. I'll wait for a new update.
[Shield Android TV Android Development] Mogster2K:
I was able to get root thru Magisk on my 2015 (foster) unit, so it should also work on the Pro. I used the Magisk Manager app on my Shield to patch the boot image. (Strangely, patching it on my phone did not work.) I have not heard of any successes with a 2017 darcy unit.

---------- Post added at 05:00 PM ---------- Previous post was at 04:57 PM ----------

I would wait it out. 7.2 fixes some things but breaks others. And yes, 7.2.1 was released to fix some bugs in 7.2, notably wireless-AC not working on channels above 50.
[Shield Android TV Android Development] ACiDxCHRiST:
topjohnwu specifies that you must patch the boot.img on the same device it is for. It uses processes to patch the image that are different depending on model/version. That is not saying that it is NOT possible to patch a boot.img on a different device, but that it WILL fail to produce a working patched_boot.img if the files/processes that Magisk Manager use differ between the 2 devices.
[Shield Android TV Android Development] ACiDxCHRiST:
[MENTION=2772353]Downunder35m[/MENTION] Hey, I figured out why Magisk Manager was creating bootloops when using it to patch the boot.img from v7.2

From your posts, I am betting you're probably already aware of this but I figured I would let you know just in-case. Below is how I got a working v7.2.1 on a 2017 Shield TV rooted with Magisk v18.0

Extract boot.img from developer image or full OTA (Partial OTA probably has a complete boot.img in it as well, but I don't ever mess with those)

In Magisk Manager check the box for the "Preserve AVB 2.0/dm-verity" option

Click Install, and select the boot.img

Copy patched_boot.img to PC

'adb reboot bootloader'

'fastboot flash boot patched_boot.img'

'fastboot reboot'

I verified that this works perfectly
[Shield Android TV Android Development] bp328i:
Thanks for posting this!

I can confirm this works on both my Pro and 2017 Shield TV. Both rooted with Magisk v18, both running v7.2.1.
[Shield Android TV Android Development] iLLNiSS:
Where did you get the 7.2.1 boot.img from?
[Shield Android TV Android Development] bp328i:
At the very bottom of Developer options I turned on Provide full system upgrades. I flashed 7.2 then download the update (but did not flash it then). It can be found in data/data/com.nivida.ota (it's going to have a long number for the name but it's over 1gb in size) and pulled it out of that. It's just a zip file.

Edit: if you want I can upload the patched boot.img. I have the one for the Pro and the 2017 16gb.
[Shield Android TV Android Development] ACiDxCHRiST:
I have posted a full [GUIDE] in General, that has that info and more

https://xdaforums.com/shield-tv/general/guide-root-nvidia-shield-experience-t3882254
[Shield Android TV Android Development] iLLNiSS:
Thanks for the info. Sadly I bricked my unit tonight. Accidentally flashed the pro boot to my 16gb unit :(
[Shield Android TV Android Development] Mogster2K:
The boot image, or the bootloader image? If it was the boot image then your Shield is not bricked - just flash the correct one and it should work again.
[Shield Android TV Android Development] Downunder35m:
Update in the first post - worthy to read ;)
[Shield Android TV Android Development] Downunder35m:
Tried that but not all root stuff worked.

For example my adblocker fails to get root despite being granted.

But will test again on a really clean and fresh install.

@ iLLNISS: I agree with Mogster2k.

Even if the image sizes are totally wrong the normal flash process can't break the partitions.

And unless there was a true bootloader included all is good :)
[Shield Android TV Android Development] nanerasingh:
On 7.2.1 2017 16GB MODEL.

How to downgrade to 7.1 or 7.2? i saw 1st post but its quite complicated writeup, can you give me steps to downgrade from 7.2.1 to 7.1?

i worried if i follow wrong step and may cause booloader bricked .Thanks
[Shield Android TV Android Development] iLLNiSS:
The initial steps before the first reboot were done:

adb reboot bootloader
fastboot flash staging blob
fastboot flash boot boot.img
fastboot reboot

At this point the device showed up as an APX device and I could no longer use adb or fastboot. It does not have any lights and I cannot get into recovery with a keyboard. As far as I can find when it's showing as APX it's bricked until nvflash is updated and apx drivers are released for the Shield.
[Shield Android TV Android Development] Downunder35m:
The staging blob is your new bootloader.

Flashing it manually could be what caused your troubles.

Some Shields require a full blob, some only the partial, while a few do need one as they run a special bootloader.

The updater script should make sure no bootloader is changed the wrong way or update if not required.

I will check for options to get APX drivers to work that allow to flash the stock booloader again to get access.

My initital searches however do not look good.

I am sorry for the problem!

But there is a final light available now!

I will update the first post a bit and hopefully a friend of mine will join in to share his findings soon.
[Shield Android TV Android Development] nanerasingh:
Solved!

Thanks [MENTION=2772353]Downunder35m[/MENTION] for guide.

I downgraded to 7.1

-Flashed developer 7.1 firmware.Flash all.bat

-After install i hold AB button to enter fastboot and locked the bootloader.

-Rebooted and on 7.1 firmware setwizard,Luckily after few steps i goes directly to Home screen and adb debugging on.

-Unlocked bootloader and flashed Magiskv18 via twrp.

Now i downloaded FULL OTA Update 7.2.2 and update after backup ota file from Root explorer i patched it with magisk app with Preserve AVB 2.0/dm-verity checked.And saved pathced_boot.img of 7.2.2.

-Then Updated to 7.2.2 ota.

-After boot to home screen enabled adb debugging.and reboot to bootloader.

-flashed pathced_boot.img of 7.2.2.

-rebooted and magisk root available on my 7.2.2 version(as it doesnt shows any version in system info just- Unkown)

-To check the root issue i modify the build.prop file via es explorer and changed ro.setupwizard.mode=DISABLED.

But seems file was not saved and revert back to ro.setupwizard.mode=OPTIONAL.

So Official magisk patching not working fully for pesistant.
[Shield Android TV Android Development] iLLNiSS:
No sorry needed, this was my **** up :)
[Shield Android TV Android Development] Downunder35m:
There he is with the solution, I knew I can count on Whiteak :)

Will include the instructions with a link in the first posting.

I tried Whiteak's solution myself this morning and can confirm it works just fine.

Although there might be problem for some who already tinkered too much like I did.

As the normal flashing through fastboot not always removes vital system stuff the Shield can come with some hickups.

A good way to prevent this is to do a full wipe through the stock recovery - a factory reset.

I tried one right after the flashing and before the first boot up and then the shield went on with no problems at all.
[Shield Android TV Android Development] Michajin:
This is what worked for me, using the files and commands and files from Post 36 (Great job Whiteak) I modified a flash-all.bat file and placed the files and ran it. I upgraded from 7.1 to 7.2.1 with full magisk root. I downgraded back to 7.1 with the flash-all from that image to test. After a android boot screen bootloop, i had to power down and restart (it then booted into android), i was back on 7.1. The i used the flash-all-root.bat file i modified and i am back on 7.2.1. I did not use the fastboot -w (this wipes data right?). I did notice on first boot the system seemed to lag badly until another restart, then it was all good. I did have to install the Kantjer Magisk Manager above (its included in the zip). Just run the flash-all-root.bat file. It will reboot a couple times then go back into bootloader then flash the rooted boot image and dtb file. The flash-all-root. bat is the only thing i did to get it to work. I am using the shield 2017. I would also recommend a factory wipe if you are having issues, maybe try a cache wipe first and see if that resolves issues. I'm a novice at this so I'm sorry if this information is useless to any of you. I flashed from windows, i'm sure i could modify a .sh to run in linux if anyone needs it. Use the file at your own risk.

https://drive.google.com/open?id=1OxGpiqrSyRuodhpYnVqxhpQUvUZwmIac
[Shield Android TV Android Development] unibomber:
Does 7.2.2 suffer from bad lagging like 7.2 and 7.2.1?
[Shield Android TV Android Development] Mogster2K:
Has anyone managed to downgrade a 2015/foster unit to 7.1? I can't do it on mine. The bootloader version displayed on the TV does not change, and boot images that worked before 7.2 just hang on the Nvidia logo.
[Shield Android TV Android Development] Downunder35m:
That is no good news Mogster :(

I was hoping the older models would not get the new bootloader.

I am not 100% sure whether it is the 7.2 already or the later bootloader, but they won't allow a downgrade anymore.

Almost certain I still could under 7.2.

As we can't sign them we can't use a modifed old one one to spoof a new version number.

And I doubt the system would boot if we could.

Too much on the partitions we can no access has changed.

I am working ona firmware that again gives us full and open access but first I need a working TWRP again :(

In theory all should work just fine but I can not flash it to test it as simply flashing system-, boot-, and vendor partitions won't do it.

Ayn attempt with a 7.2.x bootloader to use a custom recovery marks the system as corrupt.

Right not I am not sure if that is still true after a full wipe and format through TWRP.

So far I tend to say no and the install of a fresh firmware fixes it.

Running around in a very annoying cricle with this problem....

If anyone one is able to go back to some firmware or TWRP version that again gives us full write access and working flashing and restores then speak up please!

Getting TWRP "working" with the Zulu99 DTB is one thing, writing a backup back that actually boots and successfully flashing a zip is another story.

Hopefully someone has more time than I have to search through the to be released 7.2 sources to provide something that fully works.

In the meantime I reject reality and substitute my own!

There is a way, I just need to find it LOL
[Shield Android TV Android Development] Adromir:
I do have a rooted shield with 7.1 and TWRP working. Removed the Shield OTA, because I was aware some stuff like this might happen.

If we are not able to bring back Magisk, this Root approach might help us keeping the Shield rooted: https://xdaforums.com/android/software/root-backdoor-android-kernel-development-t3870559

Or a custom kernel with a modified fstab bringing back the system Partition maybe?
[Shield Android TV Android Development] Downunder35m:
@ Adromir: I will check the link and options that it might offer but first I have a huge requst:

I suspect that my ongoing experiments have caused some serious issues on my shield.

If yours is a 2017 model then I would appreciate a full TWRP backup of the entire system.

From a freshly installed 7.1 I then might be able to get all bootloader things back to normal, at least I hope so :(

I might have found a possible backdoor.

Under certain conditions I noticed that I have a working ADB root connection around the time the NVidia logo shows up.

It is only for a few seconds if it happens but with a bit of luck this time could be used to start a shell script to modify the system partition.

Things like renaming the OTA folder, pushing a modified build.prop...
[Shield Android TV Android Development] whiteak:
Hey Downunder, I could go back to 7.1 for you and get a full backup if you want me to. Just let me know.
[Shield Android TV Android Development] Downunder35m:
Let me try first to manually go from 7.2.1 to 7.2 and then 7.1.

Can't be impossible to get the thing back to what is was LOL

Will let you know in a few hours, thanks!