Ok so i've flashed my phone a good few times and i'm also an experienced linux user. So i have a fair idea about what i'm doing. The last 2 months i've been running the latest Xrom, and yesterday it started doing some funky stuff. My phone would randomly not wake up when pressing the menu button, had to open it up etc to wake it. Then it randomly shut off. So i started it up and it went through the android screen and then constantly on a black screen.
So i wiped it and went back to 1.5 using the RC7 image. That worked ok, but i wanted to flash it again. I must have tried flashing/wiping/restoring to 1.5 about 6 times. I'm trying to run cyanogen's mod, tried all different versions too, even the one i had tried before switching to Xrom. Everytime it just sticks at the G1 screen, no light on. I can leave it for 30+ mins before getting annoyed and going back to pre-cupcake. But it's unusable like that.
I'm thinking it might be a partition issue. What is the recommended filesystem to use? I have a 2GB card and i can't remember what partitons i have atm. I think it's half ext4 & half fat32 or something like that. Can i set the whole 2GB as fat32, then flash the rom? Is that recommended? If so, how do i do it without using the partition script?
Thanks in advance
I dont remember if ext 4 is supported in CyanogenMod, I reccomend ext 3. No its not required to have a ext partition, itll just store apps in the phones internal memory.
It was actually ext2 i was using, couldn't remember. I tried to fix the filesystem in the console and it gave me an error. So, stupidly i went into gparted and deleted the partitions, thinking i could create them again. But i'm having a little trouble now, i'm stuck in the console and i know if i reboot, i won't be able to get back into recovery mode...
How can i create a single fat32 partition in the console?
I can't do it in Linux or in Windows
Nvm, got it back into pre-cupcake...let's see if it'll flash properly with a fresh fat32 partition
How about using Paragon Partition Hardisk Manager 9, it should work, I used it...
Amon Ra's recovery image 1.5.1 allows you to format and upgrade partitions from the console.
Cyanogenmod supports ext 4
Ext 2 sux if you're trying to run apps2sd
ext 4, 10 mb hack, and zipaligned = Super FAST rom!
Ok, i tried installing cyanogen. It got to the android screen, then just went black. It was illuminated, but black. This is the same strange behaviour i was having with Xrom. It seems like my phone can't use anything but official roms now. I dunno what has happened to it. I did drop it for the first time a few days ago, but surely then the vanilla roms wouldn't work. I'm back on 1.6 now, and it seems to be working ok...I'll give cyanogen another try later i think.
Hmmm, so i bought a new sd card and now i'm running cyanogen flawlessely. Thanks for the help
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
Hello @all XDA User´s
It concerns the following ROM!!
http://forum.xda-developers.com/showthread.php?t=1275119
I do not know any more further, my Leo always hangs in the Splash Screen. Has already installed both versions Themed and Stock EU / MAGLDR. Both versions tries with 1 GB and 1.5 GB EXT4 about CWM Recovery. Started by partition size raises 5/172/5 gradually on mb 8/205/8. I had everything always with a clean installation (Task29 / MAGLDR1.13 / Recovery). Before the installation Wipe Cache, Dalvik Cache, check MD5 O.k. The problem already with V 3.1. What can I still trie?
I pursue this Thread are everyday to the version 2.1, and reads every post. As I could ascertain still 2-3 other users this problem. Up to now, however, became only this get another SD Card to be of use or to change the partition size because of bad Blocks.
All versions to 2.6 were always trouble-free.
I would clarify with pleasure with this quick nice ROM remain and would be very grateful for other tips.
My data:
HD2 EU 512
HSPL 2.08
Radio 2/15/50/14
MAGLDR 1.13
SD Card SanDisk 8 GB Class4
This can be right. Am the phone in load, CWM Recovery openly, accumulator with approx. 90% and thinks to me flash Rom over again about freshly . The last attempt. And see there, it suddenly functions. It jumps from the Splash Screen in the boat animation and boots up my hotly desired V 3.3
Can it be it lies in the connected loading cable? Had installed before always without cable accumulator approx. 80%.
I would use CLK, are you still having issues? Which CWM/ EXT4 are you using?
Question: How can I free up the internal space again?
I've searched and apparently it's very easy to do:
1. Just load up the stock recovery and do a factory reset...problem? Stock recovery just goes to the error screen (sad droid with exclamation in background).
2. Okay, just flash an sbf with more space...problem? I'm one of those people who flashed a GB with CG39 @ v.5, so my options are limited...tremendously so.
3. Perhaps flash that sbf that works, restore from nandroid...problem? Done, great, this is how I can get to CM7.2 or CM9...still 128MB internal. Why? The only nandroid backup I knew of that would help me out is no longer available (See common problems/questions here)
So really it's a single question, but either of two answers would work:
1. Anyone know how to fix the stock recovery?
2. If not, how about a nandroid backup with more internal memory space.
Any help is greatly appreciated!
Your answers::
I've searched and apparently it's very easy to do:
1. Just load up the stock recovery and do a factory reset...problem? Stock recovery just goes to the error screen (sad droid with exclamation in background). Soln: Its not error. After the exclamation press both vol+ and vol- together or vol+ or vol-. That is how you enter stock recovery.
2. Okay, just flash an sbf with more space...problem? I'm one of those people who flashed a GB with CG39 @ v.5, so my options are limited...tremendously so.
Soln: CG39 with v5 is not that bad! There are many BL5 Froyo SBF should you want a fll SBF. But even after full SBF you will have to do a data wipe from stock!!
3. Perhaps flash that sbf that works, restore from nandroid...problem? Done, great, this is how I can get to CM7.2 or CM9...still 128MB internal. Why? The only nandroid backup I knew of that would help me out is no longer available (See common problems/questions here) Soln: Not sure. try data wipe from stock. Even after Nandroid do a data wipe. Either from CWM or stock recovery..
how did you manage to fill up alll that space?! I have about 120 apps installed and still have more than 500MB free!!
Finally got it working. I noticed shortly after I posted that, just like you said, the exclamation isn't an error...I should have clarified that the vol+ and vol- together wasn't doing anything.
I was going to write down what I did to remedy it; however, after writing it all out, it didn't make sense (completely unrelated things appear to have fixed the issue).
Trouble is, I'm still stuck with no space. I finally got to do the stock wipe and I'm still ending up with 128MB total for any of the roms. Anyone got some suggestions?
Just to be clear, it's not that I'm starting with 1.3 GB and installing enough things to get down to 128MB, it's that if I go to the properties for the device, the internal memory says it has a total of 128 to start with (typically ~60 free on first boot of most roms).
jebrew said:
Finally got it working. I noticed shortly after I posted that, just like you said, the exclamation isn't an error...I should have clarified that the vol+ and vol- together wasn't doing anything.
I was going to write down what I did to remedy it; however, after writing it all out, it didn't make sense (completely unrelated things appear to have fixed the issue).
Trouble is, I'm still stuck with no space. I finally got to do the stock wipe and I'm still ending up with 128MB total for any of the roms. Anyone got some suggestions?
Just to be clear, it's not that I'm starting with 1.3 GB and installing enough things to get down to 128MB, it's that if I go to the properties for the device, the internal memory says it has a total of 128 to start with (typically ~60 free on first boot of most roms).
Click to expand...
Click to collapse
Oh is it?! Well though oriole say defy and defy + have similar memory am not sure how much one gets in defy after a full data wipe! However m sure it will be more than 128mb! Even after full sbf you get 128mb right?! M sorry but if that is the case dunno what would be the solution!
Sent from my MB526 using XDA