Related
From elocity about A7+:
The 4GB internal high speed flash memory can store up to 4 feature films, 40,000 photos, or 2,000 songs for countless hours of entertainment. Wireless & Bluetooth.... BLA bla bla.
.................................
Ok, I have been searching and finding related information but confusing me more.
I have an A7+
it came with a 8 gb card, I can't figure out how to save to card, downloads, apps etc.
It never gives choice. No options in settings > memory card or when downloading
Besides the external card issue, and because of my novice tech knowledge I don't under stand what takes up space and best way to manage with A7+ or if different then A7
The 8 gb card shows 7.39 gb available and has not changed since installed, card was new so I never formated it.
*I now have 39.62mb available user space (that's not a lot, is it?) thats after 4 gb factory and all systems use, that left me with 1.53 gb to work with?? (edit, I deleted about a dozen apps and a bunch of music. Now available internal memory is LESS, 39.61mb what's going on)?
I have downloaded a bunch of apps, I don't fully understand how this effects memory, I have about 250 songs, no movies and just a dozen or so photos
I'm guessing its the apps
Thanks in advance...
reply
well, this is more of an android topic and not A7.
anyway, to move apps to a card go to Settings/Applications and on some apps that aren't protected you will have the option to move to card. many file managers have an app backup option and will also allow you to copy/paste to/from your memory card. try Astro, it's very popular and works well.
saving downloads is sometimes done by the settings of which ever program you are using. as far as i can tell the default browser and firefox mobile only save to onboard.
Astra was not available for the A7+ that I could find, I found Es explorer app and yet to find area for my needs in it, I guess I need more time on it, it looks like much more then I need and more complicated then I can manage
I just need a easy way to manage basic downloads like photos, music, apps
the device comes with a file manager preinstalled, i can't recall the name because my A7+ is not functioning and no one replied to my post.
I think 'OI manager' is the factory manager on my A7+.
With OI manager I tried to transfer files, apps (or anything) into my 8 GB card with no success, also tried 4 or 5 apps that advertise "app to SD" type ability along with more 'astro' type apps that claim to be file managers that should do what I need all with no luck, its like my device is locked to not to allow moving files
related issue, tablet was down to about 39.62MB internal space, after removing many apps and mp3s, it always seems to effect internal storage randomly, after clearing space I would sometimes loose available space, sometimes gain space, whats going on?? Is this a quirk with Android system?
The big one is, I decided to take the 16GB sd card out of my Blackberry and try in A7+. after first installing card everything was fine, all 200 or so photos and some videos from BB card showed up as expected (with device showing the majority of the 16GB sd card available) ....I went on to do something else and left the A7+ to go into stand by, when I woke it up, it says 'sd card is full please clear space' I go check available space and it is 0 and I can no longer access any pics, internal or on the 16GB card ?? I swap back the empty 8 GB card and show a total available internal 4.33MB and system seems to work ok except low memory storage. Note, that I had 39.62MB internal user space one week ago then up to ~60.14MB as of 24 hrs ago after a lot of cleaning of music and apps, then installed & removed other BB sd card and now down to 4.33MB. Its like Android Alzheimers or something as I now have very little memory space available and a device that does erratic things.
*Last thing, could it be the music I downloaded directly into device is corrupt or not compressed correctly or just to many files "or something I don't understand"? (the mp3s are in the internal 4GB storage that really is 1.53GB usable)
I still have about 200 songs downloaded from app called "MP3 Music Download" that I got from one of the included app stores, apk or Getjar??
Anyway to transfer those mp3s to pc or thumb drive then delete them from device and check status
I have emails into eLocity now for a couple weeks with no response from previously helpful contact
~eLocity A7+ with no mods, factory settings~
over's tab said:
I think 'OI manager' is the factory manager on my A7+.
With OI manager I tried to transfer files, apps (or anything) into my 8 GB card with no success, also tried 4 or 5 apps that advertise "app to SD" type ability along with more 'astro' type apps that claim to be file managers that should do what I need all with no luck, its like my device is locked to not to allow moving files
related issue, tablet was down to about 39.62MB internal space, after removing many apps and mp3s, it always seems to effect internal storage randomly, after clearing space I would sometimes loose available space, sometimes gain space, whats going on?? Is this a quirk with Android system?
The big one is, I decided to take the 16GB sd card out of my Blackberry and try in A7+. after first installing card everything was fine, all 200 or so photos and some videos from BB card showed up as expected (with device showing the majority of the 16GB sd card available) ....I went on to do something else and left the A7+ to go into stand by, when I woke it up, it says 'sd card is full please clear space' I go check available space and it is 0 and I can no longer access any pics, internal or on the 16GB card ?? I swap back the empty 8 GB card and show a total available internal 4.33MB and system seems to work ok except low memory storage. Note, that I had 39.62MB internal user space one week ago then up to ~60.14MB as of 24 hrs ago after a lot of cleaning of music and apps, then installed & removed other BB sd card and now down to 4.33MB. Its like Android Alzheimers or something as I now have very little memory space available and a device that does erratic things.
*Last thing, could it be the music I downloaded directly into device is corrupt or not compressed correctly or just to many files "or something I don't understand"? (the mp3s are in the internal 4GB storage that really is 1.53GB usable)
I still have about 200 songs downloaded from app called "MP3 Music Download" that I got from one of the included app stores, apk or Getjar??
Anyway to transfer those mp3s to pc or thumb drive then delete them from device and check status
I have emails into eLocity now for a couple weeks with no response from previously helpful contact
~eLocity A7+ with no mods, factory settings~
Click to expand...
Click to collapse
I also have the same problem customer support was trying to help me but all I succeeded in doing was move an ebook to files and now I can't get it back or read it. I have never formatted my 8 gb card so I don't know if that is the step I missed. My stepdaughter printed out the manual but unfortunately it is more an overview than a step by step. It IS in the oi file manager. I also noted that when I tried to move the book that there was a thin strip that said move file and maybe that sucked me into loading the book to my files. My A7 also played youtube videos at first but now it don't. It will play other sites but if they go to youtube it comes and attacks the site. youtube has declared war on me and I don't know why or how to make them stop. bye for now frank
Thanks for input on this. I was never able to get issues resolved, the return period was almost up so I decided to return it 'no questions asked'
To many things building against it, lacking support online and from manufacturer, I will miss many aspects of the A7+, a nice little tablet with potential, but.....
I now have an Archos 80 G9 (8" 3.2 Honeycomb w/ 8GB) it also packs a lot for the money, so far so good
Edit: forgot to mention, on eLocity the 'HOME' key had stopped working completely
Dropped the ball
No matter what you do you cannot get the Elocity A7 or A7+ to load to the SD card.....we have been trying for months and no matter what we do nothing works. The damned thing has so much potential and is suck a powerful little machine that it is a shame that the bloody company dropped the ball. We did manage to to get it onto every market in the world and we changed the 4 Gig internal to a 32 Gig internal and reloaded the Titanium backup onto the card with the PC so there is more space and now the SD is primarily storage and a media file. To think that all they had to do was try a little harder and this would have been a monster in the market place last year. Oh well, maybe someone else will create a tablet that is fun and easy to use.
blooknight154 said:
No matter what you do you cannot get the Elocity A7 or A7+ to load to the SD card.....we have been trying for months and no matter what we do nothing works. The damned thing has so much potential and is suck a powerful little machine that it is a shame that the bloody company dropped the ball. We did manage to to get it onto every market in the world and we changed the 4 Gig internal to a 32 Gig internal and reloaded the Titanium backup onto the card with the PC so there is more space and now the SD is primarily storage and a media file. To think that all they had to do was try a little harder and this would have been a monster in the market place last year. Oh well, maybe someone else will create a tablet that is fun and easy to use.
Click to expand...
Click to collapse
i fixed the kernel in my A7CompPlus release, and apps can be installed on sdcard, and i think i updated it in the Cyanogen release as well.
it just took some kernel recompile and different framework, since elocity framework does not support this at all (it is removed from the firmware completely).
so you cannot get the feature unless you try a custom rom.
Dexter_nlb said:
i fixed the kernel in my A7CompPlus release, and apps can be installed on sdcard, and i think i updated it in the Cyanogen release as well.
it just took some kernel recompile and different framework, since elocity framework does not support this at all (it is removed from the firmware completely).
so you cannot get the feature unless you try a custom rom.
Click to expand...
Click to collapse
Dexter, Thank You for your work on A7+. I am enjoying your CM7 rom but can't get apps to load to SD. Tried every combination of settings. Are there any performance disadvantages to modding vold.fstab file ot make the SD card internal? Also please give update on your ICS mod work. I appreciate any suggestions.
denmichelson said:
Dexter, Thank You for your work on A7+. I am enjoying your CM7 rom but can't get apps to load to SD. Tried every combination of settings. Are there any performance disadvantages to modding vold.fstab file ot make the SD card internal? Also please give update on your ICS mod work. I appreciate any suggestions.
Click to expand...
Click to collapse
i believe that external sdcard should work. but maybe its just found on the /mnt/sdcard location or what vold.fstab says?
have you checked its mounted? i am sure it should have worked. let me see if i get a chance to confirm or check.
Dexter_nlb said:
i believe that external sdcard should work. but maybe its just found on the /mnt/sdcard location or what vold.fstab says?
have you checked its mounted? i am sure it should have worked. let me see if i get a chance to confirm or check.
Click to expand...
Click to collapse
Thanks for your quick reply. I checked and SD is mounted and shows up in storage. I found the following generic vold.fstab which is supposed to be set up to make the external SD act as internal storage. Please comment on any changes that might be needed.
# Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# sdcard mount for the P1
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 28 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
discard = disable
asec = disable
}
#dev_mount sdcard1 /mnt/sdcard/external_sd 1 /devices/platform/msm_sdcc.4/mmc_host/mmc2
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
#end line ## keep this line
denmichelson said:
Thanks for your quick reply. I checked and SD is mounted and shows up in storage. I found the following generic vold.fstab which is supposed to be set up to make the external SD act as internal storage. Please comment on any changes that might be needed.
# Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# sdcard mount for the P1
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd 28 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
discard = disable
asec = disable
}
#dev_mount sdcard1 /mnt/sdcard/external_sd 1 /devices/platform/msm_sdcc.4/mmc_host/mmc2
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
#end line ## keep this line
Click to expand...
Click to collapse
The file above did not work. The CM7 vold is below. Do you know what commands need to be changed to make the external card the primary internal storage.
# Vold 2.0 Malata Harmony fstab
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard 1 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount emmc /mnt/emmc 6 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
you cannot make sdcard primary internal this happens in boot stage.
you can only switch internal storage card with external card.
just change the 2 first thing in 2 first lines /mnt/sdcard and /mnt/emmc and its done
Dexter_nlb said:
you cannot make sdcard primary internal this happens in boot stage.
you can only switch internal storage card with external card.
just change the 2 first thing in 2 first lines /mnt/sdcard and /mnt/emmc and its done
Click to expand...
Click to collapse
So it should now look like this. I tried it but storage seems same with external SD card showing my 8gb of storage and internal is still 1gb. Any other steps. Thanks for your patience. I really want to get more app storage.
dev_mount sdcard /mnt/emmc 1 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount emmc /mnt/sdcard 6 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
denmichelson said:
So it should now look like this. I tried it but storage seems same with external SD card showing my 8gb of storage and internal is still 1gb. Any other steps. Thanks for your patience. I really want to get more app storage.
dev_mount sdcard /mnt/emmc 1 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount emmc /mnt/sdcard 6 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
Click to expand...
Click to collapse
dev_mount emmc /mnt/emmc 6 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount sdcard /mnt/sdcard 1 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
this is the correct way
Dexter_nlb said:
dev_mount emmc /mnt/emmc 6 /devices/platform/tegra-sdhci.0/mmc_host/mmc0 /devices/platform/tegra-sdhci.1/mmc_host/mmc1
dev_mount sdcard /mnt/sdcard 1 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
this is the correct way
Click to expand...
Click to collapse
Dexter, thanks for your continued help. I made the changes and everything looks and acts the same.Internal storage is 1g and external storage on Sd Card is 7.39 as it was before. My file card needed to be reformated before it was recognized. I rebooted after the changes anything else required?
denmichelson said:
Dexter, thanks for your continued help. I made the changes and everything looks and acts the same.Internal storage is 1g and external storage on Sd Card is 7.39 as it was before. My file card needed to be reformated before it was recognized. I rebooted after the changes anything else required?
Click to expand...
Click to collapse
i might actually have misunderstood, if i recall the A7 correct, internal storage is actually the /data partition that you cannot change, thats alot bigger process to fix.
you can only keep sdcard at the /mnt/sdcard location , the /mnt/emmc location was for USB connected devices in the CM rom.
Dexter_nlb said:
i might actually have misunderstood, if i recall the A7 correct, internal storage is actually the /data partition that you cannot change, thats alot bigger process to fix.
you can only keep sdcard at the /mnt/sdcard location , the /mnt/emmc location was for USB connected devices in the CM rom.
Click to expand...
Click to collapse
Dexter, I appreciate your timely responses and ongoing support for the A7+
FIRST TIME HERE? - SKIP DOWN AND READ IN FULL THE [ ORIGINAL THREAD CONTENT ]
Reference Section:
As this thread as evolved, Folks have contributed various methods they've used to fix/workaround this problem - Credit and Thanks to those members.
Black6spdZ - Information on Physical Removal of the Internal Memory Info - Installing CM9
^_Pepe_^ - Guide: Installing CM10 using Heimdall
TrevD ( Me )Alternative mount point Information for devices with intermittent issues
goofey2012 - External SDCard partitioning information.
Click to expand...
Click to collapse
PROTIP - GET THE LOGCAT:
adb is possible one of the most powerful tools you have at your disposal when diagnosing the source of bootloops. If you are stuck in a bootloop grab a good sized sample of what the device is doing by running.
Code:
adb logcat
PROTIP 2 - DON'T FEAR THE LOGCAT:
During a bootloop the ouput of logcat loops around, Running logcat for a couple of minutes and then read the output, It is written in plain english ( at least on English Language Roms ) and will explain what is causing your bootloop.
PROTIP3 - FIND OUT HARDWARE STATUS
Another useful adb command is dmesg, this is the output from the kernel, the kernel amongst other thing manages the interactation between the software and the hardware, you can normally find out if your sdcard has failed by running
Code:
adb shell dmesg
Run this command early in the boot sequence, if you see a line similar to the one below then there's a good chance you're sdcard has failed
Code:
[COLOR="Red"]<3>[ 4.802004] mmc0: error -110 whilst initialising MMC card[/COLOR]
Click to expand...
Click to collapse
[ ORIGINAL THREAD CONTENT ]
DISCLAIMER: DON'T TRY THIS IF YOU DON'T HAVE TO - I AM NOT RESPONSIBLE FOR ANYTHING - IF YOU ARE UNSURE ABOUT ANYTHING - ASK
I recently fixed a P1000 with a corrupt internal sdcard - I thought I'd share my experience as unbelievable as It sounds, given the size of the internet
I could not find this procedure /hack anywhere
The Symptoms
When Booting the device got stuck at the Samsung Logo Screen
ODin/Heimdall fails on any rom which include an hidden.rfs and movinand.mst
ODin/Heimdall report success when flashing flashing roms without hidden.rfs and movinand.mst
Recovery Mode reports errors after flashing. The error is different depending on which rom was flashed but are all related to file system functions.
Internal MMC checksum verify failed.
E: failed to mount /system (invalid argument)
E: failed to mount /dbdata (Invalid argument)
E: /dev/block/mmcblk0p2 on /data failed: No such file or directory
E: copy_dbdata_media:Can't mount /dbdata
IMPORTANT: THESE ARE NOT THE ONLY ERRORS AND ARE EXAMPLES. IF YOUR ERROR IS DIFFERENT THEN PLEASE SHARE IT.
THE MAJOIRITY OF THE TIME THE ERROR WILL MENTION WORDS LIKE:
mount
mmcblk
directiory not existing.
The Problem
The recovery errors alone are not enough to diagnose the problem as they can also occur if flashing has been carried out incorrectly.
The main pointer to an Internal SDCard Failure is the inability to flash hidden.rfs and movinand.mst
You should be able to confirm this to be the case by running dmesg on the device using adb from the command prompt of your computer
If you were luckly enough to have left USB Debbugging on than you should be able the run the following command
while the device is booting loop otherwise run it ) while you are in recovery
Code:
adb shell "dmesg | grep mmc0"
My output contained the following line:
Code:
[COLOR="Red"]<3>[ 4.802004] mmc0: error -110 whilst initialising MMC card[/COLOR]
Another way to check is to use adb to view the devices file system.
Code:
adb shell "ls /dev/block"
Do this WITHOUT an external sdcard.
Any Reference to mmcblk will be missing.
Normally you should be able to RMA this as it is an hardware failure.
However as warranties expire or you just can't be bothered to wait here is an alternative solution
The Solution is fairly straight forward, However It's not a repair and it is not possible to recover any data from the Internal memory.
So You've lost your Angry Birds Hi-Score forever.
That's the bad news. The Good News is, You've still got what will soon be a working Tablet again and a chance to get an even higher score.
Note: The Following description maybe considered by some as a little heavy on Technical Details.
Unfortunately. we are taking advantage of how the Linux Kernel Interacts with hardware ports and how the linux sysfs Virtual filesystem works, It's the nature of the beast I'm afraid
The Solution
In one sentence. We will use the external SD Card to store and load The Android OS.
How Do You Plan to pull that trick off?
This is made possible because of how the Linux kernel manages and addresses devices of the same type. Linux gives each device a number which increments by 1 each time.
The Hardware can control what Linux Sees. I.E the Internal Memory is always loaded first and given and index of 0 [ remember computers : Start Countong a zero ]
After trying and failing to access from the internal sdcard the Kernel quite sensibly looks for the first functioning SDCard on the System and creates it in the /dev tree with a index of zero for that Class of device. It just so happends that the first (and only) Sdcard on the System is now physically located in the external SDCard Slot.
So What Now?
Now we have to play nice with whatever rom is on the device. which means providing the number of partitions that the rom expects. In my case It was 3.
So go ahead ad format and parition your SDCard.
There is nothing to stop you having more than the base amount with what ever file systems you please as long as the Kernel Can provide a mount point to the device than You're laughing.
This Partition Below table was suitabke for UK Roms. The Fat32 Partition is what will appear when the device is connected to Windows as a disk drive.
From what I recall that is the only reason for having a fat filesystem on the Card. So If you're a Linux Junkie then You should be able to pick what Filesystem is good for you. Format the external sdcard with 3 parititions (you can probably get away with 2) I used a 32 GB card with the follwing
Partition 1: 28 GB Fat 32 (sdcard partition)
Partition 2: 4 GB ext4 (data partition)
Partition 3: 100MB Fat 32 (preload partition)
I Used Heimdall for this and I flashed everything. Odin should do the Job as long you remove hidden.rfs and movinand.mst from the tar balls
Code:
heimdall flash --repartition --pit gt-p1000_mr.pit --primary-boot boot.bin \
--cache cache.rfs \
--factoryfs factoryfs.rfs --modem modem.bin \
--param param.lfs \
--secondary-boot Sbl.bin \
--kernel zImage --recovery zImage
After That I Flash a custom kernel which If memory serves enabled the CWM Recovery. The Kernel I used was
one from Team Overcome Kernel 4 which can be downloaded from the teamovercome download page
The choice of kernel isn't any endorsement........ Actully I will say. Use Team Overcome Kernel. It Works!
Seriously any custom kernel should do the trick and In Theory even a stock kernel could be make to work [See Notes]
Boot To Recovery ( You should now see Clockwork Recovery Mod )
edit /system/etc/vold.fstab on the device to look like the following. You can use the adb pull command if you are unsure how to get at the file.
[WINDOWS USERS]
Linux and Windows use different newline characters. If you are editing the file on windows make sure you are using an editor suitable for the task (i.e UltraEdit or Notepad++)
Code:
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = disable
format_option = -r 1558
}
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
# externel sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = enable
}
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
One final Reboot should make your Still broken but functioning tablet a little less a bitter pill to swallow (see what I did there)
Note: First boot takes a while. if you are worried or think it is boot looping, you can watch the output using adb logcat
You should now have a working galaxy with the added bonus of a re-sizable data partition.
Tool List:
A Micro SD Card - The Bigger The Better , Size and Speed are everrything as this is where you everything pm your tablet will live. I would definitely pitch for a 32GB Class 10.
A Method of formatting and Partitioning the SDCard. - If your a windows user than you need a method of formatting ext4 partitions. I 'm unsure of the current state if the art regarding that.
A Custom Recovery Image. Clockwork Recovery Mod or something similiar. You can use fasboot from the android sdk to flash it to you device
A Custom Kernel Image. with support for the Ext 4and Fat32 Filesystems.
The Next Step Is To Flash A Rom to the devoce . You Should be able to flash any rom to it as long as Your sdcard Is formatted correctly
I Flash Latest Stock Rom at the time and
[Advanced User and Masochists]
You Can use you own custom recovery and kernel if you are so Inclined.
For Extra "Going To Try This Because It's There! an I can" Points
Retain A full Stock Experience. When Booting From SD.
It Should be Possible, If can find a way to format the sdcard partitions to Samsung Proprietary RFS File System.
This was also the reason a custom kernel was used ;
Does this mean that the internal SD Card is no longer fixable?
Unsucessful
Trying this with latinamerica Galaxy Tab (P1000) but with no success, at least at the moment. I tried humberOS kernel (For Latam) phone but stucked at a permanent boot loop. I was sucessful with odin and a tarball without hidden file. Then zimage (HumberOS).
How did you change the vsftab file? Any specific procedure for this?
Hi,
Thanks for posting this. Was a great shortcut through my problem.
The ROM i tried it with though wont let me type with the keyboard...i just get "null" for every key...although curiously i can backspace each one of letters in "n-u-l-l".
I did this late last night and i think somehow i have used a ROM from somewhere random in europe by mistake and not got the locals setup or something...i'm just going to try a different ROM though because i'm confused as to where i got it now...
Succesful
Succesful with LatinAmerica Version Gingerbread from Humberos.
However galaxy tab doesnt recognize sdcard partition, so i cant install anything at all.
download files or take pics.
Any tips?
Oh wow... I can't believe this happens...
Sent from my GT-P6800 using Tapatalk
fluffmonster said:
Oh wow... I can't believe this happens...
Sent from my GT-P6800 using Tapatalk
Click to expand...
Click to collapse
neither can I :/ Hope it doesn't happen to me though (or anyone else for that matter)
corrupted internal sdcard
Hello guys. I have a problem with my Samsung Galaxy Tab, my internal sdcard is corrupted . I tried to use Odin as well as heimdall to flash my device with any custom firmware, it didn't work (no internal sdcard). Finally I tried the MIUI firmware (I tried CM7 as well but didn't like it) based on CWM Recovery v5.0.2.7. Somehow it recognised my external sdcard as internal one . As a result I have two partitions in my system that correspond to my external sdcard:
Code:
C:\tools>adb shell
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 16.0 GB, 16021192704 bytes
255 heads, 63 sectors/track, 1947 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1818 14597656 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 1818 1948 1048039+ 83 Linux
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: SD NCard (sd/mmc)
Disk /dev/block/mmcblk0: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 14.9GB 14.9GB primary fat32 lba
2 14.9GB 16.0GB 1073MB primary ext4
But the system see only partition 2 (ext4) as an internal memory. Partition 1 is missed although I can see it in recovery mod and install firmware from it. sdcard is unavailable in the android system. So I can download and use only small aplications that don't require sdcard. But I can't deal with apps, that asks for sdcard. I need to make MIUI see my partition 1 as an sdcard, but I don't know how to do that. I suppose the solution is in editing
"/system/build.prop"
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MIUI-XJ
ro.build.display.id=MIUI.2.3.10
ro.build.version.incremental=2.3.10
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Fri Mar 10 11:56:49 CST 2012
ro.build.date.utc=1331265409
ro.build.type=userdebug
ro.build.user=xjmod
ro.build.host=builder
ro.build.tags=test-keys
ro.product.model=GT-P1000
ro.product.brand=samsung
ro.product.name=P1000
ro.product.device=galaxytab
ro.product.board=GT-P1000
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=en_us
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxytab
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=galaxytab-userdebug 2.3.7 MIUI 2.3.10 test-keys
ro.build.fingerprint=samsung/galaxytab/galaxytab:2.3.7/MIUI/2.3.10:userdebug/test-keys
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d[SPACE]/dev/s3c2410_serial3
ro.sf.lcd_density=240
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
wifi.interface=eth0
wifi.supplicant_scan_interval=20
ro.telephony.ril_class=samsung
# mobiledata.interfaces=eth0,pdp0
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
dalvik.vm.heapsize=48m
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
ro.removablemounts=/mnt/sdcard/external_sd
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.url.legal=
ro.url.legal.android_privacy=
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.setupwizard.mode=OPTIONAL
ro.com.android.dataroaming=false
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
persist.sys.mitalk.enable=false
ro.moddevice=P1000
ro.config.ringtone=MI.ogg
ro.config.notification_sound=FadeIn.ogg
ro.config.alarm_alert=ClassicAlarm.ogg
ro.config.sms_received_sound=FadeIn.ogg
ro.config.sms_delivered_sound=MessageComplete.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
#
# XJ ADDED BUILD PROPERTIES
#
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=1000
ro.additionalmounts=/mnt/emmc
ro.phone_storage=1
ro.gps.soket=/data/gpspipe
ro.sf.hwrotation=90
ro.modversion=MIUI-XJ-GT-P1000
ro.setupwizard.enable_bypass=1
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=false
stagefright.enable-player=false
phone.ril.classname=com.android.internal.telephony.SamsungRIL
dev.sfbootcomplete=0
# LTTLDVL
video.accelerate.hw=1
ro.media.enc.jpeg.quality=100
ro.HOME_APP_ADJ=1
debug.performance.tuning=1
and "/system/etc/vold.fstab"
Code:
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# internal sdcard
dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc3
# external sdcard
dev_mount sdcard/external_sd /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1 /devices/platform/s3c-sdhci.2/mmc_host/mmc2
#end line ## keep this line
I tried to correct these two files in different ways but no result at all. I know that the solution of my problem is very close and I suppose it is simple. I'll be glad to get any sugestion in solving my problem.
Facing same kind of problem , but tab isn't p1000 , its Spirint SPH-P100 , its got 2GB.
Above Method will only work if you have modified kernel.
what is the solution?
So, what is the solution or a 100% valid workaround for this? Maybe it is necessary to replace motherboard or something. Anyway this is for gingerbread and i need ics. Any ideas? Or maybe some examples files for ics? I Really appreciate your help.
there is no ICS that you can flash using Heimdall/Odin yet. So you can't use this method.
This method can be used for ICS as long as your kernel supports all the formats (ext2,ext3.ext4) . Stock kernel do not support ext3 or ext4 ,so if you trying on stock kernel you should try ext2 partition on you sd card.
I tried to put Overcome Kernel 4 on my TAB, odin flashed it without a problem, but on device there is still old recovery. I cannot root my device as TAB won't come to normal screen it loops at samsung screen. Any solution ?
Thanks.
Maybe you need to restock to GB stock safe v5 with repartition first.
Sent from my GT-P1000 using XDA
I allready tried with gb safe rom, It hangs at hidden file. After that i install kernel. Phone still hangs at samsung sign., When I put in recoveri mod it shows normal recovery not CW recovery.
Anythig else I can try ?
Thanks.
ics partition scheme and file
Well, hoping there is a partition scheme and files for ics. I really want ics in my galaxy tab with internal sd damaged. Who knows about this?
waqasshahzad1986 said:
This method can be used for ICS as long as your kernel supports all the formats (ext2,ext3.ext4) . Stock kernel do not support ext3 or ext4 ,so if you trying on stock kernel you should try ext2 partition on you sd card.
Click to expand...
Click to collapse
Ok i will try this tomorrow. Maybe this could be the reason. I will use ext2.
Hi Folks.... The OP here. I was just looking over some of my old threads and notice this one was active. Maybe I should subscribe to it
The actual device was returned a very happy owner I never see him without now! but It does mean I no longer have It as a reference, so I can't answer Rom Specific questions but I can flesh the details out a bit,
The Tab was a P1000 which had been acquired in the middle east. I received it in a bootlooping with stock recovery because I'm that Tech Guy that people know..... I actually knew sod all about Hardware at that point but It's just a computer at the end of the day so I let the fun begin.
Looking back at the original post, It's definitely an How To:
I'll update the Original Post, to reflect the greater understanding I have as to the Whys of this fix!
Also anyone / everyone whos had this problem post the dmesg output as an attachment.
There is nothing worst than scrolling through a cople of post containing full dmesg/logcat dumps and one line replies which re-quote the full post.
Question 1, how did you determine the number of and type of Ext2,3,4 partitions to create on the SD?
Q2, are you saying if you Odin flash a ROM it will automatically install it to the SD?
Q3, could a GB or ICS CWM ROM be modified so that the appropriate files are modified before hand and then just flashed with recovery?
Hi Black6spdZ
Thanks for the questions, they have helped In jogging my memory , I assume you have got an Internal flash failure?
Black6spdZ said:
Question 1, how did you determine the number of and type of Ext2,3,4 partitions to create on the SD?
Click to expand...
Click to collapse
A: I believe this is based on the pit (Partition Infomation Table) file which in this case was gt-p1000_mr.pit. However I just stopped when the process stopped ask for them
Black6spdZ said:
Q2, are you saying if you Odin flash a ROM it will automatically install it to the SD?
Click to expand...
Click to collapse
A: The flash process flashes to the first SD/MMC Card which after an Internal Failure is the one in the external card slot
Black6spdZ said:
Q3, could a GB or ICS CWM ROM be modified so that the appropriate files are modified before hand and then just flashed with recovery?
Click to expand...
Click to collapse
I don't know is the short answer. I recall having trouble locating a custom rom and all the stocks where In one placeplus the person I was looking at this for was new to android so stock felt the right way to go.
I've updated the original post, I seemed to have messed up the formatting which won't have helped anyone I the slightest. Sorry about that.
Like I've mentioned I no longer have the device in my possession and my main device(S) are HTC and the moment. I have emai that guy who tab it is so I can try the flashing ICS to it.
Hello guys and gals!
I've recently flashed my first rom on to my SG4 and when I got it from sprint with the stock rom (4.2.2 , MF9) it would allow me to move apps to my 64gb10 class sd card but now it won't even give me the option with the new rom, the rom is fantastic no glitches or lag and as it was restoring my internal storage was full in a few minutes and when I tried to move my apps there was no button (option) at all for it.
I've tried to swap external with internal memory no luck so far :[
Please help any help would do. I'm new to the fourms and i have tried searching as far as i can get no one else is posting same post as mine. I'm a noob on the tech stuff not super smart or too dumb average. Also if i do a factory rest on my rooted liquid smooth rom will it get bricked or will it go back to liquid smooth, as it was on first time install.
Here's the main thread (where i got it from) http://forum.xda-developers.com/showthread.php?t=2264782
bounddyy said:
Hello guys and gals!
I've recently flashed my first rom on to my SG4 and when I got it from sprint with the stock rom (4.2.2 , MF9) it would allow me to move apps to my 64gb10 class sd card but now it won't even give me the option with the new rom, the rom is fantastic no glitches or lag and as it was restoring my internal storage was full in a few minutes and when I tried to move my apps there was no button (option) at all for it.
I've tried to swap external with internal memory no luck so far :[
Please help any help would do. I'm new to the fourms and i have tried searching as far as i can get no one else is posting same post as mine. I'm a noob on the tech stuff not super smart or too dumb average. Also if i do a factory rest on my rooted liquid smooth rom will it get bricked or will it go back to liquid smooth, as it was on first time install.
Here's the main thread (where i got it from) http://forum.xda-developers.com/showthread.php?t=2264782
Click to expand...
Click to collapse
Once you download a aosp ROM your no longer in mf9 based ROM so that option to move apps to SD card goes away.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Once you download a aosp ROM your no longer in mf9 based ROM so that option to move apps to SD card goes away.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Yupp, exactly what he said. You are no longer on TouchWiz software so there is no apps 2 SD unless AOSP adds it in. There are apps on the Play Store I believe though that can do this.
ROMANTiC KiD said:
Once you download a aosp ROM your no longer in mf9 based ROM so that option to move apps to SD card goes away.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Okay I understand, what about switching external into internal and internal to external? I had it almost with a program that flips those lines but it turned my external and internal to be both directed to my sd card so had to flash rom again.
But here is my Vold file text. Can you show or edit it properly please!?
If you need anymore info let me know I can send you screenshots or file paths etc... :fingers-crossed:
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
## storage_struct - ex) series, "/mnt/sdcard/extStorages" / parallel
######################
# internal sdcard
#dev_mount emmc /mnt/emmc 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
# external sdcard
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.4/mmc_host/mmc2/ /devices/platform/msm_sdcc.2/mmc_host/mmc2/
#otg sdcard
dev_mount sda /storage/usbdisk0 auto /devices/platform/msm_hsusb_host/usb1
Problem statement
The Amazon Fire TV has a limited memory sotrage of less than 5GB.
FolderMount allows for moving App data/obb to a USB device. Remaining components of the App, which sometimes are the larger part of the app, can't be transfered using
These remaining components can be 100s of MB and even above 1GB (Sine Mora is 292MB, Walking Dead is 1.14GB)
Solution
Link2SD allows for moving these components to an external SD card in the phone world. Below I'll describe how to do this on the Amazon Fire TV with a USB device.
This post heavily relies on tweaking a post by sashavasko. Major kudos to him. Up to finding his post I was not successful in mounting in a way that Link2SD could see the mount. This was due to a change in Android 4.2+ where one App's mounting isn't seen by others.
Below is a step by step guide for running this. I've posted a script for automating this here : http://forum.xda-developers.com/showpost.php?p=54601505&postcount=33
Requirements: Root, Mouse, Terminal Application
Step 0 - Preparations : Format a USB device to the Ext4 File system and install Link2SD
Ext4
Link2SD refers to parititoning your SDcard to both Ext4 and FAT, this is not required on our USB device. All we need is an Ext4 partiton we can mount for Link2SD.
I had a high end USB device I used for FolderMount. For testing, I got a 16GB Lexar Jump Drive, which got decent reviews. $8 at Staples ( even less with the right coupon. Other sizes are also cheap). Both went into my Powered USB hub.
You can also partition a single FAT32 USB device to two partitons - FAT32 and Ext4. I have verified both options. Please note that for this second option, if you already have files on your FAT32 USB device, you'd have to first copy them to a backup, as the partitioning trashes your data. You will then need to restore the backed up files to the FAT partition.
Format/Partition your USB device to Ext4 using free MiniTool Partition Wizard Home Edition on your Desktop/Laptop. Below is a nice post on this (Refer only to step 1), you can find others. Please note that this refers to an SDCard. We will be doing this on a USB device.
http://forum.xda-developers.com/showpost.php?p=37405779&postcount=1
In partitioning, please verify the partitions are created as Primary. Also, not sure is this is required, but I didn't name my partitions.
There are also linux commands to do this - I didn't investigate these.
Stick the Ext4 partitoned USB device into your Amazon Fire TV and power it up. We will need the device in for Step 2.
Link2SD
Download Link2SD from the Google Play store, or sideload it
Make the directory Link2SD requires
Code:
su
mkdir /data/sdext2
exit
Step 1 - Fix adb localhost
Follow step 1 in sashavasko's post
http://forum.xda-developers.com/showpost.php?p=45102645&postcount=1
Note1:
You will need a terminal app for this
Note2:
This step should only be run once. Running multiple times can mess the /data/misc/adb/adb_keys file as the key values will concatenate with sashavasko's method. This will cause mounting at boot not to work. If you did this or not sure if you've done this, just erase the duplicate keys from the /data/misc/adb/adb_keys file (the end of a single key is "[email protected] ). Or, better yet, if you aren't seeing any other different keys there - simply su and copy /sdcard/.android/adbkey.pub onto this file.
Step 2 - Install scripts
Follow step 2 in sashavasko's post
http://forum.xda-developers.com/showpost.php?p=45102645&postcount=1
Note 1
Look for your Ext4 partitoned device after running:
Code:
adb shell cat /proc/partitions
You should find the Ext4 device under /device/block starting with sd.
For example: My first USB device is sda1, the Ext4 partitoned one was sdb1 (sdb2 when the Lexar drive was partitoned to FAT32 and Ext4).
You should be able to recognize the devices according to their partition sizes.
Note 2
The msd2.sh file should be changed to be:
Code:
#!/system/bin/sh
mount -t ext4 [COLOR="Purple"]/dev/block/[/COLOR][COLOR="Red"]sdb1[/COLOR][COLOR="purple"] /data/sdext2 [/COLOR]&& sleep 5 && /system/bin/vold
where the sdb1 device should be replaced by the device you located in Note 1.
Step 3 - Test the script and grant su permissions
Run this (no su command required, no path to the sd.sh file is required)
Code:
sd.sh
Verify you aren't seeing any errors. You will be granting SU permissions.
Run Link2SD. Go to the menu at the top right. Select "Storage Info" - Verify Link2SD recognizes the Ext4 partiton in the third line (under SD Card 2nd Part. ).
Step 4 - Auto Mount at initialization
For this I'm using the /system/etc/install-recovery.sh script which you should already have. This script loads at boot and calls /system/etc/install-recovery-2.sh (a non existent file).
Create a file at /sdcard/install-recovery-2.sh which contains
Code:
#!/system/bin/sh
/system/xbin/sd.sh
Now move the file to its place:
Code:
su
mount -o rw,remount /system
cp /sdcard/install-recovery-2.sh /system/etc/
chmod 755 /system/etc/install-recovery-2.sh
mount -o ro,remount /system
exit
Now Reboot (Long press remote Select + Play)
Step 5 - Link2SD ready to go
Open Link2SD to verify (as you verified before) that after boot Link2SD sees the Ext4 partiton.
Start moving files using Link2SD :
Select an App
Go to "Create Link" - You will be asked which file types to move. Check them all (not the paid option if you haven't paid).
Link2SD will show "Creating Link...", then an advert (in the non payed version) and then: Application files linked and moved to SD card
Note the expected storage change in the Amazon Fire TV's "About" menu option will be seen after Rebooting.
"Remove Link" works properly
"Move to SD card" is not relevant
Final Words
Don't use this to move system apps, or system-like apps
Responsibly for running this is solely on you. I am only describing what works for me.
Works great thanks
I'd love to see a standalone app for installing this.
Sent from my SM-N900V using XDA Premium 4 mobile app
The msd2.sh file mentioned in Step2/Note2 is used to create a fake external SD Ext4 partition for Link2SD.
You can also use it to create a fake external SD FAT partition at /storage/sdcard1 for FolderMount.
FolderMount automatically recognizes this partition and suggests this as the initial path for its destination path suggestion.
In my case - sda1 is the FAT partition (For me - a USB stick fully formatted to FAT32), and sdb1 is the ext4 formatted USB stick. The same should work with a single partitioned USB stick (but different sd* device names - see original post).
The updated msd2.sh file looks like:
Code:
#!/system/bin/sh
[COLOR="DarkGreen"]mount -t vfat /dev/block/[COLOR="Red"]sda1[/COLOR] /storage/sdcard1[/COLOR] && mount -t ext4 [COLOR="Magenta"]/dev/block/[/COLOR][COLOR="Red"]sdb1[/COLOR] [COLOR="Magenta"]/data/sdext2[/COLOR] && sleep 5 && /system/bin/vold
SaltyCookie_OnLoan2FM_SVE said:
The msd2.sh file mentioned in Step2/Note2 is used to create a fake external SD Ext4 partition for Link2SD.
You can also use it to create a fake external SD FAT partition at /storage/sdcard1 for FolderMount.
FolderMount automatically recognizes this partition and suggests this as the initial path for its destination path suggestion.
In my case - sda1 is the FAT partition (For me - a USB stick fully formatted to FAT32), and sdb1 is the ext4 formatted USB stick. The same should work with a single partitioned USB stick (but different sd* device names - see original post).
The updated msd2.sh file looks like:
Code:
#!/system/bin/sh
[COLOR="DarkGreen"]mount -t vfat /dev/block/[COLOR="Red"]sda1[/COLOR] /storage/sdcard1[/COLOR] && mount -t ext4 [COLOR="Magenta"]/dev/block/[/COLOR][COLOR="Red"]sdb1[/COLOR] [COLOR="Magenta"]/data/sdext2[/COLOR] && sleep 5 && /system/bin/vold
Click to expand...
Click to collapse
The one annoying thing about this is during boot it will read the entire partition. This in turn in my case makes booting the Fire TV really slow. Lets hope I dont have to reboot much because it now takes around 2-3 minutes to boot up.
MadFlava said:
I'd love to see a standalone app for installing this.
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I 2nd this. This is as close as we're gonna get to downloading Apps, ets., straight to an attached external drive but I know enough about this stuff to be somewhat intimidated by the initial instructions. Not that they're not clear, it just looks like I'd have too many avenues to brick my box.
Still...very good work OP. Thanks again.
MarkBP said:
I 2nd this. This is as close as we're gonna get to downloading Apps, ets., straight to an attached external drive but I know enough about this stuff to be somewhat intimidated by the initial instructions. Not that they're not clear, it just looks like I'd have too many avenues to brick my box.
Still...very good work OP. Thanks again.
Click to expand...
Click to collapse
Come on guys, this is XDA developers
OK, I have this brewing. Should post it by tomorrow.
awesome. how easy is it to reverse this entire process? I'd really like to know the risks before I take the plunge
I think the process can be greatly simplified. On my computer I created install-recovery-2.sh with the two lines below:
#!/system/bin/sh
mount -t vfat /dev/block/sda1 /storage/sdcard1 && mount -t ext4 /dev/block/sda2 /data/sdext2 && /system/bin/vold
Then I connected via adb to the fireTV from my computer.
Then an adb push of install-recovery-2.sh to /sdcard and then did an adb shell to the fireTV from my computer and su once there.
Copied from install-recovery-2.sh from /sdcard to /system/etc
Did a chmod 755 on the file to make it executable and then rebooted and all seems to be working well with partitions recognized.
tselling said:
I think the process can be greatly simplified. On my computer I created install-recovery-2.sh with the two lines below:
#!/system/bin/sh
mount -t vfat /dev/block/sda1 /storage/sdcard1 && mount -t ext4 /dev/block/sda2 /data/sdext2 && /system/bin/vold
Then I connected via adb to the fireTV from my computer.
Then an adb push of install-recovery-2.sh to /sdcard and then did an adb shell to the fireTV from my computer and su once there.
Copied from install-recovery-2.sh from /sdcard to /system/etc
Did a chmod 755 on the file to make it executable and then rebooted and all seems to be working well with partitions recognized.
Click to expand...
Click to collapse
Just tried this, didn't work for me (mount not detected).
- tselling, is Link2sd working with this ?
- If someone is working succesfully with Link2sd using tselling's method please report back. This is indeed a shorter route.
failed for me for tselling method
SaltyCookie_OnLoan2FM_SVE said:
Just tried this, didn't work for me (mount not detected).
- tselling, is Link2sd working with this ?
- If someone is working succesfully with Link2sd using tselling's method please report back. This is indeed a shorter route.
Click to expand...
Click to collapse
Link2sd found ok and I linked sevzero without problems. Should note that I use sda1 and sda2 for fat32 in first primary partition and ext4 on second primary pzrtition of same usb flash drive. Any other setup would need to have different script to match your drive setup.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
why does this need more than 1 partition to work anyways? Is it just because the app requires it for some weird reason?
edit: also which partition needs to be the bigger one? do the sizes matter? and does stickmount need to be disabled for this to work?
desc
meadtj said:
why does this need more than 1 partition to work anyways? Is it just because the app requires it for some weird reason?
edit: also which partition needs to be the bigger one? do the sizes matter? and does stickmount need to be disabled for this to work?
Click to expand...
Click to collapse
why does this need more than 1 partition to work anyways? - Link2sd description in play store:
What you need for linking apps:
● root permission.
● a second partition on your SD card.
You should have two partitions on SD card and both should be primary.
The first FAT partition is your standard SD card storage. The second partition is used for application files and can be ext2, ext3, ext4, f2fs or FAT.
You need to use a non-FAT file system (ext2, ext3, ext4 or f2fs) on your second partition in order to link app's private data files. Because the FAT file system (FAT16, FAT32 or exFAT) does not support UNIX file ownership or permissions and will cause a security breakdown of app's private files.
Link2SD Plus can move app's private data files if you have a non-FAT partition
Click to expand...
Click to collapse
So we may be able to use FAT (haven't tried it) but we will lose some moving capabilities.
From my testing - FolderMount does work with the ext4 partiton, so I need two partitions (or 2 usb sticks).
also which partition needs to be the bigger one? - No restriction. Allocate as per your decision and experience with storage costs of apps.
do the sizes matter? - Don't believe her. It does.
Sorry. Uncalled for. Apologies. Not personal. I just had to.
and does stickmount need to be disabled for this to work? - No, it doesn't
983
tselling said:
Link2sd found ok and I linked sevzero without problems. Should note that I use sda1 and sda2 for fat32 in first primary partition and ext4 on second primary pzrtition of same usb flash drive. Any other setup would need to have different script to match your drive setup.
Click to expand...
Click to collapse
Ok, let's try and minimize this. Could it be due to tselling using a single partitioned USB drive, while I'm using two drives ?
I need a report back from someone with a single USB drive who tried tselling's simpler approach. If it failed - Maybe tselling added something along that he wasn't aware of. If it passed - Maybe that's a requirement for the simpler approach.
In other news, the script to automate this is take slightly more than I thought, due to unix-android differences (I come from a unix background). That, and the fact that we may have a simpler solution is delaying me. Oh, also had to stay late at work yesterday, Oooh and the dog ate my laptop.
What about Foldermount?
What about FolderMount for Data and OBB files? Can I still use it with Link2SD on same card?
SaltyCookie_OnLoan2FM_SVE said:
Ok, let's try and minimize this. Could it be due to tselling using a single partitioned USB drive, while I'm using two drives ?
I need a report back from someone with a single USB drive who tried tselling's simpler approach. If it failed - Maybe tselling added something along that he wasn't aware of. If it passed - Maybe that's a requirement for the simpler approach.
In other news, the script to automate this is take slightly more than I thought, due to unix-android differences (I come from a unix background). That, and the fact that we may have a simpler solution is delaying me. Oh, also had to stay late at work yesterday, Oooh and the dog ate my laptop.
Click to expand...
Click to collapse
I think it has to do with the mount points. I have the ext4 partition mounted to /data/ext2 where I think link2sd looks. I think that you could use an entire usb stick with one partition as ext4 mounted to /data/ext2 but your script would change
FROM
##############################################################################################
#!/system/bin/sh
mount -t vfat /dev/block/sda1 /storage/sdcard1 && mount -t ext4 /dev/block/sda2 /data/sdext2 && /system/bin/vold
#############################################################################################
TO
###################################################
#!/system/bin/sh
mount -t ext4 /dev/block/sda1 /data/sdext2 && /system/bin/vold
###################################################
However, I have not tried this. I may try this later today since I have a second fireTV and usb stick arriving today.
also, I am planning to use foldermount with the first fat32 partition I created, but I haven't gotten that far as I want to use the Pro version but need the play store loaded first.
OOPS, I did forget one part "mkdir /data/sdext2" (otherwise the mount fails).
tselling said:
I think it has to do with the mount points. I have the ext4 partition mounted to /data/ext2 where I think link2sd looks. I think that you could use an entire usb stick with one partition as ext4 mounted to /data/ext2 but your script would change
FROM
##############################################################################################
#!/system/bin/sh
mount -t vfat /dev/block/sda1 /storage/sdcard1 && mount -t ext4 /dev/block/sda2 /data/sdext2 && /system/bin/vold
#############################################################################################
TO
###################################################
#!/system/bin/sh
mount -t ext4 /dev/block/sda1 /data/sdext2 && /system/bin/vold
###################################################
However, I have not tried this. I may try this later today since I have a second fireTV and usb stick arriving today.
also, I am planning to use foldermount with the first fat32 partition I created, but I haven't gotten that far as I want to use the Pro version but need the play store loaded first.
Click to expand...
Click to collapse
tselling said:
OOPS, I did forget one part "mkdir /data/ext2" (otherwise the mount fails).
Click to expand...
Click to collapse
i did that too but still didnt work, maybe bc i have 3 partitions. Fat then Ext2 then NTFS
meadtj said:
i did that too but still didnt work, maybe bc i have 3 partitions. Fat then Ext2 then NTFS
Click to expand...
Click to collapse
Sorry, the directory is /data/sdext2
Your mount command is:
mount -t ext4 /dev/block/sda2 /data/sdext2 && /system/bin/vold
Also I am not 100% sure that ext2 filesystem works. ext4 works for sure.
Hello!
I've been searching thru the web and these forums for an answer, but I didn't find it. Does anyone how to Swap SDCard & ExtSdCard on Samsung's official 5.0.1 ROM?
Thanks!:fingers-crossed:
This may not work on the S4 and you run the risk of bricking the device if you choose to attempt it. I will not be held responsible if something happens.
Root, then pull a copy of vold.fstab from /system/etc to your PC and edit using notepad++. Flip the mount points for SDCard and ExtSDCard, then push the edited file back to /system/etc and reboot the S4. If you have an on-board text editor you can simply edit the copy of vold.fstab right on the device. But editing directly on the device can be a bit painful, so using a PC is better.
Example vold.fstab.
Code:
# Mounts the first usable partition of the specified device
#/devices/platform/awsmc.3/mmc_host for sdio
dev_mount sdcard /mnt/sdcard auto /devices/virtual/block/nandi
dev_mount extsd /mnt/extsd auto /devices/platform/sunxi-mmc.1/mmc_host /devices/platform/sunxi-mmc.0/mmc_host
dev_mount usbhost1 /mnt/usbhost1 auto /devices/platform/sw-ehci.1 /devices/platform/sw_hcd_host0 /devices/platform/sw-ehci.2
After editing.
Code:
# Mounts the first usable partition of the specified device
#/devices/platform/awsmc.3/mmc_host for sdio
dev_mount sdcard /mnt/sdcard auto /devices/platform/sunxi-mmc.1/mmc_host /devices/platform/sunxi-mmc.0/mmc_host
dev_mount extsd /mnt/extsd auto /devices/virtual/block/nandi
dev_mount usbhost1 /mnt/usbhost1 auto /devices/platform/sw-ehci.1 /devices/platform/sw_hcd_host0 /devices/platform/sw-ehci.2