Database Users

Setting default install path in android

This post is to help you set your phones default install path to your phones sd card on any android device.
so here we go..............>>
1. First you have to enable USB debugging on your Android device from Settings > Applications > Development > USB debugging.
Now you need to download and install the Android SDK on your computer from google....please google it.
Once setup is downloaded and installed you click on Available Packages to the left.
should you get any error message at this point, enable “Force (url) in the Settings then from the list of available packages, select “Usb Driver package”, click on the Install Selected button in the bottom right corner and follow the prompts.
2. Connect your phone to your computer with a USB-cable. Your OS will prompt you to install new drivers.
Choose to install them from
C:\Program Files\Android\android-sdk\extras\google\usb_driver folder
when you are asked to install drivers
(If for some reason you are not asked to install drivers as it happens sometimes in windows 7. Go to device manager and look for your phone under the usb device list..............right click and choose update drivers....navigate to C:\Program Files\Android\android-sdk\extras\google\usb_driver folder" to update) If you do not know how to update then google it.
NOTE: You need not mount your device; you only need to plug-in the cable.
3. Next, run a command prompt and navigate to the Android-SDK/platform-tools folder. In Windows, this is done by selecting Run from the Start Menu (or by pressing Win+R) and typing cmd. You change drives in the command prompt by entering the drive letter followed by a colon ), and change folders with the CD command. For example, to enter the Android-SDK folder, simply type C: cd android-sdk.
4. Whiles in the Android-SDK/platform-tools folder, type in
adb devices
you should get a serial number starting with “H” in return. All you have to do next is enter
adb shell pm setInstallLocation 2
You’re done! Android will now install apps to the SD card by default.
To switch back to storing software on the internal memory,
enter
adb shell pm setInstallLocation 0
With everything done correctly you should not have that "annoying memory getting full" message anymore.

If you have a terminal application installed on your phone you can use also that for entering the commands and you should notice, too, that it works only with 2.x roms.
Sent from my Gingerbread on Dream using XDA App

Or you could use a utility:
http://forum.xda-developers.com/showthread.php?t=1765929

But how do you specify a specific directory?

Getting Error
I am getting error "/data/anr/traces.txt: Permission denied" when I give Command "adb shell pm setInstallLocation 2"
Please Help.....

On some updated SDK version its "set-install-location"

Hi,
I've done this and it worked. however I changed my sd card from 2Gb to 4Gb and now it will not work anymore.
I've redone the steps above and, got confirmation that [external] memory is being used, however when I want to install a new app I get the same error message "not enough space"
Android GT-S5830i
ver 2.3.6
Any suggestions
Thanks

[ROOT] VZW Note 7

First thanks to freeza and goonygugle
this is freezas method with a few adjustments from goonygugle and a little extra steps to get data on vzw
Files needed
You also need adb for this process if you dont already have it
Leaked Sprint Rom: https://www.androidfilehost.com/?fid=24651430732236681
Odin and verizon firmware, courtesy of Misterxtc
Sun7 Files: https://www.androidfilehost.com/?fid=24651430732236679 unzip this zip into a normal sun7 folder. Put the new sun7 folder into the folder that holds your adb file!
1) After downloading all the files unlock developer mode and enable usb debugging
2) Put the phone into download mode (vol-, Power, Home)
3) Connect the phone to the computer and open oden
4) Click AP and select the sprint file, wait for it to load and flash
5) The phone will reboot and go through a update process. when you get to a black screen force the phone into download mode again (for new settings menu allow first boot ~30mins then put into download mode)
6) Flash BL, CP and CSC in odin from the verizon firmware
7) After the flash it will be a long wait for first boot ~30mins (Can disconnect from computer)
8) You can skip setup. Go to settings and unlock developer options again and enable usb debugging
9) Plug the phone back in and don't forget to change from charging mode to file transfer
From freeza's post
10): Open a command prompt where your ADB executable and sun7 folder are.
11): Verify standard root access by typing "adb shell" then "su" If successful, type "exit" twice to get back to the command prompt.
12): Push the sun7 folder to your phone by typing "adb push sun7 /data/local/tmp/su"
13): Change permissions of contents in su to 777 by typing "adb shell chmod 0777 /data/local/tmp/su/*"
14): Launch adb shell by typing "adb shell"
15): Change directory to su by typing "cd data" "cd local" "cd tmp" "cd su"
16): Gain standard root privileges by typing "su"
17): Execute the SU script by typing "./root.sh"
Phone will reboot and you will have root but this leaves verizon without access to data
18) You will need a root explorer
19) Download stock verizon apn settings https://www.dropbox.com/s/x7m9v49a2eytmid/apns-conf.xml?dl=0
if you want to use different carriers download nexus 6p apn settings(includes verizon apn) https://www.dropbox.com/s/jqz3ps8xq492k8l/apns-conf.xml?dl=0
20) Copy the apns-conf to the phone
21) In a root explorer locate the apns-conf file you just transferred. Copy/Move it and navigate to system/etc
22) Delete that original apns-conf file in system/etc (contains sprint data info) and past the one you copied
23) Change the permissions to rw-r-r
24) Navigate to /data/data/com.android.providers.telephony/databases/ and delete telephony.db
25) Reboot your phone and everything should be up and running
Now you have a Samsung stock Note 7 with the only thing from Verizon being the network!

