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
I am prepping to move my CM7 install from SD to EMMC and had some questions for you gurus out there:
1. Is it possible to dual boot stock unrooted 1.2 and CM7 on EMMC? I would like the freedom to be able to install CM7 nightlies without having to wait for custom-prepped dual boot roms, so it's not 100% necessary if that's not possible. Is it relatively easy to revert back to single-boot stock? (Is it just a question of resizing partitions and removing CWR?)
2. If #1 isn't possible, do I need to de-register my NC before installing CM7 to replace stock? I had read somewhere about an issue of nooks not being de-registered before doing something then people unable to re-use stock back. Vague, I know. 2. NM, I believe it was regarding rooting stock prior to registering with B&N. Someone correct me if I'm wrong.
3. Is the performance difference worth it to even install CM7 to emmc vs using it off SD? Currently using a decent 4k-write etc. Sandisk 16GB class 4 uSD.
4. Any issues/problems with running CM7 off EMMC vs SD (besides the obvious voiding warranty, etc.) The only thing I could think of would be if I accidentally damaged the NC by dropping it (or it just dying randomly) and being unable to restore to stock to avail of my extended warranty with Best Buy.
Thanks for any help, I'm loving the Nook Color.
I can answer #1, as I am doing exactly that. I followed this walkthrough:
http://www.mobileunderground.info/showthread.php?t=51217&p=84794
and it came out perfect. Puts CM7 as the main boot and stock 1.2 and the secondary boot partition. Now I can update the nightlies without a hitch. No need to worry about a special dual boot zip because the stock is in the secondary partition and isnt affected when doing the flashing the normal way.
Answer to
no 3. YES installing CM7 is a huge boost on mine
no 4 I think if you have hardware failure (ie. dropping it) and you cant turn it on, best buy wont be able to do it as well. They just replaced you with a new one. It happens to me they replace my nook with a new one the same day (I rooted and load froyo on my old nook)
Took the plunge 10 mins ago, and man my uSD card was no slacker but it's like a whole new machine! Thanks for answering --- decided to not bother dual booting, bluefire ereader is coming out sometime next month for android and that should fix my reading needs then, for now I'll live with terrible nook app (I don't read mags or kids' books anyhoo)
If you aren't dual-booting, what did you do?
I'm considering the same thing, I've got CM7 on the emmc but I haven't moved over the app data; does just copying /data work?
I am used to rooting and nandroiding ROMs, at least on my phones: Hero, OG Evo and 3D Evo, but at this point I'm not rooting my NC. I want to back up my stock NC, which presumably has 1.3 on it, as I got it for Christmas. I ran roustabout's script to stop OTA updates. I might want to try the update, eventually. Hence I'd like to back up the stock ROM I have now, and be able to restore it, in case I don't like 1.4.1. Thanks for any help in advance. I did search, but since I'm not rooting, wasn't sure how to do it.
BTW, using Racks' multi-boot from SD card, I can boot into either CM 7.2 (Kang) or ICS. It does what I want, and runs pretty fast from my SD card. And, if I'm at B & N, I can remove my SD card, boot into the stock ROM and still read for free!
Just make a bootable clockwork card and use the backup option and you will get a nandroid of your current set up.
Sent from space
So this morning, on my ATT GS4 NC1, I went into safestrap and created a new installation on rom slot 1. I guess that's what you call it. I pressed rom slot 1, then wiped, then installed hyperdrive. The install went fine and afterwards, I installed the NC1 module.zip and the SU zip file (both found in the "all things att" thread under "NC1 instructions".
Once it was done, I rebooted but what it did was boot to the regular stock rom. All my screens were the same (app placements, settings, etc) but I noticed I had no cell signal. I went to settings>mobile network and it said something about needing to install a sim card. Sorry I can't remember exactly what it said.
Anyhow, I went into safestrap, rebooted and then activated the stock rom slot and booted. Everything is fine.
What happened? Any ideas as to what happened? As of right now, I am running on the stock slot using the stock rom pending suggestions from you all.
Thanks!
KitKat ROMs will work only when flashed to stock slot.
jmjoyas said:
KitKat ROMs will work only when flashed to stock slot.
Click to expand...
Click to collapse
Ok, that makes sense. I just did it using the stock slot and it works. thanks!
burgertime78 said:
Ok, that makes sense. I just did it using the stock slot and it works. thanks!
Click to expand...
Click to collapse
Hmm I've been wondering this since I've not had success in doing so either. So what your saying is that it HAS to be done on STOCK slot in order for the rom to work? I've been scratching my head to why it refused to work for me. So it's safe? I had accidentally erased my stock rom cause I wiped that slot by mistake. So what's the procedure? Wipe the stock slot then install the rom on it then reboot? And how would I go about getting the stock back by clearing it again and installing the back up on the same slot? Please enlighten us cause I already got stuck on the black galaxy screen losing the safestrap and I had to odin the stock tar again.
I'm on NB1 4.4.2 and off course SS 3.72 beta. Thanks.
Wanabedev83 said:
Hmm I've been wondering this since I've not had success in doing so either. So what your saying is that it HAS to be done on STOCK slot in order for the rom to work? I've been scratching my head to why it refused to work for me. So it's safe? I had accidentally erased my stock rom cause I wiped that slot by mistake. So what's the procedure? Wipe the stock slot then install the rom on it then reboot? And how would I go about getting the stock back by clearing it again and installing the back up on the same slot? Please enlighten us cause I already got stuck on the black galaxy screen losing the safestrap and I had to odin the stock tar again.
I'm on NB1 4.4.2 and off course SS 3.72 beta. Thanks.
Click to expand...
Click to collapse
Not really sure how 'safe' it is. What I did was use safe strap to create rom slot 1 and installed the rom there. It didn't work so I just went back and installed the rom in the 'stock' slot the same way - wiping first. that worked.
before I did anything, I did a full backup in safestrap. I backed up to my SD card. I'm glad I did because the rom I installed - hyperdrive - did a couple things I didn't like so I was able to reboot to recover(safestrap) and restore my backup to the stock slot. now I am back the way I Was before I messed around.
I'm still looking at other roms but I feel good I Was able to restore the backup.
here are the steps I took (I'm a noob, this may not be perfect)
1) boot to recovery in safestrap
2) make sure 'stock' is active - this means that the 'install button' is red
3) perform advanced wipe on stock slot - all but external sd card
4) press 'install' and install the rom
5) exit installer and then install NC1 ATT module
6) then install SU module
7) reboot - all is good
Awesome!
burgertime78 said:
Not really sure how 'safe' it is. What I did was use safe strap to create rom slot 1 and installed the rom there. It didn't work so I just went back and installed the rom in the 'stock' slot the same way - wiping first. that worked.
before I did anything, I did a full backup in safestrap. I backed up to my SD card. I'm glad I did because the rom I installed - hyperdrive - did a couple things I didn't like so I was able to reboot to recover(safestrap) and restore my backup to the stock slot. now I am back the way I Was before I messed around.
I'm still looking at other roms but I feel good I Was able to restore the backup.
here are the steps I took (I'm a noob, this may not be perfect)
1) boot to recovery in safestrap
2) make sure 'stock' is active - this means that the 'install button' is red
3) perform advanced wipe on stock slot - all but external sd card
4) press 'install' and install the rom
5) exit installer and then install NC1 ATT module
6) then install SU module
7) reboot - all is good
Click to expand...
Click to collapse
Holy freaking crap dude thanks! I had feeling that was the way to do it. Thanks allot man, I'm currently organizing the folders, widgets and what not so i don't have to do it again if anything. I'll venture into it tomorrow. Again thanks! You answered a long awaited question.
Just tried a tmobile rom using a "SuperSU-v1.93.Zip" and got caught in a bootloop on the set up screen and even after on the main screen. Is that the same zip you used? If not can you link me? I wonder what the hell or if anyone else has been successful with a Damn tmobile rom, i used (the warp drive rom and 2 others on the list). God it was so cool when i saw the tmobile boot screen, ugh. And to make matters worse i found out that i have a faulty motherboard with the (no Sim, phone will reboot message). Damn I'm loving this stuff, just been running into some bad luck.