Related
A little over a month ago I flashed the damagecontrol ROM and haven't looked back. Aside from having 2.1 early, I was also able to access su features, blah blah blah. My question is: I am still losing internal memory even after enabling A2SD, partitioning my SD card into three sections (ext3, swap, and probably fat32 or something). I noticed a gain of about 40mb right away but each time I download a program my internal memory shrinks. Any ideas? I'm not a pro at this but really wanting to learn.
-------------------------------------
Sent via the XDA Tapatalk App
joshuaharp said:
A little over a month ago I flashed the damagecontrol ROM and haven't looked back. Aside from having 2.1 early, I was also able to access su features, blah blah blah. My question is: I am still losing internal memory even after enabling A2SD, partitioning my SD card into three sections (ext3, swap, and probably fat32 or something). I noticed a gain of about 40mb right away but each time I download a program my internal memory shrinks. Any ideas? I'm not a pro at this but really wanting to learn.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Even with A2SD there are still files that get written to internal storage for cacheing. You will see your memory go down.
Ah. I didn't realize that. Are there other ways to free up the internal memory? I'm down to around 25mb...
-------------------------------------
Sent via the XDA Tapatalk App
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
the same thing is going on with my phone i only see an added 40mb onto the internal storage when i put on a2sd,when i hear about other kids that get around 90mb when using a2sd.
willowmp said:
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
Click to expand...
Click to collapse
I just threw a 4GB Class 6 in and partitioned it. Before that I was running the stock 2GB (Class 2 I think). I've been considering a few options but not sure what the process should be and how to proceed:
- dalvik cache to sd
- jit compiling (alhtough, I've almost completely ruled this out due to rumors of instability issues)
- swapping sd (I'm not sure if this will have ill-effects on my system or not)
I would feel at more liberty to experiment if I knew what to do if my phone ran into an error that crippled it (i.e., stuck in boot loop). I'm really fresh to this, so it's a bit intimidating at first.
joshuaharp said:
I would feel at more liberty to experiment if I knew what to do if my phone ran into an error that crippled it (i.e., stuck in boot loop). I'm really fresh to this, so it's a bit intimidating at first.
Click to expand...
Click to collapse
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
willowmp said:
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
Click to expand...
Click to collapse
This kernel (.29 kernel, right?) is one I've been recently considering. I've made a nandroid backup through ROM Manager (is this as good as RA-Amon's recovery?). I'm not sure what to do with this should something go wrong...unless I can boot up and have access to the ROM Manager app – I'll cross that bridge when I come to it. Some questions:
concerning flashing a recovery
- what exactly does this do? (as I understand it, it writes a recovery file to my sd card, so that i can boot up in recovery mode should something cause my os to fail...is this correct?)
concerning the godmode overclocked kernel
- how long have you had this flashed on your phone?
- can I flash over my current ROM (damagecontrol 2.08.1)?
- will I lose info and have to wipe everything not on my SD card?
- I've partitioned my sd card for A2SD, will this cause problems?
- how long is your battery life on average?
Thanks dude.
willowmp said:
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
Click to expand...
Click to collapse
What did you set your swap and ext on when you partitioned your sd
xxxk15 said:
What did you set your swap and ext on when you partitioned your sd
Click to expand...
Click to collapse
ext: 1024 (or whatever the first 1gig choice is, I believe it is something like this)
swap: 30 (I believe, or whatever it automatically pops up as when formatting)
Through Dconfig I have apps2sd, dalvik to sd, and sd swapping with the default 30mb enabled.
Dalvik heap is set to 16mb and lowmemkiller set to less. JIT not enabled.
Current version DamageControl, the 768 overclocked kernel and toast's newest radio.
joshuaharp said:
This kernel (.29 kernel, right?) is one I've been recently considering. I've made a nandroid backup through ROM Manager (is this as good as RA-Amon's recovery?). I'm not sure what to do with this should something go wrong...unless I can boot up and have access to the ROM Manager app – I'll cross that bridge when I come to it. Some questions:
concerning flashing a recovery
- what exactly does this do? (as I understand it, it writes a recovery file to my sd card, so that i can boot up in recovery mode should something cause my os to fail...is this correct?)
concerning the godmode overclocked kernel
- how long have you had this flashed on your phone?
- can I flash over my current ROM (damagecontrol 2.08.1)?
- will I lose info and have to wipe everything not on my SD card?
- I've partitioned my sd card for A2SD, will this cause problems?
- how long is your battery life on average?
Thanks dude.
Click to expand...
Click to collapse
RA-Amon's custom recovery is a must and is vastly more important than a back-up app. RA-Amon's recovery is an actual recovery image, thus as long as your phone boots up to the HTC logo you should be able to access RA-Amon's recovery and thus restore the backup before the phone is even accessing the rom.
Flashing a recovery image is like flashing a rom, but instead of a rom you are flashing a recovery image. Your phone has a stock recovery image on it right now, I don't know the key combo but hold a certain pattern of keys down while turning the phone on and you will enter it. It looks I think like a triangle with an ! in the middle or something. This is sorta useless for us though because I don't think you can really do much with it.
When you flash a recovery img (RA-Amon's) that stock recovery image is just replaced with Amon's. After you do flash the recovery holding the HOME and power button to turn the phone on and continuing to hold it will cause you to enter Amon's recovery, which is a green menu. From this menu you can amke backups/restore them, wipe the data on the phone (factory reset), flash .zips (roms, bootscreens, themes, kernels) and other things.
What you are referring to the writing backup to sd card is called nandroid. Nandroid is an option in the recovery, so yes if you do flash the wrong rom or your phone won't boot up (boot loop or whatever) as long as you can access recovery which is one of the first things loaded when you hit the power button (unless you really do something spectacular like flashing a gsm hero's radio you almost always will be able to get into recovery. don't even touch radios right now, flash the wrong one and your phone won't even turn on/charge. aka your motherboard will be totaled) so you will almost always be able to nandroid recovery your os if something does go wrong.
In short before you do anything flash the recovery.
Now on to your other questions. I have been running the overclocked kernel for one day, but it appears stable and seems to be working good for me. When you flash a kernel you always flash it over a rom, because if you do it the other way the rom will replace the kernel. So yes once you have damagecontrol or another rom that supports that kernel you can simply go into recovery and use flash .zip to flash the kernel over the rom. As always make sure to make a nandroid before doing so.
DamageControl supports apps2sd, and you enable it to use a2sd using the Dconfig app that is included in the rom. It is generally a good idea to partition your sd card whenever you switch between roms unless they say it is fine. You should go ahead and copy over a backup of your sd card to your computer, however you need not format or wipe your sd card when flashing roms. Honestly I don't think you need to partition your sd card again, unless after you flash the rom the os won't boot up all the way or loops/crashes. If it does then partition the sd card and try rebooting the phone and it should fix it.
Also you can format and partition your sd card in recovery under Other.
As for my battery life I have been switching b/w roms and such and I just started using the OC kernel, but with the DamageControl rom back when I only had that flashed my batt life was good.
However I do have 3 batteries and an external battery charger for my phone. Check out the accessories section of this forum, 2 batteries and the charger for 11 bucks from Hong Kong on ebay.
Hope I helped.
So, through the damagecontrol dconfig app I banned "sense", rebooted and now my phone is stuck in a bootloop. Do I restore from previous nandroid backup or do I need to flash my phone? Suck.
joshuaharp said:
So, through the damagecontrol dconfig app I banned "sense", rebooted and now my phone is stuck in a bootloop. Do I restore from previous nandroid backup or do I need to flash my phone? Suck.
Click to expand...
Click to collapse
Just want to say first off: "I am an idiot". Nandroid backup from 5 days ago, booted up by holding *home and *power, then selecting to restore. Very easy. I can actually breathe now. Back in business. Sorry to waste your guy's time. We can keep the thread going minus my drama...
joshuaharp said:
Just want to say first off: "I am an idiot". Nandroid backup from 5 days ago, booted up by holding *home and *power, then selecting to restore. Very easy. I can actually breathe now. Back in business. Sorry to waste your guy's time. We can keep the thread going minus my drama...
Click to expand...
Click to collapse
It's all good.
See why I emphasized flashing your recovery before messing with anything? xD
xxxk15 said:
What did you set your swap and ext on when you partitioned your sd
Click to expand...
Click to collapse
I set the swap to 32mb and ext3 to 512mb I believe...does this sound right?
willowmp said:
RA-Amon's custom recovery is a must and is vastly more important than a back-up app. RA-Amon's recovery is an actual recovery image, thus as long as your phone boots up to the HTC logo you should be able to access RA-Amon's recovery and thus restore the backup before the phone is even accessing the rom.
Flashing a recovery image is like flashing a rom, but instead of a rom you are flashing a recovery image. Your phone has a stock recovery image on it right now, I don't know the key combo but hold a certain pattern of keys down while turning the phone on and you will enter it. It looks I think like a triangle with an ! in the middle or something. This is sorta useless for us though because I don't think you can really do much with it.
When you flash a recovery img (RA-Amon's) that stock recovery image is just replaced with Amon's. After you do flash the recovery holding the HOME and power button to turn the phone on and continuing to hold it will cause you to enter Amon's recovery, which is a green menu. From this menu you can amke backups/restore them, wipe the data on the phone (factory reset), flash .zips (roms, bootscreens, themes, kernels) and other things.
What you are referring to the writing backup to sd card is called nandroid. Nandroid is an option in the recovery, so yes if you do flash the wrong rom or your phone won't boot up (boot loop or whatever) as long as you can access recovery which is one of the first things loaded when you hit the power button (unless you really do something spectacular like flashing a gsm hero's radio you almost always will be able to get into recovery. don't even touch radios right now, flash the wrong one and your phone won't even turn on/charge. aka your motherboard will be totaled) so you will almost always be able to nandroid recovery your os if something does go wrong.
In short before you do anything flash the recovery.
Now on to your other questions. I have been running the overclocked kernel for one day, but it appears stable and seems to be working good for me. When you flash a kernel you always flash it over a rom, because if you do it the other way the rom will replace the kernel. So yes once you have damagecontrol or another rom that supports that kernel you can simply go into recovery and use flash .zip to flash the kernel over the rom. As always make sure to make a nandroid before doing so.
DamageControl supports apps2sd, and you enable it to use a2sd using the Dconfig app that is included in the rom. It is generally a good idea to partition your sd card whenever you switch between roms unless they say it is fine. You should go ahead and copy over a backup of your sd card to your computer, however you need not format or wipe your sd card when flashing roms. Honestly I don't think you need to partition your sd card again, unless after you flash the rom the os won't boot up all the way or loops/crashes. If it does then partition the sd card and try rebooting the phone and it should fix it.
Also you can format and partition your sd card in recovery under Other.
As for my battery life I have been switching b/w roms and such and I just started using the OC kernel, but with the DamageControl rom back when I only had that flashed my batt life was good.
However I do have 3 batteries and an external battery charger for my phone. Check out the accessories section of this forum, 2 batteries and the charger for 11 bucks from Hong Kong on ebay.
Hope I helped.
Click to expand...
Click to collapse
Dude...helped IMMENSELY! I'm still digesting it.
That's good to know about flashing radios. I was going to flash the most recent one for 2.1 roms on CDMA heros, but I think I'll wait to hear more about it.
I think I feel comfortable flashing the .29 kernel over my current ROM. I gotta be honest though, the DConfig thing kind of weirds me out now, after trying to use it. I'm not sure which button is going to cause my phone to freak out.
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
Click to expand...
Click to collapse
I'm considering doing this but have read that this causes issues with nandroid backup. Have you experienced this?
-------------------------------------
Sent via the XDA Tapatalk App
ok so i tried to put rafdroid on my phone (link below):
http://forum.xda-developers.com/showthread.php?t=908528
I have tmobile HD2 running gingerbread 2.3.2. When I tried following the instructions and formatting/partitioning the SD card, my phone wouldnt work. i have clockworkmod recovery on my phone and i used it to install the rom zip file. it got to the screen where it has a picture of android and says dafdroid by dafpigna and stayed there for well over the initial startup time (over 20 min). I tried installing the dafdroid kernel as well (thru clockworkmod) and its still doing the same thing. when i tried formatting the sd card to anything other than quick format it wouldnt work and it wouldnt complete partitioning through the computer it would only work through clockworkmod on my phone. i tried to flash to another rom and even back to windows and it kept giving me an error message about some rampi.dll (something like that) isnt there.
please help! i cant use my phone at all! i have a 500 dollar paperweight
Hi,
Need a bit more information.
Can you still boot into magldr (holding down power button after switching on?)
What operating system are you running on your pc/laptop?
How far did you get when you were fomatting your sd card?
i find it quite common that an android rom wont complete the first boot after flash. mostly, pulling teh battery and booting again solves it.
Its also far more common when you didnt wipe the partitions from the previous rom first. (CWM, wipe data/factory reset, you can later use cwm - advanced restore - and just restore data and sd-ext to get your data and apps from teh previous rom back)
Partitioning, could be a dodgy sd card, no suggestions
rampi.dll - was it rapi.dll? update activesync to latest version.
I have an issue cannot install larger nand roms onto my phone previous roms worked tried various typhon cm7 roms, various miui roms both magldr and clk roms does not matter used task29 increased cwm size from 150 up to 250 and boot just hangs. Noticed roms larger than 90 MB zipped does not work at all they install but just hangs on boot
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
joostnl said:
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
Click to expand...
Click to collapse
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Buy her an iphone, then she can't pull the battery! :-D
Sent from my HD2 using XDA App
malybru said:
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Click to expand...
Click to collapse
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
lol, hahaha
joostnl said:
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Click to expand...
Click to collapse
ive seen a few posts where people have struggled with getting past boot logo, think it was fine after using a different partition in recovery but as your device is for the sd build am not quite sure how that works as Ive never had sd android or if having sd requires clockwork mod recovery? if so try different partition as i said earlier if not hang on till someone has the answer
johnerz said:
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
Click to expand...
Click to collapse
haha great answer, my girlfriend doesn't touch my hd2 or she gets alot more than a double dose with the tazer method, HD2 is not the solution for a women... you take the hd2 of her and buy her a iphone surly they are women material.
Ignore Post
Problems almost always occur after a few weeks or months of use for me, just reflash the ROM, and you'll good to go.
removing the battery is not recommended, it can corrupt files on the sd-card. Try to boot without sd-card and see if it helps. If your ROM does boot, it means the SD card is corrupted, you can try to backup the SD card and restore it after completely wiping the sd-card.
If your rom doesn't boot, than it meant there's something else going on, maybe corrupted flash, so reflash and try again. This will delete all your data, so be careful
if your girlfriend is not an daily flasher also might i suggest using a daf build. All the configuration is done for you. if you are using a sd build from magldr than make sure you change the name of the build than edit the startup txt like this "rel_path=whatever you name the build(example: "rel_path=MIUIROM nand_boot=1") the 1 for magldr 0 for windows 6.5. the reason for me saying this is all android builds create a folder android when they boot up with all your info like data and cache is in there. So its best to separate the two just in case you want to boot up more than two builds from sd.
Same here.
could be a bad block in your NAND memory. you can check this with cLK and fastboot.
see this post: http://forum.xda-developers.com/showpost.php?p=13600733&postcount=9
i checked mine and there was a bad block in the userdata. i think that is wy my phone was freezing.
now i have flashed cLK and untill now its working great!
Hi,
I've got an HTC HD2 here, with Android installed on it. (NAND, I believe.)
It was bought second-hand with Android pre-installed.
Because it was still linked to the google account of the previous owner, I had to restore the whole phone to factory settings. Since that didn't work, I've just decided to install another Rom.
After some messing around, I managed to install Clockworkrecovery. (It wouldn't boot for some mysterious reason) And then I installed an Android Rom. (Energy™ -.¸¸.·´¯ Sense 3.5 Runnymede)
After some time, the phone rebooted and got stuck on the Android boot screen.
I tried to install another Rom, but now they all get stuck on the boot screen. (I have tried another Runnymede rom, and RCMix3D)
Does anybody know how I can fix this?
I wiped my Dalvik Cache, I wiped my Cache partition, I wiped my data/factory reset. I am using the MAGLDR as boot thingie, but that's working perfectly.
I have formatted my SD-card with G-Parted, on my Ubuntu-PC. (First partition FAT32-750MB, Second partition EXT3 - 1GB and a Linux-Swap of 100MB)
For some strange reason, ClockworkRecovery cannot format my SD-card. (Well, it says it can, but as soon as I stick the card in my PC, the PC tells me it's corrupted. (Windows XP on my Father's PC tells me it has to be formatted, on my Ubuntu it doesn't show up as mountable)
Thank you in advance
P.S. I don't mind losing data, there's no personal data on it. Any solution (which doesn't involve buying a new phone) will do.
Quickest solution I would try is format the entire card to fat32, and see if your pc detects it. Once it does, put the rom on it, put in in the phone, boot into clockwork format data/cache/dalvik install the rom then reboot and see if it goes past the bootscreen (keep in mind first boot takes a while, but if it takes more than 2-3 minutes theres still a problem.
Do you know what partition layout of clockwork you installed by any chance? Some roms require specific layouts in order to work correctly.
Thank you for your reply.
Unfortanetly, that didn't work.
I have installed Clockworkmod like they say on jayceooi dot com. (I cannot past links yet, but here's the step-by-step guide:
Step by Step Guide
Power on your phone and don’t let go power button.
DFT MAGLDR Bootloader will be loaded.
Use volume down button to go down to 5. USB Flasher.
Then press call button to load USB Flasher mode.
Connect USB cable from PC to phone.
You should see Wait USB…USB.
At PC, right click on DAF.exe and select ‘Run as administrator’.
Click ‘Yes’ if User Access Control prompt up.
Follow onscreen instructions to install.
Phone will be rebooted after installation finished.
DFT MAGLDR Bootloader will be loaded then.
Disconnect USB cable from phone.
Use volume down button to go down to 8. AD Recovery.
Then press call button.
ClockworkMod Recovery will be loaded then.
That’s all.)
I used the 150MB-Partition one.
Didnt work how? Does the pc detect the sd card now after you formatted?
The directions you posted are right, so maybe try a different partition layout. The roms that you said you tried use different layouts than what you have and that may be a problem. Test a CM7 rom and see if it will boot, they tend to have less problems and are overall more stable than sense roms.
I recommend Typhoons rom: http://forum.xda-developers.com/showthread.php?t=933951
Try to install it and see if it boots. It uses the same partiton layout that you have now. If it boots, thats indication that you may need a different layout if you want to run a sense rom.
Well, I could re-format my sd-card and re-partition it, but it (Android) still got stock at the boot screen.
Using the Typhoon rom, I got the same problem. The Rom appears to be succesfully installed, but it didn't really boot.
I now tried to installed Windows Phone 7, this works fine. (I don't want to install WP7 however, I want to install android)
I tried the following too: (Post by a3r0n1)
http://forum.xda-developers.com/showpost.php?p=18868874&postcount=14
/
At the "Using "HD2 Toolkit" select "Magldr repartition" Make sure that you are using the recommended partition size for your rom!" part, I got an error that the file was too big when I tried to choose a partition of 300MB, I honestly have no idea what the partition size should be. (I want a sense-rom, I don't have a clear preference which)
I did install the Clockworkmod with 400MB with succes now.
However, still got the same problem. Android seems to get in a loop somewhere in the boot screen
EDIT:
I noticed that the Micro-SD card always corrupts after CWM installs the Android-Rom.
I think that may be the core of the issue here.
Does anybody know how I can install Android without CWM?
Are u repartitioning the phone? That might be the problem. Hope this helps
Sent from my Nexus One using XDA App
I manager to install an old Desire-based rom with Android 2.2 through a daf installation.
This one works fine but I still would like to install a Rom with Android 2.3 via a more regular way.
One problem I'm facing with this Rom is a very limited amount of internal storage. (about 55MB)
And I've got a big battery leak, the battery drains very fast. Much faster than my Desire HD. (The HTC HD2 we're talking about isn't mine, It's my mother's)
So does anyone know how I can install a regular Rom (preferably runnymede based) without CWM? Or does anyone know how I can resolve my problem?
@akaruna: I do not know how to partition the phone, I believe I didn't do that. Should I? I did partition the SD card. (CWM made unreadable cards for some obscure reasons, so I partitioned the SD card using gparted on Ubuntu)
Thanks in Advanced
Sjoerd
If you have limited internal storage then the main problem is the partition table is not correct. This is also why the roms you install are stuck on the bootscreen. When you install roms that require a bigger partition table than what you already have on your phone they will be stuck in a bootloop.
Go and download the HD2 NAND TOOLKIT: http://forum.xda-developers.com/showthread.php?t=1090783
Check out the video to familiarize yourself with the features, then repartition your MAGLDR with the correct partition table that the rom you want requires. Go into clockwork and install rom from zip.
Yes the tool kit is the best.
Yea the toolkit works wonders. Even though I still do it the original way ;p I do everything faster that way for some reason
Sent from my Nexus One using XDA App
Oh and yes, always read the thread from that certain Tom so that way u know exactly what partition table/size to use. Usually linked also.
Sent from my Nexus One??? (HD2) using XDA App
I tried it again with this rom: "[18Dec 2011] [CMR] Sensation xl Sense3.5/2.3.5 v2.7 BETA OC & marc1706 0.1.3 kernel" (I believe I'm still not allowed to post links)
I used the NAND toolkit this time for the System Partition Size.
The only thing I actually did was clicking 350MB as System Partition Size and then I clicked repartition. And then I followed the on-screen instructions, which involved clicking next and after some installing some drivers everything went fine. (With the HD2 in USB-flash mode of course, it also said the job was completed succesfully)
I wasn't able to choose a bigger size for some reason, it told me the 400MB was too big.
Still the same problem, the phone gets stuck at the Android boot-screen.
Does anybody have an idea? Thanks in advance (Again, I'm not scared of losing any data, if anyone has any solution at all: I'm more than happy to hear it)
I tried another DAF rom and got the following error:
"Error Description: Size is too big.
Info: .\RSPL\RSPL.cpp (800)"
So I tried repartitioning the System Partition Size (MAGLDR) to 400Mb.
However, It gave me the exact same error.
Does anyone know has any idea? (For example, how I can change the partitions in another way)
(Partitioning it at 360MB works fine)
Not sure what it is but the DAF file I use let me partition to 445...... those sense time are heavy and if the partition isn't right it will bootloop or not
Sent from my HTC HD2 using XDA App
" sense time " and do you have the sdcard partition at 1gb?
Sent from my HTC HD2 using XDA App
............ sense rom.........
Sent from my HTC HD2 using XDA App
Hey every1,
i got weird problem with all ics roms, even SD <
I can successfully install tytung beta1 rom and run it, but beta2+ roms and similar ones, and SD build all have same thing:
i have random freezes/stuck at bootlogo(it doesn't freeze, it simply continues to do the animation forever), only ONCE it booted, but since i needed kernel fix(for headphones) to apply - i restarted, and wasn't able to boot in successfully again. Now almost all the time i get freeze/reboot after ~5-10sec after i get into ics rom, SD build doesn't boot at all.
Partitioning problem? - have tried many partition layouts.(like 190/10,200/10,210/10,200/20,230/20,210/20 and so on, also with different bootloader partition size up to 8mb)
Also i have always used task29 and fully wiped everything and reinstalled from scratch, still didn't helped.
Also tried to boot with plugged in usb cable/without it or with/without memory card in.
Maby it's radio version problem, or don't know, what else can cause the problem?(radio ver:2.15.50.14)
Between i have created big cache/memory sometimes(up to 250mb partition/44mb cache) - and still it didn't worked fine :/ also tried different clockworkmod versions(3.0.0.5 and 5.something), magldr 1.13
p.s. i have europian hd2(not t-mobile)
or maby i'm partitioning it wrong? i change partition sizes inside flash.cfg and after i flash clockworkmod(i do task29 before that, and install fresh magldr), maby i should change somewhere else/more?
Also formatted memory card many times(sdformatter) and redownloaded roms, still same result.
p.s. tried ~3ics beta2+ roms(not sure mb even more), and 1sd rom
Edited:
forgot to mention, when phone kinda freezes(the boot animation/startguide for ics) - when i press physical buttons - the backlight appears and after that dims away as it does on every other android rom, so it kinda feels that rom isn't frozen, only the screen. Also sometimes after getting ics welcome screen - after ~5-10sec it gets back to bootloading animation and does it over and over again...
hey
I'm having the same problem did you figure it out I'm having same problems with ics and cm7
What has worked for me is 5/230/5. Im using tmous but that layout should work for your version.
Thanks
You are the man bro I cant believe it was something so simple
problem
I just tryed that partition it worked then rebooted while i was trying to set up the device do you know why?
Youngmyster said:
I just tryed that partition it worked then rebooted while i was trying to set up the device do you know why?
Click to expand...
Click to collapse
I am using the ICS beta 3 now, I have updated with every release and I didn't get this problem. It sounds like something crazy, you may just have to wait a little bit because ICS is still very beta... Check out HD2 Toolkit as well it makes it much easier flashing..
Wait, I didnt didn't see that you were having problems with cm7.. :-( I'm afraid I just wasted your time on my reply..
What Clockworkk mod recovery are you using?
And how are you transfering your data to your SD card?
---------- Post added at 05:15 PM ---------- Previous post was at 05:07 PM ----------
Try backing up your entire SD card, and then reformat it completely.
Then task29 and wipe everything.
I think you said you use magldr, since your having these problems try cLK
Use just a simple 220MB 5MB cache on HD2 Toolkit
Install ClockworkMod Recovery 5.0.2.6 as it is the newest one.
Transfer your zip file to your SD card using a card reader.
Install and see if ICS will boot.
Try that and see if it works. It should work.
Question. Do you have this same problem with any roms besides CM7 and ICS?
---------- Post added at 05:17 PM ---------- Previous post was at 05:15 PM ----------
Don't forget when using cLk you download the main zip file for the rom, and then a separate zip for the cLK kernal..