[TOOL]ADB + Fastboot v1.0.31 for OS X/4.3 [NOW Includes ADB & Fastboot][08-17-2013]
ADB & FASTBOOT FOR OS X
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
For any new OS X users I'll add a how to just so you don't have to go search for it else where:
How to setup ADB + Fastboot on OS X
Note: This is for not for developers. This only includes ADB & Fastboot and is not the full Android SDK
Step 1: Download the ZIP containing ADB & Fastboot
Step 2: Extract the ZIP to the directory of your choice
Step 3: Optional Create an environment variable
1. Open Terminal
2. Type cd to take you to your home directory.
Code:
cd
3. Type touch .profile to create a hidden file in your home directory named .profile
Code:
touch .profile
4. Type open -e .profile to open the file you just created in TextEdit
Code:
open -e .profile
5. In the file, add the following:
Code:
export PATH=${PATH}:/PathToDirectoryWhereYouExtractedTheZIP
6. Save the file and close TextEdit, quit Terminal, and relaunch the Terminal
Step 4: In Terminal type adb devices, you should see your phone's corresponding serial number Ex: HXM1005HNF012345 device
Code:
adb devices
Note: If you choose not to create an environment variable from Step 3 it effects two things:
1. You will need to cd to the directory containing ADB each time you want to run ADB.
2. When executing ADB commands you will need to add ./ in front of ADB. Ex: ./adb devices
Dropbox Download
Alternate Download
still getting v1.029
wad3g said:
There has been some confusion since I discuss using Fastboot in this post, but the zip only contained ADB. This is completely my fault and I apologize. Either way I've updated the .zip to include ADB & Fastboot.
UPDATED: 08/17/2013 - Added Fastboot to adb-1.0.31-mac.zip
I've seen several people having issues on OS X trying to use ADB since the release of Android 4.3. In my case ADB recognized my device, but each time I ran adb devices my device would be reported as offline. I downloaded the SDK from Google several times and always ended up with ADB v1.0.29 (4.2.2).
This will should solve your OS X & ADB issues if you're running Android 4.3. This ONLY includes the ADB & Fastboot executable files and is for Mac OS X ONLY. I, like many others, do not need the full SDK. If you're not an app developer, like myself, this is all you need to have ADB working on your machine.
Click to expand...
Click to collapse
would you please assist?
Firstly let me apologise If I've posted this thread in the incorrect place, I only joined XDA moments ago & I'm still struggling to navigate my way around.
I know there has already been similar posts to mine on XDA as I've worn out the search button on google trying to find a solution to my problem, with no avail. So I thought I would leave a description of my own situation and see if a more tech-savvy individual could kindly help me out...
So yesterday I decided it would be a good idea to unlock my bootloader & root my device simply because I wanted to remove all the bloatware which HTC 'generously' crammed into the One X. Unlocking the bootloader was simple enough following the instructions provided. However, rooting my handset was not so effortless. The root was ineffective & I got stuck with yet another unwanted app called SuperSU! (An error message regarding missing binary codes appeared every time I tried to open the application) I tried uninstalling via both settings & google play before finally factory resetting my phone. None of these methods worked
At this point it suddenly dawned on me someone so unenlightened in the art of software development or anything android related shouldn't being toying with stuff he can't afford to break! But I figured it was too late to turn back now and continued in my moment of intellectual darkness...
In my bewildered state I accidentally 'wiped system' using CWM and now I have no iOS. My HTC will only boot until the 'quietly brilliant' slogan appear's & no further. When I connect my phone to my computer via USB I can not access the removable storage device, a removable disk appears but when clicked I am prompted to 'insert removable disk'. I am lead to believe from reading related threads that if I had access to my phones storage then installing a new iOS would be relatively straight forward. Also trying to mount in CWM just retrieves an error message reading 'CWM unable to open ums lunfile (no such directory exists)'. Where do I go from here?
Sorry for my long-winded post! I just wanted you guys to know exactly where I'm at. I would really appreciate any helpful advice which could possibly correct this idiotic error of mine.
ADB Site load
Step by step guide:
ADB: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 - WINDOWS ONLY IF MAC PLEASE ASK
ROM:http://forum.xda-developers.com/showthread.php?t=2753450
push to sd card via adb
1)place rom into adb/fastboot folder
2)boot to recovery
3)open cmd,check connectivity:
adb devices
(should return serial number)
4)push rom to sd card:
adb push romname.zip /sdcard/ (where romname is your actual zip file name)
5)you should then be able to simply wipe and flash the rom as you normally would.
*if you can find a nandroid for your particular build,you should be able to push that,with:
adb push nandroidname /sdcard/clockworkmod/backup/nandroidname/
(again,using cw. ill update if i can determine this to work for twrp)
be patient,the nandroid is a big file,so this will take some time.
2)install from adb sideload
1)place rom into adb/fastboot folder
2)boot to recovery
3)open cmd,check for connectivity
adb devices
(should return serial number)
4)select "install from sideload" from the recovery menu
5)in cmd,enter:
adb sideload romname.zip (where romname is your actual rom's name)
you should see it installing on the phones screen
Hope it helps
Hi Jorandobnl, thanks for your reply.
I am using windows 7 & already have the android sdk bundle which I grabbed online when unlocking & attempting to root my device. It would of been great if I had the link you provided at the time as it was such a large download for the purpose of 4 files (fastboot, adb, adbwinapi & adbwinusbapi). Please let me know if I'm missing any other adb required files and I will download them.
So here's where im at...
I followed your instructions step 1 - 3 & my fastboot folder now contains root, fastboot, AdbWinApi.dll, AdbWinUsbApi.dll, adb & crDroid.zip
When typing 'C:\fastboot>adb devices' the cmd prompt returns with:
C:\fastboot>adb devices
List of devices attached
Even though the cmd prompt didn't list any adb devices I continued to the next step anyway & here's what was returned:
Code:
C:\fastboot>adb push crDroid-4.4.4-20141106-OFFICIAL-endeavoru.zip/sdcard/
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\fastboot>
'crDroid-4.4.4-20141106-OFFICIAL-endeavoru.zip' is the name of the ROM file which you kindly provided
When my handset is attached to my PC via USB I receive a different command prompt:
Code:
C:\fastboot>adb devices
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
C:\fastboot>
When I use the cmd code 'C:\fastboot>fastboot devices' It returns:
C:\fastboot>fastboot devices
HT244W103055 fastboot
I'm not sure whether this has any relevance but I would like to give you as much detail as possible.
To quickly summarise the steps which I took so you can check if I am doing anything wrong (which is more than likely)
Firstly I downloaded the ROM (crDroid) & placed it in my fastboot folder along with the adb files I already have. I connected my phone to my computer and started bootloader mode, then I clicked 'recovery' which loaded CWM. I proceeded to check for adb devices which unfortunately returned with nothing. I attempted 'step 4' regardless which returned the cmd code I copy and pasted for you above (for obvious reasons I could not complete step 5).
Your alternative method I have not tried yet because I neither know what nandroid nor sideload means (I must sound like im either 90, amish or stupid )
Any further help you could give me would be very much appreciated & hopefully I can find a way to fix this soon :fingers-crossed:
Once again I apologise on behalf of my technologically illiterate brain!
Update:
I checked out what sideload & nandroid are & attempted to fix my device through your 2nd method, sadly I bumped into more problems...
I located the correct nandroid build for my handset (which took way longer to find than I had hoped)
My computer still won't recognise any adb devices, I've downloaded at least 3 additional adb.exe files today to confirm that the one I downloaded with the android sdk bundle wasn't out dated. I've also killed all adb.exe processes via task manager & tried running it again in case one was interfering with the other... Still nothing
I then read in a separate thread that maybe the drivers were outdated? I couldn't check for driver updates using the traditional device manager route so I downloaded drivers online but still my PC wouldn't show any adb devices. Although I doubt out dated drivers are the problem as I updated them recently when I unlocked & attempted to root my HTC.
Again I ignored this and continued with your steps anyway, then I encountered my next problem. CWM doesn't seem to have a sideload feature... I understand its supposed to be located in the 'install zip from sdcard' section right? The options I have are as follows:
choose zip from sdcard
apply/sdcard/update.zip
toggle signature verification
toggle scripts asserts
I have checked every option on CWM & sideload is nowhere to be found! I am using CWM v5.8.1.8
Maybe the reason my PC can't find an adb device is because there is no removable disk showing when I plug in my phone using USB? When I use fastbootUSB my computer plays the normal sound to show it has recognised a device but nothing is showing in removable storage.
I've wasted my whole day trying to fix this problem. Surely there has to be a way...
have the same problem same rom.... hope answer will come out.
tried it too and nothing Works... have win 8.1
Hi everyone. I am experiencing problems trying to flash RR Nougat to my Oneplus 3, currently on CM13 6.0.1. It just won't flash at all. I've wiped cache etc but it doesn't want to execute. I've also tried Lineage OS but failed, I have even tried pushing the file via Unified Android Toolkit and even that didn't work. Phone has an unlocked boot-loader (I'm pretty sure) USB debugging, root access etc. Unsure what the issue is so any help would be appreciated. This is what happened whilst using UAT.
Working out the best location to set for Internal Storage..
Waiting for Adb Mode
Device mode detected [device adb]
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for sdcard
Setting push location to mnt/sdcard and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /mnt/sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for mnt/sdcard
Setting push location to storage/emulated/0 and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /storage/emulated/0/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
An Error Occured
The file did not push to the set location for some reason
Please report this in your device thread with details for more help
Press any key to return to the Main Menu..
Thank You.
I don't really have an answer for you but recently I tried to go back to stock, after I locked my bootloader I was unable to sideload anything with adb, have you tried flashing it with TWRP? Just a suggestion, are you able to use recovery at all, if uat can't find the directory, it could be a PC issue? I'm just throwing out ideas to try to help.
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Make sure you are on the latest firmware that is required.
I would just transfer through mtp or download on your op3, then just flash trough TWRP. That's what I do.
sv2203 said:
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Click to expand...
Click to collapse
Yup follow his method. This issue is somekind of adb sideload bug for huge files, name too long or not run as admin. Restarting PC, reinstall driver OP3 driver is another option if problem still persists.
(Note before you begin: If you have a SHIELD TV 2017, you will need a quality Male-to-Male USB Type A cable to connect your SHIELD TV to a PC. If you have a SHIELD TV 2015 or a SHIELD TV Pro, you may be able to just use a regular micro USB cable, because those two models have a micro USB port)
A. Download these files to your PC:
Download the Android SDK Platform-Tools
Download the Official NVIDIA SHIELD family Windows USB Drivers
Download the Magisk Manager APK (This is the latest version as of the time of writing)
Download the ***CORRECT*** NVIDIA SHIELD Experience Upgrade v7.2 Image for your model
(You will need to register for a Developer Account if you don't already have one. Flashing the wrong image will BRICK your device)
B. Setting up Android SDK Platform-Tools on your PC:
On your PC, extract the Android SDK Platform-Tools somewhere where you can find them
Add the platform-tools folder to PATH in the Windows System Environment Variables (Instructions HERE or HERE)
C. Installing the Official NVIDIA SHIELD family Windows USB Drivers on your PC:
On your SHIELD TV, enable developer options and debugging (Instructions HERE)
Using a Male-to-Male USB Type-A Cable, connect the USB port further away from the HDMI port on your SHIELD TV to your PC
On your PC, extract the Official NVIDIA SHIELD family Windows USB Drivers somewhere where you can find them
Open Device Manager and find the new device
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
adb devices
On your SHIELD TV, a prompt will pop up asking you to allow ADB access from your computer. Check the box to remember your selection and then Grant Access
On your PC, the Command Prompt should show the serial number of your SHIELD TV
(You may have to run the 'adb devices' command again since it may have timed out the first time waiting on you to authorize the ADB connection on the SHIELD TV)
Boot the SHIELD TV into bootloader/fastboot mode by typing the command:
Code:
adb reboot bootloader
(Alternatively, you can enter bootloader/fastboot mode by following the instructions HERE)
On your PC, open the Device Manager again and find the new device (it will probably have an error with a yellow triangle)
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one NOT relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
fastboot devices
The Command Prompt should show the serial number of your SHIELD TV
D. Unlocking the bootloader on your SHIELD TV (CAUTION: THIS WILL WIPE YOUR DATA AND FACTORY RESET YOUR SHIELD TV)
Plug the NVIDIA SHIELD TV Game Controller or a USB Keyboard into the USB port closest to the HDMI port on your SHIELD TV
In bootloader/fastboot mode on your SHIELD TV, select "Unlock Bootloader", read the message and confirm
(Use the Y and X buttons to scroll UP and DOWN, and the A button to CONFIRM selection, if your button presses aren't doing anything you need to reboot the SHIELD TV into bootloader/fastboot mode with the Controller or Keyboard already plugged in)
On your PC, open a Command Prompt and reboot your SHIELD TV to the OS by typing:
Code:
fastboot reboot
This process only needs to be done once per device and you will not have to unlock the bootloader again for subsequent updates
(From now on while your bootloader is unlocked, your SHIELD TV will display a warning message when it first boots saying that the system cannot check for corruption. This is perfectly normal and the boot process will resume automatically after a few seconds. There is no need to relock your bootloader unless you are selling the device or something. NEVER lock the bootloader if you have anything other than 100% stock full RECOVERY Image installed. Never even try it.)
E. Installing Magisk Manager on your SHIELD TV and Patching your boot.img
On your PC, extract the NVIDIA SHIELD Experience Upgrade v7.2 Image that you downloaded to somewhere where you can find it
Find the boot.img file in the folder that you extracted it to
Open a Command Prompt and type:
Code:
adb push boot.img /storage/emulated/0/Download/
Install Magisk Manager by typing 'adb install [path-to-magiskmanagerapk]' example:
Code:
adb install C:\MagiskManager-v6.1.0.apk
On your SHIELD TV, open Magisk Manager [Settings > Device > Apps > Magisk Manager > Open]
(The Magisk Manager App Interface is not designed to be operated with an Android TV Remote so I suggest you install the NVIDIA SHIELD TV app on your phone. Once paired with your SHIELD TV, the app has an option to let you use a virtual mouse to navigate and interact with your SHIELD TV. Alternatively, you can plug a USB Mouse into the USB port closest to the HDMI port on your SHIELD TV)
If Magisk Manager automatically pops up and asks you if you would like to Install Magisk, select Cancel
Make sure the "Preserve AVB 2.0/dm-verity" option is checked, and then select "Install"
Select "Patch Boot Image File"
Using the Virtual Mouse on the NVIDIA SHIELD TV remote app on your phone, or a USB Mouse, navigate to the "Download" folder on your internal storage and select the boot.img file that you copied over then click Open
Magisk Manager will take a few moments to patch the boot.img (pay attention to the message in the console about the path to the patched_boot.img - It should be "/storage/emulated/0/Download/patched_boot.img"
On your PC, in the Command Prompt type:
Code:
adb pull /storage/emulated/0/Download/patched_boot.img
F. Installing Magisk rooted SHIELD Experience Upgrade v7.2 on your SHIELD TV:
On your PC, navigate to the folder where you extracted the NVIDIA SHIELD Experience Upgrade v7.2 Image
Find the boot.img and rename it to boot.img.bak
Rename the patched_boot.img to boot.img
Open a Command Prompt and type:
Code:
adb reboot bootloader
Once the SHIELD TV is in bootloader/fastboot mode, type:
Code:
flash-all.bat
(It will take a few minutes for the flashing process to finish and then the SHIELD TV will automatically reboot to the OS)
Optional Stuff and Additional Information:
Disable Auto-Upgrades by going to [Settings > Device > About > System upgrade > Auto-upgrade]
Enable Full OTA's instead of Partial/Differential by going to [Settings > Preferences > Developer options > Provide full system upgrades]
(It is the very last option at the bottom and this is very important when using a rooted device and modifications to the System partition are likely)
If you want to upgrade to a new OTA update with root without waiting on NVIDIA to post the Developer/Recovery images, the downloaded OTA file is in
Code:
/data/data/com.nvidia.ota/app_download
(You will need a root file explorer to be able to access this directory)
You can extract the boot.img from the OTA zip and patch it using the same method described in step E.5 through E.10
You can then install the OTA the normal way [Settings > Device > About > System upgrade > Check for upgrade]
(Make sure you have copied the OTA zip or extracted the boot.img to somewhere on your Internal Storage like "/storage/emulated/0/Download" BEFORE you install the OTA because the system will delete the file in "/data/data/com.nvidia.ota/app_download" when it installs the update and you will be unable to get it after that)
Copy the patched_boot.img that you made with Magisk to your PC
Reboot to bootloader/fastboot mode with:
Code:
adb reboot bootloader
Manually flash just the Magisk Patched boot:
Code:
fastboot flash boot patched_boot.img
Manually reboot back to the OS with:
Code:
fastboot reboot
Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.
whiteak said:
Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.
Click to expand...
Click to collapse
I don't modify the system partition if I can avoid it. I just disable System Apps if I want them gone; however, I am fully confident that I could delete anything in /system if I wanted to. Is /system mounted as +rw? Not all Root File Managers are created equal. I recommend Root Explorer. It is not the most modern and feature rich file manager, but when it comes to Root File Managers specifically, I haven't found any other that can compare.
Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.
whiteak said:
Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.
Click to expand...
Click to collapse
I would test it for you if I had a system.img for v7.2.1 that I could reflash real quick. I just don't feel like flashing v7.2.0 then updating to v7.2.1 again to restore an unmodified system partition.
ACiDxCHRiST said:
A. Download these files to your PC:
Download the Android SDK Platform-Tools HERE
Download the Official NVIDIA SHIELD family Windows USB Drivers HERE
Download Magisk Manager APK (Link to latest version at time of writing is HERE)
Download the ***CORRECT*** NVIDIA SHIELD Experience Upgrade v7.2 Image for your model HERE
(Flashing the wrong boot.img will BRICK your device You will need to register for a Developer Account if you don't already have one)
B. Setting up Android SDK Platform-Tools on your PC:
On your PC, extract the Android SDK Platform-Tools somewhere where you can find them
Add the platform-tools folder to PATH in the Windows System Environment Variables (Instructions HERE)
C. Installing the Official NVIDIA SHIELD family Windows USB Drivers on your PC:
On your SHIELD TV, enable developer options and debugging (Instructions HERE)
Using a Male Type-A to Male Type-A USB Cable, connect the USB port further away from the HDMI port on your SHIELD TV to your PC
On your PC, extract the Official NVIDIA SHIELD family Windows USB Drivers somewhere where you can find them
Open Device Manager and find the new device
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
adb devices
On your SHIELD TV, a prompt will pop up asking you to allow ADB access from your computer. Check the box to remember your selection and then Grant Access
On your PC, the Command Prompt should show the serial number of your SHIELD TV
(You may have to run the 'adb devices' command again since it may have timed out the first time waiting on you to authorize the ADB connection on the SHIELD TV)
Boot the SHIELD TV into bootloader/fastboot mode by typing the command:
Code:
adb reboot bootloader
(Alternatively, you can enter bootloader/fastboot mode by following the instructions HERE)
On your PC, open the Device Manager again and find the new device (it will probably have an error with a yellow triangle)
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one NOT relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
fastboot devices
The Command Prompt should show the serial number of your SHIELD TV
D. Unlocking the bootloader on your SHIELD TV (WARNING: THIS WILL WIPE YOUR DATA AND FACTORY RESET YOUR SHIELD TV)
Plug the NVIDIA SHIELD TV Game Controller or a USB Keyboard into the USB port closest to the HDMI port on your SHIELD TV
In bootloader/fastboot mode on your SHIELD TV, select "Unlock Bootloader", read the message and confirm
(Use the Y and X buttons to scroll UP and DOWN, and the A button to confirm selection, if your button presses aren't doing anything you need to reboot the SHIELD TV into bootloader/fastboot mode with the Controller or Keyboard already plugged in)
On your PC, open a Command Prompt and reboot your SHIELD TV to the OS by typing:
Code:
fastboot reboot
E. Installing Magisk Manager on your SHIELD TV and Patching your boot.img
On your PC, extract the NVIDIA SHIELD Experience Upgrade v7.2 Image that you downloaded to somewhere where you can find it
Find the boot.img file in the folder that you extracted it to
Open a Command Prompt and type:
Code:
adb push boot.img /storage/emulated/0/Download/
Install Magisk Manager by typing 'adb install [path-to-Magisk-Manager-APK]' example:
Code:
adb install C:\MagiskManager-v6.1.0.apk
On your SHIELD TV, open Magisk Manager [Settings > Device > Apps > Magisk Manager > Open]
(The Magisk Manager App Interface is not designed to be operated with an Android TV Remote so I suggest you install the NVIDIA SHIELD TV app on your phone. Once paired with your SHIELD TV, the app has an option to let you use a virtual mouse to navigate and interact with apps on your SHIELD TV. Alternatively, you can plug in a USB Mouse into the USB port closest to the HDMI port on your SHIELD TV)
If Magisk Manager automatically pops up and asks you if you would like to Install Magisk, select Cancel
Make sure the "Preserve AVB 2.0/dm-verity" option is checked, and then select "Install"
Select "Patch Boot Image File"
Using the Virtual Mouse on the NVIDIA SHIELD TV remote app on your phone, or a USB Mouse, navigate to the "Download" folder on your internal storage and select the boot.img file that you copied over then click Open
Magisk Manager will take a few moments to patch the boot.img (pay attention to the message in the console about the path to the patched_boot.img - It should be "/storage/emulated/0/Download/patched_boot.img"
On your PC, in the Command Prompt type:
Code:
adb pull /storage/emulated/0/Download/patched_boot.img
F. Installing Magisk rooted SHIELD Experience Upgrade v7.2 on your SHIELD TV:
On your PC, navigate to the folder where you extracted the NVIDIA SHIELD Experience Upgrade v7.2 Image
Find the boot.img and rename it to boot.img.bak
Rename the patched_boot.img to boot.img
Open a Command Prompt and type:
Code:
adb reboot bootloader
Once the SHIELD TV is in bootloader/fastboot mode, type:
Code:
flash-all.bat
(It will take a few minutes for the flashing process to finish and then the SHIELD TV will automatically reboot to the OS)
Optional Stuff and Additional Information:
Disable Auto-Upgrades by going to [Settings > Device > About > System upgrade > Auto-upgrade]
Enable Full OTA's instead of Partial/Differential by going to [Settings > Preferences > Developer options > Provide full system upgrades]
(It is the very last option at the bottom and this is very important when using a rooted device and modifications to the System partition are likely)
If you want to upgrade to a new OTA update with root without waiting on NVIDIA to post the Developer/Recovery images, the downloaded OTA file is in
Code:
/data/data/com.nvidia.ota/app_download
(You will need a root file explorer to be able to access this directory)
You can extract the boot.img from the OTA zip and patch it using the same method described in step E.5 through E.10
You can then install the OTA the normal way [Settings > Device > About > System upgrade > Check for upgrade]
(Make sure you have copied the OTA zip or extracted the boot.img to somewhere on your Internal Storage like "/storage/emulated/0/Download" before you install the OTA because the system will delete the file in "/data/data/com.nvidia.ota/app_download" when it installs the update and you will be unable to get it after that)
Copy the patched_boot.img that you made with Magisk to your PC
Reboot to bootloader/fastboot mode with:
Code:
adb reboot bootloader
Manually flash just the Magisk Patched boot:
Code:
fastboot flash boot patched_boot.img
Manually reboot back to the OS with:
Code:
fastboot reboot
Click to expand...
Click to collapse
Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 10.295s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.641s
< waiting for any device >
sconnyuk said:
Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 10.295s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.641s
< waiting for any device >
Click to expand...
Click to collapse
Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0
If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.
Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.
ACiDxCHRiST said:
Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0
If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.
Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.
Click to expand...
Click to collapse
I have 2017 Shield TV 16gb, which is on stock 7.2.1
I am using platform tools you suggested previously.
im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.
Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?
Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it. Also i can adb push/pull/install no problems.
I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.
Im running out of ideas to be honest, quite the nightmare im having.
sconnyuk said:
I have 2017 Shield TV 16gb, which is on stock 7.2.1
I am using platform tools you suggested previously.
im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.
Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?
Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it.
I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.
Im running out of ideas to be honest, quite the nightmare im having.
Click to expand...
Click to collapse
I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.
Also try running with an elevated Command Prompt with admin rights.
ACiDxCHRiST said:
I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.
Also try running with an elevated Command Prompt with admin rights.
Click to expand...
Click to collapse
Yes i always use admin rights with CMD.
I will try re locking and unlocking again later today. (i cant see how nobody else has had issues like mine)
Thanks, il report back.
---------- Post added at 09:00 AM ---------- Previous post was at 08:36 AM ----------
Just tried re locking my bootloader then unlocking again and get same output:
Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 6.297s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.853s
< waiting for any device >
sconnyuk said:
Just tried re locking my bootloader then unlocking again and get same output:
Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 6.297s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.853s
< waiting for any device >
Click to expand...
Click to collapse
I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.
ACiDxCHRiST said:
I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.
Click to expand...
Click to collapse
Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.
As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.
I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.
I'll be in touch. ?
sconnyuk said:
Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.
As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.
I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.
I'll be in touch.
Click to expand...
Click to collapse
Here is the cable that I use: https://www.amazon.com/Cable-Matters-2-Pack-Male-Black/dp/B00HSS9IDW
Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time
Thanks for all your help.
Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.
sconnyuk said:
Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time
Thanks for all your help.
Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.
Click to expand...
Click to collapse
Awesome
ACiDxCHRiST said:
Awesome
Click to expand...
Click to collapse
So from a virgin 7.2.1 we can after all flash a modded boot ??.
Just have to wait for a TWRP that is working on 7.2.1 now.
Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.
I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.
sconnyuk said:
So from a virgin 7.2.1 we can after all flash a modded boot .
Just have to wait for a TWRP that is working on 7.2.1 now.
Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.
I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.
Click to expand...
Click to collapse
What do you need TWRP for?
Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.
I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?
Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?
ACiDxCHRiST said:
What do you need TWRP for?
Click to expand...
Click to collapse
Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.
Also if any magisk/xposed modules make my box not boot to restore also ??
nadia p. said:
Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.
I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?
Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?
Click to expand...
Click to collapse
The SHIELD TV will only force you to update when you are going through the Initial Setup after a data wipe. If you follow the guide exactly as written and your bootloader is not unlocked yet, you will be forced to update to v7.2.1 after unlocking the bootloader. But since there aren't any more data wipes and the last step is to flash the v7.2.0 image that we modified, you will end up on v7.2.0 without being forced to do the Initial Setup again. In fact, you could likely use the same steps in the guide to install other versions.
As for what Magisk patches, it modifies the bootloader to trick the OS into thinking that the SU binary is in the system partition without actually modifying the system partition.
sconnyuk said:
Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.
Also if any magisk/xposed modules make my box not boot to restore also
Click to expand...
Click to collapse
Roger that, makes sense.