Develop Bugs

Please help! CWM not working at all.

I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.

spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Odin back to stock, or flash twrp and try that. Also this should not be in this section bud. Prepare to be flamed by the community
Sent from my SGH-T989 using xda app-developers app

I had the same thing happen to me when I updated to the latest one, it would freeze at either restoring, or wiping cache. Luckily I was able to just reboot, and everything was fine on the phone, I then downgraded to 5.XXX

I've been having the same issue on stock recovery, where it sometimes it freezes at wiping, then flash the one from rom manager and its all good. by the way mods please move the thread to Q/A

Wrong section bro. Please see the noob video.
Sent from my SGH-T989 using xda premium

You don't have to Odin stock or any of that stuff, just fastboot flash the 6.0.0.5 version (or that last one that worked for you) and you should be fine.

spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!

kangelov said:
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
Click to expand...
Click to collapse
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...

spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
Look, I'm sorry for your troubles but there is a good reason why we have four different sections. This thread being in DEVELOPMENT is only causing clutter. You will get much better help if its moved to its proper place, Q&A or general. Please PM a Mod to move this.
Sent from my SGH-T989 using xda premium

spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?

kangelov said:
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
Click to expand...
Click to collapse
I dont really know where to find 5.0.2.7. the website doesnt seem to have it. I used revolutionary

Thank you for your contribution to the development of the gs2.
Sent from my SGH-T989 using xda premium

Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app

Rushing said:
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all

spuzwuzzel said:
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
Click to expand...
Click to collapse
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium

LoopDoGG79 said:
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ya Odin flash the recovery tar is probably the easiest way to go
Sent from my Galaxy Nexus using xda app-developers app

Odin is a tool used internally by Samsung. As such, you can't expect Samsung to write you a manual. Be very careful, you can cause a lot of damage with it. It is powerful, though: it can bring your phone back from the brink of death. Or it can take a healthy phone and send it over the edge. What you are doing now is something every rooter does on day 1, and only after days and days of research. I am uncomfortable with what you are going to do now given that you have never done this before, but you have no choice: it's this or a useless phone.
Here's the rundown:
A PIT file is something like the Master Boot Record of your harddisk. Problem is, the first partition is something like your computer's BIOS: it tells your phone how to bootstrap. It can bootstrap into the normal mode, which runs Android, or it can initiate Download mode. Download mode is what ODIN needs to replace parts or all of your phone's software. If something goes wrong with that bootloader, your phone is something called a hard brick: it won't power on, it won't even run Download mode so that you can recover it back to stock. It is dead. If that ever happens, you need something called a JTAG flash: you send your phone out somewhere, and someone takes it apart, hopefully carefully, plugs a programmer into an engineering port on your phone's logic board, and reprograms the bootloader back again). Now with PIT file having the major potential to trash things completely, you really have to pay attention you don't load the wrong one. Problem is, the ODIN you just downloaded DOES come with a PIT file, and that PIT file is WRONG for your device. Follow the instructions! Follow the instructions really really carefully. Don't check off extra things! Don't uncheck things that should be checked! Don't add PIT files! Make sure you load the right file to the right place in ODIN. Your phone depends on it.
ODIN will program your phone from scratch, but you wouldn't want to use it too often. It's a dangerous tool, as you can imagine, and it is meant to replace your phone's software, not maintain it! That's why we have Recovery. Recovery is what you use to do basic maintenance to Android, such as factory reset and clean cache and stuff. With those custom recoveries out there, you gain the added ability to flash custom ROMs and a few other things as well, which is what this forum is all about. So, step one in anyone seeking to root their phone is, flash a custom recovery using ODIN, since you need Download mode for that. In an ideal world, you will never need to use ODIN again after you flash your custom recovery. Well, in the real world, you should needed it only very infrequently.
Your phone first got its custom recovery from a tool designed to automate things for you, and sent you flashing without ever giving you an idea how your phone works. Now you don't know how to recover your phone from a flash gone wrong: in the long run that tool did not do any favours to you. The steps I gave you will bring your phone back to life, it brought mine several times already. Something about those new JB ROMs corrupts every recovery I have tried. I don't know why, I don't know how, but it does it. To make matters worse, ODIN without a proper PIT file cannot repartition your phone and fix whatever mess caused the problem to begin with, so restoring stock directly won't do the trick, you need to flash custom recovery, to fix recovery, and then Superwipe to recreate and realign your system, data and cache partitions: that's a good chunk of your phone. So, after you do this, you should be back in business. From beginning to end, if you know what you are doing, the entire process should not take more than 30 minutes, but don't rush. Take your time: take hours, take days. Take all the time you need.
Read before you do anything, and ask if you don't understand.

