How to skip(bypass) Google sign-in NSTV Pro 2019 with any firmware versions!

[qxotic]

I have no more idea and it should works!
add more options to build props:
ro.setupwizard.network_required=false
ro.setupwizard.wifi_required=false
ro.setupwizard.enable_bypass=1
ro.setupwizard.mode=DISABLED

My 2017 Shield tv pro's HDD went bad, I went through the SSD process several times and keep getting hung up on google sign in saying my password is wrong when it's not. I even get email new sign in notices. I have been unable to get past this point. I tried this method.. adding the ro.setupwizard.mode=DISABLED to the end... it was also further up in the file as =OPTIONAL... also tried changing it there to DISABLED..and with and without it at the end. Every time I still get the google sign in wrong password failure. I've tried using adb to install upgrades, both 6 and 8, on top of the SSD forum one but after installing them I keep getting stuck on the 4 animated dots.. even clearing cache I can't get any further. I've tried using the 6 and 8 zip files from inside TWRP but get errors and it won't try. The TWRP from the SSD forum is there and I can get into fastboot mode fine. Any suggestions on what I should try next? It's been over a week and so far no one on the SSD forum has answered with any suggestions... another user posted with the same problem. I assume.. but want to be sure I tried the DISABLE at the right time. I did this after I used dd to copy the start and stop files to the new ssd... then on first start up went into fastboot and edited the file to DISABLED. Was that the right time to do it? I've run out of ideas what to try next.. any suggestions are welcome. I didn't see any setup lines where the email and password could be included at build time... I'm ok with signing in.. if it will actually work.. but happier without google.

 

[mrhamed]

@qxotic
Hi, I don't have access to 2017 device, but it should work with provide instruction...
I'm currently using LineageOS (It's nightly release and has many bugs) and it seems you are not newbie, so you may test LineageOS (using the customized ROM is a better way to protect your privacy)

LineageOS:

LineageOS Downloads

download.lineageos.org

microG: (more privacy with more functionality)

foster

 

[qxotic]

@qxotic
Hi, I don't have access to 2017 device, but it should work with provide instruction...
I'm currently using LineageOS (It's nightly release and has many bugs) and it seems you are not newbie, so you may test LineageOS (using the customized ROM is a better way to protect your privacy)

LineageOS:

LineageOS Downloads

download.lineageos.org

microG: (more privacy with more functionality)

foster

has anyone posted an ISO anywhere for either the shield pro android or the Lineage OS? I'm not sure of the TWRP setup.. it may be part of the problem. I will try the Lineage.. but suspect I'll run into trouble there too.

 

[mrhamed]

has anyone posted an ISO anywhere for either the shield pro android or the Lineage OS? I'm not sure of the TWRP setup.. it may be part of the problem. I will try the Lineage.. but suspect I'll run into trouble there too.

What is your mean about ISO?

 

[qxotic]

What is your mean about ISO?

An ISO is an exact copy of an entire disk which can then be written to another disk. An img file would work better in this case. If someone had a working system without the google sign in (so no one would gain access to their login) they could use the dd command and pipe it to gzip for a small image file that could then be shared and that file could be written to a disk of the same size in effect making a clone of it.

 

[Lennong05]

I spent a 'couple' of hours dicking around with LinageOS and various stuff to get around the Woogle stuffs. LineageOS lacked TrueHD and lagged horribly in audio so I went back to the dev version of stock image. I stumbled upon this thread and the instructions didnt work for me as well. However, it got me a few ideas on maybe to bypass the Woogle account part and tried this path below. This is my notes that I allwas do when I try out things so live with the bloat..

I am sure one of you clever boys can pinpoint why and where it works and why..

Hardware:
Keyboard and mouse attached to Shield (USB Hub)
USB-A male to USB-A male cable between Shield and PC (Linux Debian)

On Shield:
Boot up
Hold A + B key on keyboard at boot to get into fastboot menu
'unlock bootloader'

reboot and hold A + B key at boot on keyboard
leave the Shield at that state


On PC (Linux Debian 11):
apt install android-tools-adb fastboot

Unpack the nv-recovery-image-shield-2019-pro-atv-8.2.3-dev_rooted.zip
cd mdarcy-factory_4079199_2740.7538
copy latest twrp.img, linageos_recovery.img and magisk.apk in same directory

Flash:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img


