Develop Bugs

[REF] Modem / Radio Collection (M919 I9505) Odin Flashable MDL

All modems (radio / baseband) here are for the T-Mobile M919 I9505 variant only!!
i've seen quite a few people around the threads looking for just modems so figured i'd share. i'll try to keep the thread up to date as our new firmwares release. i'll look into making CWM for those that may want it to be flashable but for now
please follow these instructions
with Odin:
Extract the contents of 7zip/zip archive. Put it in your Odin folder. Do not try to extract files from the .tar.md5.
Run Odin 3.07.exe, and prepare Odin:
1. Check "auto-reboot", and uncheck all other options.
2. Click Phone and select the TAR.md5 you downloaded. Leave other fields empty.
3. Don't panic. Odin may freeze while it checks the MD5 signature of the TAR. This is normal.
* Put your device into Download Mode:
5. Power down fully and disconnect the USB cable.
6. Hold Volume Down + Home + Power.
7. You should now be at Download Mode. Connect your device and wait for it to be recognized.
8. Click Start in Odin.
9. Wait!
10. Device will auto reboot
UVUAMDL Baseband - 05.07.2013

This should be stickied
Sent from my SGH-T999 using xda app-developers app

Can someone make is twrp flashable?

Lolento said:
Can someone make is twrp flashable?
Click to expand...
Click to collapse
it's a two part file so i'm not sure that's possible yet. i'll have to look into it tmw when i have time. if anyone else knows how to, i'll def add it to the OP.

xXchrizhurtyXx said:
This should be stickied
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ditto!
Sent from my Nexus 7 using xda premium

Thank you mrvirginia. I just did this and it worked just fine.
Wicked ROM v1

Pinan said:
Thank you mrvirginia. I just did this and it worked just fine.
Wicked ROM v1
Click to expand...
Click to collapse
np :silly:

It'll be awesome if it can be flashed through TWRP or CWM.

With this (and possibly a kernel flash), we can now run any on the international i9505 ROMs, right?

Seems like i9505 have the solution to flash through recovery.
http://forum.xda-developers.com/showthread.php?t=2192025
Maybe we would get it soon? ;p

I've tried to Odin mdl but it stays at mdb
Sent from my SGH-M919 using xda app-developers app

mrvirginia said:
np
Click to expand...
Click to collapse
Can we get the MDB radio as well? Would be good to have to experiment with. I found some dead areas, that I did not notice were dead before I changed to MDL.

xXchrizhurtyXx said:
I've tried to Odin mdl but it stays at mdb
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Same

xXchrizhurtyXx said:
I've tried to Odin mdl but it stays at mdb
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
BDHela said:
Same
Click to expand...
Click to collapse
make sure you are selecting Phone and not PDA. confirmed working by numerous people.
Pinan said:
Can we get the MDB radio as well? Would be good to have to experiment with. I found some dead areas, that I did not notice were dead before I changed to MDL.
Click to expand...
Click to collapse
if you can pull it. i don't have those files on hand. i may get them tmw.

mrvirginia said:
make sure you are selecting Phone and not PDA. confirmed working by numerous people.
if you can pull it. i don't have those files on hand. i may get them tmw.
Click to expand...
Click to collapse
I did that sir. Still saying MDB in about. Sorry
Running Wicked 2

nitrogen618 said:
Seems like i9505 have the solution to flash through recovery.
http://forum.xda-developers.com/showthread.php?t=2192025
Maybe we would get it soon? ;p
Click to expand...
Click to collapse
this is a one part modem.bin. the Odin file in OP is a two-part modem, modem.bin and NON-HLOS.bin. i'm fairly certain we need both parts and am not sure how that works via CWM. i can make one with both parts flashed to the modem location, but can't guarantee what that would do if anything...

BDHela said:
I did that sir. Still saying MDB in about. Sorry
Running Wicked 2
Click to expand...
Click to collapse
not sure what to tell you, mate.

BDHela said:
I did that sir. Still saying MDB in about. Sorry
Running Wicked 2
Click to expand...
Click to collapse
I did the same, Odin to phone and it says MDB but Odin reported 1 successful and 0 failed. Isn't there two files though?
MD5 checked out so I know all of that is solid it wasn't a bad download, maybe it's a glitch or something.

Orical said:
I did the same, Odin to phone and it says MDB but Odin reported 1 successful and 0 failed. Isn't there two files though?
MD5 checked out so I know all of that is solid it wasn't a bad download, maybe it's a glitch or something.
Click to expand...
Click to collapse
yes, two files but it will always say 1 successful. says same when you flash an entire stock image which includes quite a few files (imgs).

mrvirginia said:
yes, two files but it will stay say 1 successful. says same when you flash an entire stock image which includes quite a few files (imgs).
Click to expand...
Click to collapse
I saw the other file you listed in the scroll report while flashing but it never said it errored at all just listed then completed the reboot, meh maybe it's just one of those things it's hit or miss depending on the device.