As of now stock messenger doesn't work for MMS, just use another messenger instead
Reboot requires any bluetooth devices to be paired again
Samsung cloud fix from jeffbob48
jeffbob48 said:
Here is the fix for samsung cloud https://mega.nz/#!v5JTFBwT!FAXwgY6VTGceerWJmt2pQ0xQEh07yiNw4AxNCPnAv10
1. Download zip and unzip it to storage of phone ( Do Not Flash... this zip cannot be flashed in any way)
2. copy file from zip to /system/omc/VZW
3. make sure it overwrites the old files
4.check to make sure that the permissions of all the files are rw- r-- r--
5. etc folder does not need to be changed, do not touch anything in etc folder
6. after you set the permissions reboot the phone
7. go check settings for samsung cloud now
Any donations would be much appreciated lol i worked really hard on fixing this for you guys and i have more fixes to come
Click to expand...
Click to collapse

Thanks for the Guide. I will give this a shot this weekend and see what happens.
~SG

Pit file
Is there an advantage to using the pit file? Under what circumstances would we need this?

coton said:
Is there an advantage to using the pit file? Under what circumstances would we need this?
Click to expand...
Click to collapse
I don't think so, I've dont it both ways. didn't notice a difference

Does this affect or trip Knox? Can you still use Samsung Pay and other Knox reliant apps when Rooted? The last Samsung I had was a Galaxy S3 and it was rooted long before Verizon enabled the Knox 'feature'.

Data fix didn't work for me. I'll have to run back through to see if I did something wrong.

azradiohead said:
Does this affect or trip Knox? Can you still use Samsung Pay and other Knox reliant apps when Rooted? The last Samsung I had was a Galaxy S3 and it was rooted long before Verizon enabled the Knox 'feature'.
Click to expand...
Click to collapse
Does not trip knox. NO you cannot use Android Pay or Samsung Pay if rooted. Same with other apps such as Playstation Vue, Snapchat, etc.

Has anyone noticed any signal issues or anything? I haven't gotten a chance to run it yet.

jal3223 said:
Has anyone noticed any signal issues or anything? I haven't gotten a chance to run it yet.
Click to expand...
Click to collapse
I don't have any

