Develop Bugs

Help with reset...

So I decided to try to run ubuntu touch on my Samsung Galaxy Nexus(verizon). All went well, but now it seems I cant start the phone, can only get into fastboot mode. Can anyone please walk me through the steps of putting stock android back on my phone? I have adb and fastboot installed on my computer. There's a guide here that walks you through the process of returning the phone to stock software/firmware, but it requires USB debugging to be on, which I can't turn on because the phone won't boot up. I greatly appreciate any help!!!
Phone Info(what's written in fastboot):
PRODUCT NAME-Tuna
VARIANT- toro 32GB
HW VERSION- 9
BOOTLOADER VERSION: PRIMELC03
BASEBAND VERSION- I515.FK02 CDMA-I515.FK01
CARRIER INFO- NONE
SIGNING- production
LOCK STATE- UNLOCKED

You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command

ashclepdia said:
You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command
Click to expand...
Click to collapse
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;

vsp3317 said:
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;
Click to expand...
Click to collapse
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
https://developers.google.com/android/nexus/images
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away

ashclepdia said:
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away
Click to expand...
Click to collapse
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.

vsp3317 said:
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.
Click to expand...
Click to collapse
No problem buddy
That's what these forums are for, learning, helping, development, all that good stuff! Just happy it went smoothly for ya.
I think it used to be named .exe, at least it shows as exe on my laptop but I use Linux so it could just be seeing it differently(since I have wine installed)
There is usually a windows executable and a Linux .sh script that can be executed from the terminal to start the process.
See, it's not all THAT bad now is it? Especially since now you know how to do it, messing up the device isn't such a daunting thing anymore lol.
As for keeping status 7 from happening again I highly recommend bookmarking the TWRP or CWM official sites so that before flashing things in the future, you can make sure you have the most up to date custom recovery installed by comparing what is available vs what you have installed(booting into recovery mode will usually have the version info somewhere on the main screen) and of course having a recent nandroid backup made within your current custom recovery. I prefer TWRP but it's a personal choice to each user which they use
Just don't be afraid to play around
Congrats again on your first soft brick&restore! Lol
It's such a relieving feeling once you bring device back from the dead ain't it?

Root Working

Root is no longer working on MM update.

Don't suppose anybody knows how to get to recovery with hardware button?

hecksagon said:
Don't suppose anybody knows how to get to recovery with hardware button?
Click to expand...
Click to collapse
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.

CSX321 said:
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
Click to expand...
Click to collapse
You are a hero. I have looked for the better part of 2 hours for this. Anyway I'll sideload the LP update and start over. Hopefully somebody can make use of the recovery and boot pulls and get us a working recovery.

I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.

nethead72 said:
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
Click to expand...
Click to collapse
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.

CSX321 said:
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
Click to expand...
Click to collapse
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.

File Types?
hecksagon said:
The latest Windows version of kingroot works on the zenwatch. I currently have root that persists after reboot and I am working on pulling the boot.img and recovery.img. Not sure what to do after that, hope somebody can pick up on this.
Recovery.img
https://drive.google.com/file/d/0BxOsuCVqSlnfVzVGRWo4bmZZZHc/view?usp=docslist_api
Boot.img
https://drive.google.com/file/d/0BxOsuCVqSlnfLVp4Z19EQ0owdTQ/view?usp=docslist_api
Click to expand...
Click to collapse
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
hecksagon said:
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
Click to expand...
Click to collapse
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?

nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
Click to expand...
Click to collapse
You have to download the normal phone apk from apkmirror or some other site and use adb to sideload it. Google sideloading apps to Wear, should work the same for any watch. Otherwise you can buy Apps2Wear on the play store. I have done that because its more convenient.

Ok, went through the whole process, is there a way to check root access using ADB?

You should have KingRoot app installed on your watch. That will tell you if you have root. I imagine you could try to pull some files from /system or something that would normally not be accessible. I wouldn't recommend writing to system yet. I soft bricked by watch just by pasting a modified build.prop over the original, trying to turn off low bit depth ambient mode.

Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.

nethead72 said:
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
Click to expand...
Click to collapse
Make sure you have adb debugging and adb bluetooth debugging enabled on watch. Make sure you have usb adb debugging turn on on phone. Then make sure you have bluetooth debugging turn on in Wear app. Make sure you do these in that order because the toggle in the wear app wont show up unless you have debugging enabled on phone first.

This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.

nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
Click to expand...
Click to collapse
Sorry, they are .img. They were pulled using Flashify. The extension must have been stripped when I uploaded them to Drive.

nethead72 said:
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
Click to expand...
Click to collapse
Sometimes it fails once and works when you retry. Not sure why.

hecksagon said:
Sometimes it fails once and works when you retry. Not sure why.
Click to expand...
Click to collapse
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.

nethead72 said:
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
Click to expand...
Click to collapse
Maybe 10-15 mins when I did.

hecksagon said:
Maybe 10-15 mins when I did.
Click to expand...
Click to collapse
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.

nethead72 said:
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
Click to expand...
Click to collapse
Did you confirm the apk was good? I'd try installing it on your phone. I don't think KingRoot has file management capabilities.
On a side note, I would advise against uninstalling anything. I just went to flash the previous OTA and it failed because I didn't have Jawbone installed.

[Q] can someone please help??

I've just got a LG G4 after owning a G3 for ages.
It's LG G4 H815 UK.
I'm trying to unlock bootloader and root + install recovery.
It was easy on G3....but i'm having HUGE problems with the G4.
All the steps in the how to guide from here, go well, until I attempt to get device ID.
It just keeps coming up with the same old errors as you can see below.
Please, help me out...i've literally been trying for the last 3 hours non stop...lol.Hey, i'll even send a donation to beer money if somebody can pleeeeeezzz help me out.:good:
**********************************************
C:\adb\LG Root>adb.exe devices
List of devices attached
C:\adb\LG Root>adb.exe devices
List of devices attached
LGH8159460c7f1 device
C:\adb\LG Root>adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh
/data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
2958 KB/s (1048328 bytes in 0.346s)
1137 KB/s (9319 bytes in 0.008s)
3711 KB/s (4017098 bytes in 1.057s)
C:\adb\LG Root>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
Couldn't open the port \\.\COM4
C:\adb\LG Root>Send_Command.exe \\.\COM5
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#id
FAIL
#
FAIL
#^C
C:\adb\LG Root>id
'id' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>#ID
'#ID' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>#id
'#id' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=552
96 count=529920 of=/dev/block/mmcblk0
'dd' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-Supe
rSU-v2.46.zip /data/local/tmp/busybox
'sh' is not recognized as an internal or external command,
operable program or batch file.
C:\adb\LG Root>
*******************************************
Many thanks
Matt

Your port is closed, please check device manager>port and instead of com4 that being request why send command on com5?

Not entirely sure what you mean?
When I click on ports.bat in my adb folder it says it sees the device on port 5.
I'm lost.....please help:crying:

Here's another screenshot with it showing port 4....but still it fails to get the ID of the phone to enter into LG website to get code.

I get to this point in the screenshot below, where i have to enter "id" but nothing happens...just a blinking cursor when i enter id and press enter.
Any ideas?
thanks
Matt

fails on the last line....

matthew33 said:
fails on the last line....
Click to expand...
Click to collapse
Hi buddy are you using the right com port because you need to choose the diag1 com port not the other one , also ignore what it says in device manager just use the com port from the lg root tool which is diag1... And one last thing are you on marshmallow or lollipop??

matthew33 said:
fails on the last line....
Click to expand...
Click to collapse
try this
Code:
Send_Command.exe \\.\COM4

Xceeder said:
Hi buddy are you using the right com port because you need to choose the diag1 com port not the other one , also ignore what it says in device manager just use the com port from the lg root tool which is diag1... And one last thing are you on marshmallow or lollipop??
Click to expand...
Click to collapse
I'm using diag1 and am using the com port from lg root tool.
My phone has Android 6.0 installed.
Any ideas?
thanks
Matt

This is the latest error i got....

I get to the point where i see
"Type "id" and press enter (no quotes)."
But when I type in the word "id" on the next line comes up the word "Fail"
wtf??

matthew33 said:
I get to the point where i see
"Type "id" and press enter (no quotes)."
But when I type in the word "id" on the next line comes up the word "Fail"
wtf??
Click to expand...
Click to collapse
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
---------- Post added at 10:18 AM ---------- Previous post was at 10:12 AM ----------
Xceeder said:
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
Click to expand...
Click to collapse
Can i just ask which version of MM are you on is it 20a , 20b , 20c etc ?? You can find out this information by going into settings/about phone/software info/software version...

Xceeder said:
You are doing it the wrong way , if you are on MM then you just unlock your bootloader then flash a pre rooted kernel i will find the links for you in a few minutes
---------- Post added at 10:18 AM ---------- Previous post was at 10:12 AM ----------
Can i just ask which version of MM are you on is it 20a , 20b , 20c etc ?? You can find out this information by going into settings/about phone/software info/software version...
Click to expand...
Click to collapse
Thanks mate...really would appreciate it if you could find the links.
Below is screenshot of my phone info:
free uploader

matthew33 said:
Thanks mate...really would appreciate it if you could find the links.
Below is screenshot of my phone info:
free uploader
Click to expand...
Click to collapse
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
---------- Post added at 12:14 PM ---------- Previous post was at 12:03 PM ----------
Xceeder said:
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
Click to expand...
Click to collapse
Right if you haven't already flashed twrp then do that first then download the file on this page and flash it in recovery
https://download.chainfire.eu/696/supersu/
If you need help to install twrp just quote my post , this method should work ....
---------- Post added at 12:27 PM ---------- Previous post was at 12:14 PM ----------
P.s if this method does not work then just flash this kernel in recovery
https://www.androidfilehost.com/?w=files&flid=46800
Flash the 1.4.7 version...

Xceeder said:
Okay you are on 20g the links that i had are for a b c and d so just give a few minutes while i find the right link for your software version , back soon ...
---------- Post added at 12:14 PM ---------- Previous post was at 12:03 PM ----------
Right if you haven't already flashed twrp then do that first then download the file on this page and flash it in recovery
https://download.chainfire.eu/696/supersu/
If you need help to install twrp just quote my post , this method should work ....
---------- Post added at 12:27 PM ---------- Previous post was at 12:14 PM ----------
P.s if this method does not work then just flash this kernel in recovery
https://www.androidfilehost.com/?w=files&flid=46800
Flash the 1.4.7 version...
Click to expand...
Click to collapse
Thnaks for taking the time to help me mate....I really genuinely appreciate it.
If you could tell me exactly how to flash TWRP etc, it would be super appreciated.
I can't enter recovery on my phone.
thanks
Matt

Download twrp 3.0.2.0 and save it in the same place as your adb files , then open a command window by holding shift and right mouse click and do these commands -
adb devices
(This will check if the device is connected you should see a number next to device)
adb reboot bootloader
(This simply reboots your phone ready to flash)
fastboot flash recovery twrp-3.0.2-0-h815.img
(Make sure the twrp name is the same as the command)
Hit enter and you should have twrp installed on your device...

Xceeder said:
Download twrp 3.0.2.0 and save it in the same place as your adb files , then open a command window by holding shift and right mouse click and do these commands -
adb devices
(This will check if the device is connected you should see a number next to device)
adb reboot bootloader
(This simply reboots your phone ready to flash)
fastboot flash recovery twrp-3.0.2-0-h815.img
(Make sure the twrp name is the same as the command)
Hit enter and you should have twrp installed on your device...
Click to expand...
Click to collapse
Done exactly what you said, and this is what i got...see screenshot.....
imageupload

matthew33 said:
Done exactly what you said, and this is what i got...see screenshot.....
imageupload
Click to expand...
Click to collapse
Go to the settings of your phone and press on build number around 8 times until it says you are a developer then enable USB debugging and tick the box that says enable OEM unlock and try again , also make sure when you connect the phone to the PC select mtp connection for USB ...

Xceeder said:
Go to the settings of your phone and press on build number around 8 times until it says you are a developer then enable USB debugging and tick the box that says enable OEM unlock and try again , also make sure when you connect the phone to the PC select mtp connection for USB ...
Click to expand...
Click to collapse
Well, I'm getting somewhere....after hours of trying i've definitely 100% unlocked the bootloader.
BUT, how do i install TWRP and superuser plus how do i boot into recovery?
thanks
Matt

I tried to reboot into recovery using adb fastboot command reboot recovery.....it renooted to a black screen with a green android laying down with, i think a red mark??
Any ideas?
thanks
Matt

Is it possible to put Android OS on Nvidia Shield?

I read an article on cnx-software that said that it is possible to install an unofficial version of Android OS on Nvidia Shield. It said: "It’s also running Android TV by default, which limits the number of apps in the play store. It’s however possibly to install a full (unofficial) version of Android."
I'm not much into gaming but if i can get Android TV, Netflix 4K and others plus Android OS to me that is a deal!
How do i learn more about this? Does it work? Is it hard to do? Does it void the warranty?
Thanks!

jacobpressures said:
I read an article on cnx-software that said that it is possible to install an unofficial version of Android OS on Nvidia Shield. It said: "It’s also running Android TV by default, which limits the number of apps in the play store. It’s however possibly to install a full (unofficial) version of Android."
I'm not much into gaming but if i can get Android TV, Netflix 4K and others plus Android OS to me that is a deal!
How do i learn more about this? Does it work? Is it hard to do? Does it void the warranty?
Thanks!
Click to expand...
Click to collapse
Yes, but your bootloader must be unlocked.
Andrid 6:
http://www.videomap.it/forum/viewtopic.php?t=1580
Android 7:
http://www.videomap.it/forum/viewtopic.php?t=1646

Thanks for the reply. I'm going to check this out!

Is it difficult to put on the shield? I've been searching on the internet and YouTube but haven't found a how to video or at least a reliable one, just videos of people showcasing that they had it. Please help? Thanks in advance.

Yes a good tutorial YouTube video would be greatly appreciated
Sent from my SM-G935F using Tapatalk

jeffery225 said:
Is it difficult to put on the shield? I've been searching on the internet and YouTube but haven't found a how to video or at least a reliable one, just videos of people showcasing that they had it. Please help? Thanks in advance.
Click to expand...
Click to collapse
First you have to know which android version you currently have (android 6 or 7?) And which nvidia shield tv you used (2015 or 2017? 16GB? 500GB?)
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
pn56137 said:
Yes a good tutorial YouTube video would be greatly appreciated
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=LQaYb4oVHVc&feature=youtu.be

I have the 2017 16GB version, I'll have to check to answer the other question though
---------- Post added at 10:37 AM ---------- Previous post was at 10:26 AM ----------
I have the 2017 16GB version, I'll have to check to answer the other question though

jeffery225 said:
I have the 2017 16GB version, I'll have to check to answer the other question though
---------- Post added at 10:37 AM ---------- Previous post was at 10:26 AM ----------
I have the 2017 16GB version, I'll have to check to answer the other question though
Click to expand...
Click to collapse
OK, then you have Android 7? Nvidia Update 5.1?
A Tutorial is here: http://www.videomap.it/forum/viewtopic.php?t=1646

I believe that I updated to the latest OS on there, and thanks. I think I've seen this before but I'll try to follow all the same. Thank you.
---------- Post added at 02:39 PM ---------- Previous post was at 02:18 PM ----------
Is there a simpler tutorial or can you give a simple step by step process cause the link you gave, while I am grateful, it's kinda intimidating and confusing a bit.

I I'll write you a new tutorial

Thanks so much I will try this today when I get off from work.

jeffery225 said:
Thanks so much I will try this today when I get off from work.
Click to expand...
Click to collapse
I hope this tutorial helps you, since my English is not so good. : D
I assume no liability for damage to the device
I tested it myself and it worked.
I have written this guide only for the Shield 2017 16GB with the Shield Update 5.1 (at your own risk, to test it with other versions!)
If the console is not recognized correctly on the PC, please apply this: https://forum.xda-developers.com/sh...status-faq-t3542005/post70773842#post70773842
All games and apps are deleted so make a backup!
1. On the Shield, go to Settings-Info and then scroll down to the point Build and press 7 times up. There should be a message where you are now a developer. Go back to the settings and go to developer options. Enable developer options and enable USB debugging
1.1 Go to the page: http://www.videomap.it/forum/viewtopic.php?t=1646
2. Download the ROM: https://goo.gl/l4y33q
***Driver: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
***Minimum ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
***TWRP: https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544
***SuperSU: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
You need a USB 3.0 A Male to A Male Cable to connect the Shield with the PC
3. Install the driver and minimum ADB and Fastboot
4. Next, put your SHIELD into fastboot mode using following method:
Controller method:
Connect SHIELD Controller using USB cable
Use USB port near HDMI port for PC connection ( You need a USB 3.0 A Male to A Male Cable to connect the Shield with the PC)
Hold Button-A and Button-on SHIELD Controller and then insert power adapter to SHIELD
5. Wait until you see Fastboot menu on HDMI display
Use X / Y to navigate
Use A to select
6. Go to C / Program Files and find the folder Minimal ADB and Fastboot and open it.
7. Extract the ROM, extract TWRP and copy the SuperSu.zip file into it. (System.img, vendor.img, recovery.img and SuperSU.zip)
8. Next you have to unlock the bootloader. Open Minimal ADB and Fastboot and press Shift and right-click and then open Command Prompt here.
8.1 Write in the command prompt this: fastboot oem unlock.
- When the bootloader is unlocked, In the command prompt type:
1) fastboot flash system system.img
2) fastboot flash vendor vendor.img
3) fastboot flash recovery recovery.img
4) fastboot boot recovery.img -> to boot TWRP recovery and flash SuperSu package. You need a regular mouse.
4.1) Go to Wipe and make a Factory Reset.
5) In TWRP go to: Advanced >> ADB sideload and swipe to enable sideload mode
6) adb sideload supersu_package_name.zip (You must flash the zip via TWRP, go to Install and select the zip)
7) Reboot system

