Develop Bugs

Kernels and flashing

Noob here.
I had a question about kernels. What the hell are they and how do you flash?
I just put Miui on my EVO. I really like it but there are some issues with Bluetooth and also voice messages not wanting to send or receive. Plus the front camera issue.
I saw some others flashed a different kernel to fix some issues so I was wondering how to do that.
Also mentioned was doing a Nandroid backup... what is that?

zatos said:
Noob here.
I had a question about kernels. What the hell are they and how do you flash?
I just put Miui on my EVO. I really like it but there are some issues with Bluetooth and also voice messages not wanting to send or receive. Plus the front camera issue.
I saw some others flashed a different kernel to fix some issues so I was wondering how to do that.
Also mentioned was doing a Nandroid backup... what is that?
Click to expand...
Click to collapse
Take the zip you want drop it in your sd card use rom manager recovery and install new zip nanroid is under recovery mode as well

Flash a kernel- place the zip file on the root of your sd card [not in a folder], wipe you cache and dalvik cache, then click install zip from sd card, then select your file
Nandroid [a backup]- from the main menu, select backup and restore, click backup, done.
Always do a backup before flashing a kernel because it may not play nice.

Once you've got the basics down. Just start with one of Netarchy's (my preference) and try a few to see what seems to flow best with your phone. I've had the best luck with Nets 4.3.1 more havs nosbc. Good luck.

To wipe the cache and dalvik cache, is that listed under the recovery menu or do I have to do it some other way? What is stored in the cache?
Also hope I got this right, but I can only use AOSP kernels with Miui? I'm not sure what is different about AOSP. Is Netarchy AOSP?

Unfortunately, I don't believe Nets has any AOSP kernels. Sorry, I don't have a good kernel recommendation for Miui. I'm a MikFroyo fan, tried a lot of roms and kernels, but haven't given Miui a try. I like my 4G. Mik is fast and stable, so I've stuck with it for a while now. Depending on what recovery your using, to wipe the dalvik cache, you should have that option. In clockwork its under the advanced i believe and in amon its under wipe. Don't really know what is stored in cache, but any time you make a change or flash something new, always good to wipe the dalvik cache.

What is AOSP versus whatever else is used?

in the evo world, every rom you'll find is either AOSP or Sense based. Aosp roms are custom made roms built straight from android source. Miui and Cyanogen are the most popular AOSP roms. Sense roms are basically the rom sprint uses that people have hacked to make it faster/personalized.

Do the kernels have to be specifically for the EVO?

zatos said:
What is AOSP versus whatever else is used?
Click to expand...
Click to collapse
AOSP- Android Open Source Project ; closest to bare bones Android [Think Cyanogenmod]
the other is Sense- Think stock HTC Evo, roms like MikFroyo, Azrael, ect

zatos said:
Do the kernels have to be specifically for the EVO?
Click to expand...
Click to collapse
I believe so. Make sure you're running a stock kernel with stock rom aosp kernel for an aosp rom.

Nandroid
Nandroid backups are performed in custom recovery. They essentially backup the entire "image" of your current ROM into the "Nandroid" folder on your SD card. The beauty of this is that you can take a nandroid backup, flash a ROM and, if something goes wrong or you don't like it, you can restore via nandroid and return your phone to a previous state.

No one has still answer his original question...
Android relies on Linux version 2.6(the kernel) for core system services such as security, memory management, process management, network stack, and driver model. The kernel also acts as an abstraction layer between the hardware and the rest of the software stack.
So basically, it is what allows for better management between the rom and the actually hardware. For example, your rom could manage how many applications are running and using up cycles of your processor, but your kernel will determine how your processor elevates to the needed speeds for the ongoing task. Kernels are important to keep your phone secure, stable and longer batteries

General help - Coming from a OG Evo

