Develop Bugs

[Q] Recovery Mode Lost after flashing ROM

Maybe this is by design and I'm just missing something. I got a new e4gt and proceeded to root it using instructions found on epic4gtouchroot.com. Basically I used odin to flash a stock EL29 ROM and then install team Rogue's CWM.
All went well with this process so I proceeded to the next step, which was to download and install a custom ROM. I installed the VeNuM ICE 5.5 since I'm a comic book nerd as well as a computer geek.
This wasn't my first time rooting. I've been rooting my EVO for a year of so, and I've rooted my Wife's Nook Tablet too, so I was a bit shocked to see that the Team Rogue CWM recovery program went bye-bye after flashing the VeNuM ROM.
I downloaded ROM manager and tried to flash the latest CWM recovery program from there, but that dind't work. I haven't tried to download the touch recovery, but I was able to reinstall the Rogue CWM recovery program, which then hosed up my ROM. I actually thought I bricked my phone for a minute, but I was able to go back into Rogue Recovery and re-flash the VeNuM ROM.
All went well and I'm back into my phone, but now again when I reboot into recovery mode, I have "Android System Recovery <3e>" like an abridged version of CWM. I don't have near as many options and wonder what's going on.
I never lost my recovery mode before when flashing a ROM. Is there some sort of custom recovery included with this ROM, or am I doing something wrong?

hi. im pretty new at this also, but i think i know the answer to this. well. not really the answer, but i know how to get clockwork recovery back onto the venum rom you are using now. you need Odin3-v1.85 (just google it) and the clockwork recovery StockCWM-EL26.tar (google). Then you put your phone in odin mode, volume down and power from powered off state, run the program, check the PDA option and browse for the stockcwm file, plug in usb and hit start. That'll put the recovery back on your phone.
But as I've been reading, a lot of times, you cannot just download the rom onto the phone or sd card and flash new roms using the cwm recovery. something about the gingerbread and ics and different kernels. .... =D

Please read the "How not to brick your e4gt" or how ever it goes in general. You need to stay away from rom manager and any touch recoveries. To answer your question, rogue recovery went away because the Venum ICE rom has the stock recovery packed in because of all the custom recovery/bricking issues we've been having with ICS. So the Dev left out custom recovery included with his rom
Sent from my SPH-D710 using Tapatalk

I'm not sure what recovery Venum comes with but this might be by design since custom CWM recovery is not installed by design on most ICS roms.
First of all read through this thread: http://forum.xda-developers.com/showthread.php?t=1525495
You chose to flash ICS; if you had chosen Gingerbread this would not be an issue so please read on... ROM manager should NOT be used with ICS. Since you are new, the only CWM recovery you should be using is the stockcwm-el26 posted here: http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
Lastly and most important:
Flashing ICS can be a very dangerous thing for your phone if done improperly. Even flashing back to Gingerbread from ICS can go wrong.
Please do not do any further flashing of ICS without reading and understanding the process of flashing ICS safely!
Also, please feel free to ask lots of questions until you are comfortable with the entire process. That is why we are here.
Edit: Sorry for the very strict tone throughout. You have a very nice WORKING phone and we see a lot of newbies flashing over to ICS without a full understanding of what can go horribly wrong. We also see users asking for help here daily because they have bricked their phone (many times with no hope for repair or recovery).

Maybe I'm just lucky?
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.

BBJon said:
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
Click to expand...
Click to collapse
Coming in late to this thread but I would like to re-iterate what was said about ROM manager and pretty much everything tdunham said. Because you have been, so far lucky, does not mean that luck will continue. Best advice is to remove it and not use it. If you read through some more posts you will see that the bricking doesn't always happen on the first, second, third flash. It can all of a sudden appear. We've had VERY experienced developers brick their phones, so to think you won't just because you've been lucky is not wise.
But some of the comanailities are clear - using ICS recovery to wipe/restore and using ROM manager. Just thought I'd point that out.
If you're coming over from a different phone (HTC etc) check out Qbking77's videos. They are very informative too.
Good luck and have fun.