S4 seems to be getting stuick on bootup of ROM & other issues

Hello and thanks to all those before me who give great advice on troubleshooting....
Here's my situation:
Phone is Rooted.
I downloaded an app a few days ago from the Play Store, so I could move my app installs to the sdcard. When i installed the app it said that there was something wrong " can't remember the exact message " and it needed to fix it. My dumbass allowed it to fix it and here is where my problems began.
Right after that I began receiving a message "Shell has been granted Super User", phone began to run sluggish and the Play Store App would always say it was crashing.
So I figured, screw it I would format and start w/a new ROM anyway.... I did not have any sort of backup (of course dumbass)
However I loaded up the latest version of Odin 3.09 and just incase I installed the root.zip again incase that was destroyed. Then I installed the latest version of OUDHS CWM-Based Recovery 1.0.3.3 ( Previously I had TWRP )
I downloaded a few different roms so I could see what I wanted...However...here's where things get interesting, and I did do some research on it but couldn't find a way to resolve the 1st problem.
When I first started to install a ROM, don't remember which one I was getting a signature verification failed....I had read that it could be 2 things, one the MD5 was bad, I verified that, so that wasn't the issue. Then I came across that it may have been a ROM that my device(Samsung) somehow knew wasn't approved, therefore prevented it from being installed....OK fine...
Next I found a ROM that was going to work via installing...So i picked the CM10.2 and wiped/format/davik/cache...etc... Installation took a few mins...Then when I rebooted, it's been on the Cyangenmod screen for 45 mins +....
Is there anyway I can do some verification that something further isn't interfering w/my installs?
Thanks in advance and any guidance is GREATLY appreciated...
Regards
Erik

Odin to stock and try that, always the best choice
Sent from my SGH-M919 using xda app-developers app

aamir123 said:
Odin to stock and try that, always the best choice
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Actually I tried that and I used this one from stockroms.net TMB-M919UVUAMDL-1366964131.zip
the verification failed immediately, however, when I checked it w/the MD5 hash on my computer it checks out...That's where I'm wondering if there is something else going on...
Or are you talking about something else regarding stock? If so could you clarify...Thanks

Use sam mobile.com
And flash the mdl fw from there. Also you may have to unzip the original file to get a tar file
Sent from my SGH-M919 using xda app-developers app

aamir123 said:
Use sam mobile.com
And flash the mdl fw from there. Also you may have to unzip the original file to get a tar file
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Just wanted to say thank you for your help. Both the flashing the recovery back to default and the default ROM worked. Now in the future no more clicking yes when I don't have a backup
Have a great weekend!!

oregongreen said:
Just wanted to say thank you for your help. Both the flashing the recovery back to default and the default ROM worked. Now in the future no more clicking yes when I don't have a backup
Have a great weekend!!
Click to expand...
Click to collapse
glad it worked out for you, I know it can be scary to think you screwed up your phone.

Glad you solved it, ALWAYS MAKE A BACKUP
Sent from my customizable brickable device

mrhughy said:
Glad you solved it, ALWAYS MAKE A BACKUP
Sent from my customizable brickable device
Click to expand...
Click to collapse
This can nvr be said enough.

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

[Q] Odin a stock firmware

If i use odin to flash a stock firmware will it delete all of the pictures inside the phone?

No. I have pictures and music and all SD card contents dating back to the time I bought the phone and I used Odin last week to return to stock.
Sent from my SGH-T999 using Tapatalk

No, but you may need to factory reset, which would delete all the files in your device..
There are possible ways trying to get around this, but its safer to just back up your important files in case something unexpected happens
Sent from my SGH-M919 using Tapatalk

serio22 said:
No, but you may need to factory reset, which would delete all the files in your device..
There are possible ways trying to get around this, but its safer to just back up your important files in case something unexpected happens
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
well the phone im doing it on doesnt start and just stays stuck on the samsung logo so do you think itll still work.

lmendoza23 said:
well the phone im doing it on doesnt start and just stays stuck on the samsung logo so do you think itll still work.
Click to expand...
Click to collapse
Don't know, often times that means a factory reset might be needed, but can you tell me what happened to it? There may be other ways to fix it
Sent from my SGH-M919 using Tapatalk

The phone belongs to a buddy of mine but he told me it just randomly happened.
btw nice e90

lmendoza23 said:
The phone belongs to a buddy of mine but he told me it just randomly happened.
btw nice e90
Click to expand...
Click to collapse
Hmm.. Ok try flashing firmware with Odin, if that doesn't fix it then flash twrp recovery and reboot to recovery, after that do a factory reset within twrp.. This will perform a factory reset without wiping user files.. Reboot and it should boot up
Edit: oh and yes I know, wish it was mine :/
Sent from my SGH-M919 using Tapatalk