I am an OG Evo owners and just getting back into flashing and trying out different roms. Back when I would flash custom roms, the tool of choice for backing up data+apps was Titanium backup. Has this changed?
I am on Blazer 1.7 right now and would like to update to 1.9 but I don't want to lose all of my data and apps. He says something in his OP about there being an update.zip, but I don't see it anywhere. Is this pretty common for devs to include a update.zip that lets you seamlessly upgrade from version to version of the same custom rom?
With the OG Evo, you couldn't back up data from a ASOP rom and then flash over to a sense ROM and restore your data or else it would crap out on you. Is there anything that I need to watch out for in that respect?
So I have two questions
1. How do I retain my apps and information going from the same custom rom to a updated version of that custom rom?
2. How do I retain my apps and information going form one custom rom to another custom rom?
Thanks!

Hi and welcome to this awesome phone! XD
I too came from an OG EVO, was sporting Warm twopointthree back then...
jhoffy22 said:
Back when I would flash custom roms, the tool of choice for backing up data+apps was Titanium backup. Has this changed?
Click to expand...
Click to collapse
Nope, it is still the tool of choice and everything from the OG EVO applies. It's a universal tool and works the same across devices. Do a user app+data only back up from OG EVO and restore it on the SG3. Do not restore system apps from OG EVO to SG3, these are the apps that are red or yellow font in TB.
jhoffy22 said:
I am on Blazer 1.7 right now and would like to update to 1.9 but I don't want to lose all of my data and apps. He says something in his OP about there being an update.zip, but I don't see it anywhere. Is this pretty common for devs to include a update.zip that lets you seamlessly upgrade from version to version of the same custom rom?
Click to expand...
Click to collapse
I'm not on Blazer and haven't used it, maybe some one will come in and comment on this. You could try another ROM, like FreeGS3. It has a lot of positive reviews and is up-to-date with the latest OTA. The link is in my sig... You should have TWRP recovery for this ROM to install properly, the link is also in my sig.
jhoffy22 said:
With the OG Evo, you couldn't back up data from a ASOP rom and then flash over to a sense ROM and restore your data or else it would crap out on you. Is there anything that I need to watch out for in that respect?
Click to expand...
Click to collapse
The same applies with the SG3, this is because the system apps on the stock or TW SG3 are well Touch Wiz System.UI and framework and applying these to a AOSP ROM that has completly different System.UI and framwork will bring a lot of force closes and ultimatly an unresponsive device. You can restore user apps without issues.
jhoffy22 said:
1. How do I retain my apps and information going from the same custom rom to a updated version of that custom rom?
Click to expand...
Click to collapse
There are a few options for this, you can "dirty flash" the ROM and you'll have the same setup and data as before the flash. This is just flash the ROM and only wipe cache and dalvik, but you should only do this when it's an incremental update from the same ROM. Although some say it is best to do a complete wipe and then flash the ROM even if it's incremental update of the same... One thing reported from some doing a dirty flash is poor battery performance or randon force closes, only way to fix this is a clean flash. Also, the dev (usually) let's the user base know if there was a change to the System.UI or framework and needing a clean install of the incremental update. This was also the case back in the OG EVO. Try the different options and see what's best for you.
jhoffy22 said:
2. How do I retain my apps and information going form one custom rom to another custom rom?
Click to expand...
Click to collapse
Answered above, same applies.
Also, for clean install do the following, Wipe Factory Reset>Wipe System>Wipe Cache>Wipe Dalvik and then flash the new ROM.

dragon_rckr said:
Hi and welcome to this awesome phone! XD
I too came from an OG EVO, was sporting Warm twopointthree back then...
Nope, it is still the tool of choice and everything from the OG EVO applies. It's a universal tool and works the same across devices. Do a user app+data only back up from OG EVO and restore it on the SG3. Do not restore system apps from OG EVO to SG3, these are the apps that are red or yellow font in TB.
I'm not on Blazer and haven't used it, maybe some one will come in and comment on this. You could try another ROM, like FreeGS3. It has a lot of positive reviews and is up-to-date with the latest OTA. The link is in my sig... You should have TWRP recovery for this ROM to install properly, the link is also in my sig.
The same applies with the SG3, this is because the system apps on the stock or TW SG3 are well Touch Wiz System.UI and framework and applying these to a AOSP ROM that has completly different System.UI and framwork will bring a lot of force closes and ultimatly an unresponsive device. You can restore user apps without issues.
There are a few options for this, you can "dirty flash" the ROM and you'll have the same setup and data as before the flash. This is just flash the ROM and only wipe cache and dalvik, but you should only do this when it's an incremental update from the same ROM. Although some say it is best to do a complete wipe and then flash the ROM even if it's incremental update of the same... One thing reported from some doing a dirty flash is poor battery performance or randon force closes, only way to fix this is a clean flash. Also, the dev (usually) let's the user base know if there was a change to the System.UI or framework and needing a clean install of the incremental update. This was also the case back in the OG EVO. Try the different options and see what's best for you.
Answered above, same applies.
Also, for clean install do the following, Wipe Factory Reset>Wipe System>Wipe Cache>Wipe Dalvik and then flash the new ROM.
Click to expand...
Click to collapse
Thank you for the awesome reply! Blazer 1.7 is awesome, smooth as butter and no problems with battery life whatsoever. I'm really enjoying it. The only reason I want to update is because of the pop up that I am getting about the new software update being available. I don't want to accidentally install the update and then brick my phone.

