yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bnw99:
Hmm.. that just seems like a bit much of a batt drain when its just in standby mode. I am coming from a iphone 4 so Im used to battery drain not being as drastic. I was using batt saver mode and turning off 4g when on wifi and everything. No sync and still it was not impressive. I dont think I got 2 bad devices..:/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EVOme:
I have K9 mail running on my S3 and it shows 20% of battery. think that's why I am as low as I am right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drot84:
Anyone have good sources/info on when there might be 32GB or 64GB versions of the GS3 for AT&T?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ex-28:
cant seem to get playstore to sync with my phone

i've removed and readded google accout , let it sync i can download fine from my phone , but when on computer i click install select my device and click install , says it will be downloaded shortlly but i not getting the notification , i have also reset playstore in application manager back to default , no luck ,

any other ideas ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
I never used cwm on the gs3 I always just downloaded goo manager and clicked menu install open recovery script and it flashes twrp for u
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ebcrew:
maybe you can help me out, i went from the captivate to the iphone (which i hated so much) so i switched immediately to the S3.

I was pretty knowledgeable with the captivate, but a little confused with the S3.

Basically im rooted, not im not sure what steps i need to take to flash ROMs, and im confused about the flash counter also. captivate had no such thing and was pretty simple to flash ROMs, just used ODIN.

thanks for any help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
If this is the method u used to.root http://xdaforums.com/showthread.php...ter - [ATT / Bell / Telus / Rogers / Sasktel]

Then u should be fine to flash a recovery and just start flashing roms like u did on ur cappy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
Check out the I747 link in my signature
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brianray14:
Doesn't matter which method you've used to root, rom manager is free and will flash recovery for you. Triangle away app will reset counter (dunno why ppl are concerned about this). Also a thread exists in the dev thread for flashable touch CWM

---------- Post added at 05:14 PM ---------- Previous post was at 05:13 PM ----------

Btw, those on phone using tapatalk or xda can't see your sig
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hick.:
I'm using the stock rom, since I like the features (Motion mainly) and i'm rooted, I was wondering what's the best kernel for me? Coming from a low budget phone, to this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ebcrew:
awsome guide. thanks alot, thats exactly what i was looking for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
Glad you found it useful, buddy.

Touchwiz kernels can be found in the Android Development section. They're all pretty good. I've always used ktoonsez kernels without issue. Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OfficialDoughboy:
The rom I was using was this one - http://xdaforums.com/showthread.php?t=2176793

I have wiped everything (cache, davlik) and set permissions every time I do a reset. That is why I went to a custom rom and installed TWRP, installed Hyperdrive then did a recovery backup according to TWRP instructions. Had the phone running for a week and then it crashed again, and rebooted itself and would not load into the launcher. I then used TWRP to restore and afterwards the phone would still not load to the launcher.

I have done everything that has been suggested and there appears to be no solution. The only thing I can think of at this point is to get some type of logging app running that tells me the exact problem that is happening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
Okay, let's start with the premise that despite the fact that the model phone you have should be the same for every one of them, they actually differ enough with the combined tolerances of all the components (which themselves vary from one production run to another) that some phones have issues with ROMs and kernels that others do not. Mine are six months apart and react differently to the same kernel, but are fine with the same ROMs. Logging activities won't change this.

You really have to find another TW ROM and flash it or flash a different kernel to the Hyperdrive ROM. If the problem disappears one way or the other, there's your answer. If that TW ROM has issues, perhaps its a kernel issue -- different ROMs can have the same kernel. This is part of the process of eliminating issues.

You can also simply run with rooted stock ROM and make many of the same changes, such as debloating.

You can flash AOSP or AOKP ROM. Is there something specifically about TW ROMs you like?

Short of trading in phone for another, this is what your options are. By the way, some versions of TWRP have issues. I run CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Snow.Goose:
Hi! Just upgraded from a Captivate, haha. I was just wondering, whenever I try to transfer files over MTP/usb to the internal memory, it always freezes and stops after a few seconds. Is there a work around or anything I could try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sykotyk:
be gentle its my first time

