Note: the “sudo” is required if you are running your Linux system as a user. For Mac, you will have to start with:įor Linux, you will have to start commands with:
To use fastboot.zip, simply unzip and you will find fastboot.exe and adb.exe for Windows.įor Mac or Linux, you will have to change the file permissions first by typing:
If you are using Chromebook, you can also get the adb tools thru the Chrome Web Store here.Īlso, drivers are NOT required on Mac or Linux systems as they are included in the OS but if you are using Windows, you will need to use Android USB drivers, which are compatible with all Android devices and works on all Windows XP, 7, 8, and 11.ĭownload Android USB driver for Windows – Link These are taken straight from Android SDK so it will save you time. The Fastboot.zip included here just provides exactly that, fastboot and adb tools you need and there are 3 different versions of it, Windows, Mac, and Linux so you can use it for all 3 different platforms in one download.
But for rooting, you do not need to download the whole Android SDK, which can take up a lot of space on your hard disk and you just need fastboot and adb tools, which are less than 5MB.
Normally, fastboot and adb tools are included as part of Android SDK, which is a complete development tool for Android developers. If root access is required, you can change ro.secure=0 in build.If you need to root your Android smartphone or tablet, you will most likely need to use fastboot and adb tools(except Samsung devices which use ODIN). Now place the RSA-Key somewhere on the phone and merge it into adb_keys adb push "C:\Users\Admin\.android\adbkey.pub" /tmp/adbkey.pubĬat /tmp/adbkey.pub > /data/misc/adb/adb_keys if you don't want to modify /system you can try to push it /data/local.prop (but i guess it is not supported on this rom) or do create a file /data/property/ (i don't have exactly read this posts above) adb push "C:\Users\Admin\Downloads\platform_tools\build.prop" /system/build.prop Mount /system writeable, then push it back to phone. Pull the /system/build.prop and edit the following lines with Notepad++ (make a copy for backup) =1 (but also the other methods you linked above should work) If you need to enable usb-debugging from recovery, you may modify /system.
try another twrp version (3.1.1-0) depending on your android version adb pull /tmp/recovery.log C:\Users\Admin\Downloads\platform_tools\recovery.log post the log file in the twrp support thread and ask for help. if any error occurs, you can pull the log from adb at any time. if phone is still not booting, reboot into twrp and format data. if not, you still have to option to backup/wipe partitions from twrp. In twrp, there is a option reboot recovery which should you bring to recovery mode. Do not flash TWRP to recovery partition, first backup stock recovery! fastboot boot twrp-3.3.1-0-shieldtablet.img data is encrypted but should be mountable too. at least /system and /cache should be mountable, otherwise something is wrong. Then boot TWRP and see if partitions can be mounted. check with fastboot if the serialno appears. Enter fastboot mode from bootloader screen. Unlocking will factory reset your tablet.
you can unlock it from fastboot and try again.
If device is locked you may not be able to enter recovery. When the android symbol appears, press Vol Up + Power to enter recovery. Now navigate to recovery with Vol Keys, Power to confirm. you can enter recovery without usb debugging. I've tried these links, here and here but they seem to require USB debugging enabled or ability to access recovery mode from fastboot.Īdb and fastboot are different modes. Note: For devices released in 2015 or later, use the. Now issue the following command to relock the bootloader. Type in ‘Fastboot devices’ and confirm that your device is being recognized by your system.
I've just been researching the past few nights and trying to find a solution. Now that your device has booted into the recovery mode, connect it to your PC and open Command Prompt in the ADB directory for your system. Sorry in advance for mixing up terms etc. I'm pretty confident I have the correct drivers installed on my windows PC, which is connected to the tablet via USB.Īny help is appreciated at this point, I can't think of anything else to try. When trying to access through a platform-tools terminal, it doesn't show in a list of adb devices. Therefore, I can't perform an unlock using adb, and so can't flash a recovery image. However, the bootloader is locked and I'm pretty sure USB debugging was not enabled ahead of time. I am trying to get a recovery image on the tablet. Nvidia support says it is a 'soft-brick', as I can't get into recovery mode from fastboot. After powering down it hangs on the nvidia boot up screen when I try to boot it up. I have a Nvidia Shield Tablet that froze on me.