Develop Bugs

T-MOBILE T999UVALEM firmware ready to play with :)

just want to let you know that T-Mobile firmware is ready for download
http://samsung-updates.com/device/?id=SGH-T999

Is this for odin
Sent from my SGH-T999 using Tapatalk 2

Can this be used with the t mobile variant
Sent from my SGH-T999 using Tapatalk 2

If this is for sprint, why does the title say T-Mobile..
Sent from my HTC One X using xda premium
Edit: In that case, thanks PP
Sent from my SGH-T999 using xda premium

Its for T Mobile.. if you click on the link it says its for the T999

I was wondering the same thing, but if it matters I went to the link and it says it's for T-Mobile T999UVALEM like the title
Sent from my SGH-T999 using xda app-developers app

Tweezydak1d said:
Is this for odin
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
yes it is - same firmware as you would get updting with kies
anthonykash said:
Can this be used with the t mobile variant
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
ye, it is tmobile version i am tired and made a typo - corrected thnks and gnite

my phone came with this firmware. is this just posted to revert to stock if on a custom rom or is there other significance?

Has anyone tried flashing yet?
Sent from my SGH-T999 using xda app-developers app

So this must mean we can flash fash back to stock with odin if we have problems.

yup! this is our fall back ROM. now we need a triangle away to reset the counter!

It Works
I decided to be the test monkey on this one.
I had a nandroid backup of when I screwed my system so badly it just boot looped repeatedly. Restored that with cwm, verified it was still hosed, unpacked this zip, used odin to burn the .tar.md5 to the phone as PDA, rebooted.
It does some gear chunking while booting the first time then reboots - don't panic yet! On second boot it does some more rebuilding, then 'WELCOME!'
Bonus: CWM now sees the actual external sdcard as /sdcard and can find things like roms and backups on it. Edit: This CWM finds .zips on the sdcard, but doesn't seem to know how to backup/restore.

So is this for un rooting our phones?
Sent from my SGH-T999 using xda premium

sizer99 said:
I decided to be the test monkey on this one.
I had a nandroid backup of when I screwed my system so badly it just boot looped repeatedly. Restored that with cwm, verified it was still hosed, unpacked this zip, used odin to burn the .tar.md5 to the phone as PDA, rebooted.
It does some gear chunking while booting the first time then reboots - don't panic yet! On second boot it does some more rebuilding, then 'WELCOME!'
Bonus: CWM now sees the actual external sdcard as /sdcard and can find things like roms and backups on it. Edit: This CWM finds .zips on the sdcard, but doesn't seem to know how to backup/restore.
Click to expand...
Click to collapse
What do you mean "This CWM" ? The tars we're talking about in this thread are completely stock from samsung, there is no CWM in these... please elaborate.

hiazn said:
What do you mean "This CWM" ? The tars we're talking about in this thread are completely stock from samsung, there is no CWM in these... please elaborate.
Click to expand...
Click to collapse
After burning this with Odin I ended up with a CWM that I didn't expect - and I've never seen one that actually recognized the external card. However, with all the things I've been trying it's quite possible I ended up burning a boot image I forgot about. I need to try reburning this and see if anything changes, but can't do it right now.

sizer99 said:
After burning this with Odin I ended up with a CWM that I didn't expect - and I've never seen one that actually recognized the external card. However, with all the things I've been trying it's quite possible I ended up burning a boot image I forgot about. I need to try reburning this and see if anything changes, but can't do it right now.
Click to expand...
Click to collapse
Sounds like a plan, let us know what you find.

is this actually
T999UVALEM
or
T999UVLEM

M9x3mos said:
is this actually
T999UVALEM
or
T999UVLEM
Click to expand...
Click to collapse
Mine stock is T999UVLEM, whats the difference between the two?

does this restore everything, including stock recovery, but resetting the counter?