So, I have a galaxy s3 i747m. Rogers. Anyways as usual aways a hard time with everything you try to do with this company. Right now im dieing to try this aokp rom and my wife is getting irritated with my endless reading on the forums. The baseband im on (checked with bootloader) i747mldlk4 and it say d2can beside device also 4.1.1.. I guess my biggest questions are; Before I wipe data and cache and load the rrom and gapps on am I supposed to flash the bootloader that the developer recommends for canadian users first THEN go through the procedure of loading the rom or vice versa. I understand that the d2att will work on my phone but apparently have a possibility of losing lte. I should also mention I rooted my phone with supersu v1.27 with very little knowledge on how everything works where I followed a step by step video, and am trying to catch up and understand now. Thanks ahead of time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
There's no need to update bootloader on rooted I747M if you're going to flash the appropriate ROM for it. No need to wipe cache and dalvik first. What you need are custom recovery (CWM or TWRP) installed, then reset phone and user data with it, flash ROM zip with it and then wipe cache and dalvik in recovery before rebooting system.

There seems to be disagreement on whether 4G and LTE are the same thing, but as far as I know, they are. i747mldlk4 is the baseband, not bootloader, and d2can refers to carrier(s). As for an irritated wife...good luck with that. :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
All LTE networks are in the 4G classification, you could have 4G networks that do not use LTE. In North America, most carriers have gone with LTE for their new high speed data networks.

LTE == long term evolution, which is a specific type of high speed data network in the 4G family/classification

4G == a standard for high speed data networks, specifically with certain speed capabilities

3G == a older standard for high speed data networks, HSPA, HSPA+ and WiMax are all 3G networks NO matter what your carrier calls them.

Unfortunatly many scum sucking carriers relabelled their 3G networks to 4G as everyone knows something called 4G is better/stronger/faster. Plus rebranding your network is way cheaper than actually deploying new towers/equipement and rolling out actual faster networks. Which has led to mass confusion about both 3G and 4G networks and what kind of speeds you should get from them.

Most ASOP roms have corrected the labelling and will display H (3G HSPA), maybe H+ (faster 3G HSPA+), or 3G (for both HSPA and HSPA+) and 4G (4G LTE). Some display LTE for LTE. Almost certain CM based ROMs display 4G for LTE.

With Rogers you have GSM (2G network with god aweful slow EDGA data out in the sticks), HSPA & HSPA+ (3G in urban/suburban areas, I think all HSPA sites have been updated to HSPA+), and LTE (4G, only in some larger metro areas).

In terms of speed, the download ballpark is

HSPA - 5-8 Mbps

HSPA+ - 12-15 Mbps

LTE - 25-30 Mbps

Theoretical speeds are much faster but us mere mortals are never going to see them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sykotyk:
thank you for prompt reply

I guess my un easy feeling for loading this specific rom I am looking at is because the dev has a section for the new version of his rom, new gapps to go with it, and a section for canadian user with specific files for each baseband that he said needed to be flashed with odin through PDA if im not mistaken. Just wanted to put my mind at rest. Did a titanium backup and nandroid so I guess I'll give it a shot today after work. Hopefully you will see me here with smiley faces and not stressed out figuring out what I did wrong. Thanks again. You as well bjtheone for clarification.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bruce Lee:
You can try transferring stuff from an micro SD card from either phone to phone or phone computer to phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
This post isn't 100% accurate.

First off, it is in your best interest to update the bootloader on your phone. Cyanogenmod and other roms that use a CM base require you have the latest bootloader installed on your phone or it won't let you flash their ROMs. This was implimented because old bootloaders were causing phones to randomly reboot. This forces everyone to be on the same page and allows for a much more stable phone for everyone. So yes, there is every reason in the world to update your bootloader. This can be done by allowing Keis to update to the latest stock release (LK4) or by finding the ODIN flashable bootloaders that are floating around here in the forums.

2nd of all, LK4 can be the baseband OR bootloader. When a stock update is released there are many things that get updated including your bootloader and baseband. Both will share the "version" number as they were released as part of the same package so yes LK4 is the baseband but it is also the bootloader. Updating (or downgrading) your baseband will not reflash your bootloader. They are completely independent of each other and it is entirely possible that each can have it's own release date on your phone if you've flashed other modems. Do not assume because your modem is release XXX that your baseband is the same.

Just so everyone is clear baseband, radio and modem are all the same thing. They are basically what handles all the radio related activities in your phone such as WIFI, GPS and Cellular connections. They are easily flashable through TWRP or CWM and for the most part really don't differ from one to the next.

Bootloaders on the other hand are a lot more work to upgrade and if not done correctly can easily brick your phone. It basically tells your phone to do when you press the power button. They are completely 100% different than the baseband though they do share the same version number.

---------- Post added at 02:45 PM ---------- Previous post was at 02:24 PM ----------

