Develop Bugs

Stuck on black "Google" with open lock screen

I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?

patriot95 said:
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
Click to expand...
Click to collapse
i think that flash a new rom would solve this

patriot95 said:
I tried using the franco kernel app to install the kernel on my rooted Galaxy Nexus. There was the "download the .zip" option and the "we'll flash it for you" option. Of course I took the easy option which was probably stupid on my part. My phone downloaded the kernel and then rebooted. Now that it has rebooted... it wont get beyond the black screen that says "Google" and has the little open lock image at the bottom.
Questions:
Has anyone seen this?
Did I brick this thing (I really hope not)?
What steps can I do to try to get it back working?
Or does it just take a long time 20+ minutes to download/install/whatever once it reboots?
Click to expand...
Click to collapse
I did this last night to see, and it didn't work. I had to pull the battery, and reboot. I then just downloaded the new zip, and rebooted into Recovery to flash it as I normally would.

I wanted to do this... but with my root toolkit it looks like my phone doesn't have usb debugging on (which it was before I tried to flash this kernel). And I can't turn my phone on to turn it on... so hmm.

RMarkwald said:
I did this last night to see, and it didn't work. I had to pull the battery, and reboot. I then just downloaded the new zip, and rebooted into Recovery to flash it as I normally would.
Click to expand...
Click to collapse
This is what I want to do. Is I pull the battery and restart... I'm still stuck at the same screen though.

patriot95 said:
This is what I want to do. Is I pull the battery and restart... I'm still stuck at the same screen though.
Click to expand...
Click to collapse
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery. Do you have the ROM zip file or another kernel on your SD card? You could just re-flash the ROM zip file over your existing installation, which would leave your data alone and install the ROM's kernel. Wipe /cache and Dalvik Cache before flashing.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.

RMarkwald said:
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery. Do you have the ROM zip file or another kernel on your SD card? You could just re-flash the ROM zip file over your existing installation, which would leave your data alone and install the ROM's kernel. Wipe /cache and Dalvik Cache before flashing.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
Click to expand...
Click to collapse
This is KIND of what I'm doing. I can't access my phone from the computer because of the damn usb thing... but I'm going to try to flash back to stock and see if that works.

It's booting now and it's been on the start screen for a minute or two. How long should it take on a stock flash? Just curious how long to wait before yanking the battery and trying again.

How did you flash stock, using fastboot or a zip? These are the stock images correct?

I boot into Recovery Mode and did the factory reset.
I also have a su.zip on my sdcard that I think is the rooted image that was used when I used the WugFresh root toolkit. But I'm not sure.
Shouldn't the Factory Reset... do a Factory Reset?
Edit: I see it's just data not an actual factory reset as I am thinking.

patriot95 said:
I boot into Recovery Mode and did the factory reset.
I also have a su.zip on my sdcard that I think is the rooted image that was used when I used the WugFresh root toolkit. But I'm not sure.
Shouldn't the Factory Reset... do a Factory Reset?
Edit: I see it's just data not an actual factory reset as I am thinking.
Click to expand...
Click to collapse
If you don't have a ROM or kernel zip file on your SD card, you'll want to put one there. Factory Reset already reset any data you have, so you'll want to flashing a ROM would be recommended here.
You can use ADB to push files to your SD card. You'll need to get into Recovery, mount /data (which is under Mounts and Storage menu), then open a command prompt window and change directories to your Android SDK folder, specifically Platform-tools. Then use ADB to push the zip files to your SD card:
adb push <name of file>.zip /data/media
EDIT 2: You'll want to download and put the zip file in your SDK - Platform-tools folder before you use ADB to push it there.
You can then flash the ROM via Install file from SD card.
Does this make sense?
EDIT: The su.zip is just to get root access, not a full ROM zip.

RMarkwald said:
If you don't have a ROM or kernel zip file on your SD card, you'll want to put one there. Factory Reset already reset any data you have, so you'll want to flashing a ROM would be recommended here.
You can use ADB to push files to your SD card. You'll need to get into Recovery, mount /data (which is under Mounts and Storage menu), then open a command prompt window and change directories to your Android SDK folder, specifically Platform-tools. Then use ADB to push the zip files to your SD card:
adb push <name of file>.zip /data/media
You can then flash the ROM via Install file from SD card.
Does this make sense?
EDIT: The su.zip is just to get root access, not a full ROM zip.
Click to expand...
Click to collapse
It makes sense... but I'm a little new so I will try this. Might take me a while.
By the way... these captcha images suck.

Thank you for the help... I am re-rooting my phone now. I was able to get back to stock.

Good job, glad to help!

