I have stock hboot and currently running VJ's CM10.1 JB 4.2.2.
Despite the installation of the A2SD script, the free space of the device is really low. I thought of flashing a hboot that enables more space (Data++).
The problem is that the Data++ has a system partition size of 140MB and now, with the 250MB, there are 4MB left.
So, can I flash the Data++ hboot?
If so, what will this process require me to do?
Thank you for your time!
pspuser007 said:
I have stock hboot and currently running VJ's CM10.1 JB 4.2.2.
Despite the installation of the A2SD script, the free space of the device is really low. I thought of flashing a hboot that enables more space (Data++).
The problem is that the Data++ has a system partition size of 140MB and now, with the 250MB, there are 4MB left.
So, can I flash the Data++ hboot?
If so, what will this process require me to do?
Thank you for your time!
Click to expand...
Click to collapse
You can't. Your system is too big. You'll have to stick to the stock hboot, and use a different a2sd script, that also moves dalvik cache to sd-ext.
Can I find why has the system partition increased so much in size?
Most importantly, how can I flash another script?
Do I have to uninstall the current a2sd script firstly and then install the other via fastboot?
Do you recommend any a2sd scripts? Is this a good one?
pspuser007 said:
Can I find why has the system partition increased so much in size?
Most importantly, how can I flash another script?
Do I have to uninstall the current a2sd script firstly and then install the other via fastboot?
Do you recommend any a2sd scripts? Is this a good one?
Click to expand...
Click to collapse
Do a nandroid backup before proceeding!!
With a root explorer, go to system/etc/init.d and delete 10apps2sd. Then boot in recovery and install this:
https://www.dropbox.com/s/ngseioig6t2m3ns/apps_dalvik2ext-UNSIGNED.zip
It should also move dalvik cache to sd-ext.
Hey,
I assume you followed VJ's guide, and installed the a2sd xdata with the following settings Y | N | Y (=reboot).?
There is another thing you could try, and that is to run the xdata command in Terminal Emulator, which basicly mounts the entire /data partition to /sd-ext ! That however MAY cause some performance loss, especially if you have a lower that class 6 SD card.. However, I did it on my Desire, also running VJ's JB rom, and I can't notice any performance loss (=i have a 16 GB class 10 SanDisk SD card..)
As always, please do a nand back-up before trying anything.. If you choose to try this, just open Terminal Emulator, type "su" to get superuser permission, and then "a2sd xdata".. you might have to answer Y a couple of times, then the phone will reboot, take 5-10 mins to boot up (depending on how many apps you already installed. ), and violá: you should have your entire sd-ext partition as storage space..
Good luck!
- H
EDIT: ooops, almost forgot: if you want a simple overview and explanation of the a2sd xdata commands, look here: http://forum.xda-developers.com/showpost.php?p=21222591
- H
pspuser007 said:
I have stock hboot and currently running VJ's CM10.1 JB 4.2.2.
Despite the installation of the A2SD script, the free space of the device is really low. I thought of flashing a hboot that enables more space (Data++).
The problem is that the Data++ has a system partition size of 140MB and now, with the 250MB, there are 4MB left.
So, can I flash the Data++ hboot?
If so, what will this process require me to do?
Thank you for your time!
Click to expand...
Click to collapse
@abaaaabbbb63:
Which one of the scripts mentioned here is this?
I've checked the bash script you've posted and the one in my /system/etc/init.d/ dir, and saw that the one I have, has a lot more code than that you've posted. Wouldn't there be a problem with this?
Also, is this going to remove anything from sd-ext and just mount dalvik cache to it, or it will add dalvik cache to sd-ext?
@hhaznadar85:
To start with, thank you for the detailed answer
Yes, this is the way I've installed it! I also, have a 16GB class 10 microSD card so I am thinking about trying this.
As you've said, xdata command mounts the whole data partition. Isn't there a command that moves dalvik cache to sd-ext so as to try this first?
pspuser007 said:
@abaaaabbbb63:
Which one of the scripts mentioned here is this?
I've checked the bash script you've posted and the one in my /system/etc/init.d/ dir, and saw that the one I have, has a lot more code than that you've posted. Wouldn't there be a problem with this?
Also, is this going to remove anything from sd-ext and just mount dalvik cache to it, or it will add dalvik cache to sd-ext?
@hhaznadar85:
To start with, thank you for the detailed answer
Yes, this is the way I've installed it! I also, have a 16GB class 10 microSD card so I am thinking about trying this.
As you've said, xdata command mounts the whole data partition. Isn't there a command that moves dalvik cache to sd-ext so as to try this first?
Click to expand...
Click to collapse
It's a script i have been personally using on my desire with every ROM for the past year. It's simple, and moves data/app and dalvik cache to sd-ext.
You just flash it from recovery. Everything else will be moved my itself. Nothing will be deleted.
Ok then, I'll give it a go..
So to install the steps are:
1. nandroid backup before flashing the script
2. delete the file via root explore and flash the zip via recovery
Just in case, I need to restore the previous state, what should I do to minimize the loss of data (any data) ?
pspuser007 said:
Ok then, I'll give it a go..
So to install the steps are:
1. nandroid backup before flashing the script
2. delete the file via root explore and flash the zip via recovery
Just in case, I need to restore the previous state, what should I do to minimize the loss of data (any data) ?
Click to expand...
Click to collapse
You just restore the backup. Everything should be back in place.
whoa, sorry to ask this here, but @abaaaabbbb63, you seem like someone who knows this s**t..: VJ's JB ROM comes with some modified version of the original DT A2sd script.. Is there any way to remove it, and install the "old" a2sd script..
List of things I've tried:
a.) right after flashing ROM, go into terminal, type su --> a2sd remove --> reboot.. once rebooted, get root explorer, nav to /system/etc/init.d and remove 10apps2sd file = didn't work
b.) right after flashing ROM, go into terminal, type su --> a2sd remove --> reboot.. once rebooted, get root explorer, nav to /system/etc/init.d and remove 10apps2sd + 05mountext + 06handleswap files = didn't work
c.) right after flashing ROM get root explorer, nav to /system/etc/init.d and remove 10apps2sd file = didn't work
d.) right after flashing ROM, get root explorer, nav to /system/etc/init.d and remove 10apps2sd + 05mountext + 06handleswap files = didn't work
e.) Right after flashing ROM, get root explorer, nav to /system/etc/init.d and remove 10apps2sd. THen to /system/bin and remove the a2sd file = didn't work..!
I'm pretty much starting to give up... but I would sooooooo love to have the original DT a2sd script with this ROM.. any way of achieving that..?
Thanks in advance,
- H
EDIT: Oh, yea.. and of course when I write "didn't work" I mean that I subsequently rebooted into recovery, flashed the DT a2sd script, and then stuck on boot.. Every time...
---------- Post added at 07:58 PM ---------- Previous post was at 07:50 PM ----------
pspuser007 said:
As you've said, xdata command mounts the whole data partition. Isn't there a command that moves dalvik cache to sd-ext so as to try this first?
Click to expand...
Click to collapse
I dont think so.. I tried "dc2sd", "dalvik2sd" "cachesd", etc.. nothing worked..
I'm kinda annoyed by this modified script, so I also think I'm gonna try abaaaabbbb63's idea.. please share here if it works out for you.
- H
hhaznadar85 said:
whoa, sorry to ask this here, but @abaaaabbbb63, you seem like someone who knows this s**t..: VJ's JB ROM comes with some modified version of the original DT A2sd script.. Is there any way to remove it, and install the "old" a2sd script..
List of things I've tried:
a.) right after flashing ROM, go into terminal, type su --> a2sd remove --> reboot.. once rebooted, get root explorer, nav to /system/etc/init.d and remove 10apps2sd file = didn't work
b.) right after flashing ROM, go into terminal, type su --> a2sd remove --> reboot.. once rebooted, get root explorer, nav to /system/etc/init.d and remove 10apps2sd + 05mountext + 06handleswap files = didn't work
c.) right after flashing ROM get root explorer, nav to /system/etc/init.d and remove 10apps2sd file = didn't work
d.) right after flashing ROM, get root explorer, nav to /system/etc/init.d and remove 10apps2sd + 05mountext + 06handleswap files = didn't work
e.) Right after flashing ROM, get root explorer, nav to /system/etc/init.d and remove 10apps2sd. THen to /system/bin and remove the a2sd file = didn't work..!
I'm pretty much starting to give up... but I would sooooooo love to have the original DT a2sd script with this ROM.. any way of achieving that..?
Thanks in advance,
- H
EDIT: Oh, yea.. and of course when I write "didn't work" I mean that I subsequently rebooted into recovery, flashed the DT a2sd script, and then stuck on boot.. Every time...
---------- Post added at 07:58 PM ---------- Previous post was at 07:50 PM ----------
I dont think so.. I tried "dc2sd", "dalvik2sd" "cachesd", etc.. nothing worked..
I'm kinda annoyed by this modified script, so I also think I'm gonna try abaaaabbbb63's idea.. please share here if it works out for you.
- H
Click to expand...
Click to collapse
Try removing the 10apps2sd from the ROM zip itself, and replacing it with the "old" a2sd script. Then install the modified ROM zip from recovery.
I got to that result also. Finally i went back CM7.2..
HTC Desire
SanDisk Extreme 32GB Class 10
CM7r2 hboot
4EXT Recovery Touch
2GB 4ext partition --> Mounts2SD
ClockworkMod 7.2.0.1
- modified with 7zip
- uot kitchen kitchen
V6 SuperCharger Script
GO Launcher EX @ 160 dpi
I just tried flashing the zip, it succeeded had a successful boot, as well.
Sharing the experience:
1. deleted the script from /system/etc/init.d dir
2. booted to recovery:
got a slower boot (actually saw for the 1st time the "preparing to boot: x" message (where x, probably the percentage of completion)
got an error about mounting the system partition, telling me to wipe it..I simply rebooted to recovery and all went fine.
3. flashed the zip
4. rebooted and the rom loaded normaly with a delay of less than a minute
Now, I checked the Settings > Storage and saw the same amount of free space.
Booted into recovery and there's the info of the fs <mount point, free space>
system, 8.2MB
data, 27.8MB
cache, 38.8MB
How can I verify that the move of dalvik cache occurred?
Use an app like DiskUsage, browse all your partitions and see where the dalvik cache folder is located.
You can do this for any a2sd script on any rom, try to understand exactly what is stored where. All a2sd scripts are supposed to effectively achieve the same thing..
Eddie, thank you for the reply! I've used the DiskUsage app, and verified that dalvik cache is located at the sd-ext partition.
I've also seen that the sd-ext partition has 400MB free of a total of 1007MB.
Although, I tried installing Themer (15MB) and got the insufficient storage error.
Low memory warning comes from your /data partition, not your sd-ext
Check what is filling up /data
Make sure you have very little free space on /system as well as any free system space is wasted space. If this is the case your rom may fit into a smaller hboot
Hey! I did this with Chromium Rom. Maybe it will help..
1. Install data++ hboot from alpharev's website. 2. Flash Chromium rom build 11 slim.
3. Flash gaps.
4. Wipe cache + dalvik
5. Reboot twice - wait a few minutes every time. (Do only the performance options, but no script options)
6. Open terminal and write;
"a2sd xdata" --> yes --> yes
7. Wait again a few minutes.
8. Reboot again.
9. That's it!!!: D
Related
Hi all,
I was using the CM7 nightly 203, with the custom MTD partition 140 40. Just wanted to try Sunaabh ROM. Wil the old MTD partition give problems when i flash this new ROM? This ROM is 122MB in size. plz explain how to go abt in flashing this sense rom
Yes, it will. Sense ROMs need upwards of 200MB system partition. You will have to remove the Custom MTD Partitions before proceeding. (It can be removed by flashing Clockworkmod Recovery again, after wiping everything)
Thanks for the prompt reply I have not done that even once.. For this, i must go to ROM manager, Click on Flash ClockWorkMod Recovery and then press "Flash Recovery." Or if am wrong, could you pls explain me?
Not sure if this will work for you too but it did for me, I first changed the settings in the txt file then flashed a new rom and ran the bravo boot zip again.
I did that going from cm7 to sfm and it worked for me without having to flash cwm.
I think if you just change the txt file to fit your new rom then run it all again as you install, should be fine.
Sent from my HTC Wildfire using xda premium
No, that is the temporary way to do it, and it will not touch your actual Clockworkmod Recovery. I would recommend the Fastboot Method.
I have attempted to explain it here:
http://forum.xda-developers.com/showpost.php?p=17633085&postcount=93
So, first boot to Clockworkmod Recovery, Go to Mounts and Storage, then select:
- format /cache
- format /data
- format /system
This will remove all data from your phone (Except stuff on the SDCard). Then, reflash Clockworkmod Recovery from the procedure I linked above.
EDIT: Or you can follow what Scratch wrote above. Make your settings the default (ie 250 40 by changing the values on the text), then proceed. Now that I think of it, his method is way more efficient.
Works perfect. But one question. I had values 190 and 40. But titanium back up shows 262mb of which 94 is free for system and 183mb of which 113 alone is free for internal. Have I done anything wrong ?
Sent from my HTC Wildfire using xda premium
It seems to have reverted back to the Stock settings somehow... BTW, Ti Backup isn't the most reliable one to check the partitions. Use Terminal Emulator, and type su , followed by busybox df -h to get the exact values of all partitions.
If you don't understand what this Modification is doing, why it needs to be done, or what possible benefits come from it, then...
PLEASE DO NOT TRY THIS MOD.
***Even tho it is impossible to brick your phone when flashing this i still highly recommend you UNDERSTAND what you are attempting to do before you do it. If someone explains you are freeing up internal memory from other places not using it and you still have to ask what the benefit is, then you obvisouly dont fully understand the mod and your phone and should turn away now.***
Thank You.
Now onto the mod: Heres a quick description of what this mod is doing. Pretend your phone is a pizza cut into 3 even pieces. Each piece is memory for /cache, /system, /data. Your anorexic sister "aka cache" doesn't eat a lot so most of her slice will always be left, your fat obese brother "/data" always eats his whole slice and is left wanting more. You are healthy "/system" and only eat what you need and never less never more.
What this mod is doing is taking that original pizza and RE-CUTTING the slices to better fit whose eating them, so since your anorexic sister barely eats and your obese brother is always hungry it takes all the extra pizza "aka memory" from your sister and gives it to your brother. As for you "aka /system" you only eat exactly what you need "aka the size of the rom and files it install" so it resizes your own slice to exactly the number it needs to install the rom and its gapps/files and leaves you with just a little wiggle room.
I recently tried the v1.5.8 on the gsm hero n it worked pretty well,before i used2have 170mb of internal memory with my decked for life now after applying this mod i have about 300 mb + which means i dont need a freaking ext4 partition for all my crap! xD
PLEASE USE CLOCKWORK RECOVERY IT WILL NOT WORK ON AMON-RA:
although in the cdma forums they used adb,i didnt feel like using it n didnt cause any issues
Original Files and Instructions: Firerats Original G1/MT3G thread found Here
Media fire link - Download!
(please note i've tried only the 1.5.8 version n it runs fine!)
After you read through firerats original instructions just know that itll be slightly different on your hero!
1. Click on the link i posted above and download these files: FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip
2. Put both those files onto your SDCard.
3. While in your SDCard, make a .txt file named "mtdpartmap.txt"
4. Open your new mtdpartmap.txt file and
if ur using an aosp rom cm6 or cm7 type this into the txt
Code:
mtd 95 15
(The 95 here refers to /system size, and 15 to /cache partition size)
If you are using a larger Sense Rom then type
Code:
mtd 175 15
(This is just an approximation)
5. Once all 3 files are saved on the root of your SDCard, reboot your phone into recovery
6. Format/Wipe your system and cache.
7. Flash the file: FR-recovery-v1.5.X-CustomMTD_S.zip
8. Once the file is done flashing, it'll prompt you to wipe cache, system, and dalvik again.
after wiping cache system and dalvik reboot back into recovery
9.Flash CM7 or CM6 rom if you used 95 for /system or Flash your larger Sense Rom if you used 175 for /system
9.a.Optionally, flash any kernel you may be choosing to use.
10.Flash the file: FR-boot-v1.5.X-CustomMTD_S.zip
11.Click the top option on your recovery menu to reboot your system.
12.Once your system is fully booted you can go into menu > settings > sd card and internal storage , and check all the new added internal memory you have.
FYI : anytime you flash a new rom after this mod, or flash a new kernel to a currently flashed rom, you will ONLY NEED TO FLASH THE SECONDARY FIRERAT BOOT file named "FR-boot-v1.5.X-CustomMTD_S.zip".
so say after this mod you want to try a new kernel, you flash the kernel, flash boot, and reboot the system.
or say you want to flash a new cm7 nightly update, you flash the new rom/update, flash boot, reboot.
or say u want a new nightly and a new kernel, you flash the nightly, flash the kernel, flash the boot, reboot.
its very simple, if anything u flash overwrites current kernel specifications, u need to flash the boot file to make sure it knows how to set itself up. this goes for nandroid back ups as well.
A lil more help- i was using the decked rom so to actually check how much memory was consumed by /system i opened the terminal emulator typed in this
Code:
# su
# df -h
to show me memory consumption.
the command will tell you what % you are using on your system. if you are at 60% then you can go ahead and decrease your /system value in your mtdpartmap.txt to about 2mb over the value it says you are using. so if your rom uses 115mb of /system you can change your mtd to "mtd 117 2".
So if you are getting an error while trying to flash a rom after doing this modification you most likely don't have enough /system space and will want to up your value to something more then enough like "mtd 200 4" then run the above code and re-scale down back to 2mb over what the current rom is using.
Credits-
Foo_Blyat over at the cdma forums based on whose guide i could get this work on our hero and rewrite this guide
Firerat for even making this mode which is BRILLIANCE!!!!!
Proof?
heres a couple of my personal screen-shots after using the mod
{
"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"
}
notice the internal memory and tell me i'm ****ting u ppl
Enjoy
Is it possible to do a nand backup of my current rom, do this mod, and then restore the nand backup? Or does it only work with a fresh flash of a new rom?
Also, could you please explain exactly what the two numbers in the mtdpartmap.txt file are referring to. Thanks.
Woohoo, it works!!
OK, first I'll answer my own questions. It is possible use a nand restore, which is what I did. Secondly, the first number in the txt file refers to the system partition and the second refers to the cache partition. Whatever is left over goes to the data partition.
I decided to be cautious in my numbers. I left the cache partition exactly as it was (130!) and only reduced my system partion by 60mb (still leaving ~10mb of wiggle room in the system partition).
So now I have 60mb extra in internal storage! Sweet!
treesurf said:
Woohoo, it works!!
OK, first I'll answer my own questions. It is possible use a nand restore, which is what I did. Secondly, the first number in the txt file refers to the system partition and the second refers to the cache partition. Whatever is left over goes to the data partition.
I decided to be cautious in my numbers. I left the cache partition exactly as it was (130!) and only reduced my system partion by 60mb (still leaving ~10mb of wiggle room in the system partition).
So now I have 60mb extra in internal storage! Sweet!
Click to expand...
Click to collapse
Nice
Sry I wasn't more accurate, the first number is the system partition and second is the cache partition, cache doesn't need alotta memory perhaps u should make it 35 thereby getting 100mb of data more btw which rom?
Sent from my Hero using xda premium
what can I say ? It simply worked. I used clockworkmod to make a backup of my current ROM first (I am running the latest Heroine) then repartitioned following your instructions, restored the previously backup and voilà, swimming in a sea of free megabytes :
# df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_st
/dev/block/mtdblock3 180.0M 169.8M 10.2M 94% /system <<< was 100% before
/dev/block/mtdblock5 255.8M 153.6M 102.1M 60% /data <<< was more then 90% before
/dev/block/mtdblock4 30.0M 4.2M 25.8M 14% /cache <<< to be safe, I could probably lower it further to 15 as per instructions
/dev/block//vold/179:1
7.4G 5.9G 1.5G 80% /sdcard
I believe that was done earlier. But devs pulled out.
http://forum.xda-developers.com/showthread.php?t=913245
http://forum.xda-developers.com/showthread.php?t=755204
Cheers!
EDIT: I re-read the threads - it appears tha everything worked fine, maxima just bought a new phone
I'm so going to try this tomorrow, I have absolutely NO time today xD more cache is nice
bharat_goku said:
Nice
Sry I wasn't more accurate, the first number is the system partition and second is the cache partition, cache doesn't need alotta memory perhaps u should make it 35 thereby getting 100mb of data more btw which rom?
Sent from my Hero using xda premium
Click to expand...
Click to collapse
When I fill up my new 80mb of /data then I'll think about reducing the cache.
I'm using DeckedForLife ROM.
I always use a "move dalvik-cache to /cache" script. It is a tad safer I guess?
THIS IS CUTE. Gona try it ....
riemervdzee said:
I always use a "move dalvik-cache to /cache" script. It is a tad safer I guess?
Click to expand...
Click to collapse
Yeah, I tried it too. Pretty neat script, but unfortunately it does not increase system partition size.
Also I got suspicions that system is cleaning cache from time to time by deleting older files so as well dalvik files.
edit: proof pics are not visible. Maybe I did not understand everything, but is it possible to make it permanent mod?
It's permanent until you flash your next ROM. So you just need to flash the FR-boot-v1.5.X-CustomMTD_S.zip file after flashing any ROM/nand backup and it will continue to use whatever partition settings you have put in the text file.
For personal use this mod is fine, but if I'm building a custom ROM for public use I need to go through very complicate ROM flash explanation with possibility to brick the phone at the end.
Ok,tried this and it's super . However, I have some strange "problems".
I have set partitions to 100 for system and 30 for cache right from the beginning. If I boot into rom right after flashing, without changing kernel, everything is as it should be. Have over 300 MB on internal storage etc. As soon as I change kernel usb tethering becomes disabled (when I plug the cable it still says that's not connected when I enter "tether menu" ) and nothing helps, not changing kernel, reverting to old one, nothing. Second thing is "power menu", only three options appear in here, reboot, recovery and screenshot. Silent and airplane mode, profiles and power off options don't appear . And finally, when I try to wipe dalvik cache this message pops in recovery :
E: Can't mount /dev/block/mmcblk0p2
(File exists )
Dalvik Cache wiped.
It seems that dalvik is wiped in the end? What's this partition used for?
First two problems go away if I flash some rom without messing with partitions but last one stays
Can someone else please check usb tether and power boot thingy on their phone?
Sent from my Hero using Tapatalk
What ROM do you use?
What recovery do you use?
OP said that AmonRA is not tested, only CWM.
Using decked for life and cwm recovery.
Sent from my Hero using Tapatalk
aca89 said:
Ok,tried this and it's super . However, I have some strange "problems".
I have set partitions to 100 for system and 30 for cache right from the beginning. If I boot into rom right after flashing, without changing kernel, everything is as it should be. Have over 300 MB on internal storage etc. As soon as I change kernel usb tethering becomes disabled (when I plug the cable it still says that's not connected when I enter "tether menu" ) and nothing helps, not changing kernel, reverting to old one, nothing. Second thing is "power menu", only three options appear in here, reboot, recovery and screenshot. Silent and airplane mode, profiles and power off options don't appear . And finally, when I try to wipe dalvik cache this message pops in recovery :
E: Can't mount /dev/block/mmcblk0p2
(File exists )
Dalvik Cache wiped.
It seems that dalvik is wiped in the end? What's this partition used for?
First two problems go away if I flash some rom without messing with partitions but last one stays
Can someone else please check usb tether and power boot thingy on their phone?
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
When u changed kernel did u flash the boot.zip file again?
Also I believe ur changing from .29 to .35 kernel? Did u apply the USB fix by erasmux??
Abt the power menu just wait a bit it comes back...
I made a mistake of implementing move dalvik cache to SD,I think that's causing errors in the
Wipe
Just plug ur fone into ur comp and
Open console go to ur sdk directory and try this command adb remount /dev/block/mmcblk0p2
Not sure if the command is ryt,Bt just give it a try...
Sent from my Hero using xda premium
Thanks for your efforts.
I used Fireat's path already on my G1 (meanwhile I sold it).
It saved me from using ext partition for data, which is in no way a speed booster.
Maybe it's a dumb question, but shouldn't it be possible to integrate this patch in a ROM?
The steps described in your post are easy to understand and absolutely not complicated (for fellows that often change ROMs).
bharat_goku said:
When u changed kernel did u flash the boot.zip file again?
Also I believe ur changing from .29 to .35 kernel? Did u apply the USB fix by erasmux??
Abt the power menu just wait a bit it comes back...
I made a mistake of implementing move dalvik cache to SD,I think that's causing errors in the
Wipe
Just plug ur fone into ur comp and
Open console go to ur sdk directory and try this command adb remount /dev/block/mmcblk0p2
Not sure if the command is ryt,Bt just give it a try...
Sent from my Hero using xda premium
Click to expand...
Click to collapse
I've already done all of that several times (trying out on a few roms) and now I came back to decked and all of the sudden everything works . Menus are back and tethering works.
"/dev/block..." thing is still there. Tried your command but it doesn't help although it's properly written. I read somewhere that formating helps but in my case it doesn't, already tried. So, if you got any other idea I'll gladly try it. In the meantime I'm gonna enjoy the free space on internal storage .
Thanks for help btw.
Sent from my Hero using Tapatalk
Amon Ra
Well, I think I can definitively say this doesn't work on Amon Ra. The second reboot into recovery has to be done via a complete switch off. Tried reinstating from nand backup, but final reboot either sticks on HERO or (sometimes) semi boots into ROM, but without desktop...
Wanted to undo the error of trying this, so downloaded the REMOVE script and flashing that using same procedure, with and without BOOT script, same difference. Tried flashing ROM again, clean. Same difference. So actually I'm a bit stuck.
Any thoughts from anyone how to get back to a safe spot from here and starting over? (Prefer to avoid hard reset!)
Have you tried changing system and cache values in txt file to original ones, or at least something close to them, and then flashing boot.zip. Just a thought, don't know if It's actually going to change something.
Sent from my Hero using Tapatalk
After tons of googling ive finally been able to customize the size of my data partition.
Im sharing it with you all...
Install Instuctions
It really is quite simple
1.download FR-recovery-v1.5.6-CustomMTD_S.zip and FR-boot-v1.5.6-CustomMTD_S.zip
2.create mtdpartmap.txt and put on /sdcard/ see configuration *
3.reboot to recovery
4.nandbackup
5.wipe cache + data
6.flash FR-recovery-v1.5.7-CustomMTD_S.zip(follow onscreen instructions)
7.reboot to recovery
8.Either : -
Nandrestore
or
Flash ROM + extras
9.flash FR-boot-v1.5.7-CustomMTD_S.zip
10.reboot
*For cyanogenmod- write "mtd 135 15"
this will give ur system 135mb, cache 15 mb and rest for data!!!!(u can change the values but be sure u give enough to system otherwise ull face problems while flashing)
NOTE-each time u flash a rom u MUST flash FR-boot-v1.5.7-CustomMTD_S.zip.
NOTE-if u reduce cache size by a large amount, market and other apps depending on cache will fc.
credits-Firerat for the files and instructions at http://forum.xda-developers.com/showthread.php?t=717874
as sense roms are heavy...this wouldnt be of much help.
PS-as always im not responsible if u brick ur device.
PRESS THANKS IF IT HELPED!
Can someone test this please? To OP: does it work?
Want to do it, but don't want a bricked phone.
I just need a 100 mb more for data, so i dont need the build in "move to sd" option from android.
Henry_1 said:
Can someone test this please? To OP: does it work?
Want to do it, but don't want a bricked phone.
I just need a 100 mb more for data, so i dont need the build in "move to sd" option from android.
Click to expand...
Click to collapse
Chicken. As I wrote in the other thread....it works.
Be careful not to undersize your Cache partition though or Market and other apps that rely on it for temp storage will force close.
The guy that said he uses a 10 MB cache partition is on better drugs than I can afford...
dude,
i followed all the mentioned steps by letter but unfortunately i still have the stock part intact
1-copied the files to Sd
2-creating the text file mtd 150 25
3-flashed the recovery attached
4-flashed the rom (caynogenmod 7)
5- flashed the boot file
still have the original partitions :S i am missing smthing ?
wildfire S , **UNLOCKED**
draconian said:
dude,
i followed all the mentioned steps by letter but unfortunately i still have the stock part intact
1-copied the files to Sd
2-creating the text file mtd 150 25
3-flashed the recovery attached
4-flashed the rom (caynogenmod 7)
5- flashed the boot file
still have the original partitions :S i am missing smthing ?
wildfire S , **UNLOCKED**
Click to expand...
Click to collapse
Yes.
First this is a confusing and partially explained tutorial...No offense. Here it is for CM7.x with updated script files and an mtdpartmap.txt for CM7.x
1/ Create the txt file and do not hit enter. Make sure there is no carriage return taking you to a second line.
2/Now save it as "mtdpartmap.txt" (For CM7x you can use 145 20 with no worries).
3/ Copy the recovery file, the boot file and the mtdpartmap.txt files to the root of your SD card
4/Copy Alquez's latest nightyly CM7 zip to the root of your SD card along with the latest gapps zip
5/Reboot to recovery
6/ Erase user data
7/ Under Mounts, format system
8/ Install zip from SD card and run the Recovery zip
9/ Go back to mounts and format data, cache and system partitions
10/ Go to advanced menu and reboot to recovery
11/ If you are restoring a NANDROID backup do so now using backup/restore
12/ If you are installing CM7.x Install zip from SD and flash the CM7 zip and the gapps zip
13/ Install zip from SD card and now flash the boot zip.
14/ Return to recovery main menu and reboot device
15/ Enjoy your roomy CM7.x install!
Don't listen to 135 for CM7! It's not close to enough.
Will it work with Wildfire S with unlocked bootloader (via HTC webpage)? Or is it only for S-OFF phones?
I have the bootloader unlocked and it seems that it does not work :-( Maybe I am doing something wrong?
Y not 250 20?
HTC WILDFIRE S
Cm7
@ d33spx the tutorial is perfect and complete.the steps u posted are unnecessary.
@everyone with s on but bl unlocked: it won't work.
@everyone with soff and cyanogen mod: 135 15 is more than enough...
For sense roms which are debloated 250 20 is good...
135 means I'll have Oly 135 MB internal?
HTC WILDFIRE S
ROM:CM7
1 GB INTERNAL MEMORY
806MHZ OVERCLOCKED
ELECTRIC CYAN THEME
szpaq69 said:
will it work with wildfire s with unlocked bootloader (via htc webpage)? Or is it only for s-off phones?
I have the bootloader unlocked and it seems that it does not work :-( maybe i am doing something wrong?
Click to expand...
Click to collapse
only on s-off phones !!
If i do a nandroid backup and after partition if i do a nandroid restore will the partition go??
kp.nikhil said:
If i do a nandroid backup and after partition if i do a nandroid restore will the partition go??
Click to expand...
Click to collapse
Follow the OP... Simple as that.
kp.nikhil said:
If i do a nandroid backup and after partition if i do a nandroid restore will the partition go??
Click to expand...
Click to collapse
You need to flash flash "FR-boot-v1.5.7-CustomMTD_S.zip" immediately after flashing a new ROM or Restoring any nandroid backup before restarting your device. This will keep your partitions.
Cheers!!
What mtdpartmap would you recommend for modpunks CM9?
Hi folks,
I'm brand new to the world of Android. Over the past couple days I've managed to go from a UK Orange branded Desire, to a fully rooted, S-Off Desire running MildWild v4.3 with the help of some of the guides on this site. But I've finally hit an impasse and could really use a bit of guidance.
Given the technical limitations of the phone I wanted a stable Rom which was relatively easy to install for a first try. But I can't find the information I'm after regarding sd-ext. I'm hoping someone could clarify or point me towards answers for the following:
I've managed to enable installing and moving to sd-ext, but for some reason certain apps e.g. gmail, mail, google play cannot be moved to sd-ext let alone uninstalled from the phone. Is this because they are core system/Android applications?
Even after setting the default install location to sd-ext, once I've installed several apps my internal memory drops from 101mb to 71mb. Is this to be expected? I've not finished installing my apps so I expect this to drop some more.
On the stock HTC rom, the browser would save a cache to the internal memory, so I opted for Opera Mobile instead. Is this still true for Mildwild? Or does the rom store data & caches to the sd card?
Ultimately, I'm shooting for my apps to reside on the sd-ext partition and making sure as much of the data/cache is there, leaving as much space free on the internal memory.
1. these are system apps, so cannot be uninstalled. keep them on system partition anyway, they run fine from there.
2. yes. app data, system app dalvik cache and app cache get stored on /data partition (internal) with this rom. space will gradually decrease the more you install.
3. yes, as above app cache gets stored on /data, including browser, thought this is probably true for most roms.
a couple of points:
1. I believe you are still on stock hboot. to maximise space, you need to change to cm7r2 hboot (easy since you are s-off). basically if you are still on stock hboot, you have a lot of system partition space free and wasted, which can be repartitioned to internal by switching hboot...i.e. you get more internal memory
i recommend to:
- nandroid backup
- change to cm7r2 hboot (recommend using fastboot, guide here)
- boot into recovery, full wipe and nandroid restore2. install an app like 'diskusage'. you'll be able to browse all your partitions to see how and where all your space is being used to help troubleshoot space issues. can do this for any rom.
Thanks for the clarification.
eddiehk6 said:
a couple of points:
1. I believe you are still on stock hboot. to maximise space, you need to change to cm7r2 hboot (easy since you are s-off). basically if you are still on stock hboot, you have a lot of system partition space free and wasted, which can be repartitioned to internal by switching hboot...i.e. you get more internal memory
i recommend to:
- nandroid backup
- change to cm7r2 hboot (recommend using fastboot, guide here)
- boot into recovery, full wipe and nandroid restore
Click to expand...
Click to collapse
Regarding the hboot, you are likely correct. As far as I know the n00b proof everything guide I've followed didn't mention anything about changing hboot. I did see mention of cm7r2 on rom download pages but didn't understand what it meant.
Having looked at the Alpharev website, if I've understood it correctly, by flashing the Hboot with cm7r2, I should have approximately 140mb more than on the stock hboot. While flashing the hboot *seems* simple enough am I able to return to my original hboot at a future date or is it lost forever, meaning I have to rely on the Alpharev hboot images?
If I'm going to wipe the device anyways for the hboot it gives me a chance to try a different rom
2. install an app like 'diskusage'. you'll be able to browse all your partitions to see how and where all your space is being used to help troubleshoot space issues. can do this for any rom.
Click to expand...
Click to collapse
I downloaded diskusage, what a lovely program!
I did notice I had a peculiar folder on my sd card titled "backup" with two backups around 250-350mb in size. I'm guessing these are my nandroid backups?
5nak3 said:
Thanks for the clarification.
Regarding the hboot, you are likely correct. As far as I know the n00b proof everything guide I've followed didn't mention anything about changing hboot. I did see mention of cm7r2 on rom download pages but didn't understand what it meant.
Having looked at the Alpharev website, if I've understood it correctly, by flashing the Hboot with cm7r2, I should have approximately 140mb more than on the stock hboot. While flashing the hboot *seems* simple enough am I able to return to my original hboot at a future date or is it lost forever, meaning I have to rely on the Alpharev hboot images?
If I'm going to wipe the device anyways for the hboot it gives me a chance to try a different rom
Click to expand...
Click to collapse
you understand exactly the differences between the hboots. you'd be surprised that people who do actually flash them have no idea what they're doing or what they are
you can easily switch between hboots, you pick it depending on the rom's system size. you can go back to stock hboot by flashing 'bravo downgrader' (some hboots like cm7r2 are write protected), followed by 'bravo stock' from alpharev.
before flashing them, check the md5sums of the hboots using a free program like md5check.
once you've set up fastboot as above, follow the commands on alpharev (just beneath the table of hboots). you'll see cm7r2 at the top of the bootloader screen if successful.
I downloaded diskusage, what a lovely program!
I did notice I had a peculiar folder on my sd card titled "backup" with two backups around 250-350mb in size. I'm guessing these are my nandroid backups?
Click to expand...
Click to collapse
nandroid backups are stored in sdcard/clockworkmod/backup
i always keep a couple on PC for safe keeping, they can also start to take up a lot of space on sd once you start to install lots of apps.
make sure you always nandroid backup before flashing a zip or different rom. when/if you restore them if something goes wrong or you don't like the changes, you restore the exact state of the phone (contacts, apps, homescreens...EVERYTHING)
Ok I must be missing a trick somewhere.
I've followed all the steps outlined on Alpharev's site:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything and restore.
Click to expand...
Click to collapse
Everything is great up till step 5. In fact my fastboot menu says "alpharev cm7 v2" which I can only assume means great success on my part.
Can someone please explain what step 6 is? Do i reboot the device? Should I power down and do "volume key+power" then wipe? In my fastboot menu there is no recovery option...
5nak3 said:
Ok I must be missing a trick somewhere.
I've followed all the steps outlined on Alpharev's site:
Everything is great up till step 5. In fact my fastboot menu says "alpharev cm7 v2" which I can only assume means great success on my part.
Can someone please explain what step 6 is? Do i reboot the device? Should I power down and do "volume key+power" then wipe? In my fastboot menu there is no recovery option...
Click to expand...
Click to collapse
Fastboot erase cache is a fastboot command.
In fastboot menu select bootloader and press power and then in bootloader select recovey and press power to enter recovery
Sent from my HTC Desire
jmcclue said:
Fastboot erase cache is a fastboot command.
In fastboot menu select bootloader and press power and then in bootloader select recovey and press power to enter recovery
Click to expand...
Click to collapse
Excellent, I was lost at that last step and this is what I needed to piece it all together. I can happily confirm everything went well. I have my rom installed and the phone is still going.
Many thanks jmcclue, and of course eddiehk6 really appreciate your help in getting my up and running.
mildwild sd-ext
5nak3 said:
Hi folks,
I'm brand new to the world of Android. Over the past couple days I've managed to go from a UK Orange branded Desire, to a fully rooted, S-Off Desire running MildWild v4.3 with the help of some of the guides on this site. But I've finally hit an impasse and could really use a bit of guidance.
Given the technical limitations of the phone I wanted a stable Rom which was relatively easy to install for a first try. But I can't find the information I'm after regarding sd-ext. I'm hoping someone could clarify or point me towards answers for the following:
I've managed to enable installing and moving to sd-ext, but for some reason certain apps e.g. gmail, mail, google play cannot be moved to sd-ext let alone uninstalled from the phone. Is this because they are core system/Android applications?
Even after setting the default install location to sd-ext, once I've installed several apps my internal memory drops from 101mb to 71mb. Is this to be expected? I've not finished installing my apps so I expect this to drop some more.
On the stock HTC rom, the browser would save a cache to the internal memory, so I opted for Opera Mobile instead. Is this still true for Mildwild? Or does the rom store data & caches to the sd card?
Ultimately, I'm shooting for my apps to reside on the sd-ext partition and making sure as much of the data/cache is there, leaving as much space free on the internal memory.
Click to expand...
Click to collapse
Hi folks,
just a quick note on this post. I just moved from Mildwild CM- 5.0 to Mildwild 4.3 (Oxygen) because the first one was giving me a delay problem on call. before the move I have made a titanium backup of all my apps+data. After the I have installed mildwild 4.3 and restored all the app+data I have something like 17Mb internal memory free whether with the MildWild 5.0 I had more than 40mb.
Could something explain that? Did I do something wrong?
thanks
stegal said:
Hi folks,
just a quick note on this post. I just moved from Mildwild CM- 5.0 to Mildwild 4.3 (Oxygen) because the first one was giving me a delay problem on call. before the move I have made a titanium backup of all my apps+data. After the I have installed mildwild 4.3 and restored all the app+data I have something like 17Mb internal memory free whether with the MildWild 5.0 I had more than 40mb.
Could something explain that? Did I do something wrong?
thanks
Click to expand...
Click to collapse
Nop, you can move them manually to sdcard. I don't think when restoring apps they will all go straight to sdcard, sometimes you need to move them manually.
You can also go to cyanogenmod settings and in the first option (I think is about allowing moving apps?) select there to move to sdcard by default.
To help you can also download S2E from the market, open it, select Apps and Private Apps and if dalvik if you still need space. Leave app data on internal, selecting only Applications to be moved. Reboot, if you're still short on space, open S2E again and select to move Dalvik as well, reboot, you should be okay now
Using cmr2 hboot also allows more space on internal, less headaches
stegal said:
Hi folks,
just a quick note on this post. I just moved from Mildwild CM- 5.0 to Mildwild 4.3 (Oxygen) because the first one was giving me a delay problem on call. before the move I have made a titanium backup of all my apps+data. After the I have installed mildwild 4.3 and restored all the app+data I have something like 17Mb internal memory free whether with the MildWild 5.0 I had more than 40mb.
Could something explain that? Did I do something wrong?
thanks
Click to expand...
Click to collapse
do not use S2E with Mildwild Oxygen: "S2E works only with CyanogenMod7 and CyanogenMod9"
you do not need to use any extra apps to move apps to sd-ext. follow the instructions in the first post of the mildwild thread.
you should be s-off with cm7r2 hboot to maximise space with this rom. (cm7r2 hboot with Mildwild CM-5.0 would also work)
read my first reply in this thread to understand where all your apps/dalvik/data are stored: i.e. use an app like 'diskusage' to check
Hi all,
i was testing this ROM and it works pretty well for a pre-alpha release. Actually there is a known issue (Settings / Apps / Properties -> FC) that is driving me nuts... I really need to open the Properties to move certain apps to "internal".
There are a couple of apps natively installing parts on SD card, for example Final Fantasy 4 or the XDA developers app. For whatever weird reason when the phone is rebooting these apps are completely disappearing and need to be reinstalled from the Playstore. This is happening to all apps which are "on SD card" in Settings / Apps.
So far i could not figure out why these apps are disappearing, but i believe the Properties FC is related to the INT2EXT4 script. I tried removing the script from init.d folder in the zip file to use Mounts2SD from Playstore instead. Did a full wipe and reinstalled, but then everything was force closing at setup wizard sceen.
Is it possible to remove the INT2EXT4 script from this ROM without crippling it completely? If yes, what is the procedure to remove it properly?
Any help would be appreciated.
Thanks for opening up a Q&A thread.
To remove INT2EXT and make a full restore of A2SD, you have to
1. remove 40int2ext from system/init.d/
2. copy the following files from any JB rom with A2SD support:
- system/init.d/03sdcard
- system/init.d/10apps2sd
- system/bin/a2sd
Click to expand...
Click to collapse
I hope this will solve your problem.
Another thing to check, how did you partition your sd card? Should be done with 4EXT recovery or gparted only (not minitool)
Backup and repartition your sd card if it's not done with those methods. One FAT32 partition, one 1.5-2GB max ext4 partition, no need for swap even though I think it says in OP.
To get around apps installing partially on sd card you could try a couple of things instead of replacing the script as it should work:
- Use titanium backup, long press an app and to move them to 'internal' to move to sd-ext, gets around having to navigate app settings
- I believe the ROM comes bundled with Xposed? Find a module called Modaco Toolkit, has a system option to 'Disable Forward Lock' which should prevent auto installation of apps to SD card (it works for me on Nexus devices preventing apps installing to virtual /mnt/asec sdcard partition, not tested with a real SD card but I believe the principle is the same, try it). If this method works, it's cleaner as apps should always get installed to 'internal' (sd-ext) in the first place.
spezi77 said:
Thanks for opening up a Q&A thread.
To remove INT2EXT you have only to remove it from system/init.d/
But you will have to copy 03sdcard into system/init.d/ folder. This script comes along with a2sd and is responsible for mounting the sd-ext.
I hope this will solve your problem. If not you should insert the following files for a full restore of a2sd:
- system/init.d/03sdcard
- system/init.d/10apps2sd
- system/bin/a2sd
Click to expand...
Click to collapse
Thanks for the quick response.
Tried your suggestion without success. As soon as I remove INT2EXT from init.d in the zip file ROM is going crazy force closing everything after fresh installation. Very strange... Restoring A2SD didnt help either. Is it only me or is it reproducible for other users?
eddiehk6 said:
Another thing to check, how did you partition your sd card? Should be done with 4EXT recovery or gparted only (not minitool)
Backup and repartition your sd card if it's not done with those methods. One FAT32 partition, one 1.5-2GB max ext4 partition, no need for swap even though I think it says in OP.
To get around apps installing partially on sd card you could try a couple of things instead of replacing the script as it should work:
- Use titanium backup, long press an app and to move them to 'internal' to move to sd-ext, gets around having to navigate app settings
- I believe the ROM comes bundled with Xposed? Find a module called Modaco Toolkit, has a system option to 'Disable Forward Lock' which should prevent auto installation of apps to SD card (it works for me on Nexus devices preventing apps installing to virtual /mnt/asec sdcard partition, not tested with a real SD card but I believe the principle is the same, try it). If this method works, it's cleaner as apps should always get installed to 'internal' (sd-ext) in the first place.
Click to expand...
Click to collapse
1 GB sd-ext partition created with 4EXT, no swap. Had bad experience with minitool and even gparted so I always use 4EXT for partitioning. Works fine for every other JB or ICS ROM.
***facepalm*** YES OF COURSE TB!! - that's the workaround, shame on me... Sometimes you don't see the wood for the trees...
BTW with Xposed and Gravity / Modaco toolkit Final Fantasy 4 refused to start, I had to remove both modules to get it working again.
Thanks a lot for driving me to the right direction, I'm fine with the workaround for now.
Siluxsept said:
Thanks for the quick response.
Tried your suggestion without success. As soon as I remove INT2EXT from init.d in the zip file ROM is going crazy force closing everything after fresh installation. Very strange... Restoring A2SD didnt help either. Is it only me or is it reproducible for other users?
Click to expand...
Click to collapse
Did you make those changes directly on your device? If yes, I suppose to modify the .zip instead and then flash it after doing a full wipe.
spezi77 said:
Did you make those changes directly on your device? If yes, I suppose to modify the .zip instead and then flash it after doing a full wipe.
Click to expand...
Click to collapse
No I did not change anything at OS level - that's the weird thing, i always adjust the zip file and flash it after full wipe.
Siluxsept said:
No I did not change anything at OS level - that's the weird thing, i always adjust the zip file and flash it after full wipe.
Click to expand...
Click to collapse
Tested one more time with a fresh download. As soon as I remove int2ext from zip file and flash it after full wipe all apps are force closing at setup wizard screen.
Siluxsept said:
Tested one more time with a fresh download. As soon as I remove int2ext from zip file and flash it after full wipe all apps are force closing at setup wizard screen.
Click to expand...
Click to collapse
That's really strange. However, thanks for your feedback. For the next version, I will create two variants of the rom (a2sd/int2ext).