You were on the other thread with the guy that had an i747m, I searched forums that detailed S3 KitKat version bootloaders being locked. I can copy a paste a thread or a few if you'd like, but we established this yesterday. That's why custom recovery wouldn't work. Just like the S4 it simple to get root access, but users are unable to downgrade to pre-4.4 firmware, use AOSP ROMs, utilize custom recovery and so on. I wasn't aware the S3 had any versions with bootloaders locked, but plenty of forums here and other sites detail it, and it certainly fit all the symptoms with g33k's i747m yesterday. I'm really unclear outside of ATT and VZW and Canadian counterparts I suppose, which is or is not locked. I flashed an old S3 with the newer version bootloader included with KitKat 4.4.2 to try, and it certainly doesn't allow 4.3 JB to be reverted to afterward. That one has screen burn so its disposable anyway. I done that yesterday to see what extent the lock really is on the S3 i747. I didn't try Philz or TWRP since I think several forums cover that already. I only remember that when the new bootloader was released, it was known that it wasn't possible to revert once updated. I was never going to anyway, but I find it interesting none the less because I was unaware that any S3 had any sort of locked bootloader. It may be limited only to ATT and VZW, but it's still interesting to know.
Of course, there is a tool for the S4 now so that users with KK can use JB Stock Roms, but I havnt ever used it. I wasn't even aware the S3 bootloader had a bounty to be unlocked til yesterday. At any rate, I'm not up to speed on what ROMs can or can not be flashed with that bootloader. I have been reading though, because of the chronology it has in common with other devices. I'm also curious if that version predates the current bootloaders which are locked on the S4, S5 and other devices as it might lend some insight... or not. If I recall right though, CM11.1/2 worked with the i747 but needed the bootloader upgraded, so that isn't consistent with a locked bootloader. It makes for some interesting reading, but figuring out what applies, and what doesn't is trying. I'll try flashing a stock ROM 4.3 and see f the stock kernel works. It might! Its academic, but I'm curious about this bootloader now, and might can learn something new. I'm also curious why the i747m yesterday was so restrictive with others not being of the same device and version. I knew what it sounded like as soon as he said he softbricked going into recovery even trying different versions and using Odin and trying flashing with device. Oh, I've never used mobile Odin, but I own it lol. Were you able to flash an S3 to 4.3 with updated bootloader with PC? I'm not sure what expanded ability Mobile Odin has really. Also, did you ever use CM or an AOSP ROM after updating the bootloader? And was the device an i747 ATT? That's what I own is why I ask. I might goof around with it later and see what, if any, limits it has.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Last edited:
Good job... I suppose. Mentioning that to the user needing help yesterday, would have been nice. Perhaps, using your experience to help a user that knew how to use Odin, but had symptoms of locked bootloader just the same with recovery and reverting back to 4.3. That's your device... I747m with KK. The rest of us only had US variants and myself none with over CM 10.0. even. Just sayin'.... easy to pull up a list of devices, when you know the list already. Thanks for the clarification... ATT S3 was about the last device with an unlocked bootloader according to your article.
