[GUIDE] ADB and Fastboot - HTC Incredible S

ADB
The Android Debug Bridge (ADB) is a toolkit included in the Android SDK package. It consists of both client and server-side programs that communicate with one another. The ADB is typically accessed through the command-line interface...
FASTBOOT
Fastboot is a diagnostic protocol included with the SDK package used primarily to modify the flash filesystem via a USB connection from another computer. It requires that the device be started in a boot loader or Second Program Loader mode in which only the most basic hardware initialization is performed. After enabling the protocol on the device itself it will accept a specific set of commands sent to it via USB utilizing a command line...
INSTALLATION
1. Download HTC Sync from HERE
Remember we are installing HTC SYNC for Drivers only...If u Do not use this software then you can uninstall it...Bt keep drivers as it is...
2.Download ADB and Fastboot Drivers from HERE
Download zip file extract it anywhere in your computer (Extract it in C/android for more convenience). Just open extracted folder and run app.bat.
[No Need To Set Drivers Path It Will Detect That Automatically...]
3.Download ADB and Fastboot command's list from HERE
Here is a document file it contains commands of ADB and Fastboot.]
Caution :-
Files were not created by me. I simply collected them from many links and put them together in simplified form in one thread.
Command list file may does not contain all commands but this file contain all those commands which we use frequently.
Don't Forget to hit THANKS...If you like my work...:laugh::laugh::laugh:

Useful guide, a couple of points if I may...
Firstly regarding your step 1, I never uninstalled Sync, even though all of the guides tell you to. I used to use it to sync my phone so it was not convenient to do this. If you simply right click on the icon in the tray (on windows, next to the clock in the bottom right corner) then close the program, all off this still worked for me.
Secondly about your step 2, it would be good to create a folder in the root of C: drive (on your PC) and save these 'tools' in, call it something like 'Android' so it is easy to remember and easy to navigate to in the cmd prompt when using adb/fastboot.
.
--- --- --- --- --- --- --- --- --- ---
snt frm my inc s wiv my xda app

nniicckkss said:
Useful guide, a couple of points if I may...
Firstly regarding your step 1, I never uninstalled Sync, even though all of the guides tell you to. I used to use it to sync my phone so it was not convenient to do this. If you simply right click on the icon in the tray (on windows, next to the clock in the bottom right corner) then close the program, all off this still worked for me.
Secondly about your step 2, it would be good to create a folder in the root of C: drive (on your PC) and save these 'tools' in, call it something like 'Android' so it is easy to remember and easy to navigate to in the cmd prompt when using adb/fastboot.
.
--- --- --- --- --- --- --- --- --- ---
snt frm my inc s wiv my xda app
Click to expand...
Click to collapse
as i say in my post 1 ...there is no need to navigate through command prompt...so u can keep adb folder anywhr u want...just run app.bat...abt htc sync step i mean to say if ua not usein htc sync then uninstall...i neva used htc sync...i wil edit my post...thnks....:thumbup:
Sent from my Incredible S using Tapatalk 2

Related

[How to] Install android_winusb.inf, create adb shell loop, and root your phone

