T999 Connectivity to PC Issue [SOLVED] - Galaxy S III Q&A, Help & Troubleshooting

I had a HARD time trying to get the GS3 to connect to my PC (like a lot of other peps)
Here is my solution:
Update the pc completely using Microsoft Updates.
Download the following:[URL=http://depositfiles.com/files/jfh66znxv]http://depositfiles.com/files/jfh66znxv[/URL]
Un rar and copy the INF files (2) to your windows inf folder. I found that 1 of my original files (Microsoft installed) was actually the problem!
Install the Snapdragon Toolkit and install the Samsung driver using that software. (First option)
I already had done it via manual installs a number of times, but they never worked. This install using the toolkit worked.
(I only used it to install the Samsung Drivers)
Rebooted the PC and ran the toolkit again and saw the serial number in the ADB window, confirming a connection!
Rebooted the pc and connected the SG3 via the usb cable and it showed the files after a short moment!
All is Good!
Hope this helps someone make theirs work and alleviate all the aggrivation.
BTW:
There was not any problem with the Samsung software, It was the PC that had the problem!
I had that Samsung MTP error and the INF file installaion actually fixed that problem, so I included them in the file to download.
If this works for you, plz add a tag to this thread so that others will know this works.

This is i9300 forum mate wrong one buddy
Sent from my checkrom jellybean powered sgs 3

Related

My ADB & Vibrant Story

Mods, if this belongs elsewhere, feel free to move it.
I read many many threads about people's problems with adb on the vibrant and while there were no individual threads that matched exactly, little pieces from many helped me in my situation; in case someone else experiences what I had, this is what I did to fix it.
Environment:
Win7 Professional N x64
Vibrant (SGH-T959:2.1-update1/ECLAIR/UVJI) (this was the leaked ROM mid Sept)
Samsung x64 drivers from TGA_Gunnman's thread (forum.xda-developers.com/showthread.php?t=728929)
USB Debugging enabled
Problem:
I was able to get all the components of the phone recognized in device mgr & I was able to mount both the internal SD and my 8gb external SD cards, read & write to them with ease; I was even able to flash the leaked ROM via ODIN. I was NOT able to get adb to connect to my device.
C:\vibrant\adb devices
List of devices attached
T9596f3efa91 offline
I tried in recovery mode, no dice.
I had tried Droid Explorer, it was unable to find my device as well.
I had read somewhere that it was a driver problem, although dev mgr wasn't complaining and everything else appeared to be working just fine. One person noted they were able to use the Samsung Moment drivers from JuneFabric's website. I tried to install those drivers and was met with an error during the installation that said windows was unable to locate the file. Uninstalling, rebooting, reinstall (as many times as I had...) had no effect.
I grabbed USBDeview (thanks to masr1979's post in forum.xda-developers.com/showthread.php?t=735534&highlight=masr1979) and uninstalled every android related driver. Rebooted and when prompted for the drivers, tried the moment drivers only to face the same "unable to locate file" error. I got fed up and tried going back to the drivers from TGA_Gunnman's thread which brought
me back to the start. Atleast I was able to mount my sd cards.
Solution:
Not satisifed with this, I went to Samsung's website and found drivers for XP/Vista... i can't for the life of me re-navigate to that download page, but I have uploaded the drivers here.
After running USBDeview to nuke everythign samsung/android related (again) and rebooting, I plugged my phone back in - pointed it to the extracted folder for the attached drivers, ignored the "unsigned drivers!" error for all three devices and re-tested DroidExplorer. SUCCESS! Droid Explorer found my phone and adb (console) also shows my device attached! Everything is golden.
Summary
Random-assed drivers found on Samsung's site for XP/Vista (attached) matched what my Vibrant wanted on Win7x64 in order to get data and debugging connectivity.
Thanks
(edited for the attachment which didn't stick? & stupid 5min wait to post )

[SOLVED] Problem installing USB drivers for ADB

So I set out to root my phone and am in the process to trying to install the USB drivers so i can use ADB. At first, windows installed it's own drivers, which obviously didn't work. I tried to update the drivers in the device manager to the ones located in the google-usb directory, but it said i already had the latest installed.
Next i decided to uninstall the current drivers completely and start over. I then told it to install the drivers that were located the in the google-usb directory. It said no drivers were found. They were obviously there, so i manually gave it the "android_winusb.inf" driver as per the cyanogen mod wiki page instructions on installing the drivers. It then said that "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
I'm new to this so thanks for any help at all. I really want to learn my way around this kind of stuff.
Try it with your phone in mass storage mode with debugging on.
Still no luck. I've had it in debugging mode and charge only. Switched to disk drive mode and no change
Just download HTC Sync and use the drivers it provides. Should work for using adb.
Sent from my ADR6400L using XDA App
Now it can't even find HTC Sync on my computer... It's installed and i just used it the other day. Maybe it's something to do with the fact that i uninstalled the drivers it had? It can't communicate now?
This is what I used, worked great.
This might help also, he goes over installing the drivers a few minutes in.
Hope it works out for you.
setexascustoms said:
This is what I used, worked great.
This might help also, he goes over installing the drivers a few minutes in.
Hope it works out for you.
Click to expand...
Click to collapse
Problem solved!! I added the lines of code to the driver file to support the thunderbolt and it installed no problem. Thank you very much.
jwa0042 said:
Problem solved!! I added the lines of code to the driver file to support the thunderbolt and it installed no problem. Thank you very much.
Click to expand...
Click to collapse
You're more than welcome. You might re-title the post with [Solved] at the beginning so anyone with the same problem know to look here.
Just wanted to mention here that this was noted a while back and the CM Wiki will be updated with an easy way to correct this for Thunderbolt as well as other devices soon.
what's the solve?

[Q] Archos 80 G9 and Usb Driver problem

Goodmornig everyone..!
I just bought an Archos 80 G9 Turbo 16GB and I cannot connect it with my computer that runs Windows 7 64bit
When I plug it, it is detected as an Unknown Device (error code 43) and nothing is mounted.. (but tablet is in "slow charge")
In an old Win XP computer is working good, this made me think it's not completely tablet's fault..
here what I've tried, deeply searching on internet:
-Downloaded ADB android Drivers (in Archos site, on internet, various sources), forced installation of them, problem come out: Drivers are not for a 64 bit Os
-Uninstalled Kies, LG Pc suite and rebooted after every change..nothing changed
-Unactivate and reactivate after reboot Windows Media Player 12..no change
-Changed Usb Mode in tablet from MTP to PTP.. nothing changed
-Installed a lot of USB apps in Google Play and tried changing values..no change
-Upgraded tablet from GingerBread to ICS, deeply wiped and restored several times, and in every configuration, I allways had same results..
-Changed USB cable, several of them tested..and guess?? Nothing..eheh
-Tried shouting at it, tried kissing and asking for his forgiveness..but nothing
I'm stuck on Stock! i cannot upgrade it with XDA custom, I can only connect to pc via FTP server....!
Any Clues?!?!
Thank You to all!
1. To root and to enable SDE menu you need only adb driver
2. You can transfer archos.ext4.update files using FTP from pc to tablet
3. Recovery for flashing firmware update or custom kernel creates ramdisk which is seen as standard usb storage device- "just works"
You need to give full access (Everybody) to the folder where Android SDK is installed in Program Files (x86) and through Android SDK Manager select the second item "Android SDK Platfrom-tools for download.
This worked for me on Windows 7 Ultimate.
Ooops overread something... forget it!!!
Have you checked for the correct MTP driver package...
Regards,
scholbert
gen_scheisskopf said:
1. To root and to enable SDE menu you need only adb driver
2. You can transfer archos.ext4.update files using FTP from pc to tablet
3. Recovery for flashing firmware update or custom kernel creates ramdisk which is seen as standard usb storage device- "just works"
Click to expand...
Click to collapse
Only is an huge word, I have tried several dof them, and no one is working, no one is accepted by windows (it tells me they are not designed for the device or they are not for an x64 OS)
Strange thing, it accepted me usb drivers for Samsung Mobile, it installed them.. but not ADB from android... obviously, Samsung ones where not working with it..
xcen3x said:
You need to give full access (Everybody) to the folder where Android SDK is installed in Program Files (x86) and through Android SDK Manager select the second item "Android SDK Platfrom-tools for download.
This worked for me on Windows 7 Ultimate.
Click to expand...
Click to collapse
Installed drivers and quite everything with Android SDK, but nothing changed, even forcing these drivers... tried with access tweek, but.. nothing..
scholbert said:
Ooops overread something... forget it!!!
Have you checked for the correct MTP driver package...
Regards,
scholbert
Click to expand...
Click to collapse
Dowloaded and istalled a few from windows... the problem is, if it would be an MTP problem, I should not have it in PTP mode... I suppose...
EDIT: tried disabling Integrity Checks for non signed drivers with these string in cmd:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
nothing changed
indyjones83 said:
Only is an huge word, I have tried several dof them, and no one is working, no one is accepted by windows (it tells me they are not designed for the device or they are not for an x64 OS)
Strange thing, it accepted me usb drivers for Samsung Mobile, it installed them.. but not ADB from android... obviously, Samsung ones where not working with it..
Installed drivers and quite everything with Android SDK, but nothing changed, even forcing these drivers... tried with access tweek, but.. nothing..
Click to expand...
Click to collapse
For Gen9 you need Archos modified driver
gen_scheisskopf said:
For Gen9 you need Archos modified driver
Click to expand...
Click to collapse
These are the first one I tried.. From their site.. Not working.. Thankyou!
I wrote them in Contact and support in that site, copying and pasting the same I wrote here, they answered me, two days later.. Excited in what solution they could give me,from the heights of their knowledge, I suddenly opened and the answers was:
Please write the email in English.
Are they kidding me? This makes me suppose they have not even tried in reading it.. Well.. 1000 thanks for you and you support..!
Sent from my Optimus 2X using XDA
Second reply from Archos, this time they read it, but only first few lines..
their reply is:
"We invite you to connect the device to a 32 bits system and then to check if the Archos is seen by the pc."
Already done, and it's working with that (WIN XP)
Did you try to install manually the MTP driver from the device manager of the PC ?
YES.
any new clue from here?
Thankyou!
Try this
Sent from my ARCHOS 80G9 using XDA
1 thing, when you are plugging into your PC, are you plugging it into the main hub (rear of PC), or a front port?
I had a devil of a job getting mine to recognise the driver, in the it turned out it really needs to be plugged into the rear port, it may have been a conflict on my PC, but worth a shot.
pittnuma said:
1 thing, when you are plugging into your PC, are you plugging it into the main hub (rear of PC), or a front port?
I had a devil of a job getting mine to recognise the driver, in the it turned out it really needs to be plugged into the rear port, it may have been a conflict on my PC, but worth a shot.
Click to expand...
Click to collapse
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
indyjones83 said:
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
Click to expand...
Click to collapse
Did you try the link in my previous post? I'm running win7 64 bit and it worked for me!
Maybe just try adding the file in your USERPROFILE directory first!
Sent from my HTC Sensation using XDA
bobjbain said:
Did you try the link in my previous post? I'm running win7 64 bit and it worked for me!
Maybe just try adding the file in your USERPROFILE directory first!
Sent from my HTC Sensation using XDA
Click to expand...
Click to collapse
Yes, that one and a modified one.. the problem is, it remains as an "Unknown Device" (error 43).
I tried now to move that driver you suggested me in USERPROFILE (c:\USERS\"myname" and c:\USERS\"myname"\.android) is this you mean?
and same error: can't find in directory any compatible driver for the device. make sure it's done for a x64 system...
It seams to me device is not recognized at all.. not PTP or MTP or USB DEBUG....
but it works with win xp...! I tried again..!
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
indyjones83 said:
Yes, that one and a modified one.. the problem is, it remains as an "Unknown Device" (error 43).
I tried now to move that driver you suggested me in USERPROFILE (c:\USERS\"myname" and c:\USERS\"myname"\.android) is this you mean?
and same error: can't find in directory any compatible driver for the device. make sure it's done for a x64 system...
It seams to me device is not recognized at all.. not PTP or MTP or USB DEBUG....
but it works with win xp...! I tried again..!
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
Click to expand...
Click to collapse
OK try this :-
Download the naked universal drivers attached to this post and unzip somwhere!! (got this from the Sensation forum, would say thanks but I can't remember who posted them).
Attache your G9 then go into device manager.
Now find your badly installed driver and uninstall it. Keep doing this until all drivers are uninstalled.
Now unplug and reattach G9, let windows do it's thing. You will still have a excalamation next to "Android Drivers" at this point.
Right click on the driver in device manager and "Update Driver Software", then click "Browse My Computer....", now click on "Let Me Pick from a list...", then click the "Have Disk" button. Browse to the folder where you extracted the Universal Naked Drivers and select the andorid_winxusb.inf file.
If you get unsigned warnings click on the "trust me" or whatever it says.
Driver should now be installed.
The adb_usb.ini file is really for if you use adb, if you do it need to go in c:\users\you\.android directory (create the directory if it doesn't exist).
You can test adb connectivity by using "adb devices" from the command line.
Hope this helps
indyjones83 said:
Another doubt I have is: when I plug it to the wall charger I found on the box, it goes on "Slow Charge".. is it normal? why not fast charge or Normal? may be an hint?
Click to expand...
Click to collapse
I think this is probably because your USB cable only has 2 internal cables, not 4.
IIRC, the outside 2 are USB and data chat and the inside 2 are for 5v power.
If your G9 detects the cable doesn't have the two middle connections then it will do a slow charge regardless.
Are you using the cable you got with the G9??
bobjbain said:
I think this is probably because your USB cable only has 2 internal cables, not 4.
IIRC, the outside 2 are USB and data chat and the inside 2 are for 5v power.
If your G9 detects the cable doesn't have the two middle connections then it will do a slow charge regardless.
Are you using the cable you got with the G9??
Click to expand...
Click to collapse
Yes, I'm using the cable i got with the g9.. I could have a dual cable (the one they give to you with an external hdd), but it's mini usb, not micro...
bobjbain said:
OK try this :-
Download the naked universal drivers attached to this post and unzip somwhere!! (got this from the Sensation forum, would say thanks but I can't remember who posted them).
Attache your G9 then go into device manager.
Now find your badly installed driver and uninstall it. Keep doing this until all drivers are uninstalled.
Click to expand...
Click to collapse
And this is the problem.. I don't have any driver to uninstall, as if my device is an "Unknown Device" no service, no adb no mpt recognized.. only an "unknown device".. even with new drivers, the only driver it lets me install are Samsung drivers.. but obiously doesn't work!
I now tried in installing it as this samsung, just to have something to uninstall...
bobjbain said:
Now unplug and reattach G9, let windows do it's thing. You will still have a excalamation next to "Android Drivers" at this point.
Right click on the driver in device manager and "Update Driver Software", then click "Browse My Computer....", now click on "Let Me Pick from a list...", then click the "Have Disk" button. Browse to the folder where you extracted the Universal Naked Drivers and select the andorid_winxusb.inf file.
If you get unsigned warnings click on the "trust me" or whatever it says.
Driver should now be installed.
The adb_usb.ini file is really for if you use adb, if you do it need to go in c:\users\you\.android directory (create the directory if it doesn't exist).
You can test adb connectivity by using "adb devices" from the command line.
Hope this helps
Click to expand...
Click to collapse
You are really amazing, archos is not caring at all..
Before I tried your firs suggestion in USERDEVICE and for a minute it found my device as Error 10 and not Error 43 (unknown device)... and that's the only moment my pc saw the tablet...
Thankyou!!
indyjones83 said:
Yes, tried to connect it in every usb my laptop has, even tried in disconnecting every usb device and turned off the pc. After that I took off battery for a few minutes and started again.. no change... ERROR 43...!
In the old win xp pc I use front usb I installed 10 years ago, and works..!
ADB USB drivers from archos site are not recognized, it's not possible to manually select them.. I was able to select an old symbian driver I have in an old backup directory, but not that one... any clue?
Click to expand...
Click to collapse
I too have run across this problem--AFTER woprking for 6 months with it under ADB just fine. Not just my work computer, home devices as well. Did you ever get this fixed?

Samsung Galaxy S3 not recognized (with drivers)

I have installed Samsung USB Drivers manually and also tried Kies to install the newest drivers, but my Samsung Galaxy S3 still isn't recognized by my computer. What can I do?
EDIT: It only works sometimes, so when I plug it out and in like 10 times, maybe I'm lucky and it will connect once.
Rankiz said:
I have installed Samsung USB Drivers manually and also tried Kies to install the newest drivers, but my Samsung Galaxy S3 still isn't recognized by my computer. What can I do?
Click to expand...
Click to collapse
Switch off the phone.connect to PC.turn it on....it all surely get recognised...
Still don work means do a factory reset
Sent from my Micromax A60 using XDA
I have the same problem. My VSGS3 works with my W8 laptop but not my W7 desktop (at all). The only thing I can assume that it would be is MTP issues with Truecrypt (my desktop is encrypted). I cannot get it to work at all.
take a look at this thread...
http://forum.xda-developers.com/showthread.php?t=1652004&page=1
dont seem like there is a solution yet.
Really???? S3 Not Recognized?
Maybe I missed something in this thread but is this really the case??? The S3 cannot be recognized as a USB storage device by Windows? I accidentally left my SD card out and now have videos I need to transfer to PC, but cannot via email or any other means I can find. Anybody have a solution? I have installed the Samsung drivers but still not recognized . . . HELP!!!
gregn said:
Maybe I missed something in this thread but is this really the case??? The S3 cannot be recognized as a USB storage device by Windows? I accidentally left my SD card out and now have videos I need to transfer to PC, but cannot via email or any other means I can find. Anybody have a solution? I have installed the Samsung drivers but still not recognized . . . HELP!!!
Click to expand...
Click to collapse
No USB storage for GS3 internal memory.
Sent from my GT-I9300 using xda app-developers app
You can use MTP mode to copy the files to the computer.
The device will appear with a phone-logo in 'My Computer'
Just plug Samsung USB cable into USB port on a PC with the Samsung USB drivers installed and cut and paste as many GB as you want .SD Phone or EXT SD card via Windows Explorer as normal .
jje
This problem is quite depressing Has a restore fixed it for anyone?
I use mac OSX and after searching for a month or so, I couldnt find a solution to connect via USB. So now I use 'Air Droid' app from Play Store. Its pretty good and simple!! Plus, you can do alot more stuff like send or read SMS from PC.. Dont need to connect via USB anymore
I found that installing that rootkit installed the drivers to connect via USB - didnt root it just installed it for the drivers. THANKS!
I am having the same problem.
My Galaxy S3 charges when connected to computer via USB.
But is not detected in USB Debugging or regular mode.
Which windows version are u using. Try installing pdanet.exe on ur pc
Sent from my GT-I9300 using xda app-developers app
You must know what windows you use, 32 bit or 64 bit? Download Kies through Samsung website, make sure got right software.
Sent from my GT-I9300 using Tapatalk 2
If you are using x64 Windows 7 this will EXE file can be found here:
C:\Program Files (x86)\Samsung\Kies\USB Driver\SAMSUNG_USB_Driver_for_Mobile_Phones.exe
back this up and then you can remove KIES. This is all you need to have your phone connected without ever really needing KIES.
Or you can use the driver provided by the TOOLKIT that MSKIP has designed (thanks - love it).
Cheers,
try disabling usb debugging
it worked for me
AbdallaKhalid said:
try disabling usb debugging
it worked for me
Click to expand...
Click to collapse
nothing has worked for me. I have not tried the toolkit but I installed drivers from the TeamEpic's easy root as described by QBKing77 and those have not worked since I installed twrp
One more to this incredible situation :angel:
experienced the same on my win7 64 bit. I removed it on the faulty usb port to another one and then luckily the driver installation went fine. Weird but worked.
Sent from my GT-I9300 using xda app-developers app
YES!
Disabled USB Debugging and it worked!
Cheers @AbdallaKhalid

[Q] Trying to Restore Apps with Data (.bak) to cm 10.1

Hello;
This was my first time installing a Rom. I was fed up with my phone responding slowly and in time jams.
1-The first thing I did was install cwm recovery v6.0.2.7.
2-Then use the S3 tool kit available in xda to make a backup of all except system apps and internal storage data and it was stored in a .bak file. So that games and other apps keep their info as it is a hassle to start from the beginning.
3-Installed CM 10.1 nightly used in the instructions provided here.
All is okay up to here.
4-Tried to restore apps and app data through S3 tool kit but it won't display the data in the phone. I did enable the usb debugging on the cm10.1 (by pressing 7 times on the build name to enable the developers option and enabling usb debugging). I had the same problem when trying to do the backup in step 2, but it connected through the adb mode. This problem is that when ever I connect a device via usb windows installs the driver so every time I connect my phone windows installs the drivers.
5- When step 4 did not work I tried to restore using Holo Backup but no use no able to connect through to adb mode.
I can access the phone storage but I believe the appropriate drivers are not running when using the restore programs even though they are installed.
So the questions are:
1- Is there a way to fix the connection to be able to use S3 unified tool kit or if any one has dealt with the same problem?
2- Is there a way to restore the .bak file via cwm recovery?
3-For future use; An app or program that can be stored in the phone to avoid the use of a PC. The app or program would back-up contacts, sms text, apps and app data into the virtual sd or cloud to avoid deletion when "wipe data/ factory reset" after installing a rom.
I look forward to your replies.
Thank you.
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
wststreet said:
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
Click to expand...
Click to collapse
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
sub-80 said:
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
Click to expand...
Click to collapse
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
sub-80 said:
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
Click to expand...
Click to collapse
Tried ADB wifi but no success the pc says that there are no adb devices.
Also tried PDANet+ to install the drivers but software does not see the s3.
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
JJEgan said:
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
Click to expand...
Click to collapse
removed the .bak extension and placed it in the download folder of my virtual sd folder and pressed restore on cwm but nothing happened.
Could be because the backup is password protected?
Also tried to restore the file via titanium backup through the extract simple adb with and without the extension but only says analyzing file and remains that way for hours.

Categories

Resources