yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Okay... I'm unclear exactly what your intentions are here with the device, so I'll cover all the bases.

1) You can most likely change the device hardware out and put the hardware for an i9300 into an i747 housing. I couldn't find info that said either way, but it seems a reasonable assumption... and safe to try.

2) This is the part you do NOT want to try unless you'd like a hardbrick... You canNOT flash firmware,custom ROMS, or a system restore designed for an i747 to an i9300 (no matter what housing it is in) and expect the device to power up... because it won't. They have different processors for one huge thing, plus firmware just doesn't work that way.

ATT and TMO are all but identical, and they'll not interchange either (without porting, but that could go unsaid).

You could use the i9300 though. I think a few had 64gb internal storage even, which is pretty awesome. You won't get 4g/LTE speed though. I believe it'd be 2g if you're on ATT sim. Is the i747 hardbricked? If not, we can try to help you recover it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
Yes, d2lte. I flashed TWRP via odin and Philz from recovery. After flashing, i tried to get to recovery using the buttons combination, but after first logo, phone did boot to system. After TWRP i used command prompt to boot into recovery and after Philz i used an app from play store. Both time I ended up soft brick.

It happened to me once to flash a new version of twrp on nexus and to end up in bootloop. The problem was twrp version, because after flashing a different one i had no more problems. This time i thought it same, wrong version, but because it was happening 3 times, makes me wonder if the problem doesn't reside from hw.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Each time you flash TWRP or Philz the phone won't boot to the desktop or it doesn't boot to the custom recovery you just installed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
That is unusual... To echo [MENTION=1865934]audit[/MENTION], are you able to boot to system and only softbricked when booting to recovery. If the device is looping and repeatedly and only trying to go to recovery, pull the battery, depress volume up & down plus power for about 15 seconds with the battery removed. Reinstall battery then try to boot to system. I'm gong to check a few things for you, reply if you get to system or already could.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Unfortunately, you have an S3 with a locked bootloader. I knew the symptoms were just like what you'd get with it, but I checked as I've never had an S3 with over version 4.1.2 Android to be sure, and I'm not an expert with the i747m, but that seems to be the only thing that fits. It should have hit me, but I just didn't think about it til today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
maybe i'm wrong but i thought all s3's came with unlocked bootloaders ?!

"all i can really do , is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Don't feel bad lol... I did also until g33k described his symptoms, and I know those all too well from working on unlocking this device... An S4. I checked just to be sure. Back when the S3 debuted with ICS 4.0.4 and thru KitKat, one site said 4.3 JB, they actually had roughly the same bootloaders since the one released with 4.1.1 or UCDLK3 with the ATT Version.. I'm not sure of its carrier corronsponding versions, but you get the idea. Just like every other KitKat bootloader though it apparently is unable to use AOSP ROMS or use custom recovery flashed to the Recovery partition. If I'm mistaken, and this applies only to ATT and VZW, feel free to correct me. I never claim to know everything :) All three of my S3's are SGH-I747 ATT variants running CM 10.0 to take advantage of swapping the microSD with internal storage to create a 128GB internal storage device for my two young sons for games. They were 64GB before that... Never let it be said Samsung uses anything but amazing card readers, because they've been at it for literally years. Point is that I was rooted long ago and never took a single OTA. no reason to upgrade CM version either. I was 'trying' to break from bootloader locks and just help a few ppl with a few more simple issues to clear my head, and maybe gain a fresh insight, because I've hit a bit of a brick wall. Very odd that I'd happen across this thread.

Just one of many threads here to check out http://xdaforums.com/galaxy-s3-verizon/general/galaxy-s3-kitkat-boot-loader-unlock-t2836238 There are quite a few... A pity that Samsung feels the need to force everyone to pay for the development of security software for corp and gov contracts. How much would a Knox device cost like an S6 Edge, if that wernt the truth? I want a Google Play Edition to the future S7... LoL, I'm one to talk though being I own one of the devices with Knox and unrooted just for work purposes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
It won't matter. There isn't currently a way past the KitKat locked bootloader. I have one also on my i337 S4. Forum search safestrap and see if version 3.72 I believe works on your device. Its based on twrp recovery, but it works different. If it doesn't work, search for i747m KitKat recovery or 4.4.2 recovery. You'll find what you need ;) including learning to use xda searches to navigate to the correct threads for help, but I'll gladly help if you search and aren't sure. It's always better to ask, especially where flashing is concerned. Unless you discover that the kernel you currently have is not rootable or no one ever got a root to work before a newer version was released though, you shouldn't need to flash anything really. If you're still running the same flash though that you were trying to get TWRP and Philz to work with though, it might be good to start fresh after you assert you have stock firmware with a kernel that can be root and start from scratch. Just use Odin and be sure it's a 4.4.2 stock firmware. As long as the kernel is similar enough, you'll be able to flash it even with the locked bootloader. Again, a quick forum search will yield the answer. You already know how to use Odin, so you'll be fine. I already gave you a solid root technique that won't trip Knox, and you were successful with it... Just do it again Your recovery is actually an app you set up. You'll need to go to security in settings, then check 'unknown sources' and install. Open it and select to 'install recovery' or something to that affect. It'll need root access of course. This is the only recovery you can currently use with the locked KitKat bootloader safely I am aware of. Again, if you need help, ask me or anyone in those threads, and many will offer assistance :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g33kos:
I didn't know that, I did press only the power with battery out.