Verizon SM-N930V Root Verified
LRiley said:
First thanks to freeza and goonygugle
this is freezas method with a few adjustments from goonygugle and a little extra steps to get data on vzw
Files needed
You also need adb for this process if you dont already have it
Leaked Sprint Rom: https://www.androidfilehost.com/?fid=24651430732236681
Odin and verizon firmware, courtesy of Misterxtc
Sun7 Files: https://www.androidfilehost.com/?fid=24651430732236679 unzip this zip into a normal sun7 folder. Put the new sun7 folder into the folder that holds your adb file!
1) After downloading all the files unlock developer mode and enable usb debugging
2) Put the phone into download mode (vol-, Power, Home)
3) Connect the phone to the computer and open oden
4) Click AP and select the sprint file, wait for it to load and flash
5) The phone will reboot and go through a update process. when you get to a black screen force the phone into download mode again
6) Flash BL, CP and CSC (I've dont it with and without the pit file) in odin from the verizon firmware
7) After the flash it will be a long wait for first boot ~30mins (Can disconnect from computer)
8) You can skip setup. Go to settings and unlock developer options again and enable usb debugging
9) Plug the phone back in and don't forget to change from charging mode to file transfer
From freeza's post
10): Open a command prompt where your ADB executable and sun7 folder are.
11): Verify standard root access by typing "adb shell" then "su" If successful, type "exit" twice to get back to the command prompt.
12): Push the sun7 folder to your phone by typing "adb push sun7 /data/local/tmp/su"
13): Change permissions of contents in su to 777 by typing "adb shell chmod 0777 /data/local/tmp/su/*"
14): Launch adb shell by typing "adb shell"
15): Change directory to su by typing "cd data" "cd local" "cd tmp" "cd su"
16): Gain standard root privileges by typing "su"
17): Execute the SU script by typing "./root.sh"
Phone will reboot and you will have root but this leaves verizon without access to data
18) You will need a root explorer
19) Download verizon apn settings https://www.androidfilehost.com/?fid=95916177934521717
20) Extract that file and go to vzw-APNfix>system>etc and copy the apns-conf to the phone
21) In a root explorer locate the apns-conf file you just transferred. Copy/Move it and navigate to system/etc
22) Delete that original apns-conf file in system/etc (contains sprint data info) and past the one you copied
23) Change the permissions to rw-r-r
24) Navigate to /data/data/com.android.providers.telephony/databases/ and delete telephony.db
25) Reboot your phone and everything should be up and running
Now you have a Samsung stock Note 7 with the only thing from Verizon being the network!
Click to expand...
Click to collapse
I can verify this works.

AstonsAndroid said:
I came to the same place by flashing Verizon CSC immediately after the Sprint AP. I did not allow startup in between. Everything booted up on Verizon without activation or additional work. I can verify this works.
Click to expand...
Click to collapse
Just the CSC file after the AP, or did you do all three?

nu2droid said:
Just the CSC file after the AP, or did you do all three?
Click to expand...
Click to collapse
I only had to flash the VZW CSC immediately after the Sprint AP by holding "volume down+Home" during the Sprint Odin reboot, then add VZW CSC.
After which you will boot up on Verizon network with a Vanilla Note 7. No Verizon bloat! Follow the ADB Root instructions in this thread and be happy!

Cool. Thank you sir.... trying now
Sent from my SM-N930V using Tapatalk

AstonsAndroid said:
I came to the same place by flashing Verizon CSC immediately after the Sprint AP. I did not allow startup in between. Everything booted up on Verizon without activation or additional work. I can verify this works.
Click to expand...
Click to collapse
can you edit apn settings?
can you activate wi-fi calling?
can you go into Privacy and emergency>emergency alerts?

MrBaltazar said:
Does not trip knox. NO you cannot use Android Pay or Samsung Pay if rooted. Same with other apps such as Playstation Vue, Snapchat, etc.
Click to expand...
Click to collapse
Will the 2 ever co-exist? Will there ever be root and Android/Samsung Pay that work together?

nu2droid said:
Cool. Thank you sir.... trying now
Sent from my SM-N930V using Tapatalk
Click to expand...
Click to collapse
Lmk if this works. If so I'll add it into the guide

LRiley said:
can you edit apn settings?
can you activate wi-fi calling?
can you go into Privacy and emergency>emergency alerts?
Click to expand...
Click to collapse
No to all three questions!

AstonsAndroid said:
No to all three questions!
Click to expand...
Click to collapse
Cool same across the board then. That's the reason for the extra part, couldn't change apn. If your method works for another person then I'll add it into the guide. Always good to have more than one way

Hdhntr23 said:
Will the 2 ever co-exist? Will there ever be root and Android/Samsung Pay that work together?
Click to expand...
Click to collapse
I highly doubt it. I honestly wouldn't want it to work with root for security reasons. When you root your device it's open to all kinds of unsecured flaws. I don't know about you but I'm not putting my bank card information on a rooted device. ?
Sent from my SM-N930P using Tapatalk
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
@LRiley thanks man. Got everything working! Thanks for the help with adb earlier ?
Sent from my SM-N930P using Tapatalk

