Develop Bugs

[Fix] 4.3 ROMs stuck on splash screen after first reboot

For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
*Note* If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone. The Stock ROM contains the Bootloader which should never be downgraded. Fyi: the Bootloader is not the Baseband, the Baseband is just what Modem you're using.
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).

Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app

bullet2binary said:
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.

spongdangly said:
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
Click to expand...
Click to collapse
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!

bullet2binary said:
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
exodus454 said:
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
Click to expand...
Click to collapse
I'm glad to hear that this seems to be the proper fix. That's odd that you were having trouble with 4.2 ROMs, but then again I'd been running 4.2 ROMs on my phone since they first started rolling out. It's kind of annoying that everyone's S3 seems to be slightly different then the next.

Yeah this was a weird one all right. Just glad this post had a solution
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

glad i found this otherwise my first noob post would have truly been a noob move. Thanks wouldn't have guessed that fix for a few days at least.
verified it works. but it did require some weird time dealing with a bootloop issue on stock recoveries. had to find a .tar version of CWM to flash via odin for the final result.

Still Stuck at Splash Screen after trying to upgrade to 4.3
Background:
I had been running task's rom since 4.1.x. Upgraded to 4.2 with not problems and I kept the rom current. Tried to upgrade to 4.3 and that is where the problems started. It appeared to work, saw that Google was updating a number of apps but then then I kept getting error messages regarding various about various processes stopping unexpectedly. Rebooted the phone and it came up with Task's kernel splash screen where it remains frozen.
I can get into TWRP (v2.3.3.1) recovery and into Download mode.
I have tried wiping Cache and Dalvik Cache
I have wiped System
I have done a Factory Reset
I have Formatted Data
I have used Odin twice to get back to stock (I747UCDLK3) and both times it says "passed."
When I try to reboot it, however, it comes back to Task's Kernel splash screen (I do not see the Samsung screen)
Any help or suggestions would be great.
UPDATED: Found an older update from April and was able to restore it. Still wondering why 4.3 wouldn't take.

This Works
I was skeptical, but this actually works! Now running Task's 4.3 on my bell i747m without any problems!
Thanks for the tip OP :good:

spongdangly said:
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
I hope I posted this in the right section but apologies if it's not.
Click to expand...
Click to collapse
If this works you're a life saver! I've been posting around 4.3 threads about this for weeks and no one came up with a decent answer....
Tried reflashing stock with root but didn't work... i'll try your way, see if that works
Gonna try this tonight!!!
Thanks!

I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.

Solved
Thanks, also works for i727 skyrocket

wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?

Kastro1784 said:
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Click to expand...
Click to collapse
spongdangly said:
1. Use Odin to flash the latest stock ROM
Click to expand...
Click to collapse
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.

spongdangly said:
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
Click to expand...
Click to collapse
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?

Kastro1784 said:
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Click to expand...
Click to collapse
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.

spongdangly said:
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
Click to expand...
Click to collapse
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?

shortydoggg said:
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
Click to expand...
Click to collapse
I'm sorry that I'm unable to help. As I had mentioned I have a Canadian Rogers phone (since I'm in Canada) so I don't know what's going on with the AT&T Stock 4.3 ROMs other then the fact that lots of people are having problems.
If you never flashed or did an OTA update to 4.3 then I'd suggest flashing the Stock 4.1.2 ROM. That or try what Ozark_8125 did since it saves you a couple steps (just make sure that LK3 isn't an older ROM than the one you were on).
If you're unsure what bootloader is currently on your phone and your phone is rooted I'd highly recommend downloading one of the many Root Check apps from the Play Store to verify which bootloader you're currently on.
*Note* I don't know which bootloader is for the 4.1.2 AT&T ROM nor do I know which bootloader came with the 4.3 ROMs. I'm sure a simple search would answer that for you.
Ozark_8125 said:
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Click to expand...
Click to collapse

Samsung fixed my phone free thanks for the help
Sent from my SAMSUNG-SGH-I747 using Tapatalk