I'm glad that the op did some reading and had some extra help here. Our phones can be confusing but with extra reading it can be figured out. We try to list the kernel that's in the rom and these are all listed in the development section in some form or another with explanations of what they have, ie cwm or rogue recovery... In addition most of our roms list a change log that you can read that will tell what each version of the rom has in it in case you would rather use an older version. And we keep the older roms posted too... anyway happy flashing !

I've bricked my phone a few time messing around with different ICS roms and kernals. I go back and odin EL29 rooted...start all over from scratch. Try using new recovey kernals posted on ACS. I'm on FE22 with the ACS recovery and am having no issues with flashing zips and making backups as well restoring.
Sent from my SPH-D710 using xda premium

There are some repacked recoveries that Steady used to make for ICS before he disappeared. Those were never and still aren't safe for flashing ROMs though. It's safest to Odin/Mobile ODIN CWM EL26 tar whenever you need recovery and then flash whatever and then reflash an ICS kernel without recovery so that your phone boots
Sent from my SPH-D710 using XDA

Is the Epic a fail when custom Rom installed? Questions? also can ICS be rooted?

Well new company gave me 20% Sprint discount and have become sick of my Tmobiles poor coverage. However I fear wimax might be sucky too here in Seattle. Anyway, long time member here and have been involved in the HTC Sensation and One forums. Both with very very stable roms and kernals.
I was excited to pick up a couple Sprint Galaxy epics and the guy at Sprint had his all rooted and claimed it was smoking fast.
However I came to this forum and see all kinds of complaints of loss of stability just from simple Root of the Epic? Also have not read any stable ICS roms and I have read all of the threads. Plus read this phone is very easy to brick under clockwork. With sensation we use Aroma and it rocks!
So before I move on, I am not looking to break rules on asking ROM questions. I simply would like some input on what ICS rom is stable and supported still as I see many devs have moved on the the sg3 here.
What kernal and radio or what you call modem is stable and how do you find what is for your phone match?
Lastly, what is safest way to ROOT and flash ROMS for this phone?
I did read the stickies but am still confused.
I may be just happy at first to simply ROOT and install the fix for Hot Spot Wi fi and go from there.
Thanks so much.
Not even sure if phones will arrive with stock ICS tomorrow or GB...
Ice

The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.

rovar said:
The SAFEST way to flash stock ROMs in case of emergency is using Odin.I've found both stock ROMs (GB & ICS) very stable, however I reboot my phone everyother day (windows habit).
This thread http://forum.xda-developers.com/showthread.php?t=1525495 was my starting point.
Click to expand...
Click to collapse
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium

iceshark said:
First off thank you for your reply. Interesting, I have read ODIn maybe responsible for bricking many of these phones is that incorrect? Lots of what I found seeing the people are very unstable with the custom roms so far for ICS for this phone of course stock ICS will be here soon.is there the ability to just root the phone and leave the stock ics ROM and just run the sprint hot spot mod.
Sent from my Sensation 4G using xda premium
Click to expand...
Click to collapse
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.

Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.

revamper said:
Odin never causes any bricks as long as the process is not interrupted. Most of the instability is caused by user error. From my experience, all fresh (by fresh I mean wipe data/cache and format system) custom ROM installs have been rock solid stable. Also, most network issues are fixed by updating profile/prl. Official ICS is already out, it is build FF18. Stock ICS will not normally have the hotspot mod. You will have to use a hack to install it yourself. If you want a stock ICS experience, use this odin package (reset user data) to odin your phone to pre-rooted FF18:
http://forum.xda-developers.com/showthread.php?t=1721229
And here is your hotspot hack:
http://forum.xda-developers.com/showthread.php?t=1760712
Nonetheless, I see no reason why you wouldn't just save yourself the time and flash a custom ICS ROM.
Click to expand...
Click to collapse
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.

optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
Thats what it seems from hours reading each ROM thread. Reminds me of the Sensation when GB and or ICS first leaked. Will most likely just root stock and go from there.

CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.

