Hi,
I already asked for this issue in the this Thread, but didn't got any answer.
I tested these three JB ROMS: CM10, HellyBean and SlimBean.
All of them work nice, except that my internal sdcard does not mount at boot time.
I have to do it manually every time boot up my phone by choosing System Settings --> Storage --> Mount SD card
Anyone have the same issue?
Does anyone have a solution?
Thanks
Same here! Google found this post, perhaps it will find us an answer
xalo2k said:
Hi,
I already asked for this issue in the this Thread, but didn't got any answer.
I tested these three JB ROMS: CM10, HellyBean and SlimBean.
All of them work nice, except that my internal sdcard does not mount at boot time.
I have to do it manually every time boot up my phone by choosing System Settings --> Storage --> Mount SD card
Anyone have the same issue?
Does anyone have a solution?
Thanks
Click to expand...
Click to collapse
toddmworth said:
Same here! Google found this post, perhaps it will find us an answer
Click to expand...
Click to collapse
I have the same issue with my I9000.
Any JB with different kernels makes the internal SD eventually be unmounted. When install a JB ROM the phone works very well but suddenly, the internal SD (phone's SD) is unmounted.
In CWM both SD are mounted and read without any problem. With ICS ROMs the phone works flawlessly.
In my case, the external SD is functioning as expected.(I have a 32 GB micro sd)
The installation language is Spahish - Spain.
No matter which method of cleaning and wiping I use, the result is the same.
Also, starting from GB stock firmware (JVU) flashed with Odin, followed by installing the nightly Cianogen CM10.1 and finally flashing the desired JB ROM works.
I tested Helly Bean, Slim Bean, C-ROM Mix and Baked Blacjbean7 obtaining the same behaviour.
Important: I'm restoring around 54 apk using Titanium backup (games, applications and utilities) in every case. I did not tested the ROMs without these restorations.
marcelogabriel said:
I have the same issue with my I9000.
Any JB with different kernels makes the internal SD eventually be unmounted. When install a JB ROM the phone works very well but suddenly, the internal SD (phone's SD) is unmounted.
In CWM both SD are mounted and read without any problem. With ICS ROMs the phone works flawlessly.
In my case, the external SD is functioning as expected.(I have a 32 GB micro sd)
The installation language is Spahish - Spain.
No matter which method of cleaning and wiping I use, the result is the same.
Also, starting from GB stock firmware (JVU) flashed with Odin, followed by installing the nightly Cianogen CM10.1 and finally flashing the desired JB ROM works.
I tested Helly Bean, Slim Bean, C-ROM Mix and Baked Blacjbean7 obtaining the same behaviour.
Important: I'm restoring around 54 apk using Titanium backup (games, applications and utilities) in every case. I did not tested the ROMs without these restorations.
Click to expand...
Click to collapse
This is the problem I am having. I can see internal sd card on CWM.
But on booting in android, whatever the rom is , does not mount internal sd card on booting android.
Please help to solve this.
Same here
TheMask007 said:
This is the problem I am having. I can see internal sd card on CWM.
But on booting in android, whatever the rom is , does not mount internal sd card on booting android.
Please help to solve this.
Click to expand...
Click to collapse
I have been reading/researching about this issue for about a week (on and off) trying various fixes because this is driving me bonkers.
I have tried:
1) Reduced the amount of used space on my SD Card (Samsung 16gb SDHC) to half
2) Moved as many apps as I can to SD (Noticed more frequent unmounts after this)
3) Removed my Nandroid Back-up from my SD
4) Reflashed CM 10.1
The last thing I am going to try is wiping/reformatting my SD card. If that fails then im suspecting something else is happening at OS/kernel level. I have read in other forums where people have tried a full wipe and restore apps slowly but still get the same unmount. One user has tried another SD card (smaller 4GB one) which seemed to solve their issue?? Weird.
Anyway, I will report back if I have any joy.
In your kernel settings you have the option to mount/unmount system and more or you could write/download a script that mounts the sd card automatically.
Maybe this could help: http://forum.xda-developers.com/showthread.php?t=1971689
I give up.
cixty said:
In your kernel settings you have the option to mount/unmount system and more or you could write/download a script that mounts the sd card automatically.
Maybe this could help: http://forum.xda-developers.com/showthread.php?t=1971689
Click to expand...
Click to collapse
I tried it and no good. It seems as though the Internal SD is mounted, but some error is causing it to operate/display as unmounted via OS.
I completed more testing (extreme):
Wiped Internal SD
Wiped External SD
Try other kernel
Try other CM based ROM
The issue still occurred.
I then reinstalled Stock (XXJVT) via ODIN (Pit 512) and Semaphore kernel to see if its a hardware thing.
Nope.
This combo works amazingly. Infact its faster, smoother and easier to use (along with additional tweaks in Semaphore) than CM10 so I wont be going back to Jelly Bean on this phone. Ever.
Gingerbread for the win!
Hi,
I am using PAC-ROM v22.2 (Jelly Bean) and have the same problem: 80% boot don't mount the internal sdcard (I have no problem with the external sdcard). I can't even mount it manually as xalo2k does, cause I have no "Mount SD Card" menu under Settings/storage.
I spent many hours trying to search for a fix on google, xda, and others with no success. I found a lot of "litterature" on how to mount the sdcard on the PC, or how to swap internal and external cards. However, I don't care about mouting my sdcard on the PC, and I don't want to make believe Android that my external sdcard is the internal one, as I would not like to loose the internal 8GB that the phone is supposed to provide.
In Terminal Emulator, I can do:
> su
> mount -r -w -t vfat /dev/block/mmcblk0p1 /storage/sdcard0
> cd /sdcard
> ls -l
There I can see my files. However, if I exit root, the files don't appear anymore. Hence this looks like a permission problem.
Unfortunately ESExplorer still tells me sdcard0 is not mounted, and my apps (i.e. the camera) aren't able to access it. Additionnaly, the apps I had moved to the sdcard are'nt accessible...
So I tried to fix the permissions. Going under /storage as root, I can see:
drwx------ root root 1970-01-01 01:00 sdcard0
d---rwxr-x system sdcard_rw 1970-01-01 01:00 sdcard1
Si I try:
> busybox chown -R system:sdcard_rw sdcard0
But I get "Operation not permitted" for each dir/file in sdcard0
How comes that an operation is not permitted to the root user ???
Did anyone fix this problem ?
Edit: "You can't chown or chmod a vfat partition let alone a directory within it. You can only change ownership and permissions in fstab and it will apply to all directories and files. So to change ownership of the entire mount point you would change your fstab entry" (see http://ubuntuforums.org/showthread.php?t=1646849)
Thanks and regards
OK guys, I finally found a solution.
Thanks to http://ubuntuforums.org/showthread.php?t=1646849 I mentionned just above, I decided to write an fstab file (the name is important) and placed it under /etc:
/dev/block/mmcblk0p1 /storage/sdcard0 auto rw,uid=1000,gid=1015,fmask=0702,dmask=0702 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Basically, this script is the result of the terminal command (you need to be root):
mount | grep sdcard0 > /etc/fstab
... which I ran after I could get the sdcard mounted (after a mount on PC and eject). But it first failed with errors on options, so I removed a few of them until I kept the lines above.
Then I wrote a little script which I place on my external sdcard which does not have a mount problem at boot:
busybox mount -a
and placed a shortcut to this script on my desktop with SManager.
I just have to click on this shortcut after boot and the internal sdcard gets mounted.
I tried to place this script under /etc/init.d with the hope it would be launched automatically at boot, but this did not mount the sdcard. If anyone knows why ???
Hope this helps !
Well... still having troubles with my sdcard... With the above fstab script I can mount it, access the files, etc...
However, the camera still asks me to insert a sdcard... Is this a permission issue ? Which permissions (owner, group, etc...) does the camera need ? My DCIM dir has the following permissions:
d---rwxr-x system sdcard8RW 2013-06-04 10:36 DCIM
Thanks and regards
- Regis
Loving the CM10 ROMs. Everything has been snappy on my nook since beta 2.
I thought I had the newer (revision 1.2+) nook partition layout (5gb data(apps)/1gb media). But now with CM10 I am getting an out of space error when trying to install new apps. I have moved all apps to my sd card and still get the error about not enough space. If I try and look at the partiton size it looks like it is maybe only 1gb now. Did installing a CM10 ROM change my partition size? Am I missing something else? Perhaps I am just wrong about my original partition sizes.
I searched some threads and the web and saw some discussion on my issue, particularly mention of a 'new CM10 partition layout', but this was confusing at best. It may not have even been nook related, but pertained to some phones.
dcahoe said:
Loving the CM10 ROMs. Everything has been snappy on my nook since beta 2.
I thought I had the newer (revision 1.2+) nook partition layout (5gb data(apps)/1gb media). But now with CM10 I am getting an out of space error when trying to install new apps. I have moved all apps to my sd card and still get the error about not enough space. If I try and look at the partiton size it looks like it is maybe only 1gb now. Did installing a CM10 ROM change my partition size? Am I missing something else? Perhaps I am just wrong about my original partition sizes.
I searched some threads and the web and saw some discussion on my issue, particularly mention of a 'new CM10 partition layout', but this was confusing at best. It may not have even been nook related, but pertained to some phones.
Click to expand...
Click to collapse
You can tell by looking in settings and storage. It will tell you the size of your media storage. If you truly have the 1Gb /data, you might want to look at Dean Gibson's repartitioning thread. He has a 2gb/4gb version.
And no, there is no repartitioning that cm10 does. That was for a phone you saw.
Sent from my Nook HD+ running Tapatalk
Well, I think I do have the 5gb data/1gb media partition layout afterall.
In Setting->Apps->Downloaded it shows at the bottom 'Internal Storage, 753Mb used, 4.2Gb free'.
If I launch a terminal window:
$ df /data
/data Size=4G Used=643M Free=4G Blksize=4096
$ df /emmc
/emmc Size=1G Used=83M Free=942M Blksize=4096
$ df /mnt/sdcard
/mnt/sdcard Size=15G Used=10G Free=4G Blksize=8192
I guess the only app that is giving me the out of space is Titanium Backup. I can't get it to install from either the appstore or from .apk that I downloaded. Both methods start installing and then say 'out of space'. I have been installing and removing other apps along the way with no similar problem.
I did wipe cache/dalvik cache when installing ROM. I also tried CWM Fix Permissions. I also tried CWM Backup -> Wipe Data/Factory Reset -> Restore.
Anyone know why Titanium Backup won't install?
dcahoe said:
Well, I think I do have the 5gb data/1gb media partition layout afterall.
In Setting->Apps->Downloaded it shows at the bottom 'Internal Storage, 753Mb used, 4.2Gb free'.
If I launch a terminal window:
$ df /data
/data Size=4G Used=643M Free=4G Blksize=4096
$ df /emmc
/emmc Size=1G Used=83M Free=942M Blksize=4096
$ df /mnt/sdcard
/mnt/sdcard Size=15G Used=10G Free=4G Blksize=8192
I guess the only app that is giving me the out of space is Titanium Backup. I can't get it to install from either the appstore or from .apk that I downloaded. Both methods start installing and then say 'out of space'. I have been installing and removing other apps along the way with no similar problem.
I did wipe cache/dalvik cache when installing ROM. I also tried CWM Fix Permissions. I also tried CWM Backup -> Wipe Data/Factory Reset -> Restore.
Anyone know why Titanium Backup won't install?
Click to expand...
Click to collapse
The only thing I can think of is some users are having read only problems on both SD card and /data, which is where apps get installed. Have you tried to install other apps since the TB install failed? A test you can try to see if you are one of the users with ro issues is to use a root file manager (there is one built into CM10 now) to create a test file somewhere on /data.
Sent from my Nook HD+ using Tapatalk
LineageOS 11.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 4.4 KitKat, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is LineageOS 11.0 for LG Optimus One OS2SD edition based on androidarmv6 jenkins builds. I made this edition to solve lack of space in our P500 and and improve phone performance because many todays MicroSD cards are faster then this phone internal storage. What it does, it mounts /system and /data on SD card ext4 partitions, so this way you can have as many space as you want to install apps and flash untrimmed gapps without using any a2sd mods, link2sd, manual symlinking or dalvik2cache.
What's working:
Supports all android 4.4 (KitKat) features
Fully functional camera (preview, taking photo, recording video, panorama)
Full H/W acceleration with new adreno drivers, 3D modelling (yamato)
Hardware decoding of videos, Youtube HQ videos
Internet sharing (Bluetooth tethering, USB tethering, Wi-Fi hotspot)
Calls, SMS, MMS, 3G/2G, Mobile data, Data limit
Loudspeaker in call, Manual network search
Usb mass storage, Usb debugging
Wi-Fi, Bluetooth, Bluetooth headset, A2DP (Bluetooth Music), Car dock w/BT
GPS, Sensors, Lights, Touch screen
Funny SIM (128k USIMs)
Browser, GMail, GPlay
Youtube LQ/MQ/HQ
Offmode charging
Known issues
Wi-Fi wakelock because of the old bcm4325 wireless driver
Swipe in stock keyboard because of missing armv6 libs
FM Radio (bcm4325 FM chip is depends on bluez-hcitool)
After Wi-Fi hotspot reboot is required to use Wi-Fi
Installation instructions:
I am not responsible for lost data or dead SD card, do this at your own risk.
Backup all you data with Titanium Backup or alternatively use "Migrating to new file system without loosing data" method
Backup all SD card contents to PC
Flash TWRP recovery (20161230 or later)
While in TWRP go to Advanced>Partition SD Card and use default partition sizes or adjust it depending on your needs.
Also you can do partitioning on computer.
Use exact order and recommended partitions sizes as listed below
FAT32 primary for /sdcard
ext4 primary for /system (448 MB or more)
linux swap primary for /swap (64MB or more)
ext4 primary for /data (1024 MB or more)
Partitioning guides:
MiniTool Partition Wizard (Windows):
You need to start with one partition formatted with fat32 (or unallocated space to create fat32 partition and skip 2 step):
Right click the fat32 partition and use Move/Resize tool to shrink that partition:
Right click on unallocated space and select Create. Following this create ext4, swap and again ext4 partitions:
After that you should end with this configuration (partitions sizes may differ) then hit Apply:
GParted (Linux)
You need to start with one partition formatted with fat32 (or unallocated space to create fat32 partition and skip 2 step):
Click the fat32 partition and resize it to shrink partition:
On unallocated space create create ext4, swap and again ext4 partitions:
After that you should end with this configuration (partitions sizes may differ) then hit Apply:
Copy all SD content from PC back
Flash latest Rom and Gapps
After system booted restore your data with Titianium Backup or alternatively use "Migrating to new file system without loosing data" method
Important! For f2fs rom make sure you have /data partition formatted with f2fs.
Instructions:
Note /data will be formated! Follow method above to backup data.
In TWRP Go to Wipe>Advanced Wipe select Data. Then Repair or Change File System>Change File System>F2FS.
Note: To reverse /data back to EXT4 do the same as above except select EXT4 in last step.
Migrating to new file system without loosing data:
What do I need to migrate without loosing data?
ADB installed on your PC (somehow adb in recovery working only on linux for me) or use Terminal emuliator on TWRP
sdcard with enough memory to backup whole your /data partition
How to perform a migration?
Reboot to recovery.
Go to Mount menu and make sure that /data and /MicroSD are selected.
Open Command Line (Windows) or Terminal (Linux/OS X) on your PC or Terminal emuliator on TWRP
Type: adb shell and press ENTER (skip this if you are using Terminal emuliator on TWRP).
Type: tar -cvpzf /sdcard/data.tar.gz /data
Wait until operation will finish. If you see any error, it means you don’t have enough free space on your SDcard.
Perform steps to format /data to new file system.
Go to Mount menu and make sure that /data and /MicroSD are selected.
Now type: tar -xvpzf /sdcard/data.tar.gz -C /
If previous step didn’t produce any error, reboot your phone and check if it’s boot succesfully. If yes, you can safely remove data.tar.gz file from your SD card.
Done. You have migrated to new file system without loosing your data!
Recommendations:
Use Class 6 or even Class 10 SD card for best performance
CPU settings: SmartassV2 480-748 MHz
I/O Scheduler: I've read that for emmc devices (sd card) best choice is SIO, but Deadline is also very good, please leave your feedback
Screenshots:
DOWNLOADS
Thanks to:
LineageOS for sources
AndroidMeda, Conn O'Griofa and other members of androidarmv6 for bringing KitKat to P500
skinbark, bigsupersquid for help on OS2SD mod
XDA:DevDB Information
LineageOS 11.0 OS2SD, ROM for the LG Optimus One P500
Contributors
HardLight
Source Code: https://github.com/os2sd
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Created 2014-10-17
Last Updated 2019-03-14
Reserved
Looks promising
Does not boot!
Strange! I flashed couple of days back Androidmeda's "partitionsdcard"built from Jenkins, but failed to boot this ROM. I did a clean install in both cases!:crying:
sumansur2008 said:
Strange! I flashed couple of days back Androidmeda's "partitionsdcard"built from Jenkins, but failed to boot this ROM. I did a clean install in both cases!:crying:
Click to expand...
Click to collapse
Read the instructions carefully. You need to repartition you sd I said and use TWRP-OS2SD, not any other recovery.
Base ROM
On which ROM is this ROM based?
[ROM] [4.4.4] CyanogenMod 11.0 for LG Optimus One [OS2SD] [14/07/25]
Flashed the rom and it works perfectly well. ROM is smooth and fast as always.Thanks androidmeda.
Here is what I did:
1. Partitioned my 16GB Class 10 SD card as per instructions
2. Flashed the new recovery TWRP-OS2SD
3. Flashed the rom.
4. Rebooted and again flashed the Gapps-minimal(36MB!)
All fine. Playstore works, No FCs.
Partition info after Gapps:
/system 240MB / 394MB
/data 129MB / 1.68GB
/cache 1.15MB / 64.00MB
As mns123 posted, cm-11 (20140725) OS2SD has succesfully been installed on my obsolete device P500. It's amazing. Even using SDCard Class 6, it's running smooth like butter (or silk) and fast (and furious) :victory: Be patient, the initial reboot take a quite time, circa 7 minutes.
I think @HardLight fooled the recovery that /system and /data in SDCard pretended as /system and /data partitions in the internal memory, apparently. Very clever :good: The question is, where's 412 MB memory device, anyway?
Configuration:
SDcard: 2GB, Class 6
Processor:
Min CPU Freq: 320 MHz; Max: 600 MHz; Governor: SmartassV2
Memory management: Swap on
Dev Option: Window animation scale: 0.5X; Transition animation scale: 0.5X; Animator duration scale: 0.5X
Pros:
Space running out is no longer a problem. You can install apps as many as you want. The limit is just the SDCard capacity
Cons:
Out of known issues, none. Except I have to buy a new 16 GB SDCard Class 10. Duh! No, just kidding!
xu3sno said:
The question is, where's 412 MB memory device, anyway?
Click to expand...
Click to collapse
It is still there, probably with your last regular rom, just not mounted.
Sent from my LG-P500 using xda premium
Sarisfied till now
I have used this ROM for a day now, and this ROM has worked better for me than mukulson's CM11-v12 because, there was no insane battery drain in wifi standby.
14/07/27
Changelog:
Updated to last nightly
Increased read_ahead_kb to 2048 for better sd card read speeds
HardLight said:
Changelog:
Updated to last nightly
Increased read_ahead_kb to 2048 for better sd card read speeds
Click to expand...
Click to collapse
Firstly, thanks for the update. So it's based on 20140727 where ARMv6 enable and switch to ART runtime, isn't?
Suggestions:
1. Since OTA doesn't work, you may provide just the incremental.zip, whenever last nightly build is available. No need to download full size rom.
2. It will be helpful, if TWRP is capable "one fit for all" , one TWRP for all ROM!
Hey, you push me to buy a new Class 10 SDCard (16 GB maybe). Just kidding. The old one reserved for backup
I tried partitioning SD card using minitool partition, installed TWRP, ROM and GAPPs.
Try to do a dalvik/cache partition but I had failed, TWRP doesn't mount data partition.
I tried more time without success.
Minitool doesn't accept / before name in the labeling and then I try using data e system (instead /data and /system).
Tri to boot mobile, but It doesn't boot (I wait 20 minutes).
Any idea?
xu3sno said:
Firstly, thanks for the update. So it's based on 20140727 where ARMv6 enable and switch to ART runtime, isn't?
Suggestions:
1. Since OTA doesn't work, you may provide just the incremental.zip, whenever last nightly build is available. No need to download full size rom.
2. It will be helpful, if TWRP is capable "one fit for all" , one TWRP for all ROM! (
Click to expand...
Click to collapse
+1
casaprocida said:
I tried partitioning SD card using minitool partition, installed TWRP, ROM and GAPPs.
Try to do a dalvik/cache partition but I had failed, TWRP doesn't mount data partition.
I tried more time without success.
Minitool doesn't accept / before name in the labeling and then I try using data e system (instead /data and /system).
Tri to boot mobile, but It doesn't boot (I wait 20 minutes).
Any idea?
Click to expand...
Click to collapse
Have no experience with Windows Mini Tool. Re-partition SDCard by using Linux (assuming you have a Linux box).
Here what I did as I posted previously.
Execute Terminal as root:
# fdisk -l will show sdcard, /dev/sdx
# fdisk /dev/sdx, follow the instruction to make partition in primary (p): vfat, ext4, swap, ext4.
formatting partitions
# mkfs.vfat /dev/sdx1 (for vfat file system)
# mkfs.ext4 /dev/sdx2 (for ext4 fs)
# mkswap /dev/sdx3 (for swap)
# mkfs.ext4 /dev/sdx4
Since Android based on Linux, making partition using Linux command is more accurate than Windows, IMHO.
xu3sno said:
Firstly, thanks for the update. So it's based on 20140727 where ARMv6 enable and switch to ART runtime, isn't?
Suggestions:
1. Since OTA doesn't work, you may provide just the incremental.zip, whenever last nightly build is available. No need to download full size rom.
2. It will be helpful, if TWRP is capable "one fit for all" , one TWRP for all ROM!
Hey, you push me to buy a new Class 10 SDCard (16 GB maybe). Just kidding. The old one reserved for backup
Click to expand...
Click to collapse
Yes it's based on 20140727, but speculations about ART is wrong. Conn O'Griofa just switched to local androidarmv6 repo of art, not enabled it.
Also here is the commit message: I'm merging this now, but only because it's needed to test changes. I don't intend for ART to be included in builds.
About ota and incremental, I don't use them so probably all upcoming updates will be full zips.
You mean TWRP capable of flashing to internal and external? If yes, it would complicate some things but I will try
casaprocida said:
I tried partitioning SD card using minitool partition, installed TWRP, ROM and GAPPs.
Try to do a dalvik/cache partition but I had failed, TWRP doesn't mount data partition.
I tried more time without success.
Minitool doesn't accept / before name in the labeling and then I try using data e system (instead /data and /system).
Tri to boot mobile, but It doesn't boot (I wait 20 minutes).
Any idea?
Click to expand...
Click to collapse
Then partitioning you don't need to change partitions names, leave it blank. So after partitioning fat32 will have Removable Disk and other * names by default.
HardLight said:
Yes it's based on 20140727, but speculations about ART is wrong. Conn O'Griofa just switched to local androidarmv6 repo of art, not enabled it.
Also here is the commit message: I'm merging this now, but only because it's needed to test changes. I don't intend for ART to be included in builds.
About ota and incremental, I don't use them so probably all upcoming updates will be full zips.
You mean TWRP capable of flashing to internal and external? If yes, it would complicate some things but I will try
Click to expand...
Click to collapse
Thanks for the enlightenment. I did flash 20140727 in internal (have not yet a new 16 GB Class 10 SDCard) using @Notonlyeyes CWM 6.0.5.3 TLS compatible. Go to Settings > Developer option > Select run time to ART > Warning OK > reboot successfully, without error notifications. Don't know if the ART enable or not, feel no different with previous system set to traditional Dalvik :silly:
TWRP, yes just one TWRP capable to flash any ROM (internal or external as yours) and restore nandroid backup. No need to swap between different version of TWRP, or between TWRP and CWM. Apology for so demanding
Wish you luck!
@HardLight: Can you make a TWRP support TLS flash all ROMs?
Because my sccard have class 4, not best for performance.
And I want use Link2SD to install many apps.
How is to increase /system not use OS2SD?
New version
Uploaded latest nightly (20140729)
Made TWRP-MULTI version for flashing ROMs to internal and external memory.
Regular roms flashes normaly to /system and OS2SD roms to /sd-system. Also there is /data for internal and /sd-data for external memory.
Please note that /sd-ext and /sd-system are same partions.
For the people who don't want experimenting flashing to external and internal with same recovery: TWRP-OS2SD version will still work on new roms.
Uploaded new gapps package for new recovery (also compatible with TWRP-OS2SD)
@anhsmile
I've already made it.
Download
HardLight said:
Uploaded latest nightly (20140729)
Made TWRP-MULTI version for flashing ROMs to internal and external memory.
Regular roms flashes normaly to /system and OS2SD roms to /sd-system. Also there is /data for internal and /sd-data for external memory.
Please note that /sd-ext and /sd-system are same partions.
For the people who don't want experimenting flashing to external and internal with same recovery: TWRP-OS2SD version will still work on new roms.
Uploaded new gapps package for new recovery (also compatible with TWRP-OS2SD)
@anhsmile
I've already made it.
Download
Click to expand...
Click to collapse
You're the man :good: You save my day, bro!
Hey folks,
I have recently replaced my older Evervolv on the Touchpad with a current Milaq Nightly, and for some reason it doesn't mount the internal SDcard partition (worked fine with Evervolv).
When I 'mount -t vfat /dev/mapper/store-media /sdcard' manually, it works fine and I can see the files in there, so the file system apparently is intact, but Android doesn't seem to recognize it as usable SDcard storage (i.e. no "move to SD" option in the app manager etc). The mount doesn't persist across reboots either, and adding an entry to /fstab.tenderloin is equally pointless.
Any hints on what could it be that prevents my device from automounting this partition?
WooShell said:
Hey folks,
I have recently replaced my older Evervolv on the Touchpad with a current Milaq Nightly, and for some reason it doesn't mount the internal SDcard partition (worked fine with Evervolv).
When I 'mount -t vfat /dev/mapper/store-media /sdcard' manually, it works fine and I can see the files in there, so the file system apparently is intact, but Android doesn't seem to recognize it as usable SDcard storage (i.e. no "move to SD" option in the app manager etc). The mount doesn't persist across reboots either, and adding an entry to /fstab.tenderloin is equally pointless.
Any hints on what could it be that prevents my device from automounting this partition?
Click to expand...
Click to collapse
It's not simply a matter of flashing the newer datamedia builds over an older, probably non-DM build. It requires restructuring the internal storage of the TP. Explicit directions are here. Use the newer version of the tool.
shumash said:
It's not simply a matter of flashing the newer datamedia builds over an older, probably non-DM build. It requires restructuring the internal storage of the TP. Explicit directions are here. Use the newer version of the tool.
Click to expand...
Click to collapse
The Evervolv before already was a datamedia build, and I have adjusted the partition sizes accordingly.
It worked correctly after the EW->Milaq migration about two weeks ago, and broke when I flashed a new Nightly over it last weekend.
(I did the whole cleanup via CWM before flashing the new nightly, just to avoid that question.)