Step by step:
1. Cleared data, cache, dalvik. Flashed Moon ROM, went through the install, it installed, rebooted, couldn't get past splash screen.
2. Pulled battery, cleared data, cache, dalvik and rebooted, stuck on the same splash screen.
3. Repeated step #1.
4. Cleared system. Now when I try to reboot I get "Your device does not appear to be rooted. Install SuperSU Now? This will root your device." Answering yes or no to this just reboots it to TWRP.
tl;dr So right now I can't get past TWRP.
Hotwir3 said:
Step by step:
1. Cleared data, cache, dalvik. Flashed Moon ROM, went through the install, it installed, rebooted, couldn't get past splash screen.
2. Pulled battery, cleared data, cache, dalvik and rebooted, stuck on the same splash screen.
3. Repeated step #1.
4. Cleared system. Now when I try to reboot I get "Your device does not appear to be rooted. Install SuperSU Now? This will root your device." Answering yes or no to this just reboots it to TWRP.
tl;dr So right now I can't get past TWRP.
Click to expand...
Click to collapse
Have you checked md5sum of the Rom?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
"The codes match!"
I'm tinkering around right now. I assume I still have root even though it thinks I don't....?
Fixed: I think it was because I selected a non-stock kernel... Not sure. I also unchecked all of the additional "tweaks" it asked if I was interested in.
Hotwir3 said:
Fixed: I think it was because I selected a non-stock kernel... Not sure. I also unchecked all of the additional "tweaks" it asked if I was interested in.
Click to expand...
Click to collapse
Glad to hear its fixed
suggest you to change the thread title as [Fixed] that should avoid us to come in and check
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!
Installed gederom, kept wiping, caches, dalviks, flash, reboot, always go past TWRP and into that boot animation - robot with CM9 near it.
Never goes past this point.
What am I to do?
Factory Reset flash the ROM again followed by gapps. should be fine then
yeah wipe all just dont wipe your sd card flash rom flash gaps if needed and go to mount and make sure there are no checks in the boxes of system and data if so uncheck them then reboot
acmys said:
Installed gederom, kept wiping, caches, dalviks, flash, reboot, always go past TWRP and into that boot animation - robot with CM9 near it.
Never goes past this point.
What am I to do?
Click to expand...
Click to collapse
Did you charge full your KF battery?
I installed ezterry's kernel on my rooted/unlocked a100 (stock ICS) and now every time I restart, I get a message that Google is upgrading before I get to my home screen. It's a minor quirk, just wondering if there's a way to stop it from doing that. I've tried wiping the gapps data via the settings menu, titanium backup, and cleared cache/dalvik in recovery, no dice.
xda_rulz said:
I installed ezterry's kernel on my rooted/unlocked a100 (stock ICS) and now every time I restart, I get a message that Google is upgrading before I get to my home screen. It's a minor quirk, just wondering if there's a way to stop it from doing that.
Click to expand...
Click to collapse
This would do better in his release thread....but anyways it usually subsides on its own. Reboot it a couple times in a row without installing any apps.
You can also clear cache and dalvik in recovery, which should be done every flash anyways, it will force it again then should stop unless its needed again.
Tapatalked from my Galaxy S II - CM10
Sorry, I tried posting there, but I realized I'm still categorized as a new user (I'm mostly a lurker). And thanks, I'll try your suggestion! :fingers-crossed:
xda_rulz said:
Sorry, I tried posting there, but I realized I'm still categorized as a new user (I'm mostly a lurker). And thanks, I'll try your suggestion! :fingers-crossed:
Click to expand...
Click to collapse
Oh yeah forgot the 10+ post rule for dev lol
Tapatalked from my Galaxy S II - CM10
Okay, I rebooted into recovery and cleared cache/dalvik again, then did a full reboot 5 times (I let it set a few minutes between each reboot). Still keeps saying "Android is upgrading". Any other suggestions?
xda_rulz said:
Okay, I rebooted into recovery and cleared cache/dalvik again, then did a full reboot 5 times (I let it set a few minutes between each reboot). Still keeps saying "Android is upgrading". Any other suggestions?
Click to expand...
Click to collapse
You could restore the stock kernel and see if it goes away, then try to reinstall ez's kernel.
I've seen the kernel cause this before when I was doing his test builds, it always eventually subsided on it's own over a couple of days, other then being a longer boot time it doesn't cause any adverse issues.
If you have a backup from CWM or TWRP, what he's referring to is an advanced restore:
CWM: (this is from memory)
Go to back/restore
go to backup
go to advanced backup (it may be in the same menu as backup)
uncheck everything except Boot, don't restore anything else
restore
clear cache /dalvik cache
reboot
TWRP:
Go to restore
uncheck everything except Boot
restore
clear cache / dalvik cache
reboot
I'll give it a couple days to see if it subsides on its own and then try the recovery if it doesn't. Thanks for the help, guys! :good:
Hi,
Im trying to install this rom.
Currently using using modpunk's cm9 alpha6.
Got little problem then decided to re-flashing the rom.
Im using CWM5.0.2.8.
What i did was,
1. boot into CWM
2. factory reset
3. clear dalvik cache
4. install from zip
installation was successful. however, my phone keep booting into H-BOOT everytime.
anyting went wrong in the steps?
hellilyntax said:
Hi,
Im trying to install this rom.
Currently using using modpunk's cm9 alpha6.
Got little problem then decided to re-flashing the rom.
Im using CWM5.0.2.8.
What i did was,
1. boot into CWM
2. factory reset
3. clear dalvik cache
4. install from zip
installation was successful. however, my phone keep booting into H-BOOT everytime.
anyting went wrong in the steps?
Click to expand...
Click to collapse
cleared cache partition too?
try going into "mounts & Storage" and formatting everything (except SD Card) and try again.
elspanish88 said:
cleared cache partition too?
try going into "mounts & Storage" and formatting everything (except SD Card) and try again.
Click to expand...
Click to collapse
just re-flash rom using modpunk's alpha7.
i will try that another time.
thanks for your reply.
hellilyntax said:
Hi,
Im trying to install this rom.
Currently using using modpunk's cm9 alpha6.
Got little problem then decided to re-flashing the rom.
Im using CWM5.0.2.8.
What i did was,
1. boot into CWM
2. factory reset
3. clear dalvik cache
4. install from zip
installation was successful. however, my phone keep booting into H-BOOT everytime.
anyting went wrong in the steps?
Click to expand...
Click to collapse
I have 2 ideas.
1. When you boot the phone, just press the button instead of holding it down like most people do. It will still boot properly and should cut out any chance of it booting into H-BOOT.
2. If it still goes into H-BOOT even just pressing instead of holding the button then factory reset, clear dalvik cache and install the zip all over again.
If the problem still happens then go to the original RobotoMod thread and post the problem there so the developer can see it. He'll have the best idea out of anyone.
hellilyntax said:
Hi,
Im trying to install this rom.
Currently using using modpunk's cm9 alpha6.
Got little problem then decided to re-flashing the rom.
Im using CWM5.0.2.8.
What i did was,
1. boot into CWM
2. factory reset
3. clear dalvik cache
4. install from zip
installation was successful. however, my phone keep booting into H-BOOT everytime.
anyting went wrong in the steps?
Click to expand...
Click to collapse
I had the same problem...
i tried again except this time i did a custom installation and did not install gappsextra.what you do is when it asks you if you want to install google apps...select install but in the next screen uncheck all the apps(there are only 3)....that should do it.
---------- Post added at 01:10 AM ---------- Previous post was at 01:04 AM ----------
im getting some problems after installing the rom though and was hoping i could get some help on it.
first of all it does not recognise my ext partition through terminal or recovery...
and also my mobile network doesnt work smoothly after i installed this...i have to keep rebooting it for it to work.
I also have problem
I also face a problem while installing that rom. That is not boot. My phone is reboot to recovery when it had finished the installation. How can I fix it???
DuWun said:
I also face a problem while installing that rom. That is not boot. My phone is reboot to recovery when it had finished the installation. How can I fix it???
Click to expand...
Click to collapse
did you try the custom installation like iv mentioned?
I'm having a similar problem
When I first installed RobotoMod I used the recommended settings, but after the reboot the phone just stays on the white HTC screen it was, at first i thought it was just loading, so i gave it a little more time (about 7 hours) but still nothing happened, so I tried using the custom settings and through multiple attempts and combinations all on the CM9 alpha it booted up, but as soon as it was done loading it put me straight into the lockscreen and wont unlock no matter what I do, I've tried AOKP but that just gets the 1st problem, and ive seriously tried everything and I haven't found anyone with the same problem maybe its just me, i installed using CWMR 5.02.8
use
DuWun said:
I also face a problem while installing that rom. That is not boot. My phone is reboot to recovery when it had finished the installation. How can I fix it???
Click to expand...
Click to collapse
use gapps extra instead of rcommended ones on 2 pop up
I have a ATT Samsung Galaxy S3, running Android 4.2.2. I was putting Clockwork on and when I got done and rebooted system, nothing. It vibrates once and the words Samsung comes up then total black screen. Bootloader and downloader still work fine. I formatted, put a rom back on but the same thing happens. It just seems like there is a missing file that is stopping it from continuing to start up. Can someone give me some guidance. I jailbroke my phone 2 years ago so I am very rusty. Thanks for the help.
Clear data, dalvik, and cache in recovery, then reboot.
WARNING: doing this will wipe your data off the phone.
audit13 said:
Clear data, dalvik, and cache in recovery, then reboot.
WARNING: doing this will wipe your data off the phone.
Click to expand...
Click to collapse
cleared both, then even formatted. Like I said before, when I turn it on it vibrates, then the Samsung (in white) comes up then it goes to the black screen and stays there. Like its getting hung up. All happened after rebooting system in clockwork.
What ROM was on your phone. You mentioned 4.2.2 but I don't think ATT released a 4.2.2 ROM.
audit13 said:
What ROM was on your phone. You mentioned 4.2.2 but I don't think ATT released a 4.2.2 ROM.
Click to expand...
Click to collapse
I had a cyanogen mod on couldn't tell you which one exactly. My android version was the 4.2.2
what do you think of turning it back to stock, not that I want too?
You need to know which bootloader was on your phone before trying to restore to stock. The bootloader will determine how to restore the stock ROM.
First of all, boot into download mode and tell me what it says on the screen.
actually I had both twrp and clockwork both on there. Here is what is says on a start up downloader screen: A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise, press the volume down key to cancel.
if you have terminal emulator on your phone , type in
getprop ro.bootloader (you need the space) and press enter. this will tell you your bootloader version.
err on the side of kindness
Either do what Mrrocketdog suggested or go past the warning message to the download mode.
oooopps! forgot about going past warning message. been a very long long time since been there. :thumbup:
err on the side of kindness
I never put emulator on my phone. Here is what I just did, I followed the Cyanogen d2lte to the T. Rebooted and now it is stuck on the Samsung GalaxySlll screen with the little blue android. I flashed both files thru my recovery. Again, everything started after I rebooted my system for the first time after installing the clockwork mod
I have no idea, but jst a though. Would it help to go to advanced, mounts and storage, in clockwork and format everything except my sd card?
bootloader is clockwork v6.0.4.7
CWM is the recovery, not the bootloader.
Boot to recovery. Format system, cache, data, flash cm11, reboot
thanks for being patient with me. i will try and let you know
. this site would be nothing without people like you.
here is what i did,(1) wipe dalvik and cache. (2) reboot(3)apply cynaogen bootloader update. (4) in this step it tried rebooting to recovery and not before applying cm11. when i reboot the system it gets stuck on the samsung galaxyiii with the blue android guy, the screen gets stuck right before it would boot to the cynagogen screen. again all my problems started when i added clockwork mod and rebooted. at that time i already had twrp. what would i have to do to remove clockwork mod or just help me just start from the begining drawing board. thanks.
tepeee said:
here is what i did,(1) wipe dalvik and cache. (2) reboot(3)apply cynaogen bootloader update. (4) in this step it tried rebooting to recovery and not before applying cm11. when i reboot the system it gets stuck on the samsung galaxyiii with the blue android guy, the screen gets stuck right before it would boot to the cynagogen screen. again all my problems started when i added clockwork mod and rebooted. at that time i already had twrp. what would i have to do to remove clockwork mod or just help me just start from the begining drawing board. thanks.
Click to expand...
Click to collapse
You need to wipe data, cache, dalvik, mount system, format system, install CM11, reboot.
audit, i did exactly what you said and nothing the same results. stuck on the samsung blue android screen.