Bootloader being locked never cross my mind. I read about some version of US samsung S3 having locked bootloader and I thought I'll not have that "luck", but it seems that if something can go wrong, then will definitely go wrong.

I'm preparing for vacation so I gave up playing around with my sister phone and I returned to her before making a brick out of it.:silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Olalaekan:
thankz

.... i wanted to know if i can use a i9300 board in sgh-i747 housing........ plus my sgh-i747 is hardbricked..... forced in a bootloader and that was it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
The internals of the i9300 and i747 look similar. If tou have the parts in-hand, you could give it a try. Removing the motherboard from an i747 is very easy.

Did you try the de-brick method of the i747?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Olalaekan:
... Couldnt lay my hands on a JTAG..... (current location: NIGERIA)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Do you have ALL the internals for the i9300? If memory serves me, the i9300 uses an Exynos quad core processor with 1 GB RAM and s limited to 4G/HSPA. It also has 16/32/64GB Internal storage. The i747 components are very different. You've never clarified what your wanting. If you only need the plastic housing to hold the i9300 internals, that's fine. Take a look to see if the screws are in the right places. I'm not an i9300 know it all, but I saw a video on YouTube and that board is a different shape than mine in the i747. I'm not sure if the camera can be changed out. Remember, this is firmware. Its like software, compare to Windows. Windows literally has or can download drivers or files to support any PC you install it to. Its huge though. Firmware is a barebones compared to Software. It has exactly what it needs to run a specific layout of hardware. Only certain devices its literally created for. It can't adapt or detect anything different. Firmware is small and good for mobile devices. This is from memory, the was the camera and a small 'cover'which was a board clipped on my i747 when I had to dry it out once. I really recommend you be certain you have the original hardware, like the camera. Even if he megapixels are the same,I'm not sure its the exact same camera and with firmware it has to match up exactly. You should try to unbrick the i747. Will the device power up? Where are you at and can you access the bootloader? S3 's aren't usually too bad to recover. There are great forums to help you. With the i9300, if you have all the internals and you flash a ROM designed for the i9300, it should work. I'm sorry if I'm over explainng, but I think Ive assumed everyone knows how to do these things, so I'm explaining to try to be more helpful to ppl like you.

---------- Post added at 11:31 AM ---------- Previous post was at 11:22 AM ----------

I was mistaken here.... He has all the symptoms of being locked. It may be that he isn't flashing properly though. The VZW is the only S3 with locked bootloaders. If g33k is flashing right though, I'm pretty stumped on the issue. He needs to assert the has i747m recovery and not i747, it has to be some issue with his flash. You can forum search the VZW S3 bootloader. I saw threads that looked like unlocks for it. I actually need to look at those. I'm kind of stumped on a project I've had for almost 10 months. I'm trying to look backwards to maybe get an idea of what I'm missing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theredbaron1834:
Can someone tell me how to get NFC's tap and pay thing to work? I have tried searching, etc, and saw some posts talking about using a Touchwiz rom, but I can't get any of them to boot. I also saw one saying something about a Paranoid rom, but I couldn't find any for the my S3 ATT.

I would prefer to get it to work with Cyanogenmod, but anything would do. I just can't find out how.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Can I turn my phone on if I smashed it to a million pieces in a blended, then microwaved it?

;)

Nah, but seriously, does anyone have trouble with large aftermarket batteries not charging properly? I.e. charging to 100 but almost imidiatly dropping to below 60.

Charging overnight and not reaching 100% even with several different chargers. This is battery #3 from the same company (LAZA 4200 mAh for galaxy s3)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcrue69:
Noob question. I rooted my phone. Changed to slimkat 9.0. Got upgrade to MJ2. Now it shows I have no root access. I am unable to use a PC, and I am unsure what root app I used to gain access before. Can someone please point me I the appropriate direction?