revamper said:
CWM is in the kernel. Current kernels such as chris41g's or AGAT's kernels have patched up recoveries that avoid the emmc bug, so they are completely safe. You should use calkulins format all before flashing a rom in CWM.
For odin, it wouldn't hurt to odin sfhubs wipe data/cache, but it's not necessary. As long as you use the reset user data odin package for FF18, it will take you to stock rooted FF18. Regardless of what rom your phone comes with, run that odin package. You don't need to worry about the modem either because it will install the latest one. Be sure to update your profile/prl in settings>about>system updates after.
If you want to try a custom rom, use odin to flash a kernel with cwm (agat's or chris41g's). Once you have a recovery, flash calkulins format all, and then the ROM of your choice. Modems are not installed through CWM rom zips. You'll have to flash a modem zip in recovery or odin a modem tar.
Click to expand...
Click to collapse
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!

iceshark said:
I was studying Sfhugs FF18 thread and it says I can do the one click root and then install option D and that puts in the FF18, with agats CWM. So is this more simple then flashing FF18 and then doing a flash for either chris or agat kernal with cwm?
Should I use Calkulins format before flashing FF18 from stock?
So when you guys flash new custom roms you have to flash current modem each time? or only if you want to have a more current one? Coming from HTC you only have to flash radio when its required to match a new base leaked. So little confused there too.
Thanks your help has been great!
Click to expand...
Click to collapse
I know I personally use Mijjahz's "GOODNESS" ROM and it runs smooth. Many mods and add ons with more added daily. I flashed agat's 2.2 kernel because I don't like the 2.3 that version 16.6.1 comes with.
I also flashed FF18 over my EL26 modem. Modems don't change between flashing I believe. Those you update yourself. A lot of folks stay on EL29 or find something that works perfectly in their area.
Sent from Konnor the E4GT.

optimummind said:
Imho, there isn't any ics custom rom as of yet that is 100% stable, glitch-free, and reliable. I would wait it out until more polished versions come out. If there is a pretty good one to try, i'd say the blu kuban.
Click to expand...
Click to collapse
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app

cp320703 said:
not sure what you expect from a mobile os but I couldn't disagree more.... my experance on mijjahs goodness has been better and more stable than stock in every way, hell even cm9 and aokp are extremely reliable as well if you can live without dialer codes and prl/profile updates.... no software is ever going to be 100%.... I say flash away, you won't be dissapointed
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
QFT.
ICS ROMs are very stable at this point.