serio22 said:
Hmm.. Ok try flashing firmware with Odin, if that doesn't fix it then flash twrp recovery and reboot to recovery, after that do a factory reset within twrp.. This will perform a factory reset without wiping user files.. Reboot and it should boot up
Edit: oh and yes I know, wish it was mine :/
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
so the first odin shouldnt delete anything from the gallery? no matter which rom i flash
ohhh, if it was an m3 id be wishing too

lmendoza23 said:
so the first odin shouldnt delete anything from the gallery? no matter which rom i flash
ohhh, if it was an m3 id be wishing too
Click to expand...
Click to collapse
Right, but you're not flashing a rom, you're flashing firmware.. You could also just flash a rom, but I don't know how your buddy wants his device
Bro I love m3's!! Been in love with them since day one.. I just have that display pic because it looks nice lol
Sent from my SGH-M919 using Tapatalk

serio22 said:
Right, but you're not flashing a rom, you're flashing firmware.. You could also just flash a rom, but I don't know how your buddy wants his device
Bro I love m3's!! Been in love with them since day one.. I just have that display pic because it looks nice lol
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Alright well here goes nothing!
Hopefully when im done with my e36 ill be chasing those e90s
EDIT: When i attempt to flash with odin it says <OSM> All threads completed. (succeed 0 / failed 1) and the phone says odin flash write faliure

What firmware version did you try to flash? If it was ever updated to 4.3 you can only ever flash the same or newer firmware again. So if it had been updated to NC2 before, you can only flash NC2 firmware. (Latest version). If this doesn't apply, you might want to try reinstalling drivers. Also, only use Odin v3.07 or 3.09.
You can try to odin flash twrp recovery though, then make a nandroid backup to be safe. It also has a built in file manager and you can use it to copy the picture folder from internal to external sd card.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
What firmware version did you try to flash? If it was ever updated to 4.3 you can only ever flash the same or newer firmware again. So if it had been updated to NC2 before, you can only flash NC2 firmware. (Latest version). If this doesn't apply, you might want to try reinstalling drivers. Also, only use Odin v3.07 or 3.09.
You can try to odin flash twrp recovery though, then make a nandroid backup to be safe. It also has a built in file manager and you can use it to copy the picture folder from internal to external sd card.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I downloaded the latest 4.3 and tried to flash that but didnt work im not sure what the phone had before and can i flash the twrp recovery if the phone wasnt rooted?

Yes, you can flash a custom recovery without root. Its actually the original root method if I'm not mistaken. (Flash recovery, then from that recovery flash the SuperSU update zip. )
Since youre using the latest firmware, we know that's not the cause at least.
Few other things that are known to cause Odin to fail...
Make sure you are using the correct firmware for the device. (Make sure if its a T999, T999L, T999N, T999V and use the corresponding firmware)
If kies is on your computer, uninstall it
Try different usb cables, yes they quite often do go bad.
Try every usb port on your computer. I've seen more than a few people find it only worked on one usb port! No idea why...
Try different driver versions. Make sure you uninstall through device manager. Drivers are in my sig.
If all else fails, try a different computer if possible.
If I think of anything else ill add it.
Sent from my SGH-T999 using Tapatalk

Yup, everything Doc said.. Double check firmware or Odin may be a little picky
Sent from my SGH-M919 using Tapatalk

I tried what you guys said and none of it worked and then i tried to install a recovery through odin and that worked. Through recovery I tried to install a zip firmware that i got from another firmware and now the phone does not start at all no boot screen no download mode no nothing. Is it fully gone now?

lmendoza23 said:
I tried what you guys said and none of it worked and then i tried to install a recovery through odin and that worked. Through recovery I tried to install a zip firmware that i got from another firmware and now the phone does not start at all no boot screen no download mode no nothing. Is it fully gone now?
Click to expand...
Click to collapse
Firmware or ROM? And what zip is this you're talking about? Can you get into recovery? If not then you might have bricked it
Sent from my SGH-M919 using Tapatalk

serio22 said:
Firmware or ROM? And what zip is this you're talking about? Can you get into recovery? If not then you might have bricked it
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I used this thread http://forum.xda-developers.com/showthread.php?t=2403060 at the bottom of the first post
and yeah no recovery
but when i plug it into my computer it beeps like if something just was plugged in

That thread is pretty old and I think that was for LJA, if the phone was updated to 4.3 and you tried that it makes sense that it would brick.. Does it give you message in the connected devices?
Sent from my SGH-M919 using Tapatalk

serio22 said:
That thread is pretty old and I think that was for LJA, if the phone was updated to 4.3 and you tried that it makes sense that it would brick.. Does it give you message in the connected devices?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Nope

lmendoza23 said:
Nope
Click to expand...
Click to collapse
Try the debrick thread
Sent from my SGH-M919 using Tapatalk

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