Develop Bugs

Install CWM on new AT&T S3

Why does this never work the way its supposed to for me??
Anyway, so I just got my S3 and I hate the stock ROM already so I want to go to CM (9 maybe, 10 if it works well). I'm right now just trying to get Clockwork recovery installed and working and seem to be failing miserably. At first it seemed to be going ok, I downloaded Odin 3.04 and a recovery TAR that was on the Android Authority guide for the AT&T S3. I ran the install no problems, and booted into recovery without issue. I then tried installing CM10 and it gave and Status 7 assert failure.
After a lot of digging I finally found some people saying that it was because of an incorrect version of CWM, so I dug around till I found a 6.0.1.0 tar that says its for my phone. I install that and now I can't get into recovery at all. It will still boot into the stock rom but that's it. I saw some suggestions saying that unchecking auto reboot, and f. reset time would fix this so I did that and still nothing. I can't get into recovery at all. Is there a definitive (as in this still works) guide out there somewhere??

forwardbias said:
Why does this never work the way its supposed to for me??
Anyway, so I just got my S3 and I hate the stock ROM already so I want to go to CM (9 maybe, 10 if it works well). I'm right now just trying to get Clockwork recovery installed and working and seem to be failing miserably. At first it seemed to be going ok, I downloaded Odin 3.04 and a recovery TAR that was on the Android Authority guide for the AT&T S3. I ran the install no problems, and booted into recovery without issue. I then tried installing CM10 and it gave and Status 7 assert failure.
After a lot of digging I finally found some people saying that it was because of an incorrect version of CWM, so I dug around till I found a 6.0.1.0 tar that says its for my phone. I install that and now I can't get into recovery at all. It will still boot into the stock rom but that's it. I saw some suggestions saying that unchecking auto reboot, and f. reset time would fix this so I did that and still nothing. I can't get into recovery at all. Is there a definitive (as in this still works) guide out there somewhere??
Click to expand...
Click to collapse
Ok so I found some CWM tars that they they're v.6+ that I can get installed (at least I assume so since Odin says it worked) but when I get in there the version listed at the top is 5.5.0.4, should this number not match? I haven't even gotten around to trying to get it to install CM10 yet.

I used rom manager to flash its recovery. No problems what so ever.
Sent from my SGH-I747 using xda premium

defnow said:
I used rom manager to flash its recovery. No problems what so ever.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
By Rom Manager you are talking about the App you use from within the OS? So would I need root for this?

https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager
Installed ROM manager....opened it and click install recovery. Done. Yes, you have to be rooted to use that app.
Sent from my SGH-I747 using xda premium

defnow said:
Installed ROM manager....opened it and click install recovery. Done. Yes, you have to be rooted to use that app.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Awesome suggestion! Worked perfectly thank you!!

Stuck in a boot loop

Rooted Att Note 2. I changed my fonts using Rom Tools and now my phone just sits at the Samsung splash screen. I did factory reset in recovery, still no dice. The recovery install only let's my flash updates and no I don't have a Nandroid. Kinda ran outta of ideas.

when you say the recovery install only lets you flash updates do you mean your still using stock revocery or have you flashed custom recovery and just dont have a ROM?
If you have custom recovery Id try to flash this :http://forum.xda-developers.com/showthread.php?t=1984546 Its been tested and works on our system. Its not stock but should at least get ya up and running again until a true stock is posted and you can flash that.

search in forums for an Odin tar file to reload the stock ROM. GL & do a nandroid before doing anything next time.

RMXO said:
search in forums for an Odin tar file to reload the stock ROM. GL & do a nandroid before doing anything next time.
Click to expand...
Click to collapse
I always do, didnt think much of fonts

cjsspape said:
when you say the recovery install only lets you flash updates do you mean your still using stock revocery or have you flashed custom recovery and just dont have a ROM?
If you have custom recovery Id try to flash this :http://forum.xda-developers.com/showthread.php?t=1984546 Its been tested and works on our system. Its not stock but should at least get ya up and running again until a true stock is posted and you can flash that.
Click to expand...
Click to collapse
not custom, thats the problem. I flashed twrp thru odin but it didnt take, even though it went thru

Try to flash cwm then and see if that takes. You'll need the Odin version of this file at the bottom of the OP http://forum.xda-developers.com/showthread.php?p=33955697
Sent from my SAMSUNG-SGH-I317 using xda premium

Sloved
the cmw tar worked. flash the rom in the general section

Good stuff. Glad it worked out for ya!
Sent from my SAMSUNG-SGH-I317 using xda premium