iceshark said:
Thanks, I think we are on the same page with this!
So I just loaded the FF18 Full Restore and Samsung drivers as indicated in this thread,
http://forum.xda-developers.com/showthread.php?t=1670110
I also tested after unzipping to a folder and the ODEN program comes up waiting for me to hook up phone I dont have yet till tomorrow.
I also watched this video and it seems very easy to do if this is correct process,
http://www.youtube.com/watch?v=_IL21F8Gfbs
Still some clarifying questions,
1. If my new phone comes with ICS already pushed to it. Do I simply still install FF18 to get root for the ICS rom?
2. If phone does not come with ICS will this install ICS and Root?
3. Do I need to use this or Caulkins to wipe data first before I do this process on phone out of the box new?
http://forum.xda-developers.com/showthread.php?t=1670110
Also I am little nervous reading this post from SFHUB<, Is he saying not to do the above process thru the built in Odin recovery in the phone if it comes with stock ICS in it? What does this mean???
The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!!
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/show...1&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/show....php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/show....php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!!
- Currently there are some ICS recoveries that are thought to be safe to flash from thanks to the work done on the emmc bug. If one of these is included in your rom it will be noted by the dev in the rom thread, however the safest way is still just to Odin back to el26 in order to avoid any chance of bricking!
Next, once I do this FF!8 and have root and ICS. If I want to dabble in custom roms. I am guessing they are installed by CWM from file downloaded to root of SD card like normal. I do not find CWM touch for this phone anywhere. I am sure I am missing it. It seems from reading the exploit in ICS kernal is causing the bricks. So I am guessing to use SF hubs or Claukins data wipe before loading custom roms. Are we beating to the same drum here?
Will correct radio or modem be installed automtic with FF18 or custom roms? I see many threads just on modems.
Thanks and thanks for the hot spot mod.
Click to expand...
Click to collapse
you're quoting some of my new user guide here, and i haven't updated it since the OTA came out so it somewhat overstates the danger of bricking (not a bad thing really, made you read, didn't it!?) which was much easir to do before we got kernel source, since then agat63 and chris41g have been killin it in kernel development since they got ICS source... their ICS kernels are safe to flash from and can be found in the dev section, if you're on the stock FF18 rooted with stock kernel i would personally ODIN (mobile or desktop) back to EL26, and from there flash whatever custom ICS rom you like, as far as I'm aware all of the roms come with a safe kernel these days but do be sure to double check and flash one if it does not... at that point going forward should you wish to flash something else you can just do it via cwm as per usual without having to odin back to gingerbread....do note however that you can't use touchwiz kernels with AOSP roms, there asr safe AOSP kernels as well however...
edit: oops, just noticed revamper addressed most of this on the last page, to answer another one of your questions though you can try as many modems as you like and decide which one works best for you, its varies phone to phone and area to area... the modem is not at all required to match the build number of the rom, (example: may people still use the el29 modem with ICS) you can use ANY modem with ANY rom

Ive flashed this phone hundreds of times. Put your rom and any other zips you have on external card. Then to do a full clean wipe go to privacy. then factory data reset then check usb storage. You can skip this step, but this is how to get it factory fresh. Download the el26 cwm kenal. Its posted everywhere. Next open Odin go to pda and select EL26 cwm kernal. Uncheck auto reboot. Have battery cover off! Flash kernal pop battery out when it starts to boot. or says pass. then use the vol up and power combo hold them down until boot screen pops up then let off. Next flash calkulins wipe all or wipe no data. . Never brick never fail. Then flash your rom and tweaks and be happy. Ive done this driving down the road its that easy. Laptop sitting in passenger seat with odin up lol. Plus i drive a 5sp full size truck. Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob. I,ll be making multi scenario flashing youtube movies soon. Like mobile tech videos does.

Flashing is easy. Follow directions. There is nothing wrong with this phone just read directions if your a noob.
Click to expand...
Click to collapse
That's all there is to say.

[Q] AT&T S3 (Flashed via s3 toolkit) question on roms

I have a AT&T samsung galaxy S3 rooted by using the samsung galaxy toolkit http://forum.xda-developers.com/showthread.php?t=1746665
I'm interested in flashing the following CM10 Nightly rom http://forum.xda-developers.com/showthread.php?t=1778270 to my phone but have a few questions before I proceed.
1) What precautions should I take before flashing a custom rom? I understand I first need to make a nandoid backup (which I have done) and verify that I have the correct rom for my specific phone model that I will be flashing to. If I were to choose the CM10 Nightly rom, the link from the post goes to http://get.cm/?device=d2att which appears to be correct for my AT&T Samsung Galaxy S3 SGH-1747.
2) Since I flashed with the samsung galaxy toolkit, it flashed the following recovery "CWM-Based Recovery v5.5.0.4 - Do I need to use a different recovery in order to use the CM10 Nightly roms or is this one compatible? If not, how do I go about changing to another recovery?
3) What is the steps for flashing properly? Would I need to update kernel or model or just simply download rom, save to SD card, boot to recovery, then flash the rom in zip form?
I appreciate any your responses in advance. I tend to over analyze and I feel i've read enough about the process of flashing custom roms but I want to be certain. Thank you!

