When I wipe my Dalvik Cache using RA recovery v2.2.2 and reboot my HTC EVO 4G, my apps that I have installed on the ext3 are deleted. If I browse to /system/sd/app folder there are no files.
I have moved my Dalvik cash to the internal storage. Not sure if this make a difference.
When I wipe my Dalvik Cache using Clockworkmod 3.0.05 the ext3 files are not touched.
Does anyone have any ideas why this might be happing?
Stop using sd-ext. It's not needed. You've got an EVO, not a G1.
You might want to try updating your recovery. I'm using what's in my sig, and have apps on a ext3 by way of darktremor's a2sd. Wiping cache/DC doesn't touch the ext3.
drmacinyasha said:
Stop using sd-ext. It's not needed. You've got an EVO, not a G1.
Click to expand...
Click to collapse
I am using a custom Rom that is able to use ext3.
gpz1100 said:
You might want to try updating your recovery. I'm using what's in my sig, and have apps on a ext3 by way of darktremor's a2sd. Wiping cache/DC doesn't touch the ext3.
Click to expand...
Click to collapse
Thank you for your reply. I will flash version of ra recovery that you are using. Do you have a link to that?
gpz1100 said:
You might want to try updating your recovery. I'm using what's in my sig, and have apps on a ext3 by way of darktremor's a2sd. Wiping cache/DC doesn't touch the ext3.
Click to expand...
Click to collapse
+1.....Update your recovery to amon RA v2.3. Wiping cache & dalvik should not be affecting the apparently that are stored on your sd-ext.
Posting & replying via the XDA Premium app
gpz1100 said:
You might want to try updating your recovery. I'm using what's in my sig, and have apps on a ext3 by way of darktremor's a2sd. Wiping cache/DC doesn't touch the ext3.
Click to expand...
Click to collapse
it does seem I had a problem with the version of ra recovery. after installing 2.3 I do not have the same issue.
jcoyle said:
it does seem I had a problem with the version of ra recovery. after installing 2.3 I do not have the same issue.
Click to expand...
Click to collapse
I'm glad you were able to solve the problem. Enjoy your weekend.
Posting & replying via the XDA Premium app
jcoyle said:
it does seem I had a problem with the version of ra recovery. after installing 2.3 I do not have the same issue.
Click to expand...
Click to collapse
Congrats! In case you're wondering, there were actually 4 different v2.3's before the final came out. Buried somewhere in the RA thread is a post describing which of the test versions the final is based on. I vaguely remember it being based on test03. In my own usage, I never had a problem with test04 (which had the larger read ahead cache enabled), so I left it as is. Unlike earlier versions, it does take longer to come up once the recovery banner is visible in the bottom. Not sure if this is the case with the final, but it doesn't bother me, so long that it works!!
gpz1100 said:
Congrats! In case you're wondering, there were actually 4 different v2.3's before the final came out. Buried somewhere in the RA thread is a post describing which of the test versions the final is based on. I vaguely remember it being based on test03. In my own usage, I never had a problem with test04 (which had the larger read ahead cache enabled), so I left it as is. Unlike earlier versions, it does take longer to come up once the recovery banner is visible in the bottom. Not sure if this is the case with the final, but it doesn't bother me, so long that it works!!
Click to expand...
Click to collapse
I don't think that is the case anymore. He's only displaying the final version in his thread, i believe. http://forum.xda-developers.com/showthread.php?t=705026
http://forum.xda-developers.com/showpost.php?p=11171657&postcount=2449
Looks like all the other test versions have been pulled. Makes sense.. No need to keep an older ver when newer one working fine.
gpz1100 said:
http://forum.xda-developers.com/showpost.php?p=11171657&postcount=2449
Looks like all the other test versions have been pulled. Makes sense.. No need to keep an older ver when newer one working fine.
Click to expand...
Click to collapse
No doubt...Enjoy your weekend...
Related
I'm new to the EVO, but I have had a hero in the past and I always used "Amon RA recovery" but now with the EVO, which is best or better to use?
1. RA-evo-v1.7.0.1
http://forum.xda-developers.com/showthread.php?t=705026
2. ClockworkMod recovery
http://forum.xda-developers.com/showthread.php?t=702214
I don't think one is better than the other. Clockwork works with rom manager app, that is the only perk I see.
This belongs in Q&A.
Sent from my Evo.
Using RA here... havent had a single issue with it.
This should be in Q & A....
However, Clockwork has known issues properly wiping dalvik cache.
On the other hand, Clockwork will flash unsigned zips, AmonRa won't.
Take you pick, I prefer AmonRa.
kyleblakepeters said:
This belongs in Q&A.
Sent from my Evo.
Click to expand...
Click to collapse
The sad thing is that the OP even KNEW this; hence the preceding [Q]
*sigh*
Thank you, thats I all I need to know, I knew with the hero there was some issues with clock work and i know some perks are better but I never had a prob with Amon Ra on my hero, so thanks agaain im just going to use it on my EVO
BAttitude7689 said:
Thank you, thats I all I need to know, I knew with the hero there was some issues with clock work and i know some perks are better but I never had a prob with Amon Ra on my hero, so thanks agaain im just going to use it on my EVO
Click to expand...
Click to collapse
What drove you to post in Development versus the section specifically designated for Question and Answers?
The issues with clockwork have been fixed for a while now. It wipes everything just fine.
SteelH said:
This should be in Q & A....
However, Clockwork has known issues properly wiping dalvik cache.
On the other hand, Clockwork will flash unsigned zips, AmonRa won't.
Take you pick, I prefer AmonRa.
Click to expand...
Click to collapse
Same here. I can never get Clockwork to properly wipe dalvik cache.
clamknuckle said:
The issues with clockwork have been fixed for a while now. It wipes everything just fine.
Click to expand...
Click to collapse
+1, with rom manager and unsigned zip support, no reason to choose Amon Ra as of now.
jerryparid said:
+1, with rom manager and unsigned zip support, no reason to choose Amon Ra as of now.
Click to expand...
Click to collapse
It is still having issues for people trying to update to Froyo releases, it isn't wiping dalvik right. Maybe they have an older version of Clockwork and that's the problem.
But seriously, if someone making an update zip can't sign it, I wouldn't trust their skills anyhow. Signing a zip is simple.
I haven't been able to flash any dc or froyo tons via clockwork.
Sent from my PC36100 using XDA App
I use Clockwork, I've flashed half a dozen ROMs including CM6, no problems whatsoever. I do my flash work in recovery boot, not ROM Manager, maybe that makes a difference. Why work on a car with the engine running if you don't have to?
Trying to get to the bottom of my kernel issues and I just noticed that instead of getting a # in adb, I get a /#. Anyone know what that means?
I'm guessing you're using netarchy kernel and bash. RTFM on custom shell prompts.
I'm using KingX and I don't know what bash is. Anyway, I just tried adb again and it's back to a #, so that's a non issue now. I still can't figure out why I can't flash ANY of the new kernels without causing a bootloop. KingX 7 and 8, netarchy 4.1.9.1 or any of the 8.x snap kernels, none of them work. I can flash older ones without issue (kingx #4, #6, netarchy 4.1.8, snap 7.11). Nobody else seems to have this issue, is it possible I screwed up my Evo?
_MetalHead_ said:
I'm using KingX and I don't know what bash is. Anyway, I just tried adb again and it's back to a #, so that's a non issue now. I still can't figure out why I can't flash ANY of the new kernels without causing a bootloop. KingX 7 and 8, netarchy 4.1.9.1 or any of the 8.x snap kernels, none of them work. I can flash older ones without issue (kingx #4, #6, netarchy 4.1.8, snap 7.11). Nobody else seems to have this issue, is it possible I screwed up my Evo?
Click to expand...
Click to collapse
You'll need to wipe your phone. Data dalvik, cache.
Sent from my PC36100 using XDA App
SharkUW said:
You'll need to wipe your phone. Data dalvik, cache.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Done that about 50 times now :/
_MetalHead_ said:
Done that about 50 times now :/
Click to expand...
Click to collapse
I've pretty much stayed away from the tricked out kernels because the instability scares me, but the few times I used one I noticed that sometimes my phone had to reboot two or three times before it booted and stayed on. Just a thought.
_MetalHead_ said:
Done that about 50 times now :/
Click to expand...
Click to collapse
If you are running ClockworkMod, you need to wipe with amon-RA. they say ClockworkMod does not wipe completely.
http://forum.xda-developers.com/showpost.php?p=6855542&postcount=1
illogic6 said:
I've pretty much stayed away from the tricked out kernels because the instability scares me, but the few times I used one I noticed that sometimes my phone had to reboot two or three times before it booted and stayed on. Just a thought.
Click to expand...
Click to collapse
I've sat and watched it reboot 10 times in a row before I gave up and restored my nand.
If you are running ClockworkMod, you need to wipe with amon-RA. they say ClockworkMod does not wipe completely.
Click to expand...
Click to collapse
I've done it multiple times with both. AmonRA is my preferred recovery.
dwertz said:
If you are running ClockworkMod, you need to wipe with amon-RA. they say ClockworkMod does not wipe completely.
http://forum.xda-developers.com/showpost.php?p=6855542&postcount=1
Click to expand...
Click to collapse
Afaik clockwork has always wiped ok. I think there were a lot or still are people confused by dalvik being in a separate menu. There are also people that will tell you to wipe twice. It's not a rubber eraser, it's a filesystem.
Sent from my PC36100 using XDA App
SharkUW said:
Afaik clockwork has always wiped ok. I think there were a lot or still are people confused by dalvik being in a separate menu. There are also people that will tell you to wipe twice. It's not a rubber eraser, it's a filesystem.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I had issues with it and several other people have and I know there were seperate menus. Just saying, it has been several people even ones that have been around awhile.
http://forum.xda-developers.com/showthread.php?t=758633
http://forum.xda-developers.com/showthread.php?t=719763
from Netarchy
An important note for Clockwork mod Recovery users:
Clockwork Mod is reportedly not wiping correctly (ie; if you try to wipe cache/dalvik-cache/data/etc it's not actually doing it, or not doing it right)
You may want to consider using Amon Ra Recovery instead.
I how you know that your first link is all posts, at least as far as I read into, detailing the various levels of crazy required to believe that cm isn't wiping the dalvik cache. Did you read it or just the op?
Sent from my PC36100 using XDA App
SharkUW said:
I how you know that your first link is all posts, at least as far as I read into, detailing the various levels of crazy required to believe that cm isn't wiping the dalvik cache. Did you read it or just the op?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I read the posts. Some people are just having issues and some people are not. All I was stating is that CWM has been known to have a few issues and to try Amon RA to see if the problems get fixed. I used to have issues installing kernels with CWM. I used it through Rom manager because it made it easy. I ended up going to Amon RA because all the issues I had personally. I know Amon RA has been reducing the size because some people had bad blocks. Have you thought that maybe your phone doesnt and some people does causing the full recovery not to be there?
dwertz said:
I had issues with it and several other people have and I know there were seperate menus. Just saying, it has been several people even ones that have been around awhile.
http://forum.xda-developers.com/showthread.php?t=758633
http://forum.xda-developers.com/showthread.php?t=719763
from Netarchy
An important note for Clockwork mod Recovery users:
Clockwork Mod is reportedly not wiping correctly (ie; if you try to wipe cache/dalvik-cache/data/etc it's not actually doing it, or not doing it right)
You may want to consider using Amon Ra Recovery instead.
Click to expand...
Click to collapse
switching from rom to rom, i just do a full factory wipe, isn't that technically what dalvik is not doing in clockwork, i've had no issue's yet by doing this, even with some rom's i haven't done it and things have worked fine, but that's besides the point.
tomh1979 said:
switching from rom to rom, i just do a full factory wipe, isn't that technically what dalvik is not doing in clockwork, i've had no issue's yet by doing this, even with some rom's i haven't done it and things have worked fine, but that's besides the point.
Click to expand...
Click to collapse
Yes, the general wiping instructions are very redundant. Dalvik is within cache which is why clockwork has it under a sub menu. You "wipe" dalvik 3x with factory reset, cache, dalvik. Some roms have dalvik under data by my understanding, in which case you've wiped it once.
Sent from my PC36100 using XDA App
Hello I have been having issues flashing any sense 3.0 roms on my phone. Other roms flash perfectly fine including gb roms. I am currently running INfected Inspire 4g and ran Mikfroyo prior to that as well as many more froyo roms. I have a version 002 Evo purchased on launch day. I am fully rooted using Amon Ra's latest recovery. The roms flash perfectly fine but I get an infinite boot loop on the white "HTC Evo 4g" screen. I have tried superwipe and have used it 3x prior to flashing a rom, I have the latest radio, pri etc. I have also tried flashing with a downgraded 1.7 pri. I have "double flashed" the roms. All with no luck. I still get the bootloop. Is there any fix or ideas how to resolve this issue I would really love to use some of the newer GB roms.
Here is a list of Roms that give the bootloop after flashing:
Dominus_Zeta
Virusrom Kingdom Revolution
B.O.S. Kingdom port r2
Misfits speedy port
Virusrom gingersense
Evolved Rom shifted "Get abducted"
There may be one or two more but there are enough there to find a common denominator. If there is any way that this can be fixed I would be greatly appreciative. Also I will be subscribed to this thread and have xda sent to my phone so most of the time I will reply very soon to answer any questions to help solve the issue. A huge thank you in advance to any one willing to offer a helping hand.
i believe you need to partition the sdcard to make enough space for the /system. yes, some /system will be on your sdcard.
dkdude36 said:
i believe you need to partition the sdcard to make enough space for the /system. yes, some /system will be on your sdcard.
Click to expand...
Click to collapse
I have a 32 gb card with less than 8 used
Patb8man said:
I have a 32 gb card with less than 8 used
Click to expand...
Click to collapse
boot into recovery, and choose partition sdcard. then choose partition sd. then interactive sd partitioning. choose a size (around 2 gigs is reccomended) and parition.
dkdude36 said:
boot into recovery, and choose partition sdcard. then choose partition sd. then interactive sd partitioning. choose a size (around 2 gigs is reccomended) and parition.
Click to expand...
Click to collapse
It will wipe my card right?
Patb8man said:
It will wipe my card right?
Click to expand...
Click to collapse
yep i guess so. i have never done it, but i'm pretty sure it does.
dkdude36 said:
yep i guess so. i have never done it, but i'm pretty sure it does.
Click to expand...
Click to collapse
Cool thank you Im backing up my card now...hopefully its as simple as that
edit: I partitioned the card and still no luck anymore ideas out there. Should I create an ext. 3 partition?
Patb8man said:
Cool thank you Im backing up my card now...hopefully its as simple as that
edit: I partitioned the card and still no luck anymore ideas out there. Should I create an ext. 3 partition?
Click to expand...
Click to collapse
Both Virus ROMs instruct to create ext3.
mevensen said:
Both Virus ROMs instruct to create ext3.
Click to expand...
Click to collapse
No luck still...any other suggestions?
I have the same hardware, launch day 0002 hardware, I recently started using Virus Kingdom ROM, the latest version from his website. When I was first messing with it I would have problems with the white EVO screen not going away, I would have to pull the battery and get back into recovery, wipe cache and dalvik and make sure to select shut down phone instead of reboot.
Hope that helps!
Thank you I will try this method.
Patb8man said:
Thank you I will try this method.
Click to expand...
Click to collapse
can you get a logcat from it? if you have adb set up use 'adb logcat > log.txt' and let it run for a minute or two. Then use control+c to stop it (on a pc) and open up the file it created
xHausx said:
can you get a logcat from it? if you have adb set up use 'adb logcat > log.txt' and let it run for a minute or two. Then use control+c to stop it (on a pc) and open up the file it created
Click to expand...
Click to collapse
A log of what exactly?? After I flash a rom and it's in an infinite loop?
Sent from my Evo 4g
Patb8man said:
A log of what exactly?? After I flash a rom and it's in an infinite loop?
Sent from my Evo 4g
Click to expand...
Click to collapse
i think both a log of the flash itself and the infinite loop would be helpful.
Can I use it during the boot loop?? I will do it when I flash virus's rom tonight.
Sent from my Evo 4g
yep. u can
Great it's been a while since I used adb I well have to get my stuff in order.
Sent from my Evo 4g
I keep re-downloading the rom but every time at the end during the boot image flash I get an error. Installation aborts and I get nothing if I try to boot. Can anyone help with this?
Make sure you clear out everything good. I had an issue in the beginning and had to wipe the cache real good. No issues since
I have tried. I have done numerous cache wipes prior to install. I don't know what the deal is. Thanks for the advice though!
I guess this is probably a stupid question but, would not having an ext partition on my sd card stop the rom from flashing?
d_cook said:
I guess this is probably a stupid question but, would not having an ext partition on my sd card stop the rom from flashing?
Click to expand...
Click to collapse
no having sd ext is fine. no problems as far as i know. but are you using Clockwork mod recovery? because the rom wont flash with clockwork you need amon-ra 2.3 there is something in the godmode scripts that is in an unsupported format for clockwork.
http://forum.xda-developers.com/showthread.php?t=705026
here is a link to the amon-ra recovery. if you have questions about how to install it feel free to pm me. btw you don't flash recovery's in a recovery so don't try to flash it in one
I'm gonna try that. I realised that I couldn't flash Mik's rom either. I think I may have an old recovery. Thank You! I was using Amon-RA. I think it was an old version though
d_cook said:
I'm gonna try that. I realised that I couldn't flash Mik's rom either. I think I may have an old recovery. Thank You! I was using Amon-RA. I think it was an old version though
Click to expand...
Click to collapse
yeah you might have been on 1.8 instead of 2.3 and if it still doesn't flash then its probably never going to. godmode seems to be tempermental with what phones it wants to work on and theres multiple people who no matter what they tried cant get it to flash. so cross your fingers and hope for the best
I had the same problem. Couldn't flash with cwm. So I flashed amon ra 2.3 and then flashed synergy rc2 god mode it took about 20 minutes but worked.
Sent from my rooted s off PC36100 using XDA Premium App
Thanks for the help. It turns out that I was running 1.8. I am on 2.3 now and all is good.
Sent from my Synergized GodMode Evo
Hello. I just switched my recovery to TWRP and i wiped my cache/ dalvik/ factory reset my phone, in preparation to flash some ROMs. So i tried flashing several ROMs and they either ended up failing or it claims to be successful and when i try to boot up it bootloops the htc splash screen. So i'm stuck on recovery since I can't even boot into a ROM. I need help!! I have S-On and i'm unlocked.
It seems like TWRP has always been wonky on the Evo. It was even bricking them on version 2.1 I think. My advice would betoswitch to the smelkus mod version of Amon RA. It has never done me wrong.
Sent from my PC36100 using xda app-developers app
I never had an issue when I used to run TWRP 1.0. Having said that, I've been running Smelkus recently and haven't looked back. You might try switching recoveries and running the superwipe function and wiping the Dalvik cache in Smelkus before and after you flash a ROM and see if that clears things up. You can do a search on XDA for Smelkus recovery to find the OP and download link.
Just curious, though. What ROM are you trying to flash?
Six6tring said:
It seems like TWRP has always been wonky on the Evo. It was even bricking them on version 2.1 I think. My advice would betoswitch to the smelkus mod version of Amon RA. It has never done me wrong.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I got it flashed.
FinZ28 said:
I never had an issue when I used to run TWRP 1.0. Having said that, I've been running Smelkus recently and haven't looked back. You might try switching recoveries and running the superwipe function and wiping the Dalvik cache in Smelkus before and after you flash a ROM and see if that clears things up. You can do a search on XDA for Smelkus recovery to find the OP and download link.
Just curious, though. What ROM are you trying to flash?
Click to expand...
Click to collapse
I've tried several ROMs like Nitrous, Blackbean, Team Dirt's ICS 4.0.4 ROM and the RemICS ROM, DigitalKarma, MokeeOS, and Holo. I just finished switching recoveries so everything should work.
I have to ask. Is your SD card partitioned properly?
death-by-soap said:
I have to ask. Is your SD card partitioned properly?
Click to expand...
Click to collapse
I'm not sure. I just bought my sdcard 3 months ago. Is there a way to check? But anyway, this thread is done.
Mobiono said:
I'm not sure. I just bought my sdcard 3 months ago. Is there a way to check?
Click to expand...
Click to collapse
If your not sure. Then it ain't. Go here to see how to Partition your SD Card. Most Roms have A2SD baked in and not having your card partition will cause issues.