I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?

gypsy214 said:
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
Click to expand...
Click to collapse
I have had the problem you describe as well. Some ROMs like certain recoveries better than others and if you end up with the wrong combo, they don't boot. Flashing the right recovery after that fixes it instantly, without even a need to reflash the ROM. No, this is a different problem.
We are talking about a problem where flashing a ROM corrupts your recovery so it will stop working on you completely: it just hangs, it won't restore, it won't flash anything. Also, one or more of the ROM partitions on your phone get corrupted somehow so that even ODIN back to stock doesn't get your phone working again (you end up with a fully stock phone that doesn't boot). Maybe the two are related, but I will let those who know more speak. I am just a regular guy who fiddles with his phone a lot more than he should.
As for the problem being on JB only: I've only had it when flashing JB ROMs. I first noticed it with MIUI, but then AOKP started acting up, and when I finally dared to flash a CM10 unofficial nightly for the first time, it happened too... And then I noticed it doesn't happen always, only sometimes, and other times it just leaves me with a JB ROM that doesn't boot, and in some rare occasions: it works without a hitch. Go figure.

Clockworkmod Recovery Incessantly Freezing

---First off, let me preface this by acknowledging the fact that, yes, I am indeed a noob. And I'm sure some of the info I'm going to put in here probably isn't needed, but as I said, I am a noob, and thus am not entirely sure what is relevant and what is not. I also apologize if some of what I say and/or what I did doesn't make sense and/or is idiotic, but again, noob. That being said I don't have any techie friends and never really had a nack for this kind of stuff, but hey gotta start somewhere right? So, that being said, here's my dilemma:
This all started last week when I was downloading the CyanogenMod Nightlies *Rom. The download started and was going along just fine when my phone suddenly turned off and starting vibrating and then wouldn't turn back on. Everything I would press power it would just start vibrating in regular one second intervals over and over. Finally I remove the battery. It turns back on fine. Download resumes. And... Bam! Happens again. This time I try the same remove to no avail and about 15 minutes later I'm thinking that this is it for my phone when it finally reboots. So I decide, alright, lemme just download this Rom and try to flash it, or at the very least just restore the phone and hope this is a software issue. So I had also just downloaded Rom Manager and was going into recovery via Clockworkmod recovery as the instructions prompted me to in the CyanogenMod tutorial. Now every other time I have installed a new Rom I just manually boot into recovery as the phone turns on. This time I boot into the Clockworkmod recovery though cuz I wanna follow the directions to the "T" and I proceed to selecting the factory reset and it wipes the data and freezes when wiping the cache. So I'm sitting there like, "Oh s**t, what do I do now?" I let it sit for fifteen minutes hoping it will magically unfreeze and all will be right in the world, but it doesn't and I reset the phone via the power button. Then it boots up and tells ne there a issue with my custom OS and I'm not really are what to do here. So, i reboot it and it acts like the reset was successful and prompts me to set up my phone like I just flashed the Jedi Mind Trick Rom I've been using. So I tried again, and same thing. Got stuck on clearing the cache. Luckily it lets me set up the phone again after I interrupt the frozen factory reset. This time I try to boot into recovery manually, pressing the hard keys, and all the phone does is restart. So I try again. And again. And again to no avail. I look up the key sequence thinking I may have forgotten it and am doing it wrong, but after trying every combo I can find online, it still doesn't work. So I give up and go into recovery via clockworkmod and restore my phone to my very first nandroid backup I made before I ever started messing with custom roms, and everything goes fine it seems until it gets to a command about something revolving cache and it freezes again! I eventually have to reset it and it gets stuck in a loop where the Samsung logo comes up, it makes a loud annoying beeping noise for a few seconds before it turns off and does it all over again. Now I'm sure I've bricked my phone. I take out the battery, wait, put it back in, but still nothing. I do this a few more times, wait and hour, and it finally boots up. So now I try to go into recovery manually again, but still just get the phone resetting. I try to go uninstall clockworkmod and go into recovery via Rom toolbox pro, but I still get the clockworkmod recovery rather than the phone's normal recovery I used to be able to get to before I ever installed clockworkmod. So I'm stuck here. I know that's a lot of info, but I didn't want to leave anything out incase it was important. Thanks in advance for any advice and/or directions you can give me. *
P.S. I read in someone's post here that the first issue of the phone turning off and vibrating could be the result of a bad power sensor. So I wanted to add that since this two mysterious restarts and vibrations, nothing like that has happened in the... Approximately 5 days since (for whatever that's worth). *
Thanks again, and I apologize for any ignorance you have encountered while trying to read this post.

OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app

Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?

whatiznt said:
OK seriously... save yourself the trouble and just flash TWRP recovery instead.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Ok. Checked it out and got twrp. I clicked install openrecoveryscript. It downloaded. Didn't restart or anything. Now can I just flash the new Rom I want directly from there then? All it says it that I must have installed the recovery script. Just wanted to know though, is it still right that when I reboot into recovery it goes to the cwm recovery? Just wanna make sure before I go messing up my phone.
Thanks!

mintharis said:
Missing some needed info...
Current status? What do you have access to? Recovery? Does the ROM boot?
Any issues with the phone right now? (You say no mysterious reboots for 5 day now, just confirming)
Recovery version? If you're using CWM I would suggest against using ROM manager. I would also suggest you do use the darkside scripts for wiping your phone.
Exact ROMs you flashed?
Click to expand...
Click to collapse
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!

I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..

VoiD_Dweller said:
I thought the new version of CWM was freezing, but it just takes FOREVER to do your first backup because it's building the blobs or whatever they are called. The second backup went fine, however, I think it's too much headache and went back to the 5.0.2.7. Call me crazy but I'm still very hesitant to use TWRP after the wave of phone bricks that happened a few months ago from people installing it.. I'm still not convinced its totally safe and stable..
Click to expand...
Click to collapse
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!

jalight27 said:
Currently I'm running the stock ICS Rom for the phone. Ill attach a screenshot of the specifics. I can go into cwm recovery but anything related to cache freezes. No issues with the phone other than I can't use my hard keys to boot into recovery when restarting the phone, if that even counts. I'm using cwm v6.0.1.4 and really I don't want to use cwm, how do I go about changing that? And I downloaded the darkside supervise and cache wipe. Do I just use those instead of the factory reset in the cwm recovery? Or did I read into that wrong?
Thanks!
Click to expand...
Click to collapse
Yes, the darkside scripts were used in older cwm recoveries because the default wipes didn't do the job. As for switching away from cwm I'm guessing you want to jump to twrp. You can do that by following the instructions at http://teamw.in/project/twrp2/101

same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun

Thanks for the steps there. Pretty much did a combo of what everyone was saying. Went back to an older version of cwm and used darkside wipes. Then wouldn't you know? It worked! Yay for me. So I'll just keep my older version of cwm, for now at least. Well, anyway, thanks to everyone for helping me figure this out. Much obliged!

jalight27 said:
Now when you day forever, what are you talkin here? I waited a very long time. Regardless though sounds like an easy solution so ill try this real quick and see. You think just reverting back to use 5.0.2.7. Would solve the cache problems I've been running into or would I have to try to clear that up first and then this would work?
Thanks!
Click to expand...
Click to collapse
Forever like being 10 minutes min, maybe 15

ClaireH said:
same thing happened to me on cwm v6.0.1.4 so this is what i did
1. flash an older version of cwm thru odin (search "cwm recovery tar t989")
2. reboot to cwm
3. darkside cache wipe (hopefully that will get to your homescreen, if not, super wipe and new rom that *****)
4. when you are at your homescreen, download and install goomanager from store
5. open it, tap the menu button, hit Install OpenRecoveryScript
6. reboot to recovery
7. now you have twrp, have fun
Click to expand...
Click to collapse
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?