It looks like you got all you ducks in a row, on behalf of the community thanks for being a smart user :good:.
1) You nailed it....make absolutely certain you are downloading the correct software for your device, flashing an incompatible ROM can leave you with a really sexy, expensive paper weight. The d2att identifier is unique to the AT&T variant of the SG3 (i747). Before you flash any new rom or kernel (or anything else for that matter in my opinion) make a nandroid or equivalent backup from your recovery. I do this even for the smallest mod, tweak, theme whatever if for nothing else incase i dont like it it an easy undo 'button'. Besides that i like to keep a fairly recent backup on something other than my phone.
2) For all intensive purposes that version of CWM will work, atleast currently. I would recommend you update it however as that version is several builds behind and there are sometimes updates in the more current ROM builds that may not play nice with older recoveries. The easiest way to do this is download Clockwork Rom Manager from the play store, on the main app screen at the very top is the option to install the latest recovery. It will download, preferably on wifi to minimize downloading errors as much as possible, and then install automatically. There is also atleast one other alternative recovery that i know of, TWRP, which is worth checking out in my opinion. Just keep in mind the backups from the different recoveries are NOT interchangeable.
3) It always best to follow any and all directions in the OP of whatever ROM you are installing as most differ. The generally accepted order for flashing goes something like this although everyone will have an opinion on this i'm sure. ROM > Gapps (if required by the rom) > Reboot > Kernel > Reboot. If you are really concerned you can always just flash one at a time allowing a full reboot in between each flash, personally i think this is overkill but thats just my opinion.
One last personal suggestion, I always keep a copy of my rom, kernel, and any required supporting software on my external sd just in case. It comes in handy if for some reason you try something that doesn't work out the way you had hoped and you are away from a computer and your phone is unable to boot into android. Some would argue that a nandroid makes this unnecessary but with 32 gigs in my current setup its not like im hurting for space. Hope this helps to clarify some things for you, good luck!

dntesinfrno, Thank you very much for your reply and kind words
A lot of the information has been posted on the boards but it can be a little confusing and too much information at once.
You mentioned that I can simply use Rom Manager then click "Flash ClockworkMod Recovery", are there any reports of there being problems in using rom manager to flash the recovery or is the S3 fully supported?
As for the kernel flashing.. I'm really only interested in flashing custom roms (CM10), is it necessary to flash the kernel as well when flashing custom roms? I didn't see anything on the other thread stating anything about flashing kernels so i'm guessing it's not needed?
I'm for sure going to take your recommendation and make a backup of current rom and kernel. Would you recommend Rom Manager to backup the current rom? I see an option that says "Backup current rom" in the application. How do you go about backing those up?
Thank you again! :fingers-crossed:

since I have the cwm-based recovery v5.5.0.4 i'm wondering if I were to use rom manager and flash the latest clockworkmod recovery, would it actually stick after the reboot?

found the following thread here and it looked almost identical to mine: http://forum.xda-developers.com/showthread.php?t=1801534&highlight=cwm-based+recovery
Ended up using rom manager to flash clockworkmod and after rebooting multiple times and booting into recovery, the official clockworkmod recovery is installed. (showing "ClockworkMod 6.0.1.2" now)
As for backing up kernel and everything else, will rom manager do that as well?
Thank you

[Q] Help with flashing roms

Im having trouble fashing roms on my s3.
I was on stock 4.1.2 rooted with TWRP latest recovery
i rooted by flashing a custom recovery thru doin then superSU and all that afterwards thru recovery.
tried flashing a Carbon rom nightly and it just stayed in the splash screen.
i thought it was the rom (maybe bad download)
so i tried to flash CM10.2. The S3 just restarts the recovery whenever i swipe to flash
tried CWM recovery and it said "couldnt mount SD/ExtendedSD"
so i flashed the modded recovery for newer S3s since i just got mine. And still nothing.
i tried Liquid Smooth, Slim and others and they just hang on the Galaxy S3 splash screen.
Any idea as to why this is happening? What am i doing wrong?

The new S3 have been modded by Samsung or Sprint the modded recoveries allow you to mount storage, this still does not allow the new devices to flash any aosp roms like you are trying to do. They won't flash. You can only flash TW roms.
Remember search is your best friend, Have a great day!

edfunkycold said:
The new S3 have been modded by Samsung or Sprint the modded recoveries allow you to mount storage, this still does not allow the new devices to flash any aosp roms like you are trying to do. They won't flash. You can only flash TW roms.
Remember search is your best friend, Have a great day!
Click to expand...
Click to collapse
Wow that blows!!!! Lol
i chose an S3 because of the flexibility of flashing and stuff compared to HTC, Sony, and LG but now Samsung too :crying:
oh well i guess a girl could get used to TW.
is this permanent or will this change? (i mean will someone develop a mod or something to bypass this)
one last Q.
Would the CM10 odin flashable posted by CNexus work?
i mean thats the closest thing ill be able to get right?
thank you so much on the quick reply!! ;D

