A2SD with damagecontrol Rom - Hero CDMA General

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

Related

oldrom to stock(odin) to newrom 10min flat

i dont think this has been posted if so let me know and i will retract this.It is just i think the quickest way to get to a new rom while flashing back to stock first.
disclaimer:this is for people that know what im talking about. If something happens to your phone it jumps off a cliff and laughs at you or anything else i am not responsible.
alrite as usual you should have already backed up all your apps, have your new rom on your internal sd card, and odin up and ready before this.Alright so here it is i have 3 button combo working on mine if you dont use adb i guess.
Pull battery insert battery hold volume up and down and put in cable from computer to phone download mode.It should pop up press start on odin. Now wait for it to say reset then wait for the boot animation of the signal bars right when those pop up before the sound even. Now pull battery insert battery hold up down and power button untill att pops up twice.Then select reinstall packages (this is if you already have the update.zip on your sd card for cwm if not dont bother) it will reinstall clockwork mod recovery (sometimes you have to push reinstall packages twice it just depends). Almost done now just do as normal install zip from sd card select the rom of your choice and then yes(install whatever rom your wanting to flash ) then bam your done no needing oneclick root dl rom manager instal cwm from there no need to even look at it...
and there you go done in 10 min i do this everytime and have never had any issues EVER im just trying to make flashing a new rom quick and easy and id love to hear your feed back
shadowscreation said:
i dont think this has been posted if so let me know and i will retract this is just the quickest way to get to a new rom while flashing back to stock first
disclaimer:this is for people that know what im talking about if something happens to your phone it jumps off a cliff and laughs at you or anything else i am not responsible
alrite as usual you should have already backed up all your apps have your new rom on your internal sd card and odin up and ready before this so here it is i have 3 button combo working on mine if you dont use adb i guess
pull battery insert battery hold volume up and down and put in cable from computer to phone download mode should pop up press start on odin wait for it to say reset then wait for the boot animation of the signal bars right when those pop up before the sound even pull battery insert battery hold up down and power button untill att pops up twice select reinstall packages (this is if you already have the update.zip on your sd card for cwm if not dont bother) it will reinstall clockwork mod recovery then (sometimes you have to push reinstall packages twice it just depends)now just do as normal install zip from sd card select the rom of your choice and then yes then bam your done no needing oneclick root dl rom manager instal cwm from there no need to even look at it
and there you go done in 10 min i do this everytime and have never had any issues EVER im just trying to make flashing a new rom quick and easy and id love to hear your feed back
Click to expand...
Click to collapse
Can you say: Run on sentences makes no sense.
Plus, wrong section
I agree. Some capitalization and punctuation would go a long way. Also, if speed is your goal then just drop the ROM zip on the sdcard, boot to recovery and install it.
opcow said:
I agree. Some capitalization and punctuation would go a long way. Also, if speed is your goal then just drop the ROM zip on the sdcard, boot to recovery and install it.
Click to expand...
Click to collapse
im talking about speed and the rom actually booting. I have done it that way a few times and most of those times at get failure at line watever update aborted this way has worked for me 99.99999999999999999999999999% of the time
shadowscreation said:
im talking about speed and the rom actually booting. I have done it that way a few times and most of those times at get failure at line watever update aborted this way has worked for me 99.99999999999999999999999999% of the time
Click to expand...
Click to collapse
Sorry to hear about your bad luck. It has worked for me 100% of the time.
That thing should have ended with:
"Posted using a broken older version of Swype while pressing the buttons with my face"
Comma. Semicolon. Space Bar. Enter key. Period. Pick one.
Hell.......pick a bunch.
evoic said:
"Posted using a broken older version of Swype while pressing the buttons with my face"
Click to expand...
Click to collapse
That's hilarious!
Thanks for the laugh while I'm stuck in morning traffic.
Thanks, I appreciate the info. I will try this. I had no problem understanding your post, and didn't even notice the lack of punctuation. I think punctuation is way over rated, and if you are a good reader you shouldn't need it. I threw in a few periods and comas so these Cretans could understand this.
My "10 min or so..." ROM Upgrade Guide
Backup apps/data using Titanium Backup
Remove all garbage folders from internal SDCard
Odin back to stock.
Insert <AWESOME ROM XX> onto internal SDCard
Use the update.zip for CWM when rebooting into recovery. (Reboot into recovery - run the update.zip - reboot again into CWM)
Install <AWESOME ROM XX>
Sign into Google and have it replicate contacts etc.
Restore Apps/Data using TiBu.
Usually takes a little more than 10 minutes due to backup/restore of TiBu - but the actual Odin/Install new ROM part takes under that.
But this isn't for those new to flashing - beware that this process can screw up forcing you to ODIN - and if you didn't keep a copy of your TiBu restore somewhere other than your Internal SDCard you'll be fubard.
avgjoegeek said:
My "10 min or so..." ROM Upgrade Guide
Backup apps/data using Titanium Backup
Remove all garbage folders from internal SDCard
Odin back to stock.
Insert <AWESOME ROM XX> onto internal SDCard
Use the update.zip for CWM when rebooting into recovery. (Reboot into recovery - run the update.zip - reboot again into CWM)
Install <AWESOME ROM XX>
Sign into Google and have it replicate contacts etc.
Restore Apps/Data using TiBu.
Usually takes a little more than 10 minutes due to backup/restore of TiBu - but the actual Odin/Install new ROM part takes under that.
But this isn't for those new to flashing - beware that this process can screw up forcing you to ODIN - and if you didn't keep a copy of your TiBu restore somewhere other than your Internal SDCard you'll be fubard.
Click to expand...
Click to collapse
@ avgjoe This is about it. But I would add one suggestion which will help out a ton with Odin.
[*] Ensure you have a good usb cable. Make sure to wiggle the cable. If the the phone loose connection to the pc while wiggling cable save your self 20 minutes and get a good cable.
I have 5 cables. Best to worse...
- 1 BlackBerry Cable ***** Best for me. I trust it. No connection loss
- 1 Stock Jabra Cable **** Worked good for me. No connection loss
- 1 Ericson Cable shaved *** Tight fit. No connection loss
- 2 Samsung stock cables* What was Samsung thinking
This is my experience. I remember the first time I flashed my Captivate. I felt sick and I blame it on my cable. I barely touched my phone and I heard the beep-beep from my pc when it detected the USB was detached and re-attached. Atleast bricking a Captivate is better than bricking a Tilt2.
An even faster ROM upgrade guide:
-Boot into CWM
-Wipe data and cache
-Install ROM zip from SD
If that fails, try again or:
-Odin one-click (or Odin to JH7 for certain batch 1010 Captivates)
-Enable debugging and sideload z4root. Permanent root.
-Install CWM using ROM Manager or manually with the update.zip
-Follow three steps above this section.
There is usually no need to go back to stock between flashes (and there are more serious risks [soft-brick, hard-brick, damaged bootloader] from a bad Odin flash than from a bad CWM install [fc's, stuck at boot logo]). Wiping your data and cache partitions (and making sure you disabled lagfix if not supported by the new ROM) should be sufficient.
avgjoegeek said:
My "10 min or so..." ROM Upgrade Guide
Backup apps/data using Titanium Backup
Remove all garbage folders from internal SDCard
Odin back to stock.
Insert <AWESOME ROM XX> onto internal SDCard
Use the update.zip for CWM when rebooting into recovery. (Reboot into recovery - run the update.zip - reboot again into CWM)
Install <AWESOME ROM XX>
Sign into Google and have it replicate contacts etc.
Restore Apps/Data using TiBu.
Usually takes a little more than 10 minutes due to backup/restore of TiBu - but the actual Odin/Install new ROM part takes under that.
But this isn't for those new to flashing - beware that this process can screw up forcing you to ODIN - and if you didn't keep a copy of your TiBu restore somewhere other than your Internal SDCard you'll be fubard.
Click to expand...
Click to collapse
It's a rather easy process, done it like 3 already. What I hate about going back to stock using Odin is that I always have to this:
Enable USB Debugging
Root the phone
Log in so I can use the market.
Download Rom Manager, Install CWM
Reboot to stock recover.
Apply package
Apply package again.
Install new rom
I wouldn't mind but the whole process until you are finally able to install the new rom takes at least 10 minutes of tapping and typing. It's rather annoying. I'm not complaining though...
avgjoegeek said:
My "10 min or so..." ROM Upgrade Guide
Backup apps/data using Titanium Backup
Remove all garbage folders from internal SDCard
Odin back to stock.
Insert <AWESOME ROM XX> onto internal SDCard
Use the update.zip for CWM when rebooting into recovery. (Reboot into recovery - run the update.zip - reboot again into CWM)
Install <AWESOME ROM XX>
Sign into Google and have it replicate contacts etc.
Restore Apps/Data using TiBu.
Usually takes a little more than 10 minutes due to backup/restore of TiBu - but the actual Odin/Install new ROM part takes under that.
But this isn't for those new to flashing - beware that this process can screw up forcing you to ODIN - and if you didn't keep a copy of your TiBu restore somewhere other than your Internal SDCard you'll be fubard.
Click to expand...
Click to collapse
It's a rather easy process, done it like 3 already. What I hate about going back to stock using Odin is that I always have to this:
[*] Enable USB Debugging
[*] Root the phone
[*] Log in so I can use the market.
[*] Download Rom Manager, Install CWM
[*] Reboot to stock recover.
[*] Apply package
[*] Apply package again.
[*] Install new rom
I wouldn't mind but the whole process until you are finally able to install the new rom takes at least 10 minutes of tapping and typing. It's rather annoying. I'm not complaining though...
Wiping your data and cache partitions (and making sure you disabled lagfix if not supported by the new ROM) should be sufficient.
Click to expand...
Click to collapse
Would it work if you install the rom, THEN, flash a kenerl that supports lagfix (without rebooting at all)?
Xstop said:
Can you say: Run on sentences makes no sense.
Click to expand...
Click to collapse
agreed. someone should start drinking decaf
sent from the midget in mah belly
cumanzor said:
It's a rather easy process, done it like 3 already. What I hate about going back to stock using Odin is that I always have to this:
Enable USB Debugging
Root the phone
Log in so I can use the market.
Download Rom Manager, Install CWM
Reboot to stock recover.
Apply package
Apply package again.
Install new rom
I wouldn't mind but the whole process until you are finally able to install the new rom takes at least 10 minutes of tapping and typing. It's rather annoying. I'm not complaining though...
Click to expand...
Click to collapse
you never have to log into your JF6 stock rom if you odin back to stock. you dont even have to boot to it. just keep the update.zip from CWM on your sdcard and boot into recovery...reinstall packages, and you are in CWM..flash your ROM, and enjoy
Nobody master clears anymore?? I do, and never have a single issue or FC. It just takes an extra five minutes to do the MC and then let the phone boot and transfer ROM of choise as well as update.zip for CW recovery to the root of my sd. But master clear is the same as a reset or a data wipe, so its not completely necessary. Just makes me feel safer!
silverslotcar said:
Nobody master clears anymore?? I do, and never have a single issue or FC. It just takes an extra five minutes to do the MC and then let the phone boot and transfer ROM of choise as well as update.zip for CW recovery to the root of my sd. But master clear is the same as a reset or a data wipe, so its not completely necessary. Just makes me feel safer!
Click to expand...
Click to collapse
nope. i never do any more. sometimes i have to flash back to stock, when i have a broken flash, but i still dont master clear. you dont actually gain anything by master clear, since it just wipes your internal sd...
>>[*] Log in so I can use the market.[*] Download Rom Manager, Install CWM
you can skip that step by simple "recycling/reusing" the recovery-update.zip from CWM. Download it once and then save it on your external sd and your pc.
When you want to use another ROM you can reuse the recovery-update.zip .
Just rename it update.zip and then reboot recovery and then do you thing.....
cumanzor said:
Would it work if you install the rom, THEN, flash a kenerl that supports lagfix (without rebooting at all)?
Click to expand...
Click to collapse
I've heard it's a bad idea to install kernels without first allowing the phone to fully boot. I've never tried it myself, I just convert to rfs without any backup or restore (using the ULF included in hardcore's Speedmod kernel) before flashing.
Stupid Questions
This is a stupid question (two actually). I think the answer is YES, but I'd like to make sure...
I've installed several ROMs by the "standard process."
Is the "update.zip" on my internal SD card the one that has cwm?
Does running "reinstall packages" from stock recovery just apply the "update.zip"?

So I installed clockworkmod

As the title says, I installed clockworkmod, but don't really know what to do next. When I installed it, it basically erased my nand and left me with no OS. From what I gather, this is right, and the machine would have been ready at that point to run update.zip files off of the sd card? But I can't get the computer to recognize the device at this point to place files on the sdcard. In addition, I had formatted my sdcard as was suggested, so I was stuck in clockworkmod, with a blank sdcard and no way to access it. Did I do something wrong? I'm sorry to sound like such a n00b, but I am trying to teach myself as much as I can about all of this with what I can glean from these forums, but this whole clockworkmod thing seems to get glossed over. I am also a bit confused as to what nandroid backup is. Thanks for the help.
You can mount your SD card in CWM, browse the menu a bit and you'll find it. Then copy your build.zip (it doesn't have to be called update.zip persé) to your SD card, unmount again and run the zip updater, all done through CWM. Easy as pie!
Nandroid backup is a full system backup to your SD card. It is advised to take one before flashing a new rom. If something goes wrong or you just don't like it, you can restore the nandroid backup and all your apps, settings, texts, ... literally everything are back to normal. Nandroid backups and restores are all done through CWM too.
What I appreciate most about having a recovery is that you don't need a computer anymore. Just download a rom to your SD card with your phone, boot into CWM, flash it, and voila, you're good to go. Got some sudden troubles? Just temp restore that nandroid backup from a couple of days ago and you'll manage till a computer is within reach. And so on...
Edit: I haven't slept for 40 hours, it's ****ing hard to read every word of a text right now so I'm just picking some and making the best out of it. I hope I correctly understood what you asked, if not I'll try again tomorrow.
To be honest, I'm not 100% steady when it comes to ClockWork Mod. I installed the excellent NexusHD2 Gingerbread NAND ROM, and that is "ClockWork Mod ready". I've used it for backing up my current build before trying another one, and then restoring everything afterwards, and I've also installed a couple of updates (GPS fix, YouTube delay fix).
I don't know about retro-fitting it to a ROM that you already have flashed on your device. As you say, you lose your current ROM, so I don't see how that's useful. (That's probably my lack of understanding of CWM, and I look forward to more educated responses on this thread!)
My recommendations would be to either spend the next couple of days reading up about CWM and find out exactly where you stand with it, or do what I did and just get a ROM that has it built in.
thanks guys. I think I'm figuring it out. If I have any more probs, you'll hear from me LOL!!

