up to 2.8.0.0 with f2fs!
to install your first f2fs os2sd rom (internal MTD partitions won't format as f2fs)
make sure your card is already partitioned for os2sd.
go to wipe>advanced, select data, press repair or change filesystem, change filesystem. f2fs.
repeat for system.
do the same but ext4 to revert.
.
Mostly clean fork of OmniROM/android_bootable_recovery, with patches from TechV/android_bootable_recovery and my modifications.
Meant for OS2SD, so you can flash things not meant specifically for the Optimus V (like pa_gapps, or other things I once recommended but don't sit well with trying to walk people through getting working anymore, like CrossBreeder,) and have it flash correctly to the OS2SD /system and /data partitions which most recoveries won't do without some natty prodding through ADB. And sometimes not even then.
You'll need this for my kitkat ROM. With the recent androidarmv6 TLS-enabling and swapping /system and /data partitions in the kernel, this is now the ONLY recovery that will properly flash my ROMs.
partition 1 is still /sdcard.
partition 2 is system. I moved it arbitrarily several times because it seems I'm the only one actively developing for thunderc right now, and now it matches HardLight's p500 OS2SD setup.
partition 3 is swap.
partition 4 is now ext4 /data. It was, in the first iteration of OS2SD, ext4 /cache, but I moved that back to mtdblock1 for speed and space.
The OS2SD partitioner knows the new layout: /sdcard, /system, /swap, /data. In Internal mode it knows the internal layout, /sdcard, /sd-ext, swap.
Now a unified Internal/OS2SD recovery!
Things that are different from stock TWRP:
In the title bar it tells if in Internal or OS2SD mode.
Whichever mode it is in, it will flash generic zips like CrossBreeder or whatever, to the appropriate partitions.
Under Advanced is a button to switch modes, labelled with whichever mode it's NOT in. It gives an abort option and swiper to activate the switch.
v4 release fixes mode switch bug.
It will flash internal roms correctly whichever mode it is in. also OS2SD roms formatted like mine where it's mount EMMC /system in the updater script.
The main point to the multi is to be able to flash the generic zips without modifying them to either internal or os2sd as wished. And to be able to format internal or OS2SD partitions separately without changing their names.
And also, the partitioner is different in each mode to reflect the partitions used.
In OS2SD, it makes vfat, system, swap, data.
In Internal it makes vfat, sd-ext, swap.
I made it multi mode because I still support internal builds for thunderc even though I don't use em myself.
Has all the TWRP 2.7.1.0 goodies like 'Repair or Change File System' under Advanced Wipe, and text wraparound.
Download
NOTE: the screen will probably blank while partitioning and won't come back on until it finishes. you can either ignore it, or increase/disable the screen timeout under settings>screen.
IMPORTANT: When you flash the new recovery, reboot recovery to be sure it works, before flashing ROM.
Thanks to TechVendetta for his source or I'd not have messed with TWRP at all.
Not to mention the partitioning code.
Thanks to androidarmv6 for the android_device_lge_p500/msm7x27-common tweaks for TWRP which I shamelessly kanged with credit given, from thunderg to thunderc, like my 3.0 kernel and much of my device folder setup.
And thanks to @Dees_Troy et al for TWRP source code. Very very pretty, fun to modify, and I love the terminal and file manager.
If any original devs of TWRP happen to see this, my apologies for mangling the source to my own ends. It's a work in progress and I take full responsibility for any bugs or glitches. And thank you again for sharing.
reserved
reserved
this spot reserved for future informational post.
internal (stock TWRP) version uploaded.
os2sd v3 uploaded.
Strongly recommended upgrade if you're using os2sd. Removes internal system and data from fstabs to fix mounting conflicts. It'll still flash files that mount them by device (/dev/block/mtdblock5 or 6 for system and data)
new updated internal and tweaked os2sd versions.
advise upgrade.
bump
new version, multi-function internal/os2sd. only flashes TLS enabled builds from 08022014 onwards, unfortunately. Everything else for the Optimus V or S, has the internal /system and /data partitions reversed from this recovery version (and newer rom builds.)
It's a change that completely breaks backwards compatibility, which I dislike immensely, but the phone does run faster and have more system space without fighting for it.
so, since no-one else has built anything for these phones that I'm aware of for months now, I feel free to make any changes I see fit no matter how exorbitant or incompatible they may be.
Just wait till I switch the whole shebang over to f2fs instead of yaffs2, that's going to break any remaining reverse compatibility with other recoveries or roms that might still linger about. I'll have to build a stock kernel for f2fs and make an f2fs redo of Rhode rom so that people can still activate the phones without having to completely redo the recovery and reformat the mtd partitions and all.
bump.
mode switch freeze-up bug fixed.
uses older update-binary to flash this from other recoveries.
v4 released.
bugs?
I've noticed some issues with this version of TWRP, so I thought I'd come here and list what I can remember off the top of my head.
after flashing zips, the 'wipe cache/dalvik' button causes the recovery to hang
under the mount option, you select what partitions you want to mount, then press 'mount USB storage', and windows gives a sound I hadn't heard before-- it's like the tone for plugging something in usb, but it is only one tone repeated 3 times, I suppose so as to indicate a communication error of some kind. When you then press 'unmount', windows sounds the proper tones, and you then get access, but only to the SD card. Enabling or disabling MTP has no effect.
Hm. There were one or two little niggling things, but I seem to have forgotten them. I should write stuff down, huh?
Related
I try to partition my sd-card using ClockworkMod Recovery 5.8.0.0.
It went ok, and I can see my partition using adb shell
Code:
# mount
...
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,nodev,noatime,nodiratime,barrier=1,nodelalloc,data=ordered)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,nodev,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
I want to convert ext3 to ext4 so I plug my phone in the USB and mount it in the recovery.
However Gparted can't find any partition in my sdcard. When I try to view it using disk utilities It only shows the FAT32 partition.
I don't understand why gparted can't detect any partition ( it shows unallocated ). Something wrong with the partition table of the sd-card formatted by CWM ? Anyone have solved this before ?
Delete all partitions on your SD card and then partition again.
MatDrOiD said:
Delete all partitions on your SD card and then partition again.
Click to expand...
Click to collapse
How to delete them if I can't see them ? I try to re-partition using CWM but still the same.
Delete partitions with cwm, and then create 1 big fat 32 partition. Alternately use Linux fdisk, which will "see" it.
After one partition is created, use parted, or 4ext.
fdisk or parted both can't find any partition...
But anyway.. after installing MIUI which convert my partition to ext4 automatically the problem is gone, every partition can be seen... So it must be some problem with CWM partition script
It ought to detect the partitions if you use a micro sd card reader. I assume you connected it via the Desire, in recovery?
Droidzone said:
It ought to detect the partitions if you use a micro sd card reader. I assume you connected it via the Desire, in recovery?
Click to expand...
Click to collapse
Yes, maybe that's the problem. I connected it via the Desire in recovery.
What could be wrong ? Because now (after flashing MIUI_xj xpart), I can see all partitions though connected via the Desire.
UPDATE : I still can't see the sd-ext if I mount USB storage in the recover...
ikidntu said:
Yes, maybe that's the problem. I connected it via the Desire in recovery.
What could be wrong ? Because now (after flashing MIUI_xj xpart), I can see all partitions though connected via the Desire.
Click to expand...
Click to collapse
First, erase that crappy recovery from your phone. Then install 4ext. Should fix it.
Droidzone said:
First, erase that crappy recovery from your phone. Then install 4ext. Should fix it.
Click to expand...
Click to collapse
... exactly what I thought atm
when you mount ur desire with usb mass storage option under recovery, it mount ONLY the FAT partition...
put the microsd in a microsd adapter on ur laptop..u will see both...
@droidzone come on, don't call CWM crappy ..every recovery is based on that..koush did a great work in order to write it for about every device (a tons of device support it now)..i agree it's a basic recovery (and maybe there are some limitations)..but it's thanks to that base recovery that now devs can easily mod it and improve it...it's like you and ur rom..ur rom its probably the best htc sense based rom for the desire, but you will never be able to do that without the crappy htc rom, and htc was never be able to do that without the crappy aosp rom made by google..i hope you got what i mean lol...modify is easy than create something from new
@andQlimax, my bone of contention is not with Koush's CWMR. It is with that half baked product called "Clockwork mod touch for Desire" that was recently released here without proper testing (the OP was using this, and his problems are directly caused by the faulty recovery). The very least the "developer" should test is to do a full backup and restore on his own phone after compilation. He has no right to treat poor hapless newbies as guinepigs. I wonder if that person even owns a Desire. If he did and he missed the fact that the recovery he released does not have the capacity to make sd-ext backups, I really feel for him.
People trust developers who release Recovery. If they cant trust their recovery to make proper backup, what's the point of calling it a Recovery software?
I have the utmost respect for Koush, Paul O'Brien and others for their development work. I dont intend to mean any sort of disrespect for those masters and pioneers of Android development. I also respect them for keeping CWMR; and Cyanogen for keeping CM open source despite all circunstances.
anyway i think the touch recovery posted in the dev section come directly from the koush build, he released it and it's on its site http://www.clockworkmod.com/rommanager for some devices
koush usually ask some people to test the recovery for him before he release it, probably someone didn't noticed that bug
Thank you. I wasnt aware of that. But I see that the subversion has increased to 5.8.0.2 while yorzua has still attached the faulty 5.8.0.0.
I've been working on this port for personal use, but I figured others may find this useful.
What is it?
It's a script flashed through recovery, same as when you flash a ROM, that wipes for you in one simple step!
What does it do? (Wipe)
Depending on which version you choose, it calls on mke2fs and e2fsk to format /cache /data /system, then check the partition afterwards.
It will wipe /cache for the cache only, or system, cache and data for the full wipe. It does not do the external SD card, but it WILL FORMAT INTERNAL SD!
What does it do?(Nullify)
Same as the wipe, however this first calls on DD to zero out the partition, leaving NO DATA behind. Its a full overwrite of all data in the partition, with no way to salvage after running. The chances of anyone being able to recover any data after this is run is pretty slim outside of extreme power users and like..the CIA or something. Even then the data would be so corrupted I doubt anything usable could be rebuilt. Best used when bugs come up regardless of wiping multiple times, or prepping the tab for sale, no personal data can be retrieved from the internal SD.
How do I use it?
This is assuming you run a custom recovery!
System Wipe:
Reboot into recovery (this has been tested on my personal device with CWM and TWRP).
Make a full backup.
Install from SD, pick the system wipe zip.
Install the zip.
Wait a bit, it should take a minute for full wipe.
You can either restore a backup or flash a new ROM zip.
OPTIONAL: Fix permissions
Reboot system
NOTE even on a restore first boot will take longer then normal.
Cache Wipe:
Reboot into recovery.
Make a full backup, just in case.
Install from SD, pick Cache Wipe zip.
It'll take a second.
OPTIONAL: Fix permissions
Reboot system
NOTE boot will take a little longer then normal.
Nullifier:
Make sure you have at LEAST 50% battery or are plugged in.
Copy all information and files you want to save from Internal SD to PC or external SD card (the slot one).
Reboot into recovery.
Make a nandroid backup.
Install zip from SD, pick the nullifier zip you want to run.
Cache nullify takes about 9 minutes, full system takes about 35-40.
Check if you can mount /system /data and /cache, if you can, proceed, if not, reboot recovery (recovery not system!)
Install from zip, pick your ROM zip, or restore a nandroid.
Reboot system, and do whatever the DEV suggests.
NOTE Boot will take longer then usual.
What's this ported from?
This is based on work by Volk's Nullifier script for the G2x, and based directly on the Hellfire Nullifier. It's no longer really even close, but the concept and work is still based on their work.
What does each version do?
Cache Wipe: Formats /cache and deletes /data/dalvik-cache.
System Wipe: Formats /cache /system and /data. Recovery mounts INTERNAL SD to /data/media, so THIS DELETES INTERNAL SD!
Please backup your INTERNAL SD before running this or you will lose everything on it!
Cache Nullify: Nullifies /cache and deletes Dalvik-cache.
System Nullify: Nullifies /cache /data /system. THIS DELETES INTERNAL SD!
Cache Wipe\Nullify is meant for cleaning up when things get buggy.
System Wipe is meant to format everything for a new rom install or nandroid backup restore. The recovery will remove directories around /media, not format, this will format /data completely in preparation for new data.
System Nullify is meant to destroy all data in /system /cache /data, including your internal SD, by zeroing out the partitions. In other words, writes 0s from start to end.
Who should we thank?
Volk, who created the initial concept and script Nullifier, which this is based roughly on.
x0hell0x who ported it to the Hellfire Kindle Series, which this is based directly on.
da-pharoah, who helped me through the process and dealing with different device IDs in different recoveries. If it weren't for him I'd have given up and made seperate zips for each recovery.
What's coming up?
Right now I think this is complete! I'm unsure of how it handles CWM, so I may need to create CWM versions.
Things to note! READ THIS!
This is intended to run on the Acer Iconia Tab A100 ONLY! I have not set this up to run on any other device, and doing so may result in a brick! This wipes partitions, and could wipe boot, recovery, or any number of other partitions if run on a different device!
This was created and tested on my personal device using TWRP recovery! Using any other recovery may or may not prevent the script from running correctly! System wipe\nullify erases internal SD please backup data and ensure your ROMs and Nandroids are stored on EXTERNAL SD CARD!
The wipes are meant for every flash, the nullifiers are NOT meant for every flash! They are meant for changes from one ROM to another rom, or every few flashes, say 10. Otherwise use manual wipes or my wipe scripts!
Porting:
I'll consider porting to other devices if I have time, please PM me if interested.
I am not responsible for any damage that may occur from use of this script! If you choose to use this, that is your choice. As with anything else, flashing can cause problems including data loss, hair loss, bricking, brick laying, and magical fairies cracking your screen.
Changelog:
5.25.12 v0.1
Initial attempt at porting over, full of fail.
5.26.12 V1.0
Wipe Cache only version completed and successfully run on my device in CWM and TWRP.
5.27.12 V1.0a
Minor changes to the script for cache only version.
5.28.12 V1.1
More changes, changed handling of device ID from recovery to handle both types of recovery reporting (thanks da-pharoah)
Adjusted the status bar indicator to better reflect where in the operation the script is (thanks da-pharoah)
5.30.12 V1.1a
Created post, minor clean up of spelling errors.
5.30.12 V1.3
System Wipe finished after some major changes to command arguments. Cache wipe getting updated as well to 1.3 with a fix to rm argument.
6.1.12 V1.4
Cleaned up an error with the cache being formatted and throwing errors. Updated and cleaned up Cache Nullifier, all scripts updated to 1.4.
6.1.12 V1.5a
I made a mistake and updated the wrong script versions, resulting in nothing being formatted due to the system not unmounting before carrying on with the script. My apologies, I hadn't noticed the issue until I attempted to use it today for a rom install. For now, use only 1.5a versions, updating them all now with the fix. Slight changes to output to help see what it's saying. Working on getting the status bar timing correct.
6.3.12 V1.5a Final
Rechecked each script, and should ALL now be FULLY working in TWRP. CWM may or may not handle the script correctly, if you run into issues like it not working, send me a PM or Email with /cache/recovery/last_log and if there dmesg. System Nullifier added finally!
Please bear with me, I'm finishing my High School course and only have limited time on any given day, and it mostly goes to schoolwork, I will update when I can, and I really hope to have the full wipe completed within a few days. Nullifier may take longer as I'm not sure why DD hangs.
Downloads: These are on my drop box for now, it's small so it shouldn't cause issues.
Blackhole System Wipe 1.5a A100
Blackhole Cache Wipe 1.5a A100
Blackhole Cache Nullifier 1.5a A100
Blackhole System Nullifier 1.5a A100
does this actually "wipe" data so that is can not be recovered? or just erase it?
joeyjojojjjjjj said:
does this actually "wipe" data so that is can not be recovered? or just erase it?
Click to expand...
Click to collapse
Right now all it does is format, or wipe, with mke2fs to whatever FS that partition uses, EXT4 or EXT3. Its not much different from using CWM wipe/format commands, just does it all for you. Once I figure out why DD hangs, it will then Nullify the partitions, complete and utter destruction of data by overwriting the partitions with 0s, leaving no traces behind at all. I'm currently hammering out the full system wipe script, which will do /cache /system /data and /data/dalvik-cache, the /cache/dalvik is done when /cache is formatted. The problem I ran into is for some strange reason, internal SD is mounted to /data/media in recovery, meaning formatting /data directly will erase the internal SD card as well. The recovery gets around this by deleting directories around it, but never formats it, which IMO can lead to issues and bugs down the line. I have only 1 method of dealing with this, and that's moving /data/media to the external SD card (SDC), formatting (or nullifying) then moving it back. As this can mean moving up to 8 GB, its not a liable method as it will take a LONG time to move it there and back.
I'm hoping to have the first full system wipe available tonight, however it WILL erase the internal SD, this is only to be used if you don't care what's there, or are having alot of bugs, and copy your stuff off before running. I can't test it since the wife is using the tab now, and I'm not gonna put it online without testing it first.
TL;DNR: It just erases it.
Updates
1.4 versions are up.
Now includes Cache only Nullifier! This is the wiping that I think joeyjojojjjjjj was looking for. Unrecoverable data destruction. Currently DDs /cache, then formats and checks, then deletes dalvik-cache. Overwrites the partition with 0s from beginning to end, leaving nothing but ZERO behind, hence blackhole nullifier.
Hoping to finish up System Nullifier tonight some time.
1.5a Final is done
Scripts are now up to 1.5a Final. The zips are still labeled as 1.5a but they are all updated. Added system nullifier! Please use caution with the wipes and nullifiers, and ensure internal SD is backed up and your nandroids and roms are stored on external SD card before using!
Tested working on TWRP Recovery, YMMV on CWM recoveries.
pio_masaki said:
Scripts are now up to 1.5a Final. The zips are still labeled as 1.5a but they are all updated. Added system nullifier! Please use caution with the wipes and nullifiers, and ensure internal SD is backed up and your nandroids and roms are stored on external SD card before using!
Tested working on TWRP Recovery, YMMV on CWM recoveries.
Click to expand...
Click to collapse
So I finally came upon this thread! Well done bro! Great work and keep it up! makes me wish I had an a100 just to test it
da-pharoah said:
So I finally came upon this thread! Well done bro! Great work and keep it up! makes me wish I had an a100 just to test it
Click to expand...
Click to collapse
It works lol it's based on your work after all
pio_masaki said:
It works lol it's based on your work after all
Click to expand...
Click to collapse
Lol I know but still u got it rockin for the a100 so that's what I meant..
Sent from my LG-P999 using xda premium
Wipes with Crossix Memory Swap?
I am using the Crossix memory swap.
If I use the system wipe script, will it erase the data on my *actual* internal sd (i.e the 5gb partition that I largely don't use). Or will it erase the data on my *tricked* internal (my 32gb microsd card)?
Thanks, I can't wait to try this stuff out!
conorkickass said:
I am using the Crossix memory swap.
If I use the system wipe script, will it erase the data on my *actual* internal sd (i.e the 5gb partition that I largely don't use). Or will it erase the data on my *tricked* internal (my 32gb microsd card)?
Thanks, I can't wait to try this stuff out!
Click to expand...
Click to collapse
Internal SD only. It will never touch your external SD card. And the reason is....
The crossix mount swap is only active when android runs from /system. This is run from recovery, so any system mods don't affect anything running in recovery.
So you're safe, only the included internal SD is wiped, regardless of crossix's mount swap.
Tapatalked from my Galaxy S II.
This is sick. Nice work.
Sent from my SGH-I777 using xda premium
could you make a port of the babsector utility ? A lot of bricks can come back to live with i believe
http://forum.xda-developers.com/showthread.php?t=1624645
Presko said:
could you make a port of the babsector utility ? A lot of bricks can come back to live with i believe
http://forum.xda-developers.com/showthread.php?t=1624645
Click to expand...
Click to collapse
This has nothing to do with these tools lol.
Anyways I can port it but its useless without the sbk, so not really a point until Acer releases it.
Sent from my Nexus 7 using Tapatalk 2
Excuse me but after a couple of days reading about this problem , what is sbk ?
What ever it is , I doubt that they are going to release even a windows 8 driver for this tablet
Btw I have contacted the Russian author via 4pda and he says to give a straight shot and to send him a screen shot
Tomorrow at work will have time to try
Is there something specific to put in the start command at prima vista ?
Presko said:
Excuse me but after a couple of days reading about this problem , what is sbk ?
What ever it is , I doubt that they are going to release even a windows 8 driver for this tablet
Click to expand...
Click to collapse
Its the encryption key for the boot loader, specifically to use nvflash in apx mode. Its covered in the brick thread.
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Its the encryption key for the boot loader, specifically to use nvflash in apx mode. Its covered in the brick thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
well that's a chance to ps my post while you aswer it
btw is there a petition or something that I can contribute with ?
Presko said:
well that's a chance to ps my post while you aswer it
Click to expand...
Click to collapse
Huh?
Sent from my Galaxy Nexus using Tapatalk 2
pio_masaki said:
Huh?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
not again I will stop editing previous posts
Presko said:
not again I will stop editing previous posts
Click to expand...
Click to collapse
Oh OK I didn't see the edits.
Anything using nvflash or apx mode needs the sbk, no way around it. It may yet be cracked like the a500s, but so far no.
Sent from my Galaxy Nexus using Tapatalk 2
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Felivel said:
I have a problem with my phone.
I believe that the internal partitions are messed up.
I have tried a couple of guides to fix this but no luck. I get "error formatting /data!" on recovery. I also tried using the formatting tools from adb shell (e2fsck, gparted).
The main problem is that when i restart my phone the /data partition gets wiped, and the phone reboots in blank, no apps no setting (some of them remain).
I wonder if i can solve this by setting my sd-card to be the new /data. I doesn't matter if i have to leave the sd-card on all the time. i mainly use this phone for developing apps.
Thanks.:good:
Click to expand...
Click to collapse
It could probably be done if you could get the sdcard to mount at boot, not sure if thats possible. You would need to create a flashable much like the ext4 mod, that edits the init.inc.rc file to mount the sdcard and /data to it. You would want to partition your sdcard with an ext3 or ext4 partition and use that for data.
Yes it can be done. That's how boot manager works, by modifying the ramdisk to load images from sdcard or emmc instead of the partition. I think I have an idea on how to make your request work.
Edit: If you feel like trying a project, what needs to be done is create a file data.img and mount it as loopback using busybox (ROM needs a working busybox).
Then the boot.img needs to be updated replacing the mount /data entry in init.inc.rc with the location of the loopback device and a loopback setup prior to this. The data.img created needs to be formatted ext3 or ext4. I know it's not too detailed but rather just a summary.
I've just recently seen in some other threads information about this Ext4 update but after searching haven't really been able to get a handle on what exactly it does and the proper process for doing it. I would love to be rid of the Low Memory messages and may even decide to root my wives as well if it will fix it for her as well. Does anyone have a link to a step by step that covers what needs to be done? I am currently running the Albinoman's Jelly Bean ROM and loving it but would really like to kick this low memory message for good.
Thanks for any insight
devo4040 said:
I've just recently seen in some other threads information about this Ext4 update but after searching haven't really been able to get a handle on what exactly it does and the proper process for doing it. I would love to be rid of the Low Memory messages and may even decide to root my wives as well if it will fix it for her as well. Does anyone have a link to a step by step that covers what needs to be done? I am currently running the Albinoman's Jelly Bean ROM and loving it but would really like to kick this low memory message for good.
Thanks for any insight
Click to expand...
Click to collapse
Im not sure if the ext4 mod will work on JB, im pretty sure its only for GB. If you go to a GB rom, its as easy as flashing the mod thru recovery.
How it works is it flashes the gingertiny kernel with a modified ramdisk. Normally the phone has a larger /data partition, and a /datadata (/data/data) partition that is way undersized. The mod takes the undersized /datadata partition and instead mounts it to the larger /data partition, esentialy giving you /data/data just as you had before. So it makes /datadata a folder on the larger /data partition, instead of being on its own smaller seperate partition.
Hope that wasnt to confusing.
There's also an ext4 mod with no kernel, got it from invisiblek's stash. I've been using it on his nightly ICS builds and it seems to work very well.
Try Link2sd and see if that helps. I use both and have never seen a warning about low space.
...sorry...I was on the phone...
omniatic said:
There's also an ext4 mod with no kernel, got it from invisiblek's stash. I've been using it on his nightly ICS builds and it seems to work very well.
Try Link2sd and see if that helps. I use both and have never seen a warning about low space.
...sorry...I was on the phone...
Click to expand...
Click to collapse
The common misconception of my mod it seems is that it flashes the kernel all the time. No. It only does that if there is a specific HTC framework file in system and that's the only difference between mine and invisibleks. Mine should work fine on ICS as it basically does a find and replace to modify the ramdisk and leave the same kernel. If you look at the script in the mod you'll see that.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
The common misconception of my mod it seems is that it flashes the kernel all the time. No. It only does that if there is a specific HTC framework file in system and that's the only difference between mine and invisibleks. Mine should work fine on ICS as it basically does a find and replace to modify the ramdisk and leave the same kernel. If you look at the script in the mod you'll see that.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So from what i'm gathering I should be ok on the Jelly Bean ROM even as it isn't going to affect the Kernel but just modify the ramdisk? I have seen a few links around is there a link to the developers site that has the most recent version to flash? Thanks for the input.
devo4040 said:
So from what i'm gathering I should be ok on the Jelly Bean ROM even as it isn't going to affect the Kernel but just modify the ramdisk? I have seen a few links around is there a link to the developers site that has the most recent version to flash? Thanks for the input.
Click to expand...
Click to collapse
I was under the impressin it always flashed the kernel, but i guess i was wrong. So it should work.
I cant find the ext4 thread right now, but you can get the files from here. http://dinc.does-it.net/EXT4_Mods/
cmlusco said:
I was under the impressin it always flashed the kernel, but i guess i was wrong. So it should work.
I cant find the ext4 thread right now, but you can get the files from here. http://dinc.does-it.net/EXT4_Mods/
Click to expand...
Click to collapse
Thanks for the link, do I just need the Convert2Ext4_normal_data.v1.0.zip or do I need one of the dalvik .zip files as well?
devo4040 said:
Thanks for the link, do I just need the Convert2Ext4_normal_data.v1.0.zip or do I need one of the dalvik .zip files as well?
Click to expand...
Click to collapse
There are 3 different mods.
1. Ext4 normal data - Converts data and cache to ext4. Does nothing for low space problem.
2. Ext4 no data limit normal dalvik - Converts data and cache to ext4. Moves /datadata to /data, fixing low space issue.
3. Ext4 no data limit dalvik moved - Converts data and cache to ext4. Moves /datadata to /data. Moves dalvik cache from /data to the former /datadata partition.
#2 is the most popular and will solve the low space issue. You can use #3, however some people have issues moving the dalvik. You can always try dalvik moved if you want. If it causes issues flash the dalvik moved revert, and you will be left with no data limit normal dalvik.
tiny4579 said:
The common misconception of my mod it seems is that it flashes the kernel all the time. No. It only does that if there is a specific HTC framework file in system and that's the only difference between mine and invisibleks.
Click to expand...
Click to collapse
But doesn't it always flash the kernel that's bundled with the mod? And won't flashing a new kernel afterward undo the mod?
(Given, all this only matters on Sense ROMs...)
Edit: Never mind. The mod only needs to modify boot.img, while a kernel uses the boot.img file that's already there. Derp.
ardax said:
But doesn't it always flash the kernel that's bundled with the mod? And won't flashing a new kernel afterward undo the mod?
(Given, all this only matters on Sense ROMs...)
Edit: Never mind. The mod only needs to modify boot.img, while a kernel uses the boot.img file that's already there. Derp.
Click to expand...
Click to collapse
Just FYI, We (jermaine151 and I) wouldn't have had a kernel in the mod for sense if it weren't for the fact that HTC's kernel doesn't support ext4 and CM's and other AOSP kernels already supported ext4.
You're correct, the mod takes the boot.img, unpacks it, makes the change, repacks it, and flashes the boot.img. If it's sense, instead of repacking with the same kernel it repacks with the bundled kernel. On AOSP it repacks with the existing kernel.
So I finally had a free night and attempted to flash Convert2Ext4_no_data_limit_normal_dalvik.zip last night. It appeared to go just fine for me but I am still getting the low space message this morning if I add any apps. I went in with Link2SD and it still shows my /system as only having 4% free while everything else has around 50% free. I've tried moving everything to the SD card that it will let me but still no luck.
devo4040 said:
So I finally had a free night and attempted to flash Convert2Ext4_no_data_limit_normal_dalvik.zip last night. It appeared to go just fine for me but I am still getting the low space message this morning if I add any apps. I went in with Link2SD and it still shows my /system as only having 4% free while everything else has around 50% free. I've tried moving everything to the SD card that it will let me but still no luck.
Click to expand...
Click to collapse
Go to menu - settings - sd & phone storrage - and look for application data storrage category. Total space should say 748mb if the mod worked. Or use a termimal app with su permission to type " mounts ". Look for /cache and /data, they should say ext4 after both.
Which EXT4 mod should I use with Pons CM10? Are there any performance improvements?
spectre559 said:
Which EXT4 mod should I use with Pons CM10? Are there any performance improvements?
Click to expand...
Click to collapse
Which mod you use is really up to you. No data limit normal dalvik is the most used. Heres a breakdown:
Convert2Ext4_no_data_limit_normal_dalvik.v2.0.zip - Converts cache and data to ext4 from ext3 (ext4 is faster than ext3), moves datadata partition to a folder on the data partition (fixes low space issues), leaves dalvik-cache in its original position on the data partition.
Convert2Ext4_no_data_limit_dalvik_moved.v2.0.zip - Converts cache and data to ext4 from ext3 (ext4 is faster than ext3), moves datadata partition to a folder on the data partition (fixes low space issues), moves dalvik-cache from the data partition to the former datadata partition (frees up more space for data, but has been said to slow the phone down/cause issues).
Convert2Ext4_no_data_limit_dalvik_moved_revert.v2.0.zip - Converts cache and data to ext4 from ext3 (ext4 is faster than ext3), moves datadata partition to a folder on the data partition (fixes low space issues), moves dalvik-cache from the datadata partition back to its original position on the data partition after using the dalvik moved mod.
Convert2Ext4_normal_data.v2.0.zip - Converts cache and data to ext4 from ext3 (ext4 is faster than ext3), leaves datadata on its original (undersized) partition (does not fix low space issues), leaves dalvik-cache in its original location on the data partition.
No_Data_Limit_Mod.v2.0.zip - Leaves data and cache as ext3 (no conversion to the faster ext4), moves the datadata partition to a folder on the data partition (fixes low space issues), leaves dalvik-cache in its original position on the data partition.
http://dinc.does-it.net/EXT4_Mods/
All right I went for the no data limit / normal dalvik option. Flashed with TWRP 2.3.x. Everything seems to have worked but is there any way I can verify that the mod took? Sorry for the noob question.
* EDIT * Never mind. The answer is a couple posts up!
spectre559 said:
All right I went for the no data limit / normal dalvik option. Flashed with TWRP 2.3.x. Everything seems to have worked but is there any way I can verify that the mod took? Sorry for the noob question.
* EDIT * Never mind. The answer is a couple posts up!
Click to expand...
Click to collapse
Go to menu - settings - sd & phone storrage - and look for application data storrage category. Total space should say 748mb if the mod worked. Or use a termimal app with su permission to type " mounts ". Look for /cache and /data, they should say ext4 after both.
Lol i copied and posted from above.
cmlusco said:
Go to menu - settings - sd & phone storrage - and look for application data storrage category. Total space should say 748mb if the mod worked. Or use a termimal app with su permission to type " mounts ". Look for /cache and /data, they should say ext4 after both.
Lol i copied and posted from above.
Click to expand...
Click to collapse
The first part is not a good way of telling (by checking storage). It will show 748mb regardless. Not mounting /data/data will not have an impact on the size of /data which is 748mb. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
tiny4579 said:
The first part is not a good way of telling (by checking storage). It will show 748mb regardless. Not mounting /data/data will not have an impact on the size of /data which is 748mb. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
Click to expand...
Click to collapse
Actually on the latest ota anyways, the sd & storage menu shows both Phone Memory (/data) as 748mb, and Application Data Storage (/data/data) as 748mb with the mod, and 147mb without. But your still correct, your way is a better way to see if its working. I just cant ever seem to remember that command.
cmlusco said:
Actually on the latest ota anyways, the sd & storage menu shows both Phone Memory (/data) as 748mb, and Application Data Storage (/data/data) as 748mb with the mod, and 147mb without. But your still correct, your way is a better way to see if its working. I just cant ever seem to remember that command.
Click to expand...
Click to collapse
I added the commands to check to the OP of the mod thread under FAQs.
Oh, the ota does show it? Wow, it's been a while since I've really used sense.
yo, this really speeded my INC up right away! thanks!
I know I'm late to the party and this was probably already discussed, but I couldn't find it with search. Has anyone considered converting the inc to a data media device (http://www.xda-developers.com/android/what-is-a-data-media-device/)? I've seen this done with other devices (e.g. hp touchpad). I'd be nice to be able to use the EMMC partition for storage and data. I know there is ext4all but I still seem to run out of space quickly since dalvik-cache is half of /data.
Not sure if hboot will let you combine partitions to do what you want; however, lvm can probably accomplish what you're hoping to achieve but it takes quite a bit of effort to setup.
Sent from my One using Tapatalk
I wasn't necessarily thinking we need to combine any partitions. Just don't mount the existing /data and /data/data partitions, and mount the EMMC partition as /data with an emulated sdcard at /data/media. I think this is how the Samsung phones work; you have both "internal" and "external" sdcards. Seems like it should just be some config changes and maybe a recovery that is datamedia aware so you don't erase the emulated sdcard when wiping data.
Smells like a project. I'll see if I will get around to this but this sounds doable.
No promises but my Inc could get bricked and I wouldn't cry over it so I can take a few risks.
Sent from my One using Tapatalk
I've only done a little research so far, but it seems like you'd only need to change a few configuration files. I don't think you could truly brick your Inc, could you? I'm tempted to try and get it working myself but I can't risk bricking my dd.
Sent from my ADR6300 using Tapatalk
ive got 2 incs so I dont mind messing with it, I have a touchpad tho and from what I know (I am decent friends with invisiblek and he does work on the touchpad) the only real difference, is re-partitioning your internal and setting the device tree to mount data as data/media instead of for say /data or /data/data
I have a TouchPad too. Finally made the leap to kk and datamedia there which is what got me thinking about the Inc. The repartioning done for the TouchPad was too make the data partition larger since it now holds both apps and sdcard data. We shouldn't have to do that for the Inc since we already have a partition with 6.6 gig available. Nothing is mounted at /data/media, it's just another directory on the main /data partition. That's why you need a special recovery that "wipes" data instead of formatting...
I've been looking at the changes milaq made. I assume invisiblek did something similar if not the same.
Sent from my ADR6300 using Tapatalk
natediggity said:
I have a TouchPad too. Finally made the leap to kk and datamedia there which is what got me thinking about the Inc. The repartioning done for the TouchPad was too make the data partition larger since it now holds both apps and sdcard data. We shouldn't have to do that for the Inc since we already have a partition with 6.6 gig available. Nothing is mounted at /data/media, it's just another directory on the main /data partition. That's why you need a special recovery that "wipes" data instead of formatting...
I've been looking at the changes milaq made. I assume invisiblek did something similar if not the same.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Ok, the last part is recovery and the current recovery images appear to be large enough to make the recovery build part fail. I'm not sure the actual recovery partition size on the inc but the images come to be about 4.5 MB and fail.
zachf714 said:
ive got 2 incs so I dont mind messing with it, I have a touchpad tho and from what I know (I am decent friends with invisiblek and he does work on the touchpad) the only real difference, is re-partitioning your internal and setting the device tree to mount data as data/media instead of for say /data or /data/data
Click to expand...
Click to collapse
/data/media uses fuse on an existing ext4 partition so the recovery as nate said has to be told to wipe /data instead of format (in other words, using an rm command and excluding /data/media).
This makes filesystem corruption harder to fix since the partition can't be wiped from recovery normally unless it's a format which TWRP does have an option to format /data.
tiny4579 said:
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Ok, the last part is recovery and the current recovery images appear to be large enough to make the recovery build part fail. I'm not sure the actual recovery partition size on the inc but the images come to be about 4.5 MB and fail.
Click to expand...
Click to collapse
Check my device tree, I have a commit on omni that compresses recovery a bit more and I use it to build
Sent from my SCH-I535 using Tapatalk
tiny4579 said:
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
Click to expand...
Click to collapse
I don't need a flashable script unless it's required. Personally, I'm fine just building a new system image and flashing that.
tiny4579 said:
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Click to expand...
Click to collapse
datamedia can be used in conjunction with sdcards. This is what the new samsung phones do. I thought the HTC One did as well, but I just remembered it doesn't have a sdcard slot. If you haven't already, check out this page: https://source.android.com/devices/tech/storage/config-example.html. Our config would be similar to the Xoom's.