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
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
I'm stuck on a friend's nook.
I've flashed mine about 100 times no problem.
I've put cyanogen on two other nooks no problem.
I'm doing something wrong with this one I guess.
I have a bootable CWM micro SD and I can boot to it no problem, I'm trying to flash the latest nightly.
What I did up to now was flash the repartition data and reformat data zips.
Then I formated system, data and cache.
Then I flashed cyanogen.
I got it to load cyanogen one time!
But when I rebooted I could never get it to load again.
Since then I have formatted the boot and flashed a few different boot fix files.
I'm stumped.
When I boot it now it goes to the green Cyanogen mod banner, than a second later it says 'loading' under that, then it goes to a black screen. I have to hold the power button down for 15-20 seconds after that to shut it off.
So I have a nook that I can boot to CWM v3.2.0.1 from a micro SD card.
What steps should I take to get this thing working again?
What I did up to now was flash the repartition data and reformat data zips.
Click to expand...
Click to collapse
That wasn't really necessary with CWR 3.2.0.1. I would say drop a copy of the stock 1.3 ROM on the SD card, boot up and start all over wiping data, system, cache and Davlik and then install the stock .zip. That will get you back to the very beginning. Stock full ROM is here: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Courtesy of Taosaur : http://forum.xda-developers.com/showthread.php?t=914690&page=28
patruns said:
That wasn't really necessary with CWR 3.2.0.1. I would say drop a copy of the stock 1.3 ROM on the SD card, boot up and start all over wiping data, system, cache and Davlik and then install the stock .zip. That will get you back to the very beginning. Stock full ROM is here: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Courtesy of Taosaur : http://forum.xda-developers.com/showthread.php?t=914690&page=28
Click to expand...
Click to collapse
Tried that, Now I get 'Read Forever' then a quarter second of the 'N' screen that is Grey then turns a sort of washed out in orange color for a half second, then a message screen that says: 'Install Failed' over a picture of a nook with a red exclamation mark on the screen and 'Please power OFF and back ON again. If you continue to have issues please contact Customer Support or visit www.nookcolor.com/support' Then the device turns itself off.
I had gotten that screen a couple of times leading up to this. Got rid of it by flashing some boot fix files or something.
Something is wrong with the loader or some boot data or something I don't know about.
Can anyone give a step by step on how to take a Nook down to a clean slate then build it back up so I can boot Cyanogen nightly?
I can Boot off a micro SD into Clockwork Recovery.
Those were the steps I took to restore and deregister a Nook recently before returning it for a replacement. However, I never messed with the partitions. Someone familiar with the partition structure will hopefully chime in.
Bump having the same issues. Just started today.
Mine works if I leave it charging, As soon as I unplug it..it turns off.
CM7 and 1.3 ROM hang ups
patruns said:
That wasn't really necessary with CWR 3.2.0.1. I would say drop a copy of the stock 1.3 ROM on the SD card, boot up and start all over wiping data, system, cache and Davlik and then install the stock .zip. That will get you back to the very beginning. Stock full ROM is here: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Courtesy of Taosaur : http://forum.xda-developers.com/showthread.php?t=914690&page=28
Click to expand...
Click to collapse
First tried to install final CM7.1.0 over nightly. Followed instructions here on Opening page Nook Color Android Development thread for this and then tried step-by-step Maurice Mongeon - Nook Color: updated Clockwork Recovery Bootable SD page. I left a similiar comment to this post at his page. Scroll up to see his instructions.
http://mrm3.net/nook-color-how-to-install-cyanogenmod-7-1/#comment-1069
From his site: Everything good from ROM Manager making sure latest CWR 3.2.0.1 until reboot into recovery. Get dark purple-black screen, have to power+n force it into internal CWR 3.2.0.1. Gets through Install from sdcard complete. Mounts and Storage > format /cache > Yes – Format gives me Error Formatting /cache!.
If I try format /system… it hangs. Reboot into CWR again it hangs again at Formatting /system… No way to format system, data, cache from Mounts and Storage to boot into clean new ROM!
I can use – wipe cache partition and – advanced > Wipe Dalvik Cache instead afted installing – update-cm-7.1.0-encore-signed.zip (correct checksum) from sd-card. Everything goes OK except it boots back into CyanogenMod-7-08192011-NIGHTLY-encore.
Restoring previous Nandroid from internal CWR or SD CWR also hangs at restoring /system. What should I do? Can not update or get it back to original 1.3 ROM either? Lockups and errors in Mounts and Storage formats stop me! Tried suggestions in this thread using the boot SD version of ClockworksMod Recovery, none of them seem to work. Anybody have any suggestions as to what to do next?
@ Izord and lschroeder.
If you guys absolutely cannot get it going with CM7, I then suggest trying to get back to the original, stock ROM.
If you had formatted /boot, then I cannot help since I never did mine so I don't know for sure but if not, you should be able to bring the NC back in the original stage.
votinh said:
@ Izord and lschroeder.
If you guys absolutely cannot get it going with CM7, I then suggest trying to get back to the original, stock ROM.
If you had formatted /boot, then I cannot help since I never did mine so I don't know for sure but if not, you should be able to bring the NC back in the original stage.
Click to expand...
Click to collapse
I can not get to stock ROM either, format/system... hangs and I have to hard reboot.
Question for anybody: Can I use ADB or adbWireless to help get around the format/system... error and install CM7.1.0 or Stock 1.3?
Sorry to resurrect an old thread but this is the only place I've found that describes my problem. I'm experiencing the exact same thing with my Nook Color and followed the exact same suggestions without success.
Was this ever resolved? What finally made it work?
This is exactly what is happening to me. I've already posted my problem to another thread but I thought I would comment here in case this thread finds a resolution.
BTW, my thread is http://forum.xda-developers.com/showthread.php?t=1578127
My Vibrant (which is not rooted at all, its 2.2) is not starting up properly. When I start it up, it makes it past the S logo and it only shows the notification bar (which has the time, battery status, etc.) at the top which doesn't go down when I pull it down. Everything on the screen under the bar is just blank black and every 10 seconds it all goes blank and the notification bar reappears again and that's all.
I've tried taking out the battery and restarting several times. I've also held down the 2 Volume (up & down) keys while holding down Power and entered the recovery menu thing which has some options for me. I see: reboot system now / reinstall packages / delete all user data / delete cache data / format internal sd-card
What is wrong with my phone and what do I do?
Any answers would be greatly appreciated. Thanks.
Do you know what Odin is?
I've seen Odin around here a lot, but I'm not fully aware of it. Would it be helpful in my case?
Will it delete all my data from my phone or just the apps? If so, is there any way I can fix my phone without deleting my photos, videos, music, etc. I don't care if some apps get lost but I want my media.
Odin will delete your apps but it will not lose your Photos, Videos, Music, any of that stuff. It resets your phone to stock state (2.1 eclair) and doesn't touch the internal SD (unless you tick Masterwipe-so don't do that).
I posted this in another thread but it'll do for you too.
Go to the Dev section and download tha AIO Toolbox (Stickied at the top). It has the Odin v1.8 (I think), all the drivers and pit/tar files that you need to get back to stock 2.1 and then you can download CWR from my signature, find a ROM.zip that you want to install and put them on your Internal SD card.
Make sure you put the ROM in a folder and also make sure that the CWR that you get from my sig is on your internal and is the only thing on it labeled Update.zip. Once those are done, boot into recovery, scroll down to "Reinstall PAckages" and hit it. Let it cycle through and you might have to do it again. Once it cycles through your recovery will go from Blue (stock) to Green (CWR) from there, you can flash your ROM and profit. [If you are going to an ICS flavor, you may have to be on GB bootloaders and flash CM7 as an intermitant step. I suggest trying Moped_Ryder's ROM and Fishman's Bionix Mod-both 2.2 but quality and everything works.]
The toolbox is a valuable thing and you can do many things with it, but mainly and most importantly, it HAS the files to get you back to TMo 2.1. (I use it all the time and I am not even a TMo customer).
One thing you could try before going the Odin route that Woodrube mentioned(which sounds like what you're going to have to end up doing anyway) is find a CWR (Clockwork Recovery) zip file that you can install. You can find them somewhere on XDA if you do some searching; should be a little under 2 megs.
If your status bar comes up, even briefly, are you able to mount your phone on your PC and copy a file over? If you can, I'd say try putting that CWR zip file (renamed to update.zip) on your internal SD (where everything else is) and in the recovery you can get to now do "reinstall packages".
It'll load up CWR (you may have to do that "reinstall packages" twice), and you can do a couple of last ditch efforts. Wipe the cache, go to advanced and wipe the dalvick cache, and then fix the permissions.
You don't have to be root to do that, and while a long shot it may at least get you back to workable. But even if you do you should still backup your apps and goodies in preparation to Odin back to stock and format everything. I'm a big fan of clean wipes when things get all quirky like that.
Why don't you just root it while you at it its makes life easier lol
Sent from my Sensation using xda premium
I would recommend trying out a custom rom if you are going to Odin anyway. I had numerous issues with Samsung's software. You can Odin flash quite a few custom roms as well.
Sent from my SGH-T959 using xda premium
TLDR: See this post for the solution; but do read through the thread, lots of good info!
I've got a MB525 for parts, seller got rid of it because it won't boot up anymore. I've tried it and it shows black screen but it can be seen over USB and I can flash .sbf files. Now, I'm curious whether it can be made to work after all.
First I've tried most of the smgver=4 stock .sbf files but no luck, still got black screen. From what I've read, black screen means the efuse has blown to a higher version. So I tried the JORDN_U3_97.21.51 (smgver=5). Still nothing.
The only thing left would be to flash a Defy+ .sbf, I've seen people recommend DFP-231 Taiwan retail or similar, hopefully a smgver=6 or 7 would work.
I've no idea what the seller did to the poor thing, nor what ROM it came with originally or from where.
Am I right that I should try a Defy+ .sbf? On the one hand, no risk really, I got it for pennies so no big loss. On the other, it just irks me that a potentially fully working Defy should just be abandoned for scrap.
You can try it. But if your defy is green lens the camera won't work on stock Rom only on custom Rom CM10.....CM11.
Sent from my MB526 using Tapatalk
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
wirespot said:
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
Click to expand...
Click to collapse
Try DFP-231. If it works, you can go ahead with custom ROMs.
I've successfuly flashed DFP-231. By "successfuly" I mean it now shows the Moto logo and I can enter bootloader (version 10.00, FWIW) and the stock recovery.
But it won't go past the Moto logo, shows it for about 10 seconds and then it reboots, forever. I pulled the battery after ~10 reboots in a row.
Yes, I did a factory reset from recovery (ie. cache and data wipe).
Any idea what might be causing this or what else I can try?
Try to reflash sbf.
And say "bye" to your battery charging via phone.
I've been trying all kinds of DFP-231 .sbf images. So far no luck, still got a few to go. Some of them have a longer delay, such as the first Moto logo staying on for more than 10 seconds – some for 20-30 seconds... but eventually they all bootloop.
I have another Defy+ so I can charge the battery through that one, but why do you say I can't charge through this one anymore?
PS: I've just realized that the stock recovery can flash stuff from the SD card. Would it be ok if I take a nandroid backup and slap it in there? Does it matter from what kind of system the backup is from eg. stock, a CM version etc? Or will anything work?
For battery you can check lasts posts of my problem here http://forum.xda-developers.com/showthread.php?t=2568049... I have never solve it .
Try ti omap blank flash option in rsdlite
Stock recovery cannot help unless you can brute force or steal Motorola's private key
You could try making a custom sbf, which would include custom recovery, from where it could work out.
@sterver1 the battery issue is an exception, it does not occur for most
Sent from my MB526 using Tapatalk 4
Oh, so ok. I'm only unlucky...
Good luck...
Still no go unfortunately.
I tried DFP-231, including with TI OMAP blank flash option. If TI blank flash didn't work, am I looking at a hardware problem?
To recap: it's a MB525 (unknown whether red or green) stuck in bootloop: will show Motorola logo for ~10 seconds then restart and repeat forever. I can enter bootloader and flash SBFs but so far none of them helped. I can enter stock recovery and wipe /data and /cache, still no help from there. It was already at BL7 when I got it (tried lower versions first and got blank screen, only BL7 will allow it to boot).
Cannot flash ZIPs from stock recovery because it will only accept ZIPs signed with Motorola's private key which I obviously don't have.
I've read that the wrong region SBF might be the bootloop cause so I will still try out the rest of the official BL7 SBFs, just in case.
The only thing left I can think of is to somehow put custom recovery in there so I can try flashing a custom ROM.
But how do I build a custom SBF with 2ndinit and CWM or TWRP? I have the unpacker and I know how to unpack and repack a SBF. I also know that CG39 is an ext3 image of the /system partition, but that's about it. Which CG files do I have to modify and how?
I'm also not clear on what a "fixed SBF" is. I've noticed that it usually contains only certain CG files, but not sure how it works together with other types of flash and what good are they.
You can flash one of the cm 10 sbfs in the dev forum. Basically you need the sbf to contain the boot menu and recovery to try flashing from custom recovery. A fixed sbf is used to prevent bl version from incrementing by removing the higher version files
Sent from my MB526 using Tapatalk 4
I did it! The SBFs that did the trick are the ones in the OP in the thread Motorola defy bl7 sbf all in one. First the Asian Retail BL7, then wipe from stock recovery, then the MIUI SBF (which also contains CWM custom recovery). Then it booted right up.
I'll be back with more info about this Defy just returned to the land of the living after I poke around a bit (the MIUI ROM is in Chinese, gotta figure out how/if I can switch to English...)
So! Once again it's been proven that it's nearly impossible to softbrick a Defy. Given enough obstinacy ^_^ you can find a SBF that will put it right again.
PS: I should probably also add to the wiki page various stuff I've learned while doing this. I've had a hard time looking up some info, maybe it will help others.
Aaaand I spoke too soon. It booted MIUI successfuly exactly once (1 time). Now after the Moto logo dissapears I get a blank screen (but lit, not off) and nothing happens. I also tried a CyanogenMod ROM (Quarkx), both 10.0 and 10.2 – the CM spinning logo appears, it goes on for a while, sometimes it attempts to boot (got to the Dalvik generation, for example) but then it reboots, other times it will keep spinning and nothing happens.
On the bright side, I now have access to the advanced bootloader and custom recovery with all the goodies (ADB shell etc.) which opens up possibilities. If anybody has any ideas what I could try to diagnose this, please speak up – like I said, I can now have access to the actual Linux system on the phone.
The only idea that pops to mind right now is the CPU settings. Maybe it got overclocked by the original owner and something got fried? Resetting them to defaults didn't seem to do anything.
Still no luck. The MIUI I linked above is the only one that boots up, but won't recognize the SIM card and claims there's no GSM connectivity.
I'm speculating that perhaps something is messed up with the radio hardware, and that MIUI is the only ROM that somehow works around that and boots up, but the other ROMs don't expect it and reboot halfway through the bootup sequence.
I'll see if there's any logs made during bootup.
The reboots are characteristic of bad eMMC(data not getting wiped properly). Does miui work fine apart from radio? Also 2ndboot builds require a specific stock kernel(from eu dfp 231) so try that as well. Try full wipes from cwm, and make sure the data partition is formatted correctly from boot menu(ext3 for ics and below, ext4 for jb+).
The miui sbf masked the data problem(atleast temporarily) allowing the phone to boot up. Unfortunately if you do have other /data issues(which are seemingly unrelated), they all point at bad eMMC, necessitating replacement of the motherboard as the only viable option.
Sent from my MB526 using Tapatalk 4
@thekguy: Yes, apart from the GSM MIUI seems to be working fine, including WiFi. But only one time, if I reboot it doesn't start up again. Sometimes I get a hanged boot logo, sometimes I get endless bootloops. Other ROMs never work, it's straight to hanged or bootloop.
Are you saying that the internal memory has gone bad, like an HDD getting bad blocks? If that's the case, I can probably use a recovery update script to repartition the memory and work around the bad zone(s). As long as I can figure out which exactly are the bad zones (other than trial and error).
Or are you saying it's simply not getting scrubbed properly and it's a problem with the filesystem? In which case I can reformat at least some of them (/system, /data/ and /cache).
But doesn't the flash tool overwrite the partitions by raw-dumping images on them? So how can a bad filesystem survive SBF flashing?
And what about update zips? Do they reformat/raw-dump partitions – or do they just take the filesystem for granted and copy to it?
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.
I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.
A log obtained via adb should be able to verify the same
Sent from my MB526 using Tapatalk
thekguy said:
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.
I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.
A log obtained via adb should be able to verify the same
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
If the bad eMMC blocks are entirely within the ext3/4 partitions, we should be able to run badblocks on them (taking care not to overwrite the signature at the end of /dev/block/mmcblk1p21 but past the actual file system) and avoid them. As the badblock list is stored in the file system rather than the partition table, I believe that would work.
I've also been experimenting with using an SD card partition for /system and keeping only a few minimal files on the eMMC (I think we could get away with busybox and a modified logwrapper script)—no unexpected problems. It's quite likely those two files won't interfere with the bad blocks, and after they've booted the kernel we wouldn't be touching the eMMC at all (assuming /data and /cache are also SD partitions, but that should be doable). I have been using Quarx's CM11, and I don't think my trick works with stock ROMs (at least I've never had success booting a stock kernel with 2nd-boot), so it might not be a helpful suggestion.
2nd system/ multiboot is a good idea to get past the bad blocks (probably some performance hit though) but better than a non functional phone. 2nd system should work even with a stock ROM as secondary system, not sure why it isn't working for you. I have no idea about the badblock remapping logic
Sent from my MB526 using Tapatalk