jhoffy22 said:
Thank you for the awesome reply! Blazer 1.7 is awesome, smooth as butter and no problems with battery life whatsoever. I'm really enjoying it. The only reason I want to update is because of the pop up that I am getting about the new software update being available. I don't want to accidentally install the update and then brick my phone.
Click to expand...
Click to collapse
Gotcha! No worries here, just hit apply update and it'll reboot and "try" to install but it will fail since you have a custom bootloader. It won't brick the phone at all, unlike ye ol EVO :/
The thing that has bricked many SG3 has been flashing a ROM the international version... stay away from those.
BTW if you think Blazer is smooth, try FreeGS3, you'll be blown away haha
There's also a JB leak from Sprint in the dev section, I'm trying that tonight.

dragon_rckr said:
Gotcha! No worries here, just hit apply update and it'll reboot and "try" to install but it will fail since you have a custom bootloader. It won't brick the phone at all, unlike ye ol EVO :/
The thing that has bricked many SG3 has been flashing a ROM the international version... stay away from those.
BTW if you think Blazer is smooth, try FreeGS3, you'll be blown away haha
There's also a JB leak from Sprint in the dev section, I'm trying that tonight.
Click to expand...
Click to collapse
Haha I will be careful to avoid that then.
I have one more question. When doing a restore with Titanium backup coming from one rom to another (just switched from Blazer to FGS3), what restore option do I choose? I chose to "restore missing apps with data"

jhoffy22 said:
Haha I will be careful to avoid that then.
I have one more question. When doing a restore with Titanium backup coming from one rom to another (just switched from Blazer to FGS3), what restore option do I choose? I chose to "restore missing apps with data"
Click to expand...
Click to collapse
Yup, just that and select which user apps you want to restore and let go through the process.

dragon_rckr said:
Yup, just that and select which user apps you want to restore and let go through the process.
Click to expand...
Click to collapse
Sweet, thanks a lot!

jhoffy22 said:
Sweet, thanks a lot!
Click to expand...
Click to collapse
No prob
You can also restore some system apps, but be careful with which ones. I usually restore dialer storage, msg storage, wifi settings and account sync settings.

[Q] HouseCleaning Questions

After flashing my first custom ROM half a year ago life been great. However, with 4.3 in the pipelines, now seems like a good time to update and wait for 4.3 or maybe KLP.
So some questions before I take the jump:
1) Sweep2wake. I really like it, but is it a large battery drain?
2) TWRP and CWM. Any significant difference (for casuals)? I betting it doesn't so, TWRP updater suggestions?
3) Junk files. My phone came with a crappy Chinese Sense ROM and there were some files leftover. What are non-essential folders and is there a app to do it for me?
4) Good utilities/tools. I know a few renown ones like Titanium Backup and Tasker, but it's always good to know more.
Thanks in advance for taking you time to read this! :victory:

Metaception said:
After flashing my first custom ROM half a year ago life been great. However, with 4.3 in the pipelines, now seems like a good time to update and wait for 4.3 or maybe KLP.
So some questions before I take the jump:
1) Sweep2wake. I really like it, but is it a large battery drain?
2) TWRP and CWM. Any significant difference (for casuals)? I betting it doesn't so, TWRP updater suggestions?
3) Junk files. My phone came with a crappy Chinese Sense ROM and there were some files leftover. What are non-essential folders and is there a app to do it for me?
4) Good utilities/tools. I know a few renown ones like Titanium Backup and Tasker, but it's always good to know more.
Thanks in advance for taking you time to read this! :victory:
Click to expand...
Click to collapse
Wait for 4.3? Plenty OASP ROMs based on it just now.
If you mean an official 4.3 that's VERY unlikely, and there isn't a chance in hell we'll see an official KLP.
I expect AOSP KLP to be available though. They'll have it on old Nexus 7 at least, and that's port-able to HOX, mostly.
Your questions:
1) No.
2) Use Philz Advanced Touch Recovery. It can backup AND restore in BOTH TWRP and CWM formats amongst MANY other things.
3) Non-essential folders? You''ll be completely wiping the phone if you move to 4.3 anyways. You won't be keeping the installed apps or data intact it won't even boot for you.
4) BetterBatteryStats. GSam Battery Monitor. Trickster MOD. Battery Monitor Widget. Greenify. SManager. And I would also consider Superbeam an essential.

Tigerlight said:
Wait for 4.3? Plenty OASP ROMs based on it just now.
If you mean an official 4.3 that's VERY unlikely, and there isn't a chance in hell we'll see an official KLP.
I expect AOSP KLP to be available though. They'll have it on old Nexus 7 at least, and that's port-able to HOX, mostly.
Your questions:
1) No.
2) Use Philz Advanced Touch Recovery. It can backup AND restore in BOTH TWRP and CWM formats amongst MANY other things.
3) Non-essential folders? You''ll be completely wiping the phone if you move to 4.3 anyways. You won't be keeping the installed apps or data intact it won't even boot for you.
4) BetterBatteryStats. GSam Battery Monitor. Trickster MOD. Battery Monitor Widget. Greenify. SManager. And I would also consider Superbeam an essential.
Click to expand...
Click to collapse
All the 4.3 ROMs are nightlies, and my preferred ROMs, PA and ICJ, don't even have nightlies yet.
1) Yay!
2) Thanks I will check that out, but I am also looking for something like ROM Manager for updating my recovery to the latest version.
3) "Complete" wipe apparently means "Wipe Cache, Dalvik, Factory Reset and System" cuz "If you click anything else, IT WILL WIPE YOUR SD CARD AND YOU WILL HAVE MORE ISSUES ON YOUR HEAD!" that's what I did and I still had a few files leftover. Just junk files taking up ma space
4) Ohh thanks, I already had Greenify, will check the rest out.

Metaception said:
All the 4.3 ROMs are nightlies, and my preferred ROMs, PA and ICJ, don't even have nightlies yet.
1) Yay!
2) Thanks I will check that out, but I am also looking for something like ROM Manager for updating my recovery to the latest version.
3) "Complete" wipe apparently means "Wipe Cache, Dalvik, Factory Reset and System" cuz "If you click anything else, IT WILL WIPE YOUR SD CARD AND YOU WILL HAVE MORE ISSUES ON YOUR HEAD!" that's what I did and I still had a few files leftover. Just junk files taking up ma space
4) Ohh thanks, I already had Greenify, will check the rest out.
Click to expand...
Click to collapse
You can't use ROM Manager unless your HOX is S-Off.

Tigerlight said:
You can't use ROM Manager unless your HOX is S-Off.
Click to expand...
Click to collapse
Well darn, I'm guessing no luck with a TWRP updater either then :/
I suppose I will have to manually update the recovery then.
EDIT: Would GooManager work?

Metaception said:
Well darn, I'm guessing no luck with a TWRP updater either then :/
I suppose I will have to manually update the recovery then.
EDIT: Would GooManager work?
Click to expand...
Click to collapse
No. You cannot flash recovery on an S-On HOX with ANY app on the phone, it MUST be done from fastboot.