Yeah I'm going to take my time and go step by step, how long did it take you to do it?

jeffery225 said:
Yeah I'm going to take my time and go step by step, how long did it take you to do it?
Click to expand...
Click to collapse
30 - 45 minutes

Ok thanks it's a bit confusing but I think I got it

jeffery225 said:
Ok thanks it's a bit confusing but I think I got it
Click to expand...
Click to collapse
I'm sorry, I've tried to explain this step by step, but my English is not so good!

LM209 said:
I I'll write you a new tutorial
Click to expand...
Click to collapse
LM209 said:
I'm sorry, I've tried to explain this step by step, but my English is not so good!
Click to expand...
Click to collapse
Nah, it's cool, I'm just going to read over everything a couple more times before I'm confident in trying it. I did try to start downloading some of the stuff, I tried to get the Nougat but it was taking too long and then it stopped. I got the second and third pieces but haven't tried the fourth and fifth things yet. I'm also about to get a USB male to male cable in a bit and try again.

LM209 said:
I hope this tutorial helps you, since my English is not so good. : D
I assume no liability for damage to the device
I tested it myself and it worked.
I have written this guide only for the Shield 2017 16GB with the Shield Update 5.1 (at your own risk, to test it with other versions!)
If the console is not recognized correctly on the PC, please apply this: https://forum.xda-developers.com/sh...status-faq-t3542005/post70773842#post70773842
All games and apps are deleted so make a backup!
1. On the Shield, go to Settings-Info and then scroll down to the point Build and press 7 times up. There should be a message where you are now a developer. Go back to the settings and go to developer options. Enable developer options and enable USB debugging
1.1 Go to the page: http://www.videomap.it/forum/viewtopic.php?t=1646
2. Download the ROM: https://goo.gl/l4y33q
***Driver: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
***Minimum ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
***TWRP: https://forum.xda-developers.com/shield-tv/development/recovery-twrp-shield-android-tv-2017-t3545544
***SuperSU: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
You need a USB 3.0 A Male to A Male Cable to connect the Shield with the PC
3. Install the driver and minimum ADB and Fastboot
4. Next, put your SHIELD into fastboot mode using following method:
Controller method:
Connect SHIELD Controller using USB cable
Use USB port near HDMI port for PC connection ( You need a USB 3.0 A Male to A Male Cable to connect the Shield with the PC)
Hold Button-A and Button-on SHIELD Controller and then insert power adapter to SHIELD
5. Wait until you see Fastboot menu on HDMI display
Use X / Y to navigate
Use A to select
6. Go to C / Program Files and find the folder Minimal ADB and Fastboot and open it.
7. Extract the ROM, extract TWRP and copy the SuperSu.zip file into it. (System.img, vendor.img, recovery.img and SuperSU.zip)
8. Next you have to unlock the bootloader. Open Minimal ADB and Fastboot and press Shift and right-click and then open Command Prompt here.
8.1 Write in the command prompt this: fastboot oem unlock.
- When the bootloader is unlocked, In the command prompt type:
1) fastboot flash system system.img
2) fastboot flash vendor vendor.img
3) fastboot flash recovery recovery.img
4) fastboot boot recovery.img -> to boot TWRP recovery and flash SuperSu package. You need a regular mouse.
4.1) Go to Wipe and make a Factory Reset.
5) In TWRP go to: Advanced >> ADB sideload and swipe to enable sideload mode
6) adb sideload supersu_package_name.zip (You must flash the zip via TWRP, go to Install and select the zip)
7) Reboot system
Click to expand...
Click to collapse
Is this for the 2017 shield or the 2015? I have the 2015 one.
Sent from my SM-G935F using Tapatalk

