I tried almost any ROM known to work from user's feedbacks in the XDA forums, but I couldn't get any android ROM to work on my HD2.
I have installed magldr 1.13, installed radio 2.15.50.14 (BTW, my HD2 is NOT t-mobile), installed CWM recovery*, put some android ROMs on the microSD (2GB card) and then installed android ROMs from the Android recovery.
The installation process goes fine, no warnings, no errors. After installation comes trouble, either of the next will happen:
- the phone will go in bootloop forever
- the phone will freeze on the bootscreen (freeze like the animation is still going but after hours nothing happens)
- the phone will go in soft-reboot loop. With this I mean it goes on on the boot animation, almost finishes doing whatever it was doing, and then a black screen and the boot animation will just start over and keep doing so forever.
- android will boot and do the applications installation thing (where it says "Installing apps... 10/30" or so) and when it has finished it will just reboot. On reboot it will do again the applications installation thing, and then reboot once more, and do so forever.
*I tried many recoveries: 3.0.2.4; 4.0.1.5; 5.0.2.6; 5.0.2.7; they all work fine on their own, it's just the android ROMs will go crazy. Tried different partition sizes, including 500MB system and 100MB cache, nothing changes.
I followed guides that I found on this forum, which seem to work just fine for others.
Can you help me with this? Please, my WP7 ROM is working for most things but gives me some huge troubles and lacks many apps that I need...
EDIT
Answers to obvious questions you might ask me:
Are you trying to dual-boot WP and Android? >> NO
Have you wiped before installing? >> YES, tried wiping dalvik as well
Are you using wrong ROMs? >> NO, just ROMs from NAND development section
Have you tried with GB ROMs? >> YES, same thing as with ICS/JB ROMs.
Are you trying to install ROMs with HCT Sense? >> tried one, didn't work. all others are without HTC Sense
A few things come to mind; you might have a too small data partition (i.e. gave too much to /system) or perhaps repartitioning didn't take- it's a little harder to check with magldr than cLK. If you have adb installed (or TWRP) you could boot to recovery and check with adb shell df (or df).
Have you tried with NativeSD? Repartition the sdcard in recovery (give it 1GB ext4), this will wipe the sdcard and install it as NativeSD, this would rule out any problems with the NAND (size or otherwise).
Can you give me some more info about sizing the data partition? From recovery I can only wipe the partition but it gives me no choice on how much space to give it. Also, if it helps with the issue, I tried with many system partition sizes, including the "standard" 150, 250 and 450 MB.
No, I don't have adb installed on my PC. I haven't tried to install as nativeSD yet, mainly because the card is very slow (class 2 if I remember well). I'll try though, maybe it works...
T3STY said:
Can you give me some more info about sizing the data partition? From recovery I can only wipe the partition but it gives me no choice on how much space to give it. Also, if it helps with the issue, I tried with many system partition sizes, including the "standard" 150, 250 and 450 MB.
No, I don't have adb installed on my PC. I haven't tried to install as nativeSD yet, mainly because the card is very slow (class 2 if I remember well). I'll try though, maybe it works...
Click to expand...
Click to collapse
If I recall NAND resizing is done when flashing CWM by reading a flash.cfg file, I'm thinking perhaps that the data partition (which houses dalvik) is full leading to the stall. Try installing a ROM as NativeSD (Even if your sd is slow it should at least boot) - that'll check if the issue is with something else (radio, HSPL etc.), you could try booting an SD TWRP and running df in terminal emulator (after trying to boot), to see the partition sizes and how full they are.
If you install adb - no need to install the whole sdk, you should be able to see what's causing the bootloop.
Found the issue after a dozen of trial-and-fail. Yes, the issue was that the data partition was too small (actually, it didn't exist at all).
So here's the deal. the flash.cfg file did not contain anything specific to the "data" partition. I guess it simply can't be managed from flash.cfg or for other reasons it wasn't included as an option. Unfortunately, it seems like all the guides/tutorials I have read (here on XDA, but even elsewhere) simply lack any mention about this. So for any future user having the same issue as me, the solution follows. For guide writers, if you wish you may copy-paste this to your guide. BTW, this is magldr 1.13 specific, I have no idea how cLK works.
After flashing CWM recovery, boot your phone to magldr > AD recovery. From CWM menu choose Advanced > parition sdcard. You will be asked for:
Ext size >> this is the data partition that will be used for your system
Absolute minimum size: 512MB. You'll be able to install most ROMs and boot them properly, but on first app install you might fill the whole partition
Recommended minimum size: 1024MB. You'll be able to install a handful of apps, but it's still pretty small. I have filled it with just 20 apps or so...
WARNING: don't give this partition the full sdcard or you won't have any more space for the "sdcard" partition where all your storage goes (photos, music, settings, and anything).
swap size >> a swap partition can be used to augment (read: improve efficiency, not quantity) your RAM
Any cached processes (background applications) may sit in swap when inactive. A swap partition will NOT increase your RAM to 32GB if you own such microSD card, active processes are still executed in your physical available RAM. Instead it may leave more free RAM available to active processes instead of keeping it filled with inactive applications. Please note that I strongly recommend NOT to create such partition on slow microSD cards (I'd recommend a class 6 microSD minimum). It's perfectly fine to run with no swap partition (choose 0MB size).
There you are. Now, all the ROMs that can be installed with [email protected] and [email protected] (data on sdcard) will use the newly created Ext partition.
I hope this will come useful to more people than just me
p.s. thanks for help HypoTurtle
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.
Hi.
After getting my HD2 last week I tentatively but successfully flashed my first ROM, which was the Rafdroid 4.0.2.
I had correct radio.
I installed HSPL 2.08.
I installed MAGLDR 1.13
I got the Rafdroid ZIP file
Prepared SD card with Primary Partition and 1GB ext3 partition.
Downloaded the 400MB CWM partition and flashed to HD2
Then installed the Rafdroid Zip from SD card via CWM.
Everything seemed to go fine and I've been using the Rafdroid for a week. But now I want to try a new ROM, specifically the NexusHD2-Gingerbread V2.7 ROM.
Now I'am a bit unsure on how best to proceed still being new to the world of NAND. A few things in the Nexus ROM thread confuse me.
Installing CWM_Recovery_for_NexusHD2 (135MB system and 2MB cache)
Does this mean I need to reflash to CWM partiton size 1.3v 150MB? I'm unsure what the 2MB cache means.
Enter ClockworkMod Recovery when you're on MAGLDR 1.13 (hold "Power" button during boot) and select "AD Recovery" or "Boot AD SD" (if ever copied CWM's initrd.gz and zImage to SD).
The first part of this I understand but I don't know what the bold bit is. Do I need to copy these files to my sd card? I didn't do anything like this when I flashed Rafdoid.
Thanks for your time. Hopefully a few pointers can get me on my way
Yes, reflash cwm but with a different partition layout.
(look in cwm folder find flash.cfg, open it in notepad, you will see the numbers to change)
The bit in bold - ignore that, there are two types of cwm, one that installs to the nand, like you have, and one that runs from sd, so ignore the sd bit.
So,
Into magldr,,
usb flashing,,,
flash the new layout with the sizes the rom suggests, (you can tinker with your own sizes as you get used to changing, it's the system size that is important, a few meg bigger than the unzipped size of the system folder in the rom.zip)
When that completes, back into magldr,
Ad recovery (option 8 I think) to boot cwm, and flash the rom.
You can set the system size to what you like, so long as it is bigger than the roms system folder, but anything over is wasted, it doesn't count towards internal storage, so if the rom says 135 and you flash 150 layout, there is 15meg wasted space. (that being said, 150 is a good size to use, since quite a few roms use that or smaller,, sense free roms will mostly all fit in 150 layouts,) meaning you can switch between them without flashing cwm again. Also means you can restore cwm backups from any of them into that layout, so you can set one up, take backup, flash another, take backup, flash a third, then any time restore either of the backups.
Use flash.cfg to change partition.. Btw. I read in NexusHD rom topic you need to flash 135MB system and 2MB cache.
About the second problem:
Just make sure you have zipped rom on your sd card, enter MAGLDR, select AD Recovery and flash zip.
I think the second way is possible if you manually copy those files, never tried it.
Hi Sam and volv.
Many thanks for taking the time to answer my queries!
Should I get rid of the Rafdroid sd card layout and just re format the card to FAT32? I don't think I'll be going back to it.
Another thing about the backup - where are they stored - in the NAND memory or on the sd card for loading back into NAND?
Everything else you've posted has been very clear and super helpful. I'll definitely be a lot more confident at flashing the ROM tomorrow!
Thank you.
Warren_Orange said:
Hi Sam and volv.
Many thanks for taking the time to answer my queries!
Should I get rid of the Rafdroid sd card layout and just re format the card to FAT32? I don't think I'll be going back to it.
Another thing about the backup - where are they stored - in the NAND memory or on the sd card for loading back into NAND?
Everything else you've posted has been very clear and super helpful. I'll definitely be a lot more confident at flashing the ROM tomorrow!
Thank you.
Click to expand...
Click to collapse
Hi,
Before starting anything,BACKUP YOUR STUFF.
Go to ad recovery>backup and restore and make a backup of your current system and data.This is stored on your sd card in clockworkmod/backup.
Next ,flash your new partition.
Then go to ad recovery and wipe data,cache partition,and dalvik(advanced)
Then go back and choose install zip from sd card(having placed your new ROM zip on the root of your sd card using a card reader)
Most roms support using the ext partition, so definitely keep it.
Before you flash, in cwm, do a 'wipe data/factory reset','wipe cache', and then 'advanced - wipe dalvik cache'. This will clear out the data and such from the previous rom, so no need to format it. (there may be some leftover folders from certain apps in the fat32 partition, you can manually delete them as and if necessary, shouldnt cause any problems)
backups get saved to the sd card, in a folder called clockwork, so be sure and back that up if you plan on formatting your sd card.
Hi again.
I just want to say the flash went like clockwork (no pun intended ) The NexusHD ROM has a really nice feel to it. Its my first taste of stock Android and I like it.
I was going to sell the HD2 and keep my old Hero, but I'm not so sure now after trying NEXUS HD ROM.
Hmmn decisions decisions.
Once again thanks for all your help. It definitely filled in the missing blanks.
Ta Ta
you can use every flash.cfg and change the values to the needet. Run the flash tool and after that flash the zip via recovery
I want to try a ROM which says:
Partition Layout (5/155/5) use hd2 toolkit
SDext: min. 500mb
I am not 100% sure what does it mean SDext is probably 500 ext patition bigger than 500
5/155/5 is
5 cashe
155 data and
5 WHAT????
Cant figure this out.
Thank you
Do you have any android rom installed? If yes, then you should (I had on every rom) have an option on reboot menu: reboot, recovery and BOOTLOADER - choose this one. And there you have SETTINGS->REPARTITION NAND and there set these ones your roms prefers. If you have not, then try to install this rom choosen by you, and maybe there will be option BOOTLOADER on menu. These are partitions, for example 155data(system) is space for system (I think). But standard settings are good for me and works with every rom.
[EDIT]
Try to boot phone by holding [back] nad [Power]. This opens bootloader and there you can set all.
Partition your nand using HD2 Nand Tookit.
First 5 is boot partition set to 5 by default
155 is system partition,
next 5 is cache size.
sdext partition can be set up from recovery (in cwm recovery go to advanced menu and select partition sd card), follow instructions for your rom. This can be used as if it was internal memory by your rom..
ALSO you might want to take a look HERE..
Edit: best to post any questions about any specific ROM in the ROM thread
This question was not "how-to", but more "what does 5/155/5 mean" type of question. Last time I played with internal memory of the device all I had to do was select the appropriate CWM version. This is why I asked here, I think it belongs, cos is general knowledge kind of thing.
I kind of dont see how to fiddle the size of /boot, no problems with /data and /cashe, but since you say this is default I wont have to, I suppose.
A few days ago I was pissed of by CyanogenMod (and stock Andriod in general), cos the only option to deal with Vcards is Handsend sms, but Handsend will not search for contacts correctly in Bulgarian (CYR) when installed on vanilla Android - small letters will not match capital and vice versa in contact names. This is why I decided to go for Sense - the message app is simply better...
Rather than using toolkit, download the CWM package and inside is a file called flash.cfg. Open this file and you should get this (maybe a different system or cache size)
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 5M
userdata ya|asize|hr allsize
Click to expand...
Click to collapse
5/155/5 is basically the middle three lines, i.e. 5Mb boot partition, 150Mb system partition and 5Mb cache partition. I don't know why chefs post it like this as I'm reasonably sure the boot is always 5Mb (I've never seen differently) so they could just post the system partition size (as quite a lot do). Hope this helps
shanman-2 said:
Partition your nand using HD2 Nand Tookit.
First 5 is boot partition set to 5 by default
155 is system partition,
next 5 is cache size.
sdext partition can be set up from recovery (in cwm recovery go to advanced menu and select partition sd card), follow instructions for your rom. This can be used as if it was internal memory by your rom..
ALSO you might want to take a look HERE..
Edit: best to post any questions about any specific ROM in the ROM thread
Click to expand...
Click to collapse
?????????!!!!!! ???
shanman-2 said:
?????????!!!!!! ???
Click to expand...
Click to collapse
mmmm which part for the "?????????!!!!!! ???" ?
! that bit
You can use CWM Recovery it's very easy to use for repartition your nand, but you must install MAGLDR or CLK first if you want go to recovery..
ariebower said:
You can use CWM Recovery it's very easy to use for repartition your nand, but you must install MAGLDR or CLK first if you want go to recovery..
Click to expand...
Click to collapse
Hm, this is something I missed!
1. I use mainly Ubuntu, hence I have have to rely on Wine or a pc I almost dont use for windows
2. I have CWM and MAGLDR installed
How to re-partition based on config file only? Can I do it?
Put the config where? (sdcard, ROM.zip)
Run what in CWM.
You would make my day, since I am away form how, with my laptop only, the ROM I run has a bug with wifi tether and I have to change it, but options are quite limited, since I dont know how to re-part, I have to choose ROMs that rely on system less or equal to 155 at teh moment. And I need a Sense, since others cant receive 100% vcards in Bulgarian (CYR)
deckoff said:
Hm, this is something I missed!
1. I use mainly Ubuntu, hence I have have to rely on Wine or a pc I almost dont use for windows
2. I have CWM and MAGLDR installed
How to re-partition based on config file only? Can I do it?
Put the config where? (sdcard, ROM.zip)
Run what in CWM.
You would make my day, since I am away form how, with my laptop only, the ROM I run has a bug with wifi tether and I have to change it, but options are quite limited, since I dont know how to re-part, I have to choose ROMs that rely on system less or equal to 155 at teh moment. And I need a Sense, since others cant receive 100% vcards in Bulgarian (CYR)
Click to expand...
Click to collapse
Maybe this thread will help you to do it without a PC
There is a huge thread on how to move data from the System partition to the SD, but I think it is still not very clear (at least to me) why the system partition gets so full when installing new modern ROMs on the HD2. Every installation guide starts with partitioning in clk or magldr. For instance, the HexusHD2 ICS ROM has to have at least 170mb system partition. I made it 300 just to be sure and android says I have a total of 105mb internal storage. (I barely have place to install new apps, since android takes around 75mb of those 105mb)
My question is what is what is the relation between the system partitioning in clk and the size I get after the ROM is flashed. Will i have more storage if I partition clk to a greater figure- 450mb? ...or will it be vice versa?
thanks
archibrid said:
There is a huge thread on how to move data from the System partition to the SD, but I think it is still not very clear (at least to me) why the system partition gets so full when installing new modern ROMs on the HD2. Every installation guide starts with partitioning in clk or magldr. For instance, the HexusHD2 ICS ROM has to have at least 170mb system partition. I made it 300 just to be sure and android says I have a total of 105mb internal storage. (I barely have place to install new apps, since android takes around 75mb of those 105mb)
My question is what is what is the relation between the system partitioning in clk and the size I get after the ROM is flashed. Will i have more storage if I partition clk to a greater figure- 450mb? ...or will it be vice versa?
thanks
Click to expand...
Click to collapse
You've got it completely the wrong way around, the /system partition is where the actual OS is installed, so the smaller the /system partition, the greater the internal storage which remains, which is thus usable for apps.
Smaller partition = more storage.
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...