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.
Related
okay, i was trying to root and flash cyanogenmod9 on to my friends s2. i personally have a droid x, that has been flashed a billion times, so i had a good idea of what to do. i rooted his phone using odin to flash clockwork, then flashed superuser in clockwork. after confirming i had root i booted into clockwork, and wiped cache and data. then flashed the hercules.zip and gapps. here's where things get tricky. his power button is broken and everytime i tried to reboot it couldn't because the power button was constantly pressed. eventually he got it to boot, but it never booted up completely, it just stayed on the boot animation. my question is did i do something wrong? do you guys thinks its because of the button since it couldn't have a fresh boot up. should i try flashing another rom to see if that works? any ideas?
I ran across this problem when I was flashing a Jellybean version of Cyanogenmod. If you flashed it on a NON-TOUCH recovery it will most likely boot loop like mine did. I installed a touch recovery and flashed and BANG. I had had Cyanogenmod. Hope this helped
This was my fix...
dj923 said:
okay, i was trying to root and flash cyanogenmod9 on to my friends s2. i personally have a droid x, that has been flashed a billion times, so i had a good idea of what to do. i rooted his phone using odin to flash clockwork, then flashed superuser in clockwork. after confirming i had root i booted into clockwork, and wiped cache and data. then flashed the hercules.zip and gapps. here's where things get tricky. his power button is broken and everytime i tried to reboot it couldn't because the power button was constantly pressed. eventually he got it to boot, but it never booted up completely, it just stayed on the boot animation. my question is did i do something wrong? do you guys thinks its because of the button since it couldn't have a fresh boot up. should i try flashing another rom to see if that works? any ideas?
Click to expand...
Click to collapse
If it is the CM9 bootloop issue (where it hangs at the little blue dude) check out this page (sorry it won't let me insert a link because I'm a new user lol):
forum.cyanogenmod.com/topic/59357-cm9-boot-loop-issues-my-solution/
I couldn't get it to work until I followed this method, likely the use of Darkside Super Wipe and Darkside Cache Wipe was what fixed it. Hope this helps.
OOOhhh this happened to me when i first rooted my phone LOOOL......this is what u do....
if you are on cwm 5.0.2.7 or lower...u need to use darkside super wipe then flash the rom
i did the darkside wipe and it booted up fine. thanks a lot guys!
if cant be fixed flash stock. it happened to me once too. i think it was because i flashed the wrong radio
Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Runge2970 said:
Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Click to expand...
Click to collapse
flash twrp recovery via fastboot
simms22 said:
flash twrp recovery via fastboot
Click to expand...
Click to collapse
okay, just did. Tried the wipe and cleat options on that, but whit same results...
Runge2970 said:
okay, just did. Tried the wipe and cleat options on that, but whit same results...
Click to expand...
Click to collapse
are you wiping data(factory reset) or are you just wiping your dalvik and cache?
Runge2970 said:
Hi you guys. Im have a bit of trouble whit the CWM. Im stuck in a kind of bootloop after updating to latest CM10. It boots up and i can access my homscreen for like 6-7 sec, but then it reboots to bootscreen.
So i thought i have to wipe my data, get it back to factory state. So i do that, wipes cache to. I have even tried the Mount and storage > format /system /cache and /data.
But when i re-install my rom allmy apps, wallpaper and that, are all where i put them. I can even mange to open some of the apps whitin the 6-7 sec window i have before the phone will reboot. The CWM says it done all things right. No error messages at any time ...
Any one whit an idea to get this back on track ?
Click to expand...
Click to collapse
OK do what simms22 has explained. That should work.
But from what I am interpreting is that you are doing cache not wipe. So you go to "wipe data/factory reset" menu and hit/press yes. It should wipe it and done. BTW it might have been in a boot loop because you might of dirty flashed or you didn't wipe cache and dalvik cache. That is very important to remember. Never dirty flash and also wipe cache and dalvik cache.
Also did you play with tweaks and such before this was happening. Like voltage or over clock because that could be the problem too.
Dalvik cache and cache are hash signed by the last rom that was flashed. New rom, new hash sign. No need to wipe caches, just data.
Sent from my i9250
Cwm is notorious for failed wipes.
Definitely upgrade to twrp, and if your phone is so messed up twrp can't wipe it, use the android revolution wipe script.
Sent from my Galaxy Nexus using xda premium
If you're backed up and don't mind losing EVERYTHING, yes, EVERYTHING in /data, then boot into fastboot mode and run
Code:
fastboot erase userdata
from your computer. (Might need root privileges if running on Linux)
Hi guys. I got it to work finally. I didt some tweaking whit the DPI. Maybe that was the cause of the crash ??
But i went to use the Galaxy Nexus toolkit, first of all to flash the other recovery program. But since it dint work either i flashed it whit sock rom, from the same toolkit at started all over. That did work, but hell of a way to go
Hi
I was flashing back to Stock from task650 to fix my gps. Well something blew up and when the phone reboots the screen goes black but I hear the AT&T start-up tune. Essentially I can't get to enable USB debugging to reflash. I can get to download or recovery, but there are no files to recover<?> and busybox never got installed.
What do I do now?
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
CZ Eddie said:
Do you have the stock recovery now? If so, try going in there and resetting to defaults. That helps sometimes.
Otherwise, you may need to Odin back to stock if you still want to go stock.
Click to expand...
Click to collapse
Yes I have stock recovery. Odin is of no use because it hangs waiting for the USB debug to respond. And i can't turn it on because the screen is black and I can't navigate
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
xBeerdroiDx said:
Do you have a micro sd card? If so, throw a rom on there. If you want to go back to stock, there' a flashable stock zip at the bottom of post #2 in the link in my signature. Under the emergency toolkit section. Flash that, turn on use debugging, do your gps fix and continue on with the task release
Click to expand...
Click to collapse
Thanks. I created an emergency tool kit on an SD, I wiped data, wiped cache and Davlik and formated system. Flashed the stock rom. When I rebooted it now hung at the Samsung Galaxy S III screen.
How do I get out of this mess?
Try wiping data and cache again in recovery
xBeerdroiDx said:
Try wiping data and cache again in recovery
Click to expand...
Click to collapse
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
BertMor said:
I've wiped data and cache several times, and format/system. I've even tried to flash CWM 6.0.3.1 and I get a status 7 error. Nothing is taking.I get signature failures.
I re downloaded all the files figuring they were corrupted. Nothing doing. I need some real help, because this is beyond my abilities to figure out.,
Now I've got a red triangle showing up in recovery.
Click to expand...
Click to collapse
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
xBeerdroiDx said:
i dont know why some of these things are not working correctly for you. you're seeing the red triangle because you have stock recovery now from the stock firmware zip. you cannot flash anything in stock recovery nor can you format /system. what happens when you boot up after a factory reset and cache wipe?
a couple of your options include either using odin to flash the stock firmware back onto your device or to use odin to flash a custom recovery back and make a move from there.
Click to expand...
Click to collapse
When it rains it pours. Now I can't get into recovery. I get the empty battery graphic cycling on and off, and its very warm to the touch. I think the battery is not charging.
I tried using Odin and flashed a stock rom but I kept getting verification errors and status 7 errors. Things just are not taking. I fear I've got a hard brick and I don't know what to do to fix it.
I appreciate your help
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
xBeerdroiDx said:
aaaaand let the questions roll:
you got verification errors in odin? and after flashing the firmware, i'm assuming you then flashed cwm and that's where you were getting the status 7 errors?
at what point did it all go off? i need to know what order you did all of these things.
can you still get into download mode?
Click to expand...
Click to collapse
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
it might indeed be drained. leave it plugged in for a while and report back.
you were getting the error/status 7 messages after you flashed cwm back on it likely because the cwm wasnt up-to-date.
what was the last thing you tried before it stopped working altogether?
It gets really hot if I leave it plugged in. But it seems like I can get into recovery again. The last thing I flashed was CMW 6.0.3.1. But what is on it now is CMW 5.5.0.4
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
BertMor said:
No, it won't go into download. I initially flashed stock rom, but I don't think I wiped anything. That was probably the big mistake. I used something called Samsung S3 QCom tool kit to do an initial flash. It never failed me before. And I also flashed a CWM.
I followed your advice and made a emergency SD kit and flashed from there. I did a clean flash several times. Things just never worked and I kept getting those error messages. Then it just got more difficult to get into download. Now it just flashes a drained battery
Click to expand...
Click to collapse
xBeerdroiDx said:
actually, what you're saying is the last thing you flashed was cwm 5.5.0.4, just via odin not cwm.
if the phone was in my hands, i would:
flash the cwm 6.0.3.1 zip, select advanced and reboot recovery. now you will be in the updated cwm recovery.
perform a full wipe: wipe data, cache, dalvik, format /system, format /data
flash rom and gapps. if you're going to stick with tasks, use the 4/23 release. i'm on that with no feature or stability issues.
wipe data, wipe cache, reboot.
give it a few minutes to boot up.
Click to expand...
Click to collapse
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
BertMor said:
Nope. When I try to flash CWM 6.0.3.1 I get an assert failed error. I came across this fix, I wonder if it is safe to try http://mobotechie.com/tips-tricks/how-to-fix-android-custom-rom-status-7-installation-abort-assert-failed-error-in-recovery-easily-ultimate-guide
Click to expand...
Click to collapse
Well I think I managed it!. First I tried to install an update d/l'ed from Dropbox and that did nothing. Then I flashed an old .tar that was a rooted stock and it rebooted!
I tried editing the updater-script but I couldn't getit to save the changes properly.
Well I will now re flash the RM and CWM and hope for the best
Thanks for all your help, greatly appreciated
I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.
Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.
I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.
CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...
It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!
Hi guys,
I have a Samsung Galaxy S3 I747m, running Cyanogen Mod and as of right now, it will not turn on. It will begin the boot animation and the freeze once it reaches the end. I cannot access Recovery Mode but I can access Download Mode. This all began when my version of gapps started glitching, or at least Google play Store. I downloaded a new gapps and tried to install it without wiping out the dalvik cache or uninstalling the old gapps. Yes I am a noob at this and an idiot.
Please guys if anyone of you has the patience to tell me what I need to do to get my phone operational again. please do so. My family is not doing well financially right now and can't afford another phone. Please give me some hope. Please.
Well.....I'm not expert but I can tell you its not hard bricked. So you're safe for now. I suggest checking out how to flash another OS using download mode. I believe it involves using your sd card as a "bootable media". (Like, usb stick for windows 7)
Do some research about that. And I think it should work.
Try this!
ABCordova said:
Hi guys,
I have a Samsung Galaxy S3 I747m, running Cyanogen Mod and as of right now, it will not turn on. It will begin the boot animation and the freeze once it reaches the end. I cannot access Recovery Mode but I can access Download Mode. This all began when my version of gapps started glitching, or at least Google play Store. I downloaded a new gapps and tried to install it without wiping out the dalvik cache or uninstalling the old gapps. Yes I am a noob at this and an idiot.
Please guys if anyone of you has the patience to tell me what I need to do to get my phone operational again. please do so. My family is not doing well financially right now and can't afford another phone. Please give me some hope. Please.
Click to expand...
Click to collapse
I would try and flash a new recovery image either twrp or cwm through download mode using Odin and try getting back into recovery and clean flash cyanogenmod and gapps all over again. Basically start from scratch and see if it fixes the problem, if you can get in to recovery mode after flashing a new image you may only need to wipe cache/dalvik to fix it but I'd start with trying your best to get a recovery image reflashed and the ability to get into recovery mode. You can find the images for recovery at the official sites either twrp or clockwork recovery and the instructions on how to flash them anywhere by searching through Google! Hope this helps you
From download mode you can flash a stock firmware with Odin unless you have installed the stock 4.3 update. This will wipe your phone but you will have it booting and recovery back.
NightyNineNights said:
I would try and flash a new recovery image either twrp or cwm through download mode using Odin and try getting back into recovery and clean flash cyanogenmod and gapps all over again. Basically start from scratch and see if it fixes the problem, if you can get in to recovery mode after flashing a new image you may only need to wipe cache/dalvik to fix it but I'd start with trying your best to get a recovery image reflashed and the ability to get into recovery mode. You can find the images for recovery at the official sites either twrp or clockwork recovery and the instructions on how to flash them anywhere by searching through Google! Hope this helps you
Click to expand...
Click to collapse
Thank you so much! However, in the Clockwork Mod website, it does not say anything about downloading Clockwork Recovery. What should I do from this point? Also, some people suggest installing an entirely new OS. Would this be a better or worse solution compared to flashing Clockwork Mod Recovery?
Thank you once again!
BCSC said:
From download mode you can flash a stock firmware with Odin unless you have installed the stock 4.3 update. This will wipe your phone but you will have it booting and recovery back.
Click to expand...
Click to collapse
Another user here suggested flashing Clockwork Recovery. Which one one in your opinion is the best option and what are the disadvantages/advantages of both?
ABCordova said:
Another user here suggested flashing Clockwork Recovery. Which one one in your opinion is the best option and what are the disadvantages/advantages of both?
Click to expand...
Click to collapse
As for your previous post, the Clockwork downloads are under the 'Rom Manager' tab here: http://www.clockworkmod.com/.
Twrp recovery here: http://teamw.in/project/twrp2 (Hit 'Get TWRP for your device' then this link at bottom of page 'Download - Odin Flashable Tar:').
Which you chose depends on which you had before the issue and whether you want to restore a previous backup once recovery is restored. If you are not going to be restoring a back up, I'd recommend the TWRP file as it can be flashed with Odin.
Your other option is to Flash a stock firmware from Odin and start from scratch. This can be the more labor intensive way because you then need to setup the phone again and get it back to how you like it. The benefit of this method is that it wipes absolutely everything, including whatever problem had you screwed in the first place. Because I tinker with my phone a lot, I always have everything important stored on an external SD. Pictures, Titanium Backup, Nandroid, etc. If you have backups of everything you need off the phone, I'd recommend that you Odin it. If you do not have things backed up try installing recovery first and getting the phone to boot. In the end if you do chose this method you should still wipe as there was obviously something that really buggered your phone and a wipe will be the best way to fix that so it doesn't recur. That's my opinion anyway.
Update!
Apparently I can access Recovery Mode now!! However, it still does not boot up. I backed up all my filed to my external 8GB SD card, and then wiped the dalvik Cache. Nothing. I did a full Factory reset and still nothing. AM I missing a step? Is there a step I should take before or after clicking full wipe? The phone boots all the way to cyanogen mod logo, where an arrow spins around it. However, that's all it does.
Any ideas?
ABCordova said:
Apparently I can access Recovery Mode now!! However, it still does not boot up. I backed up all my filed to my external 8GB SD card, and then wiped the dalvik Cache. Nothing. I did a full Factory reset and still nothing. AM I missing a step? Is there a step I should take before or after clicking full wipe? The phone boots all the way to cyanogen mod logo, where an arrow spins around it. However, that's all it does.
Any ideas?
Click to expand...
Click to collapse
So you can access recovery mode?
*Before you follow the next steps, understand everything will be deleted from your PHONE, NOT sdcard.*
You have to wipe everything clean. That means(in recovery mode):
Wipe Data/factory reset
Wipe cache partition
Wipe dalvik cache
Then you would install your rom. From there everything should work. Also, are you installing CM10.2? 10.1? 11? (I personally suggest 10.2.)