fe1ixs said:
+1.
Just happened to me last night. I was using CWM 6.0.1.4 touch version and finally crash without reason.
I almost tried to ODIN back to stock/unroot, then I thought it might be possible just re-flash the CWM recovery to 5.0.2.7 version.
And it works!
try to avoid 6.0.1.4 version at this time. lots of issues.
btw, twrp is better than CWM? what's the difference? how do I activate the recovery menu from boot?
Click to expand...
Click to collapse
Yep, same thing I ended up doing, thought I posted that but I guess I never did. I ended up using the darkside wipes and going back to an older version like you and someone else said. Now everything's just fine. And btw, to get into recovery from boot just restart it holding power, volume up, and volume down at the same time. Then once you see the Samsung logo let go of the power button but keep holding volume up and down till you see the recovery menu.

[solved] [Q&a] s3 stuck at Samsung logo

Hey guys
A buddy of mine has his s3 stuck at Samsung boot logo it won't do anything can't get into safe mode or anything. His phone is not rooted and he needs to recovery some important business text from the phone . I am wondering is there anyway to install a custom recovery and nandroid his device then restore it with his data. Or if there is anyway to get it. To device to recovery the data? I know you can wipe it but he can't have that happen with the data
Thanks in advice
PS: I looked already and only found ways to wipe to recovery so far
Sent from my blazing fast nexus 4 o yeah baby this phone is awesome

Re: [Q&a] s3 stuck at Samsung logo
you should be able to get into download mode. pull the battery, replace it, and volume down + home + power button.
if you can get to that, shut the phone down and download Odin here, install drivers from here if you need to, put the phone in download mode, and flash this in the pda section.
if you successfully get to that point, reboot into recovery using volume up + home + power, and then you should go to backup and restore using the volume up/down buttons and make a backup. it doesn't matter if you choose internal or external unless you don't have space on one of them. once it's done backing up, go to wipe data/factory reset and wipe. then go back to backup and restore and select advanced restore and only restore /data.
this should achieve what you want. hopefully it boots. if it doesn't, wipe data/factory reset again and boot. if it boots, there's most likely a problem with an app installed. I don't know what to tell you if that's the case.
if this worked, use this in Odin to go back to stock recovery if the phone is on DLK3.
hopefully I got everything right! it's 4 in the morning for me, if anyone sees a mistake let me know!
sent from my i747 with xda-premium

Alicklee said:
Hey guys
A buddy of mine has his s3 stuck at Samsung boot logo it won't do anything can't get into safe mode or anything. His phone is not rooted and he needs to recovery some important business text from the phone . I am wondering is there anyway to install a custom recovery and nandroid his device then restore it with his data. Or if there is anyway to get it. To device to recovery the data? I know you can wipe it but he can't have that happen with the data
Thanks in advice
PS: I looked already and only found ways to wipe to recovery so far
Sent from my blazing fast nexus 4 o yeah baby this phone is awesome
Click to expand...
Click to collapse
i'm assuming you've tried a battery pull?

Re: [Q&a] s3 stuck at Samsung logo
Thanks for the info.
I ended up putting custom recovery twrp and using it to do a full back up, then wipe and doing a restore, it didn't work still had the same problem, but I figure it has to be one of the 5 partitions restored from backup? I so one by one I flash each partition to see where the problem was.
I tried different roms, but the problem only happen right after I restore the data file
It turn out to be the data files In the data partition, soon as I restore that it would do the same thing. I am so I ended up going to file manager in the twrp file manager and Manually copying the log files for the text and phone number I was not able to find the call log file but the other two was easy to get plus was able to get most of his media data that was on the Phone saved too. I copy the log into the new flash rom and it worked Al lhis txt messages are saved! I
cehf said:
you should be able to get into download mode. pull the battery, replace it, and volume down + home + power button.
if you can get to that, shut the phone down and download Odin here, install drivers from here if you need to, put the phone in download mode, and flash this in the pda section.
if you successfully get to that point, reboot into recovery using volume up + home + power, and then you should go to backup and restore using the volume up/down buttons and make a backup. it doesn't matter if you choose internal or external unless you don't have space on one of them. once it's done backing up, go to wipe data/factory reset and wipe. then go back to backup and restore and select advanced restore and only restore /data.
this should achieve what you want. hopefully it boots. if it doesn't, wipe data/factory reset again and boot. if it boots, there's most likely a problem with an app installed. I don't know what to tell you if that's the case.
if this worked, use this in Odin to go back to stock recovery if the phone is on DLK3.
hopefully I got everything right! it's 4 in the morning for me, if anyone sees a mistake let me know!
sent from my i747 with xda-premium
Click to expand...
Click to collapse
Sent from galaxy s2x close by using the force of jedi knight 3 while charging my nexus 4