[Q] Can't boot... have been meticulous... Help please?

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!

sd-card

how do I un-partition a sd card? running a rom and was just showing b not telling me how much space i have left or anything. was not even telling me how much internal memory i had on phone
reformat it....
copy all your contents off the card..reformat and go from there..
sd card
crstfr said:
reformat it....
copy all your contents off the card..reformat and go from there..
Click to expand...
Click to collapse
ok i got that copied now it is sticking on splash screen. did a battery pull and still sticks on spash screen. did I ruin my phone.
Callie_evo said:
ok i got that copied now it is sticking on splash screen.
Click to expand...
Click to collapse
can you get to recovery?
try flashing a new rom?
i mean your not to borked.. it still somewhat booting!.. your not dead in the water yet
crstfr said:
can you get to recovery?
try flashing a new rom?
i mean your not to borked.. it still somewhat booting!.. your not dead in the water yet
Click to expand...
Click to collapse
yes i can get into recovery. I tried flashing synergy rom. would it be best to just run the ruu and redo the rooting process?
Reformatting is by far the best way. There is a remove sd partition selection in ClockWorkMod and Amon Ra recoverys,but ive never used them,bcuz i have no need to partition my sdcard because i always have 150mb,or more,free space,no matter which rom i use or what apps i add/install(original Evo 4G).Id simply copy the contents of your sdcard to your computer,then reformat the sdcard,and reinstall the content back to your sdcard.I dont suggest the remove sdcard partition method simply because ive never used it. Good luck.
thank ibcary we got that far now i'm just stuck on the splash screen. the reason for wanting to get rid of the partion is cause it was just saying b. not giving me any info on the card.
If u can get to recovery your doing good. Use Amon Ra if possible. CWMod doesnt always do a full wipe. id try going into recovery and perform a full wipe,wipe dalvik,wipe data,etc,etc...Then download a rom that u know works and is stable. I like MikGs Sense 2.1/3.0 roms,but which rom all depends on your device. Choose a rom thats well known to be a good,stable rom.Try flashing the newly downloaded rom from your sdcard thru recovery and if that doesnt work,then id try using a new/different sdcard. Sdcards dont last forever,and some are downright junk. As long as u can get to your bootloader theres still hope. Im sure your device is ok,but it could be a bad sdcard or a bad rom download. Thats why i recomended a new rom download,and if that doesnt work then try a new sdcard. Goodluck
ok. it was a new sd card that i partioned. am download a rom that I have used before and never had any problem with. but if this doesn't work should i just unroot and run the ruu and start over again?
how do i load the rom onto the sd card since it gets stuck at the splash screen??
Callie_evo said:
how do i load the rom onto the sd card since it gets stuck at the splash screen??
Click to expand...
Click to collapse
mount the SD card from recovery and then flash it in recovery.
Holsum said:
mount the SD card from recovery and then flash it in recovery.
Click to expand...
Click to collapse
thanks you Holsum will give it a try.
once you have root and busybox installed correctly theres not much unrooting and then rooting again will solve.Except to return your device to stock,and to unroot i usually flash the unrooted stock rom. U can try the Root Checker app from the Market just to make sure your rooted and have busybox installed correctly. However custom roms are already rooted and have busybox installed correctly. If its a new sdcard id still try another sdcard. Use an sdcard u know is good. I bought a few cheap sdcards that were 8GB class 10 becuz i got a great deal on them,10 for $110.but out of the 10,only 7 were even recognized by my Evo or my HP dv7 Netbook and worked.Also i highly doubt they are class 10,bcuz my SanDisk 16GB C10 sdcard is much faster,and older too. So just bcuz its new doesnt mean its good.If it still wont work after a fresh wipe using Amon Ra recovery,NOT ClockWork Mod recovery,and a fresh/newly downloaded rom flashed from a different sdcard using Amon Ra recovery to fully wipe,then flash the newly downloaded rom from the different sdcard to your device. That shud work,but if it doesnt u can try reinstalling or updating your recovery.
As usual im a little behind again with my post. Good luck
lbcary said:
once you have root and busybox installed correctly theres not much unrooting and then rooting again will solve.Except to return your device to stock,and to unroot i usually flash the unrooted stock rom. U can try the Root Checker app from the Market just to make sure your rooted and have busybox installed correctly. However custom roms are already rooted and have busybox installed correctly. If its a new sdcard id still try another sdcard. Use an sdcard u know is good. I bought a few cheap sdcards that were 8GB class 10 becuz i got a great deal on them,10 for $110.but out of the 10,only 7 were even recognized by my Evo or my HP dv7 Netbook and worked.Also i highly doubt they are class 10,bcuz my SanDisk 16GB C10 sdcard is much faster,and older too. So just bcuz its new doesnt mean its good.If it still wont work after a fresh wipe using Amon Ra recovery,NOT ClockWork Mod recovery,and a fresh/newly downloaded rom flashed from a different sdcard using Amon Ra recovery to fully wipe,then flash the newly downloaded rom from the different sdcard to your device. That shud work,but if it doesnt u can try reinstalling or updating your recovery.
As usual im a little behind again with my post. Good luck
Click to expand...
Click to collapse
oh k. will try the card that came with the phone then. I know that one worked great. just wanted more memory and I got it from walmart. so it maybe poop.
Callie_evo said:
oh k. will try the card that came with the phone then. I know that one worked great. just wanted more memory and I got it from walmart. so it maybe poop.
Click to expand...
Click to collapse
ok got the rom installed on sdcard and booted up. think i'm done flashing roms. that was scary. Thank you all for your help. I really do appreciate it.
Callie_evo
Callie_evo said:
oh k. will try the card that came with the phone then. I know that one worked great. just wanted more memory and I got it from walmart. so it maybe poop.
Click to expand...
Click to collapse
First: Did you partition all the card or only a certain amount ?
Second: Almost all the Custom recoveries have format card so do that.Then boot back in recovery and mount your card from recovery.
Third: Do not run RUU Period.
Fourth: Wipe all, cache, dalvik and all 2or3 times.
You wont get stuck on splash. since you wipe all give it a bit of time to check everything about 5-10 minutes
uraganone said:
First: Did you partition all the card or only a certain amount ?
Second: Almost all the Custom recoveries have format card so do that.Then boot back in recovery and mount your card from recovery.
Third: Do not run RUU Period.
Fourth: Wipe all, cache, dalvik and all 2or3 times.
You wont get stuck on splash. since you wipe all give it a bit of time to check everything about 5-10 minutes
Click to expand...
Click to collapse
on partition the card i just hit the power button on all of it. got a custom rom back on my phone now it is up and running.
I would suggest using this program when formatting your SD ..
https://www.sdcard.org/consumers/formatter_3/
Just and FYI, when partitioning your SD Card, it will wipe the contents. So you'll need to partition SD Card and then move over any content you want to install.

