Develop Bugs

[Q] Help...I can't wipedatea/factory reset

Hello everyone! I am trying to flash a new rom and I am at a loss. I have tried both Amon RA and Clockwork, and neither will fully wipe for some reason. I have been at this for quite some time and have never run into this problem. I am currently running Myn's rls4. I have s-off root and have tried both recoveries with no avail. It tries to wipe then stops al too quickly. Then even after attempting to flash another rom it boots into myn's as if i just flashed it. weird huh? any help would be GREATly appreciated! I hope it ok to post this here! Thank you in advance!
creative.....

whats your hardware #
EDIT--if new hardware read zikroik"s root, just asked question about this sortta thing.

Thread moved to Q&A.

Removed text. Wrong post. Sorry.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!

Its 003, ive never had any problems at all before.

Take it you cleared all caches..reg and dalvik? Also might want to re download new ROM in case its a bad file for whatever reason and try it again.

And try wiping everything at least twice. I usually start with the Dalvik and Battery stats and then the data and cache partition wipes.

devnulldroid said:
Take it you cleared all caches..reg and dalvik? Also might want to re download new ROM in case its a bad file for whatever reason and try it again.
Click to expand...
Click to collapse
Yes I have cleared everything, and tried at least two different ROMs

Google "Calkulin's FORMAT ALL" & put the zip on your sd card & flash. It will clear everything. with the exception of dalvik, so you may want amon ra for that

theultimatev said:
Google "Calkulin's FORMAT ALL" & put the zip on your sd card & flash. It will clear everything. with the exception of dalvik, so you may want amon ra for that
Click to expand...
Click to collapse
Thanks I'll give it a go. I hope this works.

Additional Info
Ok there is a little more info about the situation. Ive been running Myn's... rls4. I moved all my apps to the partition on my SD. I then decided to run the dalvik cache from there as well. Well, when I moved it (through the terminal) and rebooted the entire system FC'd, everything entirely. Well I wiped everything and went back to a nandroid backup. Ever since then Ive been unable to use Apps2sd, then I came to discover the recovery problem.

Format all did the trick! Thanks so much and Merry Christmas!
Sent from my super sweet freakin Evo using XDA App

CM7 Stuck in Bootloop

Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick

What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed

Try a full wipe, cache, dalvik, and data. Then reflash the rom.

By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?

That's correct, just wipe dalvik and cache before doing so.

So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...

I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17

You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.

The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??

deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.

Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.

deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.

No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?

Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.

Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.

deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn

[Q] Wipe before flashing new ROM

I tried to wipe with caulkins and vt superwipe, but when I select them on the SD card it runs for a moment then stops and says installation aborted. Is this supposed to happen? If not why would it not be working?

irl5fan said:
I tried to wipe with caulkins and vt superwipe, but when I select them on the SD card it runs for a moment then stops and says installation aborted. Is this supposed to happen? If not why would it not be working?
Click to expand...
Click to collapse
If I may, Calkulin's Format all and the other method, though nice, is not really necessary, especially if your recovery is amon RA 2.3....All you have to do is go to the wipe menu and wipe EVERYTHING in it except the SD card itself and you should be good to go afterwards.
As for your question, No, it it not suppose to state that. I am assuming you need to toggle the signature verification option to get them to flash, depending on your recovery & version.

And to add to what's already been said, Calkulin's format all is amend scripted (I believe), but Clockwork 3.x only supports edify. You could either flash an earlier version of CWM or Amon Ra - I'd suggest trying out Ra if you haven't yet - or you could use King's format all zip, which is the same as Calkulin's but with edify.

Thanks guys! I just ended up going in a wiping cache and davlik cache manually. I'm running CM7 Final with Tiamat. Still trying to get the gps fixed though.

irl5fan said:
Thanks guys! I just ended up going in a wiping cache and davlik cache manually. I'm running CM7 Final with Tiamat. Still trying to get the gps fixed though.
Click to expand...
Click to collapse
Go into the CM7 thread. There, you will find numerous references to the GPS fix.
posting & replying via the XDA Premium app

CM7 final bootloop

So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?

i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App

KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.

If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed

snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?

Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk

Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.

eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.

Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?

teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.

Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!

I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.

Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.

SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?

when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu

Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk

[Q] Salvage Mod 1.2.1 won't boot.

I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?

it is salvage mod 1.2.1.

JerenOtt said:
I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?
Click to expand...
Click to collapse
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.

k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.

I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?

JerenOtt said:
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.
Click to expand...
Click to collapse
No problem man. It will boot up after a doing a full wipe, most likely.

JerenOtt said:
I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?
Click to expand...
Click to collapse
Can you boot into the bootloader? Power off your device. Simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text should scroll across the screen and then you will see a few options. One of the options will be recovery. Anyway, at the top of the screen, you should see either S-ON or S-OFF. Hopefully, it displays S-OFF. Anyway, select recovery from the set of options and then, as k2buckley has instructed, go to the wipe menu and wipe EVERYTHING except the SD card itself. When you're done, do not reboot. Go to the flash menu and flash the rom you want to flash. Do not flash the gapps zip yet. Reboot after flashing the rom. I want to make sure you're able to boot into the homescreen. If you're successful, reboot into recovery, wipe cache & dalvik and then flash the gapps.zip. afterwards, reboot. When you're all setup, go back I to recovery and make a nandroid backup.
posting & replying via the XDA Premium app.

also, make sure you got the full ROM, not just the patch for going from 1.2 to 1.2.1. I did that

I was having similar issues, mine went into a boot loop about twice before getting hung up at the initial setup with FCs. I was coming from CM7 Nightly 41 that was acting weird with FC's, I always double wipe cache/dalvik/factory reset. I thought that I might have had a bad download so I re-downloaded, wiped and flashed. I couldn't get past the initial setup so I went back to Ultimate Droid and have been running that for the last 4 days or so with out any major problems except for the Facebook update dicking things up and one random reboot that I had today... I really want to give Salvagemod a shot though since it's Evo-centric.

still not working for me
hey guys... i been trying to boot into salvage mod for the past 2 days... i get it to install just fine i do get the salvage screen up too...
then when the rom is supposed to be loaded up i get the Android dude with emergency call and a crash u keep pressing ok then it goes away and comes back right away... i just wiped everything again and reflashed it and now i am stuck with salvage screen re looping..
any help would be appreciated
thanks

The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.

dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3? (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Glad you got him going Doug. I had asked him to use RA in a PM, and he responded that he liked clockwork and rom manager better, and wouldn't use RA, lol. I'm glad you convinced him otherwise.
Sent from my PC36100 using XDA App

lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.

dougjamal said:
lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Thank you Doug, happy Easter to you as well.
Sent from my PC36100 using XDA App

dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks

Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App

k2buckley said:
Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yup did everything... weird but i got it working now..did everything the same way as b4...its really sweet.. and really fast... thanks a bunch for the help

nxtstep said:
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks
Click to expand...
Click to collapse
You're very welcome, my friend. I'm glad I was able to help. Take care and have a great day....
posting & replying via the XDA Premium app.

k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
You're a genius. I was doing a data/factory reset, cache, and dalvik, but not boot and system. When i did those, it worked. Thanks!