Database Info

ADB Access Win x64 (CM10)

Since I can't respond to threads in Developer and I think that this might belong here to answer some folks questions. I have read that a lot of people are having issues with ADB access under Windows x64 using the latest CM10 by h8rift. I found a solution that worked for me and I wish to share it with everyone in case it will work for them. A few critiria:
- Your device is connected via USB cable to your computer
- Your device is listed as "HTC MTP Device" in Windows Device Manager
- When you open a CMD prompt under your Android Directory and type "adb devices", nothing is listed
This is because you have the wrong device drivers installed on your system and it needs to be corrected. This is how I accomplished it.
1. Uninstall the driver completely from your system. This has to be done under the device properties. Under "Action", select "Scan for New Hardware Changes". Your system will see the new device and identify it under "Other Devices" as "One". If Windows tries to install the wrong drivers, you will have to restart all over until the HTC MTP Device driver is completely removed from your system.
2. Install HTC Sync from their website. Once installed, it has to update to the latest version. This is needed to install all additional drivers for SD Card access.
3. HTC One X Drivers will be listed under C:\Program Files (x86)\HTC\HTC Driver\Driver Files (default install location).
4. For ADB access, you will need the drivers located here; download appropriate drivers for your Windows flavor. These are the ADB drivers.
5. Download the zip, and extract. Remember the location of the files. Go into Device Manger, find "One" under "Other Devices" and Update Driver Software. Point to the new directory you made and install. The One X will now be listed in Device Manager as "My HTC" under "Android USB Devices"
6. To verify ADB, open a CMD prompt, point to Android directory and type in "adb devices". Your beautiful HTC One X should be listed.
I am not the maintainer of any of these webpages nor can I guarantee that these pages will exist to the end of time. Those of you wishing to have ADB access under Windows for CM10, this worked well for me. I gathered up this information just by doing a quick search in Google and through the forums.
Thank you to h8rift for CM10 and all the hard work he puts into it.

Will try this when I get home! Thanks.

This worked perfectly for me. Thanks man!
------------------------------------------------------------
HTC One X, CM10-Evita JellyBean, Win7-x64

Not working for me, evertime I scan for hardware changes it tried to install HTC MTP DEVICE, and when I try to update that driver with the new ADB driver, it says it's already installed. Then when I uninstall that driver, I don't see the One devices anywhere, until I scan for hardware changes again, which then repeats the above. What am I doing wrong?

Chrysis said:
Not working for me, evertime I scan for hardware changes it tried to install HTC MTP DEVICE, and when I try to update that driver with the new ADB driver, it says it's already installed. Then when I uninstall that driver, I don't see the One devices anywhere, until I scan for hardware changes again, which then repeats the above. What am I doing wrong?
Click to expand...
Click to collapse
I think I found a fix for that. Let me restart my computer and verify
edit: nope.. nothing so far. mine doesn't even show HTC MTP DEVICE anymore >.>

same i see one when i look for new hardware but it always just auto sets to mtp.

Delete old drivers
The reason for this is that you cannot completely delete existing drivers using device manager. They still exist in the driver store, and are loaded as soon as you scan for hardware changes.
There might be a better way to do this, but here's how I did it:
- uninstall driver in device manager. Don't scan for hardware changes.
- Run a CMD prompt as administrator (right click "Run as Administrator")
- navigate to C:/Windows/system32 which is the location of the driver store
- type pnputil.exe /e
- this will list the drivers that exist in the driver store. They are denoted as oem##.inf
- find the driver that has "HTC Corporation" in the description. Write down the oem##.inf number (ex. oem81.inf)
- type pnputil.exe /d oem##.inf (where ## corresponds to the number of the HTC driver).
This will remove the old driver from the driver store. Now when you scan for hardware changes, it should fail to find a driver and prompt you for a location.
NOTE: I actually had several HTC drivers in the driver store. Its because I've had a few HTC devices over the years. I deleted them all. This may break HTC Sync, I dunno. I don't use it.

Fixed. See post below