[Q] T999L, trouble with installing custom roms after 4.3 update

I had my phone rooted before the update, but then I thought I'd try going without root once the update came out. But now I am rooted once again and running the "T999L 4.3 deodexed, Knox Free". But when I try to install cm (I tried 11 and 10.2), I either get the executing updater binary error, status 7 error, and when I removed the asserts, it just aborted installation. Any help or suggestions are greatly appreciated

Update your Recovery to the latest version.

Perseus71 said:
Update your Recovery to the latest version.
Click to expand...
Click to collapse
I did that, tried both CWM and TWRP and it's still aborting the flash. It seems like the only rom it's letting me install is the deodexed 4.3

Actually I had a issue a few days where I accidentally wiped my internal memory and that is why I installed te deodexed 4.3, could that be a reason why nothing is working properly (I'm able to make backups but not restore them and what I mentioned before in my fist post)? Should I install the original 4.3 (with knox and everything) to get my phone on the correct thing and then use the knox remover from the forum before trying again?

wanderingghost said:
I had my phone rooted before the update, but then I thought I'd try going without root once the update came out. But now I am rooted once again and running the "T999L 4.3 deodexed, Knox Free". But when I try to install cm (I tried 11 and 10.2), I either get the executing updater binary error, status 7 error, and when I removed the asserts, it just aborted installation. Any help or suggestions are greatly appreciated
Click to expand...
Click to collapse
Why dont you try this:
S3Rx 3.0
http://forum.xda-developers.com/showthread.php?t=2326763
Its basically the same thing, except its debloated with a few mods..
Just be sure you have the MK4 Modem..
if you have not updated the bootloader (DONT) It will trip your warranty counter..
Just be sure you flashed the MK4 Modem, then flash the 4.3 rom..
Also be sure to Flash the T999L Connectivity patch on top
with the Insecure Kernel.. If you dont flash the Kernel you will lose wifi connectivity..

Zaphodspeaks said:
Why dont you try this:
S3Rx 3.0
http://forum.xda-developers.com/showthread.php?t=2326763
Its basically the same thing, except its debloated with a few mods..
Just be sure you have the MK4 Modem..
if you have not updated the bootloader (DONT) It will trip your warranty counter..
Just be sure you flashed the MK4 Modem, then flash the 4.3 rom..
Also be sure to Flash the T999L Connectivity patch on top
with the Insecure Kernel.. If you dont flash the Kernel you will lose wifi connectivity..
Click to expand...
Click to collapse
Do I also flash the MD5 file that's right above the t999l data connectivity patch? On the download link it says t999 so I'm not sure

wanderingghost said:
Do I also flash the MD5 file that's right above the t999l data connectivity patch? On the download link it says t999 so I'm not sure
Click to expand...
Click to collapse
Yes.. Flash that (Its the ROM), then flash the Connectivity patch (its the T999L patch), then flash the insecure Kernel..

Zaphodspeaks said:
Yes.. Flash that (Its the ROM), then flash the Connectivity patch (its the T999L patch), then flash the insecure Kernel..
Click to expand...
Click to collapse
Oops, I somehow missed realizing that that was the rom and was downloading an older version of it that was lower down on the post. I got this rom to work, but I am still unable to install other custom roms. I really liked the CM11 (4.4) rom, but after updating to 4.3 (unrooted), I am unable to install anything but 4.3 roms so it seems. I did update to the latest version of twrp and I also tried cwm, but I'm still getting failure messages, any idea on how to fix that? Thanks for your help so far

wanderingghost said:
Oops, I somehow missed realizing that that was the rom and was downloading an older version of it that was lower down on the post. I got this rom to work, but I am still unable to install other custom roms. I really liked the CM11 (4.4) rom, but after updating to 4.3 (unrooted), I am unable to install anything but 4.3 roms so it seems. I did update to the latest version of twrp and I also tried cwm, but I'm still getting failure messages, any idea on how to fix that? Thanks for your help so far
Click to expand...
Click to collapse
To be honest there isnt much difference between 4.4 and 4.3.. other than ART..
I much rather stay on 4.3 because it has App Ops, where 4.4 had it removed..
I much rather have an AOSP rom rather than Touchwiz, but no other ROM i have found that is non Touch Wiz
that has Wifi Calling

Zaphodspeaks said:
To be honest there isnt much difference between 4.4 and 4.3.. other than ART..
I much rather stay on 4.3 because it has App Ops, where 4.4 had it removed..
I much rather have an AOSP rom rather than Touchwiz, but no other ROM i have found that is non Touch Wiz
that has Wifi Calling
Click to expand...
Click to collapse
True, but I guess my issue is that I can't install any of the CM roms, not even 10.2 which is based on 4.3. I just like CM because of the customization and the rom you linked me to has some of them, but not all. I've already tried unrooting and re-rooting, but that still did not help. Is there a different way you're supposed to root after the 4.3 update? I've always followed the instructions on DocHoliday's T999L/T999N thread and before 4.3, I was able to use twrp to flash t999 roms without removing asserts, but now even removing the asserts, I can't install any custom roms

wanderingghost said:
True, but I guess my issue is that I can't install any of the CM roms, not even 10.2 which is based on 4.3. I just like CM because of the customization and the rom you linked me to has some of them, but not all. I've already tried unrooting and re-rooting, but that still did not help. Is there a different way you're supposed to root after the 4.3 update? I've always followed the instructions on DocHoliday's T999L/T999N thread and before 4.3, I was able to use twrp to flash t999 roms without removing asserts, but now even removing the asserts, I can't install any custom roms
Click to expand...
Click to collapse
I have been able to install a couple of CM 10.2 Roms.. Not sure what ones I flashed, because I couldnt connect my phone to my PC via USB..
the phone started to act a bit bazaar.. So I reverted to something I knew..

Zaphodspeaks said:
I have been able to install a couple of CM 10.2 Roms.. Not sure what ones I flashed, because I couldn't connect my phone to my PC via USB..
the phone started to act a bit bazaar.. So I reverted to something I knew..
Click to expand...
Click to collapse
Different CM 10.2 roms as in stable, rc, nightly? I tried the stable version earlier and still no luck. I'm kind of starting to give up on it because I'm just getting frustrated lol

wanderingghost said:
Different CM 10.2 roms as in stable, rc, nightly? I tried the stable version earlier and still no luck. I'm kind of starting to give up on it because I'm just getting frustrated lol
Click to expand...
Click to collapse
Im pretty new to this area myself.. I've had a few trial and error issues..
Flashing Nexus devices is far to easy compared to this.. But since they have no Micro SDcard reader..
I'll never own a Nexus phone..

This is the first phone I've rooted, I didn't have problems until after 4.3. But would you happen to know where I can find instructions on how to unroot this device? I was going to try to find an 100% 4.3 stock rom, unroot, and then try this (http://forum.xda-developers.com/showthread.php?t=2563955) to see if it would work and if it didn't, then I'll just leave my phone unrooted. But I can't find any instructions anywhere, the only one's I can find are DocHoliday's but that's to return to stock 4.1.2

Never mind, I figured out

[Q] Note 2 bricked

Today i flashed CM 11 with CWM and after rebooting the baseband and IMEI were gone. I tried to flash the baseband but nothing happened. I then tried to flash the stock rom touchwiz through ODIN and it failed. Now the phone reboots asking to connect to KIES and do a recovery which i can't perform.
Any clues about?
Thank you in advance,
Davide

you have back up of your phone..?
can you boot into recovery..?
which stock rom you tried to flash , 4.3..? 4.4
http://forum.xda-developers.com/showthread.php?t=2758855 See this might help you
caravaggio971 said:
Today i flashed CM 11 with CWM and after rebooting the baseband and IMEI were gone. I tried to flash the baseband but nothing happened. I then tried to flash the stock rom touchwiz through ODIN and it failed. Now the phone reboots asking to connect to KIES and do a recovery which i can't perform.
Any clues about?
Thank you in advance,
Davide
Click to expand...
Click to collapse

tnt4ever said:
you have back up of your phone..?
can you boot into recovery..?
which stock rom you tried to flash , 4.3..? 4.4
http://forum.xda-developers.com/showthread.php?t=2758855 See this might help you
Click to expand...
Click to collapse
Thanks for the prompt reply. The Rom I flashed is the 4.4.2 snapshot.
In the meantime i flashed this pit file from this link
http://forum.xda-developers.com/showthread.php?t=2137008
and now the CYM is back and working but still no baseband.
Is there any way i can reinstall the stock rom ? is the partition a problem?
I dont have a backup of the EFS folder (I made it once but i cant find it)
EDIT: CWM is installed and working

is your IMEI Same..?
i assume there are several reasons, it can be a simple fix by installing a stock 4.4 KK which will eliminate the problem you are facing, iin past week, i done alot of experiences on my bricked note 2, specially the failed PIT flashed, i tried couple of them but at the end the only thing turned the phone in right direction was stock KITKAT
you can find that in the the post i posted earlier.
i am 100% sure you will get your phone back to life.
also remember to when you are done flashing go to stock recovery and wipe data and cache. It is needed after re-partiton to form the partitions correctly
edit: best keep a nand of your current rom as well
4.4.2
https://mega.co.nz/#!2QRmCbyb!YkWs927BfvYxqL-vJiQHXkshqG3UtqHm4XIDbgLsEK0
best of luck
caravaggio971 said:
Thanks for the prompt reply. The Rom I flashed is the 4.4.2 snapshot.
In the meantime i flashed this pit file from this link
http://forum.xda-developers.com/showthread.php?t=2137008
and now the CYM is back and working but still no baseband.
Is there any way i can reinstall the stock rom ? is the partition a problem?
I dont have a backup of the EFS folder (I made it once but i cant find it)
EDIT: CWM is installed and working
Click to expand...
Click to collapse

tnt4ever said:
is your IMEI Same..?
i assume there are several reasons, it can be a simple fix by installing a stock 4.4 KK which will eliminate the problem you are facing, iin past week, i done alot of experiences on my bricked note 2, specially the failed PIT flashed, i tried couple of them but at the end the only thing turned the phone in right direction was stock KITKAT
you can find that in the the post i posted earlier.
i am 100% sure you will get your phone back to life.
also remember to when you are done flashing go to stock recovery and wipe data and cache. It is needed after re-partiton to form the partitions correctly
edit: best keep a nand of your current rom as well
4.4.2
https://mega.co.nz/#!2QRmCbyb!YkWs927BfvYxqL-vJiQHXkshqG3UtqHm4XIDbgLsEK0
best of luck
Click to expand...
Click to collapse
Exactly. Flashing the official stock rom based on kitkat 4.4.2 (which has been released few days ago I believe) solved the problem. I'll try to flash CM tomorrow (tonight get.cm is not reachable and can't download the android app).
Thank you!

Hello
very happy to see your problem is fixed
enjoy your galaxy note 2
this community is very helpful for every one my friend
caravaggio971 said:
Exactly. Flashing the official stock rom based on kitkat 4.4.2 (which has been released few days ago I believe) solved the problem. I'll try to flash CM tomorrow (tonight get.cm is not reachable and can't download the android app).
Thank you!
Click to expand...
Click to collapse