No the one posted in that thread from Noobernl will work. I believe it's a 10.1 version if you need to have aosp.
If not I highly recommend TPR or MOAR great TW roms... Which is what his phone was really designed for.
Yes as soon as some quality developers get their hands on one of these new S3's it will be figured out. I believe it's in the works right now.
Remember search is your best friend, Have a great day!

Thank you once again.
Ill try that CM rom
if not ill flash the peoples rom
thank you for taking the time to help out.
its really appreciated!!!

[Q] Having trouble with the I747M and ROMs.

Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.

Czaran said:
Alright so I'm new at this and haven't managed to brick my phone yet so that's a good sign.
As far as I've learned the process is Root>Recovery>Rom Flash, at least generally.
I rooted it successfully, but when I try to install recovery with ROM Manager it lists only one S3 with a bracketed cell phone provider I don't think I have. So I ditched CWM and went to Goo Manager but when I try to install that, it just hangs on some download page telling me its about to start.
So I'm going to assume the recovery thing is pretty easy to sort out and move on to my next question.
My S3 is unlocked, but I am under Koodo, which is an extension of Telus. My phone model is a I747M, not an I747. As far as I can see they are identical in hardware and software, but I'm really wondering what ROMs I can install. I've researched but didn't find much, and I don't want to blindly flash a i747 rom onto a potentially different phone, and risk anything.
Oh and PS any ROM with the vanilla android (like on the google phones) will do.
Thanks.
Click to expand...
Click to collapse
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.

BCSC said:
Hello Noob (I mean that kindly, I used to be one)
I'll help you with what ever you need. I'm Canadian and on Bell i747M. Feel free to ask me any questions and I'll reply as soon as I can. Hopefully I wont be too confusing. I'll just try to break down all your questions in a point form.
First, i747 and i747M are almost identical. With the latest 4.3 ROMS there are differences in the bootloader that will make data not work on your phone. For now, stay away from any stock 4.3 ROM. AOSP ROMs (CM10, Task650) are fine.
Recovery: Through Rom Manager you will want to download the recovery titled "Samsung Galaxy S3 (ATT) " The AT&T version of the S3 is commonly shown as D2ATT(i747). This recovery will work for you. I have had a problem with TWRP myself recently being stuck on the download page. There is another way to install TWRP, but it is a bit more difficult. Try CWM first and if you like I will give you instructions for TWRP.
ROMs: If you want the most common and most stable Vanilla ROMs for your phone you are gonna want Cyanogenmod or Task's ROM. They are very similar with a few different features. Beware, if you ask questions in Task's thread you will be told it is an ATT ROM only. It does work on the i747M though.
Latest Cyanogen: http://download.cyanogenmod.org/?device=d2att
Latest Task : http://forum.xda-developers.com/showthread.php?t=1766684
You will of course lose Touchwiz on these ROMs.
Touchwiz Roms:
STAY AWAY FROM 4.3 ROMS!!!!!!
These ones will do as is. Watch that they are still 4.1.2
http://forum.xda-developers.com/showthread.php?t=1766684 This one has a white theme and is my favorite.
http://forum.xda-developers.com/showthread.php?t=2176793 This one has tons of options.
As always be sure to read the OP in every thread. You will learn lots there. If you want any more info reply and I will try and help.
Click to expand...
Click to collapse
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.