The OP for the Rom likely had a section for bootloaders not basebands.

I, and I'm sure most would agree, that you should always follow the recommended steps by a ROMs owner when flashing a ROM. If they tell you to update the bootloader through ODIN, then you should do that or their ROM won't install correctly. It's mentioned for a reason.

Rule number one should always be read and follow the instructions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
LK4 Is most current Rogers baseband/bootloader, so advice to update depends on version on phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
LK4 is the most current baseband for all Canadian (I747M) variants of this phone. Not just Rogers. Even if you have an AT&T version, you are highly recommended to update to the latest release for that phone (LK3). Of if you live in Puerto Rico, update to the latest for that one which is LL1.

I understand different versions of the phone have different releases but updating to the latest bootloader has nothing to do with version of the phone. We all use the same ROMS and there are asserts in most if not all CM based ROMS now that check to make sure you have the latest bootloader on your phone no matter what version you have.

It is highly recommended and almost mandatory with the asserts being added that you run the latest bootloader. Independant of what version you have. Just make sure you flash the correct one for your version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sykotyk:
Me being on jb 4.1.1 and the aokp I want to flash to is 4.2.2.. I am no genius but assuming is why a bootloader update would be required?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I mentioned it in my first post but I'll elaborate a little more.

A few months ago some folks running AOSP based ROMs on the I747 phone were getting numerous completely random rebooting of their phone. The smart people over at Cyanogenmod discovered that users who were not running the latest bootloader on their phone were the ones who were seeing the random reboots. I had the latest bootloader from day 1 so I never saw any of the random reboots that others were seeing and once everyone flashed the latest for their version of phone, all the random reboot issues went away across the entire XDA scene.