First off you need to have Android-SDK installed on your computer. I will not go into details about that process but here is the link to Google's official install page. Navigate to the folder you placed Android-SDK and run the SDK Setup.exe and make sure that you download the usb 3.0 driver software from the sdk updater window. I recommend erasing any HTC Sync software or drivers so that you can start from a clean point then reinstalling them.
Once you get the SDK installed from Google you need to go in a modify the USB 3.0 .inf file. Navigate to the folder you placed the Android-SDK and one step down you will see a folder that is named usb driver. Open the usb driver folder and then open the android_winusb.inf file in notepad. It should default into notepad when you click it. Next you need to copy and paste this text into notepad.
Find the section labeled [Google.NTx86]. At the end of that section, add the following lines.
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
Then find the section [Google.NTamd64]. At the end of that section, add the following lines.
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
Again just copy and paste. I have attached pictures to show where these need to go.
So now we have the USB driver on the computer and ready to be installed once you plug-in your Incredible.
On your Incredible press->Menu->Settings->Applications->Development->(check)USB debugging. Plug in your Incredible and you should get the found new hardware notification, select the No, not this time radio button, Install from a specific location(Advanced), Don't search, I will chose the driver to install. You should now have "Android Composite USB Device" in the white field selection box, click have disk and browse to the location of the android_winusb.inf file and click ok. Click next and it should install the USB driver you need for ADB to work properly.
Now if you click Start->(right click)My Computer->Properties->Hardware(tab)->Device Manager, you should see Android Phone at the top then when you open the tree you should see Android Composite USB Interface.
This will enable you to use the Android SDK from a command prompt to access your Incredible.
Once that is done open a command prompt by clicking Start->Run(XP) or the search box in W7 and type CMD(in W7 you need to right click command prompt and run as admin.). Then in the command prompt window type; cd (your file path to Android-sdk). now to test it type adb shell and press enter then reboot recovery and press enter. This should reboot your Incredible into recovery. (You can also type reboot bootloader to get to that screen.)
Once you make sure that is working press vol. up and power, then select reboot with the power button. GO back into Settings and deslect the USB debugging check box. Now we need to get adb shell to loop so that it can catch the Incredible in its flawed sequence that allows us to access the phone in recovery. Navigate your command prompt box to your tools folder and then follow these directions courtesy of prerunnerseth over at AndroidForums.com
type edit loop.bat
in edit enter the following
Code:
@echo off
:TOP
adb shell
GOTO TOP
press alt-f then x
hit enter for yes
Here is a link to Androidforums.com with two different methods for gaining root access on your phone.
This is a great 10 min. video on how to root as well.
I hope this helps clear some confusion up for those that can't quite get the Android Composite USB interface going. This credited to all parties involved and is just a collection of info.
So what you are saying is we need to take it off of debug mode before looping the shell command?
Hmmm...I had mine in Debug mode every time (failed every time, too). Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Here's the android_winusb.inf file for the Incredible.
Switch this file out with the one that's inside your AndroidSDK/usb_driver folder.
http://www.megaupload.com/?d=S2H4R3QZ
Here's the adb shell loop for Windows.
I placed it inside my AndroidSDK/tools folder.
http://www.megaupload.com/?d=N0150VUI
I hope this helps!
SeanRinVA said:
Hmmm...I had mine in Debug mode every time. Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Click to expand...
Click to collapse
I had mine on and it worked. Try, try, try you'll get it!
Good luck!!!
SeanRinVA said:
Hmmm...I had mine in Debug mode every time. Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Click to expand...
Click to collapse
Report back. Rooting the DI will only get simpler and more reliable the old fashioned way: a LEAK from HTC!! If we had something to flash from fastboot or recovery without first obtaining root, we would all have root except for those who didn't check their MD5's, in which case they'd brick. So this new (not you, OP, or you Unrevoked team, but this exploit in general), ****ty, hard way = relatively safe, totally unreliable. Old way = almost 100% reliable but little room for error.
jesus this is frustrating
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
sylent101 said:
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
Click to expand...
Click to collapse
It is supposed to say that... and you can't install the android sdk you can only open it... its is just a basic dos applicarion with a GUI front of it if I'm not mistaken so just try redownloading it
Try following the 10 minute video exactly on a cpu that does not have the sdk already on it. I used the same exact sd card and could not get it on my pc that already had the sdk , sync , drivers on it. I followed the instructions on the 10 minute video using the sdk and htc sync from the video link on a machine that did not have them prior and it worked first try using the first (adb shell) method. I think it had something to do with the prior sdk install I had.
another let down, tried with the 10 mins video also, oh well
sylent101 said:
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
Click to expand...
Click to collapse
Right click on Android adb interface and then select update drivers, then follow the instructions above for installing the android_winusb.inf file. As stated before SDK doesn't actually "install' it is more on an interface that you can open to download the new sdk's for app development and debugging. you should get the black box and another box that is called Android SDK and AVD manager. Within that window you should have these options on the left; Virtual devices, installed packages, available packages, Settings, and About.
Edit; Did you follow the instructions about editing PATH with the C:\Android-SDK-Windows\tools directory path?

[Q] ABD Drivers + Windows 7 issues (plus a couple more questions)