For anyone having problems. I finally got it working.
THIS SHOULD BE NO LONGER NEEDED. ROHAN'S NEW AOKP VERSION 2 SHOULD WORK WITH STOCK DRIVERS. IM ASSUMING THIS WILL BE MERGED WITH ANY OTHER AOSP ROMS. IF YOU STILL NEED THIS INFORMATION HOWEVER, I WILL LEAVE IT UP.
1. Uninstall HTC Sync and any HTC sync drivers listed in your "Add/Remove Programs"
2. Delete EVERY driver pertaining to HTC when you run CMD as admin and type "pnputil -e" and then type "pnputil -d oem##.inf" (such as oem13.inf ONLY IF it says HTC or HTC Corporation)
3. Download Deview - 32 bit OR 64 bit, and run as administrator and uninstall ALL disconnected drivers (it won't matter if you uninstall the wrong thing, because it will just reinstall again when you plug in the hardware. make sure your phone IS NOT plugged in)
4. Download ADB drivers 32 bit OR 64 bit. (windows)
**Restart Computer**? (I did just to be safe)
5. Plug in your phone. Go into device manager, and find your device. It should be listed as "One" with a yellow question mark.
6. Right click and update driver software
7. find your USB drivers you downloaded and choose to install those.
your device should now be listed under "Android USB Devices" as "My HTC"
When I did this, my phone skipped being labelled as "HTC MTP Device" all together
If it is not detected in ADB after installing drivers...
1. UNPLUG PHONE
2. Run USBDeview as administrator
3. Uninstall any unplugged devices
4. Restart computer
5. Plug in phone
{
"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"
}
and after verifying adb reboot bootloader worked. I thought, well heck. I'm sick of installing a file manager to install a file manager that's already stored on my sdcard.
and to verify it installed (no restart)
I hope this helps someone

done everything, nothing work. sees my HOX only while being ON and thus can't get the cid :/

pet3rs said:
done everything, nothing work. sees my HOX only while being ON and thus can't get the cid :/
Click to expand...
Click to collapse
What exactly are you trying to do? Did you install HTC Sync drivers? This is for using ADB on the old CM10/AOKP, not for rooting your phone

device is already rooted, I need to get adb working because I can't get my cid from fastboot command.

pet3rs said:
device is already rooted, I need to get adb working because I can't get my cid from fastboot command.
Click to expand...
Click to collapse
Boot your phone into fastboot from your bootloader
Sent from my HTC One XL using xda-developers app

i'm in fastboot and type adb shell getprop ro.cid, message says error: device not found. fastboot getvar cid returns CID: none

Found a great way that fixed it for me on Windows 8:
use this tool: http://www.nirsoft.net/utils/usb_devices_view.html to remove all instances of anything that has to do with HTC. Then, follow steps above to scan for new devices, and set the driver accordingly (with USB debugging on on the phone). It should register as "My HTC" and then you will be able to see the device in "adb devices" list.

pet3rs said:
i'm in fastboot and type adb shell getprop ro.cid, message says error: device not found. fastboot getvar cid returns CID: none
Click to expand...
Click to collapse
you can't use adb from fastboot. you use fastboot.exe e.g.
fastboot oem getvar cid
no adb needed.

Guys can u pls help me? I've done the above procedure for installing the drivers on my htc explorer, it all worked, in the device manager panel i can see My htc when i'm in fastboot, and i can see Android bootloader Interface when i'm in the bootloader, but nevertheless I can't run adb shell because it doesn't find the device, and when I run adb device it gives me an embty list, i must use adb in order to attemp to recover the nand that it's probably burned.

[how to] remove your "tampered" banner

*this thread is for E8. it will NOT work on m7(or anything older). search your device general forum for a specific thread
if you have recently s-off'ed using an exploit that did not remove your tampered banner from the bootloader screen,then this thread is for you.
*note: if you are on hboot 3.19.0.0000 this thread will change software status: modified banner to: software status: official. to my knowledge,this banner is not completely removable (more info)
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on
the usual disclaimers:
i have tested this my my m8_ul t mobile variant,but use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
-andybones for testing it on m7_wlv
-WorldIRC and brar.arsh for testing on m8
-ian.anindya and a couple others have provided dumps. let me know and ill add you to the credits. if someone wants to provide screen shots,i can add those as well.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and lower)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify tamered is gone
your cmd window should look something(but not exactly) like this(red= my inputs,blue=additional comments):
Code:
c:\miniadb_m8>[COLOR="Red"]adb shell[/COLOR]
[email protected]_m8:/ $ su
su
[email protected]_m8:/ # [COLOR="red"]echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564[/COLOR]
ock/mmcblk0p6 bs=1 seek=5314564 <
1+0 records in [COLOR="Blue"][COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m8>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.022s
c:\miniadb_m8>
other useful threads:
lock/unlock without htcdev:
change mid without eng hboot: http://forum.xda-developers.com/one-e8/general/how-to-change-mid-eng-bootloader-t3019148
if this does not work for you
*first reread this thread in its entirety. make sure you have met the prerequisites,and double check your code and make sure you have not forgotten a step,or screwed something up trying to type it (especially if using a terminal emulator),and check that you have not gotten any errors.
if youre still confident you did things correctly,you need to PM me:
1)the results of: fastboot getvar all
2)a link to an uploaded p6.
you get fastboot getvar all by:
-place phone in fastboot
-enter in fastboot getvar all right click,click mark,highlight in white,hit enter or right click to copy
you dump p6 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6
transfer the file on internal storage to your pc and upload it
im not trying to be a ****,but its not helpful to post "didnt work" if you screwed something up,or if your not willing to help find a solution. especially if others have found it to work on their same variant.
important:
from now on,i will need a copy of your cmd window as well if we want to get to the bottom of whats happening. some folks seem to be simply writing extra bytes,wich is screwing up the flag location. please make sure this shows an entire session,not just a last part where it looks correct. we cant figure it out if you only show part of what you did.

