yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xCAVEMANx:
Correction NO OTA

I had flashed back to root stock ICS on accident...then I flashed root stock JB (DLK3 4.1.1) After boot up on ICS I was notified their was an update. I ignored because I knew I had flashed the ICS and I was just going to flash the JB version. After JB boot up I was notified there was an update. I accepted and after a lengthy 387 MB download it reset and lo and behold...nothing updated. MEH :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
If you're happy with just root then flashing a rooted stock image will not trip your counter and you have nothing to worry about.

If or when you decide to flash a custom recovery and rom, you can do it many different ways. Keep in mind there is an app called triangle away which resets your flash counter so I personally don't worry about tripping the counter.

For my custom recovery I downloaded goo manager from the play store and installed twrp recovery which I prefer over cwm. That is probably the easiest way IMO.

I've already had to bring my phone in to repair the bluetooth and I simply ran triangle away, reflashed the stock no root image and did a factory reset and was fine so I don't think twice now about the flash counter.

Hope that helped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Longstreet:
Rooted last night, using the method in the OP. Worked slicker than snot on a glass doorknob.

That does help, thank you.

I have the thread for Triangle Away bookmarked, and plan to read through it when I'm done with this one. But the big red warning

made me want to stay away from Triangle Away until I knew more about it (I don't even know what a USB jig is). Glad to know it works that well and reliably.

I'm going to leave my phone as is for now, though as I say I'm sure I'll get the "new ROM itch" soon enough.

Thanks again for the help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DXP2:
Excellent guide.

Thanks a lot:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vampir4997:
Whats the big deal with the flash counter? Sorry i dont own a samsung device i am asking because i am rooting an s3 for a freind this weekend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chromium:
if its it more than 0, and you try to return it to samsung for warranty, they wont take it because they know that you modified it by flashing something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vampir4997:
Ok,so it wont hurt it though? I guess i mean you can still flash all you want and its not gonna,say lock up because the counter is at a certain nukber or anything? Ty,like i said im not a sammy guy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
No it won't hurt it. Mine is constantly at 1. If I ever have to send it in for repairs, I just use triangle away to reset it back to 0, and flash back to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chromium:
Ya mine is at 1 constantly as we'll, even when I flash something through twrp.

I actually heard somewhere that the warranty only gets ruined if the counter is more than 1, rather than 0.

Anyone know if this is true?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Maybe if it's a warranty through your carrier, that's a possibility but not through samsung. I had a horrible experience dealing with Samsung directly regarding my warranty. I actually swore I would never buy a Samsung device ever again afterwards. Their customer service is absolutely horrendous. You will get 5 different answers from 4 different people about one question. Then when you actually find out the truth, it turns out that everyone was wrong.

Anyone who opens the phone who is not a licensed samsung service tech voids the manufacturer warranty.

Any non samsung software flashed voids the manufacturer warranty.

Manufacturer Warranties are non transferable. In fact if I bought a brand new Samsung phone from an authorized retailer, turned around and sold it to the person standing next to me, unopened not even touched, the warranty is technically void.

After being screwed around for days by Samsung I got fed up and brought my phone to a phone service tech who fixed my issue for 20 bucks. Had my phone back in less than a week. Samsung would have had the phone for up to 3 weeks.

If everything works on your Samsung phone you will love it. If you have any issues, dealing with Samsung directly will be a nightmare.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
+1, will never buy Samsung. Horrible customer care, unfriendly company
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
No **** if a non Samsung tech opens the phone the warranty is void. Why would you think otherwise?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
I never thought otherwise. I always knew that was their policy. But since you mentioned it, one of samsungs customer service representatives told me a phone service store CAN open the phone and service the hardware, so long as they don't touch the software. I told him he was wrong. He insisted he was right. I told him to check with his supervisor. Sure enough he came back and apologized for the misinformation. That was only one of the pieces of misinformation samsung customer service fed me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KeeperOfThePizza:
Mkay so, I just flash the stock rooted rom via odin then go to playstore, install clockworkmod flash the recovery via the app and boom bamm done?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
That's about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
GooManager reports that there are no recoveries for my d2att... I just got this replacement S3 today and rooted it. Rom Manager finds no recoveries for it either. Says device is unsupported... but it is a d2att!

Do you know what I'm doing wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
I've found that Rom Manager won't find any recoveries for the S3 unless you're running something other than stock. When I was running CM10, it would find the phone model and recoveries no problem, but on stock the phone doesn't exist. Not sure why.

Grab the recovery from the rom manager website (http://clockworkmod.com/rommanager), and manually install it.

Look for Samsung Galaxy S3 (AT&T). Grab either normal or touch and save the .img to your PC. Rename it to recovery.img and copy it to the root of your onboard sd (not external).

Then fire up the terminal

type su and grant super user access

then type the following dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18

Once that's done, reboot in to recovery and it should be updated to 6.0.2.8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Thanks. I did get Clockworkmod loaded, but I perfer TWRP, which will not load... even though Clockworkmod is. I never had this problem with TWRP before. I guess I'll have to download and install it manually instead of using the script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
Why don't you just use ODIN to flash TWRP onto your phone? The OP has an ODIN flashable version of TWRP at the end of the main post. The longest process is downloading ODIN if you don't have it as well as TWRP. Once you open ODIN and select the recovery, it takes seconds and it is done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ztrike:
Thank you for the work done here in this post, I have a question do you simply has the modem for DLK3 because "CWM Flashable ATT UCDLK3 Modem - modem_CWM_I747UCDLK3.zip" it is like flashing the whole rom again I just want the UCDLK3 modem, please let me know if you could upload or give me a link, sorry if this has been already asked. thank you for your support.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Not sure why you think that is a whole rom. That is just the modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ~wolverine~:
Well I'm gonna ask a stupid question here. If I flash this for ATT stock will it be exactly like I have now only rooted? I would like to keep all the Samsung apps and touchwiz. I don't want to lose anything just gain root. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jthrasher47:
That is exactly what you get all mr Robinson hasdone here is for body do you a root system
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Yup, you can pick either pure stock, or stock w/root injected. You can even flash a ROM for a different carrier, if you wanted to see how the other side lives. You might even get lucky and get NO carrier apps at all like I did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DKaine:
Rather bizarre problem here

Let me first say, excellent information, and it all makes a lot of sense. I am coming from a Nexus S, without any external storage to the SGS3 with a 32gb ext and 16gb int... I don't know what to do with all the space! :rolleyes:

So as the title states, I have a rather bizarre problem that I've encountered.... I followed all the steps as posted, got the root-injected stock ROM installed just fine and dandy. Was able to update binaries on SuperSU, install ROM Manager/ROM Toolbox, etc... Phone seems to be working just great, and then I move on to the next step.

What is causing me some problems is when I try to flash a custom recovery. I've tried flashing CWM (touch and non), both through ROM Manager, as well as through adb shell, and when I reboot into recovery it won't leave recovery... I can't boot into the regular OS anymore. The only way I've found to get back into the OS is if I go through the beginning steps of ODIN and flashing the root-injected stock ROM again, but this wipes the recovery.

So do any of you fine folks have any idea what could be causing this?! I just got the phone yesterday, and I really want to play with it already. :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Where are you getting CWM from? I've never had any issues flashing CWM to my SGS3 via Odin. I've never done it through the ROM manager, always ODIN. Here is the recovery file I've always used to flash via ODIN, and I've never had any issues with it. Then grab the latest CWM recovery from here. Search for Samsung Galaxy S3 (AT&T) to grab the latest recovery or touch recovery img. Rename the file to recovery.img and copy it to the root of your INTERNAL SD, then follow the below instructions to flash the updated recovery image.

Once that's done, you're set.

1. Open Terminal

2. Type su

3. Type shell@android:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18

It should say:

14004+0 records in

14004+0 records out

7170048 bytes transferred in 1.430 secs (5014019 bytes/sec)

Then to test, type reboot recovery and press enter. You'll boot in to recovery. Now you can keep stock w/root, or flash another ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
You can use the method as stated above, or you can use twrp which is my preference. I just downloaded goo manager from the play store and installed the recovery from the app. Done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DKaine:
I'm actually getting the CWM recovery image directly from http://www.clockworkmod.com/rommanager, and replacing the stock recovery with CWM through adb shell, I have also used Terminal on the phone as well as just installing ROM Manager and flashing through the app. I have not used ODIN to flash any recovery. Did I miss that step in the initial post?

I guess I'm going to flash with ODIN the root-injected stock, and then the recovery as well. Then go from there.

Of course I'm currently stuck in CWM at the moment, so starting from scratch again. D'oh.

Thanks for the ideas.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KentuckyHouse:
I'm going to ask a really stupid question (I admit that up front), but bear with me...:D

Is there a file out there that's flashable through TWRP or CWM for this stock rooted ROM? Maybe I missed it, but the OP seems to only have files that can be flashed through Odin.

Right now I'm on Task's AOKP and I'd like to flash back to stock rooted and make a nandroid of it, just to have a clean install. I do already have a stock rooted nandroid, but there were some funny things going on before I switched to AOKP.

If someone could point me in the right direction, I'd appreciate it very much. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Ah. Ya, from my experience, it's best to do an initial flash w/Odin then once everything's working properly there, with CWM flashed successfully, then you can xfer the recovery.img to update the recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DKaine:
I downloaded the most recent CWM image from clockworkmod.com/rommanager website

Then, I ran the dd command, after running the su command in adb shell.

I get this:

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
11040+0 records in
11040+0 records out
5652480 bytes transferred in 1.091 secs (5181008 bytes/sec)

course this is running as root due to the su command.

I did flash everything else as you mentioned and it seemed to work. When I saw the above instead of

14004+0 records in
14004+0 records out
7170048 bytes transferred in 1.430 secs (5014019 bytes/sec)

I didn't bother rebooting and just reflashed from within ROM Manager, keeping the most recent 6.0.2.8 for SGS3.

I'm not sure if there's a size discrepancy for a reason, or there's something I'm doing wrong... Which is infuriating, because I'm no stranger to Linux or the command line... Any ideas why this could be? Oh, I should mention, I did use the CWM Touch version, could that be the reason?

Thanks,

DKaine

:fingers-crossed: At least the phone seems to be working for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
Yes if you look i was using a 5.8 version. So it was just an example. Newer versions or other recoveries will have different sizes so that is all you saw there. Everything looks good though so nothing to worry about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rockstad:
so this is my first go at the s3, i downloaded the root66.7z I honestly dont know what to do with it, clicking it opens something and prompts for a password, i dont know how to extract it..any info would be appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Did you read any of the instructions?

Can you try again, and get some exact error messages? I don't think any of the files that Op has posted require passwords, and if they do, it should be posted in the first couple of messages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rockstad:
I read them all. I'm familiar within Odin. The file in the first post for at&t jb 4.1.1 once downloaded it is an application or something of the sort, not an Odin flashable file
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Grab 7Zip and install it. use that to open the .7z file. Extract the contents to it's own folder. Then in Odin click on the PDA button, open the folder that you extracted the contents of the .7z file to, and select the only file that displays.

Make sure your phone is in download mode and connected to the PC, and that COM0 shows up (usually it's COM0, sometimes it's COM1). Click Start and wait for the magic to happen.

Once it's done, phone will reboot, update will finish installing and you'll be set.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DXP2:
I'm beginning to think I am the only one on this section of xda that uses Winrar rather than 7zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
I find that 7zip is a nicer program, smaller and doesn't harass you to buy it. I think that it opens more than winrar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Herox:
I just got a refurb SG3 today and I also am a winrar lover.

Thanks for the tutorial.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uzii305:
Ok guys i think im bricked. I need immediate help please.

Ok heres what happened. i was rooted running a 4.2.2 rom(Tasks). I went to flash an update. I did the usual. Factory reset, wipe cache, wipe dalvik, and wipe system. I flashed the ROM, then my phone wouldnt boot. I then tried to reload a TWRP backup. The phone still wouldnt boot. Recovery didnt show any errors or nothing. I went to odin, downloaded the lastest jelly bean att stock rom, flashed through odin, and my phone still wont boot. It is stuck on the Samsung Galaxy SIII screen. i Downloaded the lastest samsung USB drivers from this thread, and im using stock usb cable. Im at a loss. Any help would be greatly appreciated. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
After flashing back to stock w/Odin, try booting in to recovery and performing a wipe of data and cache. Then reboot again. If the two touch buttons at the bottom light up after a few seconds to a few minutes then phone is booting up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uzii305:
Ok ill try that. Its on stock recovery, will it still allow me to wipe data and cache??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Absolutely. It's built in to stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uzii305:
This Worked man, thanks for your quick response. In the words of the great Carlitos Way (Al Pacino), "If you was a broad, i'd marry you". Thank again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Can I odin the Rogers file onto an AT&T i747?

If I download the file for Rogers and use Odin to put it on my i747, will it cause any problems? Reason I ask is because I like the ability to turn off LTE, which AT&T rom does not have.

I read somewhere that using Odin to flash the Rogers system image onto an i747 might cause me to lose my IMEI. Can anybody confirm?

If flashing the Rogers file using Odin is not a good way to get the Rogers ROM onto my i747, what is?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
I don't think that there will be any issues. My phone is from Bell, and I've flashed a Rogers rom w/o issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Flashing an I747M firmware onto an I747 will cause problems, most likely the loss of your imei. There could be other problems as well

Flashing a Bell Rom to a Rogers device isn't as big a deal because both devices are an i747M.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
Issues

HI...i dont know if i did something wrong....i followed everything exactly as was said....i just wanted root with the stock rom...followed all the steps but when my phone rebooted and everything i do not have root....so i am confused as to what i may have done wrong....any suggestions? I am running the stock 4.1.1 jellybean on Sasktel....i used odin and put on the root injected rom and i still have no root access...im soo confused lol :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
What is the filename of the ROM you flashed to your phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Night_1:
Sorry for the delay in this message...i have never rooted a phone before and apparently after the tenth flash i said screw it and then when i installed an app it asked if i wanted to grant or deny root access...superSU...so i did everything right...just inexpereince and not a clue about phones...so...apparently it works...was my own stupidity lol....thanks for the reply though :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
No problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dvazriel:
Since flashing a custom recovery trips the counter with the new JB versions, can I flash the old ICS version with Odin, then use goo manager to flash a custom recovery without tripping the counter? I will be using a custom ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TrainAss:
Flashing ANY recovery but stock will trip the counter. The counter indicates how many times you've flashed a custom recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dvazriel:
From the OP:

Third, (optional)

On JellyBean versions

, flashing a custom recovery will trip your counter no matter the method used.

Reason i want to ask / confirm is because I rooted by phone using this method back in October of last year, and only the ICS rom (4.0.4) was available. I installed TWRP via goo manager then flashed MIUI.

Yesterday, i had to send my phone back for repair ( sound chip died ). I put the phone in download mode to flash stock back, and to my surprise it didn't show any counter. It was listed as stock.

I don't recall doing anything extra to reset the counter. I just to want to confirm for when i get my phone back so i can do it again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrRobinson:
That was ICS. Now on jb flashing any custom recovery will trip it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dvazriel:
Right, that's what i am trying to get at. If I Odin the old ICS rooted stock, then install a custom recovery without upgrading to JB, it should not trip the counter, yes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheScaryOne:
Yes. Precisely. If you don't want to trip your counter, simply install the injected ICS rom with Odin, then install CWM or TWRP with adb. This should be added to the front page to clear up the confusion.

Note: ATT will bug you to get on wifi so they can force you into JB. Don't enable wifi until you have a custom recovery flashed.

And I know because I softbricked my phone tonight, and had to reflash from download mode using Odin and didn't want to trip the counter. I used the ICS root-injected rom, and still show No under the "Custom Binary Download" field in download mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dvazriel:
Don't have my phone to try, but you should be able to do all that wihout using you SIM no? You should be able to connect to wifi without been pushed the JB upgrade?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
If you have the rooted ics Rom installed, there's no need to use adb for recovery installation. Goo manager will install twrp and I've heard Rom manager will install cwm. Attempting to use adb could brick your phone if you push the recovery file to the wrong block.

And even if you get prompted to upgrade, you can postpone it up to 24hrs before it installs automatically (unless something has changed).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheScaryOne:
Yea, but then I'd have to log in, two step verify, blah blah blah.

I could ADB as soon as I turned on debugging in the developer menu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TTboy404:
Just to calrify for Att

this

First download the stock odin tar that has a rooted system image injected into it:

ATT Image

Current I747UCDLK3 (JB 4.1.1) - NEW JellyBean

Mirror 1: Download root66_ATT_I747UCDLK3.7z

Mirror 2: Download root66_ATT_I747UCDLK3.7z

Is just the stock, Only rooted Stock.JB. No custom recovery.

However if you have the ATT model (not sure if this will work on Bell, Telus, Rogers, etc.), this recovery will see the extSdCard and seems better for our devices:

For ATT models use either this recovery or this touch recovery.

connect your phone to computer and use adb

type adb shell

once in the shell run su

then

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18

Just trying to be clear on this.

I had a problem when I flashes a ROM. When i originally rooted my phone, it was rooted some how thru a VZW build or file. But once i loaded a different ROM, my phone thought it was VZW (even my computer then said it was a different phone than my SGH i747 or Att). But my rom was for an ATT. Needless to say, I am getting SMS from Verizon, and crap. And I am not even a VZW customer. Made a big mess of the whole thing.

It appears the Root66, have the verizon base root, and need the custom recovery install as n the second step, with the dd if=/sdcard/recovery blah blah blah to make less complicated to flash later on...

The other thing, do I need to worry about losing my IMEI anymore? Or has that issue basically being adverted when they write the newer ROMS now?

Anybody made an Odin Flashable tar of the ATT custom recovery, you know to make this even easier? :fingers-crossed:

Thanks