They have added what is called an assert to their flash script which checks the bootloader on your phone before doing anything else. If you have the latest bootloader on your phone (LK4 for Canadian users, LK3 for AT&T and LL1 for users in Puerto Rico) the ROM will proceed to flash itself. If however you do not have the latest bootloader on your phone you will get an assert error, you will be kicked out of the flashing process and you will not be able to flash their ROM without updating the bootloader first (or modifying the script but I don't recommend doing this). This is to make sure everyone is on the same page and so they don't have to deal with people complaining about their phones rebooting when the issue has already been resolved (update bootloader)

So with that being said, you are going to be very limited with the amount of AOSP ROMs you can flash if you do not have the updated bootloader. Most AOSP use the same base and this assert will be included in pretty much all of them. If you want to run TW Roms than none of this even applies.

So that's why you want to update your bootloader. Don't do it and you won't be able to flash the latest and greatest ROM releases. Trust me for the little amount of time it takes, just do it.

Have you even verified what bootloader you actually have on your phone? It may not even be an issue for you if you already have LK4 installed. There are apps in the market such as Android Info that will easily tell you what bootloader you have installed.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sykotyk:
I freakin love you. Yes I have Lk4 and the bootloaders the dev has on his page are for people that havent updated to that yet (such as the ones that were running possibly his old version of rom). Ughh... I was just complicating this for myself but thank you for shining light on my noobness. Much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Any time buddy.

What bootloaders people have on their phone are 99% accurate to whatever the last stock version of firmware they had on their phone was. If you updated to the latest official release through KIES on your phone before taking the custom ROM adventure then you are good. If you've had your phone for a while and the last official firmware update you did was last summer lets say, you most certainly don't have the latest and greatest.

That being said, there are ODIN flashable files out there now that will just replace the bootloader and some other pieces of firmware saving the user a trip back to stock to update via KIES.

So that's the story of the bootloaders and why having the latest for your version is a must if you want to play around here. You have the latest so flash away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sykotyk:
I'd hate to bug you guys again but am at work and searching forums while boss is out of office. Tried flashing rom but failed (assuming because the rom is d2att and im d2can and i have to delete the check it preforms in the beginning) getting fail /status 7 it says assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att" e:Error in /sdcard/aokp_d2att_nightly_2013-06-15.zip . Trying to restore nandroid and it failed while restoring data.Guessing i now need odin to atleast be able to use my phone again. Quick search on youtube i found something about when flashing the new rom to open some file put it into txt format, and delete some lines that involve some sort of "check" on start up. I've been told to stop worrying and flash because i should be good, but I guess i probably didn't explain my situations properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Are you using TWRP or CWM?

I'd recommend flashing the d2att version of TWRP instead of d2can version. If you used the Goo.im app to install open script recovery the first time around it likely installed the d2can version. I'd recommend getting the d2att version from the TWRP website and flashing it instead. Yes you are flashing a d2att ROM but all roms even for the I747M are considered d2att ROMs. There technically aren't any "d2can" labelled AOSP roms out there. They are all called d2att and us canadian users flash them.

What failed while you were restoring your nandroid? Perhaps try it again?

If you can get your phone running again, go to the TWRP site, download the recovery image method (.img file) and use terminal emulator on your phone (download from market if you don't have it on your phone) to type in the commands it lists. This will install the d2att recovery on your phone.

EDIT! Now that I think about it, you shouldn't have to nandroid back to anything. When you attempted to flash that nightly, it didn't flash anything before it kicked you out. The phone should still be in the same state it was before you attempted it. Just try to boot normally. Unless of course you did a factory reset/wipe before installing.......then you are likely screwed and have to go back to ODIN. In that case, use the ODIN version of TWRP d2att to install it, then you should be good to go to install the nightly you are currently trying to install.

Hope all this makes sense.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I second flexfulton. That's what I did on my d2can, running d2att recovery since day one after realizing they're both identical and no one specifically develops for d2can. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sykotyk:
If you have a cause I. good sir, would like to donate to this.

So being on cwm now, just follow same steps in odin and flash TWRP "over" the CWM. No need to wipe anything first. This flashable will just overwrite what is existing im assuming. The same if i were to just be updating TWRP or CWM. Just use odin to flash over what is on phone now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
No cause. Thank you though. Save your money or donate to the great developers around here who actually make all of this possible.

Yes just follow the steps indicated on the TWRP website to flash the d2att version of TWRP right over CWM and you will be good to go.

No need to wipe anything as wiping dalivk/cache and a factory reset won't touch anything recovery related anyway.

Once you get TWRP installed however, I'd recommend doing a factory reset before flashing the AOKP rom you want to try out or you might get a hang up at first boot. If you forget and DO get the hangup on the Samsung logo, just boot back into recovery with the three button trick and factory reset then and you should be good to go. I'd avoid an internal storage reset as that will wipe all photos on your phone as well as downloads including the ROM you eventually want to flash. Just stick with what TWRP calls the factory reset and you will be good to go.

Once you finally do get up and running the first time, there is great debate around here as to what is required for wiping before installing a new update for whatever ROM you are running. I dirty flash every CM nightly wiping only dalvik and cache and never have any problems. If you do however have a problem, it's common practice to do a factory reset and reinstall the ROM to see if the problem still presists before bringing it up on the forums. As for how to and the best way to back up your stuff before doing a factory reset is another debate in itself which we will also save for another day.

Also you may not know but if your phone ever does hang up, you don't have to pull the battery. You can just hold the home button and the power button for about 5 seconds and your phone will reboot itself. A good little bit of information that I don't believe it widely known. Really helps when you have a pain in the a$$ to remove case such as an Otterbox on your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kayone73:
Thanks for discussing this, I wanted to ask: Is it possible when first rooting a new SGIII with stock ROM, to install TWRP right off the bat and avoid doing the whole Odin/CWM recovery installation thing?

Or do I have to follow the basic procedure that's in all the existing tutorials? (Odin -> CWM install -> flash team epic root zip -> dl goomanager -> install TWRP)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Just replace TWRP with CWM when you talk about doing the whole Odin/CWM recovery installation.

I've only done the process once. I installed a root injected stock rom (doesn't really matter which carrier). Then used ODIN to flash TWRP instead of CWM like some threads suggest and I was good to go. I'd recommend doing a nandroid of your stock root image incase you ever need to go back and then flash away.

If you are on an M variant of this phone I recommend against using goomanager to install TWRP your first time. It will see you have a "d2can" and install that recovery then you will have the same issues as the guy above. Instead use ODIN method and d2att TWRP files to install.

Everything you need is here. http://xdaforums.com/showthread.php?t=1739426 Just follow the instructions to flash TWRP instead of CWM, make sure you get the d2att recovery and don't use GOO to install the recovery as he says you can do if you are on a canadian variant of the phone for reasons listed above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eduardo_b:
You can use autoroot: http://xdaforums.com/showthread.php?t=1963790 and then install TWRP. I use CWM on five devices (most with Touch CWM) with absolutely no issues, but it's basically irrelevant which one you choose when it comes to recovery functions. Flashing one recovery over an existing one works fine.