Related
Ok first of all , i don't know if frp bypass stuff is allowed on xda anymore , because too much changed here and it's not same as it was before , but anyway ..
Tutorial is based on this video https://www.youtube.com/watch?v=gjU9C6xb_ps
but it only worked partially for me , so if you have trouble with unlocking that way , here is little bit more steps which will help you
Here is link to downloads : https://drive.google.com/drive/u/1/folders/12vVeqaEsuPEj2dPgIugA_Z4I-3AkPPhE
You'll need to install drivers first , then use that program
1) Reboot to bootloader mode
Turn OFF device, push vol down and then power button . after 2-3 sec release power button and you'll be in bootloader mode
2) start that Motorola_FRP
3) wait until 3rd or 4th restart when it asks for ADB Access.
4) First close that program and ONLY AFTER THAT Click OK on screen of phone
5) Go to your ADB folder , Open CMD( Just click on folder name and write cmd there ,then click enter)
Then use this command:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
"If Above Command not Working Then Try This Command:
adb shell am start -n com.google.android.gsf.login/
If Above Command not Working Then Try This Command:
adb shell am start -n com.google.android.gsf.login.LoginActivity"
Then just reboot your device and you're good to go
I'm quite sure this will work with many other variants too, but i've tested this on my XT1776 , so ...
fastboot erase frp
thats it
Francesco Franz said:
fastboot erase frp
thats it
Click to expand...
Click to collapse
Really?
fastboot erase frp is even command?
I don't know if that's how it works on mediatek chipset , but i'm quite sure that won't work on qualcomm? maybe i'm wrong ...
jkjambo said:
Really?
fastboot erase frp is even command?
I don't know if that's how it works on mediatek chipset , but i'm quite sure that won't work on qualcomm? maybe i'm wrong ...
Click to expand...
Click to collapse
it will work if qualcomm variant has frp partition.
mtk variant already have one.
Francesco Franz said:
it will work if qualcomm variant has frp partition.
mtk variant already have one.
Click to expand...
Click to collapse
I didn't know that .
Don't really have time to test it right now , but i'm interested if qualcomm variant also can be reseted that way , i'm 90% sure it won't work , but still there is chance
jkjambo said:
Really?
fastboot erase frp is even command?
Click to expand...
Click to collapse
Yes. Its a commands. It depend on the type of partitions in your device. There are several threads floating around there in moto e4 dev. section related to this topic.
---------- Post added at 01:36 PM ---------- Previous post was at 01:35 PM ----------
jkjambo said:
I didn't know that .
Don't really have time to test it right now , but i'm interested if qualcomm variant also can be reseted that way , i'm 90% sure it won't work , but still there is chance
Click to expand...
Click to collapse
i owns a mediatek variant of E4 and it worked for me.
Francesco Franz said:
Yes. Its a commands. It depend on the type of partitions in your device. There are several threads floating around there in moto e4 dev. section related to this topic.
---------- Post added at 01:36 PM ---------- Previous post was at 01:35 PM ----------
i owns a mediatek variant of E4 and it worked for me.
Click to expand...
Click to collapse
We are running Qualcomm Owens and "erase" is not a terminal or fastboot command, I tried yesterday after a boo-boo.. ? When I used "fastboot rm -rf frp" cmd, it didn't protest.
bcrichster said:
We are running Qualcomm Owens and "erase" is not a terminal or fastboot command, I tried yesterday after a boo-boo.. When I used "fastboot rm -rf frp" cmd, it didn't protest.
Click to expand...
Click to collapse
fastboot erase partition_name
fastboot flash partition_name file_name.img
Hope you familiar with this.
---------- Post added at 06:58 PM ---------- Previous post was at 06:55 PM ----------
bcrichster said:
We are running Qualcomm Owens and "erase" is not a terminal or fastboot command, I tried yesterday after a boo-boo.. When I used "fastboot rm -rf frp" cmd, it didn't protest.
Click to expand...
Click to collapse
There's nothing like this *rm -rf* in fastboot.
Its a basic shell command to remove files.
If it didn't work than do this.
fastboot erase system
and then try to boot into system. you will get it.
Francesco Franz said:
fastboot erase partition_name
fastboot flash partition_name file_name.img
Hope you familiar with this.
Click to expand...
Click to collapse
You are absolutely correct, not that ya point that out [emoji23] I must've typo'd when I tried. Looks like I did it the hard work way outta frustration. [emoji28]
Running an Xp3r!meπt with my XT1776
Moto E4 Plus XT1776
My device hard brick Qualcomm please need blank flash file for Moto e4 plus xt1776 ????
Frp bypass March 1 2018-no PC needed just WiFi
Just did a bypass on the March 1 2018 security patch.sorry if there's no new information as I do these as a hobby and purposely don't look for answers on the web.
I do a lot of redundant things and useless steps in case I go down that rout. Like setting up Microsoft accounts in Gmail or turning the font size down, is for personal preferance.
If you would like a compleat list of steps in chronological order your sol. I do these once and done. I can only roughly give a Quinton Terintino style retelling of what happened.
(Skip all setup related screens that have a "skip" or "later" button)
basicly; from a freash factory reset! Talkback settings
Help&feedback
YouTube video share arrow
YouTube home page on YouTube app
YouTube settings
Google privacy policy
Google home page in Chrome app
FRP.f0il. C o m -best website ever
Link #1 (we'll come back for link #2)
*Sometimes you have to long press link1 and select gmail
Gmail set up skip but sometimes I've used a method you'd login with a Microsoft account oddly enough I use my Xbox 360 account info and it works (@yahoo.com lol)
in Gmail top right three dot menu -account management settings
youre probably in the system settings by now
Security settings
enable unknown sources
dissable all administration apps
(Useless here but most other times nessisary)
apps- show system- clear data and/or dissable all wizzards and/or things that say setup
(Do not press home button if it appears to light up at any time)
(End of useless crap)
carefully press back button until we reach FRP.f0il again
download link #2 and install the app
(The money shot)
the e4 is the only fone I've ever seen this on.
Ims settings (screen shot added)
provision phone - turn switch on (screen shot added)
change underwear
pull down notification settings
press the gear for system settings
goto backup&restore
FACTORY RESET
ERASE EVERYTHING
spike fone on ground
*not liable for broken device
your FRP has now been bypassed
good day to yous :itallianfingerpinch:
whats password for moto all frp then please
NOTICE: Several users have reported issues downgrading from v7.2.x, so it might require some additional experimentation to downgrade from that version.
-
Missing your screenshot or twitch streaming functionality? Hate the new launcher layout w/ its tiny one row of icons and its numerous rows of psychologically-aggressive suggestion imposition?
Well, now you can stop cursing at Nvidia, because they provided a way (albiet, a highly technical and mostly-undocumented way), to load any version of their OS that you choose.
I've seen others wanting to downgrade (including myself), so I've collected the relevant steps which I used to successfully revert to an earlier version. This guide assumes a bit of technical working knowledge, so I apologize if you are one of the 'normal' people that Nvidia has bulldozed over...
All the usual "don't blame me for bricked devices" caveats apply.... please be careful, know what each step does! research each step!
Best of luck...
0 - prereqs
make sure your PC & nvidia shield are both plugged into a UPS, b/c a power failure during a flashing operation is not very pleasant.
make sure you have (or do get) the adb & fastboot binaries ("commands") for your computer
make sure that you get all your userdata off the device, because it will be erased by this process
1 - using a web browser
register for an nvidia developer account (which you will have an opportunity to do if you attempt the next step)
download the 6.3 'developer os' rom for your particular model
https: //developer.nvidia.com/shield-developer-os-images (sorry, noob filter won't allow the real/clickable url)
NB: The 6.3 developer rom for the 2017 console is missing the userdata.img, there are currently no reports (on this thread) if a different userimage (pre-6.3 or for the 2015 version) works on the 2017 console (testers welcome!).
NB: if the cost of being identified as a developer offends you (i.e. yielding a name, company, email, etc), then you can probably dig up a link to the roms in the comments or elsewhere on the xda forums.
2 - on the device
enable developer mode by clicking the 'build' entry in settings->info
enable usb debugging in settings->developer-options
plug it into your computer using the usb port furthest from the hdmi port
3 - in a terminal
unzip the downloaded rom & cd into the resulting directory
edit the 'flash-all.sh' script to add the following line just before the final reboot:
fastboot flash userdata userdata.img
#(this will add even more wall-time to the flashing process, but will clobber the already-erased newer 7.0 user partition data with the old)
adb reboot bootloader
fastboot oem unlock && ./flash-all.sh
NB: Now confirm your willingness to lose all your data. On the 2015 'pro' version of the console, this is accomplished by pressing (or holding) the nvidia logo 'button'... AND WILL TAKE NEARLY TWO HOURS. Others use the x/y/a/b buttons on the game controller connected to the usb port nearest to the hdmi port.
[... time passes ...]
NB: the 7.0 to 6.3 was a clean backstep for me, but if you are going between other versions, I can see that this script might stall in the middle if the device does not come back up with adb services available... in which case you will need to enter fastboot manually using a hardware method.
4 - Break TegraOTA
You have now flushed the correct version onto your device, but we can't complete the setup process... if you were to try, the final step would immediately and automatically start downloading & applying the latest (7.0) experience update! Therefore, we must neuter the updater itself.
Still in the terminal:
adb root
adb remount
adb shell
# now these commands are run in the adb shell (technically on the phone through the PC terminal)
# the first path was the right one for me, but I'm putting here all the paths known to me in case you are using a different version
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
5 - you should now be able to setup and pain-stakingly reconfigure your nvidia shield to the way it was before you blindly trusted an OEM update without doing extensive research beforehand.
PS: if you fear that netflix or amazon-video will at some point stop working because of this process, you might wish to "fastboot oem lock" the device (knowing that an unlock will erase your user-data, but having the developer rom means you can always get root access via adb).
I hope you find this useful.
Thanks! I will be trying this tonight! I miss 6.3 and PLEX is BROKEN in 7.0!
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
rossbeck said:
Thanks! I will be trying this tonight! I miss 6.3 and PLEX is BROKEN in 7.0!
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
Click to expand...
Click to collapse
Plex is NOT broken in 7.0 i use it everyday.
Builtfordtough1 said:
Plex is NOT broken in 7.0 i use it everyday.
Click to expand...
Click to collapse
I use it every day too... and since Plex v6.13, files fail to play after 3 seconds unless you run them a 2nd time.
It's a known issue that everyone is having due an acknowledged bug in exoplayer2 with certain containers like mkv. Since 7.0/oreo has plex v6.14 baked in as a system app, it's impossible to downgrade to v6.12 to get rid of the issue until Plex fixes it... and they've known about it for 2 months now. Since quantity has been their focus over quality lately, I'm not holding my breath for a fix.
The solution is to downgrade to 6.3, manually install plex v6.12, and turn off app updates.... so that's my plan.
rossbeck said:
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
Click to expand...
Click to collapse
I think it depends on the model. AFAIK, the newer 2017 ones need a controller (or possibly a USB keyboard) to confirm the userdata partition wipe.
Osndok said:
I think it depends on the model. AFAIK, the newer 2017 ones need a controller (or possibly a USB keyboard) to confirm the userdata partition wipe.
Click to expand...
Click to collapse
Ahhh, good call. I'll have him try a usb keyboard.
doesnt work for me... i have a nvidia shield tv 2015. i tried with flash-all.bat
and im stuck after reboot. is there any other way?
crazyscow said:
doesnt work for me... i have a nvidia shield tv 2015. i tried with flash-all.bat
and im stuck after reboot. is there any other way?
Click to expand...
Click to collapse
What command did the script stop at? and how 'stuck' are you (i.e. can you get to fastboot?).
I imagine that if you started with the wrong rom, it would likely fail to boot.
thanks for the fast reply, i just manually installed it without the bat file
I went manually into the fastboot mode by unplugging the power pressing the power button and plugging it back in until fastboot mode comes.
then i typed
fastboot flash staging blob
fastboot flash boot boot.img
wait until the sound on windows comes then - adb devices
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and then it booted
crazyscow said:
thanks for the fast reply, i just manually installed it without the bat file
I went manually into the fastboot mode by unplugging the power pressing the power button and plugging it back in until fastboot mode comes.
then i typed
fastboot flash staging blob
fastboot flash boot boot.img
wait until the sound on windows comes then - adb devices
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and then it booted
Click to expand...
Click to collapse
How did you get past the forced update? I was able to flash 6.3, but it forces the update during setup and I don't have ADB access yet because usb debugging isn't turned on. Can't disable the OTA updates without it!
Basically I've successfully flashed 6.3 and am sitting at a working fastboot prompt. Not sure what to do from here.
rossbeck said:
How did you get past the forced update? I was able to flash 6.3, but it forces the update during setup and I don't have ADB access yet because usb debugging isn't turned on. Can't disable the OTA updates without it!
Basically I've successfully flashed 6.3 and am sitting at a working fastboot prompt. Not sure what to do from here.
Click to expand...
Click to collapse
Disabling the OTA update is step four, if ADB does not work, I would guess that you forgot to flash userdata.img in the previous step(s).
Osndok said:
Disabling the OTA update is step four, if ADB does not work, I would guess that you forgot to flash userdata.img in the previous step(s).
Click to expand...
Click to collapse
So you did what to get userdata.img? Created it in TWRP or something? It's not included with the recovery images... and this basically bypasses the OOBE/setup stuff?
Thanks man
rossbeck said:
you did what to get userdata.img? ... It's not included with the recovery images... and this basically bypasses the OOBE/setup stuff?
Click to expand...
Click to collapse
userdata.img is inside the ZIP from the nvidia developer website, as can be seen here:
Code:
$ jar tf nv-recovery-image-shield-atv-pro-6.3.0-dev_rooted.zip | grep user
nv-recovery-image-shield-atv-pro-6.3.0-dev_rooted/userdata.img
rossbeck said:
[the userdata.img] basically bypasses the OOBE/setup stuff?
Click to expand...
Click to collapse
No... not really. The userdata.img from the developer pack both (1) matches the 6.3 version (doesn't have any of the newer, potentially incompatible entries), and (2) has developer-mode & adb enabled by default.
So in addition to it probably just working better, flashing the userdata will let you get adb access, and thus break the OTA, and thus complete the setup w/o the update.
I thought it would boot up, but im still stuck on the android loading screen!
Ill try to reflash the rom again tonight.
update:
I got it to work now, without update having to update to 7.0.2
Code:
adb reboot bootloader
fastboot flash staging blob
fastboot flash boot boot.img
fastboot reboot
//waiting for nvidia logo and the Windows PC to make the connection noise
//otherwise you can check by typing
adb devices
// if it shows something then continue
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot reboot
once it booted it up, i went thru the procedure of setting it up with my network and google account, then the window pop-up "downloading version 7.0.2" then i followed the guide in the first post
Code:
adb root
adb remount
adb shell
# now these commands are run in the adb shell (technically on the phone through the PC terminal)
# the first path was the right one for me, but I'm putting here all the paths known to me in case you are using a different version
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
after that it booted up into android 7 with not OTA update notification.
thank you!
hello, thanks for the contribution, but when decompressing the image of developer 6.3 of shield tv 2017 I do not know where to get the file userdata.img, could you give me where to get it?
lohengrim93 said:
when decompressing the image of developer 6.3 of shield tv 2017 I do not know where to get the file userdata.img, could you give me where to get it?
Click to expand...
Click to collapse
As I said in #13, I found the userdata.img inside the archive from nvidia (the 2015 "pro" version to be exact), and I don't know why it is missing from (at least) the 6.3 archive for the 2017 device.
If you are feeling adventurous, you can try downloading either of the 2015 zips, and use its userdata.img... maybe the 16gb one?
I would be eager to know if that works for you, since I'm unsure if the userdata.img can be mixed between different versions of the console...
JUST BE VARY CAREFUL to not mix up your directories and start flashing the wrong blobs & boots... that would be a recipe for a brickin', methinks.
crazyscow said:
I got it to work now, without ... having to update to 7.0.2
... i followed the guide in the first post...
after that it booted up into android 7 [without] OTA update notification.
thank you!
Click to expand...
Click to collapse
I'm quite pleased to hear that it worked for you... (my first success report!).
Adb root
When I attempt to run the adb root command it just errors on me at the end, do I need to have the shield booted into setup for it to work?
Insatiablejimmy said:
When I attempt to run the adb root command it just errors on me at the end, do I need to have the shield booted into setup for it to work?
Click to expand...
Click to collapse
You forgot to include (or even describe) the actual error message, so I can only guess as to what is wrong.
However, since "adb root" is the linchpin of the developer rom, I would assume that you did not flash a developer rom (or as indicated above concerning the 2017 model) are missing the "userdata.img", which could also cause this behavior.
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
CruelSun said:
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
Click to expand...
Click to collapse
This happens because the device drivers are not completely installed.
CruelSun said:
I just bought an unlocked Pixel 3XL from the Google store.
PC is Linux Mint 19 with both adb and fastboot installed.
I have developer mode, usb debugging on. PC has been granted permission to debug.
I am stuck trying to unlock the bootloader.
$ adb reboot bootloader --boots the phone into the boatloader as expected,
Device state: locked
Power button options do not include: Unlock Bootloader
$ fastboot flashing unlock --returns: < waiting for any device >
$ fastboot devices --returns: no permissions (user in plugdev group; are your udev rules wrong?)
Seems that adb can communicate with the phone but fastboot does not see the phone... I have been searching for further info on adb/fastboot, but so far no joy.
Can anyone recommend a solution or further troubleshooting in this situation?
Click to expand...
Click to collapse
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS)
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Thank you for the replies.
I tried to use adb/fastboot on a Win7 desktop after I posted the above, and I cannot get the phone and win7 to see each other at all.
I have since tried to get into recovery mode but get "No Command".
What can I do to move forward? Phone boots and works fine once I get out of recovery.
This phone is fresh from Google, never had a sim in it.
Thank you for the detailed answer. I am having difficulty implementing the mods you listed. I have been a Linux user on and off for several years but I do not have deep knowledge of the inner workings.
uicnren said:
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS) This returns "permission denied"
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev" <-- I have no rules.d file, just an empty folder named rules.d in that location
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Click to expand...
Click to collapse
Make sure you are using the latest ADB download files.
Sent from my Pixel 3 XL
Eudeferrer said:
Make sure you are using the latest ADB download files.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Yes, r28.0.3.
Update:
CruelSun said:
Thank you for the replies.
I have since tried to get into recovery mode but get "No Command". I found out how t get past this, I'm going to do a factory reset and start over.
This phone is fresh from Google, never had a sim in it.
Click to expand...
Click to collapse
Success!
After factory reset, stepped through process again, but still no joy on Linux (Certainly still the above mentioned group permissions issue which I failed to figure out how to fix).
Win7 did not seem to be working for a long time (got no popup on phone asking for debugging authorization), after a half hour of attempts I walked away for 15+ minutes and when I looked back at the phone the Debug auth popup was finally there...
Booted to fastboot, did $ fastboot flashing unlock <= Returned: "Finished. Total time: 0.356s" LOL, yeah, with me struggling since yesterday...
Now fastboot screen says Device status: Unlocked
Thanks to everyone here at XDA!
CruelSun said:
Success!
After factory reset, stepped through process again, but still no joy on Linux (Certainly still the above mentioned group permissions issue which I failed to figure out how to fix).
Win7 did not seem to be working for a long time (got no popup on phone asking for debugging authorization), after a half hour of attempts I walked away for 15+ minutes and when I looked back at the phone the Debug auth popup was finally there...
Booted to fastboot, did $ fastboot flashing unlock <= Returned: "Finished. Total time: 0.356s" LOL, yeah, with me struggling since yesterday...
Now fastboot screen says Device status: Unlocked
Thanks to everyone here at XDA!
Click to expand...
Click to collapse
Glad you figured it out.
Sent from my Pixel 3 XL
Hi !
I had the same issue here, new pixel 3 XL owner
win 10 home.
debugging mode active (allowed PC), OEM unlock checked.
searching for devices using : .\adb devices while the phone is on results : 89EY06JQW device
while phone Off : empty list.
trying to unlock using : .\adb fastboot flash unlock .
wont do nothing.
I did a factory reset, still the same results :/
any idea ?
done.
re-installing the drivers, reboot Pc, and using cmd without administration did it. lol
STALKER18 said:
Hi !
I had the same issue here, new pixel 3 XL owner
win 10 home.
debugging mode active (allowed PC), OEM unlock checked.
searching for devices using : .\adb devices while the phone is on results : 89EY06JQW device
while phone Off : empty list.
trying to unlock using : .\adb fastboot flash unlock .
wont do nothing.
I did a factory reset, still the same results :/
any idea ?
done.
re-installing the drivers, reboot Pc, and using cmd without administration did it. lol
Click to expand...
Click to collapse
Glad you got it sorted out.
Frankly I expected to have smooth sailing on my Linux PC, but had to resort to win7.
Sent from my Pixel 3 XL using Tapatalk
CruelSun said:
Glad you got it sorted out.
Frankly I expected to have smooth sailing on my Linux PC, but had to resort to win7.
Click to expand...
Click to collapse
Windows has to update. The 30 minutes was probably the update in the background. My windows 10 did the same thing. Linux doesnt work anymore. I used ubuntu with latest adb and fastboot packages. Manually installed newest tools zip. Nothing. I got it to work a few times. Windows 10 is a little buggy too. Only fastboot I found to work on the pixel 3 xl without and or little errors was my MacBook. Which I have dual booted to chromeos and Ubuntu in chromeos. Also restarting on windows anything puts it into the loop of things. You can install adb and fastboot on windows but they need a restart to work. Unless just mounting the file folder and using it that way.
I am still trying to get adb/fastboot to work on my Linux Mint 19.1 laptop so that I don't have to rely on an old Win7 machine to sideload monthly updates. I have been a Linux user on and off for several years, but I have no deep knowledge of what goes on 'under the hood'...
Can anyone here with a deeper knowledge of Linux and/or Mint 19 help me implement the mods that uicnren outlined, or otherwise help me get adb/fastboot to work?
uicnren said:
As stated, the user trying to execute the command has not been added to the udev rules.
Basically, you'll need: usermod -aG plugdev $LOGNAME (or equivalent for your OS)
Click to expand...
Click to collapse
I think I succeeded in adding myself to the plugdev group with this command:
Code:
sudo usermod -aG plugdev cruelsun
uicnren said:
the rules.d file in etc/udev needs to be edited (if its not already) to include: SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
Click to expand...
Click to collapse
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
uicnren said:
then: chmod 644 51-android.rules
and: chown root: 51-android.rules
Click to expand...
Click to collapse
I Have not run these commands yet, as I am trying to do this in the order that uicnren specified...
CruelSun said:
I am still trying to get adb/fastboot to work on my Linux Mint 19.1 laptop so that I don't have to rely on an old Win7 machine to sideload monthly updates. I have been a Linux user on and off for several years, but I have no deep knowledge of what goes on 'under the hood'...
Can anyone here with a deeper knowledge of Linux and/or Mint 19 help me implement the mods that uicnren outlined, or otherwise help me get adb/fastboot to work?
I think I succeeded in adding myself to the plugdev group with this command:
Code:
sudo usermod -aG plugdev cruelsun
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
I Have not run these commands yet, as I am trying to do this in the order that uicnren specified...
Click to expand...
Click to collapse
Simplest method: https://github.com/corbindavenport/nexus-tools
CruelSun said:
...
In Mint 19.1, I find no rules.d file in etc/udev. There is an empty folder named rules.d there, and a file named udev.conf.
Should I maybe try adding the specified line to udev.conf, or create a rules.d file?
...
Click to expand...
Click to collapse
I realize this is a bit old now, but, in case it's helpful for someone in the future...
Often the /etc/used/rules.d directory is empty. You just need to add the file 51-android.rules into that directory.
Code:
sudo touch /etc/used/rules.d/51-android.rules
You need to run that command as root which is why it's prefaced with sudo.
Then you can edit the file as described in the first post. As stated earlier, much better to type into your editor rather than cut and paste because you want to make sure no weird html characters get introduced.
The bootloop started very randomly one day and my phone kept restarting and the battery became very hot.(I was asleep so I noticed this after I woke up). I had already switched to an iphone but I was using the moto g for music and stuff like that. I was able to boot once and then the storage suddenly got full and the bootloop started again. So, I just removed the battery and left it. I have a whatsapp backup on it that has some very important data which I need at the moment. The phone is stock without root or cwm. Usb debugging was on, I don't know if that helps though. I really need to recover just that one backup file. I went through quite a few threads and didn't find anything that could help me. Is there any way to recover it. I don't mind if the process is tedious.
Z91 said:
The bootloop started very randomly one day and my phone kept restarting and the battery became very hot.(I was asleep so I noticed this after I woke up). I had already switched to an iphone but I was using the moto g for music and stuff like that. I was able to boot once and then the storage suddenly got full and the bootloop started again. So, I just removed the battery and left it. I have a whatsapp backup on it that has some very important data which I need at the moment. The phone is stock without root or cwm. Usb debugging was on, I don't know if that helps though. I really need to recover just that one backup file. I went through quite a few threads and didn't find anything that could help me. Is there any way to recover it. I don't mind if the process is tedious.
Click to expand...
Click to collapse
I guess you can pull files from your phone via ADB commands. Can you get into recovery mode?
sharjeel.019 said:
I guess you can pull files from your phone via ADB commands. Can you get into recovery mode?
Click to expand...
Click to collapse
I can get into recovery but adb only works in sideload so I can't do stuff like adb pull, etc.
If your bootloader is unlocked you can flash twrp and then pull files via adb or by mtp (drag and drop files to pc)
If your bootloader is locked there's nothing you can do
Note adb doesn't work in stock recovery
TheFixItMan said:
If your bootloader is unlocked you can flash twrp and then pull files via adb or by mtp (drag and drop files to pc)
If your bootloader is locked there's nothing you can do
Note adb doesn't work in stock recovery
Click to expand...
Click to collapse
I haven't unlocked the bootloader so I'm assuming it's locked. Is there no way around it?
Z91 said:
I haven't unlocked the bootloader so I'm assuming it's locked. Is there no way around it?
Click to expand...
Click to collapse
No - unlocking the bootloader requires a data wipe
Technically if adb debugging is enabled your phone might boot enough for adb to become available but it might only be for a few seconds before it restarts
You'll keep having to type
adb devices
And see if you get a device listed but the chances of it being available long enough for you to pull anything is pretty much zero
TheFixItMan said:
No - unlocking the bootloader requires a data wipe
Technically if adb debugging is enabled your phone might boot enough for adb to become available but it might only be for a few seconds before it restarts
You'll keep having to type
adb devices
And see if you get a device listed but the chances of it being available long enough for you to pull anything is pretty much zero
Click to expand...
Click to collapse
Ohh, I don't remember exactly where but while researching I had read that it's possible to stop the phone at that boot stage. Is something like that doable?
Z91 said:
Ohh, I don't remember exactly where but while researching I had read that it's possible to stop the phone at that boot stage. Is something like that doable?
Click to expand...
Click to collapse
Found this it may help
Create a script and run it when adb is available on the device - usually sometime after boot logo
Windows version batch script eg run.bat
Code:
@ECHO off
cd /d %~dp0
echo.
echo Waiting for device…
adb wait-for-device
echo.
adb -d shell stop
adb pull (put directory location here)
Linux Version script eg run.sh
Code:
#!/system/bin/sh
echo " "
echo "Wating for device..."
./adb wait-for-device
echo " "
./adb -d shell stop
./adb pull (location of directory here)
TheFixItMan said:
Found this it may help
Create a script and run it when adb is available on the device - usually sometime after boot logo
Windows version batch script eg run.bat
Code:
@ECHO off
cd /d %~dp0
echo.
echo Waiting for device…
adb wait-for-device
echo.
adb -d shell stop
adb pull (put directory location here)
Linux Version script eg run.sh
Code:
#!/system/bin/sh
echo " "
echo "Wating for device..."
./adb wait-for-device
echo " "
./adb -d shell stop
./adb pull (location of directory here)
Click to expand...
Click to collapse
So, I tried this. Bu I realized soon that adb devices was recognizing the device during the boot. SO, the scrip couldn't work I guess. Do I have to do something so that the phone gets recognized during boot.
Z91 said:
So, I tried this. Bu I realized soon that adb devices was recognizing the device during the boot. SO, the scrip couldn't work I guess. Do I have to do something so that the phone gets recognized during boot.
Click to expand...
Click to collapse
If your phone doesn't reach the stage where adb is enabled there's nothing you can do
I just wanted to gather resources and guidance on workarounds for caveats found in:
nVidia Shield Experience Upgrade 9.0.0 with Android 11
Scoped storage for instance.
New Google TV launcher
Caution: I'm not responsible if you end up bricking your nVidia Shield Android TV.
Change default launcherLauncher alternativesFLauncher
https://play.google.com/store/apps/details?id=me.efesser.flauncher
https://gitlab.com/etienn01/flauncher
Example: FLauncher
Install FLauncher from Google Play store.
Open FLauncher to make sure it works.
Enable ADB over network on the nVidia Shield (developer options).
Connect ADB from a computer with android-tools.
Disable default launcher with following ADB command:
Code:
adb shell pm disable-user --user 0 com.google.android.tvlauncher
Disconnect ADB.
Press "Home" button on the nVidia Shield. This should open FLauncher.
Instructions
https://techmogulchannel.com/tutori...lt-launcher-to-custom-launcher-windows-guide/
https://www.reddit.com/r/AndroidTV/comments/o96tun/how_to_install_a_3rdparty_launcher_as_default_on/
Set scoped storage permissionsExample: Solid File Explorer
Markdown (GitHub flavored):
### Example session with nVidia Shield Android TV
#### Start ADB server
adb start-server
#### Connect (approve request on the Shield)
adb connect 192.168.86.36:5555
#### Solid Explorer
adb shell cmd appops get --uid pl.solidexplorer2
adb shell cmd appops set --uid pl.solidexplorer2 android:MANAGE_EXTERNAL_STORAGE allow
adb shell cmd appops set --uid pl.solidexplorer2 android:REQUEST_INSTALL_PACKAGES allow
#### Disconnect
adb disconnect
#### Turn off ADB server
adb kill-server
Instructions
https://www.codetd.com/en/article/10481938
https://forum.xda-developers.com/t/...adb-on-note-10-updated-to-android-11.4221617/
https://developer.android.com/train...es#enable-manage-external-storage-for-testing
https://www.reddit.com/r/androiddev/comments/mscu80/as_a_user_is_it_possible_for_me_to_grant_an_old/
Roll back to 8.2.3Download
https://developer.nvidia.com/gameworksdownload#?search=recovery os image
Instructions
https://developer.download.nvidia.c...ar/howtoflash/How-To-Flash-Recovery-Image.txt
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/t/3321404/
https://forum.xda-developers.com/t/4392605/#post-86397133 by @perieanuo.
Other related guides by me
Ready made Leanback Icons and Shortcuts for "regular" Android Apps
[Tool][Windows][PowerShell] Android Platform Tools Updater (ADB & Fastboot)
Thanks for this !
I just hate this google tv launcher update and those F****** ads.
Now it's clean, Flauncher looks great
Thank you for that awesome guide
I have one question regarding scoped storage permissions. I'm trying to achieve the same with Kodi like you did with Solid File Explorer.
The first command worked fine: adb shell cmd appops get --uid org.xbmc.kodi
I get the following output:
Uid mode: LEGACY_STORAGE: allow
TAKE_AUDIO_FOCUS: allow; time=+2d3h23m52s536ms ago
WAKE_LOCK: allow; time=+2d3h23m52s331ms ago; duration=+22m38s145ms
READ_EXTERNAL_STORAGE: allow; time=+14h44m6s853ms ago
WRITE_EXTERNAL_STORAGE: allow
Unfortunately, when I try to execute the 2nd command adb shell cmd appops set --uid org.xbmc.kodi android:MANAGE_EXTERNAL_STORAGE allow I get the following error:
Error: Unknown operation string: android:MANAGE_EXTERNAL_STORAGE
Is there anything that I'm missing or not possible with Kodi?
No_Reason said:
Thank you for that awesome guide
I have one question regarding scoped storage permissions. I'm trying to achieve the same with Kodi like you did with Solid File Explorer.
The first command worked fine: adb shell cmd appops get --uid org.xbmc.kodi
I get the following output:
Uid mode: LEGACY_STORAGE: allow
TAKE_AUDIO_FOCUS: allow; time=+2d3h23m52s536ms ago
WAKE_LOCK: allow; time=+2d3h23m52s331ms ago; duration=+22m38s145ms
READ_EXTERNAL_STORAGE: allow; time=+14h44m6s853ms ago
WRITE_EXTERNAL_STORAGE: allow
Unfortunately, when I try to execute the 2nd command adb shell cmd appops set --uid org.xbmc.kodi android:MANAGE_EXTERNAL_STORAGE allow I get the following error:
Error: Unknown operation string: android:MANAGE_EXTERNAL_STORAGE
Is there anything that I'm missing or not possible with Kodi?
Click to expand...
Click to collapse
Are you using the latest version of Android platform-tools? I also got some errors when following a guide, turned out the command syntax had changed a little with newer versions of adb.
https://developer.android.com/studio/releases/platform-tools#downloads
I just switched to the latest version of Android platform-tools.
adb version is giving me:
Android Debug Bridge version 1.0.41
Version 32.0.0-8006631
But I still get the same error message as mentioned above
Any idea, why it's still failing? Does the app itself need to support this?
hi,
i downgraded but the flashing is not really like described here
https://developer.download.nvidia.c...ar/howtoflash/How-To-Flash-Recovery-Image.txt
those 2 are incorrect:
- fastboot flash dtb mdarcy.dtb.img
- fastboot flash vbmeta vbmeta.img
in my case i did (the files were in "c:\adb\822" folder, i used official 8.2.2 recovery image, but tested the same for 8.2.3 and 8.2.0)
fastboot flash staging ./822/blob
fastboot flash boot ./822/boot.img
fastboot flash recovery ./822/recovery.img
fastboot flash system ./822/system.img
fastboot flash vendor ./822/vendor.img
fastboot flash dtb ./822/tegra210-darcy-p2894-0050-a08-00.dtb
(attention i choosed /tegra210-darcy-p2894-0050-a08-00.dtb because my shield was this version, to be checked before flashing in settings/about...)
I tried with and without dtb and with and without erasing user data from fastboot menu (the last option)
I guess mdarcy.dtb.img and vbmeta.img are from other recovery archives, my test was done 27 jan 2022, maybe nvidia modified those recovery archives?
anyway, for inexperienced users it should be more clear what to flash, in what order, why writing this and that, the tutos for this downgrade are a mess. someone on reddit says we should format all those partitions but he says it at the end of his post, so if you respect command orders and reboot shield you're screwed.
my 2 cts, you should write ALL partitions provided by nvidia in archive after unlocking bootloader (maybe formatting them before??? but with UPS attached, risky thing btw), reset shield, relock bootloader and maybe reset shield from bootloader menu or gui.
i hope a pro take this in hand explaining for us
in the process i managed to fry my 'away' usb port power (it works well as debug port but his power control chip is dead, tried already deactivating usd debug and usb file sharing and reflashing 3 times like i described before, but it's clearrly a hardware issue). well, this one it's on me, I had olimex usb separator with power supply conected and after reflash i set that away usb as normal port, mayhe the two devices (shield and olimex usb-iso isolator tried to power the +5V line at once and the nvidia one was the weaker one). normally nvidia should entered protected mode, but i'm not the hw designer on that one
Any you guys know how to force landscape android tv 9, whole apks I used to forces doesn't work, I have 2015 and 2017 models, please help.
No_Reason said:
I just switched to the latest version of Android platform-tools.
adb version is giving me:
Android Debug Bridge version 1.0.41
Version 32.0.0-8006631
But I still get the same error message as mentioned above
Any idea, why it's still failing? Does the app itself need to support this?
Click to expand...
Click to collapse
Hmm. I'm certainly no expert at this. But what you say about the app need to support it might make sense. With the get command on Solid Explorer, I saw that permission that I could set, but you can't.
baba702 said:
Any you guys know how to force landscape android tv 9, whole apks I used to forces doesn't work, I have 2015 and 2017 models, please help.
Click to expand...
Click to collapse
Tried hotfix 3?
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481434/shield-experience-upgrade-90-hotfix-image/
o-l-a-v said:
Tried hotfix 3?
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481434/shield-experience-upgrade-90-hotfix-image/
Click to expand...
Click to collapse
Thank you I didn't know about it I'll try
Ok just I installed hotfix 3 but I'm still have several issues, now button mapper doesn't work and the screen rotation doesn't work, any help
baba702 said:
Ok just I installed hotfix 3 but I'm still have several issues, now button mapper doesn't work and the screen rotation doesn't work, any help
Click to expand...
Click to collapse
If you use button remapper so change default launcher, use the method in the original post instead to just disable the default launcher app. Else, ask the button remapper developer I guess.
For the 2nd problem (orientation), I think there is a adb command to set it. Google it and see what you find.
Edit: Orientation, found some related info:
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481782/shield-experience-upgrade-90-known-issues/3206852/
I
o-l-a-v said:
If you use button remapper so change default launcher, use the method in the original post instead to just disable the default launcher app. Else, ask the button remapper developer I guess.
For the 2nd problem (orientation), I think there is a adb command to set it. Google it and see what you find.
Edit: Orientation, found some related info:
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481782/shield-experience-upgrade-90-known-issues/3206852/
Click to expand...
Click to collapse
I give whole the permite but doesn't work the buttons remapper, something with YouTube vanced is the problem, I unistalled and that works, rotation I tried with whole permite included the energy optimization access but no work
perieanuo said:
hi,
i downgraded but the flashing is not really like described here
https://developer.download.nvidia.c...ar/howtoflash/How-To-Flash-Recovery-Image.txt
those 2 are incorrect:
- fastboot flash dtb mdarcy.dtb.img
- fastboot flash vbmeta vbmeta.img
in my case i did (the files were in "c:\adb\822" folder, i used official 8.2.2 recovery image, but tested the same for 8.2.3 and 8.2.0)
fastboot flash staging ./822/blob
fastboot flash boot ./822/boot.img
fastboot flash recovery ./822/recovery.img
fastboot flash system ./822/system.img
fastboot flash vendor ./822/vendor.img
fastboot flash dtb ./822/tegra210-darcy-p2894-0050-a08-00.dtb
(attention i choosed /tegra210-darcy-p2894-0050-a08-00.dtb because my shield was this version, to be checked before flashing in settings/about...)
I tried with and without dtb and with and without erasing user data from fastboot menu (the last option)
I guess mdarcy.dtb.img and vbmeta.img are from other recovery archives, my test was done 27 jan 2022, maybe nvidia modified those recovery archives?
anyway, for inexperienced users it should be more clear what to flash, in what order, why writing this and that, the tutos for this downgrade are a mess. someone on reddit says we should format all those partitions but he says it at the end of his post, so if you respect command orders and reboot shield you're screwed.
my 2 cts, you should write ALL partitions provided by nvidia in archive after unlocking bootloader (maybe formatting them before??? but with UPS attached, risky thing btw), reset shield, relock bootloader and maybe reset shield from bootloader menu or gui.
i hope a pro take this in hand explaining for us
in the process i managed to fry my 'away' usb port power (it works well as debug port but his power control chip is dead, tried already deactivating usd debug and usb file sharing and reflashing 3 times like i described before, but it's clearrly a hardware issue). well, this one it's on me, I had olimex usb separator with power supply conected and after reflash i set that away usb as normal port, mayhe the two devices (shield and olimex usb-iso isolator tried to power the +5V line at once and the nvidia one was the weaker one). normally nvidia should entered protected mode, but i'm not the hw designer on that one
Click to expand...
Click to collapse
this is really good info - seriously. I'm about to downgrade to 8.2.3 on the 2017_16gb model and I'm trying to take it all in. Weird how there's not a ton of good information on this. Did you follow any other videos or guides?
Alekos said:
this is really good info - seriously. I'm about to downgrade to 8.2.3 on the 2017_16gb model and I'm trying to take it all in. Weird how there's not a ton of good information on this. Did you follow any other videos or guides?
Click to expand...
Click to collapse
hi,
i did kinda mixup of some guides like
https://www.reddit.com/r/ShieldAndroidTV/comments/s3yqe1
(also tested like he said, first fastboot erase boot/staging/recovery/system/vendor, then write those)
the procedure was as simpliy as this:
__________________________________________________________________________________________________________________
How to downgrade your Shield TV Pro back to 8.2.3 (Android 9)
The first step is to go to Settings, Device Preferences, About, tap build number 7-8 times for developer options and enable USB debugging and allow debugging through your PC. Before you reboot to the bootloader, plug in a keyboard or your Shield Controller to continue, then input adb reboot bootloader (must have drivers installed), unlock bootloader, and factory reset, reboot and unplug the USB and power for a full unlock or else you'll get "write failed" when flashing.
first, wipe partitions:
fastboot erase boot
fastboot erase staging
fastboot erase recovery
fastboot erase system
fastboot erase vendor
second, flash partitions (i saved/unzipped in c:\adb\823 the files, that's why "./823/" appears below)
fastboot flash boot ./823/boot.img
fastboot flash staging ./823/blob
fastboot flash recovery ./823/recovery.img
fastboot flash system ./823/system.img
fastboot flash vendor ./823/vendor.img
I relocked bootloader at the end
fastboot oem lock (or via bootloader GUI)
Just used a simple usb keyboard ( a french one, "A" was in the place of "Q" key) and bootloader use US layout as default for keyboard.
The USB cable must be a quality one, mine was USB3 one, 1m long.
Hey, so you guys don't recommend updating to Android 11 on the 2017 Shield TV?
I'm still running Android 9 (NVidia Experience 8.2.3) and everything works well. Will I gain anything by updating?
Ghisy said:
Hey, so you guys don't recommend updating to Android 11 on the 2017 Shield TV?
I'm still running Android 9 (NVidia Experience 8.2.3) and everything works well. Will I gain anything by updating?
Click to expand...
Click to collapse
I'd wait for next stable/ non-hotfix release, and then check feedback on Reddit and the nVidia forum before doing the jump.
But I won't bother rolling back to 8.2.3 either, 9.0.0 works OK for me. If you're hosting Plex server on your Shield, definitely wait. I only use it as a media player, nothing fancy.
o-l-a-v said:
I'd wait for next stable/ non-hotfix release, and then check feedback on Reddit and the nVidia forum before doing the jump.
But I won't bother rolling back to 8.2.3 either, 9.0.0 works OK for me. If you're hosting Plex server on your Shield, definitely wait. I only use it as a media player, nothing fancy.
Click to expand...
Click to collapse
Well, I guess 9.0.1 is the stable one apparently: https://9to5google.com/2022/02/15/shield-tv-9-0-1-update-android-11/
I need to wait for the developer image because I want to root my Shield TV again. Although there's no guide here that's up to date unfortunately...
baba702 said:
I
I give whole the permite but doesn't work the buttons remapper, something with YouTube vanced is the problem, I unistalled and that works, rotation I tried with whole permite included the energy optimization access but no work
Click to expand...
Click to collapse
For the screen orientation setting, have you tried something as simple as a "forced rotation" app? I've used that for apps that normally come up in portrait that i wanted to force into landscape mode (ie YouTube Vanced, Magisk Manager, etc).
Here's one that's worked for me in the past (side loaded):
https://m.apkpure.com/set-orientation/com.googlecode.eyesfree.setorientation
o-l-a-v said:
I just wanted to gather resources and guidance on workarounds for caveats found in:
nVidia Shield Experience Upgrade 9.0.0 with Android 11
Scoped storage for instance.
New Google TV launcher
Caution: I'm not responsible if you end up bricking your nVidia Shield Android TV.
Change default launcherLauncher alternativesFLauncher
https://play.google.com/store/apps/details?id=me.efesser.flauncher
https://gitlab.com/etienn01/flauncher
Example: FLauncher
Install FLauncher from Google Play store.
Open FLauncher to make sure it works.
Enable ADB over network on the nVidia Shield (developer options).
Connect ADB from a computer with android-tools.
Disable default launcher with following ADB command:
Code:
adb shell pm disable-user --user 0 com.google.android.tvlauncher
Disconnect ADB.
Press "Home" button on the nVidia Shield. This should open FLauncher.
Instructions
https://techmogulchannel.com/tutori...lt-launcher-to-custom-launcher-windows-guide/
https://www.reddit.com/r/AndroidTV/comments/o96tun/how_to_install_a_3rdparty_launcher_as_default_on/
Set scoped storage permissionsExample: Solid File Explorer
Markdown (GitHub flavored):
### Example session with nVidia Shield Android TV
#### Start ADB server
adb start-server
#### Connect (approve request on the Shield)
adb connect 192.168.86.36:5555
#### Solid Explorer
adb shell cmd appops get --uid pl.solidexplorer2
adb shell cmd appops set --uid pl.solidexplorer2 android:MANAGE_EXTERNAL_STORAGE allow
adb shell cmd appops set --uid pl.solidexplorer2 android:REQUEST_INSTALL_PACKAGES allow
#### Disconnect
adb disconnect
#### Turn off ADB server
adb kill-server
Instructions
https://www.codetd.com/en/article/10481938
https://forum.xda-developers.com/t/...adb-on-note-10-updated-to-android-11.4221617/
https://developer.android.com/train...es#enable-manage-external-storage-for-testing
https://www.reddit.com/r/androiddev/comments/mscu80/as_a_user_is_it_possible_for_me_to_grant_an_old/
Roll back to 8.2.3Download
https://developer.nvidia.com/gameworksdownload#?search=recovery os image
Instructions
https://developer.download.nvidia.c...ar/howtoflash/How-To-Flash-Recovery-Image.txt
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/t/3321404/
https://forum.xda-developers.com/t/4392605/#post-86397133 by @perieanuo.
Other related guides by me
Ready made Leanback Icons and Shortcuts for "regular" Android Apps
[Tool][Windows][PowerShell] Android Platform Tools Updater (ADB & Fastboot)
Click to expand...
Click to collapse
Do you need to be rooted to Set Scoped Storage permissions or install an alternative launcher?
Is there a guide for rooting the Nvidia Shield 2017 using linux?
Thanks.
bdika