[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.

[Q] Need some advice for a noobie

Hi first time posting so please take it easy on the noob. So i just rooted my nexus 7 2013. The main reason was because i wanted to be able to extend battery life and the main thing is that i bought a micro usb host otg cable with power and want to be able to charge as well as power my external hard drive. now i read that elementalx kernel allows you to do that. Would i flash the elementalx kernel first or do i flash a rom before a kernel. I'm pretty confused on where to go to download and which one i flash first.

Welcome to an experience with a great tablet! You want to flash a kernel after a ROM. As the intro to ElementalX says,
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.

Pandae said:
Welcome to an experience with a great tablet! You want to flash a kernel after a ROM. As the intro to ElementalX says,
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.
Click to expand...
Click to collapse
can you install any rom with any kernel. are their roms that will be more compatible with certain kernels. lastly is flashing a rom and kernel the same process of wiping out all the cache then installing while in recovery mode?

j0hnnyyyy said:
can you install any rom with any kernel. are their roms that will be more compatible with certain kernels. lastly is flashing a rom and kernel the same process of wiping out all the cache then installing while in recovery mode?
Click to expand...
Click to collapse
For the most part there will be two types of ROMs
#AOSP based ROMs
#Cyanogen based ROMs
Each kernel and ROM developer will state in the OP (original post; first post of the thread) which source they built their ROM off of.
As a general rule, flash AOSP based kernels for AOSP based ROMs and Cyanogen based kernels for Cyanogen based ROMs.
Flashing a ROM usually requires a factory reset in recovery (apps will be gone, but your personal data/media will be intact) if coming from another ROM. For example you are on ROM A and want to try ROM B, you must factory reset and wipe caches and flash ROM B.
Once you are on ROM B and if the developer updates ROM B, you can sometimes flash ROM B without the factory reset and only perform the wiping of the caches (this is called a dirty flash).
** IMPORTANT ** Each ROM might have their own special instructions for installation, so always read the first 2 or 3 posts of the thread to get all the important info you need.
If you need help:
1. Check the OP
2. Use the search function in the thread
3. Google it
4. After you have done that and still can't find an answer, post in the respective thread about your problem and provide as much detail as possible.
The reason for this is because threads sometimes get spammed with the same questions over and over again, which clog up the thread unnecessarily. Your question might have been asked before, so searching to see if the question has been asked can also lead you to the answer!
Another thing I've learned is to use the thanks button for those developers whose ROM or kernel you use and like, and people who have helped you. Sometimes donating money to developers to show support isn't a viable option for some, but using the thanks button to show appreciation can go a long way as well!
Hope this helps!
- Another noob

Protomartyr said:
For the most part there will be two types of ROMs
#AOSP based ROMs
#Cyanogen based ROMs
Each kernel and ROM developer will state in the OP (original post; first post of the thread) which source they built their ROM off of.
As a general rule, flash AOSP based kernels for AOSP based ROMs and Cyanogen based kernels for Cyanogen based ROMs.
Flashing a ROM usually requires a factory reset in recovery (apps will be gone, but your personal data/media will be intact) if coming from another ROM. For example you are on ROM A and want to try ROM B, you must factory reset and wipe caches and flash ROM B.
Once you are on ROM B and if the developer updates ROM B, you can sometimes flash ROM B without the factory reset and only perform the wiping of the caches (this is called a dirty flash).
** IMPORTANT ** Each ROM might have their own special instructions for installation, so always read the first 2 or 3 posts of the thread to get all the important info you need.
If you need help:
1. Check the OP
2. Use the search function in the thread
3. Google it
4. After you have done that and still can't find an answer, post in the respective thread about your problem and provide as much detail as possible.
The reason for this is because threads sometimes get spammed with the same questions over and over again, which clog up the thread unnecessarily. Your question might have been asked before, so searching to see if the question has been asked can also lead you to the answer!
Another thing I've learned is to use the thanks button for those developers whose ROM or kernel you use and like, and people who have helped you. Sometimes donating money to developers to show support isn't a viable option for some, but using the thanks button to show appreciation can go a long way as well!
Hope this helps!
- Another noob
Click to expand...
Click to collapse
thanks this helped out a lot and completely understand about not trying to repost questions that have been answered. Just one question if i flash a rom and do a backup. then flash a completely different rom and do a backup for that as well I'm guessing ill have back up for both roms. my question is i use twrp and have the app online nandroid backup, would it be better to go into recovery and backup or is it safe to use the app? Also after flashing a rom is it the same process to flash the kernel?

Yes, it is the same process. Some flashable zip packages are included with the AROMA installer, which is a simple interface to give you options as you flash. Be sure to wipe Cache and Dalvik Cache after flashing roms and kernels.
Don't bother asking for the best Rom and Kernel combo. Try them out for yourself, if you truly want to learn more about what you are doing. Please don't become another user looking for a quick fix. (You called yourself a noobie, so I assume that you intend to learn more.)
Read, read, read! Follow the advice of the users who replied to you! It could save your life! Or, at least, save you a brick.
Most importantly, DON'T PANIC when your device doesn't get past the boot animation. Most likely, you asked something that doesn't work well with the Rom/kernel/MOD combo. Reboot into recovery, wipe, and try again.
Extra tips: clean flash whenever you can. You tend to lose track of stuff that you have flashed when you dirty flash a few times, and not every mod gets removed completely. Backup often as well.
Feel free to come back if you need more help.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

aarsyl said:
Yes, it is the same process. Some flashable zip packages are included with the AROMA installer, which is a simple interface to give you options as you flash. Be sure to wipe Cache and Dalvik Cache after flashing roms and kernels.
Don't bother asking for the best Rom and Kernel combo. Try them out for yourself, if you truly want to learn more about what you are doing. Please don't become another user looking for a quick fix. (You called yourself a noobie, so I assume that you intend to learn more.)
Read, read, read! Follow the advice of the users who replied to you! It could save your life! Or, at least, save you a brick.
Most importantly, DON'T PANIC when your device doesn't get past the boot animation. Most likely, you asked something that doesn't work well with the Rom/kernel/MOD combo. Reboot into recovery, wipe, and try again.
Extra tips: clean flash whenever you can. You tend to lose track of stuff that you have flashed when you dirty flash a few times, and not every mod gets removed completely. Backup often as well.
Feel free to come back if you need more help.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
Click to expand...
Click to collapse
thanks. I flashed cleanrom and wiped all the cache before doing so. then i flash elementalx but i didn't wipe cache. one of my friend told me it doesn't really matter that much for kernels but does for roms. he also suggested i wait before rebooting after installing a rom in recovery mode. can you answer any of the part of waiting a certain period of time to let the rom and kernel set?

j0hnnyyyy said:
thanks. I flashed cleanrom and wiped all the cache before doing so. then i flash elementalx but i didn't wipe cache. one of my friend told me it doesn't really matter that much for kernels but does for roms. he also suggested i wait before rebooting after installing a rom in recovery mode. can you answer any of the part of waiting a certain period of time to let the rom and kernel set?
Click to expand...
Click to collapse
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app

Protomartyr said:
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
he tried explaining to me over text but confused so go into recovery mode wipe all cache. then click install. find file swipe to install then page comes to reboot. on that reboot page is that when you wait or click reboot then wait?

j0hnnyyyy said:
he tried explaining to me over text but confused so go into recovery mode wipe all cache. then click install. find file swipe to install then page comes to reboot. on that reboot page is that when you wait or click reboot then wait?
Click to expand...
Click to collapse
Once you get to the reboot screen in recovery, go ahead and reboot. It's after you reboot that first time that you should wait some time.
Sent from my Nexus 4 using xda app-developers app

Protomartyr said:
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I didn't know that about Nexus devices. I always wipe caches for my phone, because I will enter a bootloop if I do not do so. This is my first Nexus device, and I'm learning a lot of new things myself.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

I have a question about backups. I've been researching and reading lot but there are a lot of different opinions . so I installed cleanrom with elemntalx kernel. Would it be best to make a backup in recovery mode or use online nandroid backup. I read something like online nandroid backup works only on certain Roms. Also I have titanium backup but I read that it isn't good to use titanium backups on different Roms? So if I backup through titanium backup and flash let's say a different ROM like cyanogenmod ROM I can't use the backup I created when I had cleanrom flashed?

j0hnnyyyy said:
I have a question about backups. I've been researching and reading lot but there are a lot of different opinions . so I installed cleanrom with elemntalx kernel. Would it be best to make a backup in recovery mode or use online nandroid backup. I read something like online nandroid backup works only on certain Roms. Also I have titanium backup but I read that it isn't good to use titanium backups on different Roms? So if I backup through titanium backup and flash let's say a different ROM like cyanogenmod ROM I can't use the backup I created when I had cleanrom flashed?
Click to expand...
Click to collapse
Nandroid and Titanium backups are used for different purposes.
Titanium backups deal with apps and app settings. They are useful when after flashing a ROM Update. For example, you are using ROM A revision 1 and the developer has posted a new update ROM A revision 2. Since it's usually recommended to clean flash updates of a ROM (read the OP of the ROM thread for further info), this would result in you having to reinstall all your apps and reapply settings and such (which takes time). However with titanium backup, all you have to do is make sure you backup apps/settings when on revision 1. Then after you flash revision 2, you can restore your titanium backup and now you have all your apps and settings.
** IMPORTANT ** Titanium backups should not be used when moving to a DIFFERENT ROM. This may cause problems/incompatibilities.
Nandroid Backups are basically system images. So basically it just takes a snapshot of the current state of your phone, and when you restore it it will be the same as if nothing has changed. This is especially helpful in two situations:
1) when trying different ROMs (i.e. you flash another ROM but don't like it, you can easily switch back via the nandroid backup)
2) when messing with system files and reverting to a previous state (i.e. you are trying to mod your navigation bar or some other customization and decide you don't like it or accidentally messed up. You can use the nandroid backup to revert those changes)
It's also usually helpful to take backups at the appropriate time and name them accordingly. For example, this is the process I take when flashing a custom mod.
1) Nandroid backup before you apply custom mod A. I name the backup "Before applying custom mod A"
2) Apply custom mod A
3) If all goes well and mod A works, I also make a nandroid backup after this and name it "Applied custom mod A"
OR
If custom mod A messes up my phone, I just restore the backup named "Before applying custom mod A"
The reason why I also make a nandroid backup after successfully applying mod A (and decide to keep the mod) is so that I can have an up to date restore point. If you make modifications to the phone and decide to keep them, make an updated nandroid so you don't have to reapply the modifications again.
Sorry for the long wall of text, but hope this helps!

