Hey this took me a few hours but its relatively simple. you'll need a little knowledge of DOS or maybe i'll just spell out everything for the noobs being that i'm one. IF YOU HAVE MANUALLY INSTALLED FROYO AND THE OPTION TO MOVE APPS TO SD IS STILL GREYED AND CAN'T BE SELECTED JUST DO THIS.(i'm running windows vista)
1. download and install the android sdk (unzip folder on desktop for easy access)
2. go to my computer then click on C:\ create a new folder here called android
3. go back to the sdk folder on the desktop then open it and go to tools
4. copy the contents of the tools folder to the android folder u just created
5. connect your phone in debug mode if u don't know how to do this go to settings then applications then developement then enable the usb debugging.
6. after doing that you should be prompted to install the drivers 3 will install automatically and one will fail once that one fails select "I DON'T HAVE DISC" then browse for drivers go back to the desktop where u have the android-sdk-windows folder, then go to the usb drivers folder and press ok the adb utility driver should now install. you will also be prompted to reboot the computer in order to access it do so.
7. once rebooted connect ur phone in debug mode again. it should connect smoothly. Now open up a command prompt.
8. From here you'll need to set the path to the android folder to get access to the adb commands do this by typing "path=c:\android" to test it just type adb and you should see all sorts of crap comming up in dos if that happens ur golden.
9. Now all u do is type adb shell you should now see this sign "$" if that happens ur golden now just give the command "pm setInstallLocation 2"
10. you should see the message pm setInstallLocation 2 after which the dollar sign will appear again.
11. exit then reboot you phone and UR GOOOOOD
7
Has anyone else tried this? I assumed that the apps had to support copying to SD in order to work, but Last.FM and a few other apps I have updated to 2.2 support today, and yet I still can't copy them to SD.
xSiraris said:
Has anyone else tried this? I assumed that the apps had to support copying to SD in order to work, but Last.FM and a few other apps I have updated to 2.2 support today, and yet I still can't copy them to SD.
Click to expand...
Click to collapse
i updated to froyo last night and i have been trying to move the apps to sd but it was all greyed and couldn't be selected. i finally figured it out about an hour and a half ago after reading up on adb and stuff i decided to give it a test run cuz what ppl were saying about the apps didn't make any sense. so i tried that and VOILA worked like a charm let me know if it works for u. it did just fine for me
Apps to SD works fine with stock Froyo. The developer just has to support it. One app that does support it that I have found so far is "Armadillo Roll".
After you install, go to manage applications and you will see that the "move to SD" is not grayed out and you can in fact move it over with stock froyo.
thats a way around it man screw the developers
lordvikon said:
thats a way around it man screw the developers
Click to expand...
Click to collapse
have you rebooted your phone yet?
Well, this has been discussed in a couple of threads before, and yeah, it's a working workaround...
pm is the the package manager application which install apks.
installLocation is a parameter which has 3 values...
0 - auto (phone or app decides where to install)
1 - force internal (forces apps to install in the internal memory)
2 - force external (forces apps to install on the sd card)
So, in short, in adb shell or a terminal enumlator, if you type
> pm setInstallLocation 2
all apps will be forcefully installed on the sd card, and you can move them to the phone.
But be careful, if you install widgets and some other aps which run as background processes, they will be killed if you mount ur sd card.
Also, if you have an apk file, u can force install that to the sd card via the adb install command without performing any of the above steps.
> adb install -s AppName.apk
-s forces the app to be installed on the sd card, without that flag, the phone or app will decide where to the app will be installed...
craigacgomez said:
Well, this has been discussed in a couple of threads before, and yeah, it's a working workaround...
pm is the the package manager application which install apks.
installLocation is a parameter which has 3 values...
0 - auto (phone or app decides where to install)
1 - force internal (forces apps to install in the internal memory)
2 - force external (forces apps to install on the sd card)
So, in short, in adb shell or a terminal enumlator, if you type
> pm setInstallLocation 2
all apps will be forcefully installed on the sd card, and you can move them to the phone.
But be careful, if you install widgets and some other aps which run as background processes, they will be killed if you mount ur sd card.
Also, if you have an apk file, u can force install that to the sd card via the adb install command without performing any of the above steps.
> adb install -s AppName.apk
-s forces the app to be installed on the sd card, without that flag, the phone or app will decide where to the app will be installed...
Click to expand...
Click to collapse
so far so good! Thanks for the tip!
Used with adb but I understand you to mean this command will work using terminal emulator app? this would be an easy way to control which apps go to the sd card.
Thanks again for the original post and the clarification. I do love Android and Froyo is rockin' more every day!
help
I downloaded a terminal app and typed
pm setInstallLocation 2
And the dialog gives me an explanation of what the 0 1 2 is and dosen't move the apps. What am I doing wrong?
Ah, this actually works. You have no idea how it feels to move those space hungry navigation apps to the sd card. Perfect!
Thanks!
Awesome! It works, now I can install more games that take up way too much space
Thanks!!
How did you guys do it, I tried with a terminal on the phone but no dice. Did I do something wrong?
glwinkler said:
How did you guys do it, I tried with a terminal on the phone but no dice. Did I do something wrong?
Click to expand...
Click to collapse
Erm, I just followed instructions. I'm on unrooted N1 with Froyo.
Remember to reboot your phone for it to take effect. As Froyo categorizes apps in the application manager, you can tell which apps are installed on sdcard straightaway.
Only downside is once this takes effect, all future apps that you install will immediately be installed to your sdcard. May screw up apps that have background tasks or widgets.
lordvikon said:
thats a way around it man screw the developers
Click to expand...
Click to collapse
disgusting comment.
Without the developers you would have nothing. NOTHING.
Don't do this, you're gonna end up with malfunction applications and then you're gonna get pissed at the developers for your own stupidity.
As i have written on my blog, you need to be aware of a few things:
"Don’t move apps that require a background service running all the time. Things like twitter, widgets, streaming apps (internet radio) and IM apps (you need the notifications even if you use the SD card for something else) should stay on the internal storage because they will break when you’ll use your sd card as a mass storage on your PC.
All the apps you’re going to install from now on will default to the SD card. In case you know for sure that the app uses a background service we advise moving it to the phone’s internal storage."
What you can do is to enable this trick, move all the apps you want to the sd card and reverse the trick so all your future apps will default to whatever setting they have.
lordvikon said:
Hey this took me a few hours but its relatively simple. you'll need a little knowledge of DOS or maybe i'll just spell out everything for the noobs being that i'm one. IF YOU HAVE MANUALLY INSTALLED FROYO AND THE OPTION TO MOVE APPS TO SD IS STILL GREYED AND CAN'T BE SELECTED JUST DO THIS.(i'm running windows vista)
1. download and install the android sdk (unzip folder on desktop for easy access)
2. go to my computer then click on C:\ create a new folder here called android
3. go back to the sdk folder on the desktop then open it and go to tools
4. copy the contents of the tools folder to the android folder u just created
5. connect your phone in debug mode if u don't know how to do this go to settings then applications then developement then enable the usb debugging.
6. after doing that you should be prompted to install the drivers
7
Click to expand...
Click to collapse
Done step 1-5 and when i connect phone i dont get prompt to install drivers???
Please help
This worked like a charm, just gotta remember it when I install new apps (or revert it)
glwinkler said:
How did you guys do it, I tried with a terminal on the phone but no dice. Did I do something wrong?
Click to expand...
Click to collapse
If you want done from terminal, you need root(su). or use ADB save you from trouble.
The only issue with this method is market lost most of downloaded apps link after reboot the phone. Untill you install or upgrade any apps, then the link will refresh.
Use AppBrain check for any update first, then only need install one update. Go back to stock market, everything come back.
BTW: leave phone idle for 1 min after start the phone, otherwise some apps(home screen or app draw) will show default Icon. Phone need time to refresh the apps from SD.Hope next android release can mount SD before phone try to search for Apps(Like the APP2SD on root).
Related
Just a quick note to everyone who is constantly switching between ROM's with their 'daily driver' phone.
Make sure all of your apps are backed up using Astro or AppControl. They will be backed up to /sdcard/backups/apps.
Once your new ROM is installed, and your phone has been wiped, mount your SD card on your PC.
Open a command prompt and navigate to the \backups\apps folder on your SD card.
(this assumes that your adb.exe is in your PATH)
In the command prompt, type in:
for %%f in (*.apk) do adb install %%f
Watch all of your apps install! This really saves a lot of time over using Astro or AppControl to re-install all of your apps.
Absolutely brilliant!
I've done this dozens of times over the last couple weeks. I felt so dumb finding this little snippet of code after manually installing 100+ apps every time I wanted to try a new ROM.
Huh, how about a script to back up via adb? Or backup/restore app data?
Actually, the latter is far more important =P.
I think easy backup restore is with astro file manager...
SpaceBoy2000 said:
Huh, how about a script to back up via adb? Or backup/restore app data?
Actually, the latter is far more important =P.
Click to expand...
Click to collapse
That's more difficult since the data is stored in a DB inside Android (for most apps, anyway). I noticed there is a sqlite3.exe inside the Android SDK so I assume you can query the DB using that and extract certain data, for example SMS and call history, just need to invest a bit of time reading up I think!
I just want to give props to a program for windows called Android Commander. I am not sure if its been mentioned on the Vibrant forum yet, but it got me out of a major jam today.
Android Commander is basically ADB with an easy to use interface. It lets you pull and push files to and from your pc to your Android device.
Story:
I tried to MM the Androdena theme but it seems the framework was corrupted and caused me to keep me in a forceclose loop not letting mount or boot or really do anything. I did make a nandroid backup but some how deleted the CW update zip from my sd at an earlier date and could only boot up into the stock recovery. I was ok with having to reflash the stock rom using Odin, but needed some important pictures that I took for work. Needless to say I starting freaking out. I have ADB set up but only know a few basic commands and I'm sure what I needed to be done could have been done from there. I started searching for solutions on Google and found this awesome program.
I was first able to move the picture folder from my sd card to my pc, then move and rename the CW update.zip to root of the sd card in turn letting me boot into CW recovery and restoring my nandroid.
The only thing I needed to do was to make sure my device was online through ADB and Android Commander was able to find the device and show me all my files and such. Its a great program, and I highly recommend it if you are not familiar with ADB.
I will need to check this out when I get home. I want an easy way to remove the bloatware on my phone.
it seems like an interesting program, and would be good, but for me it doesn't show that i have root. it tells me "root no" and when i use the console in it and use the su command it tells me no. but still a good program over all, i did some looking around and i believe it will only show you have root access if you have an APP2SD installed. i might be wrong with that, but atleast if anyone else has the same trouble with it please let me know if you figure a work around.
ps, you can view root files and folders just not push or pull anything from them.
Yep, I am seeing the same thing.
I did some research on Google and this is what I came up with:
"adb remount and adb root are protected commands and need either a rooted kernel or a flashed recovery model to run" - Source: Rastaman-FB
ah I see. That's good to know. I guess ill be sticking with just the normal ADB. But I think the program will still be very useful for other stuff considering we don't have to mount the USB so no rescan media after the unmount. That alone is a keeper for me. Thanks again for the information pal.
Sent from my SGH-T959 using XDA App
I must say
I have been using android commander since his 1st beta on all my android rooted phone..
It is the best android tool Out there.
Im usually private about the tools I use but
Android Commander (By PanPiotr) is the best and easiest adb GUI tools out there.
Features
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- update
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more…
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off phone
- screenshots (beta)
Stupid question. I accidently deleted my update.zip file and I attempted to reflash another rom. Of course now I'm stuck at the Vibrant Logo and tried to use this app. It says its trying to connect, but never does. I have SDK installed, but I think its the version from when I was tinkering with the G1.
I got into Download mode with the BIG yellow triangle, but my PC never seems to show anything connected via USB unless I try connecting via Recovery.
This app sounded like something would help me since I'm not very good at ADB, but I guess I'm having issues getting over the first hurtle is seems. LOL
Qverse said:
I have been using android commander since his 1st beta on all my android rooted phone..
It is the best android tool Out there.
Im usually private about the tools I use but
Android Commander (By PanPiotr) is the best and easiest adb GUI tools out there.
Features
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- update
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more…
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off phone
- screenshots (beta)
Click to expand...
Click to collapse
I'd say it's ok at best. I don't know of any other ADB GUI tools but this one doesn't work well with my Vibrant.
StrayPanda said:
I'd say it's ok at best. I don't know of any other ADB GUI tools but this one doesn't work well with my Vibrant.
Click to expand...
Click to collapse
I'm going to have to agree with this. Is nice to have but doesn't play nice with the vibrant.
Sent from my SGH-T959 using XDA App
It sometimes is very slow in reading internal sd memory on samsung vibrant and it loads up as a blank screen. Disconnecting usb cable and refreshing does the trick for me.
Sent from my SGH-T959 using XDA App
Hi,
like I said I cannot get Google apps on my nook color. I've tried everything. I originally had cm7.0.3 but that wouldn't work so I tried 7.1.0 rc and it still won't work. I tried booting in recovery mode numerous times, I've tried using ROM manger to install from SD but again doesn't work. Someone please help!
chad11 said:
Hi,
like I said I cannot get Google apps on my nook color. I've tried everything. I originally had cm7.0.3 but that wouldn't work so I tried 7.1.0 rc and it still won't work. I tried booting in recovery mode numerous times, I've tried using ROM manger to install from SD but again doesn't work. Someone please help!
Click to expand...
Click to collapse
settings > accounts and sync > add account > log in
that should help. That's how i fixed it when i had the same problem.
thanks but in the first post I forgot to mention I also can't add my Google account. I get as far as it is checking the server connection bu then it say it can't connect
chad11 said:
thanks but in the first post I forgot to mention I also can't add my Google account. I get as far as it is checking the server connection bu then it say it can't connect
Click to expand...
Click to collapse
can you connect to the internet at all?
re-do everything. Do "adb pull /data/app/ app/" and "adb pull /data/data/ data/" and go into the app folder. Delete anything that has to do with Google (market, googleservices, etc.) Download cm7 and gapps from the links at the end of this post Put em on your sd card. Boot into recovery. Mounts & Storage, wipe data, system, and cache. Now flash cm7 first, then gapps. Now flash anything else you use (dal's OC kernel, etc) and reboot. Re-setup your Nookie. Now push puth the app/ and data/ folders to your sd card. Download File Expert and Root Explorer. Using file expert, navigate to the sd card. Select the app/ folder you pushed, and press and hold. Now hit install all apk packages. Keep installing. If you get an error, Setting>Applications>Allow Non-Market installs. Now use root explorer to merge the data/ folder on your sd with the /data/data/ folder on the emmc. Done. Hope that wasn't to complicated.
ikingblack said:
re-do everything. Do 1) "adb pull /data/app/ app/" and "adb pull /data/data/ data/" and go into the app folder. Delete anything that has to do with Google (market, googleservices, etc.) 2) Download cm7 and gapps from the links at the end of this post Put em on your sd card. Boot into recovery. Mounts & Storage, wipe data, system, and cache. Now flash cm7 first, then gapps. Now flash anything else you use (dal's OC kernel, etc) and reboot. Re-setup your Nookie. Now push puth the app/ and data/ folders to your sd card. Download File Expert and Root Explorer. Using file expert, navigate to the sd card. Select the app/ folder you pushed, and press and hold. Now hit install all apk packages. Keep installing. If you get an error, Setting>Applications>Allow Non-Market installs. Now use root explorer to merge the data/ folder on your sd with the /data/data/ folder on the emmc. Done. Hope that wasn't to complicated.
Click to expand...
Click to collapse
You are aware that when you do #3 you will take care of #1. wiping the /data wipes everything in it.
And if you want go about it that way you could even just do a
Code:
c:\<target folder> adb install [package name]
and it will install the app for you. so you can pull it, wipe it then reinstall everything.
adb pull backs it up. and whoops, here are links:
CM7: http://download.cyanogenmod.com/get/cm_encore_full-123.zip
Gapps: http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip
ikingblack said:
adb pull backs it up. and whoops, here are links:
Click to expand...
Click to collapse
Then why are you having the [OP] reflash the gapps if they are just going to manually install them?
the problem the [OP] is having is the device [Nook Color] will not connect to google's servers. It has nothing to do with the g/apps not showing up on the device.
No, we are backing up all the apps, because one time I had this problem and a fresh slate caused it. And as for the adb install commands, It would take forever, because you would have to type in the APK's name. For my method, all you have todo is hit Install. Just keep stabbing the right lower corner of the screen.
ikingblack said:
No, we are backing up all the apps, because one time I had this problem and a fresh slate caused it. And as for the adb install commands, It would take forever, because you would have to type in the APK's name. For my method, all you have todo is hit Install. Just keep stabbing the right lower corner of the screen.
Click to expand...
Click to collapse
So because you reinstalled the applications it's magically reconnected to Google's servers?
Nope. There was something corrupt in my /data/ folder. Wiping and re-installing all apps was what I had to do.
OK your first post was a little complicated for me. this is the first time I've rooted somethiing. could you please put in simpler terms. by the way I don't have any apps on my device or any other data i care about so I don't need to back anything up if that would make it easier
also yes (neidlinger) I did have a internet connection, and I also can't install a new build through recovery
Alright, if you don't have anything to back up, do this:
Download CM7, gapps, and other stuff you want (overclock kernel) and put it on the sd card.
Now boot into recovery, CWM.
Go into Mounts + Storage. Wipe system, data, and cache. Go into advanced (on the first menu) and wipe dalvik cache.
Hit "install zip from sd card" and then "choose zip from sd card".
Now select CM7. Wait for it to flash
Choose zip again, but choose gapps, then flash an OC kernel if you wanted. Note the NC doesn't have back and menu buttons, so download a Hard Key editor to make Volume+ to menu and volume- back.
Now reboot device. Now set it up. After typing in your google account, it will *attempt* to connect to Google Servers. It will fail. It will then show a button to connect to wifi. Hit it and connect to the wifi. Then continue set up steps. Enjoy CM7 with a smaller guide. Much smaller.
ikingblack said:
Alright, if you don't have anything to back up, do this:
Download CM7, gapps, and other stuff you want (overclock kernel) and put it on the sd card.
Now boot into recovery, CWM.
Go into Mounts + Storage. Wipe system, data, and cache. Go into advanced (on the first menu) and wipe dalvik cache.
Hit "install zip from sd card" and then "choose zip from sd card".
Now select CM7. Wait for it to flash
Choose zip again, but choose gapps, then flash an OC kernel if you wanted. Note the NC doesn't have back and menu buttons, so download a Hard Key editor to make Volume+ to menu and volume- back.
Now reboot device. Now set it up. After typing in your google account, it will *attempt* to connect to Google Servers. It will fail. It will then show a button to connect to wifi. Hit it and connect to the wifi. Then continue set up steps. Enjoy CM7 with a smaller guide. Much smaller.
Click to expand...
Click to collapse
Please Take TIME to read the entire post before firing off solutions that will not help the [OP]
chad11 said:
also yes (neidlinger) I did have a internet connection, and I also can't install a new build through recovery
Click to expand...
Click to collapse
To the OP. Do me a favor. And i under stand this is your first time messing with a rooted device.
I need you to either get your SDK up and running, and do the patch for it to pick up your Nook Color. Once you do that you need to go into the adb command prompt and type
Code:
adb kill-server
adb start-server
that will kill and start the the bridge to connect your phone to the computer
then type
Code:
adb devices
it should show your serial number
once that is done type
Code:
ls /data/app
That will show you all of your applications that are store in the /data folder on your device.
should see a bunch of com.android.[package_name]
They'll look like this
Code:
com.google.android.apps.books-2.apk
com.google.android.apps.docs-2.apk
com.google.android.apps.googlevoice-2.apk
com.google.android.apps.maps-2.apk
com.google.android.apps.plus-1.apk
com.google.android.apps.reader-1.apk
com.google.android.gm-1.apk
com.google.android.music-2.apk
com.google.android.street-1.apk
com.google.android.voicesearch-1.apk
com.google.android.youtube-1.apk
If you see those then you know your Google Apps were installed when you flashed the package from the get go.
you can also do a
Code:
ls /system/app
and look for MarketUpdater.apk GoogleServicesFramework.apk. If you see those then you know are good to go.
The only reason i'm not suggesting it's a bad flash is i had the SAME problem when i went from Rooted Stock to CM7. Once i logged into my device all of the G/Apps showed up. It was almost like they do appear until you are logged in.
what is SDK and adb
chad11 said:
what is SDK and adb
Click to expand...
Click to collapse
SDK is Software Development Kit. It enables one to create ROMs, Themes, Applications and what not. (http://developer.android.com/sdk/index.html)
the ADB is the Android Debug Bridge it is what enables your phone to talk to your computer. via the CMD prompt. (http://developer.android.com/guide/developing/tools/adb.html)
The very basics of it you will need the ADB drivers. Which i have a link to in my signature. However some extra steps must be taken to make the computer pick up the Nook Color.
I mtried to get them both but when I tried to install SDK It said I had to install a java SE thing but i don't know which windows to install: 84, 64, or ititium. I don't know if I spelled it right but they wouldn't work
@neidlinger in your post it said "ls /data/app". Well, actually it should be "adb shell ls /data/app"
Heads up.
hey, I just figured something out. when I boot into clockworkmod recovery it deosn't show up. then when I take the sd card out and power it back on it shows up. what does this mean
After having rooted (with nexus 10 toolkit v1.3.0) my nexus 10 and flashed AOPK Nexus 10 (WIP) Task650 & Ktoonsez (1-4) rom, I'm unable to upload to, change or move any files or folders on my internal SD card. I installed Root Explorer and changed from Mount R/O to Mounted as r/w. Access is granted by Super SU. I also tried to change permission settings, unfortunatedly without any success. There appeared the following message:
"Warning
Permissions change was not successful. Please note that some file systems (e.g. SD card) do not allow permission changes."
Is there a possibility to change these permissions in order to be able to create and move files and folders on my SD card?
Thanks for taking your time to help me with my issue!
Anzirothu
1. Clear cache
2. Clear dalvik
3. Fix Permissions
forgot something ?
Thank you for your reply, Patrik!
1. done.
2. done.
3. Fix Permissions - How? With cwm? I did fix permissions with cwm recovery, but the problem persists...
Just so we are clear, when you say "upload to, change, or move" are you meaning you cannot copy a file from your computer to your Nexus 10? Or just that you cant arrange stuff through root explorer from within the tablet itself?
Neither copying from PC to Nexus nor arranging stuff through root exlorer from within the tablet itself. I can't even download an email attachment and put it to the SD card. The card seems to be locked.
I had that problem once but I dont remember what caused it or what exactly I did to fix. I think I just did a complete wipe by locking and unlocking the bootloader and then installing a new ROM again.
I think I did this too (unroot, lock bootloader, then root and unlock bootloader) and then installed the same rom again. I will try it this time with another rom.
Isn't there really no other solution to get access to my SD card again??
Thx for your help!
Are you using a toolkit to unlock and root? If so them maybe it is not doing something right and it messing up a permissions somewhere. It could also be a driver problem on your PC with being unable to copy a file to the tablet.
Thank you for your help!
I am using the nexus 10 toolkit V1.3.0. Right now I'm trying to intall twrp recovery with a fully wiped sd card. No easy task fot me being a noob...
In ClockWorkMod, make sure that /data is mounted
Then download the Android SDK: http://developer.android.com/sdk/index.html
I usually put all the files just in C:/android-sdk-windows
Once you have it all there open up the SDK Manager and download all the additional files needed. You probably only need to download "Android SDK Tools" and "Android SDK Platform-tools", but I always download the other files for whatever version of Android I am running, in our case Android 4.2. That way I have them if I need to do something else.
Once downloaded, open the Android-sdk-windows/platform-tools directory. copy:
adb.exe
adbWinApi.dll
adbWinUsbApi.dll
fastboot.exe
to your base C:/Android-SDK-Windows directory.
Now open command prompt from Start -> run
type: cd C:/Android-SDK-Windows
type: "adb devices" and it should list your tablet. It will actually say something with your devices serial number and then "Recovery" after it, showing your tablet is in recovery. If you dont see this then you either dont have your tablet mounted right from in the Recovery, ClockWorkMod is stupid, or you dont have working adb drivers.
Now copy the ROM you want to flash to C:/Android-SDK-Windows
Then type: "adb push blahblahblah.zip /data/media/0"
That should push the ROM to the root of your SD card. Give it time, it takes a while to push a ROM file. Once it is done, flash the ROM.
That *should* put it in the right spot where it looks like it is on your "internal storage" (what you see when navigating files within the ROM). If you dont see the ROM in clockworkMod then keep navigating back to the root of your internal storage and then open up "data", then "media", then "0" and you should see it. If you still cant find the ROM, push it again but just use "/data/media" as the location.
I just did all these steps myself to verify I remembered it all correct and I was able to successfully copy a ROM and find it on my tablet to flash by doing everything I just listed above. SO you should be good to go if you follow all those steps properly. I know it looks like a lot of work, but it really isnt and will go quite fast. Most of it is just the setup for getting ADB and Fastboot ready to use.
For a ROM to install, I would recommend to someone new like you either of these:
http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ That one is pretty close to the stock ROM with a few fixes and a couple extra features
or: http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ This one is pretty much CyanogenMod 10.1, but built by a different guy and not pulling every new thing from CM, just the "cherry picks" of features. It tends to be a bit more stable and less buggy than the real CM10.1 nightly's
And for a kernel you can flash and forget you will want to try this one:
http://forum.xda-developers.com/showthread.php?t=2098157
^^^^^ To flash that you will want to do a similar thing as how you pushed the ROM to your device. Only this time you will copy the kernels' "boot-r4.img" file into your android-adk-windows directory and use the command: "fastboot flash boot boot-r4.img"
While I enjoy the KTManta kernel more, it does require a bit of tweaking to get running perfect. Which is one of the things I like about it because of all the options to tweak. But for someone just learning this stuff that would be a bad thing, so Franco's kernel is much better than stock and doesnt require you to adjust anything once it is flashed to your tablet.
Hey, is there a way to make whatsapp save media to sdcard instead of internal storage?
Whatsapp does not support external SD card for storage.
stluiz said:
Hey, is there a way to make whatsapp save media to sdcard instead of internal storage?
Click to expand...
Click to collapse
If your phone is rooted, you can make a link from the normal whatsapp folder to the sdcard
make a whatsapp folder on your sdcard, move all of your content and delete the old one and then in console or adb as root type :
ln -s /storage/ExtSdCard/whatsapp /storage/sdcard0/whatsapp
reboot your phone and that should do it.
WarDrake said:
If your phone is rooted, you can make a link from the normal whatsapp folder to the sdcard
make a whatsapp folder on your sdcard, move all of your content and delete the old one and then in console or adb as root type :
ln -s /storage/ExtSdCard/whatsapp /storage/sdcard0/whatsapp
reboot your phone and that should do it.
Click to expand...
Click to collapse
I'm not that good with android and entering codes, how can I run the command using the phone?
I tried using folder mount but all it did was move the files and after that I couldn't open new media that came to me.
thanks a lot
stluiz said:
I'm not that good with android and entering codes, how can I run the command using the phone?
I tried using folder mount but all it did was move the files and after that I couldn't open new media that came to me.
thanks a lot
Click to expand...
Click to collapse
If you want to enter the command in the phone directly you'll need to download a terminal emulator from the play store and enter the same commands on the phone, while on the fodler where the original whatsapp folder was located at.
WarDrake said:
If your phone is rooted, you can make a link from the normal whatsapp folder to the sdcard
make a whatsapp folder on your sdcard, move all of your content and delete the old one and then in console or adb as root type :
ln -s /storage/ExtSdCard/whatsapp /storage/sdcard0/whatsapp
reboot your phone and that should do it.
Click to expand...
Click to collapse
Are you sure this will work? Linux doesn't normally allow cross-device symlinks. Does android behave differently in this regard?
BLuFeNiX said:
Are you sure this will work? Linux doesn't normally allow cross-device symlinks. Does android behave differently in this regard?
Click to expand...
Click to collapse
soft links work on linux, it's hard links that are restricted, and even then, since the whole storage procedure is now emulated in android, it shouldn't be a problem
however, you just made me think of something, he'll need to re enable 3rd party write access to the sd card or he'll just keep getting I/O errors, that's disabled on KK by default, i used "NextApp SDFix" from the play store to do it on mine.
WarDrake said:
soft links work on linux, it's hard links that are restricted, and even then, since the whole storage procedure is now emulated in android, it shouldn't be a problem
however, you just made me think of something, he'll need to re enable 3rd party write access to the sd card or he'll just keep getting I/O errors, that's disabled on KK by default, i used "NextApp SDFix" from the play store to do it on mine.
Click to expand...
Click to collapse
Ah, you're right. I should have known that, otherwise how else would mount points work in general?