Also, I have the newest cwm recovery. I am trying to upgrade my bootloader and modem. Again, I have no access to a pc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcrue69:
As a note. Flashify indicates I have root access, everything else I have tried says otherwise. And how can I check to see if my boot loader is unlocked?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
If you're on d2att/d2can they have never had a locked bootloader. There are some bootloaders since Samsung Knox that can't be downgraded, but they are not locked. You are free to run any unsigned binaries you want.

If you're on Slimkat then you are rooted, you just need to enable it. Go into Settings -> About and tap on build number about 8 or 10 times. That will enable Developer settings. Now go into Developer settings and you can turn on root access. This is how most AOSP ROMs that don't package SuperSU with the ROM work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Did you go to developer options and enable root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcrue69:
Yes, it was already checked for app and adb. But everything I try says no root access. I'm still very new to this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
lol... funny... I used to have that exact battery back when I used an S3 still. I never had that issue at all. It was actually very quick charging. I used an Anker multi USB charger for it and some other devices and a standard cable. The charger is a smart charger that detects the right voltage for the devices. Very nice, you might try that, or it might be a weak battery. Laza has a great warranty for replacement. You can contact them thru Amazon and send a message. I assume that's where you got the battery. Might look into a charger also though. Theyre handy no matter what.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
You could get a TWRP/CWM flashable SuperSU zip and flash that in your recovery. It should take over for the ROM's built-in root manager if that's not working right for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
If you have recovery installed, but lost root, just reboot device to recovery. Under advanced itll have an option to reroot the device I believe, and CWM checks system for root access when you exit and will prompt you to root the device. The i747 doesn't have a locked bootloader and just be very sure you want to upgrade the bootloader, because you cant go back once you do. KK isn't the greatest lol... Id keep going with JB, but that's your call to make :) You sound like you need to really read a lot before you go flashing bootloaders though... no offence. Flashing bootloaders is pretty high risk if youre unsure what youre doing. Be sure to have everything youll possibly need ahead of time and make a nandroid backup right before. Also having the rom and gapps youll be going to, after flashing bootloader, already on your microSD is a good idea. Good luck and hope this helps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcrue69:
I currently have slimkat.9.0, which I do enjoy very much. Just have a terrible battery drain issue. But I'm looking at spirit 1.7. And maybe the allblackscreens . is there anything I should know or consider?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stunna946:
My device is softbricked i was running 4.2.2 before this happened what file do I need to download and where can I find this... Thanks In Advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcrue69:
Have you tried flashing from recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stunna946:
Sure what file?? -__________- I747UCDLK3_I747ATTDLK3_ATT I flash this i get hit with signature verification errors every rom i try flashing does this

---------- Post added at 03:00 PM ---------- Previous post was at 02:57 PM ----------

Is there a better program other than odin we can use.... Like Motorolla has rsd lite It Literally hard Flashes the rom to the phone none of this MD5 mess.. or am I using odin wrong? I really want to have a working phone this sucks. Samsung is a fail

ISSUE RESOLVED http://xdaforums.com/showthread.php?t=2549068&page=73 If you know what your doing and looking for this link will help anyone in the future with my problemo..... WOOOOOOOOOo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
Dude! Edit the screen shot with your IMEI! No one needs to know that, never post your serial number or IMEI... Its been there for days unfortunately.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stunna946:
fixed my problem:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gol101:
I have the:

i747 running 4.0.4 (icecreamsandwich)

one of the older firmware codes before knox (both my props match).

I have root and cwm already done and the rom for cyanogen 10 / the 4.1 store downloaded.

Do I have to update my firmware to 4.1.1 using odin or is there somewhere I could download cm 9 with the 4.0.4 marketplace?

tbh the only reason i'm flashing is in light of the recent certifi-gate exploit.

thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lt1streconbn:
I'm not clear on what you're asking... If you want Stock Firmware for 4.1.1 go to this link and create a free acct and you can search and download it for sgh-i747.

http://www.sammobile.com/firmwares