pn56137 said:
Is this for the 2017 shield or the 2015? I have the 2015 one.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
For the 2017 Version, but i can create a tutorial for you.

Sorry I'll answer my own stupid question
2017
Sent from my SM-G935F using Tapatalk

June update help.

Hello, so I am currently rooted on the January update and decided to update to June's update and reroot.
I downloaded the official full image and tried to flash it using the flash-all command. But I am getting this error I MOST be doing something working. Any ideas or a quick guide on how to update and root June's update !?
Thank you

jblanko6 said:
Hello, so I am currently rooted on the January update and decided to update to June's update and reroot.
I downloaded the official full image and tried to flash it using the flash-all command. But I am getting this error I MOST be doing something working. Any ideas or a quick guide on how to update and root June's update !?
Thank you
Click to expand...
Click to collapse
Did you extract the files first from the factory image and place them in your SDK/platform-tools folder?

Badger50 said:
Did you extract the files first from the factory image and place them in your SDK/platform-tools folder?
Click to expand...
Click to collapse
Yes sir

jblanko6 said:
Yes sir
Click to expand...
Click to collapse
Are you using minimal adb?

Badger50 said:
Are you using minimal adb?
Click to expand...
Click to collapse
I am not sure ...
Trying with poweshell and still not getting it to work .ugh.
I was trying to flash the bootloader to both partitions and getting this .