[Sprint/others?] Hotspot now functions correctly with root

Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Code:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.

I used that code for my Nexus 5 on T-mobile without rooting. My Pixel is on back order and not able to test it on T-mobile. Is it necessary to root for only the phones on Sprint? Anyone test it on T-mobile (for native hotspot)?

Sorry, yes, I copied my post from a comment I made in another hotspot thread where the code was brought up and I tested it, but it didn't work for me without root. Some people were able to use hotspot after using a workaround, including Verizon, but it seemed like for Sprint doing that gave hotspot but no internet access. Once you get your phone I would check out that workaround comment, and if you have problems try the root command.

Sprint Tether working now for me on adroid 7.1
I tried many things including the above..but none worked. I was able to root the system and what worked for me.
I followed these directions
Go here http://www.theandroidsoul.com/enabl...ing-pixel-and-pixel-xl-verizon-sprint-others/
Setup ADB and Fastboot on your PC (link).
Download the CarrierEntitlement.apk file and save it to a separate folder on your PC.
Connect your Pixel phone to the PC.
Open a command window inside the folder where you saved CarrierEntitlement.apk file in Step 2 above. To do that, “Shift + Right click” on any empty white space inside the folder and then select Open command window here from the context menu.
Once the command window is open, issue the following commands one-by-one disable provishning checks on your Pixel phone:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
└ You may get a prompt on your phone to grant root access, accept it.
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
Your phone will now reboot. Once that is done, go to Settings » More » Tethering & portable hotspot » and enable Portable WiFi hotspot. It should work.
I found this did work to enable the wifi hotspot app but this didnt let the computer connected browse the internet.
I then found this and now im able to browse on a computer connected to my hotspot
http://www.theandroidsoul.com/enable-tethering-nougat-alongside-android-pay/
I only used this part
Download/install a Terminal emulator app from Play Store (link →).
Make sure the terminal asked for rights when typing su because you have to grant it before it works correctly
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
Now my computer connected to the hotspot worked perfect and im very happy.
but i think if you follow this you can get it working right away without my above stuff.
Root your Android device running on Android 7.1 Nougat.
Edit build.prop file: Add the net.tethering.noprovisioning=true line to the bottom of build.prop file on your Android device. Use the link below for help with editing build.prop file.
How to edit build.prop on a rooted Android device
Reboot device after saving changes to build.prop file.
Download/install a Terminal emulator app from Play Store (link →).
Open Terminal emulator on your device and issue the following commands one-by-one:
su
settings put global tether_dun_required 0
exit
└ Grant root access to the app when asked.
Reboot device.
That’s it. You should have Tethering enabled on your Android 7.1 Nougat running device now.
I hope this helps as I haven't found this info in one area on here and sorry if it is but I didnt find it.

Sprint, Tmobile, Verizon (unlocked phone) Wi-Fi hotspot working method. Latest Pie

UPDATE: November 26.
It also works with Tmobile and Verizon (unlocked phone)
Running on latest Pie 9.0 and November update, and magisk beta 17. 3
Original.
you need to root the phone. Or else it does not work.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
@filthysanches did a detailed step by step for newbies down below.
Thanks.
filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse

I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!

beezar said:
I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!
Click to expand...
Click to collapse
Do you have a tutorial link for this, I've followed at least 3 of them I've found online and I can't get Magisk modules to install. Says that /system can't be mounted.

eloko said:
you need to root the phone.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
Click to expand...
Click to collapse
does this work the same way using android sdk?
Step 1: open command window
Step 2: type "cd (folder location of the platform-tools sdk)"
step 3: type "settings put global tether_dun_required 0"
step 4 :type "reboot"
I'm going to try this when I get home, just wanted to confirm if this method makes sense.

Step 2.5 type adb devices. If you see your device then step 2.6. type adb shell

Boom! Works now. Thanks ya'll.

I did everything with adb... I think modules with magisk are tricky sometimes

Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)