Hello XDA Community.
I'm attempting to install the new RC of CyanogenMod-6 for the Hero CDMA. I'm currently running the stock 2.1 version of Android. I've been following the guides that were referred to in the thread (I tried posting the urls but new users can't do so to prevent spam).
I've successfully rooted my phone and now I'm trying to do a Nandroid backup. I'm running Windows 7 32-bit and have hit a road block with ADB not recognizing my device. I followed the guide put together by Nephron to install the Android SDK. I've spent several hours going through threads and doing google searches looking for the solution. I have debugging turned on and I don't mount my SD drive when I plug the USB cord in. I've used USBDeview as some have suggested to delete current HTC drivers and then reinstall - no luck.
Here is a screen shot of what happens when I plug in my Hero:
See attached - "failedinstall.jpg"
Then I'll go to device manager to manually install the driver (it never allows me to manually select upon connection for some reason):
See attached "devicemgr.png"
And then this is the message I get when I point it to the "right" folder with the drivers:
See attached - "unabletoinstall.png"
So, on the Android SDK site I noticed this message:
"The USB driver for Windows provides support for the following Android-powered devices:
T-Mobile G1* / ADP1
T-Mobile myTouch 3G* / Google Ion
Verizon Droid*
Nexus One
* Or similar hardware on other carriers
Any additional devices will require Windows drivers provided by the hardware manufacturer.
^So is all of this HTC's fault? I've downloaded a couple of different .zip folders from different threads claiming that these drivers would work. But none of them have yet to do the trick for me.
I'm new at this so I have a few other questions as well:
Most guides I've read about how to do a Nandroid backup always recommend flashing a ROM b/f doing a backup. But I want to backup my current stock rom and settings before I flash. Wouldn't I want to create a recovery image before installing any other ROMs? Perhaps I'm misunderstanding some requirements?
Referring again to the thread on the CyanogenMod RC, can someone help me understand step #3? How do I know if it is necessary to update my radio? What implications does this have? I tried looking for info about this on the wiki and I couldn't find anything comprehensive enough to answer my question.
I'd appreciate any guidance!
Before you modify anything you will want to boot into recovery, assuming you flashed one, by holding down Home and turning the phone phone back on(power button). But since you don't have adb working then you probably haven't. You can still do this using terminal on your phone.
Download terminal emulator from market and then download a revoery image (AmonRa 1.6.2 or Darch's 1.7xx) and then mount your sdcard to the computer and transfer the recovery to the root of the sdcard. Open up terminal emulator and type in
Code:
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.6.2.img(type the exact file name of the recovery you are using)
reboot recovery
If you had factory 2.1 on your phone then you have the latest radio. The radio can be flashed just like any ROM, but make sure that the radio is not for GSM phones as this will destroy your phone.
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others)
Latest windows sdk version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may change with further updates..
Run C:\AndroidSDK\SDK Setup.exe
If you get an error about not having Java SDK installed but you do, add the path to 'bin' within your Java installation location to the Path environmental variable as described above before the sdk entry you just made. (eg add "C:\Program Files\Java\jdk1.6.0_20\bin;") This is likely to only be necessary where the 64 bit Java SDK is installed (obviously) on a 64 bit machine.
If it gives you an error about http go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
If all else fails try installing HTC Sync software-- http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC_Sync_2.0.40.exe and then removing the drivers for it and then trying to install the android sdk drivers
Or you can dual boot with Linux and all you will need to do is download and unzip android sdk and edit 2 files and everything will work.
WOW>>>>>no that is way to confusing. the best thing to do is install vmware workstation. Then do a virtual WINDOWS XP MODE. from there you will be able to install the drivers and such in order to get the phone to be seen.
the version of htc sync i used for all my computers including win 7 was 2.0.33
if you want it then just pm me and I will get it to you
they don't offer it for a download anymore
this version corrected all my driver issues

[TUT] ADB Guide