esincho said:
Rooted Att Note 2. I changed my fonts using Rom Tools and now my phone just sits at the Samsung splash screen. I did factory reset in recovery, still no dice. The recovery install only let's my flash updates and no I don't have a Nandroid. Kinda ran outta of ideas.
Click to expand...
Click to collapse
I had the same problem with Sprint note 2 and i just went to download screen and then flashed the cwm tar file and then all was good. Whew!!! Thought I bricked it! I made the mistake of using a quick boot app to reboot in to recovery. DON'T DO IT!

chidochuck said:
I had the same problem with Sprint note 2 and i just went to download screen and then flashed the cwm tar file and then all was good. Whew!!! Thought I bricked it! I made the mistake of using a quick boot app to reboot in to recovery. DON'T DO IT!
Click to expand...
Click to collapse
Just bought a ATT GN2... coming from SkyRocket... on the SR, I used to always use "Quick Boot" app to reboot, or reboot into CWM Recovery. When you reference "quick boot app", are you referring to this? When my GN2 arrives, want to be sure I avoid using "Quick Boot" app if it doesn't play well on the GN2 and JB. Thx.

DoctorQMM said:
Just bought a ATT GN2... coming from SkyRocket... on the SR, I used to always use "Quick Boot" app to reboot, or reboot into CWM Recovery. When you reference "quick boot app", are you referring to this? When my GN2 arrives, want to be sure I avoid using "Quick Boot" app if it doesn't play well on the GN2 and JB. Thx.
Click to expand...
Click to collapse
Most of the custom ROMs here use the built in 4 way Rebooter so ya really shouldn't need a quick boot program
Sent from my SGH-I317 using xda premium

I've had rom tools boot loop the phone after a font change. Moral of the story-nandroid.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

That's the one I used. Wish I knew why it happened.
Sent from my SPH-L900 using xda app-developers app

At a loss with cwm

Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay

maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.

pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..

Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951

pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks

Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways

Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app

RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?

Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump

what version of CWM are you currently running?

you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.

xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7

Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app

CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).

zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app

Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.

Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app

CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app

CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files

RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!

[Q] How to get CWM to work on Tab3 7 T210R

I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k

Wolfgar2k said:
I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k
Click to expand...
Click to collapse
did you check auto reboot in odin? if you do, just try to flash cwm again w/o checking auto reboot. it happens to my tab coz i've check auto reboot.

Just tried that. Same results. Everything looks good when flashing, but when I boot into recovery it's the stock recovery.
Sent from my Galaxy Nexus using xda app-developers app

Wolfgar2k said:
I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k
Click to expand...
Click to collapse
1.Dont check the autoreboot. Ketut.kumajaya said something about the system is restoring recovery when rebooting
2. Try to redownload the cwm recovery.
3. If that didnt work, What odin are u using? Try 3.07 ..
4. You can also try twrp. I am using twrp and it is working great
Sent from my SM-T210R using xda app-developers app

I've been using Odin 3.07 the whole time. I tried twrp as you suggested and that worked. Not sure why cwm didn't work, but at least now I'm rooted. Thanks.
Sent from my Galaxy Nexus using xda app-developers app

I will recreate an autoroot package for you in my spare time. Samsung Android boot image has a known feature to patch the boot image and use it to overwrite the recovery image on every boot. This feature disabled in blackhawk kernel, some recovery has a capability to disable this feature as well.

ketut.kumajaya said:
I will recreate an autoroot package for you in my spare time. Samsung Android boot image has a known feature to patch the boot image and use it to overwrite the recovery image on every boot. This feature disabled in blackhawk kernel, some recovery has a capability to disable this feature as well.
Click to expand...
Click to collapse
Can I flash your kernel on the stock rom while having cwm recovery or do I need Infamous 1.1?
I would like to stay at german on my tablet but also want to use USB OTG

Wolfgar2k said:
I've been using Odin 3.07 the whole time. I tried twrp as you suggested and that worked. Not sure why cwm didn't work, but at least now I'm rooted. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Got to hear that u have twrp. Im happy 4 u
Sent from my SM-T210R using xda app-developers app

Jediritter said:
Can I flash your kernel on the stock rom while having cwm recovery or do I need Infamous 1.1?
I would like to stay at german on my tablet but also want to use USB OTG
Click to expand...
Click to collapse
Yes, you can flash it on stock rom (with CWM), but OTG isn't functioning yet.

Root issues (moved from Virgin rom as requested) Help

I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....

Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app

th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?

I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4

I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app

I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app

th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app

If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.

norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again

th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.

mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew

SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!

th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app

See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!