jblanko6 said:
I am not sure ...
Trying with poweshell and still not getting it to work .ugh.
I was trying to flash the bootloader to both partitions and getting this .
Click to expand...
Click to collapse
Looks like you are using sdk/platform-tools. Are you also using a Mac laptop?

Badger50 said:
Looks like you are using sdk/platform-tools. Are you also using a Mac laptop?
Click to expand...
Click to collapse
No , windows 10 .
I know the device is being detected in fastboot mood by the computer. It might be something to do with how I am currently rooted. Most "how to " instructions only talk about partitions _a and _b.

Put a space between bootloader and C:\

bradputt said:
Put a space between bootloader and C:\
Click to expand...
Click to collapse
I agree error in syntax

jblanko6 said:
I am not sure ...
Trying with poweshell and still not getting it to work .ugh.
I was trying to flash the bootloader to both partitions and getting this .
Click to expand...
Click to collapse
there's no such fastboot command "flash_other", you don't have to flash bootloader to both partition.

use googles release of sdk not the entire thing
fastboot flash-all
and bam

You can also go straight to your platform-tools folder and double click the flash-all.bat file to start the installation :good:

Badger50 said:
You can also go straight to your platform-tools folder and double click the flash-all.bat file to start the installation :good:
Click to expand...
Click to collapse
Set it all up on a different computer at work. And still can't flash it. I was using flash-all command

