Develop Bugs

Need help Installing CWM on i747

Its been awhile since I've done my firmware, but I'm giving my phone over to my sister soon and upgrading to a Note Edge.
I'm trying to get this phone on Likewise S5, but having a little difficulties with the older guilds to install various stuff, also all the warning on the Likewise S5 don't show up in the guide I was following for the actual installation, like stuff about bootloaders and modems (I don't know what these are), I am a techy just I'm not well versed in Cellphone Firmware talk at all, more of a PC person.
This was the guide I'm following well can't link it, its on Team android, for the likewise S5 for S3 i747
I'm Trying to install CWM Because I believe I don't have one currently installed, if I do is there a way I can find out? all I believe I have is just a oem 4.1.2 firmware that was rooted.
Almost all the CWM guides that are out have their own downloads that no longer work for the CWM that they provide, and honestly I don't wanna mess with it anymore and want to get the proper combination, I've downloaded the latest one for Samsung Galaxy S3 from the Official Clockwork mod website for Touch version, but I'm not sure how to flash "that" I know it says to use PDA on 1.85 Odin which i've tried but it just says
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1) (No pass or fail)
I'm not sure what I'm doing at this point and could really use some help, specific to what I'm doing.
And to be specific I have a Samsung Galaxy S3 i747 From Rogers Wireless in Canada (Sept 2012), and it isn't bricked have booted it up just fine.
Currently I am dealing with a finnicky USB port as well, need to get some alchohol and see if I can get a more reliable connection out of it. I got it to point now I feel like I'm comfortable flashing it just eh, could be better, long as its sitting generally its connected slight pressure in cord to be sure, usually charges no problem but USB connectivity is whats finnicky. I cleaned out the lint with a needle didn't really seem to help a whole lot but definetly lets the plug go in further now, even bought a new cord that gets a decent click but it still a little floppy side to side, feels like its the plug has room to move inside the female end of the plug, vs anything being "loose"

Any chance your phone is already rooted? Odin flashing anything with a flaky USB port would make me a little nervous.
If you're rooted, there's an app called flashify that makes updating recovery pretty simple and there is no USB connection needed.
Also in the Play store if you search for Samsung Phone Info you should find an app that will tell you what firmware you're on. Install it and report back what it tells you you're on for bootloader and baseband and someone here should be able to chime in on whether it will run newer roms ok, or how to proceed if its out of date.

jason2678 said:
Any chance your phone is already rooted? Odin flashing anything with a flaky USB port would make me a little nervous.
If you're rooted, there's an app called flashify that makes updating recovery pretty simple and there is no USB connection needed.
Also in the Play store if you search for Samsung Phone Info you should find an app that will tell you what firmware you're on. Install it and report back what it tells you you're on for bootloader and baseband and someone here should be able to chime in on whether it will run newer roms ok, or how to proceed if its out of date.
Click to expand...
Click to collapse
I am already rooted I know that I did the root myself, to get Super admin permissions for the Ps3 controller blutooth controller permissions.
I'll look into Flashify, I'll install phone info now

Ok here is from my Samsung phone info app;

DMF1 firmware is pretty out of date. Unless you pick an older build of a custom rom, you'll run into some issues.
The full Canadian carrier updates for i747m are all available for download from sammobile.com, but those will be really big files to flash with Odin. I wouldn't try that unless you're really confident in that USB port. This won't be a really quick flash and interrupting it could brick your phone.
The safest route might be to unroot the phone and take carrier OTAs until your firmware is up to date. You'll have to be on stock recovery for OTAs. Once you're unrooted if you power down and reboot your phone, I'm pretty sure the stock recovery will come back. If not, here's a link to a stock recovery: http://forum.xda-developers.com/showthread.php?t=2026751
To get going with rooting and custom roms again you'll have to flash a custom recovery in Odin once you get up to date on OTAs, but that will be a 5 - 10 MB file to flash as opposed to a 1 GB+ full system update. Don't worry about that until you get the bootloader and modem up to date, one step at a time. :good:

How do I perform an update though to manually update the phone, like to unroot it basically I'm Connecting it to USB getting it to recognize in Kies?
Like I have full USB access to my phone now, yes the port is flaky but it functions. Kies says my device is on latest firmware even though I know 4.4.2 was released by rogers for the device, i.e I don't understand how to unroot it and bring it up to date
I don't know what a OTA is, I don't understand what a modem/bootloader is etc.
I'm assuming what I have to do is update it to 4.4.2 via the normal firmware but currently it isn't giving me an option to

