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
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.
[TUTORIAL][S-OFF!]290 MB Data Partition!!! & Installing CyanogenMod 7 Step By Step!
Now with a video tutorial for download!!!
A while ago I came across a great scrip from Firerat and I figured it was time to highlight it again as he's updated it constantly.
I thought I would take the time to put together a tutorial on how to do the following:
1/ Change the size of your /System, /Data, and /Cache partitions to give you a HUGE amount more /Data space for efficiently sized ROM's like CyanogenMod 7.x
2/ Show you how to install CyanogenMod 7.x with these custom partition sizes and verify that they are as expected.
What you will need:
A prerequisite is a custom recover, preferably Alquez's Unofficial CWM Recovery 5.0.2.6
1/ To download and place on your SD Card the latest build of Alquez's CM7.x. (Do not unzip!)
2/ Google apps (GAPPS) for CyanongenMod 7.x, which you will also place on your SD card (Do not unzip!)
3/Firerat's 1.5.8 MTD Boot Script which you will also place on you SD card (Do not unzip!)
4/ Firerat's 1.5.8 MTD Recovery Script which you will also place on you SD card (Do not unzip!)
5/ The custom mtdpart.txt file that defines your custom partition sizes. Place this on your SD card in the same folder as the boot and recovery scripts. For ease of explanation let's just put all the required files on the root of your SD card.
Now you have all the files that you are going to need it's time to begin:
1/ Alter the txt file to suit your need but do not hit enter. Make sure there is no carriage return taking you to a second linein the file.
{
"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"
}
2/Now save it as "mtdpartmap.txt" (For CM7x you can use 145 20 with no worries). Don't listen to people telling you that 125 5 is a good setting. They don't know what CM7.x you are using and I do. Trust me.
3/ As mentioned earlier download and opy the recovery file, the boot file, the mtdpartmap.txt, Alquez's latest CM7.x nightly, and the latest version of GAPPS to the root of your SD card
5/Remove the rear cover of your phone
6/ Remove your phone's battery and replace it while unplugged
7/ Ensure you have a good charge before you begin (Say 30% or more)
8/ Press and hold Volume Down+Power at the same time to reboot into CWM or Razor recovery. (We will be using CWM Unofficial 5.0.2.6 for this tutorial)
9/ Perform a Nandroid backup of your current ROM to make sure you have something to go back to should you wish!!!
10/ Choose wipe data/Factory reset from the menu and follow the prompts.
11/ Go to the Mounts and Storage Menu and follow the prompts to format your system partition.
12/ Go back to the main menu and choose Install zip from SD card and follow the prompts to install the Recovery zip that will set your mount points for your partitions and give you the space you are looking for. (WHEN DONE BE CAREFUL! THERE IS ANOTHER IMPORTANT STEP TO PERFORM HERE IN THE NEXT STEP!!!)
**Notice it now says to wipe system, cache, and data partitions then reboot to recovery. Very important! This is the #1 reason why this fails for people. Read it carefully.
Now here's how to do it!:
1/ Return to the Mounts and Storage Menu
2/ Format the Cache, Data, and System partitions by following the prompts. (DO NOT FORMAT ANYTHING ELSE AND BE CAREFUL TO CHOOSE SYSTEM NOT SD CARD!!!)
Now for part three...
Part 3:..
1/ Go to advanced menu and reboot to recovery
2/ If you are restoring a NANDROID backup do so now using backup/restore and restoring the NANDROID backup you wish to put on the new partitions but beware about trying to restore something onto the new cache and system partitions that is too big for them!!!
**Note! From here on in we are going to skip the screen shots of Install zip from SD, and confirming it. If you haven't gotten this down by now it's perhaps time to head to your local nerd and get him/her or he-she to do this for you.
3/ Installing CM7.x install zip from SD
4/ Install the Google apps GAPPS zip from the SD
5/ Install the boot portion of the script from the SD card. This portion allows your device to find the right start and end points for the newly resized partitions that you created.
**NOTE!!! You must rerun this portion of the script every time you do a wipe and install or wipe and NANDROID restore! If you do not your device will become stuck at the boot splash screen. So keep this script file on your SD card!
6/ Return to recovery main menu and reboot device and enjoy your roomy CM7.x install!
Now:
Let's confirm through Terminal Emulator that your partitions are actually changed!
-Click on the centre home button on the bottom of your screen to bring up the all apps list.
-Scroll across to the T's and load Terminal Emulator by clicking on it.
-Once inside Terminal Emulator type the following followed by Return/Enter on your virtual keyboard:
"busybox df -h"
-This will bring up the list of all the partitions on your system and as you can see your Data partition is now 290 MB, your Cache partition is now 20 MB and your System partition is now 145 MB with 8.8 MB remaining on your system partition. Just enough for integrating updates to your system apps into the System partition.
So that's it!
Now how about moving ahead to my LINK2SD prepping and configuring tutorial and my Speed up your GPS CWM flash update to top it all off!
Well done!
IF THIS TUTORIAL HELPED YOU PLEASE CLICK THANKS!!!
Excelent tutorial, thx.
really good tutorial but i didn't get it what advantages i got from this ?
speed or more space in internal memory
hanynemesis said:
really good tutorial but i didn't get it what advantages i got from this ?
speed or more space in internal memory
Click to expand...
Click to collapse
Well CM7 is a speedy ROM as it's well tweaked to begin with and obviously has a low overhead due to the size.
This gives you an additional 120 MB of internal memory! Combine that with LINK2SD and you've got a phone virtually unlimited for apps.
Glad the tutorial helped.
One more thing...
Even though the tutorial show 1.58 beta files the linked files are actually 1.58 final. A little added bonus.
Thanks for the PM question so I could clarify that and please click THANKS if if you appreciate this tutorial.
D
So, overall this increases the internal memory for apps am I right?
Great tutorial mate, will do this on next nightly update with a kernal.
Check this out...
Now with a video tutorial for download!!!
See the first post...
isn`t it easier to flash cm, then just boot into recovery and install data 2 sd, after partitioning your sd card ext4 1 gb + rest fat32 ?
What exactly do you have to do with 1.5.8 MTD Boot Script zip file?
I try to install another ROM (circle battery - change the battery icon) and when I was going to reboot, my phone get stucked at the CyanogenMod logo. It reproduced it again and again. Should I reinstall 1.5.8 MTD Boot Script zip file after doing this or what? Do you know the correct way to install it?
Besides, I pretty good tutorial. Too clearly explanated.
You have too flash the boot script after you flash a new ROM or a backup. That's explained.
Sent from my cm7.2 Wildfire S
b02 said:
isn`t it easier to flash cm, then just boot into recovery and install data 2 sd, after partitioning your sd card ext4 1 gb + rest fat32 ?
Click to expand...
Click to collapse
Do what you wish of course.
I prefer link2sd and a load of internal fast memory for booting and important apps. A distinguishing feature that data2sd doesn't have.
If your SD card fails you still have your most important stuff with you. Can't say that for DATA2SD or DATA2WHATEVER, etc...
Sent from my cm7.2 Wildfire S
not working for my htc wildfire s a510e after doing all steps and "busybox df -h" show me the data partition size 150 mb and 40 mb was used (
d33ps1x said:
You have too flash the boot script after you flash a new ROM or a backup. That's explained.
Sent from my cm7.2 Wildfire S
Click to expand...
Click to collapse
Ok. That's what I thought but I think I did it wrong or something. So the steps are this:
1. Install new ROM or backup.
2. Go to install zip from sd and select the boot.
3. Install it.
4. Reboot the phone.
ROMTesting said:
Ok. That's what I thought but I think I did it wrong or something. So the steps are this:
1. Install new ROM or backup.
2. Go to install zip from sd and select the boot.
3. Install it.
4. Reboot the phone.
Click to expand...
Click to collapse
Yes. Of course this is for a backup or different rom or something. You still have to do the recovery scrip to resize for your initial resizing.
d33ps1x said:
Do what you wish of course.
I prefer link2sd and a load of internal fast memory for booting and important apps. A distinguishing feature that data2sd doesn't have.
If your SD card fails you still have your most important stuff with you. Can't say that for DATA2SD or DATA2WHATEVER, etc...
Sent from my cm7.2 Wildfire S
Click to expand...
Click to collapse
i just asked, and i just hope that sd card wont crash (didnt happen since i first flashed cm)
though, a GREAT guide mate, very well explained ...
p.s. guys click thanks for this, cos' that takes some time to be made, even if oyu dont use it
You know, I've tried (probably) every single method posted on these boards about flashing CM7, and yet I can't get it to work properly. This is really the most step-by-step tutorial I've seen and I thought it would work, but no, still no data connection.
With other methods I've tried, they've either disabled both Wi-Fi and mobile data connection, just one of the two, or there's a missing phone/dialer app.
With this one, the Wi-Fi's working, but I still have no data connection. Any ideas as to why this could be?
johnnyspritz said:
You know, I've tried (probably) every single method posted on these boards about flashing CM7, and yet I can't get it to work properly. This is really the most step-by-step tutorial I've seen and I thought it would work, but no, still no data connection.
With other methods I've tried, they've either disabled both Wi-Fi and mobile data connection, just one of the two, or there's a missing phone/dialer app.
With this one, the Wi-Fi's working, but I still have no data connection. Any ideas as to why this could be?
Click to expand...
Click to collapse
Did you try the libril fix? What is your radio version?
http://forum.xda-developers.com/showthread.php?p=21147430#post21147430
If you have a different RUU that Euro 2.3.5 then grab your own libril.so from /system/lib on your RUU install and save it to your SD.
Re-install CM7 and replace and set permissions on libril.so
I've followed this tut d33p, but my phone still displays total 150mb internal storage, why?
Strange, I've used this mod also a month ago and it works great.
However I've used slightly different instructions.
Here we go:
put all the required data on the root of your sd card
reboot in recovery
take nandroid backup
go to mounts - format system
factory reset
advanced - wipe dalvic cache
install custom recovery script
reboot in recovery
restore nandroid backup
install custom boot script
reboot
This worked for me, don't know if it works for you guys.
Say it
Hi everyone.
I'm currently using ICS 4.0.4 (by sandvold) and I've once before made a post about this problem but never got a definite answer. So here goes again.
My problem is that I'm running out of memory on my Desire even though I should have plenty of space left on my sd-ext partion. I have a 2 GB partion on my external memory card of 32 GB total which I created using gparted. I'm using Stock HBOOT.
Today I got the message of getting low on memory again. Last time I tried fixing it by doing a full wipe, update the rom, and install a2sd again with the commands:
Code:
su
a2sd install
followed by a y/n/y answer to the command line questions. After which I did a manual re-installation of the apps I wanted from market.
I really need a solution for this problem since I happens too often for me, and always at the worst possible times.
Would it help me to install another HBOOT?
Is there some limit on how huge a partion I can use on different HBOOTs/Roms?
Is there any difference of which ext-partition you use? (ext2-3-4? I'm using ext-4 myself)
Could it be possible that the a2sd install command doesn't execute properly or that I'm limited in some other way?
I've tried using different ways to check if a2sd really is installed but my problem is that I don't know where to look for the answers or how they should really look.
I tried using Disk Usage which I got from the market and I tried using the following command in the terminal emulator:
Code:
ls -l /data
In the Disk Usage app I went to the "required root" option and checked my sd-ext partition which looked to be filling up nicely and still had plenty of space. Don't know if that was what I was supposed to though. I posted the reply I got from running the command written above and got told that it looked like my a2sd wasn't working.
I really look forward to getting some answers or ideas for what I could try.
Can you show the results of running df from a terminal? Should give you an idea of what is filling up.
I believe that a2sd leave the app data (not the apk) on the internal nand rather than in sd-ext so I'd expect /data to be quite full.
If this is the case, you can change hboot to give more space in /data or try a different a2sd script (from the installer).
Here's the output from the df command:
{
"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"
}
You can see that /data is pretty full as it still contains the app data while the app apk's are on the sd-ext.
Your choices are install a different hboot, this basically repartitions the internal nand to give you more space in /data but takes space away from other partitions such as /system. Please bear in mind that some ROM's will need a specific hboot configuration to give them enough room to run.
Sanvold's ICS isn't too picky and I'm currently running it with cm7r2 which takes the /data partition from 147MB to 287MB giving you much more space! There are risks involved when changing your hboot and you will need to be s-off - the guides at the top of the forum can run you through this.
An alternative if you don't want to change hboot is to try a different a2sd option when installing the rom. I believe that Amarullz should give you more space as it moves more to sd-ext.
You'll need to experiment to see what works best for you
langers2k said:
You can see that /data is pretty full as it still contains the app data while the app apk's are on the sd-ext.
Your choices are install a different hboot, this basically repartitions the internal nand to give you more space in /data but takes space away from other partitions such as /system. Please bear in mind that some ROM's will need a specific hboot configuration to give them enough room to run.
Sanvold's ICS isn't too picky and I'm currently running it with cm7r2 which takes the /data partition from 147MB to 287MB giving you much more space! There are risks involved when changing your hboot and you will need to be s-off - the guides at the top of the forum can run you through this.
An alternative if you don't want to change hboot is to try a different a2sd option when installing the rom. I believe that Amarullz should give you more space as it moves more to sd-ext.
You'll need to experiment to see what works best for you
Click to expand...
Click to collapse
I think that a2sdx by amarullz dosn't wotk with stock hboot, tried it a few times with different rom and always without success. But with cm7r2 works perfectly.
Sent from my HTC Desire using XDA
langers2k said:
You can see that /data is pretty full as it still contains the app data while the app apk's are on the sd-ext.
Your choices are install a different hboot, this basically repartitions the internal nand to give you more space in /data but takes space away from other partitions such as /system. Please bear in mind that some ROM's will need a specific hboot configuration to give them enough room to run.
Sanvold's ICS isn't too picky and I'm currently running it with cm7r2 which takes the /data partition from 147MB to 287MB giving you much more space! There are risks involved when changing your hboot and you will need to be s-off - the guides at the top of the forum can run you through this.
An alternative if you don't want to change hboot is to try a different a2sd option when installing the rom. I believe that Amarullz should give you more space as it moves more to sd-ext.
You'll need to experiment to see what works best for you
Click to expand...
Click to collapse
I think that a2sdx by amarullz doesn't wotk with stock hboot, tried it a few times with different rom and always without success. But with cm7r2 works perfectly.
Sent from my HTC Desire using XDA
I have a question regarding the change of a hboot. Currently I'm on stock and I wanna try out the cm7 one.
First of: "Where do I find it?".
Secondly: "How do I change hboot?"
I tried using the search function but was unable to find the answer to any of the above two questions. I might be able to find a cm7 hboot, but where do I find the correct one, the newest one for desire?
Third: "Will I have to "format" my device to change hboot?"
Thanks in advance
Sent from my HTC Desire using XDA
before you go down the route of changing hboot i suggest you try the command su a2sdcachesd this worked for me when i used sandvolds rom. failing this try and flash dk_zero-cool ROM http://forum.xda-developers.com/showthread.php?t=1403113 which uses mount2sd and has a giu. if you cant get either of these to work you must be doing something wrong, but if you do want to change hboot you can use fastboot (http://forum.xda-developers.com/showthread.php?t=619153). you can find hboot-bravo_alphaspl-cm7r2.zip here http://diaduit.bounceme.net/ there are also some other good things found in this repository.
Hammerbak said:
First of: "Where do I find it?".
Secondly: "How do I change hboot?"
Click to expand...
Click to collapse
As you are stock there are probably two parts to changing your hboot, firstly to s-off your device and then to flash the hboot you want. On the following thread http://forum.xda-developers.com/showthread.php?t=1275632 search for [14]FLASHING HBOOT/SPL for more info.
When I did s-off I used http://alpharev.nl/ but this has since been replaced with http://revolutionary.io/ which I have no experience of. Once you have s-off, changing hboot is pretty easy.
Hammerbak said:
Third: "Will I have to "format" my device to change hboot?"
Click to expand...
Click to collapse
If you were to try a backup/restore when changing hboots, you would run out of space when you did the restore leaving the device stuck in a bootloop. The installer checks which hboot you have and puts some files in /system and others in /data which will then be moved to the sd once you activate a2sd.
You'll need to:
- backup stuff you care about
- s-off your phone
- change the hboot to cm7r2
- complete wipe from recovery to be safe
- install the rom from recovery (version 0.12 is out now)
- activate a2sd
I already used the revolutionary method and my device is s-off.
When you say I could run out of memory when taking a backup, which kind of backup are you then referring to?
I am currently using titanium backup to backup my app and settings.
I am assuming that taking a nand backup is what I should do before changing my hboot.
My current understanding is that I should do a nand backup, back up my sd-card by saving everything to my pc, install the hboot, restore my nand backup after I restore stuff to my sd-card from my pc.
Is this the right process?
Sent from my HTC Desire using XDA
I'm talking about a nandroid backup, if you do a backup you'll have a potential 250MB of data from the system partition. If you change the hboot to one with only 145MB (such as cm7r2) then there is a very good chance the backup simply won't fit when you come to do a nandroid restore. This will leave a half restored /system that won't boot.
It's always good practise to do a nandroid backup, that way you can restore the hboot to stock then do a restore to get to a known good state if needed.
In this case don't do a nandroid restore, use titanium backup after you enable a2sd. This way your apps will be restored into the sd-ext partition.
Thanks a lot. I'm gonna try to flash this cm7 once I get home from college
I have just one question which I feel I haven't gotten a reply to yet. How do I change my hboot? Do I just flash it from recovery like any other rom or will I have to use ADB?
Hammerbak said:
Thanks a lot. I'm gonna try to flash this cm7 once I get home from college
I have just one question which I feel I haven't gotten a reply to yet. How do I change my hboot? Do I just flash it from recovery like any other rom or will I have to use ADB?
Click to expand...
Click to collapse
posts 8 and 9 posted guides for you .
plenty of searchable posts within Q&A too, edit: searched 'change hboot' and found another one
there are a few methods, but i recommend using fastboot. you do not flash them from recovery or use adb...
Thanks to all of ya.
It seems I finally got the courage to fix my longer existing problem. And it works. Flawlessly!
I was a little "slow" regarding the guides that were posted but I'm glad I got the links for these.
See you all until next time!
Hi guys,
Newbie to the forum and android just need a bit of help as im pretty stuck at the moment and i dont know whats gone wrong.
I wanted to install Jelly Bread v5.0 or something other that the restricted phone carrier os on my phone when i got it (i wont mention just incase) so heres what i did.
rooted the phone using an update.zip from on this forum somewhere.
installed: signed_cwm-5.0.2.7-flashablezip-ext4only.zip
then installed: Jelly Bread v5.0
was ok for a while and working but then i wanted to play with other ROMS (in this case i now wanted to try cm-10.1.4-GT-S5660-gio++.zip)
I enter recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, wipe batt stats
Then install cm-10.1.4-GT-S5660-gio++.zip
Then it hung for 35mins at loading blue circle screen.
I then took battery out and enter recovery, and attempt to wipe data/fatory reset and it says:
--Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/stl13
Formatting /Cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/ .android secure...
Data wipe complete
Also i cant wipe dalvik cache it just does nothing blinks 1 second then back to menu.
From here (silly me i forgot to backup) ive tried to flash a few stock roms but still getting boot loops and the same above errors.
Is there any way i can format and write /data and /sd-ext?
Anyone know what i can do to fix this please?
Thanks for any help in advance.
update
Hi guys,
Just an update.. have tried several stock ROMS via ODIN always flashing CWM and flashing custom ROMS but nothing with flash and reformat the /dev/stl13 block. im always getting this error and i believe its causing my boot loop issues.
I found this thread via google:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
is there anybody on here that could guide me through using ADB shell to rebuild/reformat the /dev/stl13 block?
I dont feel confident enough to do it. (Have already installed shell on my laptop though)
This is driving me crazy trying to fix. My first android ROM flash gone wrong
(i got it working fine with Jellybread but wanted to try something else)
Any help appreciated.
Cheers
Richie
Got your PM, but this sort of discussion is best kept in public.
Be careful with that HTC-related thread, it's a different device, with a different set of tools and likely a different partitioning method.
Back to basics: have you tried flashing back to stock with Odin and formatting your /data and /cache partitions with the Samsung stock recovery?
AFAIK CWM5 is for Gingerbread (2.3.x). For anything above (CM10.1 is Jelly Bean 4.2.2), you need CWM6.
http://forum.xda-developers.com/showthread.php?t=1894456
Darkshado said:
Got your PM, but this sort of discussion is best kept in public.
Be careful with that HTC-related thread, it's a different device, with a different set of tools and likely a different partitioning method.
Back to basics: have you tried flashing back to stock with Odin and formatting your /data and /cache partitions with the Samsung stock recovery?
Click to expand...
Click to collapse
Hey dude,
Thanks for the reply.
I have tried flashing back to stock (latest from samfirmware) and it still wont let me mount data.
Although its giving me my orignial load screen (my carrier) but still boot loops.
Ive tried look for another stock ROM i can use but alot of the links are down/broke or withdrawn etc.
I note with stock recovery i just can't mount data but after i install CWM 5.0.2.7 ext4 only it cannot format ext to block stl13.
Could this possibly mean that my internal memory has failed or it just needs to be repartitioned?
Will continue to look for another stock rom that can hopefully fix the problem.
You don't care about the errors failing to mount in the stock recovery. It's expected since it isn't set to work with an ext4 partition.
Just run the format operations from the stock recovery.
Most "stock" ROMs released here were made to run on ext4 since performance was that much better and most CWMs built also run ext4, unless explicitly stated to run RFS.
I can't think of any tools to repartition the Gio, otherwise we would have been all over it back in the day to solve the /system space shortage.
Harakhti said:
AFAIK CWM5 is for Gingerbread (2.3.x). For anything above (CM10.1 is Jelly Bean 4.2.2), you need CWM6.
http://forum.xda-developers.com/showthread.php?t=1894456
Click to expand...
Click to collapse
Do you suggest to flash stock via Odin?
And then correct me if im wrong but to get to CM10,1 i go in this order after a stock flash:
1. Install CWM 6.0.3.2
2. run ext formatter
3. install ROM (in this case CM10.1??
Cheers for any help in advance.
Im quite new to Android.. but not new to flashing etc (BIOS, PSP's other devices etc) but this is my first android phone and i didnt like the Phone Carrier custom ROM and network lock. So attempted to try something else. Got Jellybread running fine but decided to have a look around. And now im phone less (well not really using my old nokia n97) but it is sooo painful! lol
I don't think my initial reply could have been much clearer. If you've been flashing these so called "stock" ROMs with CWM, they weren't entirely, completely stock.
1 - Flash original, unmodified Samsung ROM with Odin.
2 - Boot to recovery
3 - Clear user data (or however they named the format operations, I forget)
4 - Reboot
Only if those steps did not work then do we have to start poking around more.
Sent from my SGH-T889V using xda app-developers app
Darkshado said:
I don't think my initial reply could have been much clearer. If you've been flashing these so called "stock" ROMs with CWM, they weren't entirely, completely stock.
1 - Flash original, unmodified Samsung ROM with Odin.
2 - Boot to recovery
3 - Clear user data (or however they named the format operations, I forget)
4 - Reboot
Only if those steps did not work then do we have to start poking around more.
Sent from my SGH-T889V using xda app-developers app
Click to expand...
Click to collapse
Sorry man i had not read your reply before my previous post.
As stated in my previous post, I have flashed 2 stock ROM's from samfirmware via Odin and it passes.
On one of the ROMS (an NZ ROM) it gives me the error: E:format_Volume: rfs format failed on /dev/stl13
On the other ROM (The Aus ROM) it gives me the error: Unable to mount /data
On both im getting boot loop.
If the stock recovery refuses to format the /data and /cache partitions, I'm afraid you'll have to consider warranty service.
Otherwise, try dd'ing the RFS images I've already posted into place, but I'm not sure that this'll work.
Darkshado said:
If the stock recovery refuses to format the /data and /cache partitions, I'm afraid you'll have to consider warranty service.
Otherwise, try dd'ing the RFS images I've already posted into place, but I'm not sure that this'll work.
Click to expand...
Click to collapse
It formats the /cache partitions just not the /data as it cant mount it.
Warranty service? I will have to pay? as i have bought the phone 2nd hand and i dont think its under warranty.
I did see the other post and have downloaded "Samsung GT-S5660M Galaxy Gio - RFS format data and cache partition images to dd back into place"
But i cannot find the post again with the directions. Also when pushing these images from the SD card am i meant to be in stock recovery or RFS CWM?
Cheers Darkshado for all the help so far.
I had the explanation right below that download link here and a more detailed one here.
hmm doesn't look good eh?
Darkshado said:
I had the explanation right below that download link here and a more detailed one here.
Click to expand...
Click to collapse
Could it possibly be a physical hardware failure?
Could be, or some unusual partition table corruption. Problem is, I'm not even sure how the partition table is defined on the phone or if we can alter it...
Try the df command, it should give a listing of partitions on the phone.
Also try ls -l /dev/block/ to list all block devices and see what's there.
Maybe, just maybe parted as well? But by this point your odds aren't in your favor.
Good luck,
Darkshado
you can install a rom after downloading and flashing ext4 formatter.zip
Darkshado said:
Could be, or some unusual partition table corruption. Problem is, I'm not even sure how the partition table is defined on the phone or if we can alter it...
Try the df command, it should give a listing of partitions on the phone.
Also try ls -l /dev/block/ to list all block devices and see what's there.
Maybe, just maybe parted as well? But by this point your odds aren't in your favor.
Good luck,
Darkshado
Click to expand...
Click to collapse
Have been extremely busy with other projects and work lately and haven't had net the past week (so painful!)
but otherwise latest results are attached. Can you make anything of it? Does this look normal?
Cheers again.
Richie
Looks normal at first glance, though I don't have a Gio to compare with.
You could try and dig into how these phones are partitioned exactly and go from there, but you'll probably be on your own since most people who were interested in early MSM7227 devices have moved on.
Unless the underlying memory is defective, it's possible your only option left at this point is to try a JTAG repair.
However, depending on how much you'd be charged for such an operation locally, and taking into consideration the value of your typical used Gio (I've seen them go for 50$CAD in local classifieds)... You're probably better off cutting your losses and getting another phone.
Good luck,
Darkshado
Sent from my SGH-T889V using xda app-developers app
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