Just wanted to ask you something. I installed the Nordic version of the latest Android update which is at the moment the only one available and I have the impression that the voice quality is not that good. I was wondering if this may depend on the baseband version installed on this one. I'm from Italy and kitkat 4.4 is still not available in my country. Flashing a different baseband may change the situation? If so, Is there a baseband more compatible with this touchwiz version and the Italian telco providers?
Thank you again,
Davide
Sent from my GT-N7105 using XDA Free mobile app

[SOLVED] I think my i747M may be soft bricked?

Hey all. I am fairly inexperienced when it comes to rooting, though I have done a few succesfully in the past. I currently have the newest version of TWRP installed on my Samsung I747M. The I747M I have is not from one of the major carriers, but as far as I am aware, the phone is factory network unlocked. Carrier is GCI, in Alaska.
I currently have a 4.4.2 Touchwiz Rom installed and started having problems after I attempted to flash the ROM Dandroid, which is 4.3 (http://forum.xda-developers.com/showthread.php?t=2121506). I had created a backup using TWRP before flashing the ROM and reverted back once I noticed the problem.
The main issue I am experiencing at this time is the Baseband Version, IMEI, and other information related to the modem is showing "Unknown" and features such as wifi will not toggle on.
I had also attempted to flash the most current version of the modem that I was able to find thru Odin. Odin showed the flash as successful. The version I flashed to the phone was I747MUMUEND3: modem_CWM_I747MUMUEND3.zip - 18.80 MB - April 3rd, 2014 (http://forum.xda-developers.com/showthread.php?t=1831898)
At this point, I can still get into recovery, download modem and I am able to boot up the phone and access most all functions. The next step I was going to try was going to be to flash back to stock firmware from sammobile's website (Was using to use the Roger's version of 4.4.2), though I don't want to cause more issues than I can handle or resolve thru software.
Any advice on how to proceed would be greatly appreciated or even just how to get the modem/wifi features functional again would be helpful. I'm just as happy staying on my current ROM at this point if I can get the phone fully functional again.

It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.

audit13 said:
It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.
Click to expand...
Click to collapse
Forgot to mention, this is something I did try. I attempted to flash Cyanogen Mod 12.1 (Download: cm-12.1-20151017-NIGHTLY-d2att.zip (286.76 MB) ) and most recent nightly build & the most recent stable release (CM11) (Download: cm-11-20140210-SNAPSHOT-M3-d2att.zip (194.37 MB) ). When flashing these, I transferred the downloaded ZIP file to the internal storage of the phone in the root directory and attempted to run an install from TWRP. Both installs failed.

Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: http://www.sammobile.com/firmwares/database/SGH-I747M/
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: https://dl.twrp.me/d2att/twrp-2.8.7.0-d2att.img.tar
Create a nandroid backup using TWRP and then try to flash a custom ROM again.

audit13 said:
Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
Create a nandroid backup using TWRP and then try to flash a custom ROM again.
Click to expand...
Click to collapse
I'll give that a shot when I get home. Stock firmware was one of my next thoughts. I have it downloading at the measly 15 Kbps offered for free from sammobile so hopefully should be done by the time I get home & update this thread with any progress.

Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in TMS3KK thread. The ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)

