Related
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!
I was flashing radio, wimax, NV, PRI. I was trying to fix android os from showing up on the battery. I downloaded from here http://forum.xda-developers.com/showthread.php?t=715485 put to root of sd. Flashed one by one, each one cleared my cache upon returning to recovery. I did not reboot phone completely after each flash, I flashed the next one, all in a row. Can I be saved?
Please help
Is your phone not turning on...or what's 'not' happening?
I reboot and it stuck at splash for 15 minutes. I pull battery, I reboot to bootloader then recovery. I wipe and flashing cyanogen again. I hope it works.
Boot into the bootloader, and verify that the correct radio you flashed is displayed there; if so, go into recovery from the bootloader, do a full wipe [factory/data, cache, dalvik cache], then flash your version of CM7, wipe cache and dalvik again, flash the latest gapps, then reboot.
Its fixed! Thank you for taking the time to help. I been flashing for a while and forgot my user/pass, dont have the same email either, lol. Thanks again
Lawlz, it happens, and you're welcome.
I'm asking if I bricked my EVO as well...I'm new to the whole rooting, ROM, Kernel thing, so I was very nervous to jump into the deep end.
I rooted successfully, took a nandroid backup, then flashed Deck's new ROM, and a kernel. When I selected "reboot" it wouldn't boot.
Can you guys think of anything I did wrong? Any help is greatly appreciated.
jp_danger said:
I'm asking if I bricked my EVO as well...I'm new to the whole rooting, ROM, Kernel thing, so I was very nervous to jump into the deep end.
I rooted successfully, took a nandroid backup, then flashed Deck's new ROM, and a kernel. When I selected "reboot" it wouldn't boot.
Can you guys think of anything I did wrong? Any help is greatly appreciated.
Click to expand...
Click to collapse
False alarm! I rebooted the phone into recovery and restored the backup that I just took. I flashed the ROMS and Kernel, then rebooted and now all seems to be working.
Man, that almost gave me a heart attack!
jp_danger said:
False alarm! I rebooted the phone into recovery and restored the backup that I just took. I flashed the ROMS and Kernel, then rebooted and now all seems to be working.
Man, that almost gave me a heart attack!
Click to expand...
Click to collapse
Glad its working; just make sure to backup, then do a full wipe before flashing a new rom. If flashing multiple things, wipe the cache and dalvik between flashes.
teh roxxorz said:
Glad its working; just make sure to backup, then do a full wipe before flashing a new rom. If flashing multiple things, wipe the cache and dalvik between flashes.
Click to expand...
Click to collapse
Thanks for the tip!
About a month ago I went from myns 2.2 to CM7 and eventually cm7.1 well I had terriable 3g 4g wifi and gps connection issues with CM and I flashed a bunch of kerenel and radio driver combos trying to fix the problem. Well out comes the synergy and I decide to try that and give up on CM. I did the usual wipe dalvic data ect twice and flashed synergy which got stuck on the white evo splash screen and won't go past that. Additionally when I flash any other rom's either myn's, cm, ect I get the same problem. I have tried wiping several times with both the Clockwork and RA recoveries with no success. As it stands now I can only recover previous nandroid backups or run the pc186img. Anyone have any ideas??? Help would be appreciated.
Thanks
Frankie
Go to the bootloader, do a clear storage [factory reset], then from recovery, do the full wipe, and only flash a rom, then boot; flash the kernel [if any] afterwards.
Frankie_Bones said:
or run the pc186img.
Frankie
Click to expand...
Click to collapse
hope thats an typo
dased14 said:
hope thats an typo
Click to expand...
Click to collapse
yeah pc36img
teh roxxorz said:
Go to the bootloader, do a clear storage [factory reset], then from recovery, do the full wipe, and only flash a rom, then boot; flash the kernel [if any] afterwards.
Click to expand...
Click to collapse
Worked, thanks. I had myself worried for a minute there.
About a month ago I decided I wanted to try out Synergy ROM for my EVO, so I went for God Mode and everything has been running fine...until now. I had installed a kernel earlier this week for underclocking and such, but decided today that I didn't really use it as much as I though so I decided to reflash the HTC stock 4.24. I just did that about 10 minutes ago, I made a backup in case something went wrong and I backed up all my apps/texts as well. It flashed, rebooted...then it got stuck in a boot loop. So I pulled the battery and booted up into the bootloader to go into recovery...when I found every time I hit recovery it would just restart to the bootloader. So I'm not really sure if there is anyway to restore my backup or any other way to boot into recovery. Am I just screwed? Or can I use ADB to boot into recovery/restore my backup? This is sort of my first question post so...If you need any more information just ask.
Thanks,
Suprgamr232
If your phone is still going into bootloops. Connect your phone to your computer and go to adb and type in adb reboot recovery. There you can revert back into a nandroid backup. Hope this helps
Not to be rude, but you didn't read the entire post did you? I can't access my recovery and AFAIK adb doesn't work while it's in a bootloop. Also, I don't think adb recognizes my device when it's in the bootloader either.
Hey im just trying to help, Maybe some how you lost your recovery? Maybe try reflashing your recovery from the bootloader, make sure it named pc36img.zip. See if you can access your recovery after that. What recovery are you using btw, clockworkmod or amon ra? and did you wipe your cache and dalvik cache files through recovery before you flashed your kernel?
If you can access your recovery after reflashing it, Try wiping those in recovery and rebooting, see if it boots into your rom. If not and you still get a boot loop but you can access recovery do a full wipe and reflash your rom or try restoring a nandroid
Not gonna argue with you, so I'll let it slide...I'm using clockworkmod and I did wipe my cache and dalvik cache. ATM I haven't been able to get a hold of a new recovery img for some reason...can never get it to download 100%, will try it soon hopefully.
There's no need to argue Ive heard that clockworkmod doesnt always completely wipe the cache and dalvik maybe try using amon ra this time around http://forum.xda-developers.com/showthread.php?t=705026
Cant hurt to try it. hope you can get it working for ya, gl
Still stuck in the bootloop. I tried restoring but that didn't help. I tried reinstalling the ROM and the kernel I used before and no change, I don't really want to wipe my phone and try it but...I guess it might turn out that way. Before I do though I was wondering if there is anything else I should try?
suprgamr232 said:
Still stuck in the bootloop. I tried restoring but that didn't help. I tried reinstalling the ROM and the kernel I used before and no change, I don't really want to wipe my phone and try it but...I guess it might turn out that way. Before I do though I was wondering if there is anything else I should try?
Click to expand...
Click to collapse
You're gona have to do a full wipe [ factory/data, cache, and dalvik ] , reflash your rom, kernel, ect. Once you sign in, boot, ect, you can use titanium backup to restore your apps and data, NOT system settings.
Alrighty then. Did that and everything seems to be working fine...A little disappointed but as long as I have my phone! Thanks for your help!
suprgamr232 said:
Alrighty then. Did that and everything seems to be working fine...A little disappointed but as long as I have my phone! Thanks for your help!
Click to expand...
Click to collapse
Glad its working again.
I'm running amon ra, haus mod rev .a
i've partitioned my sd card with 32 swap, 1024 ext2, then to ext3
I've wipes all data/factory reset, then cache, dalvik cash, and data
I then have tried flashing 2 different ROM's and boot leave me stuck in a boot loop after flashing.
I'm not sure what to troubleshoot next.
Thank you in advance for your gracious help.
Chris
TurbineTester said:
I'm running amon ra, haus mod rev .a
i've partitioned my sd card with 32 swap, 1024 ext2, then to ext3
I've wipes all data/factory reset, then cache, dalvik cash, and data
I then have tried flashing 2 different ROM's and boot leave me stuck in a boot loop after flashing.
I'm not sure what to troubleshoot next.
Thank you in advance for your gracious help.
Chris
Click to expand...
Click to collapse
First off,what roms did you try flashing and Then you need to wipe everything,from data/factory reset,cache,data,android_secure,SD ext.,system,dalvik-cache,never the SD card.Now understand that sense 3.5 roms take alot of space,so the boots and such take longer and boot more times.
Diablo67 said:
First off,what roms did you try flashing and Then you need to wipe everything,from data/factory reset,cache,data,android_secure,SD ext.,system,dalvik-cache,never the SD card.Now understand that sense 3.5 roms take alot of space,so the boots and such take longer and boot more times.
Click to expand...
Click to collapse
I tried Nitrous and Express.
This is the first time i have seen instructions to wipe SD ext and system.
So here is what i did per your instructions.
I went right down the wipe list in amonra haus mod rev .a and performed the following wipe operations:
Wipe ALL userdata/factory reset
Wipe CACHE
Wipe DALVIK-CACHE
WIPE DATA
Wipe SDCARD:.android-secure
Wipe SYSTEM
Wipe SDEXT
Wipe DATA:battery stats
I did not wipe the following:
Wipe BOOT
Wipe SDCARD
Wipe DATA:rotate settings
I then flashed this ROM
http://forum.xda-developers.com/showthread.php?t=1542036
I had heard to give everything lots of time to complete, so i have let my phone sit in the boot loop and reboot about 30 consecutive times. I think that's enough time to do something different. I then took the battery out to stop the boot loop, replaced battery and powered on the phone. It continued to boot loop, and i let it sit again for another 5 or so mintues boot looping away. I pulled the battery again and powered it back on and it continued to boot loop. It reboots every 25 seconds and the only thing i see on the screen is a black background with
"htc EVO 4G"
In white letters across the middle.
I Wiped everything again and this time i also did
Wipe DATA:battery stats
I then partitioned the sdcard again, with
SWAP: 32
ext2:1024
then under the partition menu in amonra, i selected
SD:ext2 to ext3
that process complete
Then i go to the main recovery menu and select
USB-MS toggle
and copy over the ROM from my pc to the sd card. this was the only thing i copied over and the sd card is totally empty accept for the 269MB ROM zip file. (in past attempts i have copied over the ENTIRE contents of the sd card that i backed up)
I then flash the zip and wait for it to complete.
It finishes and then goes into the boot loop again. and i've let it continue to try and do anything other than what i have described above. It does not. I pull the battery and it boot loops again.
Is there something else in the partitioning process that i need to do? Do i need to format the sd card first or after?
What you really need to wipe is: boot, system, data, cache, dalvik, and sd ext [if partitiooned], and you're good to go. Wipe the boot, and then try again.
teh roxxorz said:
What you really need to wipe is: boot, system, data, cache, dalvik, and sd ext [if partitiooned], and you're good to go. Wipe the boot, and then try again.
Click to expand...
Click to collapse
Thanks for the help!
edit: I wiped everything you said and nothing else and i still get boot loops. It reboots once every 30 seconds or so and i let it keep rebooting for about 8 minutes. Then i popped the battery and let it try to boot again but i got the same boot loop.
Again, i really do appreciate the help, what should i try next?
After flashing the rom wipe cache and dalvik again before reboot if it loops more than 3 full loops pull battery and reboot to recovery wipe cache and dalvik then under.advanced menu fix permissions(uid mismatches) and the wipe cache and dalvik again and reboot when wiping before flashing wipe each option a few times in a row until they complete the wipe rather quickly that will ensure they are wiped properly. U can also try reflashing your recovery or changing recoveries to amon RA 2.3 or amon RA style supersonic recovery v3.11 depending on what recovery you are using currently
Sent from my SPH-D710 using xda premium
TurbineTester said:
Thanks for the help!
edit: I wiped everything you said and nothing else and i still get boot loops. It reboots once every 30 seconds or so and i let it keep rebooting for about 8 minutes. Then i popped the battery and let it try to boot again but i got the same boot loop.
Again, i really do appreciate the help, what should i try next?
Click to expand...
Click to collapse
Are you sure your downloads aren't corrupt somehow?
Sent from the original Swagged Out EVO via Tapatalk 2
-EViL-KoNCEPTz- said:
After flashing the rom wipe cache and dalvik again before reboot
Click to expand...
Click to collapse
Thanks for your help!
The ROM flash goes directly to a reboot so i never get the chance to wipe anything after it installs.
if it loops more than 3 full loops pull battery and reboot to recovery wipe cache and dalvik then under.advanced menu fix permissions(uid mismatches) and the wipe cache and dalvik again and reboot
Click to expand...
Click to collapse
It boot looped again I followed your instructions and i still get the same boot loops.
when wiping before flashing wipe each option a few times in a row until they complete the wipe rather quickly that will ensure they are wiped properly. U can also try reflashing your recovery or changing recoveries to amon RA 2.3 or amon RA style supersonic recovery v3.11 depending on what recovery you are using currently
Click to expand...
Click to collapse
The last time i wiped everything about 4 times in rapid succession and then let the phone sit for about 5 minutes before flashing the ROM. Still got boot loops
For the ROM in question the OD posted a specific version of amon ra recovery, Haus Mod, and said it worked. I downloaded that reovery from
http://forum.xda-developers.com/showthread.php?t=1542036
What can i try next?
swagstr said:
Are you sure your downloads aren't corrupt somehow?
Sent from the original Swagged Out EVO via Tapatalk 2
Click to expand...
Click to collapse
someone else suggested that as well. I did md5 checksums on the file i downloaded and on the file as it sat on the card, and both were identical.
This also happens when i try to flash another newer ROM that requires partitioning the sd card.
What should i try to do next?
TurbineTester said:
someone else suggested that as well. I did md5 checksums on the file i downloaded and on the file as it sat on the card, and both were identical.
This also happens when i try to flash another newer ROM that requires partitioning the sd card.
What should i try to do next?
Click to expand...
Click to collapse
Are you flashing Apps2SD with the ROM?
Sent from the original Swagged Out HTC EVO 4G via Tapatalk
swagstr said:
Are you flashing Apps2SD with the ROM?
Sent from the original Swagged Out HTC EVO 4G via Tapatalk
Click to expand...
Click to collapse
No I'm not. Do i need to?
And how would i do that?
THe thread for the ROM is was trying to flash doesn't mention anything about flashings apps2SD. Is that something that is required for all the newer ROM that require the partitioned SD card?
HTC EVO 4G reboot
After having had the same re-boot problem and reading the postings here and other forums and having tried all the solutions I still have the problem. I can only conclude that it is hardware related. Some of the HTC EVO 4G phones have this defect and there is nothing to do but get a new phone. This is a good reason not to root the phone until you have run the phone long enough to uncover any defects and have your carrier replace the phone. Living with an unreliable phone has made it personal for me. I won't buy another HTC product. What then, is the best Android/iPhone alternative currently?
lordway said:
After having had the same re-boot problem and reading the postings here and other forums and having tried all the solutions I still have the problem. I can only conclude that it is hardware related. Some of the HTC EVO 4G phones have this defect and there is nothing to do but get a new phone. This is a good reason not to root the phone until you have run the phone long enough to uncover any defects and have your carrier replace the phone. Living with an unreliable phone has made it personal for me. I won't buy another HTC product. What then, is the best Android/iPhone alternative currently?
Click to expand...
Click to collapse
All products... And I mean all products will have defects. You got the one in a million. And that sucks, it really does. But you need to realize one defective product does not mean ALL HTC phones are terrible. If I were you, I would talk to Sprint and HTC, it may be a long shot. But if this wasn't your fault, one of them should try to help you fix it.
Sent from the original Swagged Out HTC EVO 4G via Tapatalk
lordway said:
After having had the same re-boot problem and reading the postings here and other forums and having tried all the solutions I still have the problem. I can only conclude that it is hardware related. Some of the HTC EVO 4G phones have this defect and there is nothing to do but get a new phone. This is a good reason not to root the phone until you have run the phone long enough to uncover any defects and have your carrier replace the phone. Living with an unreliable phone has made it personal for me. I won't buy another HTC product. What then, is the best Android/iPhone alternative currently?
Click to expand...
Click to collapse
Same here. But i have had my evo 3D for nearly a year and have had no issues. I only decided to root because all the bloatware that gets added with every system update was killing me, then i found out u can flash ROMs and such. I have a headache from this bootloop issue as well and i was wondering, after you gain S_OFF, HBOOT returns to *** LOCKED *** and i was wondering if that had to be unlocked before flashing, but i havent heard anyone say to do this.
Flashing a ROM and getting stuck on boot is an issue with the ROM usually, flashing a ROM and getting stuck at a black screen that may or may not reboot is usually kernel base mismatch. Flashing a ROM that just plain reboots usually means something is wrong with system boot or one of the caches. Between different ROMs and or ROM bases (stock, modified stock, custom aosp) you need to perform a full system wipe before flashing new rom. I have a guide for the new evo lte but all the relevant knowledge is the same. And sorry for crashing the thread I'm very tired and I thought I was in the lte forums