Database Info

[Q] Fastboot Missing from Android SDK

It appears (and this has been verified by multiple installs by myself and people on #android and #android-dev on freenode) that fastboot has been removed from the R14 release of the Android SDK.
Does anyone know how to get fastboot via another method so I can unlock the boot loader of my Nexus S (my platform is Windows 7 SP1 X64)?
Thank you in advance.

I think I found the answer to my own question:
http://dl.google.com/android/android-sdk_r13-windows.zip

I don't think it's been a part of the Android SDK, at least for a while. I've always had to manually download the binary.

It can also be made in your build environment. Command: make fastboot. It will create the binary.

where to put that command? thx

Here's fastboot.exe: http://www.mediafire.com/?wrgw1erxw71o77a
geo741 said:
where to put that command? thx
Click to expand...
Click to collapse
You have to place it in the same folder containing adb.exe (platform-tools for the last sdk).

[Q] Noob Root Walkthru

I am new to the ASUS family of tablets, and j just can't figure out how to root. I have rooted many tablets and installed custom roms before but the i cannot follow the how tos listed here. For one fastboot doesnt work on my computer. It opens and closes immediately. What i would like is a detailed step by step guide with a trouble shooting guide. I mean now i reading about downgrading, blob files and a few other things i never dealt with on my galaxy. Someone help......would love to root this thing. Email me if u want [email protected]

You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?

Check this thread, it has videos about rooting and whatnot, hope it helps:
http://forum.xda-developers.com/showthread.php?t=1663244

Northern-Loop said:
You need to run fastboot from the DOS Prompt
start run - cmd
then type fastboot command.
I take it you have unlocked your bootloader?
Click to expand...
Click to collapse
Yes, Bootloader is unlocked. Ok, so I tried the flashboot command, so now what? I typed the command from the walkthru "fastboot -i 0x0B05 flash recovery recovery.img " but get an errorcannot load recovery.img. So what am I missing. I have the recovery image on my desktop.....

Put the recovery image in the same folder as your fastboot application and it should work.

xAshxMoneyx said:
Put the recovery image in the same folder as your fastboot application and it should work.
Click to expand...
Click to collapse
....what fastboot folder? I installed the ADK per the instructions, I downloaded the root and recovery image. I looked in the system for a fastboot folder and do not see it. Plus when I try to type in the fastboot command now, it says it is not a recognized command. I am sure this is something simple, but I am just not getting it. Is there a more detailed step by step somewhere that will actually walk you thru the steps without assuming you know what they are talking about? I can root my phone, my galaxy tab all day long and install and change ROMS, but this one has me upside down.

When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.

xAshxMoneyx said:
When you installed android SDK and ran SDK manager to install the tools, it should create a "platform tools" folder. In that folder you should see "fastboot.exe." Put the recovery image into the same platform tools folder.
Make sure when you run the command that you are in the command prompt, and that you have navigated to the same platform tools folder. It should then recognize the fastboot command and flash your recovery.
Click to expand...
Click to collapse
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.

That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.

xAshxMoneyx said:
That file should be in your platform tools folder as well. I think it's a driver issue. Is your tablet showing up in device manager? Does it have a yellow triangle? I'm not really an expert unfortunately, hopefully someone with more knowledge can jump in.
Click to expand...
Click to collapse
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......

tccc143 said:
So I think I am going to delete everything and start from scratch. This shouldn't be this difficult. Here we go......
Click to expand...
Click to collapse
Ok, so reinstalled everything.....did a quick refresher on CMD directions and had it rooted with CWM in 10 minutes. I have been working in Android so long without the use of a PC that I forgot how to use the PC. Thanks for the help....now we wait for some nice roms.

Sweet, glad you got it, I've done this stuff a few times but I always have to refresh myself and take it slow on each different device.

tccc143 said:
Found the folder and it did have the platform tools in it but Apparently I have forgotten how to navigate in CMD, so I moved the folder to the current location CMD was at. I typed in the command fromt the walkthrough and I get "adbwinapi.dll" is not installed. Not sure if this is progress or not.....so now what.
Click to expand...
Click to collapse
You should not move the folder. This can cause all kinds of problems. in the cmd prompt just type
cd \folder\folder\etc.
The cd means change directory and you start off with a backslash to set the initial path to the root of your drive. if folder names include spaces then wrap the path with quotes, cd "\folder one\folder two\etc". the prompt should change from C:\windows or whatever to what you typed in.
if you've installed on a drive other than C: then first change to that drive by typing the drive letter followed by a colon, ie D:
Good old DOS will never die.
Sent from my SCH-I510 using XDA

Bootloader unlock

Not needed..............

@jmz will this work on OS 4.5.2

krazyace35 said:
@jmz will this work on OS 4.5.2
Click to expand...
Click to collapse
I don't see why it wouldn't as I am on 4.5.3 and it worked.

jmz said:
I don't see why it wouldn't as I am on 4.5.3 and it worked.
Click to expand...
Click to collapse
Cool thanks I'll give it a try and thanks for this unlock tutorial

jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.

ryanyz10 said:
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.
Click to expand...
Click to collapse
do steps 1 through 6 in this thread
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311

Question
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol

ryanyz10 said:
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol
Click to expand...
Click to collapse
if on windows you need to get python installed

jmz said:
if on windows you need to get python installed
Click to expand...
Click to collapse
I've got python 3.4.2 installed. Which version would you recommend?
After some researching, people have said that python doesn't work very well on Windows 10, which is what I'm on right now.

jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !

edouble312 said:
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !
Click to expand...
Click to collapse
sorry, with that tool you only get the unlock.img . I need to correct the post

In my linux box 'cuber' module, required by cublock.py, is not installed; is this the correct source? https://github.com/benesch/cuber
One more question: I forgot to block OTA update so my HD6 updated to 4.5.4, loosing root permissions. What I should do? Need to wait KingRoot supports the new software version or can I proceed to unlock bootloader and install twrp? Or could install, if available, a 4.5.3 recovery through dd? Very thanks.

I sense many roms being ported very soon...

Sure hope so!

I used the tools (cuber) in this post:
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689

So i generated unlock.img, but i am still unable to enter fastboot mode,
i tried changing boot to 4002, i rooted and tried to execute fastboot file, nothing works tbh, how do you suppose i fix this?
thanks in advance

robert896 said:
So i generated unlock.img, but i am still unable to enter fastboot mode,
Click to expand...
Click to collapse
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.

DoLooper said:
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.
Click to expand...
Click to collapse
ok im on ubuntu 15.04 got full adb and fastboot (they work on other devices) --- fire os 4.4.3---device model, kfhd 3rd gen
i also have windows 7 x64 dual booted with full adb and fastboot set up also
when i do adb reboot-bootloader, it restarts but doesnt enter fastboot ,, it boots into normal mode

robert896 said:
device model, kfhd 3rd gen
Click to expand...
Click to collapse
These unlock instructions are for Fire HDs (4th gen). You need a fastboot cable for KFSOWI. Try G+ KFSOWI modding.

I am new to the tablet scene. This is my very first tablet. I would like to root the device and install custom recovery and hopefully custom Rom. Is this the first thing I do or should I start somewhere else?

Can't boot or flash TWRP from MacOS ADB. Can't find file...

Hi,
I successfully unlocked my bootloader and the MacOS ADB can still see my device.
However, I have the TWRP files and Magisk downloaded and ready to go on the Mac (and on my phone) but the ADB commands won't work. Fastboot boot or Fastboot flash...
It's my girlfriends Mac and I'm not familiar with MacOS at all. Am I doing something obvious wrong..??? Any ideas please??

the.Great.Skua said:
Hi,
I successfully unlocked my bootloader and the MacOS ADB can still see my device.
However, I have the TWRP files and Magisk downloaded and ready to go on the Mac (and on my phone) but the ADB commands won't work. Fastboot boot or Fastboot flash...
It's my girlfriends Mac and I'm not familiar with MacOS at all. Am I doing something obvious wrong..??? Any ideas please??
Click to expand...
Click to collapse
cant find file?
Seems like youre in the wrong folder. Try to navigate to your download folder with the command cd
You can also send pictures in here

You have to open a Terminal window in the same folder where you have adb and fastboot.
Also, on OSX, the commands have to be preceded by ./
For example:
./adb devices
./fastboot boot twrp.img

Done it thank you.
I did the 'cd' command.
Then dragged the img. file from Finder to the terminal window. Then put the 'fastboot boot' command in front of that. It worked obviously.
I was unfamiliar with the file location name. This seems an easy way for someone that doesn't have a clue like me. ??

Debian/Ubuntu/Mint Linux and Moto X4

Personally, after Windows 8, followed by Windows 10, I started to seriously look into Linux (which is free) as my primary desktop. Today LibreOffice (which is free) has more features than Microsoft Office and can open, edit, and save all of Microsoft Office's documents. Thanks to Steam's new deployment, I can even now run my Windows-only games on Linux too. The one thing I found very hard to swallow was trying to get my Andriod device (which is technically Unix too) to actually connect to my computer and I imagine that is because the documentation (even via a Google search) to using ADB or Fast Boot with Linux seems to be hidden among pages upon pages of Windows users.
For simple ease of reference as I couldn't even find this here on XDA, allow me to correct the matter.
Type out (or copy and paste) the following commands to install ADB and Fastboot.
Code:
sudo apt-get install adb
sudo apt-get install fastboot
Now you have both adb and fastboot installed. Next, you'll need to enable adb.
Code:
sudo adb
Now boot your phone to your bootloader screen (you get there by pressing both your power and lower volume keys at the same time). Once there load TWRP with the following command.
Code:
sudo fastboot boot '/your_path_here/twrp-3.2.3-0-payton.img'
Your path will be wherever you happen to have downloaded your copy of TWRP. From there I was able to successfully mount my device within TWRP and upload my ROM zip file as needed.
You will upload files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push lineage-16.0-20180921-UNOFFICIAL-payton.zip /sdcard/
I hope this was helpful.

Note: Because you're doing this in Linux, the files you upload to your phone may not have the correct permission settings (chmod settings) after they are uploaded. This is very unlikely, but still technically possible.
Thankfully, the folks at TWRP have thought of this and in the 'Advanced' menu, you will find a file manager. From there select the file of your choice and click the chmod button that reads "chmod 0777". Don't forget to mount the DATA partition (before using the file manager) else you may not see the file you are looking for.

or just download the package from here
https://developer.android.com/studio/releases/platform-tools
unzip and have fun

munchy_cool said:
or just download the package from here
https://developer.android.com/studio/releases/platform-tools
unzip and have fun
Click to expand...
Click to collapse
This is helpful, but most newbies to Linux wouldn't even know how to execute those base files. lol But Windows users coming to Linux do know how to run command prompts (good old Microsoft kept the command prompt around long enough that folks moving to Linux just associate the terminal in the same light). Which is why I thought to have them install a preconfigured program would be easier.
But thanks for the source. It is still useful.

MotoX4 said:
This is helpful, but most newbies to Linux wouldn't even know how to execute those base files. lol But Windows users coming to Linux do know how to run command prompts (good old Microsoft kept the command prompt around long enough that folks moving to Linux just associate the terminal in the same light). Which is why I thought to have them install a preconfigured program would be easier.
But thanks for the source. It is still useful.
Click to expand...
Click to collapse
lol..i thought the first thing a Linux newbie would learn is command prompt.
you need to read about terminal before you decide using a Linux box.

munchy_cool said:
lol.. I thought the first thing a Linux newbie would learn is the command prompt.
you need to read about terminal before you decide using a Linux box.
Click to expand...
Click to collapse
:laugh: I agree. But there are a lot of folks who feel intimidated whenever learning something new. If I had started this thread with a full introduction to manually configuring and executing everything, most folks would have easily been discouraged. Especially the younger or older generations who fall somewhere between the line of "I don't got time for that" or "why so difficult". lol :laugh: Inoculating folks into using Linux I feel works best. Keep it simple and suggest that there are more in-depth ways of doing things to peak curiosity. -- Which is why I'm glad you pointed that out and why I'm loving writing this reply at the moment. :angel: