Develop Bugs

[HOWTO] Install Google SDK and ADB drivers in Windows 7

I'm posting this guide because my Galaxy Nexus I9250 I purchased from Google Play would not to recognize in any way, shape or form the official Google drivers provided into Android SDK. Obviously, if you installed any Samsung drivers, you will have to uninstall them. Personally, I always connect the device to my PC and let Windows Update find the best driver. In this way, the basic Windows interface is handled by Microsoft drivers:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google SDK 64bits Setup
This is a quick howto for those who actually want to setup their SDK properly in Windows 7 64bits. I saw a lot of craziness on the Internet so I wanted to share how I set a proper 64bits development environment.
Android SDK: http://developer.android.com/sdk/ (installer_r21-windows.exe)
Java JDK: http://www.oracle.com/technetwork/java/javase/downloads/ (jdk-7u5-windows-x64.exe)
Eclipse Classic: http://www.eclipse.org/downloads/ (eclipse-SDK-4.2-win32-x86_64.zip)
First, download the 64bits software versions, not 32bits. Android SDK is the only 32bits package but it will work fine with 64bits development tools, if you know what you are doing. Obviously, if you are on a 32bits OS download the 32bits software versions. We are discussing a 64bits setup, so let's move on.
Install Java JDK and only if you run a 64bits OS, set a JAVA_HOME variable with value "%ProgramFiles%\Java\jdk1.7.0_05" into Environment Variables (adjust the value with whatever version you downloaded):
Reboot your PC to enable all the settings done above.
Next, install Android SDK. You only need to download Android SDK Tools, Android SDK Platform-tools and Google USB Driver, if you just want to play with the phone. If you plan to develop apps, install also the API of your choice and Eclipse Classic (yes, that is the recommended version by Google devs).
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Now, on with the fun part. There are 2 drivers needed for Google Nexus, the Composite ADB and Bootloader (Android 1.0).
Android Composite ADB Interface Driver
First, enable USB Debugging in your phone:
Plug your USB cable, you will notice in Device Manager the failed driver notice:
Right-click on it and select "Update Driver Software...", then "Browse my computer for driver software". Don't bother browsing to your ADB USB driver location, it will not install the proper driver. Instead, click on "Let me pick from a list of device drivers on my computer" button:
Make sure "Show All Devices" is selected and click on Next button:
With the list of devices displayed, click on Have Disk button:
Browse to your Google Driver location, mines is set in "C:\Program Files (x86)\Android\sdk\extras\google\usb_driver":
Pick the "Android Composite ADB Interface" driver and click on Next button:
You will be asked to accept the driver installation, do it and be done with this part of drivers setup:
Android Bootloader Interface Driver
Make sure USB Debugging is still enabled in your phone. With the USB cable connected, manually boot into Bootloader mode by powering down your phone and restarting it with all 3 buttons pressed (Volume Up + Volume Down + Power). You will notice in Device Manager the new unrecognized Android 1.0 device. Follow the same steps explained above and when you reach the driver selection, choose "Android Bootloader Interface":
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
You are done, enjoy the official USB drivers from Google.

Quick Root Command references
Nexus Images: https://developers.google.com/android/nexus/images#mysid
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
SuperSU: http://download.chainfire.eu/205/SuperSU/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
adb reboot bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Backup Device
Code:
adb backup -apk -shared -all -f backup.ab

TECK said:
Nexus Images: https://developers.google.com/android/nexus/images
CWM: http://www.clockworkmod.com/rommanager/
Superuser: http://hosted.androidsu.com/superuser/
Root Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install Supersuer + Root (match the file names with the ones downloaded):
Code:
adb push Superuser-3.1.3-arm-signed.zip /sdcard/
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
Flash Superuser: On device, select "install zip from sdcard", then "choose zip from sdcard" and select "Superuser-3.1.3-arm-signed.zip". Confirm install, then "+++++Go Back+++++" and "reboot system now".
3) Lock the bootloader (optional):
Code:
adb reboot bootloader
fastboot oem lock
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
Click to expand...
Click to collapse
This is nice I wish this was around 2 weeks earlier when I got this phone this would have made setting up a lot easier. This deserves to be sticky
Sent from my Galaxy Nexus using Tapatalk 2

I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.

TECK said:
I added also a quick Howto for the Android SDK setup in Windows 64bits. Lots of crazy info out there on the Internet so I said might as well post it so others can do it right in their computers.
Click to expand...
Click to collapse
glad i came across this post. I'm going to use your instructions to return my daughter's GSM Galaxy Nexus to stock JB so we can determine if the proximity sensor is bad or if it's due to the other JB ROMs i've put on her phone. right now, the proximity sensor does not turn the screen off when she places the phone to her ear during phone calls.
question: i prefer not to overwrite the CWM recovery, so i'm planning to remove the recovery.img from the image-yakju-jro03c.zip file before updating via fastboot. next i'll reboot to recovery and flash the superuser zip file to gain ROOT access. my question is this: will removing the recovery img cause the update via fastboot to fail? thanks to anyone who replies to my question.

I would simply flash the entire stock image without skipping any files. Then temporarily flash back the CWM, just to keep the phone stock.
Code:
adb reboot bootloader
fastboot boot recovery-clockwork-6.0.1.0-maguro.img
This will not write CWM to the phone, but rather use it once to bypass the stock recovery. Personally, I'm only interested to root the device and will not install custom ROM's. But even if you do install custom ROM's, you rarely need CWM... and if you do, you will work near your computer where you have access to adb.

This is a splendid guide!
Absolutely what all new Androiders need.
Sent from my Transformer TF101 using Tapatalk 2

Did everything you said and got to the point where I was testing those commands, and it says devices attached but my device isnt listed. I was still in boootloader and fastboot usb was attached. is that correct? any ideas? I do have CM9 installed and there are plenty of options regarding root access.

TECK said:
To test the setup, run few basic commands:
Code:
adb devices
adb reboot bootloader
fastboot reboot
Click to expand...
Click to collapse
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
I installed Android SDK and Java SE JDK and it all went well. I installed the drivers and when in fastboot mode, I get "Samsung Galaxy Nexus BootLoader Interface" in Device Manager, which I think is what I should be getting.
Would you know what is it that I am missing? Could it be something that I haven't installed from the Android SDK? Thanks again for the tutorial.

You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
You need to change to the directory in which you installed the SDK
So like:
cd <insert directory here and remove the arrow brackets>
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.

bozint said:
I'll try that, thanks.
His screenshot shows that he is not in the SDK installed folder though.
My phone was in fastboot mode when I tried that. I hope that's the correct mode.
Click to expand...
Click to collapse
That is because you missed this part:
TECK said:
[snip]
To make available everywhere your platform tools (adb, fastboot, etc.), add your platform-tools directory to Path:
Myself, I installed the SDK in "C:\Program Files (x86)\Android\sdk" directory, so my path looks like:
Code:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;%ProgramFiles(x86)%\Android\sdk\platform-tools
Technically, you need to add the ";%ProgramFiles(x86)%\Android\sdk\platform-tools" location at the end of your current path.
Reboot your PC to enable all the settings done above.
Click to expand...
Click to collapse
bozint said:
One more thing, when I choose go to Recovery in fastboot, the red triangle comes up, but Volume Up + Power doesn't do anything and I have to take out the battery in order to reboot.
Click to expand...
Click to collapse
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.

efrant said:
That is because you missed this part
Click to expand...
Click to collapse
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....). It might be the issue, and I will use default path after I uninstall it and then install it again. I also added the Java SE in the Environment Variables.
efrant said:
What you are seeing is the main screen for the stock recovery. To access the menu from that screen, hold power and press volume up.
Click to expand...
Click to collapse
Thanks for this, I got into now. I guess all the time I was holding vol.up and then power.
I am on stock now, so in order to root, should I be following the following procedure?
Stock Device
1) Unlock the bootloader (if locked):
Code:
adb reboot bootloader
fastboot oem unlock
2) Install the image files (match the file names with the ones downloaded).
Commands are listed inside flash-all.sh shell script, validate them:
Code:
fastboot reboot-bootloader
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jro03c.zip
3) Lock the bootloader:
Code:
adb reboot bootloader
fastboot oem lock
My baseband is XXLF1, and the build is JRO03C.I9250WLH2, if this helps in any way.
Thanks for the comment guys, much appreciated.
====================================================
EDIT: @efrant, I just checked your guide on rooting without unlocking the bootloader, so should I fail with the backup you also referenced in you guide, I will give it a try. The phone is rather new though, so even if I lose some apps it's not that big a deal.

bozint said:
[snip]
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.

bozint said:
I did add a line in the Environment Variables, I installed the Android SDK in the root of "C" though (C:\!Android\.....).
Click to expand...
Click to collapse
So the path was not the issue. Originally I had this in Path in the Environment Variables: "....;%!Android%\Google_Dev\android-sdk\platform-tools" and adb did not work unless I went directly inside the platform-tools folder in command prompt.
I then tried to add additional line in Environment Variables for the whole path, without the % symbol (C:\!Android\Google_Dev\android-sdk\platform-tools). And it worked, now adb lists the device at any time and location.
The final line in Path looks like this: ....bunch of lines......;%!Android%\Google_Dev\android-sdk\platform-tools;C:\!Android\Google_Dev\android-sdk\platform-tools

bozint said:
Mate, when I type "adb devices" I am getting an error saying that "'adb' is not recognized as an internal or external command, operable program or batch file"
Click to expand...
Click to collapse
If you add adb to the Windows path, you will not get this error. I explained into tutorial what to do.
Edit: Never mind, efrant explained well what to do.

efrant said:
I think you are confusing a few things. Unlocking the bootloader is not the same as getting root. You should have a look at the "basics" link in my signature.
Click to expand...
Click to collapse
I got it rooted now, but I need to do some additional reading yes. I'll read the guide and hopefully things will be more clear. Thanks guys.

bozint said:
I am on stock now, so in order to root, should I be following the following procedure?
Click to expand...
Click to collapse
No. The tutorial has separate sections, Root Device" and "Stock Device", not "Rooted Device". You want to root, so you follow the "Root" procedure, right?

Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks

Logic_ said:
Does anyone have a separate link to the ADB drivers for windows? I need this pc to recognize my N7 in bootloader etc but I don't want to go through the whole Java SDK etc hassle to get ADB just to get the drivers, it's not my pc.
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1379875

[HOWTO] Use ADB in recovery

Did a quick search and didnt see a comprehensive tutorial on getting this working. It may solves a lot of headaches for a few people. Sure did for me!
Here we go!
1. First reboot your phone to recovery
2. Plug your phone into your computer.
3. You should/might get an error stating that your driver was not installed.
Looks like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Windows 7 cool guys, type "Device manager" into the start menu and open device manager. Everyone else its under control panel
5. You should see an "Other devices" section with "SAMSUNG_Android_SGH_T999" in that seciont
6. Right click the "SAMSUNG_Android_SGH_T999" listing. And select "Update driver"
Should open a window which looks like this. Select the bottom option.
7. Select once again the bottom option.
8. Scroll down to Samsung android device.
9. Then if you show two devices as i do, doesnt matter which one you pick.
10. After clicking next it should do its thing and you should receive a window that looks like
11. Lets run adb devices and see if it worked.
And it does!
Now you can ADB push pull reboot pretty much anything you want. Even adb shell.
When pushing and pulling, i noticed that the internal SD card is mounted as "/data/media" not "/sdcard" or "/storage/sdcard0"
Hope this helps someone! Sure helped me!

Instructions for XP
This is nice but I wasn't able to follow these instructions on XP. When I select the "Don't search. I will choose the driver to install." option, I don't see Samsung Android ADB Interface as one of the options. I do have the driver installed and adb does recognize the device when it's not in recovery mode.

EvilBoz said:
This is nice but I wasn't able to follow these instructions on XP. When I select the "Don't search. I will choose the driver to install." option, I don't see Samsung Android ADB Interface as one of the options. I do have the driver installed and adb does recognize the device when it's not in recovery mode.
Click to expand...
Click to collapse
Holy hell its been forever since I've ran xp.... um let me get on my dads computer and get reminded as to what the driver installation is like.
Sent from my SGH-T999 using Tapatalk 2

Don't worry about it, dude. I used the naked USB driver from this thread and that worked just fine.

hi elesbb i have a galaxy young (gts5360) and was looking to adb while in recovey, i tried to follow your guide but my compurer dont recognizes just one device plugged it recognizes 4, so i do the process for all 4 but it didn't work, can you give a hand? i attached a print screen:
http://i40.tinypic.com/2d6x03.png

I wish I would have seen this yesterday

Is it posible to select Recovery options via ADB?
I have a Supersonic Tablet (a generic Android tablet) I'm trying to make a Hard Reset to it, its locked. When I get into Recovery Mode and select "Wipe data/ Factory reset" i get into the common menu:
No
No
No
No
No
No
No
Yes - Delete all user data
No
No
When I scroll down and put the cursor at here:
No
No
No
No
No
No
No <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<----------------
Yes - Delete all user data
No
No
If I try to Select "Yes - Delete all user data" the cursor goes to the top. Its kind of trickie....
No
No <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<----------------
No
No
No
No
No
Yes - Delete all user data
No
No
So I conect it via ADB and it is recognized as:
"List of devices attached
0123456789ABCDEF recovery"
so I wonder if there is a command on ADB to select the options at recoovery.
Thanks

bullracing said:
Is it posible to select Recovery options via ADB?
I have a Supersonic Tablet (a generic Android tablet) I'm trying to make a Hard Reset to it, its locked. When I get into Recovery Mode and select "Wipe data/ Factory reset" i get into the common menu:
No
No
No
No
No
No
No
Yes - Delete all user data
No
No
When I scroll down and put the cursor at here:
No
No
No
No
No
No
No <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<----------------
Yes - Delete all user data
No
No
If I try to Select "Yes - Delete all user data" the cursor goes to the top. Its kind of trickie....
No
No <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<----------------
No
No
No
No
No
Yes - Delete all user data
No
No
So I conect it via ADB and it is recognized as:
"List of devices attached
0123456789ABCDEF recovery"
so I wonder if there is a command on ADB to select the options at recoovery.
Thanks
Click to expand...
Click to collapse
that is really really weird lol. The only thing I could think of would to use a recovery script but if its stock recovery it probably won't run it. I wonder if they designed it to do that? I'm not sure there is an adb option to wipe data aside from running a shell and executing commands. But that would require root.

I know this tablet it's laughing of me....
I'm looking for something to allow me to active the USB debugging, or kinda trick...
But I hadn't heard nothing like that. Thanks for replying elesbb

Were you able to activate USB debugging under the tablet's settings?

Nop, but in recovery mode, the device is detected well....

bullracing said:
Is it posible to select Recovery options via ADB?
I have a Supersonic Tablet (a generic Android tablet) I'm trying to make a Hard Reset to it, its locked. When I get into Recovery Mode and select "Wipe data/ Factory reset" i get into the common menu:
No
No
No
No
No
No
No
Yes - Delete all user data
No
No
When I scroll down and put the cursor at here:
No
No
No
No
No
No
No <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<----------------
Yes - Delete all user data
No
No
If I try to Select "Yes - Delete all user data" the cursor goes to the top. Its kind of trickie....
No
No <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<----------------
No
No
No
No
No
Yes - Delete all user data
No
No
So I conect it via ADB and it is recognized as:
"List of devices attached
0123456789ABCDEF recovery"
so I wonder if there is a command on ADB to select the options at recoovery.
Thanks
Click to expand...
Click to collapse
You can try fastboot.
Boot into fastboot and then type
fastboot devices
you should see a serial number with fastboot
then type
fastboot erase system -w
or
fastboot erase data
fastboot erase system
fastboot erase cache
Hope this helps!

Use ADB in recovery
Just to add up. .
to run adb shell in recovery, you should not use the USER Binary! Engineering Binary will give you permission!

error
when i type adb shell it gives error adb closed

[Q&A] [GUIDE][ROOT] Smartwatch 3 KNX01V

Q&A for [GUIDE][ROOT] Smartwatch 3 KNX01V
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][ROOT] Smartwatch 3 KNX01V. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

HELP!?
XorZone said:
You have been warned!
Links:
Sony PC Companion
SWR50-rootboot.img@ mega.nz, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?

13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
Sounds like your'e missing the right drivers. I'm sorry I don't have a link right now but it should be somewhere on the OP.

13noninja said:
I've been following directions from here and from the lggw tutorial with no success. I get fast boot running on the watch but after typing "Fastboot oem unlock" the command terminal stays on "waiting for device". Could you help me please?
Click to expand...
Click to collapse
1. Download and install google usb driver: http://developer.android.com/sdk/win-usb.html
2. Check if you have adb driver in place: adb devices, if not - go into Device Manager and force missing driver to be "Android Composite ADB Interface".
To force it "Update Driver" -> "Browse My Computer" -> "Let me pick from a list ..." -> Select "Google, Inc." on left and "Android Composite ADB Interface" on the right.
Verify that you have adb access, by typing "adb devices", if needed confirm connection on the phone
3. Reboot to bootloader by typing "adb reboot bootloader", you should see "Running Fastboot" on watch screen.
4 Check "fastboot devices", you should see device id followed by fastboot word.
If not - go into Device Manager and force missing driver to be "Android Bootloader Interface" by followinf instructions for adb, but make sure to pick "Google, Inc." on left and "Android Bootloader Interface" on the right.
5. Verify fastboot working by executing fastboot devices.
6. Follow guide.

Got It
Thx XorZone and nobunnysapro, i found the missing drivers and got everything running smoothly.

I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Oh and ADB Debugging is on

I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.

Orvils said:
I can't seem to get it working..
I have the drivers and ADB works fine, i can sideload stuff to watch and install apk and everything.
But when I write "adb reboot boatloader" it does just normal reboot. Can't get into fastboot mode.
Click to expand...
Click to collapse
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader

XorZone said:
boatloader? I do not think sony included boat on board... JK
correct one is
Code:
adb reboot bo[B]o[/B]tloader
Click to expand...
Click to collapse
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk

Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Sent from my SM-N910F using Tapatalk
Click to expand...
Click to collapse
1. Are you doing it through USB connection and not over bluetooth?
2. What is your current build number/version in about menu?

Yes I'm doing everything with USB connection.
Build number is KNX01V
Sent from my SM-N910F using Tapatalk

Orvils said:
Sorry, misspelled. But in terminal I am writing everything correctly. Not sure why it doesn't go into fastboot.
Click to expand...
Click to collapse
Always check if adb in general works (may be driver probs in Win):
Code:
adb devices -l
(That's a lowercase L)

A guide for relocking the boot loader? I'm looking to go to lollipop for wear so I'd like to know how to go back to stock.

Fastboot OEM lock, and better reflash using Sony companion before.
I plan to try to get ota as is, then if it'll not work reflash using companion and then if it is still not upgrades I'll relock as last resort.

I have reinstalled Google USB drives over and over again manually and through SDK... When I try to manually point it to the right drivers I don't even get offered the right drivers.. I have google inc. Selected on the left but I dont see android composite or android bootloader interface...help would be much appreciated

Hello, any idea to make it work on lollipop? Thanks!

I have Sony Smartwatch 3 and want to install normal APK via Sideload and USB/PC (do not want to root my smartphone).
Is this possible and which SW i need to install on Windows PC?
Step by step guide (for noobs) would be great. Thanks
Gesendet von meinem SM-T310 mit Tapatalk

ADB can't recognize my Asus Zenfone 2 phone - Please Help!

Sorry, I have checked with many forums, but couldn't find any solution to this problem...
I shall present a detailed step-by-step recollection of events...
1.) I am running Windows 7 (64-bit) on my PC.
2.) I have recently bought an Asus Zenfone 2 (ZE551ML) on 05-July-2015.
Specs: 2.3 GHz, 4 GB RAM, 64 GB in-built memory, Android 5.0 Lollipop.
OEM Firmware no. that the phone came with is: <WW 2.15.40.13_20150506>
3.) The first thing I did upon receiving the phone is to set a password and encrypt the phone (encryption took only 30 seconds or so).
At that time, my phone did NOT have any SIM card or External SD Card.
Phone was also NOT rooted.
4.) Enabled USB Debugging on my Zenfone 2 (in MTP mode).
5.) Downloaded latest updated Firmware from Asus Support Centre: <WW V2.19.40.22> dated 03-07-2015
The firmware is in ZIP format and is stored on my PC's harddrive.
6.) Downloaded "ASUS Android USB Drivers for Windows" v2.0 dated 05-03-2015
7.) Downloaded "Intel USB Driver for Android Devices" v1.9.0 dated 29-Apr-2015
8.) Downloaded latest ADB FastBoot Drivers v1.4.2
9.) Installed the Intel USB Driver (from step-7 above).
10.) Restarted PC.
11.) Went to Windows Device Manager, updated driver from ASUS Android USB drivers (from step-6 above), even though Intel's drivers are more recent.
After installing Asus's own drivers, my Device Manager looks like this (see image):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
12.) Restarted PC.
13.) At this time, Zenfone 2 is connected to Windows via both MTP (Media Files) and PTP (Camera files) modes.
14.) Installed ADB drivers into System-wide Mode (C:\adb) in Windows.
15.) Turned-off the phone and restarted phone in Recovery Mode.
16.) Connected the phone to Windows PC by OEM cable.
17.) On phone's recovery menu, selected "apply update from ADB".
18.) Opened Windows Command Prompt in the ADB folder (C:\adb),
and typed: "adb devices".
19.) This is where I am stuck. The CMD screen looks like this (see image)
20.) After reading some forums, I have switched to PTP Mode in phone's Settings->Storage USB Settings.
But the problem persists. I cannot get ADB running in Windows to detect to my Android phone even after connecting to it.
Can anyone tell what have I missed? If someone knows the solution, please please help me.

Simple straightforward way to update firmware on Asus Zenfone 2 without ADB
GOD SAVE ME!!!
Barely minutes after I had given up on the ADB thing, I have found a way to install firmwares on my Asus Zenfone 2 phone.
Note: The main problem I have outlined in this thread is to be able to install Updated OEM Firmware from ASUS. This is not OTA upgrade, but FULL firmware update.
I shall share my experience on this subject in a step-by-step way:
1.) First, make sure that you can transfer files from your Android phone to Windows via USB cable (install the necessary drivers – see my post above.)
2.) You must also have downloaded the latest firmware in ZIP format from ASUS support page (for links, please refer to my above post).
Rest of the stuff I am paraphrasing from ASUS Support section:
3.) Connect your phone with PC via micro USB cable, and copy the entire ZIP file (firmware) to the root directory of internal storage of phone (see pic below).
4.) After copying is complete, detach the USB cable from the phone.
5.) The notification for firmware update will pop-up on status bar (top-left corner, see pic below):
6.) Pull down the notification bar, and tap "System Update File Detected..." (see pic below).
Follow steps to update firmware.
- Phone may restart several times during update,
- Phone must have min. 15% charge, or best, connect phone to power source while update is on.
7.) After update, I have noticed that:
- Phone encryption is intact and is just like what it was before update,
- But screen UI settings have been completely reset,
- I can't comment on Phonebook / Contacts, because my phone still does NOT have a SIM card.
- My phone is still NOT rooted.
8.) Do remember to delete the original Firmware ZIP file on the root directory of your phone. The file size is huge and the phone does NOT delete it automatically. Besides, once updated, there is no need for the ZIP file, I think.
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy!

But despite the above solution, the fact still remains that the "15 seconds ADB Installer v1.4.2" does not work with Asus Zenfone 2 (as least that is my experience so far).
I am looking for another ADB installer in which, hopefully, my phone will be detected by ADB so that I can root/flash stuff.

xbox-er said:
GOD SAVE ME!!!
Barely minutes after I had given up on the ADB thing, I have found a way to install firmwares on my Asus Zenfone 2 phone.
Note: The main problem I have outlined in this thread is to be able to install Updated OEM Firmware from ASUS. This is not OTA upgrade, but FULL firmware update.
I shall share my experience on this subject in a step-by-step way:
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy!
Click to expand...
Click to collapse
xbox-er said:
But despite the above solution, the fact still remains that the "15 seconds ADB Installer v1.4.2" does not work with Asus Zenfone 2 (as least that is my experience so far).
I am looking for another ADB installer in which, hopefully, my phone will be detected by ADB so that I can root/flash stuff.
Click to expand...
Click to collapse
Seriously this method was there since ages... Nothing new.. And how is it possible that the tool which worked for every android user didnt work for u i didnt even install "ASUS Android USB Drivers for Windows" on my PC just installed "Intel USB Driver for Android Devices" and "15 sec adb installer" and eveything works fine from adb to MTP/PTP... Forget doing "adb devices" command just try this simple command "adb reboot bootloader" ... You will see your phone reboot into bootloader/fastboot mode...if this works it means you have a working adb.... And if you were trying to sideload a file via adb you just had to enter adb sideload "filename" and press enter...Thats it!! no adb devices and all

mhp1995 said:
Forget doing "adb devices" command just try this simple command "adb reboot bootloader" ... You will see your phone reboot into bootloader/fastboot mode...if this works it means you have a working adb.... And if you were trying to sideload a file via adb you just had to enter adb sideload "filename" and press enter...Thats it!! no adb devices and all
Click to expand...
Click to collapse
adb devices is an easy way to detect if adb can see any devices.
If adb devices returns nothing, then no matter what adb commands you enter, nothing will work. You're basically telling him to enter commands while nothing is detected. They'll have no impact.

Harfainx said:
adb devices is an easy way to detect if adb can see any devices.
If adb devices returns nothing, then no matter what adb commands you enter, nothing will work. You're basically telling him to enter commands while nothing is detected. They'll have no impact.
Click to expand...
Click to collapse
I know but sometimes when i also enter adb devices i also dont get anything... But then if i enter adb reboot recovery etc or just sideload the zip file it works...Maybe he has the same problem...

I had this problem this morning, tried three different micro USB cables and the third one worked. The first two would charge but not let the device get detected by ADB.

I have similar issue..adb recognizes my phone...but i can't flash .img onto the phone..when i type fastboot devices my phone doesnot come out next....what can i do?
Sent from my ASUS_Z00AD using Tapatalk

Try this
http://forum.xda-developers.com/showthread.php?p=61528830
OTA links for stock ROM
yemnic said:
I have similar issue..adb recognizes my phone...but i can't flash .img onto the phone..when i type fastboot devices my phone doesnot come out next....what can i do?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
If you're in adb the code is
adb sideload
Not
fastboot sideload
Sent from my ASUS_Z00AD using XDA Free mobile app

Nope..am trying to flash my recovery SKU to WW...cos mine is CN,
Sent from my ASUS_Z00AD using Tapatalk

My zenfon 2 works with adb when its open in android. But it is not recognized in recovery. If i do adb reboot recovery, it works. But when i try adb sideload filename.zip from recovery, it says: device not found!

ione2380 said:
My zenfon 2 works with adb when its open in android. But it is not recognized in recovery. If i do adb reboot recovery, it works. But when i try adb sideload filename.zip from recovery, it says: device not found!
Click to expand...
Click to collapse
did you first select " apply updates from adb " on your phone before " adb sideload filename.zip " from PC command prompt
select " apply updates from adb " on your phone first, then the phone say's give the zip file from your pc command prompt using " adb sideload filename.zip ".... at the time only the sideload code work.

Yes, i did that, of course.

ione2380 said:
Yes, i did that, of course.
Click to expand...
Click to collapse
Nothing new here? i have the very same problem..

I think i found the final soloution.
Download the newest ADB Tool here: http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
(its an old one mentioned in the guide on XDA how to flash Zenfone2)
Also - use the latest Intel (IntelAndroidDrvSetup1.10.0) driver found here: https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Then try again. If you search for devices in ABD (by typing "abd devices") it might still not show your phone, but all the commands will work and you will be able to flash your phone in recovery mode.

Have you found a solution for this? I'm experiencing the same thing on my zenfone 2 (z00ad) on 2.20.40.139. I've tried 4 usb cables and 2 pc's one 64bit win7 and one 32bit win7. Both setup the same way with latest drivers/adb/fastboot and adb system wide installed. This isn't my first android, but it is the first android to leave me stumped with no fastboot/adb access. Also tried with mtp selected, then ptp selected, then none selected. Still the same "Fastboot devices <waiting for devices>" developer mode is enabled with usb debugging enabled

Hi everyone,
Installing only Intel USB Driver won't solve the problem. You should update the driver manually.
Plug in the device in state where you will update the driver from (like on Recovery mode). Open Device Manager, right click on the only driver with exclamation mark and select 'Update Driver Software...'. A new window will appear. Select 'Browse my computer for driver software', and then select 'Let me pick from a list of device drivers on my computer'. Select ADB drivers and then any driver with ASUS ADB name.
The driver will be installed. You can verify if the driver is installed or not by typing adb devices on a Command Prompt window.
Sent from my ASUS_Z00AD

krasCGQ said:
Hi everyone,
Installing only Intel USB Driver won't solve the problem. You should update the driver manually.
Plug in the device in state where you will update the driver from (like on Recovery mode). Open Device Manager, right click on the only driver with exclamation mark and select 'Update Driver Software...'. A new window will appear. Select 'Browse my computer for driver software', and then select 'Let me pick from a list of device drivers on my computer'. Select ADB drivers and then any driver with ASUS ADB name.
The driver will be installed. You can verify if the driver is installed or not by typing adb devices on a Command Prompt window.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
:good::good: WOOOOOOOOORKKKKSSSSS thanks bro, work fine, just update and enjoy ! adb sideload FILENAME.zip enjoy thanks bro!

3.) Connect your phone with PC via micro USB cable, and copy the entire ZIP file (firmware) to the root directory of internal storage of phone (see pic below).
View attachment 3392841
4.) After copying is complete, detach the USB cable from the phone.
5.) The notification for firmware update will pop-up on status bar (top-left corner, see pic below):
View attachment 3392842
6.) Pull down the notification bar, and tap "System Update File Detected..." (see pic below).
Follow steps to update firmware.
- Phone may restart several times during update,
- Phone must have min. 15% charge, or best, connect phone to power source while update is on.
View attachment 3392843
7.) After update, I have noticed that:
- Phone encryption is intact and is just like what it was before update,
- But screen UI settings have been completely reset,
- I can't comment on Phonebook / Contacts, because my phone still does NOT have a SIM card.
- My phone is still NOT rooted.
8.) Do remember to delete the original Firmware ZIP file on the root directory of your phone. The file size is huge and the phone does NOT delete it automatically. Besides, once updated, there is no need for the ZIP file, I think.
So this is a simple (and the official) way to update firmware on an Asus Zenfone 2 without any need for Rooting / ADB and other hacks.
No need to install ADB, no need to Root the phone!
Easy![/QUOTE]
Do you think can work if i want to substitute de cn firmware with ww firmware?

juanpirata said:
:good::good: WOOOOOOOOORKKKKSSSSS thanks bro, work fine, just update and enjoy ! adb sideload FILENAME.zip enjoy thanks bro!
Click to expand...
Click to collapse
Please can you tell me exactly what you did step by step and can you include download links please

HTC Desire 530 Root/S-OFF