mine

Working like a Bomb

Many thanks. Works like a charm.

thank you sir, it works on M8Sd MEC_DWGL :good:

Works on the M8sd Indian version HBOOT 3.19.0.0000
Sent from my HTC One_E8 dual sim

how can we remove tampered banner when device is s-on please help me

eminteoman said:
how can we remove tampered banner when device is s-on please help me
Click to expand...
Click to collapse
The only way is to run a signed ruu that meets all the phone's s on criteria

scotty1223 said:
The only way is to run a signed ruu that meets all the phone's s on criteria
Click to expand...
Click to collapse
Can you explain a little further? I really couldn't understand

eminteoman said:
Can you explain a little further? I really couldn't understand
Click to expand...
Click to collapse
Easy way: s-on can't get rid of the text
Send via my CM 12 Gtab3

wildanw2 said:
thank you sir, it works on M8Sd MEC_DWGL :good:
Click to expand...
Click to collapse
Does it works on m8sx??

[how to] lock/unlock your bootloader without htcdev(s-off required)

READ THIIS!
*this thread is for E8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-ian.anindya and a couple others have provided dumps. let me know and ill add you to the credits. if someone wants to provide screen shots,i can add those as well.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
(yes this is m7. i dont have an E8. if someone wants to provide correct screenshots,ill add them)
other useful threads:
remove tampered banner: http://forum.xda-developers.com/one-e8/general/how-to-remove-tampered-banner-t3019164
change mid without an eng bootloader: http://forum.xda-developers.com/one-e8/general/how-to-change-mid-eng-bootloader-t3019148

sorry for the delay,guys. hope you find it useful

This way doesn't wipe out all the data, right?

buggerman said:
This way doesn't wipe out all the data, right?
Click to expand...
Click to collapse
Correct. It will not wipe any data
Sent from my HTC One max

Good job.
Any way to do S-OFF to S-ON ??
greg

gregferns said:
Good job.
Any way to do S-OFF to S-ON ??
greg
Click to expand...
Click to collapse
Sunshine again..

windows 8 and above
am using windows 10 but it seems the required tool does not support the operating system
any other option for me?

cant get # prompt
hi, when i enter the Su command it says su not found and the prompt still remains $ instead of #. Is it something am not getting right or something. Thanks

Samsung SM?T230NU 5.0- ADB Shows Unauthorized Device

adb shows Unauthorized device on custom ROM for SM-231
I successfully rooted my SM-230NU and installed the custom ROM provided in this post
http://forum.xda-developers.com/tab-4/development/rom-android-5-0-lollipop-material-t3061873
However, when I connect the device using USB to my Mac and try "adb devices" I get "unauthorized" beside the device ID. I have already tried the following:
a. on the Mac: adb kill-server followed by adb start-server
b. on the Mac: Deleted the ~/.android/adbkey and ~/.android/adbkey.pub
c. on Device: Revoked the USB debugging access to all computers (on the device) and also via terminal emulator app verified that on the device /data/misc/adb/ directory is empty
d. on PC: Repeated all the above on a Windows 7 machine (still shows "unauthorized" beside the device ID)
e. Changed multiple cables and tried the same cable with other devices and they are all detected as valid devices.
Unless I get the device to be recognized I am not able to install some apks using adb install. Any help will be highly appreciated.

execute "adb tcpip <port_no>" command without using usb

NON ROOTED PHONE
I am trying to create to backup of all application in android but I don't want the users to connect to USB even for the first time.
okay let me first explain what happens when we connect our phone with USB to ADB client
0. USB Debugging mode is enabled in the phone.
1. The phone is connected to PC using a USB cord.
2. We run
Code:
adb tcpip 9999
command from cmd with ADB already installed.
The above command helps now switched the abd demon (adbd) inside the android phone to listen through TCP-IP protocol
3. now we can disconnect the phone from the PC
4. using a terminal emulator application we can now fire the commands
a)
Code:
adb connect localhost:999
b)
Code:
backup -all -f /sdcard/dev/bck.ab
now a backup pop-up will open up, you can simply click backup button.
Now we can anytime execute the command in 4.a and 4.b util the user restarts the phone or
but the problem is I wish to execute
Code:
adb tcpip 9999
without PC. Can someone suggest me how to approach this problem. From where should I start reading or there is some existing application that can do this on a non-root phone.