Dont know y but my usb debugging is not working.
Flashed stock ftf 2 times.still not work.
When i connect phone to flashtool.it says phone connected with usb debugging turned of.
Reinstalled all drivers expect adb.
I used adb universal installer many times.but it can not detect my my phone.
Thanks in advance
Sent from my LT26ii using xda premium
nisu4717 said:
Dont know y but my usb debugging is not working.
Flashed stock ftf 2 times.still not work.
When i connect phone to flashtool.it says phone connected with usb debugging turned of.
Reinstalled all drivers expect adb.
I used adb universal installer many times.but it can not detect my my phone.
Thanks in advance
Sent from my LT26ii using xda premium
Click to expand...
Click to collapse
In flashtool folder there should be a driver folder with all of the drivers use those drivers.
You may have a conflicting driver. (eg HTC and Sony drivers cross talk the same port)
You may have another software using a instance of adb, eg a sync software, use task manager to kill any that apply.
What's the adb error?
Sent from my HTC One using Tapatalk
XDA_h3n said:
In flashtool folder there should be a driver folder with all of the drivers use those drivers.
You may have a conflicting driver. (eg HTC and Sony drivers cross talk the same port)
You may have another software using a instance of adb, eg a sync software, use task manager to kill any that apply.
What's the adb error?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
No error.but adb is not detected.
Not even in device manager.
Bytheway can u give me frmework-res.apk from stock rom...i need that.
Edit: when i normally connect,i got 2 auto play.1 for s and second for sl.
Sent from my LT26ii using xda premium
nisu4717 said:
No error.but adb is not detected.
Not even in device manager.
Bytheway can u give me frmework-res.apk from stock rom...i need that.
Edit: when i normally connect,i got 2 auto play.1 for s and second for sl.
Sent from my LT26ii using xda premium
Click to expand...
Click to collapse
Yeah this has happened to me when I bought my phone. I did some very hard tinkering to get it to work - I think it was forcing the install with device manager.
Before we see anything else - make sure adb is updated to the recent version Also there may have been problems with android drivers if your running windows 8 and 8.1 - which version are you running?
You've said you get 2 autoplay dialogs: one for s and one for sl. Is this for just one phone? It seems like you may have installed s and sl drivers...
I'm currently not running a stock rom so I can't give you a framework-res.apk
XDA_h3n said:
Yeah this has happened to me when I bought my phone. I did some very hard tinkering to get it to work - I think it was forcing the install with device manager.
Before we see anything else - make sure adb is updated to the recent version Also there may have been problems with android drivers if your running windows 8 and 8.1 - which version are you running?
You've said you get 2 autoplay dialogs: one for s and one for sl. Is this for just one phone? It seems like you may have installed s and sl drivers...
I'm currently not running a stock rom so I can't give you a framework-res.apk
Click to expand...
Click to collapse
M running windows 7.
For drivers,i hav installed every driver comes with flash tool.
For my sl i got 2 autoplay.
Sent from my LT26ii using xda premium
nisu4717 said:
M running windows 7.
For drivers,i hav installed every driver comes with flash tool.
For my sl i got 2 autoplay.
Sent from my LT26ii using xda premium
Click to expand...
Click to collapse
To be honest, I've tried all of the troubleshooting tips... I dont the problem myself Wait and see for someone to reply if not go to the sony xperia support forums where they can help you a bit more as they're a bit more active than us in terms of helping. XDA is more of a developer forum where people develop and collabrate.
Apparently, there has been *some* issues with usb 3. Try usb 2 just for compatibilites sake. If not then continue reading
Also read this thread
And this could also help:
Quoted from the thread posted:
I've got an Xperia S and I'm using Windows 7 SP1 (x64). Had the same problem but this is what worked for me:
First of all disable USB debugging mode on your Xperia S. If your phone's connected to your pc/laptop disconnect it and then open CMD by typing 'cmd' in the start menu's search box. Then type this exactly as it is:
net localgroup Administrators "local service" /add
After this step, exit CMD. Now connect your phone and it should get detected by PCC and your computer :smileyhappy: Hope this helps!
Click to expand...
Click to collapse
If you know the device manager port then this should help
Quoted from microsoft kb support (kb 817900)
Method 3: Disable and re-enable the USB controller
Use Device Manager to disable and re-enable all the USB controllers. This lets the controllers recover the USB port from its unresponsive condition. The USB controllers represent the USB ports in Device Manager. If you are not comfortable with advanced troubleshooting, try the steps in the "Workaround" section.
To disable and re-enable the USB controllers, follow these steps:
Click Start, and then click Run.
Note If you are running Windows Vista, click Start, and then use the Start Search box.
Type devmgmt.msc, and then click OK. Device Manager opens.
Expand Universal Serial Bus controllers.
Note You might have to scroll down the list to find this item.
Right-click the first USB controller under Universal Serial Bus controllers, and then click Uninstall to remove it.
Repeat step 4 for each USB controller that is listed under Universal Serial Bus controllers.
Restart the computer. After the computer starts, Windows will automatically scan for hardware changes and reinstall all the USB controllers that you uninstalled.
Check the USB device to see whether it is working.
If the USB port recognizes the device and if you can use the device, you are finished.
If this method fixed the problem, you are finished. If this method did not fix the problem, go to the "Workaround" section.
Click to expand...
Click to collapse
Tried both but still debugging not working.....
Sent from my LT26ii using xda premium
Ive had the same problem. I used flashtool with the stock ROM. I used flash mode with the stock ROM. When booting the device with USB cable i pressed volume down before pushing cable in and then i pushed cable in. Sorry for the laggy english
Verstuurd vanaf mijn Xperia S met Tapatalk
Is your problem solved allready
Verstuurd vanaf mijn Xperia S met Tapatalk
bikeriderr1 said:
Is your problem solved allready
Verstuurd vanaf mijn Xperia S met Tapatalk
Click to expand...
Click to collapse
No,having exams....
So will solve after this....
Sent from my LT26ii using xda premium
Related
Hey all, I know it's cliche, but I'm having a lot of troubles with ADB.
This isn't my first Android device, but it is the first Android device I've had in which the "adb devices" command still doesn't find even after having drivers/Companion Software installed.
Here's a full run-down of things I've done: installed that crappy software, the computer can recognize the Ion in terms of being able to access it for moving files, I have both Unknown Sources and USB debugging ticked, I've rebooted the phone, and a few other things.
Thanks for reading, and please assist!
King Cole said:
Hey all, I know it's cliche, but I'm having a lot of troubles with ADB.
This isn't my first Android device, but it is the first Android device I've had in which the "adb devices" command still doesn't find even after having drivers/Companion Software installed.
Here's a full run-down of things I've done: installed that crappy software, the computer can recognize the Ion in terms of being able to access it for moving files, I have both Unknown Sources and USB debugging ticked, I've rebooted the phone, and a few other things.
Thanks for reading, and please assist!
Click to expand...
Click to collapse
Ok, here is the deal. I am assuming you have downloaded the SDK package. What you are going to have to do is go into device manager and manually select ADB USB composite driver.
The problem is, I've never been able to find my device in devmgmt. I'm not home at the moment, so I can't check, but where would it normally be under if not the "Unrecognized Devices" category?
Sent from my Sony Xperia Ion using xda premium
King Cole said:
The problem is, I've never been able to find my device in devmgmt. I'm not home at the moment, so I can't check, but where would it normally be under if not the "Unrecognized Devices" category?
Sent from my Sony Xperia Ion using xda premium
Click to expand...
Click to collapse
Are you using windows? It is under Android Device or Xperia Ion should be easy to find, if you have Sony Companion software loaded, if you have Ubuntu it is a little hard and I don't remember all the steps I had to take to set up mine. It was something about finding the USB device name in all 3 modes.
popfan said:
Are you using windows? It is under Android Device or Xperia Ion should be easy to find, if you have Sony Companion software loaded, if you have Ubuntu it is a little hard and I don't remember all the steps I had to take to set up mine. It was something about finding the USB device name in all 3 modes.
Click to expand...
Click to collapse
I'm using Windows 7, but I don't recall being able to find it. I'll try again when I get home on Friday, and get back to you then.
Sent from my Sony Xperia Ion using xda premium
popfan said:
Are you using windows? It is under Android Device or Xperia Ion should be easy to find, if you have Sony Companion software loaded, if you have Ubuntu it is a little hard and I don't remember all the steps I had to take to set up mine. It was something about finding the USB device name in all 3 modes.
Click to expand...
Click to collapse
Thanks for the help. I found the problem was my cable, and as soon as I had changed that out, it worked fine.
King Cole said:
Thanks for the help. I found the problem was my cable, and as soon as I had changed that out, it worked fine.
Click to expand...
Click to collapse
Please add [solved] or fixed to subject line of your OP. It helps others in searching
~Jaramie
from my LT28at rooted & eating an Ice Cream Sandwich
ToledoJab said:
Please add [solved] or fixed to subject line of your OP. It helps others in searching
~Jaramie
from my LT28at rooted & eating an Ice Cream Sandwich
Click to expand...
Click to collapse
Just forgot, thanks for the reminder.
When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?
Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app
Disregard. I figured it out. It was a driver issue after all.
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.
thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
fixed mine by just forcing it to reinstall the drivers.
fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.
Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app
To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.
hi, i have problem connecting my arc s in fastboot to flash kernel i install drivers but windows say Unknown USB Device
is fix on the way
Doktor-X said:
hi, i have problem connecting my arc s in fastboot to flash kernel i install drivers but windows say Unknown USB Device
is fix on the way
Click to expand...
Click to collapse
same here
same
the same
The same
http://flashtool.net/disabledrivers.php
Someguyfromhell said:
http://flashtool.net/disabledrivers.php
Click to expand...
Click to collapse
Yeh tat didn't help..
as suggested in another forum, i disabled one of my usb root hubs in the device manager....it didnt give me that enumeration error and installed the driver but my pc only detects my phone in flash mode(even though i press the button for fastboot)...
It's a common problem with the fastboot drivers at the moment.
The really strange thing is that things still don't work properly if you have 8.1 with XP running in vmware.
Hopefully some smart cookie will work it out
Sent from my Xperia Arc S using XDA Premium 4 mobile app
try
i'll try this thanks
The same problem. I tried UpdateService and PCC , it still does't work!
Someguyfromhell said:
Apparently something was changed in 8.1, making the current method useless.
For now, nothing can be done, you will just have to wait until a new solution is made or move back to Windows 8 or any previous OS.
Click to expand...
Click to collapse
There is no known solution at the moment. Just wait until a solution is found or return to older version of Windows.
i m also having have problem ... in sonypcc its given unable to connect change to window 7 r later
altshift said:
i m also having have problem ... in sonypcc its given unable to connect change to window 7 r later
Click to expand...
Click to collapse
PCC works perfectly on Windows 7.
Someguyfromhell said:
PCC works perfectly on Windows 7.
Click to expand...
Click to collapse
bt mine is window 8.1
hi
my phone is Xperia Mini and recently i update to windows 8.1 .
but when i want conect it in flash mod or fast boot ,
the windows say "usb devise not recognized"
what have to do?
cmureza said:
hi
my phone is Xperia Mini and recently i update to windows 8.1 .
but when i want conect it in flash mod or fast boot ,
the windows say "usb devise not recognized"
what have to do?
Click to expand...
Click to collapse
Use another PC, which has earlier version of Windows. There are no fastboot drivers, which work with Windows 8.1, nor there is a solution to make the older ones work.
http://forum.xda-developers.com/showthread.php?t=2095087
This might help
esarve said:
http://forum.xda-developers.com/showthread.php?t=2095087
This might help
Click to expand...
Click to collapse
Works on Windows 8 but not on Windows 8.1.
Someguyfromhell said:
Works on Windows 8 but not on Windows 8.1.
Click to expand...
Click to collapse
If you have usb 3.0 you can try it is working http://forum.xda-developers.com/showthread.php?p=46997772
Sent from my MT11i using xda app-developers app
I found this guide - http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
I have USB 3.0, but I don't use Intel-based stuff. Maybe if I update to 8.1, I might try. For now, up to you to test, if you are willing to.
Hi,
Lately I have been trying to flash a rom to my htc one v (primou), but for some reason fastboot won't see the device. I was able to control the device with ADB (for booting into bootloader and fastboot).
I have already tried to install htc sync manager (for the drivers) and standalone htc drivers (some from the XDA forums). But so far I was unable to install any of the standalone drivers, because most of the time they give an error that my OS is not the correct version, not compatible, etc... :banghead:
I am currently on Windows 8.1
Has anybody else experienced this issue? And is there a possible solution for it?
Thanks in advance
PS: First post on XDA (finally got the guts to make an account)
Check this guide, it got my fast boot working :beer:
http://forum.xda-developers.com/showthread.php?p=46233842
Sent from my One V using xda app-developers app
Same problem here HTC sync works but in bootloader impossible to connect to usb can't flash kernel etc
Sent from my HTC Butterfly using xda app-developers app
Guys the problem is that the usb driver is now made by Microsoft and does not let you connect the phone in fastboot mode (and has problems with many other devices, not only phones). You need to change the driver to the one released by your USB manufacturer. That guide is for Intel drivers. Anyway I guess you can do it with any other manufacturers drivers.
Sent from my One V using xda app-developers app
I have USB 2.0 on original intel drivers and windows 8.1 and fastboot usb is still not working any suggestions
mr_nooby said:
Guys the problem is that the usb driver is now made by Microsoft and does not let you connect the phone in fastboot mode (and has problems with many other devices, not only phones). You need to change the driver to the one released by your USB manufacturer. That guide is for Intel drivers. Anyway I guess you can do it with any other manufacturers drivers.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Try disabling driver signature and reinstall HTC sync
Sent from my One V using xda app-developers app
still doesn't work
Bassie39 said:
still doesn't work
Click to expand...
Click to collapse
any news? usb 2..
I installed all original drivers for usb 2.0 on my Dell laptop disabled signed drivers did try everything but stil no luck. Still using adb an fastboot on my old winxp laptop
Sent from my HTC Butterfly using xda app-developers app
I'm also having the same issue + sync manager also not detecting the phone
DarkShadow69 said:
I'm also having the same issue + sync manager also not detecting the phone
Click to expand...
Click to collapse
Its all microsoft fail again. They put their crap drivers instead of your usb provider. So either you can look for drivers of ur usb provider, install them and set up windows in device manager to use them which is pain, or just look for a pc without win 8 I did the second thing.
Check my temporary solution:
http://forum.xda-developers.com/showthread.php?t=2598155
Fix for windows 8.1 update: http://forum.xda-developers.com/dro...er-fix-windows-8-1-update-2-fastboot-t2831385
hello. please help me, I do not know who to ask. at one point, my computer does not recognize the tablet. came out inscription unknown device. I tried to connect the tablet to other computers, all to no avail. then I made a factorial reset. that is completely erased tablet, in the hope that it will solve the problem. but he also failed to recognize. What shall I do?? I tried to connect via a USB flash drive OTG. but the tablet does not see any stick. I trust only your help
sergio1231 said:
hello. please help me, I do not know who to ask. at one point, my computer does not recognize the tablet. came out inscription unknown device. I tried to connect the tablet to other computers, all to no avail. then I made a factorial reset. that is completely erased tablet, in the hope that it will solve the problem. but he also failed to recognize. What shall I do?? I tried to connect via a USB flash drive OTG. but the tablet does not see any stick. I trust only your help
Click to expand...
Click to collapse
I have the same problem. I fixed it before on my nexus 10 by trying a different kernel. Let me me know if it helps.
Sent from my Nexus 7 using XDA Premium HD app
Do you have the correct drivers installed? If so, you could uninstall and reinstall them. Also, have you tried PTP connection rather than MTP?
Sent from my XT1080 using XDA Free mobile app
Jhall8 said:
Do you have the correct drivers installed? If so, you could uninstall and reinstall them. Also, have you tried PTP connection rather than MTP?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Been there done that and have always eventually been able to get it back so the computer sees the device as mtp. Wugs toolkit has always been helpful
To me. I like the step by step directions for manually updating the drivers and configuring them correctly in adb AND fastboot.
Bit I have come to an impass..........I am currently on the latest carbon nightly, with f2fs file storage for data and cache. My computer will not recognize the device in mtp and I am unable to pass files with a USB cable. I am wondering if my computer has to be compatible with f2fs, because iam sure that it is not. Will this make a difference PR should I once again uninstall and reinstall the drivers configuring them correctly?
Sent from my Nexus 7 using XDA Premium 4 mobile app
1
I'm telling you that there is no firmware on the tablet. what do you advise.
sergio1231 said:
I'm telling you that there is no firmware on the tablet. what do you advise.
Click to expand...
Click to collapse
Plug it in to a computer.
Boot into recovery if you have one
Adb devices......hopefully it shows and work from there.
Or boot into bootloader mode (after getting the twrp IMG)
Fastboot flash recovery......
Then you can side load your favorite OS
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Been there done that and have always eventually been able to get it back so the computer sees the device as mtp. Wugs toolkit has always been helpful
To me. I like the step by step directions for manually updating the drivers and configuring them correctly in adb AND fastboot.
Bit I have come to an impass..........I am currently on the latest carbon nightly, with f2fs file storage for data and cache. My computer will not recognize the device in mtp and I am unable to pass files with a USB cable. I am wondering if my computer has to be compatible with f2fs, because iam sure that it is not. Will this make a difference PR should I once again uninstall and reinstall the drivers configuring them correctly?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this worked for me im just passing along a possible fix http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post #3888 is the one I followed and been no problems since. also cpl days before in my sdk program google had updated drivers which may or may not have played a roll. before this I could not pass files with mtp only ptp would allow my device to appear. hope it helps!
edit also should note I did device manager then android devices removed drivers in there. plugged in n7 and the adb composite interface drivers installed and that was it. if that doesn't do it make sure sdk has updated google driver which should be 10.0.0 or something don't quite remember exact #
jblaze10 said:
this worked for me im just passing along a possible fix http://forum.xda-developers.com/showthread.php?t=2383146&page=389 post #3888 is the one I followed and been no problems since. also cpl days before in my sdk program google had updated drivers which may or may not have played a roll. before this I could not pass files with mtp only ptp would allow my device to appear. hope it helps!
edit also should note I did device manager then android devices removed drivers in there. plugged in n7 and the adb composite interface drivers installed and that was it. if that doesn't do it make sure sdk has updated google driver which should be 10.0.0 or something don't quite remember exact #
Click to expand...
Click to collapse
Thanks jblaze. I've been able to function pretty well usind adb. Sort of glad cuz it forced me to learn some pretty essential stuff I have been getting along with for far too long.
Sent from my Nexus 7 using XDA Premium 4 mobile app
aircooledbusses said:
Thanks jblaze. I've been able to function pretty well usind adb. Sort of glad cuz it forced me to learn some pretty essential stuff I have been getting along with for far too long.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ur right, I wish I knew more about it. I'm in that phase now where I'm digging thru Xda for info such as adb backups among other things. Hey no prob, take it easy.
Sent from my Nexus 7 using Tapatalk