Czaran said:
Awesome, I appreciate the writeup. So I flashed recovery successfully (ROM Manager doesn't seem to have d2att anymore so I used ODIN).
I'll probably go for Cyanogen mod tommorow, I'll post again if I have any questions.
Thanks.
Click to expand...
Click to collapse
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.

BCSC said:
CM is a good ROM. There should soon be Kitkat versions available. You will be seeing nightly updates when it does come around. Before you start flashing, you should learn what a 'Nandroid' is. You can take a Nandroid backup in CWM or TWRP. Always save these to an External SD card. If anything ever goes wrong with your ROM, you can just re flash the Nandroid backup and be back to where you were the day you did the backup. The farther you get into flashing the more likely you will need these. Before doing your first Flash, do an Nandroid and copy your photops and stuff off of the phone. When jumping between Stock and AOSP roms, you will need to do a full wipe and will lose what you have not backed up. Be sure to sync contacts to Google....this is the one that has screwed me the most.
Click to expand...
Click to collapse
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.

Czaran said:
Alright, so I have CWM v5.5.0.4, which from what I understand is pretty outdated. It was probably just me following an outdated guide and forgot to look up an updated version. Will I need to update of will it cause any problems? I already backed up my phone on 5.5.0.4 with Nandroid.
Also I feel like I'm misunderstanding the procedure of flashing a new rom. So I downloaded a cm-10.1.3 zip which is is the latest stable build on android 4.2.2. This has an .img inside so this is the rom. I use CWM to flash this onto my phone correct? (Once I figure out if I need to update CWM)
Lastly whats the deal with Gapps? I downloaded the CM Gapps for 10.1 from their wiki. Is this the only way to get Gmail, Maps, and the Google Play Store onto the phone?
From what I understand I think I can just use odin to flash, correct? If so I'd probably prefer that because its the most familiar and noob friendly.
Click to expand...
Click to collapse
I wouldn't use Odin. It really will only become necessary if you want to flash back to complete stock.
You do want the latest version of CWM installed or you will run into problems flashing. You can get this 2 ways.
1: through Rom Manager. You will find your specific CWM with these steps. a-Recovery Setup b-ClockworkMod Recovery c-Hit menu button to left of home and pick 'Show All Devices' d- Here scroll until you get 'Samsung Galaxy S3 (AT&T)' D2ATT. e- Click Flash ClockworkMod Recovery. Allow permissions for root. Ignore the touch option unless you want to pay for it. I can teach you the free way.
You will now have the latest CWM
You can download the latest CM-10.2, it is in release candidate stage and is extremely stable. They have been working on it for months. It will give you 4.3 (The good kind, not the one I warned against). After downloading a ROM, you leave it zipped exactly like it is. Do not extract it, just move it to your SD card. You will also want Gapps. Gapps is necessary because it is Google's own software that is legally not allowed to be built into ROMs. It must be installed separately. You can find those here. They help you know which to use with chart depending on which Cyanogen you use http://wiki.cyanogenmod.org/w/Gapps. Again just move the zip over to your internal.
With these 2 zips transferred to your phone you are ready to start. Before you do, make sure you have transferred all your pics and stuff off of the phone. Also be sure to save your contacts. You can now boot into recovery. You should notice recovery version 6.0.4.3. Volume button scrolls menu, Power button selects. You will want to do a Nandroid backup in case anything goes wrong. I know you did one with CWM 5.5 but should do another just to be sure it is with current CWM. You can delete the other one later.
Goto - backup and restore
Goto - backup to external or /storage/sdcard1 (i put both because im already on 4.4 and may have different menu than you.
Let this work and when done continue to flashing ROM
Go to 'choose zip from /sdcard'
Select CM-10-xxxxxxx.zip
After this completes you will do the same with Gapps.zip
After completion of both files you will need to factory reset your phone. Flashing AOSP over Stock will cause boot loops if you do not.
Go back to CWM main menu and select wipe data/factore reset
After completing this go to wipe cache partition and select this.
Finally you want to wipe Dalvik cache. you will find this in CWM under main menu /advanced/wipe dalvik cache.
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.

BCSC said:
Upon completion of this you should have CM10 4.3 running. Just exit CWM reboot phone and when booted follow setup instructions.
Let me know if you get stuck somewhere.
Click to expand...
Click to collapse
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!

Czaran said:
Alright cool. So through Mod Manager, there was not d2att, there was only S3(Metro PCS) which I thought was a bit odd. I found a way to flash an updated recovery via terminal emulator so that went well.
And your steps were very well written and concise. I'm now running CM without a problem.
Thanks for your help!
Click to expand...
Click to collapse
Cool terminal emulator was that other way to do it. Hope all is well for you with this. Welcome to flashing. As another tip, if you are going to flash a lot, there is an app called Titanium backup that is well worth the $5 it costs. It saves all your apps and data and after a clean wipe you can just reinstall all your apps in one step. For example after a wipe you will not lose your Angry Birds levels if you restore your titanium data. It's worth a look.