Related
OK so far my problem has stumped everyone.
I have a rooted and hacked G1(HTC Dream) with a 16GB MicroSDHC that is divided into a 2GB Ext2 partition and a 14GB FAT32 partition. It worked fine for a while but then my G1 started to freeze up and reboot continuously so I took the card out and it stopped. I tried chkdsk in Vista and it hung in elevated .cmd prompt and it says i have bad sectors but it cannot fix in read only mode. I tried format in Vista and cmd and it tries, says the data is RAW and that it tried to convert to FAT but cluster size too big. Then when I try fs command for vfat in .cmd it still won't work. I used Paragon Partition Manager 9.0 PAID version to create partitions but now it hangs every time it tries to read the card and it won't format. Tried sdformatter and a low level formatter to and no good.
I have Terminal in my G1 but I am not familiar with Linux commands. I tried fdisk and it says the FAT32 is in read only mode. When I type busybox df -h it won't show the "/dev/block/mmcblk0p1" but it shows the Ext2 partition. But when I type the mount command it shows up as "rw". But i cannot access it at all to wipe the stupid card out.
HELP!!!!
1) can you mount the fat32 partition in you phone and can see the files?
2) did you tried as root *mount -o rw,remount -t vfat /sdcard* ?
Yes I tried it and it doesn't work. Is there anyway to flash the bootloader or the ramdisk?
assuming i have ramdisk.img boot.img and system.img on sdcard root and I want to copy to system files, anyone know the commands in Terminal Emulator?
Download the ubuntu live cd, burn it, then boot your computer with it. Plug your SD card into an external reader, NOT the g1. Run gparted and select the sd card from the list of drives and see if you can format or re-partition your card. If it wont let you then try selecting Device->Create Partition Table, to create a new partition table. If none of that works then either your card or card reader is dead.
Mike
Nevermind, it was a class 2 16GB card...i think I broke it...getting a class 6...
need help....
i have a 16gb class 6 and i need help or technically a walk through on how to partition this card....hence i am an extreme noob. i got into parted and it says i have a 16.1 gb so would that translate to 16001 mb? reason i ask is cause i dont know what to subtract 32mb from and such? also what is the optimal set up for a card this size? thanx in advance for any help that you guys may supply me...
TeCH NiNJa said:
i have a 16gb class 6 and i need help or technically a walk through on how to partition this card....hence i am an extreme noob. i got into parted and it says i have a 16.1 gb so would that translate to 16001 mb? reason i ask is cause i dont know what to subtract 32mb from and such? also what is the optimal set up for a card this size? thanx in advance for any help that you guys may supply me...
Click to expand...
Click to collapse
do it from phone terminal its much easier, if you need any more help pm me
i got guys thanks alot....i think ill try 42mb linux-swap to see if the hero rom will run smoother. to
JJbdoggg
Senior Member
thanx
What does this notification really mean? I'm running CM7 off an 8G SanDisk. The /sdcard filesystem appears intact, it mounts properly on CM7 and Linux, but this notification won't go away.
fsck on Linux reports no problems.
Might something be confused about partitions? I can't mount /emmc for some reason, CWM can't mount it when I tell it to format it, and USB mode doesn't export it, although it looks like it's trying to; Linux reports a /dev/sde (along with /sdcard at /dev/sdd), but it can't be used:
Code:
# fsck /dev/sde
e2fsck: No medium found while trying to open /dev/sde
Any ideas?
Thanks!
Dennis
Fixed it!
To recap, I'm running CM7 from SD. I was getting a "Damaged SD Card" notification, and my /emmc vanished, and it wouldn't export via USB ("No media present" was the error reported by Linux, although /dev/sde was created), and CWM couldn't format it for me (why not?).
Both were apparently from the same cause. I repaired mmcblk0p8, and now my /emmc is back and the Damaged notification is gone.
So, if you're getting that notification, it may not be about your SD card!
Details: I couldn't use dd from Linux, but I could dd if=...blk0p8 within Terminal Emulator. My busybox doesn't have mkfs.vfat, so I used dd to copy /boot onto the partition; this gives it a (small but sane) filesystem. I rebooted to get /emmc mounted properly (check fstab.vold for the gory details), connected the cable to my Linux PC, checked that the expected contents were on /dev/sde, unmounted it (command line, not via GUI) and ran sudo mkfs.vfat -I -n MyNookColor /dev/sde from the Linux command line. All is now well.
i hv the same issue but since i'm a noob at nook color and i dont knw anything abt linux... i hv no clue what your are talking about...
it would be a gr8 help to me and others who are not well versed with linux, if you could tell me exactly what did u do to fix this problem.
please help me with this issue.
ty
sd
stavan_d said:
i hv the same issue but since i'm a noob at nook color and i dont knw anything abt linux... i hv no clue what your are talking about...
it would be a gr8 help to me and others who are not well versed with linux, if you could tell me exactly what did u do to fix this problem.
Click to expand...
Click to collapse
Android is just as much a Linux system as Ubuntu or Fedora.
This applies if and only if Settings/Storage claims that you have no /emmc or /mnt/emmc, and if you've installed CM7 to emmc. Read the headers carefully.
Start Terminal Emulator.
In this window, type su. The prompt changes to #.
Type df.
If there's a listing for /mnt/emmc or just /emmc, try something else; this isn't for you.
We're going to reconstruct /emmc by copying /boot onto it. THIS WILL ERASE /emmc!!!
Type VERY CAREFULLY:
dd if=/dev/block/mmcblk0p1 of=/dev/block/mmcblk0p8
That's blk zero pee one and blk zero pee eight.
This will grind away for quite some time.
When it's done, reboot.
If you still get the notification, you have some other problem.
You now have a tiny /emmc instead of the 5G partition that should be there. Plug the cable into your PC, enable USB mounting, and verify that one of the volumes looks like a boot partition. If you run a Linux PC, check the device name (mine was /dev/sde, yours is probably different), unmount it, and do the mkfs I showed before.
If you run Windoze, tell it you're done with the /boot drive (like you would do with a thumb drive), and format that device (E:, F:, whichever it was) by (IIRC) right-clicking on it in an Explorer window and selecting Format. Again, SELECTING THE WRONG DEVICE WILL SCREW YOU UP. I am not responsible.
If you're not sure about ANY of these steps, please get expert local help.
Good luck!
Sent from my NookColor using XDA Premium App
i m booting cm7 from the sd card... and settings/storage/additional storage/mnt/emmc Unavailable...
so how do i fix this...
also when i plug NC in boot OS it shows 2 partitions, 1.undefined and 2. 4.98gb... instead of 5gb single partition originally present...
I'm guessing theres no way in CWM recovery to get ext4 am i correct. I've heard that it's ext3 by default, so my question is what program would i need to do this. I am running winblows 7, i do have a built in card reader so i could mount the microsd card from there to partition it.
d12unk13astard said:
I'm guessing theres no way in CWM recovery to get ext4 am i correct. I've heard that it's ext3 by default, so my question is what program would i need to do this. I am running winblows 7, i do have a built in card reader so i could mount the microsd card from there to partition it.
Click to expand...
Click to collapse
taken from
Here
How to manually partition your SD card for Android Apps2SD
Taylor Wimberly on Aug 21, 2009 at 9:27 pm119 comments
5share0share4 42
How to manually partition your SD card for Android Apps2SD
Update: You might also want to check out the Amon_RA recovery image which will automatically partition your SD card.
This article is for people with rooted Android phones. Everyone else please ignore. There are dozens of ways to partition your SD card and I would like to share the one that has worked for me every time. I prefer to manually partition my SD card because it gives me complete control.
Requirements before getting started:
Cyanogen Recovery Image v1.4 or greater (Easy to install with the 1-click hack)
SD Card (Class 6 suggested): A-DATA has good prices on Amazon (4GB, 8GB, 16GB)
Android Device Bridge(ADB): Comes with the Android SDK.
Android build that supports Apps2SD: I suggest Cyanogen’s latest stable release (Does Apps2SD automatically)
These instructions apply to both the Windows command prompt and the Mac terminal. As you can see from my screens, I was using Windows Vista. You can partition your SD card at any time, but you might as well do it before you flash a new build of Android. As always, back up your data when performing any hacks. Partitioning your SD card will erase all data on it. I split this guide into 9 steps, but it is not as difficult as it looks. Read the whole thing before starting.
All commands you need to type are in bold (my comments are in parenthesis). If you do not know how to use ADB, leave a comment for help or read ADB for Dummies over at XDA.
Step 1: Connect your phone to your computer via USB. Reboot into recovery mode.
Command:
Code:
adb shell reboot recovery
(this will reboot your phone into Cyanogen’s recovery image. Or power on phone when holding home button)
Command:
Code:
adb shell
(type this after your phone has booted and on the recovery screen. it should take you to a # prompt)
Step 2: Open parted to partition your SD card.
Command:
Code:
parted /dev/block/mmcblk0
(opens parted and mounts your SD card)
Step 3: Check the size and partitions of your SD card. The print command will display this info. You can see the size of my SD card is 7969 MB (8 GB). I have 1 partition which is fat32. If your SD card is blank and no partitions are listed, you can skip to Step 5.
Command:
Code:
print
(displays SD card information)
Step 4: Remove all existing partitions. If you have multiple partitions, remove each one at a time.
Command:
Code:
rm 1
(deletes partition number 1)
Command:
Code:
rm 2
(if needed. keep going till all partitions are removed)
Command:
Code:
print
(check when you are done to make sure all partitions are removed)
Step 5: Create your new partitions. You can make these any size, but the most common setup is 32 MB linux-swap partition, 512 MB ext2 partition, and remaining free space as a fat32 partition. In order to work properly, the partitions must be created in this order: fat32, ext2, linux-swap.
The linux-swap partition is used for a swap file on some builds. Not all builds use linux-swap, but I create one just in case I ever need it.
The ext2 partition is where your apps will be installed. I use 512 MB which gives me plenty of room but you can go larger like 1024 MB if you want. Parted only creates ext2 partitions and we can convert them to ext3 or ext4 later.
When using the Linux command mkpartfs, you must tell it where to start and and end each partition. This can be done by taking the total SD card size and subtracting the linux-swap then ext2 partition sizes. See the following example for my 8 GB card.
Command:
Code:
mkpartfs primary fat32 0 7425
(start is 0 and end is Total C)
Command:
Code:
mkpartfs primary ext2 7425 7937
(start is Total C and end is Total B)
Command:
Code:
mkpartfs primary linux-swap 7937 7969
(start is Total B and end is Total A)
Partition sizes for a 8 GB SD card.
Partition sizes for a 8 GB SD card.
Step 6: Check the sizes of your partitions. Use the command print again to display the partition sizes. If you made any mistakes you can return to Step 4 and remove them.
command:
Code:
print
(displays your partition information)
Step 7: Exit parted and upgrade your ext2 file system to ext3. For most users this is the final step. We suggest all users upgrade to ext3. Its main advantage over ext2 is journaling which improves reliability and eliminates the need to check the file system after an unclean shutdown.
command:
Code:
quit
(exit parted and return to # prompt)
command:
Code:
upgrade_fs
(script to upgrade from ext2 to ext3)
Step 8 (Optional): If you wish, you can upgrade your ext3 partition to ext4. Skip to Step 9 is you wish to use ext3. I asked Cyanogen what file system he uses and he tweeted ext4. The file system offers enhancements like delayed allocation. See Wikipedia for more info on ext4.
command:
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
(enter this command from the # prompt)
command:
Code:
e2fsck -fpDC0 /dev/block/mmcblk0p2
(run e2fsck after tune2fs. wait for the file check to finish)
Step 9: Finished. Check your work with print.
command:
Code:
parted /dev/block/mmcblk0
(open parted again)
command:
Code:
print
(check all your system partitions and their sizes)
command:
Code:
quit
(exit parted)
command:
Code:
reboot
(reboot your system to the operating system)
I was under the impression only CWM worked for our mt4g phones... So the AMON_RA recovery would work as well or just the older cyanogenmod 1.4?
I've known about the older cyanogen and amon ra recoveries back when i had my g1, that had ext4 partition built in(cyanogen i had to type in all that extra stuff e2kfs to get ext 4) but had no idea they were avalable fo rour mt4g, where do i download the mt4g amon ra recovery!?
@neidlinger
I appreciate your help, tho i knew those commands and recoveries back when i had the OG tmobile g1 the amon ra 1.7 recovery was the shizznit as it had soo many better options compared to cwm. I answered my own question by reading up into the forums about the dark tremor apps 2sd, i dunno how i missed it the first time but there was an obvious command list that will let you convert an ext partition to 3 or 4 lol It really does help to read up on older posts in development.
All those commands work on CWM. Koush converted the scripts into binary c programs.
You can use adb to run these commands inside the recovery console.
RichieDaze said:
All those commands work on CWM. Koush converted the scripts into bindary c programs.
You can use adb to run these commands inside the recovery console.
Click to expand...
Click to collapse
so just boot into recovery and run adb commands, or do i need to mount sd card thru recovery first.
Sent from my HTC Glacier using XDA Premium App
Try it without mounting. The binary should mount it or display a message telling you to mount it manually.
Please, Let us know the out come!
Have you tried sdparted from the recovery command line? (included in CWM)
It takes the guess work out of using parted!
Source:
[UTIL] sdparted v0.6 - easy sdcard partitioning, upgrading to ext3/4
Can I have external card mounted as ext2? I have files names not supported by fat and sync'ed with dropbox
Yes, you can but afaik there is no easy way to do this.
I formatted my sdcard to ext2 (because I wanted to put large file (image for wikipedia offline) on my sdcard).
I formatted the beginning (~30MB) of my sdcard to fat32 so that the Nook detect the sdcard and does not trigger an error and the remaining part to ext2.
Then I used a script that mount manually the ext2 partition to /sdcard on boot.
This generally works but I have sometimes a few bug in some applications, especially when I connect and disconnect my Nook to my computer...
The best solution would be to find a way so that Android can automount a ext2 partition by itself but I don't know how to do it.
Instead of using the whole card I partitioned the first 4gb as fat16 (msdos) and then set the rest to ext3. When the fat16 space runs out I'll look into making some sort of script to try to mount the second partition. At the moment with the card acts like a normal 4gb card.
is it possible to repartition the nook to be able to use the space that b&n reserves for its contents? I heard that the space for our files is just 250 mb.
user4242 said:
is it possible to repartition the nook to be able to use the space that b&n reserves for its contents? I heard that the space for our files is just 250 mb.
Click to expand...
Click to collapse
yes of course. If you're used to linux repartitioning and the dd command then it's a breeze. If you're a Windows user who've never done partitioning or disk imaging then you can easily mess up.
I'll assume the former.
It's just a case of:
boot with a noogie.img that you've written to a sdcard (root of card, not partition 1)
then plug it in
now you can see all the nook partitions like it's an external USB drive and fdisk, cfdisk, partitionmagic or whatever you want
Obviously you're gonna want to backup first because if you mess up the only way to restore would be asking one of us off this forum to break the distribution laws and send you a 2gb (or whatever it is) image.
All the details on this forum
Has someone tried editing /system/etc/vold.conf to get a ext-formated SD-Card mounted?
mali100 said:
Has someone tried editing /system/etc/vold.conf to get a ext-formated SD-Card mounted?
Click to expand...
Click to collapse
I checked, I had modified it adding a line "partition 2" in the section "volume_sdcard2" so that Android does not show the message "SD card blank or has unsupported filesystem".
But I couldn't make it mount a ext2 sdcard itself. (if you know how to do it without using another script, I'm interested)
Time to resurrect this thread.
FAT is ugly. File timestamps are in local time (whatever that means, summer? winter?).
The Nook vfat implementation has problems with caching in and out directory info on vfat
and intermittently changes all the modify timestamps by 1, 4 or 5 hours.
This can play havoc if you are trying to keep things synchronized by filetime.
I've decided to have my SD card be ext3
Our volume demon, /system/bin/vold (which is ancient) uses /system/etc/vold.conf to configure automounting.
It presumes that all volumes are vfat.
It seems from a brief look inside that it does handle ext2 and ext3 somehow.
There is also the question of getting it to automount USB drives.
The easiest solution to ext3 on the SD card is to make it non-removable.
First, delete the second section out of vold.conf that relates to the SD card.
Then edit init.rc:
Code:
mkdir /sdcard 0777 system system
...
mount ext3 /dev/block/mmcblk1p1 /sdcard nosuid nodev noatime nodiratime uid=1000,gid=1015,fmask=117,dmask=007
chown system sdcard_rw /sdcard
chmod 0770 /sdcard
If you feel like having 12 partitions on your SD card you can.
That leaves vold only handling the mounting of /media
This exists so that you can serve /media as USB Mass Storage.
You could have /media be a fixed mount by doing what you just did to the SD card.
The only hiccup there would be the Adobe Digital Editions wants to see /media as UMS.
Note: To edit init.rc, download bootutil from the signature, extract, edit and replace init.rc in uRamdisk.
Make sure that you have a backup and a recovery!
Note: All of the above changes to init.rc are wrong.
I can get it to mount in a shell, but not in init.rc
Whoops.
Oops, this thread has been forgotten.
Yes, auto-mounting ext3 SDcards has been solved.
See: http://forum.xda-developers.com/showthread.php?t=2184495
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.