Strange - I had kind of a weird experience with this. I flashed via Odin as usual (as I've done a 100x before) and when it rebooted, it still had remnants of the previous rom I had installed. I didn't get the "welcome" screen as if I was starting from a new factory rom. but at least it got me back to step 1 and I could flash the Lean 2.1 rom again to repair my screw ups.

[Q] CWM Recovery on i317M

Hi,
I'm having issues installing CWM Recovery on my Rooted GN2. It's the Canadian variant, SGH-I317M.
It does go through the process of flashing the recovery, but never gets to saying PASS in ODIN. When I try to get into the Recovery, it still has the stock Samsung Recovery. It does, however trip the flash counter.
I'm followiing the instructions here: http://forum.xda-developers.com/showthread.php?t=1988785
This is what I get after flashing in ODIN.

Maybe a bad download? Have you checked to see if it installed? I dont usually recommend this but koush's Rom Manager supports our device now, you can use the app to flash it if your already rooted:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

In your screen shot it shows the f-reset box checked I believe it should be unchecked.

Slff said:
In your screen shot it shows the f-reset box checked I believe it should be unchecked.
Click to expand...
Click to collapse
I tried it with the f-reset box unchecked, and I got it to say PASS, but still no CWM...
cdshepherd said:
Maybe a bad download? Have you checked to see if it installed? I dont usually recommend this but koush's Rom Manager supports our device now, you can use the app to flash it if your already rooted:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I've also tried to download the file again, and still... No dice...

BlueBagodah said:
I tried it with the f-reset box unchecked, and I got it to say PASS, but still no CWM...
I've also tried to download the file again, and still... No dice...
Click to expand...
Click to collapse
Try rom manager?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

cdshepherd said:
Try rom manager?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
ROM Manager doesn't have a Recovery for the Rogers i317M...

http://forum.xda-developers.com/showthread.php?t=1988785
Sent from my SAMSUNG-SGH-I317 using xda premium

twanskys204 said:
http://forum.xda-developers.com/showthread.php?t=1988785
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks,
I've been following that thread, and it doesn't work. It will trip the flash counter, but doesn't actually install the recovery. It appears that I'm not the only one having this issue after the most recent OTA update...

Can u try and flash a kernel
Then try flashing cwm ...just a hunch
Sent from my SAMSUNG-SGH-I317 using xda premium

BlueBagodah said:
Thanks,
I've been following that thread, and it doesn't work. It will trip the flash counter, but doesn't actually install the recovery. It appears that I'm not the only one having this issue after the most recent OTA update...
Click to expand...
Click to collapse
I'm also having problems after the OTA update. Before OTA update, I was able to flash CWM without problems. Following exact same procedure as before when it was working. Only variable that changed is the OTA update.

wiser212 said:
I'm also having problems after the OTA update. Before OTA update, I was able to flash CWM without problems. Following exact same procedure as before when it was working. Only variable that changed is the OTA update.
Click to expand...
Click to collapse
I was able to install CWM by following this post: http://forum.xda-developers.com/showpost.php?p=36201055&postcount=54
But I'm starting to think that it may have been my fault the whole time...
While doing the 3 button combo to try to boot into Recovery, I was using Vol-DOWN, instead of Vol-UP. So I was going into download mode. I'm going to try flashing the CWM through ODIN again and see if I was just an idiot the whole time.
***EDIT***
It looks like I was just an idiot the whole time...

*facepalm*
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

.. so ROM manager doesnt work to insall cwm recovery after rooting on the i317m? i tried it and didnt succeed. i guess flashing is my only option but i dont want to lose anything on my phone. just install the bootloader/ recovery with no other changes. i want to start flashing some roms... jedi first.. skynote after.. any thoughts or help would be great!!

Clean rom I would suggest its awesome battery life I have a universal theme flashed over clean rom and a custom blue keyboard if I find the link to the themes ill post em on here
Sent from my sgh-1317 aka MY BLUE DEVIL using xda premium

Dewaynelives said:
Clean rom I would suggest its awesome battery life I have a universal theme flashed over clean rom and a custom blue keyboard if I find the link to the themes ill post em on here
Sent from my sgh-1317 aka MY BLUE DEVIL using xda premium
Click to expand...
Click to collapse
I thought of cleanROM but it is pretty stock. I feel if im going to flash any rom i might as well go with something modded and tweaked rather then stock, while keeping most of the note 2 and s-pen features. If i start finding them being a little buggy or draining my battery or anything, ill settle with cleanROM and just flash some custom mods.
i flashed my CWM through MobileODIN. worked like a charm. then i ran into issues with backing up to extSD, which ended up working after i formatted it but i took way longer then onto internal SD.
i know its off topic for this thread..Any suggestions or thoughts on the JEDI X9 and SKYNOTE roms will be great guys. Im all backed up and ready to flash pretty quick here.

I guess you have custom ROM. You must root and rename recovery restore files before you boot to android or stock recovery will be restored.

[Q] t999 pacman rom install issues

I can't get any version of pacman ROM to install. I'm using the latest twrp. I perform a full wipe each time and the install fails each time...it says something about partitions in the final line of text after the install fails. I've been around the block a few times but I still consider myself to be a noon. Please help.

Iceberg1914 said:
I can't get any version of pacman ROM to install. I'm using the latest twrp. I perform a full wipe each time and the install fails each time...it says something about partitions in the final line of text after the install fails. I've been around the block a few times but I still consider myself to be a noon. Please help.
Click to expand...
Click to collapse
First Roll back to version 2.5.0.0 of TWRP. In TWRP version 2.6.x.x, there are known issues in Data Partition mount or wipe.

Ok try that tonite. Thanks
Sent from my SGH-T999 using XDA Premium 4 mobile app

Just tried it out and it failed again. Now it says - assert failed : getprop("ro . Bootloader") = t999UVDLJC =T999UVDMD5 , it also says error executing updater binary in zip
Sent from my SGH-T999 using XDA Premium 4 mobile app

Iceberg1914 said:
Just tried it out and it failed again. Now it says - assert failed : getprop("ro . Bootloader") = t999UVDLJC =T999UVDMD5 , it also says error executing updater binary in zip
Click to expand...
Click to collapse
You need to update your Bootloader. Its named the same as the baseband. If you feel technically savvy enough then try this thread to do so. If not, then try Flashing Rooted Stock Rom UVDMD5 from Root66 thread.

You'll prob need a newer recovery too. I think TWRP issues are mostly in 2.6.3.0
Use 2.6.1.0 instead is my recommendation if updating the firmware doesn't solve it.
Sent from my SGH-T999V using Tapatalk 4

DocHoliday77 said:
You'll prob need a newer recovery too. I think TWRP issues are mostly in 2.6.3.0
Use 2.6.1.0 instead is my recommendation if updating the firmware doesn't solve it.
Click to expand...
Click to collapse
@DocHoliday77 I didn't reccomend 2.6.1.0 since even that gave me the same Data Partition problem. Please see my github post.

Perseus71 said:
@DocHoliday77 I didn't reccomend 2.6.1.0 since even that gave me the same Data Partition problem. Please see my github post.
Click to expand...
Click to collapse
Oh, ok. I only remembered seeing people report it on the latest, sorry. I never ran into any issues with it myself, but I didn't use it much either, so I may have just not triggered any bugs while on that version.
Thanks!
If the OP still has the binary error after flashing the firmware though, it may be because of the older recovery at that point.
Sent from my SGH-T999V using Tapatalk 4

SUCCESS!!!!!
Sent from my SGH-T999 using XDA Premium 4 mobile app

Thank you guys
Sent from my SGH-T999 using XDA Premium 4 mobile app

Iceberg1914 said:
Thank you guys
Click to expand...
Click to collapse
If your problem is solved, please ask to have the thread closed.
P.S. - Just FYI the best way to thank on XDA is 1 click on that Thanks button for anyone who helped you.

[Q] What does RQT_CLOSE mean?

I am at the point where my AT&T Note 2 SGH-i317 either displays the Samsung Note II screen or I can go into the Odin screen. It will not open recovery.
If I try to install CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin, I get the message from the title.
Odin appears to load the factory 4.1 rom but I end up with the same message at the end.
I had successfully restored 4.1 using Odin and then the phone auto updated to 4.3. After that, I followed the instructions for installing Jedi Master but the phone won't restart. I tried to use the same files I got 4.1 back with (this has worked twice before from 4.3) but they will no longer work. Is there anything I can do to get the phone working again?

mid_life_crisis said:
I am at the point where my AT&T Note 2 SGH-i317 either displays the Samsung Note II screen or I can go into the Odin screen. It will not open recovery.
If I try to install CF-Auto-Root-t0lteatt-t0lteatt-samsungsghi317.tar.md5 using Odin, I get the message from the title.
Odin appears to load the factory 4.1 rom but I end up with the same message at the end.
I had successfully restored 4.1 using Odin and then the phone auto updated to 4.3. After that, I followed the instructions for installing Jedi Master but the phone won't restart. I tried to use the same files I got 4.1 back with (this has worked twice before from 4.3) but they will no longer work. Is there anything I can do to get the phone working again?
Click to expand...
Click to collapse
Which version of odin are you using?
Can you enter stock recovery or only download mode?
If you can get into stock recovery if it says anything about knox then you have the new bootloader, which you should if you updated to 4.3 via an ota update or an odin file. If you have this we can skip a few steps. If you don't, we will basically be starting from the beginning.
Assuming you have the newer bootloader, this is what I need you to do.
Go to teamw.in and download the latest twrp and make sure it's the recovery.img.tar.md5 flash that through odin.
In the mean time start a fresh download of jedi masterx2. When that download finishes make sure you verify the md5 sum. This is key. One digit off and the entire download is bad and you'll end up bootlooping again.
Once you have twrp and a good download of jmx2 boot into twrp. Do a system wipe and then flash the rom.
Let me know how it works. Just be patient and we can get this fixed for you. As long as you can power on you can recover your phone and make it work.
Sent from my SM-N900T using XDA Premium 4 mobile app

I use an app called hash droid to verify md5
Sent from my Jedi MasterX Note 2

kushXmaster said:
Which version of odin are you using?
Can you enter stock recovery or only download mode?
If you can get into stock recovery if it says anything about knox then you have the new bootloader, which you should if you updated to 4.3 via an ota update or an odin file. If you have this we can skip a few steps. If you don't, we will basically be starting from the beginning.
Assuming you have the newer bootloader, this is what I need you to do.
Go to teamw.in and download the latest twrp and make sure it's the recovery.img.tar.md5 flash that through odin.
In the mean time start a fresh download of jedi masterx2. When that download finishes make sure you verify the md5 sum. This is key. One digit off and the entire download is bad and you'll end up bootlooping again.
Once you have twrp and a good download of jmx2 boot into twrp. Do a system wipe and then flash the rom.
Let me know how it works. Just be patient and we can get this fixed for you. As long as you can power on you can recover your phone and make it work.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odin shows the Knox flag, so I assume I am on 4.3.
I cannot find this file, "recovery.img.tar.md5".
The most likely looking file I found was this, but it isn't an md5, "openrecovery-twrp-2.6.3.1-t0lteatt.img.tar".
In fact I find no files with an "md5" extension on that site.

mid_life_crisis said:
Odin shows the Knox flag, so I assume I am on 4.3.
I cannot find this file, "recovery.img.tar.md5".
The most likely looking file I found was this, but it isn't an md5, "openrecovery-twrp-2.6.3.1-t0lteatt.img.tar".
In fact I find no files with an "md5" extension on that site.
Click to expand...
Click to collapse
I apologize. For the recovery.img it needs to be the tar extension.
Once you push that to the device you're back in business.
Sent from my SM-N900T using XDA Premium 4 mobile app

kushXmaster said:
I apologize. For the recovery.img it needs to be the tar extension.
Once you push that to the device you're back in business.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I gave you a thanks because I truly appreciate the attempt to help me, but that wouldn't load either.
Fortunately the guy at the Samsung counter was able to use a Samsung loader to force 4.3 and the phone is working again.

Just curious - is your knox warranty counter back to zero in download mode?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

mid_life_crisis said:
I gave you a thanks because I truly appreciate the attempt to help me, but that wouldn't load either.
Fortunately the guy at the Samsung counter was able to use a Samsung loader to force 4.3 and the phone is working again.
Click to expand...
Click to collapse
Hmm that us interesting. I wonder why it wouldn't load...
What version of odin do you use? I've been using 3.07 for a long time with no issues.
I'm curious about the knox counter as well.
Sent from my SM-N900T using XDA Premium 4 mobile app

Zen Arcade said:
Just curious - is your knox warranty counter back to zero in download mode?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Neither counter reset. It still displays the count for custom roms and a "1" for the Knox toggle.

kushXmaster said:
Hmm that us interesting. I wonder why it wouldn't load...
What version of odin do you use? I've been using 3.07 for a long time with no issues.
I'm curious about the knox counter as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's 3.7

That's good and weird at the same time.
Its good because its what we expected AND that the Samsung person fixed your phone even though you tripped the KNOX bit.
Its weird because the Samsung person fixed your phone even though you tripped the KNOX bit.

Soft Bricked? Stuck at boot screen.

Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?

BWolf56 said:
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
Click to expand...
Click to collapse
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.

BWolf56 said:
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
Click to expand...
Click to collapse
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's in your System folder. Should be able to navigate to it using your recovery.

BWolf56 said:
It's in your System folder. Should be able to navigate to it using your recovery.
Click to expand...
Click to collapse
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?

donutkidd said:
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
Click to expand...
Click to collapse
Hopefully it is. And I duno about the command, you'll have to look that one up (or perhaps someone here knows it).

If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk

Ok I will try that when I get home.
Sent from my SM-N900T using XDA Premium 4 mobile app

DocHoliday77 said:
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ok I did the getprop ro.bootloader command and it's I747UCDLK3. I have already tried the lk3 Odin but let me try to re download a fresh copy of it.
Sent from my SM-N900T using XDA Premium 4 mobile app

No dice, I even downloaded a 4.1.1 lk3 rom. It flashed and said successful so I rebooted and back to the blue Android. Is it possible NY partitions or whatever are corrupt and if so anyway to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app

I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.

DocHoliday77 said:
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
Click to expand...
Click to collapse
I honestly think I tried what you suggested already but just to triple check I will do so again in the morning and report back with hopefully good news.
Sent from my SM-N900T using XDA Premium 4 mobile app

@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?

DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
No, nothing for 4.1.1 (LK3).
I don't think that's his issue though. Last time I saw that issue was on the S1 (Captivate) and the solution was to use Heimdall.
If the repartition doesn't work though, I'm not exactly sure what will.

DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.

donutkidd said:
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
Click to expand...
Click to collapse
Do you have the actual link to that thread? Search is derping on me.

BWolf56 said:
Do you have the actual link to that thread? Search is derping on me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouff that's one bad issue, it can take a while to figure out which partition got messed up. And sadly, I can't be much help there :/