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.
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.
hey can anybody guide me to the right way of partitioning my hd2 nand(tmobile) so i can install dl desire z from dandiest and get faster smoother working rom....plus 2 see 3000 on my quadrant scores.......i already have desire z 4.1 but its not as smooth as i thought it would be....i heard running the rom from a partition would increase read and write speeds...so before i install 4.2 i would like to know how to partition my nand to run the rom off of it....thank u.
Have you tried the video guide posted by locn?
http://forum.xda-developers.com/showpost.php?p=11656790&postcount=3943
there's also a lot of partition tutorials all over that thread, xda & the web, I could link them for you, but that would deprive you of all the joy you will get when you actually find such info for yourself.
Good luck
Kam
Yeah I found partition videos and tutorials...a lot ...but they were all for partitioning memory cards not nand memory ..
Sent from my DL DesireZ v4.1 using XDA App
trinfinate said:
Yeah I found partition videos and tutorials...a lot ...but they were all for partitioning memory cards not nand memory ..
Sent from my DL DesireZ v4.1 using XDA App
Click to expand...
Click to collapse
Exactly. I'm running HyperDroidGBX and it says my internal storage is only 729MB, out of 1024MB. So just roughly 256MB Of the nand is being used for the system/data/cache partitions. What I want to do is resize all my nand partitions to allow for a data partition of atleast 900MB of internal storage and still have sufficiently sized system/cache partitions as necessary. What are the sizes of the partitions by standard? How do we use Android SDK and AVD "Andriod Virtural Device" on a Windows desktop to adjust the partition sizes?
THANKS!
BTW - It's called the mtd partitions. So look up how to resize mtd partitions android sdk avd.
Look in the folder where your cwm instal files are.one is called flash.cfg. open that in notepad, each line is one of the partitions. Adjust size and flash.
(Allsize means all the leftover space)
If you aren't using a clockwork rom, then the same applies.... in the daf rom folder is flash.cfg
If it is a daf rom, if you merge the partition info from your flash.cfg with the info in a cwm flash.cfg, and copy in the recovery.img you can flash your daf rom with your partition layout and apply cwm recovery at the same time.
samsamuel said:
Look in the folder where your cwm instal files are.one is called flash.cfg. open that in notepad, each line is one of the partitions. Adjust size and flash.
(Allsize means all the leftover space)
If you aren't using a clockwork rom, then the same applies.... in the daf rom folder is flash.cfg
If it is a daf rom, if you merge the partition info from your flash.cfg with the info in a cwm flash.cfg, and copy in the recovery.img you can flash your daf rom with your partition layout and apply cwm recovery at the same time.
Click to expand...
Click to collapse
Wow! Your great man! Ok I'm using HyperdroidGBX v11 and CWM 1.13. Do i need to edit the hyperdroidgbx flash.cfg and the CWM flash.cfg? What do you mean by copy in the recovery.img. So what should I do? Should i just adjust partition sizes in the cwm flash.cfg and then just flash hyperdroid or even better i could perform a nandroid backup and just restore right?
Ok so its a cwm rom so only the cwm flash.cfg exists.
However you should find the data part is already set to allsize meaning it takes up all the space after the small fixed size parts are done.
Do you have an ext partition on your SD card? If so, the rom is automatically putting apps there instead of on the phone.
(At least that's my understanding of app2sd+ enabled roms, certainly I never manually move apps to the SD card, yet there they are on my SD in the ext part. If you manually choose to move apps to SD in app manager, it takes them from the ext part and puts them on the fat32 partition.)
Get rid of your ext part and re try before you bother editing flash.cfg
If someone who knows yes or no could confirm my understanding of apps2sd+, that would be great.
Ok so i downloaded the recovery_150M is what i had on it. Edited the partition sizes. Now after flashing MAGLDR 1.13 edited flash.cfg, I'm stuck at the boot screen where the android is and it doesn't do anything. Do i need to edit a flash.cfg within a CWM folder? I tried several different sizes. IDK why it won't boot.... No ext3 and no i don't want apps installed to sd automatically, i have 1 fat32 partition on class 10 32gb stick. I want all apps to be installed to nand and i don't want my sd to be used at all unless i specify to move the data to sd card. Do i need to flash in HARDSPL? or on FLASHER in MAGLDR?
There was no need to do magldr again, only cwm, having looked in flash.cfg in the cwm folder.
Going back to your post 1 "how do I partition",,, that's what cwm is doing, creating partitions as per instructions in flash.cfg. you can't run nand android without partitioning first, therefore the answer to your original question is "it already is partitioned"
could somebody explain me the difference between american android MAGDLR NAND and american android CLK NAND?
What are advantages and disadvantages of them ?
Samuelgentl said:
could somebody explain me the difference between american android MAGDLR NAND and american android CLK NAND?
What are advantages and disadvantages of them ?
Click to expand...
Click to collapse
CLK and MAGLDR are the two different bootloaders used to get android on to the hd2's nand. american clk nand is the rom for the clk bootloader while amercian magldr nand is the rom for magldr bootloader.
If you dont know what clk and magldr are or what nand is then you google it. or search here in the forum before posting, everything has been explained, usually more than once, then over and over again, by various different people with various different guides.
evilbarcode said:
CLK and MAGLDR are the two different bootloaders used to get android on to the hd2's nand. american clk nand is the rom for the clk bootloader while amercian magldr nand is the rom for magldr bootloader.
If you dont know what clk and magldr are or what nand is then you google it. or search here in the forum before posting, everything has been explained, usually more than once, then over and over again, by various different people with various different guides.
Click to expand...
Click to collapse
could you give me some links please where was my question answered ? I was searching by google but I have not get satisfactory answers.
Samuelgentl said:
could you give me some links please where was my question answered ? I was searching by google but I have not get satisfactory answers.
Click to expand...
Click to collapse
Read this first!!
Then this!!
Then This!!!!
Read all before you do anything, well that's my opinion.
evilbarcode said:
Read this first!!
Then this!!
Then This!!!!
Read all before you do anything, well that's my opinion.
Click to expand...
Click to collapse
Thanks
I think Ill keep MAGDLR ... I just need to solve two problems:
1. how to create partition on my SD cart to extend internal memory (because in my american android I have only 80 MB free). I know how to do it in CLK but I have no idea how to do it in MAGDLR
2. somehow make my opera mobile browser play flash videos properly.
Samuelgentl said:
Thanks
I think Ill keep MAGDLR ... I just need to solve two problems:
1. how to create partition on my SD cart to extend internal memory (because in my american android I have only 80 MB free). I know how to do it in CLK but I have no idea how to do it in MAGDLR
2. somehow make my opera mobile browser play flash videos properly.
Click to expand...
Click to collapse
For problem one, download the free tool Mini Tool Partition Wizard. Use the Home Edition.
Steps to partition sdcard:
1. If possible turn off device, take out sdcard, use a sdcard reader to connect micro sdcard to pc/laptop.
2. Backup all sdcard content to pc/laptop.
3. Open partition wizard, delete partition on sdcard
4. Now, first create a fat32 partition, with 32kb cluster, make it primary, leave atleast 500mb free space. THIS HAS TO BE DONE BEFORE THE NEXT PARTITION.
5. Then using the remaining space, create a second partition, also primary, forrmat ext3 or ext4 depending on your rom, with 4kb cluster. THIS HAS TO BE THE SECOND PARTITION.
Apply all changes then put sdcard back into device, turn it on, run data2sd script or a2sd+ script depending on rom then you should be good to go.
I would recommend searching the american android thread for data2sd or a2sd+ scripts and instructions before following my advice.
Disclaimer: I take no responsibility for device breakages or sdcard loss of life, it is not my fault, blame god, technically he created everything so its his fault.
evilbarcode said:
For problem one, download the free tool Mini Tool Partition Wizard. Use the Home Edition.
Steps to partition sdcard:
1. If possible turn off device, take out sdcard, use a sdcard reader to connect micro sdcard to pc/laptop.
2. Backup all sdcard content to pc/laptop.
3. Open partition wizard, delete partition on sdcard
4. Now, first create a fat32 partition, with 32kb cluster, make it primary, leave atleast 500mb free space. THIS HAS TO BE DONE BEFORE THE NEXT PARTITION.
5. Then using the remaining space, create a second partition, also primary, forrmat ext3 or ext4 depending on your rom, with 4kb cluster. THIS HAS TO BE THE SECOND PARTITION.
Apply all changes then put sdcard back into device, turn it on, run data2sd script or a2sd+ script depending on rom then you should be good to go.
I would recommend searching the american android thread for data2sd or a2sd+ scripts and instructions before following my advice.
Disclaimer: I take no responsibility for device breakages or sdcard loss of life, it is not my fault, blame god, technically he created everything so its his fault.
Click to expand...
Click to collapse
Im very thankful for your advice but there is problem. I dont have sd card reader on my desktop
Samuelgentl said:
Im very thankful for your advice but there is problem. I dont have sd card reader on my desktop
Click to expand...
Click to collapse
And you don't have a usb card reader? in that case boot into clockworkmod recovery, i'm guessing you know that? go down to mounts and storage, the go to mass storage, the bottom one, plug usb cable in and that will mount sdcard to pc.
Then follow my instructions from before.
When you say!" I know how to do it in clk but not magldr",,, are you sure you don't mean you know how to do it in cwm? Cwm and clk are not the same. Cwm on clk is the same as cwm on magldr.
Clk is not cwm.
Into magldr, start cwm, advanced, partition SD card, done.
samsamuel said:
When you say!" I know how to do it in clk but not magldr",,, are you sure you don't mean you know how to do it in cwm? Cwm and clk are not the same. Cwm on clk is the same as cwm on magldr.
Clk is not cwm.
Into magldr, start cwm, advanced, partition SD card, done.
Click to expand...
Click to collapse
That works tooo but if your rom needs a ext4 partition then you cant use that as cwm partitions using ext3. but if thats all yo need then fine that works jut make sure you dont use a swap space unless your rom requires it.
And i was meaning did you know ho to get into cwm on magldr and obviously you did so thats good. And yes i know cwm is not clk cwm is a recovery, clk is a bootloader, i was the one that pointed you to that info on clk and magldr
evilbarcode said:
That works tooo but if your rom needs a ext4 partition then you cant use that as cwm partitions using ext3. but if thats all yo need then fine that works jut make sure you dont use a swap space unless your rom requires it.
And i was meaning did you know ho to get into cwm on magldr and obviously you did so thats good. And yes i know cwm is not clk cwm is a recovery, clk is a bootloader, i was the one that pointed you to that info on clk and magldr
Click to expand...
Click to collapse
to be honest Im completely confused now .. I thought that CLK ane CWM are the same things.
when I was downloading american android NAND 2.3.7 there were 3 download links:
1. AmeriCanAndroid MAGLDR NAND
2. AmeriCanAndroid *CLK NAND - this link is dead
3. CLK starterkit - this link is dead
I thought that AmeriCanAndroid MAGLDR NAND is one whitch is installed trough MAGLDR and AmeriCanAndroid *CLK NAND is one witch is installed trough clock work mode
evilbarcode said:
And you don't have a usb card reader? in that case boot into clockworkmod recovery, i'm guessing you know that? go down to mounts and storage, the go to mass storage, the bottom one, plug usb cable in and that will mount sdcard to pc.
Then follow my instructions from before.
Click to expand...
Click to collapse
I very appreciate your help. Im beginner in installing android and to be honest Im totaly lost.
so if I understand it right I have to do this ? :
0. install wm 6,5 to erase everything (I want to start from very beginning)
1. install Magldr
2. install clock work mode CWM
3. make a partition like this:
-Boot into the Clockwork Mod menu
-Go down to 'Advanced' and select (by pressing 'Call Button')
-Select 'Partition SD Card'
-Select Size of required partition not sure then 1024M is a good size)
-Make ABSOLUTELY sure you want to continue and then select 0M Swap Size
4. go back to magldr and install again wm 6,5 to erase everything except the created partition
5. install magldr again
6. install american android magldr NAND
Do I understand it right ?
Hey man there are plenty of guides and tutorials on this topic, that is if you search !!
Try this one: http://forum.xda-developers.com/showthread.php?t=893948
Samuelgentl said:
to be honest Im completely confused now .. I thought that CLK ane CWM are the same things.
when I was downloading american android NAND 2.3.7 there were 3 download links:
1. AmeriCanAndroid MAGLDR NAND
2. AmeriCanAndroid *CLK NAND - this link is dead
3. CLK starterkit - this link is dead
I thought that AmeriCanAndroid MAGLDR NAND is one whitch is installed trough MAGLDR and AmeriCanAndroid *CLK NAND is one witch is installed trough clock work mode
Click to expand...
Click to collapse
No CLK and MAGLDR are two different bootloaders. Obviously the links are just dead for american android CLK nand.
American android MAGLDR is installed through clockworkmod recovery using the MAGLDR bootloader.
AND
American Android CLK is installed through clockworkmod recovery using the CLK bootloader.
CWM works on both bootloaders, that is why you are getting confused.
There are plenty guides to use to make sure you can do it with out problems, you just need to search. Dont do anything until you know what you are doing, just read and re-read until you understand what has to be done and what the different aspects of the HD2 android are.
I don't want to be mean by saying this but if you can't understand what is happening you shouldn't try and put android on your HD2
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...