Ok, I've been able to keep up with all the flashing of android on hd2 fairly easy since the beginning almost a year ago. This is the only time I've ever really had a hard time figuring it this thing out.
I have flashed nand miui rom with 250mb partition on my eu hd2 through clockwork recovery. I'm trying to try other builds so I do the same method previously by flashing the zip file on my sd card through clockwork but it always get stuck at "unpacking sdext" files.
Is it because each build require different size partitions? Is it something else? Am I missing a step?
This clockwork stuff is pretty confusing...help is appreciated and thank you all in advanced. Much love.
Yes, different builds do require different partition sizes. A GingerBread build can get by on a 150mb (and possibly less) partition, whereas a Desire HD based build will require a 400mb partition.
so how do i go about doing this? because ive tried to partition my card, but it just erases everything clean even with a backup
mini_robot said:
so how do i go about doing this? because ive tried to partition my card, but it just erases everything clean even with a backup
Click to expand...
Click to collapse
The latest cwm partitions are flashed to your NAND and has nothing to do with partitions on your sd card. The sd card partitions are needed to run certain roms on the EU512 device.
To flash a cwm 1.3 partition, you need magldr 1.13, download the partition size you need, boot to usb flasher in magldr and run the daf.exe file from the download. It will wipe data on your phone NAND memory and should have no impact on data on the sd card.
I already have cwm 1.3 and magldr 1.13. I already flashed miui rom. That means I have to use a computer to flash other Roms as well? I thought the point of cwm is so u can flash and switch between roms without a comp?
or does this mean flash through the computer once and then u can switch between roms? sorry if I'm really dumb
You can (as long as you have the same partition size as is needed). I haven't tried it, but I guess you could install the 400mb partition and that should cover all rom types. The only problem is that you then create a larger partition on NAND than may be needed for some roms thereby reducing the internal memory available.
ClydeB1 said:
You can (as long as you have the same partition size as is needed). I haven't tried it, but I guess you could install the 400mb partition and that should cover all rom types. The only problem is that you then create a larger partition on NAND than may be needed for some roms thereby reducing the internal memory available.
Click to expand...
Click to collapse
ahhhhhh. I think I will try that and report back to see how it goes. thanks so much for your help. I will try to do the same for other people once I figure this out
I'd be interested to know the answer. Good luck....
welps. I have tried with no luck. I actually ruined my 8gb SD card trying it and had to get a new one.
Ive been able to flash the 400mb partition and have been able to flash any rom but like it has already been stated it affects the amount of internal memory available, not too bad for me as i have a tmous
Sent from my HTC HD2 using XDA App
mini_robot said:
welps. I have tried with no luck. I actually ruined my 8gb SD card trying it and had to get a new one.
Click to expand...
Click to collapse
Ok, send me your 8Go SD if you think it's dead
NAND and SD are two different things. For your SD, just delete/recreate the partition and it will be new again.
Explanation I post somewhere else (hope it wll help you to understand):
===
I will try to explain.
I assume you have a non-TMOUS device. So your internal storage (let call it NAND) is 512Mo. This is all what your have.
The CWM xxxMo will be what your allocate for your build.
If you allocate 150 (by flashing CWM 150MB) you will have 512-150=362Mo free.
If you use CWM 400... you will have 112Mo free space.
The build you want to use take a little bit more than 100Mo. So why using CWM400 to fill it with only 100Mo???
You have to use the smallest CWM to put your build in it. This will give you the more storage space after installing the build.
Don't think the more "CWM" you will use the more space you will have. It's exacly the opposite.
Hope you understand. Please take into account that the figures I give are appoximation. Don't complain if instead of 362Mo you have only 300... it's more than enough anyway for most of us.
===
So if your first NAND needed a small partition only, you may have to flash again CWM with another partition setting (for ex a 400Mo to fit a desire HD NAND).
Go on the CWM thread to find the version you need (150, 250 and 400 are available). Some thread are also available to modify the config file to make the partition size you want.
By using the 400Mo most build will be flashable... but you will have very little free space and will have to use your SD card (APP2SD or other soft).
I prefer to put everything in NAND for two reasons:
1/ I can remove my SD when I want
2/ I think it's better for battery consumption to not use the SD (but this I don't know, it's just what I think).
i was able to recover the sd card (thanks). anddddd i was able to kind of, sort of, dual boot, two different builds except that one of them has force close issues constantly.
mini_robot said:
i was able to recover the sd card (thanks). anddddd i was able to kind of, sort of, dual boot, two different builds except that one of them has force close issues constantly.
Click to expand...
Click to collapse
What are you talking about? You can't dual boot with clockwork
Sent from my HTC HD2 using XDA App
dung8604 said:
What are you talking about? You can't dual boot with clockwork
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
well its not dual booting. i just kind of re-install each build from clockwork.
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.
If I resize my recovery partition on my HD2, is all data on my SD card lost? and would i have to reflash a new NAND ROM?
Repartitioning your internal memory will not affect the data on your sd card in any way.
Yes, you would have to flash a new ROM, or restore a backup.
so i take it the recovery partition clockwork uses it not on that sd card
which leads to my other question, if my rom requires a 169mb recovery and i use a 400mb recovery, will it work?
yes it will work, but you will waste 231mb of rom space. This is because you will set a system partition of 400mb, and load into it 169mb of files, BUT once the rom is running, all your user data, installed apps, etc get put into different partitions. Nothing will use the extra 231mb in the system partition, so it will be completely wasted and unuseable.
abdalla21 said:
so i take it the recovery partition clockwork uses it not on that sd card
which leads to my other question, if my rom requires a 169mb recovery and i use a 400mb recovery, will it work?
Click to expand...
Click to collapse
is there any sense rom that will work on a 150mb recovery? if so please share the link
Very unlikely. Why not just change the size?
samsamuel said:
Very unlikely. Why not just change the size?
Click to expand...
Click to collapse
bored on my help desk job, was gonna mess with my rom,but if im goin to resize i rather do it at home....lol
think im gonna try the bliss rom, any takes on it?
well you could always flash the rom, play with it, then when you get home, do a cwm backup, change the part size, reflash the rom, then in cwm do an advanced restore and just restore the sd-ext and data partitions. hey presto, system size changed and any settings you configure today will be restored into the new flash.
CAnt comment on the rom, i only use typhoon.
abdalla21 said:
so i take it the recovery partition clockwork uses it not on that sd card
which leads to my other question, if my rom requires a 169mb recovery and i use a 400mb recovery, will it work?
Click to expand...
Click to collapse
CAUTION; the CWM partition make it is for the SD and it WILL ERASE ALL DATA ON SD , for partition internal memory u have to use other tools on a PC (my favorite its HD2 toolkit)
Enviado desde mi HTC HD2
Typhoon has a nice stable sense rom.?
Send me a link
Sent from my HTC HD2 using XDA App
Typhoon is a cm7 rom. Cm7 roms don't have sense.
I CAN highly recommend it, though. I've been on an older version typhoon for over a month now, and the only bug is the occasional failed video capture. Annoying, but doesn't happen often.
"EU users need 150MB CWR system partition and ext2/3/4 partition on sdcard."
any1 can tell me plz how i can do that? what cwr exactly is and what ext 2/3/4 partition is?
thank you very much
achileus11 said:
"EU users need 150MB CWR system partition and ext2/3/4 partition on sdcard."
any1 can tell me plz how i can do that? what cwr exactly is and what ext 2/3/4 partition is?
thank you very much
Click to expand...
Click to collapse
CWR stands for ClockWork Recovery, it's a custom recovery for Android phones. When you download it, there will be a file called flash.config
You have to edit that file to make it flash a 150 Mb system partition to your phone's internal memory.
Or go the much easier route an do a forum search for HD2 NAND Toolkit
It will make things much easier in terms of flashing HSPL, CWM, and pretty much everything else you need to do to get Android running on your HD2
I highly suggest reading the sticky threads in the HD2 NAND Android forum, you're gonna want to know as much as you possibly can before messing around with stuff. You don't want an expensive paperweight, and you don't want to spend extra time correcting a mistake that could've been avoided with a little reading.
Basically you will need:
HSPL
A X.XX.50.XX radio
MAGLDR or clk
CWM with partition layout of correct size for the rom you intend to flash
ext2/3/4 are just a different type of file sytems used by the Linux platform. Use ext3 for your sd card's partition.
You can use CWM to partition your SD card, backup the contents of your card before you partition it.
huggs said:
CWR stands for ClockWork Recovery, it's a custom recovery for Android phones. When you download it, there will be a file called flash.config
You have to edit that file to make it flash a 150 Mb system partition to your phone's internal memory.
Or go the much easier route an do a forum search for HD2 NAND Toolkit
It will make things much easier in terms of flashing HSPL, CWM, and pretty much everything else you need to do to get Android running on your HD2
I highly suggest reading the sticky threads in the HD2 NAND Android forum, you're gonna want to know as much as you possibly can before messing around with stuff. You don't want an expensive paperweight, and you don't want to spend extra time correcting a mistake that could've been avoided with a little reading.
Basically you will need:
HSPL
A X.XX.50.XX radio
MAGLDR or clk
CWM with partition layout of correct size for the rom you intend to flash
ext2/3/4 are just a different type of file sytems used by the Linux platform. Use ext3 for your sd card's partition.
You can use CWM to partition your SD card, backup the contents of your card before you partition it.
Click to expand...
Click to collapse
Any rom you would recommend to me with an easy to follow guide?
I have an Eu htc hd2 btw
I posted this in your other thread but in case you miss it: try this guide. I found it pretty self-explanatory.
The ROM in my sig is pretty old, but it's absolutely the ****.
I don't know for sure if it's still posted here on XDA, if you'd like to try it, I s'pose I could upload it to a filesharing site.
I would definitely recommend CyanogenMod, try this one:
http://forum.xda-developers.com/showthread.php?t=769026
If you like HTC Sense, I'd try a ROM with Sense 2.0, maybe 2.1
Any of the Sense 3.0, 3.5 ROMs still have some bugs need worked out
Hi,
Today i flashed with succes my first android rom Hyperdroid GBX v12, Gingerbread 2.3.3
But i missing sense in this rom so i wish an other rom with sense. I started to partitining my sd card but i get scared and flashed the same rom again.
1. can i flash each nand rom from sd card
2. if not is it possible to undo the partitining of th sd card
I'm so glad that i am windows free
arjanbannie said:
Hi,
Today i flashed with succes my first android rom Hyperdroid GBX v12, Gingerbread 2.3.3
But i missing sense in this rom so i wish an other rom with sense. I started to partitining my sd card but i get scared and flashed the same rom again.
1. can i flash each nand rom from sd card
2. if not is it possible to undo the partitining of th sd card
I'm so glad that i am windows free
Click to expand...
Click to collapse
I didn't' get it! What scares you? You should partition your sd if its needed. Some ROMs, especially Sense, required SD Partition. If you skip this part the rom wouldnt boot. And the instalation is from SD!
First of all, don't be scared flashing a ROM. One of the only ways to brick a HD2 is by flashing the wrong radio.
Partitioning the SD card? Just use minitool partition manager or easeus partition manager (both work fine) and then create your Ext3 partition there. Just make sure you have the files on your SD card backed up to your PC as when you're partitioning, it'll need to format the card.
EDIT: to answer your questions...
1) it's only possible to have one android rom installed at one particular time.
2) it is possible to wipe the partition on your sd card to make it full capacity again. Search for 'Panasonic SD Formatter' and that works just fine.
Sent from my GT-I9100 using XDA App
both of you thanks a lot for the quick reaction.
What scares me is that when i put a new rom at my sd card and flash it, is that enough or do i have to delete the old first???
And second, does it mather what kind of rom i flash there are to much to choose i think. i have a european model so i shouldnt choose the tmous models are all other roms save to flash?
What the heck i did it!!!!
No thinking just doing!!!!
but now its hanging on the start up
so back to the first flash who worked is there anyone who knows what i am doing wrong????
You should have enough space to have more than one rom on your SD card. Why it's looping on boot is because you have the wrong clockwork partition. In each rom it should be outlined as to what size you need the partition, then just reflash the right size clockwork from magldr/cLK.
Sent from my GT-I9100 using XDA App
Skellyyy said:
You should have enough space to have more than one rom on your SD card. Why it's looping on boot is because you have the wrong clockwork partition. In each rom it should be outlined as to what size you need the partition, then just reflash the right size clockwork from magldr/cLK.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
do i need the panasonic sd formatter before doing this?
Nope you don't need to do anything to the SD card partition. It's the internal memory you're partitioning to make room for your ROM. Can't remember exactly but you can just edit one of the files that you've got in your clockwork folder to change the partition size or just go to the clockwork thread and download the partition size clockwork you need.
Sent from my GT-I9100 using XDA App
Like everyone here, I have the famous HTC Leo. A friend installed Android on NAND, the 2.3.4 with the mod-HyperDroid CM7-v2.1.0.
This is a great device, but the more I use it, the more I have less internal memory.
At first, I installed a lot of applications, I was full of things and I ended up filling the internal memory. I moved the more applications possible on the SD card, but the internal memory ended up being full. So I uninstalled applications not too useful, and applications more useful, clean caches, remove data, but it is still too small. My system tells me that I only have 217.3 Mb total internal memory and while I hardly more than application system installed, I only have 21.3 MB available. Now, I know that this model has double.
I do not understand: what is this devilry? Where is my memory? How can I resume normal operation until all the memory is gone and my phone becomes unusable?
I can't be the only one to whom it happens, right?
only the data partition counts as internal memory, the rest is taken by the system, boot and recovery partitions, so your200+ sounds about right.
read up on creating an ext partition on your sd card, and either flash a rom that supports it already, or add a script to your current rom, , then, instead of using the data partition on the nand the system will use the sd-ext partition as if it were nand. (This is NOT the same as choosing 'move to sd' in the apps config screens, that moves it to the fat partition, and some apps wont work from there, , , all apps will work from the ext partition, and faster than the fat partition.)
There are two sets of scripts, some move the whole data partition to ext, meaning of course you are not using the 200+ mb on the nand, so for me i prefer the scripts that move only the apps to the ext partition, and keeps your actual data (txts, contacts, stuff like that) on the regular nand data partition, thus spreading the useage.
look out for keywords like 'app2sd+' 'data2ext' 'dataonext', , stuff like that when you're searching.
samsamuel said:
only the data partition counts as internal memory, the rest is taken by the system, boot and recovery partitions, so your200+ sounds about right.
read up on creating an ext partition on your sd card, and either flash a rom that supports it already, or add a script to your current rom, , then, instead of using the data partition on the nand the system will use the sd-ext partition as if it were nand. (This is NOT the same as choosing 'move to sd' in the apps config screens, that moves it to the fat partition, and some apps wont work from there, , , all apps will work from the ext partition, and faster than the fat partition.)
There are two sets of scripts, some move the whole data partition to ext, meaning of course you are not using the 200+ mb on the nand, so for me i prefer the scripts that move only the apps to the ext partition, and keeps your actual data (txts, contacts, stuff like that) on the regular nand data partition, thus spreading the useage.
look out for keywords like 'app2sd+' 'data2ext' 'dataonext', , stuff like that when you're searching.
Click to expand...
Click to collapse
Excellent advice, but I think you forgot to mention this
Late I think me brain is playing tricks on me...:cyclops:
shanman-2 said:
Excellent advice, but I think you forgot to mention this
Click to expand...
Click to collapse
so, pretty much exactly what i described, then....
shanman-2 said:
Excellent advice, but I think you forgot to mention this
Late I think me brain is playing tricks on me...:cyclops:
Click to expand...
Click to collapse
So, I don't really need to use this. I just can install a new ROM on my NAND after making extending place on my SD for the 'dataonext', can't I?
I have to choose a dataonext ROM (with french version) and make new partition on my CD card. I'm saving all the SD card data's just now (with luckyBackup, because I'm on ubuntu PC).
My problem is find a good ROM for my needs. So, I have HSPL 2.0.8 and MAGLDR. How can I find the rom radio number? I need this information to choose the good ROM. Any advices about good ROM for my needs?
r no need to change the radio,,, if magldr works then the radio is fine.
samsamuel said:
r no need to change the radio,,, if magldr works then the radio is fine.
Click to expand...
Click to collapse
I bought a new 16 GB SD card to try the method of post 1843062. I am trying to format as it should, and tonight or tomorrow, I'm trying to see if I can install the script without too much risk, I am not a very experienced user of ROM for HD2 and, in addition, as I'm 100% Linux Ubuntu, I saw that many procedures are more complicated or impossible to run from a Linux desktop.
Thank you for all your help and I'll let you know.
I need to understand.
I have a EU HD2 with HyperDroid CM7 installed on it.
Like many people here, my memory became too small over time. So I look for a solution and I was guided to this thread. While speaking, I read everything I could understand (and frankly there really is too much to read and understand, here ) and I ended up deciding to adopt the solution Kokotas.
So I bought a new SD card (16GB class 10 Duracell - I know, Duracell is a brand of batteries ...) and I formatted properly Gparted as shown, with one primary partition of 12 GB fat32 I named /données (French for datas) and a second primary partition 4 GB Ext4 I named /data.
Then I primed to install the script Kokotas (but I have not yet done so, this is the trick!) And there: surprise!
I suddenly 4 times more free memory internally (from 20 MB to 80 MB), but it is still the same overall size!
I wonder how it is done, because it's been months that I want to release the NAND memory, I deleted almost all my applications downloaded without great effect and there, before installing the solution Kokotas, hop, I have the place!
I run Nautilus on my HD2 connected via USB and what do I see? in the partition /data in ext4, records were Cres /app /app-private and /dalvik-cache.
What does that mean? My ROM can do one DATAtoEXT 2011 alone, when she sees a partition SD / data?
Do I install the script Kokotas or it is not worth it?
Do I flash a new ROM (I thought MIUI-MIX_3.3.1, but I'm not sure it's a good idea) without risk, in short I need to understand what happens with my phone.
Thank you.
(Sorry for my english : this is the fault of Google translation )
You might also consider just running an SD build instead of NAND. You can get a 2GB "internal storage" system.img and you don't risk getting bad blocks on nand by constantly flashing things. In my use of both I didn't really see any great speed increase or advantage in using NAND other than boot-up time is a bit less, but does that really matter?
Just another thought on this.
orangekid said:
You might also consider just running an SD build instead of NAND. You can get a 2GB "internal storage" system.img and you don't risk getting bad blocks on nand by constantly flashing things. In my use of both I didn't really see any great speed increase or advantage in using NAND other than boot-up time is a bit less, but does that really matter?
Just another thought on this.
Click to expand...
Click to collapse
I thought NAND is better for battery's management...
Monolecte said:
I thought NAND is better for battery's management...
Click to expand...
Click to collapse
I didn't see any great battery improvement with NAND.
ROM flashing don't work
I tried to flash MIUI-MIX_3.3.1, but, it wasn't working. I think this is because Resurection needs this specific table of partition and I don't how can I modify this table of partition. CMW had a partition tool? How can I do?
Monolecte said:
I tried to flash MIUI-MIX_3.3.1, but, it wasn't working. I think this is because Resurection needs this specific table of partition and I don't how can I modify this table of partition. CMW had a partition tool? How can I do?
Click to expand...
Click to collapse
use the nand toolkit
samsamuel said:
use the nand toolkit
Click to expand...
Click to collapse
With an Ubuntu PC?
After miles of thread reading here, I won against the machine!
I have something like a new phone.
Thank you everybody.
If I can do it, anybody can do it!
ubuntu or windows will be fine.
The NAND Toolkit is a Windows software... so...