Related
Hi,
I have a Spice Mi-270 dual sim android 2.2 phone.Searching on the internet I came across an article where the procedure for installing the apps by default to sdcard is possible for non rooted phones.I tried it but when I type "adb devices" I get a blank list under list of devices attached.My phone came with the usb drivers, I have installed that.Tried installing Google USB driver package,revision 4.When the phone is plugged in get the message on the phone "USB Debugging started".Windows device manager shows "Android Phone" > Android Composite ADB Interface.Still my device is not detected with the "adb devices" command.I am using winxp pro sp3 32bit.Please Guide!
(If I have posted in the wrong section please inform me where to post)
I probably won't be helping. But on my un-rooted HTC Sensation i just have an app called app2sd. After i installed an app, if it's supported, i copy it to sd card.
Can't you just use that and save the hassle?
try this apps2sd
I have already installed the apps2sd but as said one can move the apps to sd if and only if supported by the app.Besides Android 2.2 by default provides the option to supported apps.How do I change the default install path to sd without rooting?
sounds like u need to root it and add the a2sd+ scripts OR root, install rom with a2sd+ and partition sd card accordingly.
do0b said:
sounds like u need to root it and add the a2sd+ scripts OR root, install rom with a2sd+ and partition sd card accordingly.
Click to expand...
Click to collapse
Sorry doOb but I am not looking at rooting my phone but use the option
adb shell pm setInstallLocation 2.
Why not root your phone? At the end or the day you still can unroot it. It's not like you flash to a different Rom and lost your stock Rom.
As far as I know your running froyo you already have move app to SD at the manage application in setting. There are free market app that can help you to move apps to SD with simple clicks without going to setting with the slow loading.
I'm afraid there are no default to app to SD unless you root your Rom and flash a2sd script like darktermor to make the whole process default. Better still, you also need to partition your card with an ext partition for it to work.
By the way... You should be able to adb shell your phone with a proper setup from your pc. You need to look for adb shell howto.
Sounds like your doing it from the wrong folder at cmd if your using windows. Try start cmd from the folder with adb.exe or set your system path to include the folder with adb.exe. I'm not with a pc now, I can't direct you. You have to look for it on what I mean.
By the way, can you also post the link for the article you found?
I have friends that can't root their phone. E.g HTC wildfire s
Sent from my HTC Legend using XDA App
darryl_co said:
Hi,
I have a Spice Mi-270 dual sim android 2.2 phone.Searching on the internet I came across an article where the procedure for installing the apps by default to sdcard is possible for non rooted phones.I tried it but when I type "adb devices" I get a blank list under list of devices attached.My phone came with the usb drivers, I have installed that.Tried installing Google USB driver package,revision 4.When the phone is plugged in get the message on the phone "USB Debugging started".Windows device manager shows "Android Phone" > Android Composite ADB Interface.Still my device is not detected with the "adb devices" command.I am using winxp pro sp3 32bit.Please Guide!
(If I have posted in the wrong section please inform me where to post)
Click to expand...
Click to collapse
Sounds like the original issue was the pc not seeing the device....I know this may be elementary, but do you have it in "charge only" mode and not in the disk drive mode?
"Sounds like your doing it from the wrong folder at cmd if your using windows. Try start cmd from the folder with adb.exe or set your system path to include the folder with adb.exe." - pysionx
I am starting cmd from the folder with adb.exe that laocated in platform-tools.If I was not doing so I would get the error " 'adb' is not recognized as an internal or external command operable program or batch file." and on typing adb devices in the cmd prompt I would not get the answer "list of devices"
pysionx - "By the way, can you also post the link for the article you found?"
Unfortunately no as this is my first post I am not allowed by the administrator to do so.Please Check out the attachment.Sorry for giving you the trouble to download attachment.
pfroyjr - "Sounds like the original issue was the pc not seeing the device"
If the pc does not see the device how do I get in Windows device manager showing "Android Phone" > Android Composite ADB Interface.
pfroyjr - "I know this may be elementary, but do you have it in "charge only" mode and not in the disk drive mode?"
I do not have it in "charge only" mode but in the disk drive mode, USB debugging started is the message received in the notification area.
But this causes hw to crash!
root_toor said:
But this causes hw to crash!
Click to expand...
Click to collapse
I sorry but I did not understand. what causes hardware to crash?
Google "Spice driver" I'll find a link if you can't. Windows is odd with its drivers sometimes. I remember the first time I ever used SDK I had to remove the default drivers and install the one from HTC but recently just installing the driver was good enough and I've only used adb and not the SDK. just a suggestion.
Sent from my HTC Glacier using xda premium
EDIT: I forgot which posting I was replying to, sorry....
I found THIS which sounds like it's an issue with the phone and maybe not the same Android OS that everyone else has....just what I read. Happy Googling my friend. Sounds like it's a cool device, just not quite up to par with adb.
I do have the drivers of my mobile Spice Mi-270 which was shipped along with the phone. The drivers files are of similar names with that of the google usb drivers for android except for the file versions.
Thanks pfroyjr for the link.It seems it is the problem with the phone itself as I am not the only one facing the problem with adb comand.
darryl_co said:
I do have the drivers of my mobile Spice Mi-270 which was shipped along with the phone. The drivers files are of similar names with that of the google usb drivers for android except for the file versions.
Thanks pfroyjr for the link.It seems it is the problem with the phone itself as I am not the only one facing the problem with adb comand.
Click to expand...
Click to collapse
Best advice is stay active searching for an answer...someone will eventually figure it out
I think it can be done with the help of adb .
Just run command from the folder having adb.exe file after connecting your phone in USB Debugging Mode.
"adb shell pm setInstallLocation 2"
YOu can change it to default by the following command.
"adb shell pm setInstallLocation 0"
Type the commands without quotes....
Hope it helps!!!
darryl_co said:
I have already installed the apps2sd but as said one can move the apps to sd if and only if supported by the app.Besides Android 2.2 by default provides the option to supported apps.How do I change the default install path to sd without rooting?
Click to expand...
Click to collapse
Hey try this adb command from the directory having adb.exe file after connecting your phone to your pc by enabling USB Debugging Mode on it.
adb shell pm setInstallLocation 2
You can change it back to default by this command ..
adb shell pm setInstallLocation 0
Hope it helps you ...
yagya said:
Hey try this adb command from the directory having adb.exe file after connecting your phone to your pc by enabling USB Debugging Mode on it.
adb shell pm setInstallLocation 2
You can change it back to default by this command ..
adb shell pm setInstallLocation 0
Hope it helps you ...
Click to expand...
Click to collapse
when I type "adb devices" I get a blank list under list of devices attached.When my phone is not listed how would the adb shell pm setInstallLocation command work ?
but The pc does see the device and I get in Windows device manager showing "Android Phone" > Android Composite ADB Interface.
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!
---------- Post added at 09:34 PM ---------- Previous post was at 09:33 PM ----------
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!
yagya said:
Try to install universal root/z4root/any other rooting app and shell commander in your phone then root your device temporarily (temporary root means root will be removed when you reboot)with universal root asn then in shell commander type the commands
su
pm SetInstallLocation 2
and then you can unroot your phone
Also if you want to change back do the same but change 2(externel) to 0(auto)
Hope it helped you!!!)
Click to expand...
Click to collapse
I installed universal androot and rooted the phone.
Instead of shell commander I installed Move2SD Enabler.The move2sd had three radio buttons Auto, Internal and External.Initially it displayed the radio button on Auto.I selected External and clicked apply.Now it shows External.Then I unrooted the phone.In Apps2SD I found many apps that were listed under phone only under movable apps.Few questions do arise
1.If I restore to factory defaults will the installation to external storage be resetted?
2.Whenever I Install new apps it gets installed in the phones internal storage and the I have to move to sd.Why is that so?
3.Even after moving to the sd some amount remains in the phone internal storage.why?
4.Can I check using shell commander if the install location has changed? what is the command? Do I have to root the phone again to use the command?
darryl_co said:
I installed universal androot and rooted the phone.
Instead of shell commander I installed Move2SD Enabler.The move2sd had three radio buttons Auto, Internal and External.Initially it displayed the radio button on Auto.I selected External and clicked apply.Now it shows External.Then I unrooted the phone.In Apps2SD I found many apps that were listed under phone only under movable apps.Few questions do arise
1.If I restore to factory defaults will the installation to external storage be resetted?
2.Whenever I Install new apps it gets installed in the phones internal storage and the I have to move to sd.Why is that so?
3.Even after moving to the sd some amount remains in the phone internal storage.why?
4.Can I check using shell commander if the install location has changed? what is the command? Do I have to root the phone again to use the command?
Click to expand...
Click to collapse
Restoring factory default settings will reset default install location to auto.
Since you used move to sd enabler it only makes all apps movable to sd but doesn't move them automatically.
System apps and Those apps that don't support app to sd by default can't be completely moved to sd card
Yes, you can check using shell commander but you need to riot you phone to use the command.
pm getInstallLocation
(returns default install location)
pm setInstallLocation 2
(installs app direct to external storage)
Sent from my GT-S5570 using XDA Premium App
Hey guys,
is it possible to access the internal storage via adb, without having a display?
My Galaxy SII Display is broken, but the rest should work.
usually i have to lock in with the security points that have to be connected (i dont know how that is called in english),
to allow access via usb.
now that the display does not work, i can not go that way.
so is it possible to access the internal storage via adb?
or do you have another way for me to get my data back?
i am not going to buy a new galaxy s2 and replacing the motherboard,
because its not worth it.
i have cm10.1 installed with dorimanx kernel, and root is allowed for adb and apps.
i never used adb, so i dont know how to start my search.
i also have the problem that i dont know how to look for that thing,
because im not english.
it would be nice if you can give me a start,
or another way to access the internal storage.
i also thougt about accessing via recovery.
i think i can go into recovery, and by pressing volume and power keys,
i can naviagte to mount data.
but im not sure about the steps,
so if anyone have a dorimanx 7.xx kernel,
can you please write the steps down for me?
thank you.
Grandtheftman said:
Hey guys,
is it possible to access the internal storage via adb, without having a display?
My Galaxy SII Display is broken, but the rest should work.
usually i have to lock in with the security points that have to be connected (i dont know how that is called in english),
to allow access via usb.
now that the display does not work, i can not go that way.
so is it possible to access the internal storage via adb?
or do you have another way for me to get my data back?
i am not going to buy a new galaxy s2 and replacing the motherboard,
because its not worth it.
i have cm10.1 installed with dorimanx kernel, and root is allowed for adb and apps.
i never used adb, so i dont know how to start my search.
i also have the problem that i dont know how to look for that thing,
because im not english.
it would be nice if you can give me a start,
or another way to access the internal storage.
i also thougt about accessing via recovery.
i think i can go into recovery, and by pressing volume and power keys,
i can naviagte to mount data.
but im not sure about the steps,
so if anyone have a dorimanx 7.xx kernel,
can you please write the steps down for me?
thank you.
Click to expand...
Click to collapse
if you can mount in recovery then mount everything in recovery,connect your device to PC and the open command prompt and navaigate to folder where you have set up android sdk.
now do the following
1) adb shell
2) now type ls -it'll list all folder and files.
3) now navigate to your sd-card (can't tell exact name for internal sd card) by typing cd <directory name>
4) you can list all files by using ls command.
5) Once you find the exact directory name of sd card and files to be recovered then type exit
6) now type adb pull /path/to/your/folder/filename.File will be saved in working directory...
i don't have s2,just helping you with some common adb stuffs.
btw you can use adb file managers which provides GUI.Like this one http://forum.xda-developers.com/showthread.php?t=1821601
adb
Connect the phone to system, Open terminal and do adb remount then adb shell.
Now do ls, you will be able to see all the folder and everything. Go to Sd-card folder and there you should have all your data.
There is and app ADBExplorer. I have never used this tool, but you can check it is GUI.
Thanks,
The ADBFileexplorer worked very well for me.
Just booted in recovery and started the explorer.jar in the adb folder.
Thank you for the tips.
This can be closed now
I've got a droid razr; rooted, stock rom
I broke the screen accidentally and now the screen isn't showing anything and touch isn't working.
I'd like to recover all the data off my device, but since it's locked, it won't budge. Drives won't mount when I plug it into my PC.
I've got a previous backup which is a little older, but i'm interested in backing up the actual databases (texts, call logs, etc) and system data too, along with my images and personal data.
Is there any way I can perform a whole backup while the system is locked like this?
I've already searched the forum for previous threads with similar issues, but I couldn't find one with a viable solution.
Any help is appreciated, thanks in advance.
Partial Update
Hey all-
I've partially solved my problem.
I was able to get ADB working miraculously. I downloaded the Motorola Device Manager and installed it, also downloaded the Android SDK/Java SDK;
Using the sdk manager i installed the google usb drivers (im not sure it helped any way, but just in case)
after that I ran through the process of adb
Code:
adb kill-server
adb start-server
**plug in device**
adb wait-for-device
adb get-serialno
From there I was able to use "adb shell" and navigate around the file system; used su, went to /data/system/ and did "mv gesture.key gesture.key.bak"
I then restarted my phone and did a repeat of wait-for-device, and get-serialno just to verify the phone was connecting properly.
I then browsed to my computer and amazingly, the drives mounted, my sdcard, and sdcard-ext as removable drives and I was able to view the contents.
-------
So now, I'm stuck here with a device that's NOT locked, I can view my files, and I can navigate the file system.
My end goal is to be able to copy everything from /data/ to /etc/ /system/ /root/ /sdcard*/ /vendor/ /xbin/ and any other system file that's not available through the mounted drives.
I'll keep this thread updated, and if anybody has any help or clue on how I'd do this, it'd be greatly appreciated.
So far I've tried variations on "adb pull" using / as a root dir; trying to find a way to use the shell to invoke scp, ssh, or some other file transfer, but I get no network connection. While in the adb shell and doing any file operations, I get an error stating that it's a read-only file system as well.
Fixed
I just wanted to let you all know that I've resolved my problem.
Let me state the issue again.
- Screen and touch broke.
- Device locked with pattern
- Rooted
- ICS - Stock Verizon ROM
- USB Mode was UMC, not PTP/MTP
- USB Debugging enabled
I used ADB to delete /data/system/gesture.key and rebooted, effectively removing the device lock, and allowing drives & data on my SD cards to show up in explorer after a reboot of the phone.
After futzing around for a bit, I realized the phone was tied to my Google account, and I remotely installed "Droid VNC Server" (app name org.onaips.vnc)
From there I found a way to activate the VNC server through the ADB command line
Source: android.stackexchange.com/a/31957
Code:
Application located in
/data/data/org.onaips.vnc/files
With a root shell, run this
chmod 766 /data/data/org.onaips.vnc/files/androidvncserver
Then you can execute the vnc server from the command line
/data/data/org.onaips.vnc/files/androidvncserver
Run this to forward the port
adb.exe forward tcp:5901 tcp:5901
On your VNC client, connect to localhost:5901
From there I was able to get access to my home screen and pulled the notification drop down and changed from USB Mass Storage to Camera/Media Mode
Rebooted the phone, started the vnc server again, connected to it and moved some files around to my SD Card
In another adb shell as root, I was able to copy files from /data/data/ (or anywhere else I wanted) and write them to anywhere on /sdcard-ext/
From there in another command shell, I ran adb pull /sdcard-ext/datafolderfile
=========================================================================
I believe this to be the overall gist of things, though I ran into hiccups along the way, while I was messing around, I changed some permissions which caused my su executable to break and only be allowed to run shortly after booting the phone; and also because of the broken screen, something would cause the phone to reboot every so often, breaking my connections, backups, file transfers, and etc
There's also a cool option in adb
Run
"adb backup" and it'll give you all the switches, you'll have to confirm the backup on your phone, so be sure to be running VNC and confirm it, but adb backup should be able to grab everything you need. Like I said it didn't work for me because my phone would reboot;
I hope everybody that sees this can benefit from it
Annafunny said:
So did you extract your data from your Razr with adb finally?
Click to expand...
Click to collapse
This thread is really old (4 years)... and the answer was provided.
To avoid further issues, closed.
After fighting with this for nearly a month and reading dozens of threads on xda, stack-overflow, etc... I finally figured out this issue, so I'm putting it here in hopes it saves someone else the frustration.
The issue presented itself on my HTC One (M8) running the ViperOne 6.1.0 ROM.
I'm putting this thread in the general section though since I've seen many people with very similar, if not the same issues on a wide variety of devices.
I believe the root cause of my particular issue may be the way HTC sets their devices to simply allow all debugging without authorization if the phones are s-off.
Mine is still s-on, but I have another M8 that's s-off with the exact same ROM as well as an s-off M9, and both of them go straight into debugging, no questions asked, no prompt.
I'm wondering if maybe the ROM was developed using a developer version of the phone and is just missing the prompt, or something similar, but this is just conjecture.
The basic problem was that, when I tried to connect ADB, it showed the phone as "unauthorized" and no matter what I did, the prompt would not come up on the phone to allow debugging.
Also of note, I was missing the "Revoke USB debugging authorizations" menu item entirely (I could search for it, but it wasn't actually there in the menu)
I tried many different combinations of changing drivers, USB modes, enabling/disabling debugging, different machines, deleting the public and private keys for ADB on the computer, etc... all to no avail.
Finally, after much research and testing, I found this comment on stack-overflow and figured out how to manually authorize keys.
Note: This will require root, a custom recovery, or some way of writing the the system partition (I used TWRP at first, then TerminalEmulator later)
The key was to understand what clicking the dialog to 'always allow' a machine actually does.
When you click to always allow, android appends the public key from ADB on the computer into a specific file on the phone.
Since my phone wouldn't connect in the first place though, I didn't have that file or understand the format, etc...
The file is called adb_keys, it is a file (not folder) which is located at: /data/misc/adb/
The format of this file is one public key per line.
Thus, there are a couple of ways to go about manually authorizing a machine for debugging.
First, manually building the adb_keys file. (This is what I did at first)
Second, copying an existing adb_keys file from another device (Which doesn't need root)
For manually building the adb_keys file, the first step is to find the public key on the computer.
For me (Windows 10) it was located at C:\Users\<my profile>\.android\adbkey.pub
For Linux and OSX, I believe it is at: ~/.android/adbkey.pub
If you only need to authorize one computer:
Simply copy the adbkey.pub onto the device location: /data/misc/adb/ and rename it from adbkey.pub to adb_keys
chmod 0644 and then reboot.
Now, the phone should accept debugging from the computer just as though you clicked the dialog.
If you need to authorize several computers...
As mentioned, the /data/misc/adb/adb_keys file is actually a list of all the keys which have debugging permissions, one key per line.
First, collect the adbkey.pub files from each computer you want to authorize.
Then, using a text editor which supports linux style line breaks (Notepad++ if on windows) simply create your own adb_keys file by appending the contents of each adbkey.pub file, putting a line break between each key
Now save the adb_keys file you just created, and put it on the phone's /data/misc/adb/ folder using whatever method you prefer, and chmod 0644
If you need to revoke debugging permissions, (like the menu option, if the menu option is missing)
Simply delete /data/misc/adb/adb_keys
And finally,
If you have access to another device (does not have to be rooted) and want to replicate its debugging permissions
Plug the 'donor' device into the computer first, then issue:
adb pull /data/misc/adb/adb_keys c:\temp\adb_keys
(Or replace "C:\temp\adb_keys" with whatever file path works for you)
Then, copy the file to the 'target' device in the same location (/data/misc/adb/adb_keys) and chmod 0644
I've tested all of these methods and they worked well.
In the end, I used the last method since my tablet had all the debugging permissions I wanted on my phone.
Thanks,I have the same issue with the same rom. I tried your solution and it worked.
Hi, I ran into this issue with my Moto G5 plus. The only difference is that I'm not missing the Revoke Auth option, even though using it does nothing for me, and I still fail to get the Authorization popup when connecting via USB/using ADB.
I tried the above method of copying the adbkey.pub file to my device directory, renaming, etc. I am doing something wrong and would like a hint.
I copied the adb_keys via Windows Explorer to my devices root directory. There was a /data/ directory, but only Titanium Backup had a subdirectory within, so I created .../misc/adb/, and placed the adb_keys file there.
I rebooted to the TWRP recovery Terminal, and navigated to the /data/misc/adb directory. I ran chmod, and the system could not find the file specified. Listing directory contents also showed the directory to be empty (yet when viewed in Explorer or LineageOS, it's visible).
Did I place the keys file in the wrong place?
Copying via windows explorer does not place it in the device root.
Inception
I was trying to Copy one donor device's Adb key file to my broken android phone to mirror it on my PC, Following the guide of another post, and somehow i stumbled across this post, after failing to copy from Donor device. Now i managed to copy the adb_key from Donor device but LOL my broken Android device is Unauthorized. What should i do? IS THERE ANY SOLUTION?
misuvi said:
I was trying to Copy one donor device's Adb key file to my broken android phone to mirror it on my PC, Following the guide of another post, and somehow i stumbled across this post, after failing to copy from Donor device. Now i managed to copy the adb_key from Donor device but LOL my broken Android device is Unauthorized. What should i do? IS THERE ANY SOLUTION?
Click to expand...
Click to collapse
Do you have any way of writing to the /data/misc/adb/adb_keys file on the broken device?
I think i just did!
NFSP G35 said:
Do you have any way of writing to the /data/misc/adb/adb_keys file on the broken device?
Click to expand...
Click to collapse
I rebooted into recovery mode, copied, but still the mirroring application is not working, still prompting for allowing USB debugging. Now i connected the donor device on That mirroring application and Saved the RSA of Mirroring application, and going once again. Wish me good luck
misuvi said:
I rebooted into recovery mode, copied, but still the mirroring application is not working, still prompting for allowing USB debugging. Now i connected the donor device on That mirroring application and Saved the RSA of Mirroring application, and going once again. Wish me good luck
Click to expand...
Click to collapse
Well, don't forget to post back if it worked :good:
Guess I did i good job
NFSP G35 said:
Well, don't forget to post back if it worked :good:
Click to expand...
Click to collapse
Well it didn't work since the Adb server of Cmd and mirroring application were different, so i searched for another application which has same server as Cmd, and luckily i found a great software by Genymobile, named scrcpy, from github, just one click on scrcpy-noconsole and boom? Thanks for all the help.
misuvi said:
Well it didn't work since the Adb server of Cmd and mirroring application were different, so i searched for another application which has same server as Cmd, and luckily i found a great software by Genymobile, named scrcpy, from github, just one click on scrcpy-noconsole and boom Thanks for all the help.
Click to expand...
Click to collapse
Cool, glad to help.
For a while, I looked for ways to get around this from a different angle (for example, making the keys match on the ADB server side) but I ran into some issues and ended up getting what I needed via the steps in the OP.
Glad you got it working though!
"And finally,"...you should have led with that
I cannot thank you enough! Other proposed solutions to this hellish problem made my head hurt. This was beautifully simple - copy file from the working device onto non-working, change permissions and BOOM! It works.
Thanks again, you're awesome!
Happy to help!
Oh my god, it's not a folder! Thank you so much! I was about to give up, this was driving me totally crazy. Everywhere on the internet they just keep repeating the same advice that did nothing, I actually created that as a folder and no wonder it wasn't working.
I still can't believe it's working now, ahhh...
can't believe in my eyes. work perfect for me. thanks you so much!!
I am trying to use the 'copy keys file from another device' method.
I've copied the adb_keys file to my PC.
Now, how do I copy that file from the PC to the data folder?
adb won't allow it as it's not authorised, what am I missing?
Thank you in advance for your help!
Bungle2000 said:
I am trying to use the 'copy keys file from another device' method.
I've copied the adb_keys file to my PC.
Now, how do I copy that file from the PC to the data folder?
adb won't allow it as it's not authorised, what am I missing?
Thank you in advance for your help!
Click to expand...
Click to collapse
You can't copy to the device through ADB until you get ADB authorized... that's the whole point... you have to use some other method to get the file there.
I used TWRP custom recovery to copy the file from an external SD card the folder.
If you don't have an external SD card, use USB MTP/PTP, Mass Storage, a USB OTG adapter and thumb drive... if you desperate, zip the file and email it to yourself... pretty much endless methods of actually getting the file onto the phone somehow.
But you'll need root (or a custom recovery) to copy the file from wherever it is on the device to the correct location (/data/misc/adb/adb_keys)
You could potentially use several methods, for example you could use terminal emulator or a root file explorer to get the file to the correct folder.
NFSP G35 said:
You can't copy to the device through ADB until you get ADB authorized... that's the whole point... you have to use some other method to get the file there.
I used TWRP custom recovery to copy the file from an external SD card the folder.
If you don't have an external SD card, use USB MTP/PTP, Mass Storage, a USB OTG adapter and thumb drive... if you desperate, zip the file and email it to yourself... pretty much endless methods of actually getting the file onto the phone somehow.
But you'll need root (or a custom recovery) to copy the file from wherever it is on the device to the correct location (/data/misc/adb/adb_keys)
You could potentially use several methods, for example you could use terminal emulator or a root file explorer to get the file to the correct folder.
Click to expand...
Click to collapse
Hey NFSP G35, thank you for the reply!
I figured there was something I was missing, I just don't know the steps to do it right.
I have a Moto X Play that has a broken screen, so no display, and does not accept touch input.
It powers on and is working as it was before the screen broke as far as I can tell, so I'm trying to connect it up to the PC to get all the data off it.
However, before it broke, something happened with the software that meant Google Play disappeared.
The device is stock Motorola device, so not rooted, no TWRP etc. USB debugging is enabled but not authorised.
What would you recommend is the best way to get the adb_keys onto the phone given the issues above?
Your help is greatly appreciated!
Sorry, given your circumstances, it's likely impossible or very difficult
?? Thanks, it worked perfectly on Samsung J6 run Evolution X 4.0
Thank you it's working
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.