jblanko6 said:
Set it all up on a different computer at work. And still can't flash it. I was using flash-all command
Click to expand...
Click to collapse
Do you have all the files you extracted from the factory image inside the platform-tools folder?? Especially the large secondary zip that has all the images?

jblanko6 said:
Set it all up on a different computer at work. And still can't flash it. I was using flash-all command
Click to expand...
Click to collapse
If still no luck, download this from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Download another copy of June update in case first was corrupt.
Place all Tools files plus unzipped June update files into one folder. Make sure your usb cable is an oem Pixel cable.
Use Windows command prompt instead of Powershell. Type fastboot devices with phone connected in fastboot mode.
If you get a serial number, double click on flash-all.bat. It oughta run fine.

Okay so i have doing this fine but i can't seem to update as well
I use window latest platform tools all files in one directory where i open the cmd
Here is what it says @Badger50
Sent from my Google Pixel 2 XL using XDA Labs

michaelbsheldon said:
If still no luck, download this from Google: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Download another copy of June update in case first was corrupt.
Place all Tools files plus unzipped June update files into one folder. Make sure your usb cable is an oem Pixel cable.
Use Windows command prompt instead of Powershell. Type fastboot devices with phone connected in fastboot mode.
If you get a serial number, double click on flash-all.bat. It oughta run fine.
Click to expand...
Click to collapse
If you can look above post i am doing everything right i guess
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
If you can look above post i am doing everything right i guess
Click to expand...
Click to collapse
It sure looks right, and I know you've done this before. What happens when you shut the phone off and then enter bootloader manually. I know it shouldn't matter, but what the heck. That's exactly what I do every month, I never boot into fastboot from the OS and adb ?

Badger50 said:
It sure looks right, and I know you've done this before. What happens when you shut the phone off and then enter bootloader manually. I know it shouldn't matter, but what the heck. That's exactly what I do every month, I never boot into fastboot from the OS and adb ?
Click to expand...
Click to collapse
I'll try it out and let you know stay put ?
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
I'll try it out and let you know stay put ?
Click to expand...
Click to collapse
I'll be here :good::good: