Develop Bugs

Need help

I have the TMobile Galaxy s3 rooted on most recent stock firmware. I installed a new font using rom toolbox after backing up firmware with TWRP, so it though. After installing the font I got a message telling me to reboot for changes to take effect. Reboot hangs at the glowing Samsung logo. I have rebooted in to recovery and it comes up with CWM recovery vice TWRP some how? I know I flashed TWRP through rom toolbox but it didn't take apparently. I did get a message that backup was successful. CWM will not recognize TWRP backup. I need a flashable zip for the correct TWRP recovery. Could someone please point me in the right direction for the TWRP recovery file or to get me out of this boot loop. Should I just flash the stock firmware?

If you dl the tool all the recoverys
Are in there just flash team wins recovery thru Odin
Sent from my SGH-T999 using xda premium
---------- Post added at 07:40 PM ---------- Previous post was at 07:38 PM ----------
http://forum.xda-developers.com/showthread.php?t=1746682
Sent from my SGH-T999 using xda premium

funziebear said:
If you dl the tool all the recoverys
Are in there just flash team wins recovery thru Odin
Sent from my SGH-T999 using xda premium
I'm not following you what tool do I dl for all of the recoverys? Link?
Click to expand...
Click to collapse

I posted a link
Sent from my SGH-T999 using xda premium

Sweet! I didn't realize that a tool kit existed! Thanks for the help looks like this should do the trick.

dashhackinfread said:
Sweet! I didn't realize that a tool kit existed! Thanks for the help looks like this should do the trick.
Click to expand...
Click to collapse
When you install it and choose for the custom recovery it will open Odin and ull have I think 3 options for the T-Mobile s3 just choose the teamwinsrecory I think its the last one on the list and flash it thru Odin: ) hope it helps out
Sent from my SGH-T999 using xda premium

I was able to get the team win recovery but the backup I made did not show up there either. I guess I will have to flash the stock rom and start over again. I don't know what I did wrong, thought I had backed up with TWRP. Kinda weird how stock recovery comes back after a new one is flashed. If I reboot into recovery now I get stock after being able to access TWRP and rebooting. Next time I go in I am back in stock? Don't know I will have to find a fix after I get back to stock.

dashhackinfread said:
I was able to get the team win recovery but the backup I made did not show up there either. I guess I will have to flash the stock rom and start over again. I don't know what I did wrong, thought I had backed up with TWRP. Kinda weird how stock recovery comes back after a new one is flashed. If I reboot into recovery now I get stock after being able to access TWRP and rebooting. Next time I go in I am back in stock? Don't know I will have to find a fix after I get back to stock.
Click to expand...
Click to collapse
That happen to me but it was my fault I backed up and didn't check file size the folder was there but it was empty, just start over and make sure ur backups are there you should be able to just flash a rom if u have a card reader to transfer files onto SD card, that's what I did and I was back at it phone working 20 mins later
Sent from my SGH-T999 using xda premium

I'll give it a shot. What rom would you recommend? I was just rooted on stock b4. I was thinking about the Frosty JB rom.

dashhackinfread said:
I'll give it a shot. What rom would you recommend? I was just rooted on stock b4. I was thinking about the Frosty JB rom.
Click to expand...
Click to collapse
If you like the stick features something stock rooted, I'm running paranoid cuz its easier for me to use with one hand and i like the features on it
Sent from my SGH-T999 using xda premium

Cool! Thanks so much for your help. I just want back to stock for now as soon as the f/w is done dl'n I will let you know how it goes.

All is well now back to stock and going through the setup process. Going to re-root and stay away from rom toolbox this time.

How are you guys getting TWRP to install?

Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium

mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".

SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium

mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!

mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?

SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium

Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?

Did you ever get TWRP on your phone?

I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==

wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.

Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.

wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)

Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.

[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.

Root issues (moved from Virgin rom as requested) Help

I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....

Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app

th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?

I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4

I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app

I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app

th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app

If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.

norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again

th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.

mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew

SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!

th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app

See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!

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