I've currently attempted to root my Galaxy and everything went well until I tried to back up my applications.
I can't get clockworkmod to work, I hold vol up, power, and home and it shows my the android character laying back with a red ! in Android System Recovery.
Not really sure what to do. I've been searching for possible solutions but I can't find anything.
I followed this method, http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
The FAQ section under it talks about two files that should be deleted as it overrides CWM but file explorer isn't finding them for me.
Just use the Root66 rooting method : http://forum.xda-developers.com/showthread.php?t=1949687 .
It sounds like whatever you did, it did not work and you still have stock recovery. Just do it through Odin as described in the thread linked - it is very easy.
Any possible chance of me bricking my phone by adding additional files along with the ones I've added? CWM seems to be working through the ROM Manager app but not working through Vol Up, Home, and Power.
You press power. Wait a second or two, then hold vol up and home.
If you hold power, the phone will never turn on. If you wait too long, the phone will boot into the OS. It's a timing thing.
I've done that and that's how I get sent to Android System Recovery.
I've downloaded CWM through ROM Manager but I can only access CWM right after I download I. It worked last night but today when I tried accessing CWM it sent me to Android System Recovery. I downloaded CWM again then it worked.
For some reason it seems CWM isn't sticking onto my device.
Oh, I misunderstood. To fix that, flash CWM (version 6.0.3.0) again. And when you reboot your device, before your device boots into the OS, drop into recovery mode. It will allow you to disable the script that keeps overwriting CWM for you (you will get this option when you attempt to exit CWM).
Oh wow, I did what you said my phone rebooted. I did vol up, power, and home and got sent into CWM. I think its working now
Thank you so much bro
Sent from my SGH-T999 using xda app-developers app
Now save yourself time and hassle and flash twrp recovery cwm is.in my opinion troubled... twrp seems to be the rec of choice
With goomanager from market.
Sent from my LG-MS770 using xda app-developers app
They are crawling out of the woodwork.
There is nothing wrong with CWM. There is nothing wrong (mostly) with TWRP. They both work. Pretty well, in fact. Though, I still have issues with TWRP pretending I pressed the back button when I didn't.
Since you are on TWRP, tell me if you can reproduce this: Go into the timezone settings and start selecting different timezones as fast as you can (also works with typing filenames for nandroids, but this is quicker for reproduction). What happens on my device is I get knocked back into the settings page. It is 100% reproducible, but inconsistent with presses/time required to make it crash. I have seen other people complain about this, but not nearly as many as I would expect, given the severity and prevalence of the bug.
Related
Using Rom Manager (after updating it today), I flashed CWM Recovery to 5.0.0.1 as it suggested I should.
I rebooted to check it out, and now my Phone is stuck in FASTBOOT.
No matter what option I choose, it simply reboots to FASTBOOT again.
Yes, I tried the VOL-Up + PWR, and VOL-Down + PWR. VOL-Up + PWR gives me 3 vibrations and no other reaction. VOL-Down + PWR does nothing.
Any suggestions?
Did the same thing to me. I had to pull battery and restart and it worked fine after.
Yea, unfortunately I forgot to mention that I tried that about 10 times
Guess I get to learn how to ADB flash the recovery all over again (been about 6 months).
Side note: I did notice when selecting "Recovery" from the HBOOT screen, it seems to be scanning my sd card for a file and says it cannot find it. (It goes REALLY FAST then disappears, so I'm not sure what file it's looking for)
Do you use twitter? Send koush a message. He always responds.
I had this problem, too. In my case, it turned out that I needed to update my version of ROM Manager to 4.4.0.5. Once I did that, I just re-flashed 5.0.0.1. Works just like it should now.
I had the same thing happen to me before, turned out Clockwork did not install properly so I downloaded the HBOOT flashable recovery from here http://dougpiston.com/?page_id=85 and that did the trick.
It turned out that my troubles all stemmed from a failing sd card.
I've yet to see one, but is there an app available that performs a integrity check on mounted sd cards?
Sent from my ADR6300 using XDA App
Not that I know of. But that missing file u were talking about I believe is normal. Everytime I flash or nandroid, that error missing file thing pops up and then gets ignored. It doesn't cause an issue for me as I have flashed probably 2 dozen ROMs with several being daily drivers over the last 17 months and nandroided just as much. Never an issue.
Sent from sweet snacks off tapatalk.
Hi Guys -
First time android user and attempted rooting using the odin method. I followed the instruction listed here http://forum.xda-developers.com/showthread.php?t=1311194 to the "T" before starting. I was doing alright until after flashing the recovery-cwm-hercules.tar, then it gets weird. It didn't flash to recovery but just rebooted to the main screen (where I could see the background picture with the locker pattern), then it immediately shuts off and the cycle begins again.
The weird thing is that I can't even access recovery mode (hold vol. up+down+power), because I'll see the Clockworkmod logo then it flickers and reboot itself. This happens every time I attempted recovery mode.
My attempts to fix it:
1. I flashed the recovery, http://forum.xda-developers.com/showthread.php?t=1315390, to see if it makes any difference. The same story happens with loading to main screen w/locker then it reboots itself again and again. Sometimes I'll be lucky to input the pattern but before soon it will reboot itself again. Same thing with recovery mode as described above.
2. Flashing the stock kernel provided by http://forum.xda-developers.com/showthread.php?t=1311229 to see if it does anything. Nope, same story for both recovery mode/home screen.
3. The insecure kernel, http://forum.xda-developers.com/showthread.php?t=1320946. Same story. nope, nope.
4. Tried these in all order and permutation. Nada.
5. Tried it both ways using samsung driver/kies.
6. Tried it both ways with/without SIM card.
7. Battery is fully charged when attempting any flashing.
8. All the above in my second computer to no avail.
I'm sorry if this might come across as long winded but I just want you guys to get the full picture. I would really appreciate it if you guys could offer any solutions or advice on how to correct this problem. Please be gentle with this first time android user haha, thanks in advance man.
Manually boot into recovery (vol up/down keys) and make a backup (be sure to do this). Then try wipe data/factory reset through recovery. Sounds like a ROM issue not a hardware issue
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
redlaws said:
First off, thanks roman for the quick reply. That's the thing I can't get to recovery manually with the button combinations. When I do that it gives me this message:
[Picture]White dropbox/mail box with a yellow arrow pointing to the Android
"Verifying internal mmc block
Checksum confirmation check (0)
No need checksum confirmation already exceuted
#manual mode#"
It would then reboot and goes to the screen with the locker then immediately repeats that cycle. It doesn't have any wipe options/restart now/etc.
No way to power it down except with battery removal. I've attempted what you suggested many times too to no avail.
Click to expand...
Click to collapse
Ok, so if it actually boots into the ROM but reboots, try rebooting to recovery from adb -- "adb reboot recovery"
think it's a no go . i tried using adb recovery method and the same thing would occur, it would restart and seems to load into recovery mode but then I would only see the logo, then it flickers and restart itself.
then the vicious cycle of loading up to the screen-locker and restarting itself begins. guess this is the smartphone version of being friend-zoned.
Have you tried taking battery out then back in and while holding volume up/down plug it back into computer? That has never failed to get me into d/l mode. Man I hope you get it working.
Yeah I tried that and getting to download mode is not the problem. just that recovery mode doesn't boot properly in that it would restarts itself. and when i boot normally to screen, i would see the locker and background picture then within 3 secs, it would restart itself.
Guess last resort is to go to t-mobile store, play dumb, and get samsung on it. only problem is that i worry about the flash rom counter # since mine is like 10 already (my attempts to address this problem). Let's hope those tmobile reps aren't that tech savvy.
Thanks for all the help fellas, great early posting experiences so far.
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
kt0ce said:
I'm sorry I've read your post..and i'm confuse, if you're able to go into download mode, then why could you just start Odin and flash the recovery again. If its unsuccessful then check the MD5 to see if you have a bad download. I think you should download the recoveries files again add give Odin another shot..Good luck..
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
I'm going to give it another try. I've been trying it with different files for a good 2 days now though.
AllGamer said:
are you able to go into CW recovery ?
if so, you can mount the USB, download a stock ROM, and then flash it using CWR
Click to expand...
Click to collapse
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
redlaws said:
I understand that but that's the a big problem. If I could go to CW it would be a different story but I can't go into CW recovery. I would be able to see the logo CWR and the version number then immediately it shuts off again and reboot. Happens every time without fail.
Click to expand...
Click to collapse
did you let go of holding the vol+ & vol- buttons as soon as you see the blue text in CWR ?
it can easily reboot by accident when holding those buttons and hitting power, but the buttons are so responsive it selected the first option to reboot the phone by accident a couple of times on me
I'm positive that I held it properly and long enough. I never got to the blue text, just the CWR logo showing then turns off (like you shutting off a tv) and reboots itself. Trying to flash it again with Odin didn't work either and I tried the recoveries from different sources as well.
I went to the Tmobile store today and seems like they'll mail me a replacement then I'll return my current one to them. Only thing is stocking/processing fee but it's a small price to pay if it resolves everything.
glad they will give you another one..
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
reocej said:
Dude if you can get into download mode then it can most likely be fixed by flashing stock through odin. This would save you some $$. Just saying.
Click to expand...
Click to collapse
Dude, I understand that it should but it's not. I've flashed the stock recovery for more than 10 times and I still can't past the home screen. It would just reboot itself in less than 3 sec. And I'm positive I flashed it properly. Believe me I don't want to spend extra money if I don't have too.
Guys, I unlocked and rooted my Galaxy Nexus but kept everything stock. Downloaded ROM manager and the first thing I did was make a recovery for myself. A few days later, when the 4.04 zip was leaked onto the forums, I downloaded the file and flashed it. I havent messed with anything since.
Come today, I tried to do another back up in ROM manger but my phone does nothing after I execute the commands. Then I tried to reboot into recovery, but nothing happens.
I was able to get into recovery manually (holding down the volume up AND down keys with power button) and when I selected "Recovery" all I got was the android with an open chest plate with a Red Triangle and Black exclaimation point. Screen stayed like that and eventually booted up normally.
I tried to follow the steps listed in this thread to delete /system/recovery........p file and then reinstall cwm http://forum.xda-developers.com/showthread.php?t=1399265
but the problem I'm having is that I am when I try to delete that file with Root Explorer with the mount set to R/W, I get a msg that says it cant be deleted because its read only.
Did I lose root access by flashing 4.04? Is there a way to fix that? I'm still relatively new to all of this so if anyone can tell me whats up in a dumbed down way I'm all ears.
Thanks,
Appa
Emm, there's no need to delete old recovery. Just download recovery image you like, place it o your PC, reboot phone into bootloader and flash recovery.
Sent from my Galaxy Nexus using xda premium
But I think that's the problem: when I try to get into recovery, I get the dead android guy with the red exclamation point And phone just reboots
Appa567 said:
But I think that's the problem: when I try to get into recovery, I get the dead android guy with the red exclamation point And phone just reboots
Click to expand...
Click to collapse
Press both volume up and down + power button when you see that. It will bring up the menu.
Flash Clockwork, boot into recovery, and Flash a custom rooted rom.
Droid-Life wrote a quick tutorial just in case
http://www.droid-life.com/2011/12/1...xus-4g-lte-and-flash-custom-recovery-verizon/
Appa567 said:
Guys, I unlocked and rooted my Galaxy Nexus but kept everything stock. Downloaded ROM manager and the first thing I did was make a recovery for myself. A few days later, when the 4.04 zip was leaked onto the forums, I downloaded the file and flashed it. I havent messed with anything since.
Come today, I tried to do another back up in ROM manger but my phone does nothing after I execute the commands. Then I tried to reboot into recovery, but nothing happens.
I was able to get into recovery manually (holding down the volume up AND down keys with power button) and when I selected "Recovery" all I got was the android with an open chest plate with a Red Triangle and Black exclaimation point. Screen stayed like that and eventually booted up normally.
I tried to follow the steps listed in this thread to delete /system/recovery........p file and then reinstall cwm http://forum.xda-developers.com/showthread.php?t=1399265
but the problem I'm having is that I am when I try to delete that file with Root Explorer with the mount set to R/W, I get a msg that says it cant be deleted because its read only.
Did I lose root access by flashing 4.04? Is there a way to fix that? I'm still relatively new to all of this so if anyone can tell me whats up in a dumbed down way I'm all ears.
Thanks,
Appa
Click to expand...
Click to collapse
All updates revoke your root access, and replace any custom recovery with the stock recovery (which is the little android with the !). You will need to re-root after every update, and you will need to delete the following files (/system/recovery-from-boot.p and /system/etc/install-recovery.sh) after every update, and you will need to re-flash your custom recovery after deleting those files.
P.S. To access the menu in the stock recovery, when you are at the screen with the android, hold the volume up key and press the power button.
My Xperia Play has had a few problems out of the box, mainly that when I switch it on there is no boot animation, just a black screen. This means I can't access Recovery through the normal method of holding down on the volume or the back button etc. I've installed CWM through the CWM Xperia installer so I know it's there. I also ran the Auto-Magic Nandroid through that app, which caused my screen to go black (as it does whenever I choose to reboot through an app). When I looked on my SD card though there is now a Nandroid folder, so it's probable that the device does go into Recovery; I just can't see it.
So my question is this; is there any other way of getting my phone into Recovery so I can install some sweet, delicious custom ROMs? Maybe through ADB or similar? Or is it possible to install a ROM via another method?
Any help at all would be appreciated!!
If it wasn't working right right out of the box, I would have sent it back.
Can't you boot into recovery from the CWM-installer app?
Solar.Plexus said:
If it wasn't working right right out of the box, I would have sent it back.
Can't you boot into recovery from the CWM-installer app?
Click to expand...
Click to collapse
Sadly that wasn't an option, it was the only one they had and I wasn't about to send it back for another type of phone, I've wanted this thing for ages
I've just clicked that option in the app and it's just rebooted the phone normally.
Trism said:
Sadly that wasn't an option, it was the only one they had and I wasn't about to send it back for another type of phone, I've wanted this thing for ages
I've just clicked that option in the app and it's just rebooted the phone normally.
Click to expand...
Click to collapse
Turn on the phone, and when you see the notification light turn blue, press volume down for the locked bootloader cwm, or the back button for the one in DooMKernel.
Sent from a Galaxy far, far away
I've not yet tried installing DooMKernel, I'm worried that if I can't get into the normal recovery in won't be able to get into that one, then I'll be stuck with a boot looping phone.
Pressing down on volume on the blue led comes on doesn't seem to do much, simply stops the boot process from completing fully. I left the phone for 5 mins and got nothing. Pressing the power button again started the boot process again and it loaded up normally (minus any animations of ciurse)
It seems like stuff is happening, but I just can't see it. I doubt this is a hardware fault as the screen works perfectly all other times, so what the heck could it be!?
The recovery in DooMKernel is already built in, so it's different than using the Xperia CWM installer. By the way, the back button will get you into DooMKernel's recovery.
I'll give it a try and see what happens. Thanks for the advice guys!
Alright, so I have an i-747 (AT&T GS3) running AOKP Jellybean (8.28 build) with the KT747 kernel. I just tried to install Chainfire 3D using the automated installer, and when the phone rebooted, it stuck at the Samsung Galaxy S3 logo until I pulled battery. So I tried rebooting into CWM - same problem. And again with download mode. Even after pulling the battery for a good 5 minutes, nothing works. Am I bricked, or is there some fix for this?
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
g2tegg said:
If you can get into CWM your not bricked. If you haven't backed up your phone there is a good chance you will have to start fresh. Its always a wise decision to do a nandroid backup via cwm before doing anything major. Including installing chainfire.
Have you tried wipe/factory reset in CWM?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I made a nandroid just this afternoon, but I can't actually boot into CWM at all. As in, I turn on the phone (power+home+volume up), it gets to the Galaxy S3 logo and just hangs there. If I could get into CWM (or download mode) this would be about a 10 minute fix, but I'm kind of out of luck here.
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
HELP I have the same issue
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
Hi, sorry to say but sounds like its bricked
Thanks
MrPhantom31 said:
Huh. After another battery pull, it let me boot into download mode. I'm gonna try to reflash to stock and hope for the best.
Click to expand...
Click to collapse
I doubt it's bricked if he got it into download mode. I'm sure he's flashed it and even got his wallpaper back up by now. Please let us know of you've managed to solve this or not MrPhantom.
Sent from my SGS3 i747m (Bell) on CM10 using TapaTalk2
delete post please
Curious?
I know its technically "Solved" but does anyone have any idea why this is happening? I have a Verizon GS3 and it's happening to me. I try to boot and it vibrates once and doesn't turn on. Recovery does the same thing. But going into Download mode works. Odin back to stock as we speak but I'm just curious what went wrong. I just did a clean install of a rom, set it all up (working at the time), set it down for the night and woke up to it like this.
rrrs444230 said:
Hey, Im stuck in the same situation and was wondering if you were able to get it into CWM mode?
Click to expand...
Click to collapse
Same thing happned to me but your not bricked. You can get into bolth download and boot mode easy
Here is how you do it.
RECOVERY MODE
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
[edit]Download Mode
Save that somewhere. Make sure do it right. I got stuck also and thought I couldn't get into recovery but I had to do it right (it hit recovery mode first try) I have learned that most people do it slightly wrong. Make sure follow directions
Download mode
Unplug the USB cable.
Shut down the phone.
Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
To get out of Download Mode, simply press and hold the power button until the phone restarts
if helps hit thanks.
Just save that to a text file somewhere
I have also soft bricked when I deleted my rom once on accident. I dunno how I did it but I would get stuck at the TWRP screen. It wouldn't go to download or anything however when I plugged it into odin it saw it .... I even had a soft brick when screen went black from a bad boot animation and same thing.. and I had one bad soft brick where it took about 100 trys to get it into download mode (black screen) but odin detected it. I spent like 4 hours working on it.
I think
1. People don't follow directions correct (they do it a little wrong) which is enough if your phones messed up for it not to work.
when your phones normal it can get into recovery or download easy but when its sick you got to do it perfect.
2. I think something wrong with the phones (my s2 never had any issues in 2 years of owning it) S3 has tons of issues from usb, to bluetooth, to these soft bricks I have had)
3. Roms play a big part
4. I also think the way storage works in this new phone causes lots issues I dunno why just what I think
anyway Like I said now when I have a isssue I open text and read it and make sure I do it right and 95 percent of the time it was my fault I wasn't doing it right. K just my thoughts
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
phatchef1 said:
when i try this on my verzion s3 it wont load back into the CWM after installed to finish rooting. it just goes back into the android system recovery. tried it about 10 times and nothing different
Click to expand...
Click to collapse
That's most likely cause you're not in the right section..: http://forum.xda-developers.com/forumdisplay.php?f=1708