I recently flashed the new 4EXT Mod of ClockworkMod Recovery. The 4EXT Recovery is based off of Koush's CWM Recovery but offers additional power options, one of which is the ability to show the file system format your partitions are formatted in. To my surprise my system was formatted in the Ext 4 format and my data and cache partitions were formatted in Ext 3. The new 4EXT Recovery offers the option to convert the format without deleting any of the data. Your ROM will stay intact after the conversion. I selected that option and changed my data and cache partitions to ext 4 to match my system, rebooted, and notice quite an improvement in speed and smoothness in my current CM7 Nightly. After looking into it further I found out that the SuperwipeG2 that many of us have been flashing is formatting our partitions in the Ext 3 format. The reason only my system was formatted in ext 4 is because I used ClockworkMod Recovery the last time I did a full wipe to first flash the Superwipe, and then I immediately formatted system again with ClockworkMod Recovery. If you've used SuperwipeG2 to do a wipe, more than likely your system, data, and cache partitions are now Ext 3. You might want to check with your ROM developer to see if your ROM will run on the Ext 4 format. If its a CM7 based ROM, it will.
You can find more information about the Ext 4 format here.
Tsubus has since modified SuperwipeG2 so that it now formats the partitions into ext 4 when you flash it. I've used it and it also includes the EFS wipe. You can find it here. As I said, if there is no reason to wipe right now the new 4EXT Recovery can convert your partitions if you choose if they are in currently Ext 3. At the very least you can see what format they're currently in with 4EXT. I highly recommend it. You can always flash back to CWM Recovery if and when you choose. The partitions will remain Ext 4 once you choose to convert.
UPDATE: Several users have reported that checking partition information with Terminal Emulator is not reliable.
i just caught this issue this morning as well, all my partitions are in ext3, going to convert today. thanks for this post and the links to the new superwipe! +1
Sent from my HTC Vision using xda premium
Thanks for pointing this out. I have all of mine in ext3 right now and plan on converting to ext4 here in a minute.
if ive never used superwipe my partitions are still in EXT4?
nonione said:
if ive never used superwipe my partitions are still in EXT4?
Click to expand...
Click to collapse
Probably yes, but it wouldn't hurt to check. The new 4EXT Recovery will display your current partition status. Then you'll know for sure.
Sent from my HTC Vision using xda premium
So could someone clarify my understanding of this? If we are currently using ext3 we have 2 options to move to ex4 and keep CWM:
1) keep CWM, use the new superwipe+ext4, flash cm7
2) switch to 4ext recovery, convert fs to ext4, go back to CWM recovery
Alternatively, I would consider switching to 4EXT recovery permanently, but I am a bit reluctant to ditch CWM just because I'm so used to it. Is it worth the switch?
c00ller said:
So could someone clarify my understanding of this? If we are currently using ext3 we have 2 options to move to ex4 and keep CWM:
1) keep CWM, use the new superwipe+ext4, flash cm7
2) switch to 4ext recovery, convert fs to ext4, go back to CWM recovery
Alternatively, I would consider switching to 4EXT recovery permanently, but I am a bit reluctant to ditch CWM just because I'm so used to it. Is it worth the switch?
Click to expand...
Click to collapse
ClockworkMod is using the Ext 4 format. Its just that currently there is no way to tell what format your partitions are formatted in with CWM. If you flash the SuperWipeG2+ext4 from tsubus with CWM and don't ever use the original Superwipe and don't restore a backup, you're all set and done. BUT, if you restore a backup created by CWM that was partitioned at the time you created the backup in Ext 3, you'll be back to Ext 3 again. IE you've got to scrap all your old backups....all of us do if we want to stay with Ext 4. So, if you're willing to do a full wipe with the new SuperWipeG2+ext4 and CWM, you're good to go.
edit: yes to your number two. You can convert your Ext 3 partitions to Ext 4 with the new 4EXT Recovery and then go back to CWM. As I said above, after you do this you need to get rid of the original Superwipe and not restore old backups made in the Ext 3 format.
Sent from my HTC Vision using xda premium
I think I've just made the switch to 4EXT, it was very painless and I like the features of the recovery. Now I'm wondering, with the 4EXT recovery, do we still need the superwipeg2 zips (including the new, ext4 modified one)? Also, is there a thread with discussion about the SuperWipeG2+ext4.zip (i.e., where did you find the link to download it)?
c00ller said:
I think I've just made the switch to 4EXT, it was very painless and I like the features of the recovery. Now I'm wondering, with the 4EXT recovery, do we still need the superwipeg2 zips (including the new, ext4 modified one)? Also, is there a thread with discussion about the SuperWipeG2+ext4.zip (i.e., where did you find the link to download it)?
Click to expand...
Click to collapse
Use the new Superwipe just like you did and when you needed the old one. Tsubus modified it to format the partitions in ext 4. You can find his thread in the Development section. Its the CM7 ILWT thread. He modified the Superwipe right befor he went away for the weekend. The original link is in the OP of that thread. Be sure and hit his "thanks" button.
Sent from my HTC Vision using xda premium
Thanks very much for the info and links, Ed. I will make the switch and give you a proper 'thanks' later tonight.
Sent from my HTC Vision using XDA App
typing the following in terminal
Code:
mount
will tell you what filesystem types like ext2 ext3 ext4 etc, so u dont really need the other recovery to check if you're using ext3.
Code:
/dev/block/mmcblk0p25 [B]on /system type ext4 [/B](ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p26 [B]on /data type ext4 [/B](rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p27 [B]on /cache type ext4 [/B](rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p28 [B]on /devlog type ext4 [/B](rw,nosuid,nodev,noatime,barrier=1,data=ordered)
Still, I never even noticed that it was formatted as ext3 until i saw your post. Used the new superwipe and a fresh cm7 nightly. Everything flies now! Thanks for noticing the issue
Just checked via terminal emulator and mine are all in EXT4. Never used Superwipe before so I guess that's why.
sephiroth1439 said:
Still, I never even noticed that it was formatted as ext3 until i saw your post. Used the new superwipe and a fresh cm7 nightly. Everything flies now! Thanks for noticing the issue
Click to expand...
Click to collapse
Glad it worked out for you.
sephiroth1439 said:
typing the following in terminal
Code:
mount
will tell you what filesystem types like ext2 ext3 ext4 etc, so u dont really need the other recovery to check if you're using ext3.
Click to expand...
Click to collapse
martonikaj said:
Just checked via terminal emulator and mine are all in EXT4. Never used Superwipe before so I guess that's why.
Click to expand...
Click to collapse
WARNING: Ptesmoke and Ditamae have reported that this method wasn't accurate for them. Results reported by terminal emulator didn't match the actual file system ext's when they booted into 4EXT Recovery. After converting they have both posted that they noticed an improvement in performance.
Strange... so I checked thru Terminal and all partitions were EXT4, but after flashing the 4EXT Recovery and booting into recovery I discovered that data and cache were in fact EXT3. Hmm... I'm converting now, at any rate. Thanks again, Ed.
Just to clarify...
So the original Superwipe changes our partitions to ext3, and the new Superwipe up above changes/keeps it at ext4.
If that is correct it seems like we should remove the other instances of the original Superwipe in the forum and switch everyone over to the new Superwipe. What does reformatting via CWM change the file system to?
Nospin said:
Just to clarify...
So the original Superwipe changes our partitions to ext3, and the new Superwipe up above changes/keeps it at ext4.
If that is correct it seems like we should remove the other instances of the original Superwipe in the forum and switch everyone over to the new Superwipe. What does reformatting via CWM change the file system to?
Click to expand...
Click to collapse
Yes, the original Superwipe changes the partitions to Ext 3. I'm not sure if there are other ROMs out there doing the same thing. It depends on the scripting. Many ROMs are scripted to format the partitions first when you flash them. If users reading this thread take the information and post it to their ROM thread in the Development section of the forum that would help to get the news out to check to see if their partitions are formatted correctly.
Thanks OP! I used (my new friend) 4EXT Recovery and converted my data and cash partitions to ext4, got rid of my old SuperWipe and Dow loaded the new Superwipe.
CM7 does indeed seem smoother, and overall a bit faster.
Big thanks for the heads up!
Sent from my HTC Vision using xda premium
Also noticed the "eccentricity" of my /data and /cache being ext3, conversion to /ext4 was painless and the phone does seem to be running more smoothly.
(Then again, I utterly love this recovery--so powerful, and yet so simple to use )
Aaaand interestingly, at least if ROM Manager is any guide, they've finally pulled the 5.0.0.x "Seppuku Builds" of CWM. Which is nice, but 4EXT has sold me
I have a question that maybe someone in this thread could answer. As I said previously, I flashed the 4EXT Recovery last night and changed my data and cache from ext3 to ext4. Afterward, I noticed that my internal memory usage had decreased by approximately 70Mbs. Is this a result of less fragmentation? I'm assuming it's just a benefit of the way fourth extended filesystem works. Can anyone confirm this? Thanks in advance.
Related
Hi All,
I need real help with ClockworkMod Recovery. I have been installing Android on HD2 using storage card (haret.exe) method. Then I moved to NAND without any problems.
But I am not able to understand ClockworkMod Recovery at all. I looked at lots of threads and also the main thread for ClockworkMod Recovery. I know how to install it. I have installed it on my phone. But for some reason I was stuck in the loop after installing the ROM {[22 JAN] -=MDJ's CyanogenMod 7 v. 2.6 [A2SD+][GRH78C][RMNET][Kernel: MDJ S10.4 OC]}. I did exactly same as the video tutorial says. My radios and HSPL is fine. Coz I am able to use the same ROM in NAND mode. But still in ClockworkMod Recovery mode the phone kept restarting and never got to the main screen.
I also do not know what ext2, ext3, ext4 partitions are. Do I need to make them before installing the ROM? Also on the main thread for ClockworkMod Recovery, it has 3 partition files. 250MB, 350MB and 450MB. I do not know what that is. Which one to use for which ROM and what are the differences between them?
What is the use of ClockworkMod Recovery if I have to flash this partitions every time I install new ROM?
Also can someone tell me what backing up the ROM means? Does it mean I can back up my current one and flash new one, and if I do not like the new one I can restore the old one in the same state (with my APPS and SETTINGS)?
Please please help me with ClockworkMod Recovery fundamentals. I would really appreciate it.
One more thing, I would not post a question if I haven't looked around enough for answers. As you can see I have been doing this from months, but only asked one question before and this is the second one. So please do not take me for someone who does not look around for answers. I do, its just that I did not find anything real good to explain me from the bottom. So please someone help me out.
Thanks in advance.
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Digital Outcast said:
EXT partitions can be thought of as extended partitions on your SD card. They are used to "extend" your storage capacity. Some ROMS place some of the ROM files on the SD-EXT partition. This is done particularly for the EU HD2 where it has only half the storage on-board that the TMOUS HD2 does. If you are using a ROM that requires one you do have to create the partitions before installing/flashing the ROM.
The three different flash.cfg files on the CWM thread are files used to instruct DFT how to re-partition your on-board storage (NAND). There are several partitions, up to 16 at the moment. Some ROM's use 4 partitions, some use 6 or more. Typically, non-CWM ROM's use only 4 partitions (boot, system, data, cache), whereas CWM ROM's use those same ones as well as a miscellaneous and recovery partition.
The main reason for the different files is that some ROM's use more space for the system partition. The different flash.cfg files just simply allocate more or less space to the system partition.
You don't technically have to flash new partitions every time you flash a new ROM. As long as you know how to modify the ROM to work with your current partition setup it will work. Or, get ROM's that use the same type of partition layouts. Since the release of CWM, more ROM's are becoming available for installation via the ZIP deployment method in CWM, which means they ALL use the same partition (with exception of the system partition size) setup.
If you have a TMOUS HD2 with plenty of onboard storage it's easier to just create a larger system partition and never have to worry about repartitioning. That's what I did. I have a 450 MB system partition and every time I deploy a new CWM ZIP ROM I don't have to repartition anything.
You nailed it on the head about backing up via CWM. It backs up all your partitions (boot, system, cache, sd-ext, data, etc) and saves them to your SD card. That way you can flash a new ROM or do a hard reset. Then later if you want you can do a full restore and be exactly where you left off before doing so. That is, if you flash a ROM that has the same partition layout. If you flash a ROM with a different partition layout, the restore may or may not work until you repartition the same as the original ROM was when you flashed it.
The only issue with all this is that since there isn't a set standard yet for ROM's and their partition layouts any ROM chef can define their own partition scheme which can make for a hassle when trying different ROM's. I expect that at some point there will be a standard set of partitions that will be used between all different chefs to make things easier. CWM ROM deployments and updates are definitely the future of this and how all native Android devices are handled. I imagine that will become the case down the road for the HD2 as well.
Hopefully that clears it up for you a bit. Sorry about writing a novel...
Click to expand...
Click to collapse
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
jalshah05 said:
Amazing explanation. Thanks a lottt man. Just one more question, I have TMOUS HD2 abd I did the same thing as you said. 450MB of partition. And then tried to install the MDJ's CM7 ROM. I got the message saying the ROM is successfully installed. and then I rebooted my phone. But it kept rebooting itself. Any particular reason you know of?
Click to expand...
Click to collapse
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
To be very frank I did not understand what you just told me sir. Only thing I can tell for sure is I downloaded the .zip file from the thread at http://forum.xda-developers.com/showthread.php?t=877777 . And I do not know what logcat is. I am sure you must be thinking that I am an idiot. Forgive me for my ignorance.
Google is your friend!
I'm a better one: http://wiki.cyanogenmod.com/index.php?title=Logcat
Edit: very interesting read by the way, Digital Outcast. Much appreciated!
Digital Outcast said:
Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?
Click to expand...
Click to collapse
Thanks a lott Digital Outcast for this amazing explanation. I hope I can get the Recovery mode working. I will try some different roms and see what can be done. meanwhile if you get chance please explain me your response "Is this using the 400 MB flash.cfg file from the CWM thread? The reason I ask is that I checked that flash.cfg file and the boot partition is flagged as the bootable partition. I'm not familiar with the CM7 ROM from MDJ, but is it set to deploy via CWM with a boot folder in the ZIP file?
Also, have you run logcat (if you're familiar with that) while the issue is happening to see what is going on?"
Thanks a lott once again.
So, if I have a ROM (CMYLXGO's Stock Desire) w/ 425 MB system partition and I back it up with CWM , then install another ROM with 150MB system partition (installing the 150MB partition prior to install of course), do I need to repartition back to the 425MB prior to restoring the 425MB partitioned backup?
Common sense would tell me yes, BUT, I figured I would ask just in case I am wrong!
JWhipple said:
So, if I have a ROM (CMYLXGO's Stock Desire) w/ 425 MB system partition and I back it up with CWM , then install another ROM with 150MB system partition (installing the 150MB partition prior to install of course), do I need to repartition back to the 425MB prior to restoring the 425MB partitioned backup?
Common sense would tell me yes, BUT, I figured I would ask just in case I am wrong!
Click to expand...
Click to collapse
Yes, you definitely need to re-partition.
Thank you - thats just what I needed to know!
JWhipple said:
Thank you - thats just what I needed to know!
Click to expand...
Click to collapse
glad I could help....
What will be the problem if i dont perform repartition?
I had been wondering if a nandroid backup would restore old partition sizes, since it backs up everything, but yeah i guess it makes sense that it can't change the size of the recovery partition, since that's what cwm is running from at the time of backup/restore. But does nandroid restore system and cache partition sizes?
Sent from my HTC HD2 using XDA App
huggs said:
I had been wondering if a nandroid backup would restore old partition sizes, since it backs up everything, but yeah i guess it makes sense that it can't change the size of the recovery partition, since that's what cwm is running from at the time of backup/restore. But does nandroid restore system and cache partition sizes?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
No, the restore just loads the partition contents into the partition, it doesn't adjust the sizes, or recreate them,, just loads the backed up contents into it.
Hi,
I recently made the jump to CM7.1 KANG Oct24th, with ClockworkMod 5.0.2.0. All seems to be working very well.
But then I tried to do a ClockworkMod backup, just like I've always done. It worked through all the partitions, until sd-ext. I then get the following error:
"Could not mount sd-ext. sd-ext backup may not be supported on this device. Skipping backup of sd-ext" followed by the usual "Generating md5 sum..."
On another forum there was a mention that this error is normal. Does everyone get this error?
I think I created the SDCard partitions using ClockworkMod, so I have a 1024MB Ext4. It is my understanding that Ext4 is supported. It must be, as (I think) I used Clockwork to create the partition. I'm not certain about that, as I was also experimenting with GParted to create partitions. But had the same problem.
I am using Link2SD to move some apps to sd-card, so without sd-ext partition, the backup is incomplete!
Anyone seen this? Any ideas what might be wrong? Or how to fix it?
Thanks.
clockworkmod doesn't support ext4 on the blade. ext3 works.
Hate to resurrect an old thread but is this still the case I'm having the same problem?
Looks like I'm going back to 4EXT. After installing the latest touch version of Clockwork mod I got this message also during backup. This is fine if you have no problems on your next ROM but what if you have problem with the next ROM you chose. Doing a full wipe will include reformating EXT4 partition. That means since Clockwork mod didn't backup your EXT4 you have no way of getting all the files you want from your previous ROM. I also thought of changing my partition from EXT4 to EXT3 but besides the fact that I will have to move all my files to my PC then transfer again I read somewhere that EXT3 is not as efficient as EXT4.
xrookie24 said:
Looks like I'm going back to 4EXT. After installing the latest touch version of Clockwork mod I got this message also during backup. This is fine if you have no problems on your next ROM but what if you have problem with the next ROM you chose. Doing a full wipe will include reformating EXT4 partition. That means since Clockwork mod didn't backup your EXT4 you have no way of getting all the files you want from your previous ROM. I also thought of changing my partition from EXT4 to EXT3 but besides the fact that I will have to move all my files to my PC then transfer again I read somewhere that EXT3 is not as efficient as EXT4.
Click to expand...
Click to collapse
My version of CWM touch (the only one touch version there is afaik) does support ext4, both 6.0.1.1 stable and 6.0.1.2 experimental.
You can find it here: http://forum.xda-developers.com/showthread.php?t=1835279
You might have been using my older testing version which had a problem with some ext4 partitions (notably ext4 partitions with special attributes).
Jinxxed said:
My version of CWM touch (the only one touch version there is afaik) does support ext4, both 6.0.1.1 stable and 6.0.1.2 experimental.
You can find it here: http://forum.xda-developers.com/showthread.php?t=1835279
You might have been using my older testing version which had a problem with some ext4 partitions (notably ext4 partitions with special attributes).
Click to expand...
Click to collapse
Sorry I didn't notice the device name. I'm using HTC Desire. My latest version of HTC Desire doesn't support EXT4 anyways. It's Off-Topic here. NVM. Thanks.
Hi
I recently installed a Sense 3.x ROM from the Sensation XL Android 2.3.5 and I got only 9MB of free space. I have an initrd-patcher for ICS and JB, but I doubt that it will work on older versions of android.
Is there a way to make android 2.3.5 use the EXT4 partition on the SD-card?
Yes, you have to flash an a2sd or DataOnExt script after first boot/flashing the rom immediately. Of course, while having an ext partition created beforehand.
Marvlesz said:
Yes, you have to flash an a2sd or DataOnExt script after first boot/flashing the rom immediately. Of course, while having an ext partition created beforehand.
Click to expand...
Click to collapse
Thanks for the reply. Can you recommend a good script for doing this?
I'd suggest this one, but there's a whole lot of other ones. So if this one doesn't work well or you don't like it, don't come here asking for another one. Instead, go out there and look for the one that you like.
Marvlesz said:
I'd suggest this one, but there's a whole lot of other ones. So if this one doesn't work well or you don't like it, don't come here asking for another one. Instead, go out there and look for the one that you like.
Click to expand...
Click to collapse
and just a little clue to help out a little bit
its in the second post of the thread that Marvlesz link to
I used initrd_patcher_v2 on Gingerbread 2.3.7 and it's worked fine. So it should work on GB 2.3.5 as well. Remember to make an EXT4 partition on your SD before any installation, via recovery, and remove any script like a2sd from zip ROM.
eclyptos said:
I used initrd_patcher_v2 on Gingerbread 2.3.7 and it's worked fine. So it should work on GB 2.3.5 as well. Remember to make an EXT4 partition on your SD before any installation, via recovery, and remove any script like a2sd from zip ROM.
Click to expand...
Click to collapse
I tried to search for initrd_patcher_v2 and found this one: http://forum.xda-developers.com/showthread.php?p=36049396
I tried running it on my system, but freezes up just before boot-animation.
I use the SENSATION XL ROM V 3.0 STOCK from here: http://forum.xda-developers.com/showthread.php?t=1316632&highlight=sensation+all+in+one
I can't seem to find any a2sd-scripts in the ROM zip, but there's a sd-ext folder inside the ZIP.
CTSRP said:
I tried to search for initrd_patcher_v2 and found this one: http://forum.xda-developers.com/showthread.php?p=36049396
I tried running it on my system, but freezes up just before boot-animation.
I use the SENSATION XL ROM V 3.0 STOCK from here: http://forum.xda-developers.com/showthread.php?t=1316632&highlight=sensation+all+in+one
I can't seem to find any a2sd-scripts in the ROM zip, but there's a sd-ext folder inside the ZIP.
Click to expand...
Click to collapse
Can you do a fresh installation again of this ROM or you try to keep all you data which you using right now?
Sv: Enabling storage of EXT4 on SD-card
I tried from a fresh install, before booting the first time, and also from an aleady configured installation.
CTSRP said:
I tried from a fresh install, before booting the first time, and also from an aleady configured installation.
Click to expand...
Click to collapse
You don't understand, I mean can you format you phone and install this rom again with my advices?
Did you made an EXT4 partition of 1GB or more, with Mini Tool (free), on your sd BEFORE fresh installation of this ROM?
I checked your ROM and the script (apps2sd) is already in that ROM so you probably make a wrong Installation.
Sv: Enabling storage of EXT4 on SD-card
I do understand what you say. I made a task29, clk repartition and recovery from hd2toolkit. Under installation the installer asks if I have 1024mb us model or 512mb EU version. I selected the EU version, as this is the one I have. The only question it asks me is if I have magldr or clk.
After that it returns to clk recovery and I press reboot now. I have created the ext4 partition before I even tried installing android the very first time.
If you want, I can perform a new installation with a video recording to document the process
CTSRP said:
I do understand what you say. I made a task29, clk repartition and recovery from hd2toolkit. Under installation the installer asks if I have 1024mb us model or 512mb EU version. I selected the EU version, as this is the one I have. The only question it asks me is if I have magldr or clk.
After that it returns to clk recovery and I press reboot now. I have created the ext4 partition before I even tried installing android the very first time.
If you want, I can perform a new installation with a video recording to document the process
Click to expand...
Click to collapse
Do not use CLK or HD2toolkit this time.
I will recommend to do in this way, before touch your phone format your SD with GUIFORMAT (look here on XDA for it) in FAT32 normal mode (no quick), after format the SD use Mini Tool and make a ext4 partition of 2gb (2048mb) at the end of the SD, so when you look at the partition the ext partition have to be at the right side of you. Put inside the SD the zip of Sensation XL 3.0 only, do not do anything else with your sd.
Format your Phone with Task29, reboot in Bootloader,
Flash MAGLDR 1.13 for HD2,
From MAGLDR 1.13 via USB Flasher flash the Recovery Touch Beta 8, (I provided you the Recovery ready for you, unzip and flash)
Reboot in MAGLDR,
put the SD into the Phone,
run Recovery,
Do a wipe data and wipe cache partition and wipe dalvick cache,
Install from sd the zip via recovery,
In Aroma do not select any option if you don't know anything about it, the installation will recognize the EXT4 partition automatically and you ready to GO, GO, GO.
Let me know.
Hi,
Short / long story:
I have long time unused HTC HD2.
With Android (NexusHD2-KitKat-CM11.0_V4.5.zip is the file which I found in backup, so I assume this is what I install - sorry, it was long time ago.
Some time ago I need microSD card so I took it from my HD2, I did backup only windows FAT32 partition.
Now, I need to run my HD2 , I have install microSD 2 GB (800 MB FAT32 + 1GB Ext4) but is not working correctly.
It starting I can install Teamviewer, but when I need to install HTC module for teamviewer it's telling me that is not enough storage.
Quite often is restarting and after restart not keeping any settings (wi-fi) app installed (teamviewer) it's resetting each time to factory settings.
In Settings - Storage shows 'Total space' - Available 0.00 bytes
I did what is instructed on this webpage but it didn't help http://android.stackexchange.com/qu...mory-in-android-nand-roms-cannot-install-apps
Can anybody advise me which is the easiest way to make my HD2 working properly? Means have enough memory to do anything.
The purpose of restoring my HD2 is working as a router, tethering machine. I need to share internet from mobile network for smart TV and Tablet over wi-fi. It will be unattended so I need remote control access (team viewer host).
I'm open for a suggestion of changing the ROM if there is something reasonable easy and described (as I'm not big ROM expert). i've seen a ROM list for HD2, is too long.
Thanks in advance for your help.
it sounds like you are missing a data partition, perhaps the sdcard you used before had an ext4 partition which your new one does not have. Use recovery, in nand, to create an ext4 partition, then boot into rom, might work.
Robbie P said:
it sounds like you are missing a data partition, perhaps the sdcard you used before had an ext4 partition which your new one does not have. Use recovery, in nand, to create an ext4 partition, then boot into rom, might work.
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I did Ext4 by MiniTool Partition under Windows primarily.
And later in recovery, I have setup 1024MB and swap = 0 M.
It didn't help.
Should I mount it or so?
Update:
I have a look in log in nand - recovery and it's says that my second partition is Ext3 not Ext4.
And there is no way to change it.
What is your nand recovery? version?
Clk or magldr?
The recovery might say ext3 when it means ext4, but it does not seem right.
Robbie P said:
What is your nand recovery? version?
Clk or magldr?
The recovery might say ext3 when it means ext4, but it does not seem right.
Click to expand...
Click to collapse
It says on the top bar screen 'CWM-based on Recovery v5.0.2.6' but was install with ROM so should be fine.
try using the recovery to format the ext partition to ext2 or 3 then use it again to ext4
Robbie P said:
try using the recovery to format the ext partition to ext2 or 3 then use it again to ext4
Click to expand...
Click to collapse
As I said, I have created and formatted partitions under windows FAT32 & Ext4 and then under recovery, there was no choice of the file system file, I can only choose the size. And it was formatted to Ext3 - log saying.
badzi0r said:
As I said, I have created and formatted partitions under windows FAT32 & Ext4 and then under recovery, there was no choice of the file system file, I can only choose the size. And it was formatted to Ext3 - log saying.
Click to expand...
Click to collapse
Here's the solution:
http://forum.xda-developers.com/showpost.php?p=38956440&postcount=4
Thank you