dawgdoc said:
Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the "http://forum.xda-developers.com/showthread.php?t=2725192"Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in http://forum.xda-developers.com/showthread.php?t=2725750" TMS3KK thread. The http://forum.xda-developers.com/showthread.php?t=1756776" ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)
Click to expand...
Click to collapse
I'm not opposed to any of this. Mostly just trying to slim down this phone to the basics as much as I can and am quite open to any recommendations. Main thing I want to maximize is battery life & simplicity since this is for my wife and those are her major wants in a phone. I figure any kind of ROM that just covers the basics should cover my bases & would prefer one with a darker/black skin to maximize battery life w/ the OLED screen. I am in the process of flashing to the Roger's stock ROM as I type this w/ my fingers crossed.
Just to add, no over clocking or anything of that nature is desired. If I remember correctly I ended up putting the ktoonsez kernel on one of my handsets, either this Galaxy S3 or my Galaxy S5, though I can't recall which since it was so long ago.

Alright! So progress! Wifi, Baseband version, IMEI and all other missing information restored & now works w/ stock rom flash. In process of reflashing TWRP now.

Let us know what happens.

Still all good with TWRP installed. Have not flashed back on a custom ROM yet. After reviewing some of the above recommendations, I am kind of liking the looks & features of TMS3KK (http://forum.xda-developers.com/showthread.php?t=2725750) and feel it would suit my needs.
I factory reset, cleared cache, and cleared Dalvik thru TWRP & then made a back up. Prior to this, I confirmed everything was still working normally w/ phone fully loaded after TWRP was installed.
One of the things mentioned on the installation instructions for that ROM is the following:
---
Do not mix and match 4.3 firmware (bootloaders/modem) with the new 4.4.2 ones. You will hard brick and I warned you. This works the same as any 4.3 or ND8port ROM with 4.3 firmware and it can use the new 4.4.2 ones also.
Link to recovery flashable i747 and i747M 4.4.2 bootloader and modem packages: http://forum.xda-developers.com/gala...hable-t2856914
---
How would I go about confirming my current bootloader/modem versions to make sure they are both 4.4.2 before flashing this ROM? At the link provided, those files/links to the files were removed because they were causing some bricked devices per a note at the top of that thread. Here's a link to the thread I am referencing since the above link looks to be broken. (http://forum.xda-developers.com/gal...mware-ne4-ne6-nf2-recovery-flashable-t2856914)

If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.

audit13 said:
If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.
Click to expand...
Click to collapse
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.

fodor362 said:
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.
Click to expand...
Click to collapse
Glad to hear the phone is running well.
I've heard it said "Happy wife, Happy life."

Still can't connect properly to the network

It's been another few months and still the same problems with all ROMS i try, when the screen is off i lose connection to the mobile network, When i turn the screen back on it will connect and start buzzing and alerting me to every unread message and e-mail Which gets annoying very quickly let alone missing messages and calls.
This happens on CM 12, Pac man rom, GPE and others. Both with 4.4.4 and 5.0. CM 11 works fine for me without this issue.
I see people say they are using these roms without this issue so something is definitely wrong but I can figure out what.
I'm using an Unlocked T mobile s4 on the Wind network In canada
Model SGH-M919
Baseband M919UVUAMDL

You may need to update the baseband a bootloader in order for the phone to work properly with the latest ROMs.
http://www.sammobile.com/firmwares/database/SGH-M919/

audit13 said:
You may need to update the baseband a bootloader in order for the phone to work properly with the latest ROMs.
http://www.sammobile.com/firmwares/database/SGH-M919/
Click to expand...
Click to collapse
Thanks for the reply, before i screw anything up there doesn't appear to be any explicit guides. I'm assuming i use this guide http://forum.xda-developers.com/showthread.php?t=2678774 with the OK3 Rom. beyond this is there anything i should know, like will i have to unlock and root my phone again, or anything like that?

The stock ROMs for the sgh-m919 are here: http://www.sammobile.com/firmwares/database/SGH-M919/
The simplest way to update to the latest bootloader and modem would be to flash the phone back to stock using the above-linked software.
Once you are on the latest stock ROM, flash the latest TWRP to the phone. Once TWRP has been installed, you can flash a custom ROM. Rooting first is not necessary if you intend to run a custom ROM.

audit13 said:
The stock ROMs for the sgh-m919 are here: http://www.sammobile.com/firmwares/database/SGH-M919/
The simplest way to update to the latest bootloader and modem would be to flash the phone back to stock using the above-linked software.
Once you are on the latest stock ROM, flash the latest TWRP to the phone. Once TWRP has been installed, you can flash a custom ROM. Rooting first is not necessary if you intend to run a custom ROM.
Click to expand...
Click to collapse
Sorry for the late update but I got it working thank you.
The FOK3 and FOH3 didn't work for me, once installed it still showed the MDL version. Once i did the FNK2 it worked.
Is there a reason to upgrade to the FOH3 or FOK3 from the FNK2 versions provided i can get them to work?

I always recommend running the latest bootloader and rom but, if the bootloader and modem work without issue, you can hold off.