Hopefully this helps someone...
If something doesn't work here let me know and I'll add it and make corrections. I will gladly accept recommendations and input from anyone. Also Mac and Linux users please post your info and I'll gladly add your pieces to my guide as well.
Step 1:
Some files are needed such as the SDK and USB driver. Note: Some devices require Windows drivers provided by the manufacturer we will have to play around and see what works with Adam...
System Requirements
USB Drivers
Android SDK
- Download the zip file
Step 2:
Extract the zip and run the exe to install. It should check for JAVA dependencies and get you all setup.
Copy the SDK folder to the root of your C: drive or where ever you want. Plug in the device (Adam in this case), DO NOT MOUNT ANYTHING, and when prompted install the USB driver. NOTE: I'm not sure yet if the drivers in the link will work with Adam or not so play around and see what works. You can always go into Device Manager and remove the driver.
Step 3:
Create environment variables for ADB by right-clicking on "My Computer" and select Properties. Then go to Advanced tab (or Advanced Settings in Vista) and select Environment Variables. Add the following:
Variable name: adb
Variable value: C:\android-sdk-windows\tools
Note: that variable value may change if you do not run the sdk from the root of your C: drive and depending on the name of your SDK folder...
Step 4:
Code:
adb [COMMAND]
If you replace "[COMMAND]" with an adb command, the above should work for you. Go here for a listing of ADB commands...
A simple command to test with is:
Code:
adb shell
"adb shell" should return one of two values, "$" or "#". And this should be the shell prompt from the device, not your local terminal window.
If that code didn't work, put in your full SDK folder path and try again. If it works that way, look into the environment variable and make sure its the same as the path to your SDK folder.
References:
The first is the sweet guide from XDA member VanillaTbone and is widely used here at XDA.
The second is one I wrote over at NotionInkHacks. This one is only for Windows at the time being, but once people with other OSs leave feedback I will update to include those other OSs as well.
Thanks for the links!
They were helpful to me and I am sure they will be to others.
Thank you, stickied! This is useful to people unfamiliar with ADB.
Updated the OP so this is now a full guide. I also updated the title to reflect tutorial.
webs05 said:
Updated the OP so this is now a full guide. I also updated the title to reflect tutorial.
Click to expand...
Click to collapse
Excellent work. This will help all the first time Androiders here!
How to get your Adam detected in Windows
After following this.. you can follow this next to now make sure windows detects your Adam.
http://forum.xda-developers.com/showthread.php?p=12022670#post12022670
it would be more uniform if people installed the .exe and have 2 paths for step 3 depending on 64 bit or 32 bit
for 64 bit when installing the exe the path is
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools
and for 32 bit I believe its (not sure on this one because I have 64 bit)
C:\Program Files\Android\android-sdk-windows\platform-tools
Also might be wise to mention that if you do not define a push or pull path way when you start up the command prompt it will look in C:\users\"UserName"
edit: fixed: http://developer.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
thanks for your help
howdy,
I have previously installed the adb driver for my sgs and sgs2. When I plug in my adam, the mass storage components come up, but nothing shows up with regards to android devices which will allow me to update the driver for.
Debugging is enabled on my adam (it is a PixelQi/Wifi version running beast+clemsync v3) and shows up in the notifications. USB Mass storage works fine.
ADB also works fine for my SGS2 when I plug it in and run adb shell/devices. When I plug my adam in, adb does not see anything related to it.
Where should I go from here to get windows to like this thing?
edit:
When I plug it in I can see these things:
If the nvidia harmony device shows up in the device manager I don't know where
Click to expand...
Click to collapse

[Q] Any easy way to completely copy the state of one Moto X to another?