RMarkwald said:
Pull the battery, hold Vol Up/Vol Down/Power to get into Recovery.
EDIT: When you get into the bootloader, hit Vol Up until Recovery shows up, then hit the Power button to boot to Recovery.
Click to expand...
Click to collapse
I LOVE YOU!
(I did the same thing with the auto-flash kernel and was stuck. I totally forgot that you had to hold BOTH up/down with the power button.)
Franco's app SUCKS!
Thanks my man!!! :good:
BTW...Jelly Bean rocks!

Hello guys i have tha same problem with patriot95 (black screen Google and one small lock lower) ... my device is optimus 3d p920 and i cant reboot it .
can you help me ? PLz

This is a problem with the toolkit...
Do you have any adb and fastboot downloaded? No? Download it. There's more than enough instructions on that.
You didn't need to factory reset AT ALL. All you needed to do was just re-flash your ROM and you would've been good to go.
Next time learn how to use adb and fastboot command please. Then, there will be less chance of messing it up and not being able to fixing it.

Hi, sorry this thread is kinda old already but I don't really want to start new thread about same problem. So, similar to OP, I stupidly use the 'autoflash' option from franco app, and I'm stuck now. But I can still have access to CWM recovery. I was using the stock 4.2.2 takju before. I already tried to re-flash stock kernel -> fail. Tried re-flash stock rom - fail. Tried wipe cache and dalvik then flash deodexed 4.2.2 -> also fail. Please help me, I really need to use my phone right now.

Are you flashing a 4.2.2 kernel with a 4.2.2 ROM?
What ROM and kernel?
Sent from my Galaxy Nexus using xda premium

I flashed the stock 4.2.2 rom from the google website but it doesn't work. Then I tried the stock 4.2.2 from this link,
http://forum.xda-developers.com/showthread.php?t=1737849 but also failed.
I also flashed the stock kernel from this link
http://forum.xda-developers.com/showthread.php?t=2151154

GS3 AT&T CWM flash wont stick (resolved)

Ok so i followed the instructions here. http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
I am all rooted and everything seems to be working until i tried to boot to CWM recovery to create a back up I realized I cannot boot into CMW. I was able do while following the instructions. It seems as thought my CWM flash is not sticking? I even tried to boot to recovery from ROM manger but it still takes me to stock recovery. I tried flashing from Rom Manger, it said it was successful and then I was able to boot to CWM, but after a reboot and trying to get back to it from rom manger again or by holding volume up, home and power I cannot get back to it. Why wont my flash stick.
Please help.

abandroid said:
Ok so i followed the instructions here. http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
I am all rooted and everything seems to be working until i tried to boot to CWM recovery to create a back up I realized I cannot boot into CMW. I was able do while following the instructions. It seems as thought my CWM flash is not sticking? I even tried to boot to recovery from ROM manger but it still takes me to stock recovery. I tried flashing from Rom Manger, it said it was successful and then I was able to boot to CWM, but after a reboot and trying to get back to it from rom manger again or by holding volume up, home and power I cannot get back to it. Why wont my flash stick.
Please help.
Click to expand...
Click to collapse
First, are you sure you are rooted?
Second, how are you trying to flash CWM?

You need to follow the method posted in the ATT Development forum and use the CWM that was developed for AT&T. I am using the d2att touch version.

id_twin said:
First, are you sure you are rooted?
Second, how are you trying to flash CWM?
Click to expand...
Click to collapse
Yes I am rooted. I am using Odin3 v3.04 to flash RecoveryGalaxyS3USCanada.tar. I remove the battery once it shows it passes. Hold down volume up, power and home button. It will let me boot to CWM recovery this one time but after that once I reboot I have to redo the steps to get back to CWM recovery. I just tried installing recovery-clockwork-touch-5.8.4.6-d2att.zip. It said it was successful but still no go.

Issues fixed! Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Clock work mod problem, please help

Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.

Have you tried twrp?

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly

this could happen when you didn't root it properly
anyways, if you are rooted(as you said), get twrp and see

+1 for twrp

athens71 said:
I still have root.
Click to expand...
Click to collapse
If you still have root, you might want to try installing CWM directly from your phone, using the dd terminal command to copy CWM into the right partition:
Download the latest CWM .img file from CWM's site: http://www.clockworkmod.com/rommanager
Put the file in your phone. For simplicity reason, I would suggest you put it in the root of your internal SD card. And because you will need to type the whole path+filename in the terminal in your phone, I would also suggest you rename the file to something simple, like cwm.img;
If you don't already have it, install Android Terminal Emulator;
Now, open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
(That is, if you rename the CWM file to "cwm.img" and you actually put it in the root of your internal SD card. If you put it somewhere else or did not rename your file, you will need to adapt the "if=" part of the command.)
Profit.

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.

drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm still using stock ROM, i'd like to install a custom ROM but i'm reading that you have to have Clockworkmod to do a successful install.
When i check in the files of the phone (sd card) i can see the clockwordmod folder in there there but still can't get it to boot into cwm recovery, only the Samsung recovery and I've tried the volume up home and power button so many times but no success.
Why do you think it worked when i first rooted the phone and not now?
this is frustrating, thanks for the help.

aybarrap1 said:
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
Click to expand...
Click to collapse
Yes I've tried 3 times via Odin, i can't remember where i got the cmw file from, it's a tar file (clockworkmod.TAR), the part i don't understand is why when i first rooted the phone in August cwm worked, i used it to install the root and now after trying to install it again 3 times i can't get it to work.
I'm using the stock ROM, not jelly bean.
thanks for any help

xBeerdroiDx said:
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
Click to expand...
Click to collapse
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.

androidsavage23 said:
Have you tried twrp?
Click to expand...
Click to collapse
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you

athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
Click to expand...
Click to collapse
Download goo manager app and open that. There will be an option to "install open recovery" in the menu. Voilà a superior recovery that's easier to use
You can even use it to boot into recovery or install the new update for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Click to expand...
Click to collapse
Easiest way to install TWRP is using GooManager from the Play Store.
1. Open GooManager.
2. Press the menu key to open the contextual menu, and select Install OpenRecoveryScript.
3. The app will ask you to confirm you really want to install a new recovery image.
4. GooManager searches for the correct TWRP build for your device. Look at the Filename line, it should display openrecovery-twrp-2.4.1.0-d2att.img for AT&T or openrecovery-twrp-2.4.1.0-d2can.img for Rogers/Bell/Telus. Again, confirm the installation.
5. Wait for the download to begin. TWRP will install. Done.
If it does not work or if GooManager does not find the correct build for your device -- in this latter case, this should raise a flag for you, as you may not have a SGH-i747/SGH-i747M; double check your phone model --, you can always install TWRP manually. From TWRP website (http://www.teamw.in/project/twrp2), you can grab the IMG file to manually install from the terminal emulator, and a TAR file to install using ODIN.

athens71 said:
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
Click to expand...
Click to collapse
Did you try it exactly as i said to?

drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So if that's the case (This will happen until you load a custom ROM) how can i back up my stuff before installing a new ROM? that's the reason i was trying to make cwm work so i could back my stuff.
Is there a different way to do a full back up?
thanks

xBeerdroiDx said:
Did you try it exactly as i said to?
Click to expand...
Click to collapse
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you

athens71 said:
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
Click to expand...
Click to collapse
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.

xBeerdroiDx said:
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
Click to expand...
Click to collapse
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks

athens71 said:
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
Click to expand...
Click to collapse
you've created a backup already? if not, install cwm from ROM Manager, boot into cwm recovery and make your nandroid there. then you'll be all set to to try a new ROM

[Q] After CWM upgrade cannot start or restore phone

I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks

northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app

northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message

Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"

I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium

I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse

stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?

In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.

Same here, stay away from that update! Bad things!

This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?

Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...

I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP

I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium

xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!

xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.

J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.

[Q] Installing custom recovery? New to Samsung phones...

Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks

ovimunt said:
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
Click to expand...
Click to collapse
May I ask what variant you are using? GT-i9195?
Then please boot your phone into download mode, this can be done by first switching of your phone completely then holding the power button, home button and volume down button until the download screen appears where you press continue. Once you have done that connect your phone using the usb cable and make sure all drivers have been installed! Once the drivers are installed start up Odin uncheck the f.rest time box and click the AP section and then select the recovery file provided by Sir Arco in the root thread.
If you need more help please ask, If it worked then still reply

Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.

Whosat said:
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Click to expand...
Click to collapse
Thanks for the response. Yeah, I kind of realized that's what's happening. I've managed to boot into the custom recovery right after the flash and did what I had to do in there, but then after I reboot the phone again, the custom recovery is gone. Is there a way to stop stock recovery being reflashed automatically?
Also, if I want to install a custom kernel, how can I backup the current one so that I can restore it at a later date if I need to? I know how to do this on HTC phones but it all seems to be a bit different on Samsung and I don't want to mess up anything.

How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.

Whosat said:
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Click to expand...
Click to collapse
Umm... yeah, I think it did ask but I just accidentally pressed no before reading what it said... So I guess I'll just have to flash the recovery again and then answer yes to that question.
Thanks

Yes that would be the correct way to do it.
Hope all goes well!