Re: [Q&a] s3 stuck at Samsung logo
What's a battery pull?
Lol jk I did it.
xBeerdroiDx said:
i'm assuming you've tried a battery pull?
Click to expand...
Click to collapse
Sent from galaxy s2x close by using the force of jedi knight 3 while charging my nexus 4

[Q] I soft bricked my phone...

Last night I soft bricked my phone. At least from what i have read it is a soft brick. The phone will power up to the Samsung Galaxy s3 screen. I can also get into download mode and cwm. I am hoping this means that phone has been soft bricked.
As far as why my phone did this...I booted into cwm and i did a restore through the menu options. I'm not sure if i hit the wrong one, or what exactly happened at this point. Whatever it was loaded and i was unable to get past the gs3 screen.
I tried loading a .Tar file from a tutorial provided by "Theexcel". The tutorial was to flash the new tar onto the phone through Odin. However, in the tutorial, it says to make sure that the flash counter is set back at zero. How can i do this when my phone won't power on. I am not aware of how to reset the counter without getting an app from Playstore.
As you can see, I am new to the forum. I posted here because this seems to be a similar topic.I have ready many other instances of bricked phone. none of them seemed to match my exact scenerio. Please let me know if you have any ideas. I tried to address what i think my be wrong with the phone and some of the steps I have done to try and repair it already. I will gladly provide answers to more specific questions.
Just to clarify Tmobile Galaxy S3 (SGH-T999)

Flash counter not relevant in your case.
Factory reset through recovery should fix your issue.

Aerowinder said:
Flash counter not relevant in your case.
Factory reset through recovery should fix your issue.
Click to expand...
Click to collapse
I may have done this wrong. I think I have tried this though. home+volume up+power, this brings me to my cwm recovery. I did the full wipe and factory reset. after this it still didn't allow me past the gs3 screen. Should i somehow be using android recovery? if so, how do i get that to work again? Thanks

Weird. Try Odining a stock rom.

Aerowinder said:
Weird. Try Odining a stock rom.
Click to expand...
Click to collapse
Thanks Aero! I have tried this already as well. the file i used was T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 . I believe this is the stock 4.1.1. Also, I have just heard of md5 checked. I am not sure how to use that solely on my computer. I found a tutorial for doing it on the phone. As you know...not an option right now. I am keeping my hopes up that I don't need to send my phone off for Jtag. Like i said, i can still access cwm and download screen.
I have searched around the forum quite a bit. Do you know of any good instructions to walk me through flashing the stock rom that also includes links to the rom and gapp?

Hold on....you can get into recovery? Once in recovery you just do a factory reset? Do you have a micro SD card? Do you have a micro SD card adapter so that you can connect it to a computer?
Sent from my SGH-T999 using xda premium

Sounds like a boot loop, not a brick. Boot to recovery and wipe data then try to restart the phone.
Sent from my SGH-T999 using xda premium

707BeastMode707 said:
Hold on....you can get into recovery? Once in recovery you just do a factory reset? Do you have a micro SD card? Do you have a micro SD card adapter so that you can connect it to a computer?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I do have a card reader. Not exaclty sure where it is right now....what should I do once i have located it?
I have done the factory reset through recovery. Just to make sure i'm not misunderstanding this would be cwm? (sorry, i am still a noob!) haha