Yes, this is very similar jcase's post. His helped me out a lot, but I went more in depth. Here is his post.
http://forum.xda-developers.com/desire-530/help/root-s-off-desire-530-guide-to-root-t3410015
0) Download these files
SuperSu 2.74 - https://download.chainfire.eu/964/Su...0519174328.zip
Universal ADB Driver
Android SDK - https://developer.android.com/studio/index.html
TWRP - https://www.androidfilehost.com/?fid=24588212152304477 (Experimental build)
SunShine - http://theroot.ninja/apks/SunShine-latest.apk (Optional)
1) Visit htcdev.com and unlock your bootloader
-sign up as a dev, activate your email, and follow the steps
2) Download twrp from the app store. You won’t be able to run it yet but you still need it
3) Put the supersu zip file from your computer into your download folder of your phone
4) Get fastboot & adb running on your computer.
- open cmd prompt
-navigate to the fastboot/adb folder in your cmd prompt
-with your phone plugged into your computer type “adb devices”
-if it returns your device good
-now in cmd type “adb reboot downloader” (you can also do this by powering off your phone then turning your phone on by holding the down volume button and the power button at the same time.
-once you are in the downloader type “fastboot devices” in cmd
-if this returns your device good
-DO NOT GO ANY FURTHER TILL THIS IS WORKING!!!
4)Once your phone is in the rebooted downloader screen type “fastboot flash recovery <twrpDownloadFromAbove>”
-make sure you are on the downloader page and not the bootloader page
-this should end in .img
-this is a second boot screen for your phone. The first time I did this recovery wasn’t working because I was trying to fastboot on the bootloader page.
5) Now boot into recovery mode by navigating to it on your phone or using the cmd “adb reboot recovery”
-Once you are here you will see the twrp screen
6a) The way I did it is going into the twrp recovery boot and going to install and choosing the supersu.zip file I moved to my phone in step 3. After it is done reboot your phone and now you are rooted.
6b) The other way is to go to advanced in twrp and enable sideload
-now in cmd type “adb sideload <SuperSuDownloadFromAbove>”
7) If you need to turn S-OFF install sunshine on your phone and it will do it.
-You need to have your phone rooted first to turn your S-OFF with sunshine

Hi, I've been trying to root my phone since a couple of days but I've not been able to do it. I followed your guide as well as jcase one, but the results are the same, I can't boot to recovery mode after flashing the twrp image saying "failed to boot to recovery mood. Press volume up or down to back to menu" when I choose the option from bootloader screen (which is the only place where I can find a "boot recovery" option, and using the cmd command doesn't work.

vistor_sanh said:
Hi, I've been trying to root my phone since a couple of days but I've not been able to do it. I followed your guide as well as jcase one, but the results are the same, I can't boot to recovery mode after flashing the twrp image saying "failed to boot to recovery mood. Press volume up or down to back to menu" when I choose the option from bootloader screen (which is the only place where I can find a "boot recovery" option, and using the cmd command doesn't work.
Click to expand...
Click to collapse
I get this same thing, do yo fix it?

Faviopiano2 said:
I get this same thing, do yo fix it?
Click to expand...
Click to collapse
When you are in the bootloader screen does it say unlocked at the top? Also make sure you've flashed the twrp img to recovery. If it flashes correctly you should see that it starts downloading ok your phone

whittlestick said:
When you are in the bootloader screen does it say unlocked at the top? Also make sure you've flashed the twrp img to recovery. If it flashes correctly you should see that it starts downloading ok your phone
Click to expand...
Click to collapse
Yes its unlocked already, and when finish flashing its ok too

Successful Root!
Thanks I followed all of the instructions and I was able to successfully get Root on my metro pcs HTC Desire 530.
IF YOU ARE HAVING ISSUE with the TWRP.img
- Make sure you have "OEM Unlocking" enabled under developer options in settings since the phone wiped when you unlocked the bootloader it probably unclicked that option and you just have to enable it again.
- Check md5sum of the TWRP image file maybe you have a corrupt file and therefore a bad flash (I use OP link it worked fine).
- When pushing the TWRP image make sure you have a good USB connection.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have a problem flashing the recovery. What is the OP link?
---------- Post added at 12:38 AM ---------- Previous post was at 12:32 AM ----------
matora said:
I have a problem flashing the recovery. What is the OP link?
Click to expand...
Click to collapse
TWRP Official page?
---------- Post added at 01:15 AM ---------- Previous post was at 12:38 AM ----------
izou1838 said:
Thanks I followed all of the instructions and I was able to successfully get Root on my metro pcs HTC Desire 530.
IF YOU ARE HAVING ISSUE with the TWRP.img
- Make sure you have "OEM Unlocking" enabled under developer options in settings since the phone wiped when you unlocked the bootloader it probably unclicked that option and you just have to enable it again.
- Check md5sum of the TWRP image file maybe you have a corrupt file and therefore a bad flash (I use OP link it worked fine).
- When pushing the TWRP image make sure you have a good USB connection.
Click to expand...
Click to collapse
Please, give me the OP link. Thanks

@matora
OP is original post otherwise the link provided.
One thing I did do different is I downloaded and installed "Minimal ADB and Fastboot" and I also installed HTC sync manager prior to flashing the recovery
Hope it helps

izou1838 said:
@matora
OP is original post otherwise the link provided.
One thing I did do different is I downloaded and installed "Minimal ADB and Fastboot" and I also installed HTC sync manager prior to flashing the recovery
Hope it helps
Click to expand...
Click to collapse
From where you install the HTC sync manager and the minimal adb?

