Related
So, I'm trying to install a custom recovery to flash a new ROM on this stock, UCUFNJ1 phone, but I'm concerned I might approach it wrong. Could I get a hand, 'fellas?
I inherited the phone, and have had pretty good success with the I747 in the past, installing TWRP and CM 10.2 on a few phones in the past for friends and family (I usually default to that one since, in my experience, it's been most stable). I've heard that there's a high rate of bricking when trying to install a custom recovery on AT&T i747 devices running 4.3+ bootloaders, so I'm trying to play it safe, since I've never worked with one that had anything newer than 4.2.1 installed on it.
I can't seem to find anything definitive on rooting this phone for the UCUFNJ1, but a lot of people trying to update to that bootloader from NE4. Interestingly, this device was running UCUFNE4 (I decided to check because I had a feeling the folks weren't going to heed my warning, "NOT TO TOUCH IT BEFORE YOU GIVE IT TO ME.") But when I got it back, I discovered they must have reset it and some kind of OTA was applied when they were using it.
For the record, this device is unrooted, and is running stock TW, and has no custom recovery.
I'm going to document my approach with this, as well: from what I can see, the information on rooting/unlocking this particular model is pretty scarce, and a lot of the methods are very outdated. Since this is a newer bootloader, I have a sinking feeling it's uncharted territory.
Here's what I'm dealing with now:
Android Version: 4.4.2
Baseband version: I747UCUFNJ1
Kernel Version:
¶3.4.0-1514807
¶][email protected] #1
¶Wed Oct 1 21:09:24 KST 2014
Build Number: KOT49h.i747UCUFNJ1
SE for Android Status:
¶]Enforcing
¶SEPF_SAMSUNG-SGH-I747_4.4.2_0016
¶Wed Oct 01 21:09:13 2014
This is what the phone was running before they accepted the OTA:
Android Version: 4.4.2
Baseband version: I747UCUFNE4
Kernel Version:
¶3.4.0-1514807
¶[email protected] #1
¶Mon May 19 21:00:05 KST 2014
Build Number: KOT49H.i747UCUFNE4
SE for Android Status:
¶Enforcing
¶SEPF_SAMSUNG-SGH-I747_4.4.2_0016
¶Mon May 19 20:59:50 2014
I suggest flashing Philz Touch via Odin from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Make sure you download the tar.md5 file.
Copy a custom ROM to an SD card, boot into recovery, backup your existing ROM, wipe cache, Dalvik, data, system, and flash the custom ROM.
Is there any significant difference from using Philz versus TWRP or CWM? Can anybody report success with this configuration? I wouldn't want to brick this device, since if I do, it's back to my ancient Motorola Atrix 4G and I do not want that to happen, haha.
Additionally, will I have any trouble installing ROMs of earlier Android versions? For instance, I've had a good experience with CM 10.2 on all the GS3s I've installed it on, but since I'm running the UCUFNJ1 bootloader for 4.4.x devices, would I run the risk of bricking the phone by trying to install anything other than a Kitkat ROM? (If it just fails to install, I'm no stranger to that, I'm just trying to cover my bases here.)
Thanks.
I had issues with TWRP on my s3 and Note 3 so I switched to Philz.
Philz is actually based on CWM with a touch interface.
Older ROMs should work properly on updated bootloaders and modems. Newer ROMs may not be fully functional on older bootloaders and modems.
Feel free to wait for others to chime in. I understand your hesitation. I would not want a brick on my hands either
You do not need root to install a custom recovery and flash ROMs.
ok, chymeing in then. have had just opposite experience. lol. on mj2 had no problem flashing new roms. updated bootloader/modem to NE4 (KK), and get fail error older CM builds (cm10/10.2,etc.) but was taught by docholiday that on older roms you just edit the updater script to include the new bootloader version and bam! flashes just fine.
p.s. thanks for all your good advice/help audit13, would have drown many times without.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Alright, I'm going to give this a go on Thursday or Friday, thanks for the help--
--I'll be sure to post the procedure and results.
I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.
For reference, this is the phone at its current state:
- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)
- Modem/firmware (?): I747UCLH9
Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):
- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while
- I tried installing various LP ROMs, including CM12.1.
- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.
- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.
- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.
- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.
- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.
- I also tried going full stock by flashing this: http://forum.xda-developers.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.
So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?
Thanks...
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
jason2678 said:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.
Here's what happened thus far:
- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.
- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)
- I tried one of the ROMS. Data still didn't work.
- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.
- Tried another few ROMs. Data worked, but LTE was still erratic.
- Updated to NE4 and then grabbed the deoxed stock ROM.
- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.
- So again used Odin to put TWRP onto the phone
- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.
- Tried getting the ktoonsez kernel. My service was murdered.
- Gave up on LP. Tried Slim 9.0. Erratic data.
- Tried Liquidsmooth 4.4.4 instead.
Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.
It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.
Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.
Glad you've got it mostly working.
You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.
Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.
I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:
Code:
su
reboot nvbackup
That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.
Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
Sent from my DROID RAZR M using XDA Free mobile app
mrkhigh said:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Click to expand...
Click to collapse
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.
There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
coolwhipp420 said:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
Click to expand...
Click to collapse
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.
There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
There is a command to manually trigger the restore routine. I think it's
Code:
reboot nvrestore
but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).
Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.
coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.
I see Jason beat me to answering both of your questions.
I posted a thread a while back but I apparently posted the wrong type of thread. This one should be the right of the right type and in the right place.
On the Samsung devices I've had in the past, the boot loader was always a big deal when flashing new versions of android. I've had this tablet for a while now and haven't updated it since I bought it...and Odin flashed/rooted/installed TWRP on it.
From reading the megathreads, from threads, flashing threads, etc...it's not very clear if this is like the other Samsung devices I've had, or if this is like the EEEpad Transformer and Nexus 7 I had...and could move freely between android versions, stock roms...and nonstock ROMs, etc.
I'm running 5.0.2 and I play hearthstone competitively. I bought this for the display mainly, and now that I've loaded it with some crap, I'd like to flash a custom from/update. It seems my crap+samsungs crap saturates the ram quite well. Can I pretty much flash what I'd like? Or do I have to ODIN from stock to the latest build and then worry about number versions.
Also...I used to run an all that kept my TWRP version up to date. Goomanager I believe...but there are dozens of apps that claim to do this now...can I get a trusted suggestion?
Rooted on stock.
Android Version: 5.0.2
Kernel: 3.4.106 IronKernel V2.0 (mainly for s tweaks to boost audio)
Build LRX22G.T800XXU1BOC3
Forget about using an app to flash twrp.
Do it manually and be safe. Plus the official updates are lacking in features compared to the unofficial builds. Just check out the dev section and you'll see what I mean.
Thanks for the advice. And as far as flashing roms...can I pretty much flash what I'd like? Ex: go back and forth between Cm and stock builds...and between version builds while ignoring the boot loader? I'm basically trying to see if I've missed something critical since I rooted and flashed so long ago.
Jamesyboy said:
Thanks for the advice. And as far as flashing roms...can I pretty much flash what I'd like? Ex: go back and forth between Cm and stock builds...and between version builds while ignoring the boot loader? I'm basically trying to see if I've missed something critical since I rooted and flashed so long ago.
Click to expand...
Click to collapse
As long as you don't flash a firmware build that is incompatible with your current bootloader you can flash what you want back and forth.
ashyx said:
As long as you don't flash a firmware build that is incompatible with your current bootloader you can flash what you want back and forth.
Click to expand...
Click to collapse
Thats what I figured. I'm running the stock rom rooted. I don't know what boot loader I'm on, or how to get to the latest one. I have all the access in the world-- recovery, root. But there isn't a place here...or anywhere that clearly says what am going on. I have a charging issue and would like to foahh a new Kernel, and I might as well update in the process,...by there is no "Upgrade from Xxx while on the stock rooted ROM" guide. Plus my laptop has a crappy USB port, so If I need to Odin something on here, itd be quite the process.
Ive asked around for months, literally. I've never been in this position before. Have always kept up to date. But once you fall behind, in forums like these (especially given the fact hat there are multiple devices in this section), you need something explicit to get back where you need to be.
Last time I looked, there weren't any instructions. Ill look against today to see if I can just download the latest..zip of a 10.5 stock ROM from somewhere in the dev section and then wipe, and flash that. If you know if its alright to just wipe and flash a new ROM, lemme know. Or if I have to Odin to a new one in order to get a new boot loader before I flash the latest Kernel, which I think then one I'm trying to use his BOJ. IRONKernel. I use it for S Tweaks, the sound, and a few performance tweaks.
You have to flash the bootloader with Odin they are posted in the bootloader thread.
You can flash the stock firmware with flashfire.
So...
I got the tablet coming up on a year ago, and I rooted and installed TWRP immediately.
I'm currently running a stock ROM, and would like to continue to run stock based roms, but I've had issues with the custom kernel I'm running. The skyhigh thread is meager when it comes to details, but it also includes a few cryptic warnings about base and source and boot loader. Because I have no idea which one I'm running, or what to flash in TWRP, I'm in a terrible spot.
Searches, P.M.s and thread posts haven't gotten me anywhere.
Even if I could use Odin, the stock firmware thread, and the TW-Based ROM threads don't include the requirements, how you can test to see if you meet them, and if you don't, how you'd go about letting the requirements for base, etc.
Because of the introduction of threads like the stock firmware thread early on, root and odin methods used obscure FW, and now when selecting a few to download you have to choose between FW from France....from no country at all, or from the made up country of Us Cellular. So again, even if I wanted to broach the idea of Odin back to some semblance of stock, I couldn't.
But I ****desperately need a reflash/wipe/update***
Id like to run ironrom and kernel....
So how would I get there....from here? And preferably with TWRP?
Rooted 5.0.2 with TWRP and a really really old version of sky high.
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.