uofirob said:
Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)
Click to expand...
Click to collapse
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put
net.tethering.noprovisioning=true
Save and exit.
Reboot.
Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.
Thanks!!

cedargreen said:
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put
net.tethering.noprovisioning=true
Save and exit.
Reboot.
Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.
Thanks!!
Click to expand...
Click to collapse
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?

uofirob said:
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?
Click to expand...
Click to collapse
Had that too on wife's phone that was rma'd due to constant boot loops. Only thing I have done differently is to delete the net.tethering.noprovisioning=true as well as going into magisk and uninstalling back to normal boot img, prior to taking the Nov OTA. Once that was done I went into twrp and reflashed the magisk zip then redid the build.prop.
My noob understanding of that popup is that something in system has been modified (build.prop?) Causing the notification.
I rma'd before I was able to read about it so couldn't test to see if I could complete uninstall then back to factory then update everything and finally magisk, edit build.prop.

eloko said:
you need to root the phone.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
Click to expand...
Click to collapse
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction

I know this is mentioned for Sprint but on stock 025, Nov sec, rooted with Magisk, the above did not work on MetroPCS

access unravel
As a side note, installing a root access "app hider" will reverse the second part of this process breaking connectivity. Not a huge deal but worth noting, as I'm not sure what root access apps will also reverse this.

Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?

filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse
Worked perfect. Thank you.

I am looking for non root solution but so far I can't find it
Got it work
https://forum.xda-developers.com/pixel-2-xl/how-to/root-sprint-hotspot-t3738118

Thank you for breaking this down and explaining it. I performed the first part with the buildprop editor using ES File Explorer with root permissions. It still didn't work so I had to wait till I was done with work to perform the second process with ADB and all is working now so happy. I just got my pixel 2XL and wasn't sure if this would work or not.
Thank you so much too whoever solved this.

rockingondrums said:
Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?
Click to expand...
Click to collapse
did anyone ever confirm this?

Can anyone confirm if this works on pie? Carrier has my tethering disabled.

to move spotify files to other device

hi, I am changing my mobile and I have downloaded about 700 songs on Spotify. I need to know if there's any way I can move these files to my computer and send it to my new device. is it possible?

Set up adb on a pc. you can download the 15 second installer by XDA member snoop05.
Go to your phone's settings, go to about phone (at the end) tap build number 7 times, you will get a message saying you are now a developer.
there should be new settings called 'developer settings'
go there and enable usb debugging
connect your phone to a pc via usb
tap the 'allow usb degugging from this computer' option on your mobile
open a cmd window
type adb devices
if you get an alphanumberic code, you are successfully connected.
If it says unauthorized in a corner, reconnect and dont touch your phone screen till the 'allow' message pops up
when you're connected successfully, type adb pull /storage/emulated/0. You can be as specific as you want, but you will have to find out where in your phone's storage your songs are saved. NOTE if they are on an sd card, type adb pull /sdcard or /sdext or if those dont work, adb pull /data or adb pull /userdata.
This should pull all your songs to the computer.
---------- Post added at 12:12 PM ---------- Previous post was at 12:03 PM ----------
petelm said:
hi, I am changing my mobile and I have downloaded about 700 songs on Spotify. I need to know if there's any way I can move these files to my computer and send it to my new device. is it possible?
Click to expand...
Click to collapse
if you've pulled extra files to your computer, just delete whatever you don't need.
if you've managed to get your music on your computer, save the songs on your desktop (this is important, it has to be your desktop)
repeat the enabling usb debugging process on your new device
connect it to pc
open a cmd window again
type adb devices to check if you're connected
if you're connected, type adb push then drag and drop the folder with the music into the cmd window and hit enter. if you couldn't do that, type adb push C:\Users\(the name of your user on the PC)\Desktop\(the name of the folder with the songs) /sdcard/
if you want to save the songs to your phone's internal storage and not an sdcard, type
adb push C:\Users\(the name of your user on the PC)\Desktop\(the name of the folder with the songs) /storage/emulated/0
NOTE: this whole process is unecessary if your music is already on an sd card, because then you can just transfer the sd card to your new phone.
good luck!
and you can disable the developer options when you're done if you want.