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

Search This thread
By:
Advanced…
M

mrhamed

Senior Member
Apr 19, 2014
455
43
*** You should unlock bootloader ***

-In fastboot mode:
Code: 
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! :cool: F.ck the spy.

For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana
 
Last edited:
C

cHECKjAM

Senior Member
Aug 28, 2015
126
14
Wow you know how long I have been waiting for this?
I did not test it yet but I will soon, hopefully today. Will work with both Dev image and regular image?

Thanks @mrhamed

By the way, Do you know if this method also works on a 2017 Pro 16gb version?
 
Last edited:
M

mrhamed

Senior Member
Apr 19, 2014
455
43
This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
nstv_screen.jpg
 
C

cHECKjAM

Senior Member
Aug 28, 2015
126
14
mrhamed said:
This method should not device specific because it related to android build ecosystem, so it could be work on any device.
Have a good time...
nstv_screen.jpg
Click to expand...
Click to collapse

awesome.
by the way what is that screenshot?

If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?
 
M

mrhamed

Senior Member
Apr 19, 2014
455
43
cHECKjAM said:
awesome.
by the way what is that screenshot?

If the google skip sign in works on all devices and on both developer image and default image, what is it that is stopping us to root and flash regular image for NS Pro 2019 and get AI Enchancer to work?
Click to expand...
Click to collapse

It's my device screen.

I don't like to lock-bootloader, so AI not works at this time, I'm testing "MagiskHide Props Config" to try hide the booloader-state and I hope enable AI with unlocked bootloader:
https://forum.xda-developers.com/showpost.php?p=83972471&postcount=4626
 
C

cHECKjAM

Senior Member
Aug 28, 2015
126
14
@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2

What Im hoping is that bluetooth will work. Because when I flash the dev image earlier and used the ↑ ↑ ← ← method and choose skip setup, bluetooth has not been working. Can not find any bluetooth devices when i search for them. The same problem on 2 different devices.

So now Im trying this method right now to see if it works better.
If it does not work I need to try the the none-developer image instead.

However this method seems to bootloop.. Im not sure whats happening.. I see the nvidia logo and then reboots again and same..

---------- Post added at 08:31 PM ---------- Previous post was at 08:26 PM ----------

The steps I took:

I boot to TWRP first through bootloader.
Format and wipe all partitions basically making it totally fresh.
Then I boot to bootloader and run the flash-all without the reboot continue.
Then I boot back to TWRP and mount system.
Then pull the file and append the line, then push it back.

Then reboot to system.

Now bootloop...

just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..
 
M

mrhamed

Senior Member
Apr 19, 2014
455
43
cHECKjAM said:
@mrhamed Im testing this method now for my NS 2017 Pro 16gb - on developer image 8.2
just Nvidia logo for a while then back to the ""your device is unsafe" window.. then back to nvidia logo..
Click to expand...
Click to collapse

-Remove "ro.setupwizard.mode=DISABLED" from (end of file: system/build.prop).
-Try to bootup completely and setup ethernet with internet connection. then power off device.
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot

I hope it works.
 
M

mrhamed

Senior Member
Apr 19, 2014
455
43
If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code: 
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.

- Flash vbmeta_skip.img:
Code: 
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.

If two steps does not works too! you have to: Root and install Magisk
 
C

cHECKjAM

Senior Member
Aug 28, 2015
126
14
mrhamed said:
If above steps does not works, please try:
- Flash mdarcy.dtb.img:
Code: 
fastboot flash dtb mdarcy.dtb.img
extract from nv-recovery-image-shield-atv-2019-pro-8.2.0.zip package.

- Flash vbmeta_skip.img:
Code: 
fastboot flash vbmeta vbmeta_skip.img
extract from nv-recovery-image-shield-atv-2019-pro-8.1.0-dev_rooted.zip package.

If two steps does not works too! you have to: Root and install Magisk
Click to expand...
Click to collapse


I dont get any method working..