I got a new phone with a wood back and will be selling my old one soon. Is there an easy way to completely clone my old phone's contents onto my new one?
Could try doing an NAND backup on the old one. Then putting it in the same directory of the new one. The directory would be /twrp/backups/(some numbers assigned to be your phones ID)/backup name.
Your ID will change, but you should be able to use that backup to restore on the new phone.
Sent from my XT1060 using xda app-developers app
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
You might have to make an NAND on the new phone to have the recovery make the new filepath
Sent from my XT1060 using xda app-developers app
kkeller87 said:
Could try doing an NAND backup on the old one. Then putting it in the same directory of the new one. The directory would be /twrp/backups/(some numbers assigned to be your phones ID)/backup name.
Your ID will change, but you should be able to use that backup to restore on the new phone.
Sent from my XT1060 using xda app-developers app
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
You might have to make an NAND on the new phone to have the recovery make the new filepath
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Thanks. This requires root, right? I haven't rooted either of the phones, although I would if it sped this process up. It's something that I eventually want to do anyway.
beelbeel said:
Thanks. This requires root, right? I haven't rooted either of the phones, although I would if it sped this process up. It's something that I eventually want to do anyway.
Click to expand...
Click to collapse
Yea. Sorry. A custom recovery/safestrap is required. I kinda assume anyone who's on XDA has it. Without root I'm not entirely sure how to do it any other way than manually.
Sent from my XT1060 using xda app-developers app
Without root the best you can do is mybackup pro or titanium backup. They will back up app data but not the apps themselves. Get your new phone, download your apps, restore app data from mybackup.
I wrote this before, but this is how you can backup your apps and their data with a computer and without root. Moto X's have Motorola Migrate that can move over some settings.
This process can take a bit to explain, so sorry for the long post.
First, you'll need to install Oracle’s Java Development Kit, which the Android SDK requires. Download and install the 32-bit version. The Android SDK wants the 32-bit version, even if you're using a 64-bit version of Windows.
Next, download the Android SDK from Google. Extract the .zip folder to a location of your choosing, but remember where you put it. If you have the option to open extracted contents in a new window, do so.
Okay, now open the Android SDK Manager (you may have to open a subfolder or two) with administrative rights. You do this by right clicking on the .exe and choosing the option "Run as administrator". A window will pop up, click yes, and after a small wait, the SDK Manager will open.
Now within the SDK Manager, under the tools section, check the box for Android SDK Platform-tools and click Install. This can take some time depending on your Internet connection. Once installed, go back to the open window where you clicked the SDK Manager .exe and navigate to the folder named "Platform Tools". If you're unsure where this is, the SDK Manager has the path of install located near the top.
Now let's get the phone ready. If you can, charge your device to its fullest. Now go into the settings, scroll down to 'development options'. Near the top of this menu, make sure the toggle switch is in the 'on' position. Now scroll down to USB debugging, and tick the box. Tap "OK" when the message shows up. Now plug the smaller end of the USB cable (preferably the one that came with your phone) into the bottom of the phone and the other into an open USB port of your computer. It's best to use a 2.0 USB port (no blue end) and if on a desktop, a port located in the rear.
If your computer starts installing any drivers, let it do this. Once that's finished, go to the window with the Platform Tools folder open. You should see a few files, two named "ADB" and another "Fastboot". Now hold your Shift key, right click in an open area, and choose the option "Open command window here". You may release the shift key at this time.
We're almost done. To make sure your tablet is seen by the computer type:
Code:
adb devices
One device should be listed. If you see no devices, adb can’t communicate with your device because its driver isn't installed properly. In this case, go back to the SDK Manager and download the USB drivers. You may also need to restart your computer.
Assuming you're up and working, type:
Code:
adb backup -apk -shared -all -f C:\backup.ab
This backs up all the installed apps (APK files) and shared storage (SD card) data to the C:\backup.ab file on your computer.
After running this command, you'll have to agree to the backup on the device. You can also encrypt the backup with a password here, if you like (leave it blank if you don't want encryption). Depending on how much data there is to back up, this can take some time. The device will let you know when it's done.
Now for the restoration process:
On the new device, make sure USB debugging is enabled. On the computer, follow the same steps for opening the adb command window. Ensure adb can see the device, then type:
Code:
adb restore C:\backup.ab
On the device, you will need to confirm you want to do a full restore. If you encrypted the backup, enter in the password, then hit "Restore my data". If you didn't add encryption, then leave that area blank. Once the restoration is done, you're good to go.
Thanks for the replies.
Hikikomori-Otaku said:
I wrote this before, but this is how you can backup your apps and their data with a computer and without root. Moto X's have Motorola Migrate that can move over some settings.
This process can take a bit to explain, so sorry for the long post.
First, you'll need to install Oracle’s Java Development Kit, which the Android SDK requires. Download and install the 32-bit version. The Android SDK wants the 32-bit version, even if you're using a 64-bit version of Windows.
Next, download the Android SDK from Google. Extract the .zip folder to a location of your choosing, but remember where you put it. If you have the option to open extracted contents in a new window, do so.
Okay, now open the Android SDK Manager (you may have to open a subfolder or two) with administrative rights. You do this by right clicking on the .exe and choosing the option "Run as administrator". A window will pop up, click yes, and after a small wait, the SDK Manager will open.
Now within the SDK Manager, under the tools section, check the box for Android SDK Platform-tools and click Install. This can take some time depending on your Internet connection. Once installed, go back to the open window where you clicked the SDK Manager .exe and navigate to the folder named "Platform Tools". If you're unsure where this is, the SDK Manager has the path of install located near the top.
Now let's get the phone ready. If you can, charge your device to its fullest. Now go into the settings, scroll down to 'development options'. Near the top of this menu, make sure the toggle switch is in the 'on' position. Now scroll down to USB debugging, and tick the box. Tap "OK" when the message shows up. Now plug the smaller end of the USB cable (preferably the one that came with your phone) into the bottom of the phone and the other into an open USB port of your computer. It's best to use a 2.0 USB port (no blue end) and if on a desktop, a port located in the rear.
If your computer starts installing any drivers, let it do this. Once that's finished, go to the window with the Platform Tools folder open. You should see a few files, two named "ADB" and another "Fastboot". Now hold your Shift key, right click in an open area, and choose the option "Open command window here". You may release the shift key at this time.
We're almost done. To make sure your tablet is seen by the computer type:
Code:
adb devices
One device should be listed. If you see no devices, adb can’t communicate with your device because its driver isn't installed properly. In this case, go back to the SDK Manager and download the USB drivers. You may also need to restart your computer.
Assuming you're up and working, type:
Code:
adb backup -apk -shared -all -f C:\backup.ab
This backs up all the installed apps (APK files) and shared storage (SD card) data to the C:\backup.ab file on your computer.
After running this command, you'll have to agree to the backup on the device. You can also encrypt the backup with a password here, if you like (leave it blank if you don't want encryption). Depending on how much data there is to back up, this can take some time. The device will let you know when it's done.
Now for the restoration process:
On the new device, make sure USB debugging is enabled. On the computer, follow the same steps for opening the adb command window. Ensure adb can see the device, then type:
Code:
adb restore C:\backup.ab
On the device, you will need to confirm you want to do a full restore. If you encrypted the backup, enter in the password, then hit "Restore my data". If you didn't add encryption, then leave that area blank. Once the restoration is done, you're good to go.
Click to expand...
Click to collapse
Thanks for the detailed response. I actually use a mac, and I might have to do some research to see what parts of this process still apply. I may also just investigate other methods of transferring most (perhaps not all) of the data.
beelbeel said:
Thanks for the detailed response. I actually use a mac, and I might have to do some research to see what parts of this process still apply. I may also just investigate other methods of transferring most (perhaps not all) of the data.
Click to expand...
Click to collapse
This may help with getting adb to work on your Mac http://forum.xda-developers.com/showthread.php?t=1917237 Otherwise you could use an application like VMware Fusion to virtually run a Windows OS on your Mac. I know you can get evaluation copies of Windows to use that don't require a product key (they only work for 90 days though).