Just got this phone an hour ago since my LG-D855 is stuck in download mode so great to see a root tread/method here will try this later
Sent from my HTC Desire 530 using XDA-Developers mobile app

whittlestick said:
Yes, this is very similar jcase's post. His helped me out a lot, but I went more in depth. Here is his post.
http://forum.xda-developers.com/desire-530/help/root-s-off-desire-530-guide-to-root-t3410015
0) Download these files
SuperSu 2.74 - https://download.chainfire.eu/964/Su...0519174328.zip
Universal ADB Driver
Android SDK - https://developer.android.com/studio/index.html
TWRP - https://www.androidfilehost.com/?fid=24588212152304477 (Experimental build)
SunShine - http://theroot.ninja/apks/SunShine-latest.apk (Optional)
1) Visit htcdev.com and unlock your bootloader
-sign up as a dev, activate your email, and follow the steps
2) Download twrp from the app store. You won’t be able to run it yet but you still need it
3) Put the supersu zip file from your computer into your download folder of your phone
4) Get fastboot & adb running on your computer.
- open cmd prompt
-navigate to the fastboot/adb folder in your cmd prompt
-with your phone plugged into your computer type “adb devices”
-if it returns your device good
-now in cmd type “adb reboot downloader” (you can also do this by powering off your phone then turning your phone on by holding the down volume button and the power button at the same time.
-once you are in the downloader type “fastboot devices” in cmd
-if this returns your device good
-DO NOT GO ANY FURTHER TILL THIS IS WORKING!!!
4)Once your phone is in the rebooted downloader screen type “fastboot flash recovery <twrpDownloadFromAbove>”
-make sure you are on the downloader page and not the bootloader page
-this should end in .img
-this is a second boot screen for your phone. The first time I did this recovery wasn’t working because I was trying to fastboot on the bootloader page.
5) Now boot into recovery mode by navigating to it on your phone or using the cmd “adb reboot recovery”
-Once you are here you will see the twrp screen
6a) The way I did it is going into the twrp recovery boot and going to install and choosing the supersu.zip file I moved to my phone in step 3. After it is done reboot your phone and now you are rooted.
6b) The other way is to go to advanced in twrp and enable sideload
-now in cmd type “adb sideload <SuperSuDownloadFromAbove>”
7) If you need to turn S-OFF install sunshine on your phone and it will do it.
-You need to have your phone rooted first to turn your S-OFF with sunshine
Click to expand...
Click to collapse
uum it hangs here and nothing happens and I know and is working because I adb devices and this phone shows up
Sent from my HTC Desire 530 using XDA-Developers mobile app

dornz said:
View attachment 3915766 uum it hangs here and nothing happens and I know and is working because I adb devices and this phone shows up
Sent from my HTC Desire 530 using XDA-Developers mobile app
Click to expand...
Click to collapse
Does 'fastboot devices' return your phone or just 'dab devices'?

whittlestick said:
Does 'fastboot devices' return your phone or just 'dab devices'?
Click to expand...
Click to collapse
Ya I think I need to create a sub folder named fastboot in adb before I issue fastboot devices command thanks for reply
Sent from my HTC Desire 530 using XDA-Developers mobile app

dornz said:
Ya I think I need to create a sub folder named fastboot in adb before I issue fastboot devices command thanks for reply
Sent from my HTC Desire 530 using XDA-Developers mobile app
Click to expand...
Click to collapse
Wait so it does or doesn't? If it doesn't I think you might have a bad stock img you might have bad stock img on your phone. Is the stock img the same on that was on the phone when you bought it?

whittlestick said:
Wait so it does or doesn't? If it doesn't I think you might have a bad stock img you might have bad stock img on your phone. Is the stock img the same on that was on the phone when you bought it?
Click to expand...
Click to collapse
so I get this going and now I try to highlight token text but boot loader text keeps getting highlighted to so when I paste in in to token box in HTC dev I get error saying token string not long anuf or error. Basicly when I highlight it it needs to be token start to token end but when I mark on cmd it highlights boot loader text to
Sent from my HTC Desire 530 using XDA-Developers mobile app

dornz said:
View attachment 3916973 so I get this going and now I try to highlight token text but boot loader text keeps getting highlighted to so when I paste in in to token box in HTC dev I get error saying token string not long anuf or error. Basicly when I highlight it it needs to be token start to token end but when I mark on cmd it highlights boot loader text to
Sent from my HTC Desire 530 using XDA-Developers mobile app
Click to expand...
Click to collapse
You have to copy and paste it on a notepad, edit and remove the bootloader parts, recopy and place in the Htcdev box. At least that's what I came up with to get the job done.
DWil's Magic Carpet

wilbigdaddy2000 said:
You have to copy and paste it on a notepad, edit and remove the bootloader parts, recopy and place in the Htcdev box. At least that's what I came up with to get the job done.
DWil's Magic Carpet
Click to expand...
Click to collapse
Thanks will try again later
Sent from my LG-D855 using XDA-Developers mobile app

Did anyone get viper4android to work on our device? If so what did u do?
DWil's Magic Carpet

I cannot register in HTCDev (literally, it doesn't allow me to create an account), is there any other way to unlock my bootloader?

i get it thanks alot