On Shield:
reboot and hold A + B key on keyboard to get into fastboot menu DO NOT LET THE INITIAL SYSTEM INSTALL START!!
choose boot 'recovery image'
In TWRP:
'Mount', 'Mount system' and UNcheck 'read only'
leave the Shield at that state


On PC (Linux Debian 11):
adb shell
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop (I prefer echo'it in to avoid nasty white spaces)
exit (from shell)
adb pull /system/build.prop (just to read and verify "ro.setupwizard.mode=DISABLED" has been added)


On Shield:
reboot
Now, the "ro.setupwizard.mode=DISABLED" switch will not work (as we know) so you will have to go through setup as ususal with account bla bla.. (it will be erased later)
Go offline as soon as you past the account reg part. No LAN or Wifi!!!
enable usb debugging (if not enabled default)
After login immediately go and disable the auto update:
adb shell
pm uninstall -k --user 0 com.nvidia.ota

Root'ing:
reboot and hold A + B key on keyboard to get into fastboot menu
fastboot flash recovery linageos_recovery.img
reboot and hold A + B key on keyboard to get into fastboot menu
choose boot 'recovery image'
In Lineage Recovery:
'Apply Update', then 'Apply from ADB'
leave the Shield at that state


On PC (Linux Debian 11):
adb sideload magisk.apk


On Shield:
reboot


On PC (Linux Debian 11):
Install full Magisk / Magisk manager and then verify it is rooted:
adb install magisk.apk
Install Aurora to get access to apps:
adb install com.aurora.store.apk


On Shield:
reboot and hold A + B key on keyboard to get into fastboot menu
lock bootloader
reboot (it will not boot)
reboot and hold A + B key on keyboard to get into fastboot menu
unlock bootloader
reboot

It should now bypass the part where the nagging is and go directly to the UI. No activation of account needed. Root seems to survive as well. Just install Magisk manager again.

After fresh start disable the auto update:
On PC (Linux Debian 11):
adb shell
pm uninstall -k --user 0 com.nvidia.ota

My guess is that the lock/unlock bootloader triggers the 'reset' and deletion of data, apps and accounts but do not affect the root or the modified /system/build.prop file.
After it sets up again you should get into the UI automatically without signing in. From what I can tell it jumps over the initial setup and account login because either because it's rooted or in this 'path' actually reads "ro.setupwizard.mode=DISABLED" switch OR a result of them both. Either way, it works.

A bonus would be that a quick visit in fastboot menu and do the 'lock bootloader', reboot to fastboot again and do the 'unlock bootloader' would result in a reset device again with skipped account nagging and directly into UI. Running a developer image with unlocked bootloader I guess is not recommendable but I dont really care. All to your own.

Have a go with the non-dev image and write back here? I'm guessing it works the same.

 

[Lennong05]

Ok, as I suspected the "ro.setupwizard.mode=DISABLED" switch GETS picked up when you do a reset by using 'unlock bootloader'. Any image will work, either dev or non-dev.

So:
On Shield:
Boot up and hold A + B key on keyboard at boot to get into fastboot menu
'unlock bootloader'
reboot and hold A + B key on keyboard at boot to get into fastboot menu
leave the Shield at that state


On PC (Linux Debian 11):
Flash:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img


On Shield:
reboot and hold A + B key on keyboard at boot to get into fastboot menu
choose boot 'recovery image'
In TWRP:
'Mount', 'Mount system' and UNcheck 'read only'
leave the Shield at that state


On PC (Linux Debian 11):
adb shell
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
exit (from shell)

On Shield:
reboot and hold A + B key on keyboard at boot to get into fastboot menu
'lock bootloader'
reboot and hold A + B key on keyboard at boot to get into fastboot menu
'unlock bootloader'

..let it run thru the setup and directly into UI.

benefit from this method would be that from now on when needed a reset, a quick visit in fastboot menu and do the 'lock bootloader', reboot to fastboot again and do the 'unlock bootloader' would result in a reset device again with skipped account nagging and directly into UI because the ro.setupwizard.mode=DISABLED would again be picked up..

 

[dib_]

I haven't been able to get it working yet, unless I install the patched boot images from https://forum.xda-developers.com/t/...rmware-and-keep-stock-apps-2017-2019.4524873/

Is this supposed to work with stock? Anyone able to confirm this works?

 

[dib_]

Is there anything for skipping the entire setup? I'm stuck at it wanting to logon to a wifi network, it refuses to connect to mine because I have traffic blocked at a firewall so it refuses to accept it.