Protomartyr said:
Nandroid and Titanium backups are used for different purposes.
Titanium backups deal with apps and app settings. They are useful when after flashing a ROM Update. For example, you are using ROM A revision 1 and the developer has posted a new update ROM A revision 2. Since it's usually recommended to clean flash updates of a ROM (read the OP of the ROM thread for further info), this would result in you having to reinstall all your apps and reapply settings and such (which takes time). However with titanium backup, all you have to do is make sure you backup apps/settings when on revision 1. Then after you flash revision 2, you can restore your titanium backup and now you have all your apps and settings.
** IMPORTANT ** Titanium backups should not be used when moving to a DIFFERENT ROM. This may cause problems/incompatibilities.
Nandroid Backups are basically system images. So basically it just takes a snapshot of the current state of your phone, and when you restore it it will be the same as if nothing has changed. This is especially helpful in two situations:
1) when trying different ROMs (i.e. you flash another ROM but don't like it, you can easily switch back via the nandroid backup)
2) when messing with system files and reverting to a previous state (i.e. you are trying to mod your navigation bar or some other customization and decide you don't like it or accidentally messed up. You can use the nandroid backup to revert those changes)
It's also usually helpful to take backups at the appropriate time and name them accordingly. For example, this is the process I take when flashing a custom mod.
1) Nandroid backup before you apply custom mod A. I name the backup "Before applying custom mod A"
2) Apply custom mod A
3) If all goes well and mod A works, I also make a nandroid backup after this and name it "Applied custom mod A"
OR
If custom mod A messes up my phone, I just restore the backup named "Before applying custom mod A"
The reason why I also make a nandroid backup after successfully applying mod A (and decide to keep the mod) is so that I can have an up to date restore point. If you make modifications to the phone and decide to keep them, make an updated nandroid so you don't have to reapply the modifications again.
Sorry for the long wall of text, but hope this helps!
Click to expand...
Click to collapse
thanks very helpful so using the online nandroid backup app is the same thing as making a backup in twrp recovery mode