OTA is "over the air" updates. They are pushed to your phone and often update your phone's bootloader, modem, and rom to new versions. They'll download and install with wifi or cell data, no USB connection required. It is a very safe way to update your phone, but OTA updates will fail if you are rooted and have custom recovery (at least AT&T's will).
With android 4.1 and DMF1 firmware you're something like 2 or 3 updates out of date. Usually OTA notifications just pop up on their own, or you might have a "check for updates" option somewhere in your rom settings. Has this phone been off the grid for a while, update process frozen, or just declining OTAs for the last year and a half or so? Is it not tied to a carrier anymore?
I have updated bootloaders and modems outside of the OTA process, but only on the i747 AT&T variant. If OTA is not an option for some reason, I can't comment on what your safest route would be on the Canadian variant, but there are plenty of expert i747M users on here. Someone will chime in to help you out.
If OTA is an option, then the easiest way to unroot used to be to install SuperSU from the Play store, if you're not already using it. In SuperSU settings there used to be a "full unroot" option.

Ok So what do I need to do exactly I unrooted the phone no problem but it still doesn't recognize it as needing new firmware still so I'm still confused how to update it.
My understanding is I need to update this to latest base version which would be 4.4.2, but I'm not sure how to do that exactly since its not automatically doing it given the custom rom.

Confirm the bootloader on your phone and post it here.
It is the bootloader that will determine which stock firmware to flash from sammobile.com onto your i747m.

audit13 said:
Confirm the bootloader on your phone and post it here.
It is the bootloader that will determine which stock firmware to flash from sammobile.com onto your i747m.
Click to expand...
Click to collapse
Again, I'm not well versed in android terminology etc, I don't really know what a bootloader is, everything in those screen caps above is what I'm using

If you want to be on the latest stock, just use Odin to flash the stock Rogers 4.1.1 ROM from sammobile.com. Then use OTA updates to update the phone to the latest KK.

audit13 said:
If you want to be on the latest stock, just use Odin to flash the stock Rogers 4.1.1 ROM from sammobile.com. Then use OTA updates to update the phone to the latest KK.
Click to expand...
Click to collapse
Again, I Really Need more details Odin isn't so simple that its Oh Slot dis dat flash in der and poof completeo, if you read through the thread you'd you I have a flaky USB port that isn't 100% stable, flashing a 1gb rom through a iffy connection doesn't sound smart.
How do I flash this correctly from SD card if I can?
Please describe, Which App I need for it, what I need to do in app etc, cuz Odin is like AD AP DS WE aslaksd its all gibberish to me unforunately for different flashing locations

I know of no way to flash a completely stock ROM from an SD card.
If you wanted to flash it from an SD card, you would probably need to download the entire ROM, strip out the stock recovery, and re-pack the ROM into a zip file.

I'm still extremely confused, I need consise directions what I need to do, so far I haven't had solid details in this thread yet how to get my firmware installed :crying:

Evockzi said:
I'm still extremely confused, I need consise directions what I need to do, so far I haven't had solid details in this thread yet how to get my firmware installed :crying:
Click to expand...
Click to collapse
since youre computer literate , so to speak , perhaps this method would help/be more 'simple'. IDK , just a thought.
http://forum.xda-developers.com/showthread.php?t=2225405
"all i can really do , is stay out of my own way and let the will of heaven be done"

Is that method compatible with my device? before I've only been following ones that flash with odin.
The Reason why the isn't helpful immediately for me, I Do Not Know what I need to Do to achieve what I need.
Bootloader means almost nothing to me, I do Not know what I need to accomplish, No one has answered that question yet for me.
My Question is again, So, Do I need to install 4.4.2 Base as downloaded from that Samsmobile, and How Do I install Specifically that?
Beyond That my question expands into, Ok After I install that What do I need to do to install likewise.
I Do not know what I need to do so all these guides about doing specific tasks that you know what you need to do are useless to me at this moment I'm afraid.
I have enough of a stable USB connection I can Odin it Right now I just need to know what to select, etc

I yolo'd it with the connection, and flashed it with older odin 1.85 since I know PDA is the correct one idk what the hell it is in the new odin.
Passed, took almost 8 mintues to flash it, Now I just need to get back to original question of installing CWM Recovery and Getting Likewise S5 rom installed.
Do I have correct 4.3-4.4 Modem and boot loader that it spams in bright red on the likewise requirements?

Managed to finish all the installations without a hitch,
Followed a guide to CWM install and then root it through installing SuperSU, Then had everything to install Likewise which can be done on the device.
Everything installed perfect now I have a S5 to give to my sister cheers

@Evockzi glad you got it figured out.:victory:
"all i can really do , is stay out of my own way and let the will of heaven be done"

[Q] AT&T S3 on 4.3 OTA/SIM unlocked/Knox 0x0 - which flashing route?

Hello all, it's been a while since I understood the S3 firmware situation but I appreciate the advice.
I recently received a ATT S3 which is at OTA firmware 4.3 (MJB) and carrier SIM unlocked. I would like to arrive at CM12 with Philz recovery. I would appreciate suggestions on my best firmware upgrade route given the situation.
I understand the bootloader has been Knox'ed, so I may only upgrade (never downgrade) my Bootloader. However, I do not know the implications of KNOX on modem updates. I hear flashing a custom Recovery or Firmware will cause Knox to go to 0x1. Is it true or false that a tripped Knox (0x1) will PREVENT any further Modem or Bootloader updates? If this is true, it means I cannot use the upgraded 4.4.2 OTA modem (or later updates, if they are ever made) if I attempt flashing Cyanogenmod now (at 4.3 MJB). Is the new 4.4.2 modem worth it? Can 4.4.2 OTA still be rooted/custom recovery'd?
I am considering inserting an ATT SIM and allowing the the 4.4.2 OTA update to occur. Then I plan to use TowelRoot to apply Root from the phone itself. Then using EZ-Recovery (I used this on my VZW S3? But current seems to be Flashify?), I plan to flash Philz custom recovery from the phone itself. Then I plan to reboot into custom recovery and Clean install CM12 from the phone itself.
Does my planned approach have any issues? And what is this I hear about using Terminal commands to unlock the AWS1700 band (T-Mobile) semi-permanently? (I have a SGH-i747, not 747M. Posts seems to imply it only works semi-permanently on 747M?) I would like to keep my options open if possible. And is the ATT Knox 4.3 (MJB) firmware bootloader-locked? I was under the impressions all ATT S3 (d2att) were bootloader unlocked. (Answer here?: http://forum.xda-developers.com/galaxy-s3-att/help/bootloader-locked-t2990174 )
Thanks again for offering your opinions, there are many ways to skin a cat but I've been having a hard time matching the old methods I am aware of with the new tools. Thank you.
Edit: This thread has been helping explain the bootloader/modem pairing issues I can't understand. I am just unsure if newer = better.
http://forum.xda-developers.com/showpost.php?p=61782091&postcount=3
Regarding Stagefright bug, which is why I want to update to CM:
http://forum.xda-developers.com/showpost.php?p=62116470&postcount=6

My suggestion would be to run ota updates until you are running the latest modem and bootloader.
Flash Philz using Odin, perform a full wipe, install rom, install gapps.
Knox will not prevent installing roms, recovery, modems, or bootloader. Once on the latest kit kat, there is no need to install alternative bootloaders or b modems.

Hi, I doubt towelroot would work, as it's most likely been patched. (the exploit towelroot used). I believe the 0x1 is the warranty bit. I wouldn't think stock OTA update wouldn't be possible after, however. I'm not the one to verify this I'm on the I747M and I know the ATT stock images for the later releases are not available. So I cannot advise you there.
I'd say either use odin to flash cf autoroot.
or odin to flash recovery then supersu zip install to gain root.
I did search for ways without tripping the counter but like usual I was too late to the party to use towel root. But my warranty is out anyways.

Thank you for the insight. I think I will do just that, there are some ODIN-flashable 4.4.2 images provided by a helpful member here, but I do not want to do them out-of-order and potentially brick the device.
Since this phone has been completely abandoned by Samsung and ATT, I see no harm in voiding the Knox bit. If any applications complain, I can always use Xposed to fake it I suppose.
I will keep my fingers crossed that Towelroot will work. The last update ATT permitted was back in 2014, so there is a slim chance it may work. I will see when I do the OTA update.
Thank you! :good:

Hey all, as a followup I used OTA updates on stock combined with the procedure described here to achieve what I wanted. Knox has been tripped, of course.
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/
Some caveats:
I had to use a weird debug menu to get the unlock code ATT gave me to work. If I tried it as instructed by ATT as soon as the phone turned on it rejected the code. The #* instructions in the first post here worked and I was able to use the code ATT provided.
https://forums.att.com/t5/Samsung-D...code-for-galaxy-s3-does-not-work/td-p/3963728
I had to pull the battery after ODIN said "PASS" (as described in the video) to prevent the custom recovery from immediately being reverted to stock on reboot. When running SuperSU for the first time I had to try once, get stuck, then reboot and try again to "Remove Knox" properly.
I had to visit TWRP's site to download the newest Odin flashable TWRP TAR. The TWRP Installer Play Store app did not work when I had the CWM installed that was linked in the tutorial. The reason for needing TWRP is that CWM did not allow proper installation of the CM12.1 TK_Gapps "stock" version. I suggest anyone else in my position simply use TWRP Odin flashable TAR from the get-go. Also, simply hold down the Recovery mode button combo as soon as Odin forces a reboot rather than pull the battery.
For the record, Google Wallet Tap-And-Pay does not show up as an option in the app on the latest CM12.1 nightly (8-7-2015). Everything else seems to work. (CM12.1 for d2att recommends having the NJ1 bootloader/modem combo anyway.)
The TowelRoot method would have worked if I stopped at the 4.4.2 NE4 OTA update.... and theoretically would have preserved Knox. (At least until I flashed a custom recovery.) The OTA updates I received were a really big 4.3 MJB => 4.4.2 NE4 update (~500mb) then another, very small 4.4.2 NE4 => 4.4.2 MJ1 update (~20mb). I set my phone's clock ahead 24 hours to force the ability to immediately update.
Thank you @audit13 and @serathe for the tips. I hope this is instructional for anyone else in my position.

General mod questions - bootloader, recovery, and ROMs

Hi,
I know this information is probably available somewhere, but I have spent hours of reading, and still having some trouble getting my head around things. So I will try to be clear here as to what my issues are.
Firstly... I have Samsung Galaxy S-III, SGH-i747M, with virgin mobile canada. It started with android 4.1.2. I wanted to unlock it, and there was a way to do it with 4.1.1 (http://forum.xda-developers.com/showthread.php?t=2176719), so I used odin, with firmwares (found at SamMobile.com I think) to flash a 4.1.1 ROM, did the unlock procedure, and then used odin to flash stock firmware for 4.1.2 again. Seems to have all worked out ok.
Anyway, I want to try some custom roms, like cyanogenmod, as they are purported to improve battery life, speed, clearing off bloatware, giving me more control, etc.
However, I really want to maintain the ability to go back to how it is now, if I don't like the custom roms. (or if I need warranty help, though there's not much of that left).
The main thing that's concerning me is that while I was playing with this phone before, I read in a number of places that if I had updated to Android 4.3 or 4.4.2 when those had become available from my carrier, I would not have been able to downgrade to 4.1.1 (which I needed to be able to do to use the built-in unlock method). This is because of Knox, which would be installed, and gets "tripped." So now I'm scared: if I did that upgrade, I wouldn't have been able to revert; so now, if I flash a CGM ROM, will I also be unable to revert?
I think there are a few pieces of android to sort out in my mind... If I'm not mistaken, there's bootloader, there's recovery, and there's the ROM. Flashing a ROM with Odin apparently would restore recovery and the ROM? But not the bootloader (that's where knox is? though I still don't understand, if an upgrade can modify the bootloader and put knox there, where it wasn't before, shouldn't there be a way to put a pre-knox version back there?)
Oh, there's also EFS, which some say should be backed up before doing anything (though you need to root first, which in my mind counts as doing something before backing it up).
Anyway, please let me know if you can help clarify these issues, thanks!!

There is a lot to cover to address all that you bring up.
Regarding EFS, there are a number of ways to back it up. Use several. This thread is an excellent place to start for more info and several ways to make the backup. I was rooted, so I used A2 and B. I believe you can use A1 without being rooted, probably B as well. Long after that post was written wanam came out with two backup apps available in the PlayStore. One was specifically for EFS, but I do not think it is still supported. The other is a more comprehensive app, both require root.
As a rule, bootloaders and modems are not installed with custom ROMs. If you are flashing a stock ROM from these forums that is installed from within a custom recovery it probably does not install a bootloader and modem either, but read the relevant thread to be certain. Full stock ROMs flashed from with Odin, or Heimdall, almost certainly install a bootloader and modem.
Prior to 4.3 there was an ability to downgrade bootloaders and modems, nor were they required to match - be at the same version. Once you upgrade to the official 4.3 bootloader you can no longer downgrade it. Once you have upgraded to 4.4.x the bootloader and modem versions must always match. If they are mismatched you risk soft bricking your phone at a minimum. For the i747 there was an unofficial 4.3 release; ROM, bootloader, and modem. I do not recall seeing mention of an unofficial release for the i747M, so I will not go into the exceptions on the above the unofficial bootloader/modem introduced.
For TouchWiz ROMs, custom or stock, the bootloader (and modem) version should match or be more current than the ROM Android version. (One of the unofficial 4.3 release exceptions applies here, I make use of it.)
For CyanogenMod, CM based ROMs, AOSP ROMs, and their derivatives the bootloader and modem version can lag behind Android version of the ROM. With your 4.1.2 bootloader and modem you could run the earlier releases of 4.4.x CM and AOSP ROMs. Later in the 4.4.x development, around Oct or Nov 2014 IIRC, I began reading reports of needing to be on 4.3 or later, there were a few said the 4.1.2 firmware still worked for them. For the 5.x.x LP releases of CM and AOSP most report that they must be on a 4.4.x bootloader and modem.
Knox is in the ROM, not the bootloader and modem. It was introduced with the official 4.3 releases. It is not present in CM/AOSP nor most of the custom TW ROMs. It will be present in stock ROMs from official sources or sites like sammobile. Many of the stock ROM images/dumps have Knox disabled, especially those from enewman17, but read to make sure what you are getting.
I don't feel qualified to discuss tripping the Knox counter, I am still on the unofficial 4.3 bootloader, which has not kept me from running 4.4.x ROMs. I am not the only Luddite, but I feel we will all be updating bootloaders and modems due to the Stage Fright bug. I am long out of warranty so there is no loss.
ABOVE ALL, read thoroughly before taking any action. Keep in mind that I am on the i747 and not the i747M as you are, I am not be correct on all comments for your device. @audit13 should be able to clear any gaffs I have made.

@dawgdoc is correct about everything said.
It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.

Ok, starting to feel a bit more comfortable with the whole system and relationships, thanks!

audit13 said:
@dawgdoc is correct about everything said.
It is not Knox that prevents downgrading from 4.3 to an earlier version, it is the code in the bootloader itself.
Click to expand...
Click to collapse
Thanks for verifying that. There could have easily been small, but very important, differences in the devices that had slipped my mind since I don't have the i747M.

This is the way xda should be. Good questions from a concerned user & great answers from @dawgdoc. Nice job guys!

canodroid15 said:
This is the way xda should be. Good questions from a concerned user & great answers from @dawgdoc. Nice job guys!
Click to expand...
Click to collapse
I would like to extend similar praise and thanks to @mrrocketdog and @audit13

more uncertainty
Hi,
I'm a lot more experienced now, having rooted (I flashed root66_BMC_I747MVLDMF1 by MrRobinson, since CF-autoroot just made the phone show "booting recovery" then blank screen indefinitely), I backed up EFS by a couple methods, flashed TWRP, did a nandroid backup, and flashed a couple versions of CM. Still a few things I want to clarify though.
Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem. In general, I see a lot of posts simply saying "update the modem." From what you've said though, that will create problems, unless I update the bootloader as well, correct? Just feels like the phrase "update the modem" is said so casually, without also mentioning the bootloader, and the inability to go back.
(an older CM 11 worked with data just fine)
(a big issue is that S3 is over 3 years old, so there are over 3 years of posts, so there's a lot of conflicting information, likely due to different versions, new discoveries, etc. )
I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" There are a lot of "Never update to 4.3 (or above) because of knox!" comments. But also in general, it seems the only real issue with knox is that warranty bit, otherwise it doesn't have too big an impact on our lives? Seems the consensus is that we can still root, install custom roms, and everything else. (Do you know if this remains true with latest bootloaders and modems (OB3 for i747M). There are also "My battery life became way worse after the upgrade" or "more FCs" or other issues, which is a significant concern if my phone which currently comfortably lasts a day starts to not last a day after updating. Though it's likely a small percent noting that, while the quieter majority are fine. Meanwhile, by not updating, we may be missing out on features and security improvements (and maybe actually improved performance). What do you guys think? (I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).
As for updating, I think somewhere one of you suggested the better (or at least safer) way is to use odin to flash stock ROM, then do the OTA updates, or, directly flash the latest stock ROM, rather than trying to flash modems and bootloaders directly?
Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)
Thanks again!
I almost wish I'd just taken the blue pill at the start of all this

For XDA members that are new to rooting, flashing, etc., I always recommend the safest route which is to flash back to a completely stock ROM and just upgrade to the latest bootloader and modem via OTA updates. There's always a risk of something going wrong when flashing anything, be it a custom ROM, recovery, or OTA update.
If the phone still had warranty, I recommend not flashing any non-Samsung software until the warranty has expired. Once expired, flash away
Knox should not interfere with root if supersu is flashed from a custom recovery, regardless of the bootloader. I have used supersu to root the latest s3, s4, Note2, and Note3 ROMs without a problem.
Restoring old nandroid backups should not cause a brick as TWRP does not change the modem or bootloader.

sacrawfo said:
....Still a few things I want to clarify though.
Unsurprisingly, after flashing the final CM 11 release, data did not work, as I'm still on the 4.1.2 (MF1) bootloader/modem.....
(an older CM 11 worked with data just fine)
I'm not quite sure myself what I'm trying to ask, I guess it's something along the lines of "am I just being silly by not updating?" ....(I know dawgdoc was sticking to an unofficial 4.3 rather than updating, so it's not an obvious choice).
Once I have a 4.3 or 4.4.2 bootloader/modem, I can delete any old TWRP nandroid backups from when I had 4.1.2 since restoring them would cause a brick? Same for EFS backup (which backed up EFS, Modem, Modemst1, and Modemst2 partitions)
Click to expand...
Click to collapse
I think the change date for CM11 requiring the newer bootloaders, at least NE4, is Nov 2014. Releases prior to that date would run fine on older bootloaders.
I have since updated to NE4 in order to run ROMs patched with the StageFright fixes, specifically CM11 20150831. Knox isn't installed on this ROM or even the newer custom TouchWiz based ROMs. I am not concerned about Warranty Bit being triggered. My device is long past being covered by any warranty and I have no intentions of using Knox features on this phone in a corporate environment.
Keep the EFS backups, those are from partitions not changed by flashing roms; stock or otherwise.

Finally went through the OTA updates, surprised how long it took but all done, at OB3.
Ok makes sense, restoring an old Nandroid would effectively result in a 4.1.2 OS with a 4.4.2 bootloader/modem, which != brick.
Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.
Thanks,

Restoring a nandroid backup should not brick the phone brick the phone as twrp does not restore the modem or bootloader.

sacrawfo said:
...
Still surprised that modem updates do not effect the "modem" partition that EFS backup saved.
Thanks,
Click to expand...
Click to collapse
There are quite a few partitions not affected by flashing, not only the EFS partitions. IIRC there are secondary modem partitions, more than two extra bootloader partitions, etc.

Can't turn on WI-FI on my My Samsung S3 I747.

I loaded various ROMs on my Samsung S3 I747. I then went back to stock ROM by flashing UCUFNJ1_Rooted.zip with CWM recovery. I then
flashed UCUFNJ2_Rooted.zip. and my phone works fine, but when I try to turn on WI-FI, it stays greyed out. I flashed
d2att_I747UCUEMJB_bootloader_modem_4.3.zip but that didn't help. Does anyone have any suggestions?

[email protected] bellsouth.net said:
I loaded various ROMs on my Samsung S3 I747. I then went back to stock ROM by flashing UCUFNJ1_Rooted.zip with CWM recovery. I then
flashed UCUFNJ2_Rooted.zip. and my phone works fine, but when I try to turn on WI-FI, it stays greyed out. I flashed
d2att_I747UCUEMJB_bootloader_modem_4.3.zip but that didn't help. Does anyone have any suggestions?
Click to expand...
Click to collapse
Sounds like your firmware doesn't match your ROM. That can cause problems like wifi not working with stock kernels. Before you do anything verify what bootloader and modem you have on your phone. Either install the Samsung phone info app from the Play store or enter these commands in a terminal or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
Based on your post those should both end in MJB, but it never hurts to make sure (and sometimes it hurts a lot when you don't make sure).
You need to get your bootloader/modem to match your ROM to get everything working right since you're running stock. Since your already running the NJ2 ROM, and it contains at least partial fixes for some of the Stagefright vulnerabilities your best bet is to update your bootloader/modem firmware to NJ2 to match your ROM.
This can be done pretty quickly and easily with zips enewman17 has posted, but there is always a risk when messing with bootloaders. These need to be flashed incrementally in the proper sequence and you need to reboot into your ROM between each flash. The proper order is MJB -> NE4 -> NJ1 -> NJ2. As long as both your bootloader and modem are MJB, you can start with NE4. Just be absolutely sure to flash in the correct order and always reboot into your ROM after each flash or hard bricks can occur when messing with this.
Samsung made it pretty hard to update the firmware on this phone after they introduced Knox, and AT&T does us no favors by not releasing full firmware packages for their devices.

Do as @jason2678 stated. If you find the versions end in something other than MJB, then start your bootloader/modem fixes at the version on your phone and go on to match your rom.

No WiFi

All,
my sgh-i747 WiFi doesn't appear to work. under settings> WiFi slider (OFF)> slide to on (remains off)
next goto WiFi setup screen: no devices listed, buttons at bottom of screen dim/greyed out.
history:
phone was bricked by a forced ATT update. I finally did a rom update/reinstall to push a working stock kernel kitkat 4.4.2
thx
Rob
ALSO i need working links to Lollipop for sgh-1747 using oden
PS: I do ROM , hardware and software updates on data storage systems with petabytes of storage. BUT THIS PHONE MAKES ME FEEL STUPID....
My Hats Off to All Of You Who Hack, Play, or Make Mods for the Phones.

Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.

jason2678 said:
Boot image not matching firmware on your phone can cause wifi to not work. The kernel doesn't have the what it needs to work with the radio you have installed. It is a fairly typical stock rom problem. Custom roms typically have broader support instead of being targeted at a specific firmware.
First step is to figure out what exactly you have on your phone now. Need to know bootloader, modem, and boot image versions since this phone is finicky. Hard bricks are possible, so don't do anything hasty. There's an app in the Play store called phone info samsung by vndnguyen that helps with that. Install it and see what it says you have for bootloader and modem/baseband. Also check in Settings -> About and see what kernel version you have (the app might tell you that too, it has been a long time). Report that all back here and it will help with how to fix it.
Alternately if you don't want to mess with the app enter this in a terminal app or adb shell:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
You won't find an Odin package for lollipop. Samsung never updated this device past kitkat. Anything lollipop or newer would be a custom rom, and those are all custom recovery flashable zips, not Odin.
Click to expand...
Click to collapse
Thank You
jason2678 what you said makes perfect sense to me. like needing a VIN # for a 2002 Toyota to figure out what water pump or alternator because they used 6 different versions of each, LOL
so i would like to use 5.1 lollipop which is a custom ROM i believe, if you can suggest one i will defer to your judgement
but as a fallback suggest a kitkat ROM as well
bootloader I747UCUFNJ1
BASEBAND I747UCUFNJ1
KERNEL VERSION:
3.4.0-1514807
[email protected] #1
32-bit
modem msm8960
please and thank you
respectfully
123RobH

At NJ1 you're not on the latest bootloader and modem, but you're close enough. And your bootloader and modem match. I wouldn't mess with it. You'll be able to run all the latest custom ROMs on that, no problem.
If you want lollipop, look around the development section here. I'm not sure if you'll be able to track down a lollipop rom download linked to XDA. You might have to poke around old uploads for d2att on androidfilehost.com for 5.1.1 roms. I'm pretty partial to slimkat stable 9 on this phone, and it runs fine on NJ1 firmware too.
Oct-Os is probably the most actively supported rom currently. They've moved on to nougat these days. You'll be able to run it on NJ1 too. You might want to give it a shot.
Track down a rom and matching gapps. Then full wipe and flash them with TWRP recovery. If you run into any trouble or have any questions, just ask. I'm pretty certain once you get a custom rom on your phone your wifi problems will go away. Stick to lollipop, marshmallow, or nougat and you'll be fine. Even newer KitKat ROMs will be OK on NJ1.