Develop Bugs

Failed Root Attempt On Previously Unrooted I317UCALK7 - Bricked?

I wanted to try an AKOP ROM or two on my completely stock, never rooted Note 2 running the OTA UCALK7 update. I followed the guide here (flash the SU injected stock UCALJ2 image) to root and now my note gets stuck at the Samsung logo. I have tried the following:
Downloaded the completely stock UCALJ2 unrooted image and flashed via ODIN.
Tried flashing both stock and rooted ROMs on another computer using the stock USB cable.
Flashed CWM touch via ODIN after flashing rooted UCALJ2 image, it can boot to CWM but fails miserably most likely to the lack of root.
My guess is it's bricked because sammy closed the root hole in the UCALK7 update and flashing back to rooted UCALJ2 isn't enough to bypass the patched exploit. Is there an ODIN flashable complete UCALK7 image that I can try (I've looked to no end, all I can find are rooted zips flashable via CWM) or am I really up the creek?

Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.

shakabra said:
Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.
Click to expand...
Click to collapse
Thanks but I can get into Odin and flash the stock ROM just fine. It then reboots and gets stuck at the Samsung logo.

Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium

twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
The three finger salute lol:thumbup:
Sent from my GT-N7105 using Tapatalk 2

twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks - I actually figured that part out since my second post. The phone boots after the factory reset however I don't get phone/data service. I've since tried flashing the two AT&T modems I could find, atti317ucalj2modemfixed.zip and ATT K7 Modem - Baseband.zip. Neither resolve the issue.

Cheack ur apn
Sent from my SGH-I317 using xda premium

twanskys204 said:
Cheack ur apn
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks but I can't even enter the network configuration settings - it tells me to insert a SIM. My SIM is in the phone.

I'm having other problems too which I think are partition related. Apps are acting funny, saying there isn't space on the phone (dropbox can't download anything, etc). I'm trying to get TriangleAway installed so I can just RMA it but I can't even download it to my phone. Also a CWM fix permissions fails even though I grant it root access.

It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium

twanskys204 said:
It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
I know what you're saying, I'm definitely using the right file and process. I'm a pretty seasoned veteran when it comes to rooting/odin/RSD/fastboot, etc. I've run custom ROMs on dozens of phones since the G1. What's happening to me is apparently not a common failure with the note 2 or GS3. Is there a PIT file available for the AT&T Note 2? I see one for the Verizon Note 2 but I wouldn't dare try to flash that.

There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium

twanskys204 said:
There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Yeah, it's a tar file I'm flashing through Odin, got it from SamsungUpdates: Samsung-Updates.com-SGH-I317_ATT_1_20121005095854_bpaaavv07o.
I also tried flashing the stock ROM in deodex'd zip form after I got a custom recovery on there, still no dice. The non-functioning modem and lack of proper root/storage affects both Sammy and CM/AKOP based ROMs. I don't know about the modem part but I've seen weird things like this when the NAND starts going bad and things written to it don't "stick." I don't think that's the case here since it's only on its 4th or 5th flash. More than likely the latter problem is a file system issue. I have no idea about the radio.
I'm going to try and exchange it tomorrow. At least I got the flash count cleared and I'm back on a stock ROM (with the same problems).

[Q] Returning to stock

Wifi won't stay on for me. Will these steps get me back to 100% stock, no root?
Put phone in download mode (vol down + power)
Download ODIN 3.09:
http://odindownload.com/
Download CF-AutoRoot and root the phone here (instructions are in post 2):
http://forum.xda-developers.com/showthread.php?t=2294005
Install and run Triangle Away:
http://forum.xda-developers.com/galaxy-s2/orig-development/2013-10-04-triangleaway-v3-10-t1494114
Reboot.
Turn phone off.
Boot into download mode again.
Go back to ODIN:
Download office 4.4.2 firmware from (search for m919, first file: M919UVUFNB4M919UVUFNB4):
http://www.sammobile.com/firmwares/
Put that .tar file in the pda slot and run.
Profit?
Missing anything? I know running that .tar will update my bootloader but at this point I don't care.

DizDroid said:
Wifi won't stay on for me. Will these steps get me back to 100% stock, no root?
Put phone in download mode (vol down + power)
Download ODIN 3.09:
http://odindownload.com/
Download CF-AutoRoot and root the phone here (instructions are in post 2):
http://forum.xda-developers.com/showthread.php?t=2294005
Install and run Triangle Away:
http://forum.xda-developers.com/galaxy-s2/orig-development/2013-10-04-triangleaway-v3-10-t1494114
Reboot.
Turn phone off.
Boot into download mode again.
Go back to ODIN:
Download office 4.4.2 firmware from (search for m919, first file: M919UVUFNB4M919UVUFNB4):
http://www.sammobile.com/firmwares/
Put that .tar file in the pda slot and run.
Profit?
Missing anything? I know running that .tar will update my bootloader but at this point I don't care.
Click to expand...
Click to collapse
As far as I know triangle away is not working for 4.3 or 4.4 yet.
Sent from my SGH-M919 using XDA Free mobile app

mrzhadow said:
As far as I know triangle away is not working for 4.3 or 4.4 yet.
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
Well crap.
If I update this way will I still encounter annoying phone is rooted messages? Ultimately main goal here is to have stock recovery, wifi working (turning on/off, won't stick) and non rooted stock 4.4.2.
Thanks for the quick response.
EDIT: According to Chainfire's thread seems that its been updated as well. :-/

DizDroid said:
Well crap.
If I update this way will I still encounter annoying phone is rooted messages? Ultimately main goal here is to have stock recovery, wifi working (turning on/off, won't stick) and non rooted stock 4.4.2.
Thanks for the quick response.
EDIT: According to Chainfire's thread seems that its been updated as well. :-/
Click to expand...
Click to collapse
Have you tried editing your build.prop? What kernel are you using. Ktoonzes works perfect but you have to edit 2 lines. It will most likely fix your WiFi
Sent from my SGH-M919 using xda app-developers app

mrzhadow said:
Have you tried editing your build.prop? What kernel are you using. Ktoonzes works perfect but you have to edit 2 lines. It will most likely fix your WiFi
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
No edits. Stock kernel.
Phone is being sold and don't feel right leaving them with anything tither than stock.

DizDroid said:
No edits. Stock kernel.
Phone is being sold and don't feel right leaving them with anything tither than stock.
Click to expand...
Click to collapse
OK you are correct about triangle away. It now supports KitKat. You can go back to stock the way you stated above but keep in mind that it will only reset your binary counter. It will not reset your Knox security.
Sent from my SGH-M919 using xda app-developers app

Stuck in brickloop, Tried odin stock firmware, no go

Hello all!
So I bought a SGH M919 s4 off craigslist for 150 knowing that it wouldn't boot past the Samsung galaxy s4 boot screen, Thinking it would be an easy fix by flashing the stock firmware through odin. Well that's not the case, I've tried just about everything I am capable of...
1.Both odin 3.0 7 and odin 3.0 9 both flash and the device passes but on the boot screen it says booting recovery and just sticks there, It stuck on that over night so I am being patient.
2. I've tried flashing 4.3 which fails right away leading me to believe the phone was updated to 4.4.2 at some point in time.
3. It wont let me boot into stock recovery or I've even tried flashing TWRP, CWM and it pass's but still will not let me boot into those recovery's either.
4. Tried rooting the phone a couple times and that passes in odin but does nothing after that.
5. I ve tried different phone cables, I haven't tried a different computer yet.
6. The only thing I can get into on the phone is download mode and it says this on the screen
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTYVOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: enable
eMMC BURST MODE enable
I don't remember seeing those last two things on the list normally if I can recall. Any help will be greatly appreciated and possibly a donation if we can get this thing fixed. Thanks.

Repartition it with the pit file while youre installing the firmware.
Last 2 strings are normal.
Sent from my SGH-M919 using XDA Premium 4 mobile app

ShinySide said:
Repartition it with the pit file while youre installing the firmware.
Last 2 strings are normal.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, Do you know where the pit file can be found or what do I write in the pit file box?

Ok so I pulled the pit file from another T-Mobile s4 I have and flashed that with the stock firmware and that didn't work. The phone I pulled the pit file from is on 4.3 still so I'm assuming that's why it didn't work???

Quickvic30 said:
Ok so I pulled the pit file from another T-Mobile s4 I have and flashed that with the stock firmware and that didn't work. The phone I pulled the pit file from is on 4.3 still so I'm assuming that's why it didn't work???
Click to expand...
Click to collapse
Na that wouldnt matter. Your pit file is for your partition layouts. Which dont ever change.
I really cant think of anything else of why you can't get into recovery or boot the phone with everything you've tried. You might just need to Jtag the device
Sent from my SGH-M919 using XDA Premium 4 mobile app

ShinySide said:
Na that wouldnt matter. Your pit file is for your partition layouts. Which dont ever change.
I really cant think of anything else of why you can't get into recovery or boot the phone with everything you've tried. You might just need to Jtag the device
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help, I might jtag it or just try to find a used motherboard :laugh:

Quickvic30 said:
Thanks for the help, I might jtag it or just try to find a used motherboard :laugh:
Click to expand...
Click to collapse
The OP mentions that you tried flashing 4.3 and you speculated if it had been updated to 4.4.2. Just out of curiosity, have you tried flashing the stock 4.4.2 firmware?

lordcheeto03 said:
The OP mentions that you tried flashing 4.3 and you speculated if it had been updated to 4.4.2. Just out of curiosity, have you tried flashing the stock 4.4.2 firmware?
Click to expand...
Click to collapse
Yes I've been to flashing 4.4.2 and it passes Odin. I think maybe you meant have I tried flashing 4.2.2? I have not tried flashing 4.2.2 firmware yet, I might try that but 4.2.2 didn't have the Knox counter did it?
Sent from my SM-G900A using XDA Free mobile app

Quickvic30 said:
Yes I've been to flashing 4.4.2 and it passes Odin. I think maybe you meant have I tried flashing 4.2.2? I have not tried flashing 4.2.2 firmware yet, I might try that but 4.2.2 didn't have the Knox counter did it?
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
No, I meant 4.4.2. It was a dumb question, but sometimes it's the simple things you overlook. Like I said, the OP only said you tried flashing MK2. You won't be able to flash anything pre-KNOX so there's no need in wasting the time downloading the MDL firmware.
An idea would be to power the phone off, boot straight to download mode, flash NB4, pull the battery when it's complete, boot straight back to download mode and re-flash NB4. I know that you have to do that sometimes for the modem to stick, perhaps you could try that with the firmware itself. Hey, worth a shot. Good luck.

lordcheeto03 said:
No, I meant 4.4.2. It was a dumb question, but sometimes it's the simple things you overlook. Like I said, the OP only said you tried flashing MK2. You won't be able to flash anything pre-KNOX so there's no need in wasting the time downloading the MDL firmware.
An idea would be to power the phone off, boot straight to download mode, flash NB4, pull the battery when it's complete, boot straight back to download mode and re-flash NB4. I know that you have to do that sometimes for the modem to stick, perhaps you could try that with the firmware itself. Hey, worth a shot. Good luck.
Click to expand...
Click to collapse
I think I might have tried flashing twice in a row but I'll try it again since I haven't tried that since I've flashed the pit file. Thanks for the tip and I'll report back after the double flash.
Sent from my SM-G900A using XDA Free mobile app

So I flashed it, pulled the battery and flashed it again and still the same thing......:sigh: lol Time to look for another wrecked phone for spare parts

Bought a phone off cl with a cracked screen and swapped the motherboard into the phone and it works like a champ now! :thumbup:
Sent from my SM-G900A using XDA Free mobile app

[Q] Samsung Galaxy S4 M919 can't get past PIT partition

Hello! Let me start by saying that i have researched a ton and there is a lot of great information on here. The info I've read however doesn't seem to work for me.
My situation is I spilled a little bit of water on my phone (really not much), but it got inside my phone a little, which was already rooted using auto root. My power button thinks its constantly being pushed (i think). It doesn't bootloop, but as soon as i pop the battery in it turns on, and my phone was unresponsive to me clicking the power button. The rest of the phone was fully functional and i checked with Tmobile and it is still under warrenty (didn't mention the water). They told me to backup the phone which i was able to do in kies with no problem. Then they said do a factory reset, which again I did with no problem. It didn't solve my issue which i kinda knew it wouldn't, so the next step for me was to unroot my phone so i can return it. I popped it in odin, selected the original firmware and it started , then it disconnected by itself. Now the firmware upgrade screen pops up, but i am still able to get it into download mode (for me since the power button is suspect) i just have to hold the home and volume down, pop in the battery and it goes to download mode. The problem is that every time i try to hit start in Odin it gets to the part about the PIT partition and disconnects and says there is no PIT partition. Everywhere i've read says to either use a PIT partition (can't find one for the M919) or that the partition is in the m5 file, which as far as i can tell it is not (at least not it's own file). I've tried downloading the stock firmware from a multitude of different places even Sammobile with no luck and I've also tried different computers, different cables, and all the USB ports available to me.
Can anyone please tell me where to go from here please? I need to get this replaced asap!
(sorry i also posted this in the general section on accident)
I really think I just need the PIT partition, but I can't seem to find one for the m919 model
I have also tried different version of Odin (1.85, 3.07, and 3.09) all with the same result

What stock firmware are you trying to flash?
4.4.2?
Sent from my SGH-M919 using XDA Premium 4 mobile app

i think so. the name of the file is M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5

Ace$$ said:
i think so. the name of the file is M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5
Click to expand...
Click to collapse
When you're in download mode do you see anything that mentions KNOX in the upper-left hand corner? I only ask because MDL (4.2.2) firmware is the pre-KNOX firmware and will have no mention of KNOX in the text in download mode; it also will not flash if your bootloader has been updated to MK2 (4.3) or NB4 (4.4.2).

You're trying to flash mdl to a phone that won't take it. (ie it's already been updated to mk2 or nb4).
I'd flash the mk2 or nb4 tar file.
Sent from my SGH-M919 using XDA Premium 4 mobile app
---------- Post added at 12:56 AM ---------- Previous post was at 12:55 AM ----------
You can get them here: http://forum.xda-developers.com/showthread.php?t=2816508
Sent from my SGH-M919 using XDA Premium 4 mobile app

no nothing about knox.
Fu** yeah!! :fingers-crossed: that looks like it might be the problem. i'll download and post how it goes

Ace$$ said:
no nothing about knox.
Fu** yeah!! :fingers-crossed: that looks like it might be the problem. i'll download and post how it goes
Click to expand...
Click to collapse
If the string "KNOX WARRANTY VOID:" doesn't appear in download mode, then your phone has not been updated to 4.3 or 4.4.2 as android_monsters stated. MDL should have flashed as there was nothing related to the bootloader or KNOX keeping you from a successful flash.
One thing I did encounter myself while trying to re-flash my pre-KNOX device; did you ever update your modem/baseband to MK2 or NB4? If you did, I would recommend finding the individual MDL modem/baseband files and manually reverting them before flashing the stock MDL firmware again. Odin never failed for me at the device .pit file, but I did encounter the firmware upgrade screen while trying to revert to stock with an updated modem. Doesn't make sense to me as the stock firmware has the modem and all in it, but that fixed it for me.

That did the trick all right! :victory: :victory:
Thanks!

SAVED :angel:

I had the same problem but when i tried to flash the lastest firmware its stock on samsung logo... anyone can help me?

Ace$$ said:
That did the trick all right! :victory: :victory:
Thanks!
Click to expand...
Click to collapse
Reverting the modem before flashing the stock firmware fixed your problem? Awesome! :highfive:

Hold the power button and the volume up button and try booting into recovery,
Wipe cache
3 times
Wipe dalvik
3 times
Wipe system
3 times
Reflash rom
1 time
Wipe cache
At least 1 time
Reboot or
Flash gapps
(Only if needed)
If that doesn't help, then maybe try a different rom?
Sent from my GT-I9505G using XDA Free mobile app

Infamous_CA said:
I had the same problem but when i tried to flash the lastest firmware its stock on samsung logo... anyone can help me?
Click to expand...
Click to collapse
I'm assuming you're flashing the stock firmware via Odin... if that's the case, simply factory reset via stock recovery and you should be good to go.

lordcheeto03 said:
I'm assuming you're flashing the stock firmware via Odin... if that's the case, simply factory reset via stock recovery and you should be good to go.
Click to expand...
Click to collapse
I tried but it dosnt show recovery.. I flash a recovery but it dossnt boot on recovery. It show samsung galaxy but the screen turn in black.. I think that maybe it a board problem.
Sent from my HTC One X using XDA Premium 4 mobile app

Infamous_CA said:
I tried but it dosnt show recovery.. I flash a recovery but it dossnt boot on recovery. It show samsung galaxy but the screen turn in black.. I think that maybe it a board problem.
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try re-flashing the stock firmware in Odin. Don't flash a custom recovery at this point, just the stock firmware. Once it passes in Odin, power it off. Hold Power + Volume Up while powering up. It should show the Galaxy S4 screen with "Booting Recovery" in the upper-left.

Yes it say that on blue letters but dosnt show the recovery menu
Sent from my HTC One X using XDA Premium 4 mobile app

Infamous_CA said:
Yes it say that on blue letters but dosnt show the recovery menu
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ah. Well I don't know what to say; perhaps someone else may know? Sorry and good luck.

lordcheeto03 said:
Ah. Well I don't know what to say; perhaps someone else may know? Sorry and good luck.
Click to expand...
Click to collapse
Thanks for ur help man.
Sent from my HTC One X using XDA Premium 4 mobile app

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 :/