nickcross88 said:
I do have a card reader. Not exaclty sure where it is right now....what should I do once i have located it?
I have done the factory reset through recovery. Just to make sure i'm not misunderstanding this would be cwm? (sorry, i am still a noob!) haha
Click to expand...
Click to collapse
Don't worry about being a noob. Everyone on this forum is or has been a noob. You'll learn though.
Just follow these steps:
1.) Download this ROM on your computer (the latest from T-Mobile, stock rooted):
http://forum.xda-developers.com/showthread.php?t=2126679
2.) On your SD card create a designated folder for ROMs (just to make it easier to find the ROM when it comes time to flash it), then find the ROM you have just downloaded and put it in the folder you have created on the SD card
3.) Power on the phone, Boot into recovery which is also known as CWM by (volume up, home button and power button)
4.) Once in recovery do the following:
-wipe cache
-wipe dalvik cache
-wipe date/factory reset
-install zip from external SD card
-navigate to the folder where you placed the ROM in step 2 and select it and and select yes to flash it.
-when finished flashing go back to the main menu and select reboot device
(Device may take a few minutes to fully boot so let the phone sit and do its thing)
5.) When phone is booted up, go through the setup process with your email and what not.
6.) AFTER GOING THROUGH THE SETUP PROCESS, REBOOT DEVICE BACK INTO RECOVERY (CWM) AND SELECT RESTORE/BACKUP, THEN SELECT BACKUP, WHEN FINISHED REBOOT THE DEVICE
7.) AFTER YOU HAVE REBOOTED YOUR DEVICE GO TO THE PLAY STORE AND DOWNLOAD THIS APP:
https://play.google.com/store/apps/...tore/apps/details?id=com.j.y.daddy.customizer
8.) ONCE DOWNLOADED, OPEN THE APP (should ask for root permissions, hit accept) SELECT TOOLS, SELECT IMEI(S) BACKUP/RESTORE AND SELECT BACKUP.
You are now good to go, you may now flash and experiment with other ROMs. Stay away from the international s3 forum, just flash things that are meant for your S3 model, if you are not sure just ask the dev.
Sorry for the caps lock but steps 6, 7 and 8 will prevent you from major headaches. Especially 7 and 8. If you flash a ROM and your stuck on 2g/edge and your imei is zero, just download that app and open it and restore your imei. Step 6 is helpful just in case if you download a ROM and you run into your current problem you can just restore your backup and your phone will be fine.
Sent from my SGH-T999 using xda premium

If you have Odined a stock rom, how is it that you still have CWM? Did it fail? If you were able to successfully Odin a stock rom, then doing a factory reset should fix your problem.
UVALH2 is 4.0.4. http://www.sammobile.com/firmwares/1/?model=SGH-T999&pcode=TMB#firmware
Try using mrRobinson's root66 of UVDLJC. root66 is identical to the official firmware .tar file in every way except that root has been injected into the system image.

707BeastMode707 said:
Don't worry about being a noob. Everyone on this forum is or has been a noob. You'll learn though.
Just follow these steps:
1.) Download this ROM on your computer (the latest from T-Mobile, stock rooted):
http://forum.xda-developers.com/showthread.php?t=2126679
2.) On your SD card create a designated folder for ROMs (just to make it easier to find the ROM when it comes time to flash it), then find the ROM you have just downloaded and put it in the folder you have created on the SD card
3.) Power on the phone, Boot into recovery which is also known as CWM by (volume up, home button and power button)
4.) Once in recovery do the following:
-wipe cache
-wipe dalvik cache
-wipe date/factory reset
-install zip from external SD card
-navigate to the folder where you placed the ROM in step 2 and select it and and select yes to flash it.
-when finished flashing go back to the main menu and select reboot device
(Device may take a few minutes to fully boot so let the phone sit and do its thing)
5.) When phone is booted up, go through the setup process with your email and what not.
6.) AFTER GOING THROUGH THE SETUP PROCESS, REBOOT DEVICE BACK INTO RECOVERY (CWM) AND SELECT RESTORE/BACKUP, THEN SELECT BACKUP, WHEN FINISHED REBOOT THE DEVICE
7.) AFTER YOU HAVE REBOOTED YOUR DEVICE GO TO THE PLAY STORE AND DOWNLOAD THIS APP:
https://play.google.com/store/apps/...tore/apps/details?id=com.j.y.daddy.customizer
8.) ONCE DOWNLOADED, OPEN THE APP (should ask for root permissions, hit accept) SELECT TOOLS, SELECT IMEI(S) BACKUP/RESTORE AND SELECT BACKUP.
You are now good to go, you may now flash and experiment with other ROMs. Stay away from the international s3 forum, just flash things that are meant for your S3 model, if you are not sure just ask the dev.
Sorry for the caps lock but steps 6, 7 and 8 will prevent you from major headaches. Especially 7 and 8. If you flash a ROM and your stuck on 2g/edge and your imei is zero, just download that app and open it and restore your imei. Step 6 is helpful just in case if you download a ROM and you run into your current problem you can just restore your backup and your phone will be fine.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Finally got home. Ready to try this. My freaking phone is dead. I have plugged it in...It doesn't seem to be recharging while my phone is turned off? Do you have any ideas for what i should do here?