My best advice is to go to the following forum. I have all these files, but you can find tons of downloads for ROMS, Recovery, and detailed instructions on the SGH-I747... (Be certain to use files for the SGH-I747, NOT THE SGH-I747m. They're similar, but not interchangeable) If you hit any deadlinks for a file you need, reply to this, and I'll put up a download link for whatever you need. Be sure you have gapps for 4.1.1 before you install CM10;

[STICKY INDEX] AT&T GS III - I747 {/Root/ROMsTools}

http://xdaforums.com/showthread.php?t=1725839

If you're asking if you 'have to' upgrade the stock firmware to 4.1.1 first, in order to install CM10.0, I couldn't find any info searching that says you'd need to do that. I actually never done that particular change as I received an OTA a long time ago from ICS 4.0.4 to JB 4.1.1. if you want to be safe, just download the firmware and flash thru Odin, then reroot the device with CF Autoroot and then flash CM10.0 and gapps thru recovery and you'll be set. I'm positive that will be successful because I've done that several times. Be sure and keep that stock firmware locally. Sometimes a glitch can develop with the device and an easy fix is to just flash back to stock, reroot, then use TiBu to reinstall user apps and data.

****Be sure to create a backup thru recovery before you begin. That's the biggest mistake ppl make; not creating a backup and then something doesn't go right (md5 fails or a new user forgets to wipe cache and dalvik for examples). Recovery is a quick fix for a bootloop. If you read and follow the instructions on the forum I posted, you'll be just fine. That's an excellent place to learn about your device and find whatever you need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcrue69:
I am running slimkat 9.0 and the issue is when the phone is off. I have no battery charge indicator (just a fuzzy grey rectangle) nor led. I'd love the lollipop indicator. But any would be great. Any ideas ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
heres a dumbo question..

does the gs3 have to have both unlocked bootloaders and root to flash custom roms?

my other devices i have had needed both in order to flash custom roms.

hows this for a goofy question? ha ha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Flintlock:
That depends on the ROM. Before the gs3 bootloader was unlocked obviously none required it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
far as i know the S3 never has had locked bootloaders. bricked my first S3 running a "unlock bootloader" script.

"all i can really do , is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
Got this device from a friend to root..its the i747 android version 4.1.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Is the phone unlocked? If it isn't and the phone is running stock 4.1.1, you could use the free method to permanently unlock the phone.

[MENTION=5511100]mrrocketdog[/MENTION] is correct in that no version of the s3 bootloaders has ever been locked.

Easiest way to get root would be to install a custom recovery and flash supersu from recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
OK. Thanks. Im not new to rooting...just to the gs3(and all Samsung devices..lol) could I use max lees root method?

---------- Post added at 08:22 AM ---------- Previous post was at 08:21 AM ----------

Yea.. The device is purely stock..

---------- Post added at 08:26 AM ---------- Previous post was at 08:22 AM ----------

I have seen so many root methods...lots are different variants and branded devices. Want to make sure I know it all before modding this device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I understand your hesitation.

Here's what I would do: run OTA updates until the phone is running the latest ROM, bootloader, and modem. Then, I would install a custom recovery, flash supersu, create a nandroid backup, and fstart trying out custom ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
Ok would I use the Odin method as laid out in max lees method?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Do you have a link to the thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
Says it was interrupted. I got this though. Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
The root process was interrupted?

Also wanted to mention that rooting will prevent the phone from installing OTA updates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
No no. The ota was inrerupted.

---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------

http://galaxys3root.com/

---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------

Yea. I know rooting stops otas. ? I have rooted the HTC one xl, HTC inspire 4g,Motorola atrix HD and a couple jailbreaks.

---------- Post added at 09:21 AM ---------- Previous post was at 09:20 AM ----------

I could always manually flash the 4.4.2 update. Just figured I would root with it on 4.1.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Not sure why the OTA was interrupted.

The link in your post is the same method I recommended: install a custom recovery and flash supersu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
Tyvm. Sorry for all the dumb questions

---------- Post added at 09:34 AM ---------- Previous post was at 09:33 AM ----------

Should I manually flash the 4.4.2?

---------- Post added at 09:34 AM ---------- Previous post was at 09:34 AM ----------

P.s. if said phone is up to date... I know it isn't..lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
You can manually flash the latest 4.4.2 ROM. It really depends on whether you want to be running a custom or stock ROM.

Has the existing ROM been altered in some way that prevents the OTA update from installing? Did you try a factory reset before installing the update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
Yes. Friend reset it..maybe I should..for double check?

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

And I will probably run stock rooted for a while,then flash a custom. That's what I usually do.

---------- Post added at 10:13 AM ---------- Previous post was at 10:10 AM ----------

I think I should get a fastboot getvar all.. Maybe post the results.

---------- Post added at 10:14 AM ---------- Previous post was at 10:13 AM ----------

I know some adb cmds that are universal. But to check getvar, wouldn't I "adb reboot boot loader" or "adb reboot download"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Make sure you turn on USB debugging. Then run adb reboot-bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisb906:
So..there are three kinds with this device? Bootloader,download mode and recovery? Or is DL mode same as bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
There are basically two: download mode and recovery.