The other thread with the "how to root" is lacking so much details and steps I have no idea how it is supposed to be done..

So I tried flashing the totally default dev image 8.2 . Everything boots and goes in to the setup mode

From there if I unplug ethernet I cant go anywhere.. I then reboot to bootloader and from there boot in to twrp.
Mount the system and modify the prop file as you said. then reboot to system again. Still cant bypass setup.

I also tried the exact same with flashing the vb skip image instead of default vbmeta
same result..
And it is painfully long process and every new try is a pain.

Can you please buddy please:
Write a step by step n exactly how to from scratch:
Flash 8.2 image + root + bypass google setup entirely..
 
M

mrhamed

Senior Member
Apr 19, 2014
455
43
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
 
C

cHECKjAM

Senior Member
Aug 28, 2015
126
14
mrhamed said:
Let me share my working build.prop file with you.
Make sure the permission of this file is proper too.
Click to expand...
Click to collapse

Hey buddy..
I have not had time until now to try this again.. My shield has been semi-bricked since last try and have not been able to use it until now. So maybe can look in to getting this working during the vacation.

Have you gotten any better idea on how exactly to make this work? I followed all your steps last time and failed twice..
 
C

cHECKjAM

Senior Member
Aug 28, 2015
126
14
Is there anyone out there except for @mrhamed that has got this method working?

If so please share any real tutorial/steps/guide or whatever that can help.. thanks
 
J

jolsowka

Member
Jul 15, 2021
11
1
mrhamed said:
*** You should unlock bootloader ***

-In fastboot mode:
Code: 
twrp-3.4.0-0-20200926-UNOFFICIAL-foster.img
(Download here!)
-Make sure the system mounted (use twrp mount option)
-Pull build.prop file: adb pull /system/build.prop
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
-Reboot NSTV: fastboot reboot
-Wait for bootup (It may take a while)
-Finish! :cool: F.ck the spy.

For safe Your privacy You have to stop Google from spying You.
The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power, Zuboff, Shoshana
Click to expand...
Click to collapse
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
 
L

LazorBlind

Senior Member
Feb 25, 2020
58
16
jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
I think 9.0.0 broke alot of things we have been taking for granted. if not using a Google account is that important to you, best to go ahead and revert back for now.
 
M

mrhamed

Senior Member
Apr 19, 2014
455
43
jolsowka said:
I tried this method on the 9.0.0 2019 shield pro but I still received the google login requirement. Has anyone been able to get around this? Would like to try this out before reverting back to 8.2.3.
Click to expand...
Click to collapse
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
 
J

jolsowka

Member
Jul 15, 2021
11
1
mrhamed said:
Are you sure about these tow steps:
-Open build.prop file and append new line: ro.setupwizard.mode=DISABLED
-Push build.prop file: adb push build.prop /system
Click to expand...
Click to collapse
Just pulled the build.prop again and the setupwizard was still disabled. Did a reboot and still requires Google sign in. Guess its back to 8.2.3.
 
M

mrhamed

Senior Member
Apr 19, 2014
455
43
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
 
You must log in or register to reply here.

Similar threads

M
How to Root and install Magisk on NSTV 2019 Pro v8.2.0
Replies
94
Views
20K
M
mrhamed
jenneh
Root Nvidia Shield TV Pro 2019 Version
Replies
103
Views
28K
jenneh
jenneh
H
Bypass Google sign-in NSTV Pro 2019 Simple trick
Replies
5
Views
2K
S
savelbys
jenneh
2015, 2017, & 2019 Nvidia Shield TV Firmware Repo & Source Code Repo
Replies
41
Views
7K
Manzing
Manzing
jenneh
BOOTMOD - Root your Shield In 1 minute (2015, 2017, & 2019)
Replies
104
Views
8K
Sage
Sage

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 3
    L
    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.
    View
    1
    Q
    qxotic
    mrhamed said:
    What is your mean about ISO?
    Click to expand...
    Click to collapse
    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.
    View
    1
    L
    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..
    View

New posts