re: charging issue
nickcross88 said:
Finally got home. Ready to try this. My freaking phone is dead. I have plugged it in...It doesn't seem to be recharging while my phone is turned off? Do you have any ideas for what i should do here?
Click to expand...
Click to collapse
First thing I would do is to remove the battery and put it into the freezer for a couple hours,
then put the battery back in the phone to charge. (wipe the moisture off the battery first).
I know this sounds like a weird thing to do, but it's an old school trick which works most the time.
Once the phone starts to charge leave it alone until it has a full charge, don't play with it til then.

nickcross88 said:
Finally got home. Ready to try this. My freaking phone is dead. I have plugged it in...It doesn't seem to be recharging while my phone is turned off? Do you have any ideas for what i should do here?
Click to expand...
Click to collapse
Wait before you follow my post.....when you boot into recovery, what color is the background and what is the color of the text?
|When Emotion Goes up, Logic Goes Down|

707BeastMode707 said:
Wait before you follow my post.....when you boot into recovery, what color is the background and what is the color of the text?
|When Emotion Goes up, Logic Goes Down|
Click to expand...
Click to collapse
recovery mode is 5.5.0.4 CWM Black background with blue text. also has the top hat logo in the middle of the screen.

nickcross88 said:
recovery mode is 5.5.0.4 CWM Black background with blue text. also has the top hat logo in the middle of the screen.
Click to expand...
Click to collapse
Ok, i have loaded the provided .zip file to my sd card. however, it isn't showing up on my sd card when in recovery. It shows other files, but it won't show the new zip file or the new rom.
I see there is a setting under mount that says "mount external SD card" could this be the reason?

No. External SD mounting is broken on 5.5.0.4. Update it.

Aerowinder said:
No. External SD mounting is broken on 5.5.0.4. Update it.
Click to expand...
Click to collapse
I have fixed it. I was able to odin a stock .tar file on it 20 minutes ago. The only thing i am wondering about its that system info says i'm running 4.0.4. I am running the system update for it.
Thanks to everyone that helped me with my mistake. You guys are awesome!

Thank you sooo much!
707BeastMode707 said:
Don't worry about being a noob. Everyone on this forum is or has been a noob. You'll learn though.
Just follow these steps:
1.) Download this ROM on your computer (the latest from T-Mobile, stock rooted):
http://forum.xda-developers.com/showthread.php?t=2126679
2.) On your SD card create a designated folder for ROMs (just to make it easier to find the ROM when it comes time to flash it), then find the ROM you have just downloaded and put it in the folder you have created on the SD card
3.) Power on the phone, Boot into recovery which is also known as CWM by (volume up, home button and power button)
4.) Once in recovery do the following:
-wipe cache
-wipe dalvik cache
-wipe date/factory reset
-install zip from external SD card
-navigate to the folder where you placed the ROM in step 2 and select it and and select yes to flash it.
-when finished flashing go back to the main menu and select reboot device
(Device may take a few minutes to fully boot so let the phone sit and do its thing)
5.) When phone is booted up, go through the setup process with your email and what not.
6.) AFTER GOING THROUGH THE SETUP PROCESS, REBOOT DEVICE BACK INTO RECOVERY (CWM) AND SELECT RESTORE/BACKUP, THEN SELECT BACKUP, WHEN FINISHED REBOOT THE DEVICE
7.) AFTER YOU HAVE REBOOTED YOUR DEVICE GO TO THE PLAY STORE AND DOWNLOAD THIS APP:
https://play.google.com/store/apps/...tore/apps/details?id=com.j.y.daddy.customizer
8.) ONCE DOWNLOADED, OPEN THE APP (should ask for root permissions, hit accept) SELECT TOOLS, SELECT IMEI(S) BACKUP/RESTORE AND SELECT BACKUP.
You are now good to go, you may now flash and experiment with other ROMs. Stay away from the international s3 forum, just flash things that are meant for your S3 model, if you are not sure just ask the dev.
Sorry for the caps lock but steps 6, 7 and 8 will prevent you from major headaches. Especially 7 and 8. If you flash a ROM and your stuck on 2g/edge and your imei is zero, just download that app and open it and restore your imei. Step 6 is helpful just in case if you download a ROM and you run into your current problem you can just restore your backup and your phone will be fine.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thank you so much! this happened to me this morning, I've been looking for answers for 2 hours! I came upon yours and this helped me! I just wanna thank you so much, I thought I bricked my phone, and had to buy a new one. Thanks to you, I won't have too, just wanted to say this one more time, thank you! c:

Aerowinder said:
No. External SD mounting is broken on 5.5.0.4. Update it.
Click to expand...
Click to collapse
Could this be part of the reason i was unable to flash cm 10.1 onto the phone in the first place? Should i update to the touch version?

nickcross88 said:
Could this be part of the reason i was unable to flash cm 10.1 onto the phone in the first place? Should i update to the touch version?
Click to expand...
Click to collapse
What you have to do is go to the play store and download ROM manger, open ROM manager and install the updated version of cwm, then you shouldn't run into any more problem when flashing ROMs, just make sure the recovery is always up to date.
|When Emotion Goes up, Logic Goes Down|

Bootloop? Please help this soooper noober!

Sorry for my total noobness. I've just recently started this whole root awesomeness and I've hit a snag...... I'm sure there are many threads about my problem but I can't find one. I had CM 10.2 on my AT&T galaxy s3 and things were smooth and stable. Decided to try the "Collective" 4.3 ROM and SixShooter kernel. I put the zips in the phone (used the same gapps zip that was in there because I believe the Collective ROM is based off of the CM 10 ROM). Did a backup, then wiped chache, dalvick cache, system, and data (using TWRP recovery). Then did a multiple install of all three files in one action because TWRP lets you. so why not do it?
Rebooted, and I get the samsung logo, then sixshooter, then blank screen, vibration, pause, another vibration, then it starts all over. I can go into odin mode, or pull the battery to get it to stop.
Tried using odin to flash the .tar file, but it says PASS! and then the phone just automatically starts the loop again.
Was installing all 3 files (ROM, KERNEL, and Gapps zip files) at the same time a bad move?
I tried going back into recovery and it gives me the CWM recovery. Do I have TWRP AND CWM at the same time? Wierd. Tried wiping cache, and dalvik cache again and then rebooting, it still loops.
I'm at a a loss. I've watched a ton of videos and they all pretty much just say to find the right .tar and use odin to get back to stock. Like I said I've tried this and it just starts the loop again. Please help!! (I don't know a thing about ADB/terminal commands so if thats the fix I'll need my hand held) If theres a link to a thread that tells me how to get out of this I'd sure appreciate it. I greatly appreciate anyone who can take the time to explain to me what to do......

I would suggest booting into recovery and do the full wipe. Then just flash the ROM and gapps. If you're still bootlooping it could be a bad download of the ROM so if youve still got cm10.2 sitting around flash it instead. If that works I would look at downloading collective again. If not well maybe someone else has some input.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Ok, I just read the op again, and isn't the sixx shooter kernel packaged with the ROM? Also it states to factory data reset, wipe dalvik, install ROM, and the phone should reboot by itself do to a script, let phone settle, THEN boot back into recovery, flash gapps, wipe cache, reboot, enjoy! Maybe u shouldn't have flashed everything at once?

Yep, I'm a total tool. I installed everything in one action. ROM, gapps, kernel. Guessing I didn't need the kernel. And I should have read more closely the collective thread as it says to do the ROM. let it reboot, settle, etc. So the install all of them in one step is where I forked it up. I got it though. Pulled my head out and got the newest TWRP .img file and updated my recovery with odin. ROM is loaded and sweet as all get out!!
Crisis averted. Don't know what I would have done at work tomorrow without my podcasts and pandora! Thx for the help though. Love this forum.

Hmm. Okay, guess I don't have it completely sorted. I have gotten it to boot into the OS, let it sit a few. turned it off and tried to boot into recovery with vol+/home/power but it just starts it back up to the OS? Does the collective ROM change the way you get into recovery?

LilHoov said:
Hmm. Okay, guess I don't have it completely sorted. I have gotten it to boot into the OS, let it sit a few. turned it off and tried to boot into recovery with vol+/home/power but it just starts it back up to the OS? Does the collective ROM change the way you get into recovery?
Click to expand...
Click to collapse
Should have the four way reboot in the power menu. Long press the power button, while the phone is on, select reboot recovery. See if that helps...

Nevermind, I got it. lol
Gotta let go of that power button after vibration......man it's late