unknown device in device manager

Hi
I have HTC one that couldn't be recognized by my pc
running under windows 7 by usb
I have : VId = 0000 and pid = 0000 in : le chemin d'acces à l'instance du périphérique :
USB\VID_0000&PID_0000\6&189D988F&0&4
knowing that I have installed the last version of HTC Sync manager,
usb debogging is enabled in my htc ,
sorry for my poor english
thank you for your help
hm911 said:
Hi
I have HTC one that couldn't be recognized by my pc
running under windows 7 by usb
I have : VId = 0000 and pid = 0000 in : le chemin d'acces à l'instance du périphérique :
USB\VID_0000&PID_0000\6&189D988F&0&4
knowing that I have installed the last version of HTC Sync manager,
usb debogging is enabled in my htc ,
sorry for my poor english
thank you for your help
Click to expand...
Click to collapse
Take a look at FAQ Q#2 on getting your phone recognized.
majmoz said:
Take a look at FAQ Q#2 on getting your phone recognized.
Click to expand...
Click to collapse
Hi @majmoz
steel not finding my problem in this FAQ
hm911 said:
Hi @majmoz
steel not finding my problem in this FAQ
Click to expand...
Click to collapse
Did you follow the steps in FAQ Question #2? Can you use a different port, cable or computer? Depending on what you want to accomplish, you could use Linux on a USB!
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219​Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse

Categories

Resources