Need someone who knows this phone.. (Revert back to stock)

So.. After owning this phone for a year, I still love it to death..
But after many roms and such its been kinda slowing down on me..
what I would like to do, because I heard it helps a lot, is to revert back to the original software, then put a rom on fresh..
I'm running Synergy Rom now.. And it just locked on me.. It keeps rebooting, so I figure now is the time I do this..
Questions..
I will no have to lose my root? right?
How do I do this now? I'm using clockwork and assume I put the original rom(or zip?) on my sdcard, then go into recovery, and run it?
Correct?
I also ran a script file (v6supercharged)
I assume I will have to redo that as well?
Thanks guys!!
Have no phone right now, so would like to get started asap..
Again!! MUCH THANKS!!
As long as you fully wipe using Amon Ra, you should be able to make most updated ROMs run fast on your phone. Perhaps try reflashing Synergy. I also recommend flashing a new ROM, but reinstalling apps without data. Perhaps that is contributing to the sluggishness.
Sent from my PC36100 using XDA App
Thanks.. But I've been told over and over, its sometimes good to revert back to stock..
Wipe/clear, Install stock rom (or its an .exe. or something?) then wipe/clear again, and put the rom on..
Anyone have the stock file??
Do I let it update or no ??
fastfed said:
Wipe/clear, Install stock rom (or its an .exe. or something?) then wipe/clear again, and put the rom on..
Click to expand...
Click to collapse
That's ridiculous. A wipe is a wipe.
In fact, using the RUU (.exe) is riskier since it flashes radios and such, and if something goes wrong during, you have a bricked phone. Just do a full wipe including cache/dalvik cache and install your ROM of choice, along with a good kernel.
fastfed said:
So.. After owning this phone for a year, I still love it to death..
But after many roms and such its been kinda slowing down on me..
what I would like to do, because I heard it helps a lot, is to revert back to the original software, then put a rom on fresh..
I'm running Synergy Rom now.. And it just locked on me.. It keeps rebooting, so I figure now is the time I do this..
Questions..
I will no have to lose my root? right?
How do I do this now? I'm using clockwork and assume I put the original rom(or zip?) on my sdcard, then go into recovery, and run it?
Correct?
I also ran a script file (v6supercharged)
I assume I will have to redo that as well?
Thanks guys!!
Have no phone right now, so would like to get started asap..
Again!! MUCH THANKS!!
Click to expand...
Click to collapse
If you rooted with unrevoked or revolutionary, you will need this file to return to stock, and yes, you will temporarily lose root.
http://dl.dropbox.com/u/38127313/Un....15.00.0808_NV_2.15_release_220182_signed.zip
Change the name to PC36IMG and run it from the root of your SD card through the bootloader. You will lose your root, but your security flag should still be off (S-OFF) so that you can quickly regain root after running this file, after changing it to PC36IMG in place of the first one. (It is Amon-RA and not clockwork. You can reflash clockwork later if you want, which I don't recommend.
http://dl.dropbox.com/u/38127313/Root 2.3.3/PC36IMG3.08.zip
Also, you might need to flash a superuser app, in case you need root inside the stock ROM. Here is an old one, but it should still work for you.
http://dl.dropbox.com/u/38127313/Root 2.3.3/su-2.3.6.2-efgh-signed.zip
Like the previous users said, it's probably not necessary, but I'm just giving you what you asked for.
hmmm.. so now its not necessary ? I was always under that impression..
Ok..
Anyone know what the new HOT rom is ??
Gigerbread please ?
Like I said I was using Synergy..
Used Fresh before and a couple others..
whats the hot rom ??
FYI I also partitioned my SD card, or whatever its called.. For the gigerbread thing..
Put MikG 3.0 on it and call it done. Rock solid ROM, great battery life, and awesome tweaks built in. It will be like an all new phone. Enjoy
Sent from my PC36100 using xda premium
This is why I stress making a nandroid of your stock/rooted immediately after Rooting.
You may want to simply reformat your SD Card. I've been having a few issues and realized it's been months since I cleaned up and reformatted/repartitioned my SD Card, so I plan on doing that tomorrow and flashing a new ROM
Use "Best Method" for Cleanest way (Wiping)
OLDER: Froyo v2.2 (3.70.651.1) http://keetsa.com/files/RUU_SuperSo...15.00.11.19_NV_1.90_release_161482_signed.exe
Most Current version is "Gingerbread v2.3.3 (4.54.651.1).EXE" http://www.multiupload.com/LLV12N2WU8
with "xxx.EXE file", You'll need to Run it on Widows and install on Phone thru Micro USB plug.
BEST Method to install Most Current STOCK ROM:
1. Download + Rename to "PC36IMG.zip" on SDCARD + (Boot into Recovery +Install) "AmonRa Recovery v3.11-gnm" http://dl.dropbox.com/u/34586908/PC36IMG-ra-supersonic-3.11-gnm.zip
2. (Boot into Recovery), WIPE these 8 lines (All data/factory Reset, /data, /cache, /sdcard/.android_secure, /system, Dalvik-cache, battery stats, rotate settings)
3. Download + Rename to "PC36IMG.zip" on SDCARD + (Boot into Recovery +Install) "GB v4.54.651.1.ZIP" http://db.tt/Ck6AB18E
If you want non Stock Recovery + Rooted:
1. Rename your "(AmonRa Recovery v3.11-gnm) PC36IMG.zip" to "PC36IMG.zip" again. (Boot into Recovery +Install). (cus Stock Rom changed you to STOCK Recovery)
2. (Boot into Recovery + Install) "Root (Superuser-3.0.7-efghi-signed).zip" www.mediafire.com/?16a07x3800wvak6
No need to revert to stock.
Use vr superwipe
Save the contents of your sd card to a computer, then reformat the sd card
Wipe everything on the wipe menu, then flash a new ROM.
copy the titanium backup directory back to your sd card and restore apps without data first, then restore data of any games or what not.
Problems should be fixed.
Sent from my PC36100 using Tapatalk
You have a lot of options here. As the preceding posts may have eluded to. Depending on how consistent and deep your issues are, there are different steps that need to be taken.
You can always wipe the ROM and reflash. Do a dirty flash, by just wiping cache and dalvik, then reflashing. That tends to be my temp work around sometimes.
Worst case I've seen is reverting to stock. Unrooting. And starting back over.
With any new ROM you'll need to reflash your mods. Becareful tho of what mods you're using. Not all are compatible across the board.
HipKat said:
This is why I stress making a nandroid of your stock/rooted immediately after Rooting.
You may want to simply reformat your SD Card. I've been having a few issues and realized it's been months since I cleaned up and reformatted/repartitioned my SD Card, so I plan on doing that tomorrow and flashing a new ROM
Click to expand...
Click to collapse
Did reformatting the SD card help? I just realized and did the same thing. It had been a good 3-4 from changes and about a year since I formatted my card.
It helps a lot. I reformat mine about every 3-6 months
Swyped From The Hippest MIUI'd phone Using XDA Premium

Categories

Resources