The RCA Viking II, RCT6603W47M7, came to me crippled by default. I can't connect the device via USB.
I found an interesting item in the device's 'build.prop' -
"# USB Charge only function
ro.sys.usb.charging.only=yes".
Of course, I couldn't edit it because the device isn't rooted. It also has android 6.0, which makes it very difficult to root with a root app.
I tried everything I could possibly think of to no avail. I then installed "wifi file transfer pro" (Google Play), designed to allow file transfers between android and pc via a web browser. It works fine, but of course it can't manipulate read only files.
I then tried adb via wifi. Here's what happened:
1. Without the app
>adb connect 192.168.1.39:5555
>adb connect cannot connect to <ip>: A connection attempt failed because the
connected party did not properly respond after a period of time, or established
connection failed because connected host has failed to respond. (10060)
2. With the app
First command/result:
>adb connect 192.168.1.39:1234
>connected to 192.168.1.39:1234
Second command/result:
>adb shell
>error: no devices/emulators found
Conclusion: ADB works partially, but it's still crippled. Catch 22: PC still needs usb
connection, even if temporarily. Just as an aside: Is RCA violating anything here?
How can I use my USB port except for charging?
Any Results?
ftokc said:
The RCA Viking II, RCT6603W47M7, came to me crippled by default. I can't connect the device via USB.
I found an interesting item in the device's 'build.prop' -
"# USB Charge only function
ro.sys.usb.charging.only=yes".
Of course, I couldn't edit it because the device isn't rooted. It also has android 6.0, which makes it very difficult to root with a root app.
I tried everything I could possibly think of to no avail. I then installed "wifi file transfer pro" (Google Play), designed to allow file transfers between android and pc via a web browser. It works fine, but of course it can't manipulate read only files.
I then tried adb via wifi. Here's what happened:
1. Without the app
>adb connect 192.168.1.39:5555
>adb connect cannot connect to <ip>: A connection attempt failed because the
connected party did not properly respond after a period of time, or established
connection failed because connected host has failed to respond. (10060)
2. With the app
First command/result:
>adb connect 192.168.1.39:1234
>connected to 192.168.1.39:1234
Second command/result:
>adb shell
>error: no devices/emulators found
Conclusion: ADB works partially, but it's still crippled. Catch 22: PC still needs usb
connection, even if temporarily. Just as an aside: Is RCA violating anything here?
How can I use my USB port except for charging?
Click to expand...
Click to collapse
I just grabbed one of these on sale...
Did you ever find a way around the ADB Bug?
No! ; ) I gave up for a while.
RaiderWill said:
I just grabbed one of these on sale...
Did you ever find a way around the ADB Bug?
Click to expand...
Click to collapse
ftokc said:
No! ; ) I gave up for a while.
Click to expand...
Click to collapse
Do either of you two have a firmware backup I can use to try to get mine working? Bought it used from online retailer and it's running demo firmware. It says there is a settings lock.
RaiderWill said:
I just grabbed one of these on sale...
Did you ever find a way around the ADB Bug?
Click to expand...
Click to collapse
I'm pretty sure you have to use USB male to USB male cord.
I got my RCT6603W47 because it has a GPS, and every year or so search for any reports of modding success. Is anyone aware of another brand (badge) of the same hardware? cnet has the specs - just search "RCT6603W47 specs"
Related
As long as I have the requisite SDK files and a terminal on an Android device, or if I'm doing this programmatically in an app I'd develop, can I use adb to push a file from one device to another that's connected via USB? The devices will be a Nexus 4 and probably a Nexus 7. The N7 would be the sender, fwiw. I'm hoping that it's not required that the device executing the adb push commands be a computer as opposed to a mobile device.
I'm assuming that I can find a cable that's micro USB (if that's what it's called) at both ends to connect the two devices.
Is it possible to do the same thing via a Bluetooth connection? Or can adb only recognize a device connected via USB?
maigre said:
As long as I have the requisite SDK files and a terminal on an Android device, or if I'm doing this programmatically in an app I'd develop, can I use adb to push a file from one device to another that's connected via USB? The devices will be a Nexus 4 and probably a Nexus 7. The N7 would be the sender, fwiw. I'm hoping that it's not required that the device executing the adb push commands be a computer as opposed to a mobile device.
I'm assuming that I can find a cable that's micro USB (if that's what it's called) at both ends to connect the two devices.
Is it possible to do the same thing via a Bluetooth connection? Or can adb only recognize a device connected via USB?
Click to expand...
Click to collapse
If you tried this you would need a usb otg cable for connecting the devices. But I don't think ADB client software exists on phones just computers. Why would you want his when Android has multiple better choices? Turn on NFC and tap the device backs together for example.
shadowofdarkness said:
If you tried this you would need a usb otg cable for connecting the devices. But I don't think ADB client software exists on phones just computers. Why would you want his when Android has multiple better choices? Turn on NFC and tap the device backs together for example.
Click to expand...
Click to collapse
I have adb on my Nexus devices. I didn't even put it there, though BusyBox might have. It's in /system/bin. I can execute commands from a terminal. But I haven't tried it with another device. I'll get an OTG cable.
I'd use NFC or make one of the devices a ftp server, but that doesn't meet the needs of the project I’m working on. This isn't for personal use or convenience. I need to have one device send another a file within a certain physical environment that precludes those things.
maigre said:
I have adb on my Nexus devices. I didn't even put it there, though BusyBox might have. It's in /system/bin. I can execute commands from a terminal. But I haven't tried it with another device. I'll get an OTG cable.
I'd use NFC or make one of the devices a ftp server, but that doesn't meet the needs of the project I’m working on. This isn't for personal use or convenience. I need to have one device send another a file within a certain physical environment that precludes those things.
Click to expand...
Click to collapse
Hello Maigre,
Have you finished your experiment with the OTG cable ? I would try to do the same kind of operation.
And if I add and USB cable to the USB-OTG cable, do you know if it's working ? (I found only a micro-USB male to USB female OTG cable, and I would use it with a USB male to micro-USB male cable).
Thank you in advance,
Greg
Hi all. What I need is a way to control Android device (s) from PC via Wi-Fi. I found a lot of apps (and Desktop programs) to do it, but I didn't found a way to View OR control the Android device WITHOUT ROOT. I work on the company which asked me to find a way to do this without root with their Android devices. After googling a lot I started to think that where is no way to do this, because either way I need to root them . Is it true or maybe there is somewhere an app which could do this? It doesn't care if it's paid or not.
I have downloaded and tester these apps:
MyMobiler - Doesn't work because when I restart Android device, app doesn't start WiFi, just keyboard mode only. I need that when the app starts it should run itself and start WiFi automatically.
VMLite VNC Server - Don't know why but it didn't worked for me. Just cannot start server from the browser.
Thank you for any responses and appreciate any help.
What error messages do you get from vmlite vnc server? Make sure you enable USB debugging. We have tens of thousands of users using our app, and your device should work.
Well, actually now I tried to launch VMLite VNC one more time and IT WORKED (don't know how, because earlier I tried it and I was unable to enter to VNC Viewer in the Browser). So yeah, in this case it works perfectly now, but I just realized, that I have no way of connected more Android devices. Because what I need to do is to connect multiple Android devices to computer with USB (as I understand it's required for the first time) and when use it with WiFi. For now I see that I only capable of connecting single Android device with desktop program and everytime I want to connect to Android deice from computer, I need to connect it via USB (where is no way to save Android devices to use it any time I want to via WiFi). Or am I wrong? And it is a problem because in my company all Android devices are far away from each other. Anyway, thank your for such an awesome app, I really don't know how it is capable of connecting to my Android device WITHOUT ROOT (because I found like 10 apps, read a lot of forums, and every solution was with ROOTED devices, I am very interseting of the actual app functionality), but thank you.
You can connect to multiple devices using multiple USB cables. There is a drop down list to display devices, and you choose one by one to start the server. Alternatively, you can write some scripts to auto start the vnc servers.
There are quite some testing companies using our app this way to automate regression tests.
Alternatively, you can write some scripts to auto start the vnc servers.
Click to expand...
Click to collapse
Can I get more information about it? Thank you.
Basically you can automate the starting process using adb command:
adb shell "am start -a android.intent.action.MAIN -n com.vmlite.vncserver/.MainActivity"
adb shell /data/data/com.vmlite.vncserver/files/vmlitevncserver
Deimantas007 said:
Can I get more information about it? Thank you.
Click to expand...
Click to collapse
Thank you for this script (it's very cool, I didn't know this kind of stuff before), but it requires USB connection as well.
I googled a few things and found this app - ADB Wireless (no-root) on Google Play Store. Basically it connects ADB via WiFi and I don't need no USB cable and connection with it. But VMLite Android App Controller program on my Desktop doesn't recognize it (it requires USB connection). Can I actually connect Android device with PC with this method or I am missing something and there is no way of doing it with this method? Thank you (I promise, this is the last question from me, no more dumb questions).
I don't think it will work for you. You mentioned your android device will reboot, right?
If your device gets rebooted, you will have to use a USB connection to a PC. the ADB wireless app has same requirement.
Steps to get it working: (from ADB Wireless app page)
1. Enable USB Debugging on your phone.
2. Connect your phone via usb cable to your PC.
3. Run adb tcpip 5555.
4. Run ADB Wireless (no root).
5. Connect to the IP address.
Deimantas007 said:
Thank you for this script (it's very cool, I didn't know this kind of stuff before), but it requires USB connection as well.
I googled a few things and found this app - ADB Wireless (no-root) on Google Play Store. Basically it connects ADB via WiFi and I don't need no USB cable and connection with it. But VMLite Android App Controller program on my Desktop doesn't recognize it (it requires USB connection). Can I actually connect Android device with PC with this method or I am missing something and there is no way of doing it with this method? Thank you (I promise, this is the last question from me, no more dumb questions).
Click to expand...
Click to collapse
huisinro said:
I don't think it will work for you. You mentioned your android device will reboot, right?
If your device gets rebooted, you will have to use a USB connection to a PC. the ADB wireless app has same requirement.
Steps to get it working: (from ADB Wireless app page)
1. Enable USB Debugging on your phone.
2. Connect your phone via usb cable to your PC.
3. Run adb tcpip 5555.
4. Run ADB Wireless (no root).
5. Connect to the IP address.
Click to expand...
Click to collapse
What's right. It needs to connect my phone via USB. But I thought that maybe there is a way to automate this process, I mean maybe there is a solution to TURN DEBUGGING MODE between phone and pc programs via WiFi connection (not USB) and communicate with VMLite VNC Server program on startup. Either way, again, thank you for your software (app). I will say to my boss that we need to stay where we are at the moment. It's just awesome to have an app which doesn't require ROOT.
--Edit--
This is finally solved. There was a problem with my computer's ADB RSA key, so I simply had to delete the key file and rerun ADB and I Received the RSA Key Fingerprint window instantly on my G3.
For the full description of the problem look here:
I'm having issues trying to root my phone. I'm using the ioroot method mentioned here.
I get to "* daemon started successfully *" then nothing. After a lot of troubleshooting I know it's because my phone won't allow access by my computer. I never receive the RSA Fingerprint window allowing my computer access to my phone. Here's what all I've tried:
-Put phone into Internet>Ethernet mode (and I've also tried Internet>Modem, MTP and Camera modes as well just to say I did).
-Enable Developer Options and enable USB Debugging.
-Installed the drivers linked in the ioroot page (I've also downloaded the drivers directly from LG - believe it or not ... it's the same file).
-Installed the Verizon Software Assistant from the phone after connecting to the computer.
-Updated my ADB version with the SDK Manager.
-Used different USB ports on my computer as well as two different USB cables (one of which came with the G3).
-Checked Device Manager, all is as it should be and no unrecognized devices.
When I ran the adb server without the ioroot batch file, typing "adb devices" would return my phone's serial followed by "offline." It did this until I updated ADB; then when typing "adb devices" it would return the serial followed by "unauthorized." I've tried all various methods and combinations of switching adb debugging on and off, switching developer options on and off, installing and uninstalling and reinstalling the LG drivers, unplugging and replugging the USB cable, power-cycling all devices including myself at night, doing these methods with long pauses in between (10 minutes to ensure I wasn't being impatient), scratching my head, drinking more coffee, switching to rum and swearing at all devices but nothing seems to make a difference.
What am I missing?
I've got the Verizon LG G3 in White (LG-VS985W)
Software version VS98510B
Windows laptop running Vista 32 bit (I know I know, "eeew Vista")
I was able to obtain root using a different computer, here's what I tried with my laptop after gaining root to get it and my G3 on speaking terms:
-Deleted the ADB_Keys file on the G3 (/data/misc/adb/adb_key): no change.
-Compared running Windows services between Vista and 8.1 and started services which were running on 8.1 but not vista: no change.
Here was the resolution:
There turned out to be a problem with my laptop's ADB RSA key. I'm assuming my G3 was rejecting a bad key and disallowing my laptop to connect to it via ADB.
ADB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's profile (C:\Users\*username*\.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile\.android), the file is simply named "adbkey" with no extension. If there is no key file when ADB runs, it will generate one automatically.
Mine was located in my user folder (C:\Users\*username*\.android\). All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. I instantly received the RSA Fingerprint Key window on my G3 allowing connection between the two devices. Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. I went back to the C:\Users\*username*\.android\ folder and sure enought there were new "adbkey" and "adbkey.pub" files.
Problem finally fixed!
Here are some VERY useful links which helped me come to this fix:
How ADB enables a secure connection
Reconstructing ADB's RSA key file
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
markfm said:
Try using this set of Vertizon g3 drivers: https://mega.co.nz/#!58YHAZaQ!yNlgZG1m7toHBZp_0HF1jSQ66gMoZmmiDrNq9W5aJIc
Open the .zip, run the .msi file on Windows.
I do not run the G3's auto-install software when I plug it into the PC.
I do set the G3 to "PTP" USB before initially connecting to the PC.
The adb file in the ioroot "bts" subfolder should be okay to run on Windows.
When the phone is attached to the PC, change its USB connection type to Internet, with submenu type Ethernet. At least on my phone, right when I change the phone connection to Internet/Ethernet is when I get the phone popup to accept the PC's RSA fingerprint.
If I then run "adb devices" on my PC, I'll see the random ID followed by "attached", which means I have a good connection. If this doesn't happen, unplug, then replug, the USB connection at the PC side.
Then I can "cd .." and run ioroot.bat.
Good luck!
Click to expand...
Click to collapse
... no dice.
Ok, I'm switching to my Windows 8.1 machine (my laptop is my server and android-dirty-work machine).
So it worked without hesitation on my 8.1 machine. I used the drivers listed in the ioroot thread (same as the drivers from LG) and the process went off without a hitch. I have no idea why my Vista machine and G3 don't get along but I'll need to figure it out when I do further adb work because I use my laptop for that.
Thank you markfm for the extra drivers.
I'll call this solved for now but if I find out further reasons why it didn't work I'll post it here for others who have similar struggles.
Ok I finally solved this. It turned out there was something wrong with my laptop's ADB RSA key. All I had to do was delete the key file, run the ADB Server and connect the phone. ADB will automatically generate an RSA key if none exists. The RSA key was located in C:\Users\*username*\.android and was simply named "adbkey" with no extension. There was also a file named adbkey.pub (Microsoft Publisher) which I'm assuming is a viewable version of the key. I deleted both of these, re-ran the ADB server and voila I instantly received the RSA Key Fingerprint confirmation window on my G3.
Done and done!
unable to generate RSA key on my MCB
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
scooterd said:
I've read and re-read all the entries addressing this issue. I have a black G3 and am using a 2013 Mac Book Pro. I've followed the instructions to the letter many times but with no success. I'm at a loss. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
You'll have to bear with me because I'm not familiar with Mac file structure.
I would start from scratch. Do all these before trying to run adb again.
On your computer:
-Delete adbkey & adbkey.pub from the .android folder (I'm not sure where that is on a Mac, Home\.android?).
-I'm not sure if Macs have a device manager, but check that your phone is correctly recognized and the drivers are installed properly.
On your phone:
-Ensure you've got developer features unlocked
-Double check that you've got usb debugging enabled.
-Tap the "Revoke USB Debugging Authorizations" button below USB debugging in developer options.
-When you're plugged in be sure to set your connection to Internet >>Ethernet (you'll see the debugging icon in the notification bar if it's connected right).
I know a lot of that is basic and redundant but if it's all done correctly then it should work. If it doesn't work it gives us a good starting point to troubleshoot.
If you want to test it open terminal, change directory to the bts folder in the ioroot folder and start adb (adb start-server), with everything done right you should get the rsa window on your phone right now. Type "adb devices" and see what comes back.
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Use whatever mode will enable USB Debugging. If Internet>>Ethernet doesn't work then use any other mode that will. It's not necessarily important what mode your phone is in, but what mode will allow USB Debugging. If you have it in MTP, PTP, Camera or any other, and you have the USB Debugging icon in the notification bar, try the "adb devices" command and if it returns "*serial* device" then you should be good to go to root.
Once your phone has enabled USB Debugging and accepted the RSA key from your computer then the connection is made and your phone will accept the ioroot commands.
scooterd said:
Thanks for the assistance. I never could get anywhere with my MBP so I used Windows. I downloaded the drivers and got the RSA key after revoking all prior authorizations. However, but my computer still won't see my G3 in internet/usb debugging mode. It reads it in MTP, PTP and USB charge mode. But that's it. I've rooted numerous phones before, mostly Samsung, but this one has me stumped. Any ideas?
Click to expand...
Click to collapse
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
scooterd said:
Yes it is a Verizon VS985. I bought it last week. I have four options, charge, MTP, internet and PTP when I connect my phone to the PC. I get usb debugging under either ethernet or modem. Device Manegr sees my phone and I get the RSA key. I never get a terminal which let's me know something isn't right. This is truly weird but I won't give up. I'll start over and see what happens. Again, thanks for your patience.
Click to expand...
Click to collapse
No problem at all, happy to help! It sounds like you have everything set up properly, however the terminal doesn't open automatically (you need to do it manually). But you shouldn't need to open the terminal to get ioroot to work, after you've unzipped the ioroot.zip file, simply navigate to the ioroot folder, right-click on ioroot.bat and choose Run as Administrator. That should run through the entire process for you.
If you want to test your adb connection (testing not required for ioroot to work) you'll need to open the command prompt manually. Press Windows Key+R, in the run window, type cmd and press enter, this will open the command prompt. When you're in the command prompt, you'll need to change directory to the location of adb.exe in the bts folder inside the ioroot folder. Mine was in a folder named android on my C drive so the address looked something like this: C:\android\ioroot\bts the command you'll type in command prompt would be: cd C:\android\ioroot\bts then press enter. Then you can type adb devices and see if you're connected properly.
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
---------- Post added at 04:33 PM ---------- Previous post was at 03:46 PM ----------
scooterd said:
Okay. Here's where we are. I did everything you suggested. I got the RSA key and the G3 went into recovery mode. I toggeld down to the appropriate command and hit the power button. The little green guy fell over with the dreaded red triange and I got the message "This version of ioroot does not support your device/firmware combo. Please downgrade to previously supported software version. My G3 is running VS98510B. I can't post in the devlopment section but wonder if a software update prevents root the the version being used. Just a question but at least I know I'm not going crazy.
Click to expand...
Click to collapse
You sir are a genious. After changing my USB cord, I'm rooted and all is well in the world. It's always the little things that matter
My Pleasure! It's the little things that matter and the little things that kill!! I'm glad you're finally victorious!:laugh:
EDIT: Nevermind, I got it to work through Internet>Ethernet.
postal302 said:
Is your phone a Verizon Model (VS985)? I'm assuming not because I don't have PTP mode on my G3. If it's not Verizon, the ioroot method suggests using PTP mode.
Click to expand...
Click to collapse
Hi, hope this thread is somewhat still alive. sorry for the late add on... please help.
Sorry I'm a complete moron when it comes to rooting and ADB / RSA stuff and have no idea what exactly i am doing but for some reason my macbook won't allow me to authorize my oneplus. the authorize computer dialog box never pops up however i get a notification when my phone is plugged in that debugging is active. developer options have been reset, multiple usb cables have been used, and authorization has been revoked multiple times as well.
Im not sure how to access my adb settings on mac and when i attempt to go into terminal and try kill-server / start-server commands i get error messages as commands are not recognized.
Any help is appreciated as i can no longer use stock rom on OPO and i can't go about rooting my device
Wrong forum area -- this is for the Verizon LG G3 smartphone.
Same here! WITH NEXUS 7
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Jesusmaryqueen said:
Tried all the methods and spent almost 20hrs experimenting to retrieve rsa fingerprint, but in vain
Can you please suggest any remedy?
I cant install any os and unfortunately, my status bar and softkeys disappeared after using softkeyz apk...Dont tell to delete dalvaik data and cache[ it didnt work]
Please...
Click to expand...
Click to collapse
It is also possible to overcome the situation, by installing Mobilego software on your PC and follow the instructions accordingly (connecting your android using usb & debugging etc,.). You will get a RSA fingerprint request.. Easy Once it's done, u can close the mobilego software in the PC and open someother software for example Bacon root toolkit for oneplus one etc etc.. Hope this helps
adbkey doesn't exist
I don't know what i did wrong before, but my computer just DOES NOT have adbkey and adbkey.pub anywhere! First, i thought it was my phone's fault. Then, i tested in a different pc, and it worked. How do i generate those keys? There are no helpful answers in the internet yet...
Background:
I have a rooted SM-G900V (Verizon Galaxy S5) running Lollipop with a broken screen. I have Titanium Backup installed and it was supposed to be running weekly but wasn't. I have recovered my photos, contacts, etc. by connecting to my PC and copying the internal storage and from my gmail restore to a new GS5. I want to recover app data from a couple apps. The phone has USB debug turned on and I can connect with ADB.
I thought I could just run an ADB backup, but apparently in order for the backup to initiate I have to press a button on the lower right of the screen...which is broken. I suppose if I could connect via WiFi and then use a MHL cable I could use a keyboard/mouse to click the button on the phone but I don't have a MHL cable right now and I don't know if that would work anyway (WiFi ADB hasn't worked for me to this point).
THE QUESTION:
I've done a lot of reading and found a number of ADB options that sounded viable, but have not been successful. I have TitaniumBackup installed and thought that I could launch the "backup all" batch process but don't see how to make that happen. I have a new GS5 that is identical setup so I could record some actions on that one and play them on the broken one potentially.
I'm open to any suggestions.
bkenobi69 said:
......... THE QUESTION: I've done a lot of reading and found a number of ADB options that sounded viable, but have not been successful..........
Click to expand...
Click to collapse
The only thing I can think of is to guide you to the following thread that should, hopefully, be what you need.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
I really appreciate the suggestion. FWIW, I sort of came up with a similar approach myself that I almost have working. I turned on ADB WiFi on the device and then plugged in my wireless USB mouse/keyboard. I set up a script that performs a screen capture every 2 seconds and downloads it locally. With Windows7 image viewer, it automatically updates when the image changes so I get a slide show of what's happening on screen. The only issue I have is that the SD card isn't set up for TitaniumBackup apparently since I get an error when I select the backup action. If I can get TitaniumBackup set up correctly, I should be golden!
Thanks for posting that link. Ironically, the solution I developed was very similar in concept. I will give a short description for others who may need to recover data from a phone with a broken screen.
Prerequisites:
* TitaniumBackup - This can be installed from the Play store even if the phone is not functioning
* USB debug mode enabled - Without this, you are stuck. The only issue here is newer phones don't always enable MTP on connection. My old on did but the new one does not. If it doesn't connect via MTP, you will need to install MTPEnabler or similar.
* USB keyboard/mouse combination
* USB cable
* Charged fully functional phone sans screen
* ADB software - You must have the same version on the phone and PC. If not, it won't work reliably/at all. I went with fastboot_adb(1.0.32)_071114_r21 since I have 1.0.32 on my SM-G900V.
Basic steps:
1) Unpack the ADB software on your PC in a convenient location (C:\ADB)
2) Connect phone to PC via USB
3) Send command to enable WiFi ADB connection
4) Disconnect phone from USB
5) Connect ADB via WiFi
6) Run following batch script:
:loop
adb shell screencap /sdcard/screen.png
del screen.png
adb pull /sdcard/screen.png
echo captured
timeout /t 2
goto loop
Click to expand...
Click to collapse
This will dump a screen shot every 2 seconds
7) Open screen.png in Windows image viewer. It should automatically update when the image is refreshed.
8) Type "launch titaniumbackup" and press enter on wireless keyboard.
9) Using either tab or mouse, select the check box to launch TB.
10) Using either tab or mouse, select "menu" from upper right.
11) Using mouse, select "batch actions" from the list.
12) Using mouse, select "RUN" next to "Backup all user apps" from the list.
If all went well, you now have your phone backup up all application data to your SD card which can be easily used on a new phone to restore data.
NOTE:
It may be possible to also use the built-in ADB backup function. I attempted this at one point, but it requires selecting a button in the lower right on the phone. Since I was using ADB over USB at the time, I could not click the button on the phone since I only had one device connected (no hub). If you have a hub it may be possible to use that approach. Alternately, if you use ADB over WiFi, it should also work. However, be aware that there is no way to see where you are clicking or confirm that it worked other than looking at the files on the SD card as ADB backup doesn't appear to give any feedback. Also, this isn't as easy as TB when it comes to restoring as you either have to backup every app one at a time or all together. When restoring, it's also a one shot deal so you can't select specific apps to restore from a larger set.
Hey Guys,
Been lurking for a while. I want to get into some Android development. I bought a cheap Galaxy Tab s SM-T800 from ebay. It was a retail unit, so came with the usual retail protection, but that was no issue, I've reflashed it and rooted it, it is now running 6.0.1 with build number MMb29K.T800XXU1CRJ1.
The issue is, there are a bunch of apps and files that appear to be left over from the retail demo mode, and I can't remove them. The apps won't uninstall, it just says "uninstall unsuccessful", and the files, when I try to delete them, it just says "failed to delete".
Even after freshly restoring the new firmware, the storage on this device is pretty much zero, a lot of the space being taken up with the files and apps that I can't remove.
There was just about enough space remaining to install System App Remover, but that couldn't delete the files and apps either.
How are these files being write protected? How do I go about removing the write protection? I'm wondering if this device, because it was a retail demo unit, was configured with some kind of write protected partition, which is why the storage is so low, and why I can't delete the apps?
Any thoughts, this is driving me nuts.
Thanks
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
jwoegerbauer said:
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
Click to expand...
Click to collapse
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
DotNetDude said:
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
Click to expand...
Click to collapse
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
jwoegerbauer said:
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
Click to expand...
Click to collapse
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
DotNetDude said:
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
Click to expand...
Click to collapse
I realise I am responding to my own message!
Now that I am running with adb insecure, I have realisd that the USB debugging mode from developer settings is working in reverse. That is, if I enable it, the tab detaches form the PC. If I disable it, the tab reconnects to the pc. However with that setting disabled, and the pc connected, when I then run the command adb devices, it says there are no devices connected (even though I can browse to the tablet through windows explorer)
From within the adb insecure app on the tablet, when I enable the app, I can see it displays a message that says USB debugging is disabled.
I have no idea what is going on here...
Any help much appreciated?
Thanks
@DotNetDude
May be reading this helps.
jwoegerbauer said:
@DotNetDude
May be reading this helps.
Click to expand...
Click to collapse
Thanks for this. Actually, adbd insecure was just causing more problems. In the end I have resolved this by extracting the PIT file and re-partitioning. Firmware then restored correctly and all the problems are now gone, and there is plenty of free space remaining.