Develop Bugs

[Q] Wrong Root Method Brought on LoS -- Now what?

While I was aware that this phone was available for different carriers, I didn't realize there were multiple versions of the phone itself. So when it came out for Sprint (my carrier), I picked one up and left it stock for a few weeks. Eventually I wanted to root my phone so I began searching for simple root how-to's.
I went into this with only minor caution considering I've read so much about these simple rooting methods that "anyone can use".
These are the websites I ended up following for rooting my phone:
(I apologize that I'm a new user and can't officially make hyperlinks)
rumah-android[dot]com/root-samsung-galaxy-s2.html
android-advice[dot]com/2011/how-to-root-samsung-galaxy-s2/
Obviously it says "Samsung Galaxy S2" - but in reality it wasn't referring to our Sprint version of the phone.
So I followed the instructions to the letter, and everything ran with success. There were no errors or anything like that. So I rebooted the phone only to find that my first two buttons at the bottom of the phone were no longer working and I lost all service.
Now this is where I make mistake #2 -- I thought it was a good idea to "factory restore", thinking that I would have to just restart the whole process again - completely forgetting that once you overwrite the kernel you're only restoring what you overwrote.
Thankfully, I can still get into download mode, but where should I go from here?
Let me know if there's any information you guys need.

I'm not sure exactly what you did, but here is how to get it back to stock:
http://forum.xda-developers.com/showthread.php?t=1281287
After that if you still have no service you may have borked your modem/radio. I guess I'm tired because I can't find the thread to restore the stock radio, but its here somewhere. I'll look tomorrow and post it her if someone else hasn't already.

Hmm... You've seem to have done what I had done. You flashed a GSM version when your phone is a CDMA version. So the ROM is looking for a SIM card when the Epic 4G Touch doesn't have, or better yet, doesn't use one.
Here's a link to how-to root for the Epic 4G Touch
http://forum.xda-developers.com/showthread.php?t=1265429
^^ IDK if I can post hyperlinks yet, so yea...
My main reason for the link was so that you can get a ROM on your phone. As a just in case. The ROMs he links you to flash with Odin. I suggest clicking the link in his page instead of searching StarBurst and MidNight since there are the same ROMs on different devices.
If you have your phone working now, then oh. Never mind.
P.S. Just search for Epic 4G Touch and make sure it says that. This'll help prevent that. Also make sure it says "Epic 4G Touch" and NOT "Epic 4G". I almost made that mistake.

eagercrow said:
I'm not sure exactly what you did, but here is how to get it back to stock:
http://forum.xda-developers.com/showthread.php?t=1281287
After that if you still have no service you may have borked your modem/radio. I guess I'm tired because I can't find the thread to restore the stock radio, but its here somewhere. I'll look tomorrow and post it her if someone else hasn't already.
Click to expand...
Click to collapse
In case someone else stumbles upon this thread, I'm just letting you guys know that this did work for getting my device back to normal.

How does the GS3 compare to the Vibrant in terms of brickability?

Alright folks, this is directed more at the those that have spent a lot of time modding and flashing their GS3's. I recently got myself a GS3, and I gotta be honest, I haven't gotten the itch to customize it more than root yet because it is just that good already.
I modded the hell out of my Vibrant, constantly flashing Roms, modems, kernels, etc. Ran into a few "bumps" along the road where I thought the phone was done for, but I was always able to bring it back. For instance, a few months before I got the GS3 I was flashing a ROM and although I can't remember the details, something screwed up and I was getting the dreaded Phone to PC symbol. I have had this in the past and had a JIG that would always get me into download mode. This time however, it wouldn't work. I couldn't get ADB to send it into download, nor through the hardware keys, nor with the JIG. I thought for sure I was done for.
I decided to plug it into my computer anyway with ODIN up, and even though it wasn't in download mode, ODIN showed a "yellow COM". I said what is there to lose and so I loaded stock and hit start, lo and behold a few minutes later the ol' Vibrant was booting back up to the familiar sound of the T-Mobile jingle. I thoroughly believe that phone is unbrickable.
Now I know I'm going to get the itch sooner or later, especially as more and more ROM development ensues, but how brickable is the GS3? Anyone know if it's as "tough" as the Vibrant was in that respect, or is it quite a bit easier to brick? What is your experience with it so far?

If you flash am i9300 ROM, you will brick. That's about it.
Sent from my SGH-T999

If you know how to read warnings and have a fully functional brain you won't brick.
Posted from what apple calls "basically an iPhone" SGS3

GS3 should be less likely to brick

I flashed an HTC Rom with the vibrant and was still able to get it back to functionality.. not completely for sure about the GS3. I know of someone that hardbricked their GS3, and they are actually getting close to fixing it, but not fully yet.. just read and flash what ur suppose to.
Sent from my SGH-T999 using xda app-developers app

I use to have a vibrant too. Then I switch to this. I am a flashaholic so far everything good . Havent have anu problem that odin cant fix.
Sent from my SGH-T999 using xda app-developers app

If you do eventually decide to fiddle around with your phone, here's some advice:
1. BACKUP YOUR IMEI. No one's 100% sure what causes it (though there are several theories regarding recoveries and wipe scripts). You can inject your IMEI if you don't have a backup but the process takes maybe 10 minutes and I feel like it would save alot of headaches. There are currently two methods. I recommend you do both and keep a copy of the backup files somewhere safe:
Method 1: http://forum.xda-developers.com/showthread.php?t=1808408
Method 2: http://forum.xda-developers.com/showthread.php?t=1804123 (includes instructions on injecting an IMEI.
2. Try to stick to the thread for your particular GS3. I've heard that ATT Roms and kernels are compatible with the TMO version and vice versa. I take a little more comfort knowing a particular ROM or kernel was developed for my specific GS3 variant. Feel free to experiment with ROMS and kernels from other variants but be sure you know what they contain (be especially attentive to different modems/radios, see #3).
3. IMO the biggest source for bricking involves modems/radios. I haven't flashed any because I'm on wind and most of the new modems released have been for TMO. Flashing the wrong radio can brick your phone. Most ROMS don't flash a modem but it never hurts to ask. Be especially attentive to files that require ODIN as I believe some of these files may include modems and recoveries.
4. Since your posting on TMO forum, I'm going to assume yo have a TMO/Wind/Mobilicity variant of the phone. If your looking to root, I recommend using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1771687. Simply download the image for your cell phone company and follow the instructions in OP. It's basically just flash with ODIN. Then install a recovery. You can install CWM using the method in the post. Or you can install TWRP by downloading the goo.im app and installing it with that application..
5. HAVE FUN

I used to have a vibrant as well and had a few close calls. I was always able to finally get it back. The S3 appears to be just as hearty (as long as you don't flash a i9300 rom).
Flash away.

nicky9door said:
If you do eventually decide to fiddle around with your phone, here's some advice:
1. BACKUP YOUR IMEI. No one's 100% sure what causes it (though there are several theories regarding recoveries and wipe scripts). You can inject your IMEI if you don't have a backup but the process takes maybe 10 minutes and I feel like it would save alot of headaches. There are currently two methods. I recommend you do both and keep a copy of the backup files somewhere safe:
Method 1: http://forum.xda-developers.com/showthread.php?t=1808408
Method 2: http://forum.xda-developers.com/showthread.php?t=1804123 (includes instructions on injecting an IMEI.
2. Try to stick to the thread for your particular GS3. I've heard that ATT Roms and kernels are compatible with the TMO version and vice versa. I take a little more comfort knowing a particular ROM or kernel was developed for my specific GS3 variant. Feel free to experiment with ROMS and kernels from other variants but be sure you know what they contain (be especially attentive to different modems/radios, see #3).
3. IMO the biggest source for bricking involves modems/radios. I haven't flashed any because I'm on wind and most of the new modems released have been for TMO. Flashing the wrong radio can brick your phone. Most ROMS don't flash a modem but it never hurts to ask. Be especially attentive to files that require ODIN as I believe some of these files may include modems and recoveries.
4. Since your posting on TMO forum, I'm going to assume yo have a TMO/Wind/Mobilicity variant of the phone. If your looking to root, I recommend using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1771687. Simply download the image for your cell phone company and follow the instructions in OP. It's basically just flash with ODIN. Then install a recovery. You can install CWM using the method in the post. Or you can install TWRP by downloading the goo.im app and installing it with that application..
5. HAVE FUN
Click to expand...
Click to collapse
I did use that method for rooting already, but I didn't realize the issue with the IMEI so that's good to know for when I get the urge to start flashing again. :laugh:

[Q] SGH-T889v windmobile canada. PLEASE get in here.

Hey guys, sorry for posting this, but im desperate and have read until my eyes are falling out of my skull. I am willing to work with any dev if they need specific work/software ran/info to make this happen. Is there, or is there not clear concise directions on rooting SGH-T889v (wind mobile variant of note 2)?
remember we use AWS for our signal, the modem stuff is all different. this is were my expertise kinda falls short. BUT I AM WILLING TO HELP TO MAKE THIS HAPPEN. As far as iv'e seen there are no current methods of rooting this phone which is a damn shame considering its horsepower. i saw the all in one toolkit for note 2's, and i simply cannot afford to donate to unlock the functionality of the update that supports wind. So only ONE guy knows how? I believe dev's should get paid and should accept donations, they are the real workers and smart guys. I don't work for free either, However this kinda defeats the purpose of the ecosystem we fought so hard to have.... open and accessible platforms were we the users are in control. By with holding the method, its no longer donating, it's close sourcing ala apple,microsoft, etc. Zero offence to that guy, id just really love to "own" MY phone. Can someone PLEASE help? pass the word? anything? a peep?

gh0stpirate said:
Hey guys, sorry for posting this, but im desperate and have read until my eyes are falling out of my skull. I am willing to work with any dev if they need specific work/software ran/info to make this happen. Is there, or is there not clear concise directions on rooting SGH-T889v (wind mobile variant of note 2)?
remember we use AWS for our signal, the modem stuff is all different. this is were my expertise kinda falls short. BUT I AM WILLING TO HELP TO MAKE THIS HAPPEN. As far as iv'e seen there are no current methods of rooting this phone which is a damn shame considering its horsepower. i saw the all in one toolkit for note 2's, and i simply cannot afford to donate to unlock the functionality of the update that supports wind. So only ONE guy knows how? I believe dev's should get paid and should accept donations, they are the real workers and smart guys. I don't work for free either, However this kinda defeats the purpose of the ecosystem we fought so hard to have.... open and accessible platforms were we the users are in control. By with holding the method, its no longer donating, it's close sourcing ala apple,microsoft, etc. Zero offence to that guy, id just really love to "own" MY phone. Can someone PLEASE help? pass the word? anything? a peep?
Click to expand...
Click to collapse
Who says there is no way....use donated version of toolkit ...its in there
Sent from my SGH-T889 using Tapatalk 2

If you don't mind the flash counter, you could simply use an Odin flashable (N7100) CWM tar, push the superuser zip of your choosing to /data/media/ (linked to /sdcard/) and install that from CWM.

What I know is that the rooting part is all fine and dandy, sure its a little harder than the rest, but its okay, it not too hard. The problem I keep reading is that the ROMS aren't truly compatible with the device, as data become atrociously slow. A method one, respected fellow, recommended we take was to flash a modem that is "for" our device variant. I say that because people reported bootloops due to it. Also there's a greater chance for our device to lose its IMEI number...not sure if these problems have been resolved. But yeah your problem really isn't rooting its the whole deal afterwards, again I am going by what I've read, I myself do not wish to take the chance of it becoming unusable, so i stay far until I got time to research more and some brilliant helpful mind comes along and solves all problems.

true
MCRHAZ said:
What I know is that the rooting part is all fine and dandy, sure its a little harder than the rest, but its okay, it not too hard. The problem I keep reading is that the ROMS aren't truly compatible with the device, as data become atrociously slow. A method one, respected fellow, recommended we take was to flash a modem that is "for" our device variant. I say that because people reported bootloops due to it. Also there's a greater chance for our device to lose its IMEI number...not sure if these problems have been resolved. But yeah your problem really isn't rooting its the whole deal afterwards, again I am going by what I've read, I myself do not wish to take the chance of it becoming unusable, so i stay far until I got time to research more and some brilliant helpful mind comes along and solves all problems.
Click to expand...
Click to collapse
i think thats the issue, we just generally need someone more brilliant xD as per the "gentleman" that again, suggested using the donating kit, please re-read my post. whats this business about a flash counter????

darn shame still nothing regretting purchasing this phone completely due to this :/

I used the toolkit to root my N2 (Videotron T889v) without any problems. Just used the T-Mobile option since they are the same phone, just different software. The only difference is the modem from what I've read. Rooting does not change the modem that you currently have right now. If you decide you want to install a custom rom, then you may have to flash your modem back. I am currently using Jedi X rom without any problems and I can honestly say that it's faster than stock. He also provides a link with our modem so we can flash it after the install. All the T-Mobile software has been taken out, so you won't have to deal with any of it. Here are the links for the toolkit and rom.
Toolkit - http://forum.xda-developers.com/showthread.php?t=1957720
Jedi X rom - http://forum.xda-developers.com/showthread.php?t=1987634
There are 2 Jedi Roms available. Jedi X has the multi-window function working but no wifi calling. I believe the other is called Jedi Master and that one has wifi calling but no multi-window. I'm not sure if the wifi calling is a T-Mobile thing but I never installed that rom and can't really give much more info on it. In the end, you can always go back to stock if you're not satisfied. You can find a copy of your stock rom at sammobile. I would suggest making sure it's still available before doing anything.
As for the OP, this is my first time dealing with a flash counter although not my first time rooting. The flash counter is some type of software that Samsung puts in their phones to be able to tell if you have "tampered" with the phone's software. From what I've noticed, when you put your phone in the "download" state and install anything, that triggers the counter to rise. If you send your phone to Samsung for service and the counter is not 0, they will deny service since you would have broken your warranty. There is a program called Triangle Away that will return your counter back to 0, should you need to return the phone to Samsung. Although in my case it would only take it back down to 1 using their instructions. I finally got it back to 0 by adding an extra step. From what I've read, I think it depends on the kernel that you're using. Here is the link for the program.
Triangle Away - http://forum.xda-developers.com/showthread.php?t=1494114
I'm not an expert on any of this, just trying to help. I can say that I've rooted, unrooted and reset my flash counter back to 0 along with my stock Videotron rom.
Good luck

JDLS said:
I used the toolkit to root my N2 (Videotron T889v) without any problems. Just used the T-Mobile option since they are the same phone, just different software. The only difference is the modem from what I've read. Rooting does not change the modem that you currently have right now. If you decide you want to install a custom rom, then you may have to flash your modem back. I am currently using Jedi X rom without any problems and I can honestly say that it's faster than stock. He also provides a link with our modem so we can flash it after the install. All the T-Mobile software has been taken out, so you won't have to deal with any of it. Here are the links for the toolkit and rom.
Toolkit - http://forum.xda-developers.com/showthread.php?t=1957720
Jedi X rom - http://forum.xda-developers.com/showthread.php?t=1987634
There are 2 Jedi Roms available. Jedi X has the multi-window function working but no wifi calling. I believe the other is called Jedi Master and that one has wifi calling but no multi-window. I'm not sure if the wifi calling is a T-Mobile thing but I never installed that rom and can't really give much more info on it. In the end, you can always go back to stock if you're not satisfied. You can find a copy of your stock rom at sammobile. I would suggest making sure it's still available before doing anything.
As for the OP, this is my first time dealing with a flash counter although not my first time rooting. The flash counter is some type of software that Samsung puts in their phones to be able to tell if you have "tampered" with the phone's software. From what I've noticed, when you put your phone in the "download" state and install anything, that triggers the counter to rise. If you send your phone to Samsung for service and the counter is not 0, they will deny service since you would have broken your warranty. There is a program called Triangle Away that will return your counter back to 0, should you need to return the phone to Samsung. Although in my case it would only take it back down to 1 using their instructions. I finally got it back to 0 by adding an extra step. From what I've read, I think it depends on the kernel that you're using. Here is the link for the program.
Triangle Away - http://forum.xda-developers.com/showthread.php?t=1494114
I'm not an expert on any of this, just trying to help. I can say that I've rooted, unrooted and reset my flash counter back to 0 along with my stock Videotron rom.
Good luck
Click to expand...
Click to collapse
so you flashed the modem that ptmr3 provided for the t889v along with his jedi x rom and all good is good? no signal issues ? you get hspa+?

First Post:
I'm on Wind Mobile T889v Note 2. And I cant wait for this phone to get rooted so that I can run debian or whatever have you full blow linux desktop experience on my phone.
The current limited version of android on its own is too limiting for the processing beast that this phone is.

MCRHAZ said:
so you flashed the modem that ptmr3 provided for the t889v along with his jedi x rom and all good is good? no signal issues ? you get hspa+?
Click to expand...
Click to collapse
That is correct. Never had any issues whatsoever. Always get full signal strength, no disconnections and overall great service. As long as you flash after the rom, you will get your modem back. To be honest, the rom itself has never changed my modem, I always just flash it in case it's just reporting it as an error. In the directions it states that it will change it but I always check it and it has remained the same every time.

you mean by letting bootup and set up first then go back to twrp or cwm? and then flash the modem...my exams are done hoping to do it by tomorrow.

MCRHAZ said:
you mean by letting bootup and set up first then go back to twrp or cwm? and then flash the modem...my exams are done hoping to do it by tomorrow.
Click to expand...
Click to collapse
After you flash the rom (if you're flashing Jedi) you need to let it sit for 10 minutes on the first boot up (after the android logo, just use the reboot option after the 10 minutes). Once you've booted up and finished your setup, just go back into cwm or twrp and flash the modem.

how did you reset the flash counter with triangle away? it doesnt seem to work on my 889V
Sent from my GT-N7105 using xda app-developers app

[Q] [HELP] Soft Bricked i9505

I rooted my GS4 yesterday and had no issues at all until i tried to flash a MOD to obtain wireless hotspot, but what i didnt notice was the MOD was for a Sprint version GS4. I know know if thats exactly what made my phone brick but im pretty positive because it was during the reboot that the phone got stuck on the TMO screen and apparently remaining soft-bricked. I spent the rest of the night and all of today reading and researching how to fix it myself before coming here to ask for help, so please bare with me.
I have already attempted to flash the official stock firmware using Odin, but it displays an error everytime saying it failed and something about AUTH. Sorry if im sounding vague, i am on a back up phone to use the internet and forgot to right down the exact message.. Anywho, i tried wiping everything and redoing the process and i even tried to flash the appropiate PIT file that i found but it still displays an error and says failed because of some AUTH or SEC problem.
Ive been at this diligently for almost 12 hours. My brain is filled with all these suggestions and methods that i have tried to use to restore my phone back to factory, but none of them have worked. I can still get into recovery and all that, so im assuming that there is still good chance i could fix the problem?
Also i am starting to get myself more and more confused about whether the firmware i downloaded is the right one i need for my phone, it seemed so at first but now i see theres TONS of region codes that can determine the firmware version?
Sorry if im all over the place, but i just dont know which step to take next..
I appreciate any help that is given, and im even willing to pay (some) bucks or maybe even (btc) for someone to walk me through what i need to do or what im doing wrong.
Thanks in Advance

Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?

Toleraen said:
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Click to expand...
Click to collapse
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..

koolbreez12 said:
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
Click to expand...
Click to collapse
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.

Toleraen said:
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Click to expand...
Click to collapse
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.

error post

If you can get into download mode i would suggest flashing stock with that then rerooting that way the program downloads all of the nessacary stuff on its own.

koolbreez12 said:
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
Click to expand...
Click to collapse
Welcome!
Sent from my SGH-M919 using xda premium

Looking for PIT files for SM-N910P

I'm looking for the PIT files for Sprint's Note 4. Or does anyone know if the PIT for SM-N910F will work. Is the (F) version compatible in all of the Sprint versions. I.E. when looking for Sprint programs there is no SM-N910(P) but always a SM-N910(F). Is it safe to use the F version? Or is there a safe way to update/redo the bootloaders? I flashed some bad files with Odin right around the BOB7 udate and my device has been spinning in circles around that since. Even if I go full stock and Odin the latest firmware my device is set back to that period from a protected file that is in between bootloaders. I can't touch it. The closest I can get is with a terminal command from TWRP [/sbin/recovery] I can then chmod the files and erase or do whatever with them but they are restored in cold boot. Even after flashing the official firmware it reverts to the files from BOB7. What's really crazy is I'm running stock firmware so can not use xposed but if I mount data and system wipe and then run uberwipe my device will boot with xposed apps functional. It is as if I am running two ROMS one that can not be removed or changed. I can see it happening but not from where exactly. In cold boot it loads the RO biuld from /dev/block/platforms/msm_scc1.by_name/hidden. I can find everything but the hidden. In the stock recovery logs it says the command to fix it is wipe_data_crypto but I can't accomplish it. Any suggestions?

PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I appreciate the advice. I hope to avoid allot with the PIT. That's what flashfire back up says it needs. Shutting the phone of is a good idea. The recovery log was actually making fun of me for not. Along with the simple command I needed to open /sbin/recovery then wipe cane and data crypto. The /sbin/recovery was an eye opener (try it from the emulator in twrp to see if root has crippled you. The thing is most of us use a universal supersu update to reinstall and that is not good. That is written to take out the marines if that's what it takes to accomplish root. Remember the food old days when superuser binary was a line compatible with your cu?
Anyways another good command people don't know is if odin fails don't pull the battery. I put am s4 tip sleep forever that way. volumedwn home and power reatart the bootloader and wipe the cache for the software out is rejecting.
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man

TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk

samep said:
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
i dont know the problem seems to have been in a update.. playing with it for a while it started charging and turned on and finished a update....
i got a s6 active did the same thing to me just started working i run it for like 6 months no probs
of coarse its on sprints black list just found out due to non payment of ezpay. but ill deal with that on my own as such talks are downed and frowned upon.
man i got this thing for 20 bucks.... even if nothing else my buddy needs a screen for one in his shop. but most def thank you for responding..
too further your post i do all my own repairs ussually the cheapest route currently behind the wheel of a unrootable verizon note 5 and a lgg4 which is rooted but no twrp method available. each i have very little invested in.

I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.

TheMadScientist420 said:
i dont know the problem seems to have been in a update.. playing with it for a while it started charging and turned on and finished a update....
i got a s6 active did the same thing to me just started working i run it for like 6 months no probs
of coarse its on sprints black list just found out due to non payment of ezpay. but ill deal with that on my own as such talks are downed and frowned upon.
man i got this thing for 20 bucks.... even if nothing else my buddy needs a screen for one in his shop. but most def thank you for responding..
too further your post i do all my own repairs ussually the cheapest route currently behind the wheel of a unrootable verizon note 5 and a lgg4 which is rooted but no twrp method available. each i have very little invested in.
Click to expand...
Click to collapse
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
Sent from my SM-N910P using XDA-Developers mobile app

PIT_SM_N910P
https://mega.nz/#!cJREFYqS
Sent from my SM-N910P using XDA-Developers mobile app

planb234 said:
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.

TheMadScientist420 said:
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.
Click to expand...
Click to collapse
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.

planb234 said:
PIT_SM_N910P
https://mega.nz/#!cJREFYqS
My bad. I did not know that there has to be a key for mega. This one should do better.
Fwd: https://www.dropbox.com/sh/b0b3ywj5rbiec7h/AAAUM9TvOLUCDPJXXZTZBd_Ea?dl=0
Click to expand...
Click to collapse

planb234 said:
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.
Click to expand...
Click to collapse
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations

planb234 said:
I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.
Click to expand...
Click to collapse
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk

samep said:
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yeah it didn't work . It just shut down . I'll explain what has going on. Thank you for this post. It's good to know there's more options.
I actually did take a note 4 and s4 back. It dependes on how they upgraded. The bootloader doesn't change in an fota. I could do the s4 again now.
Thanks again for the awesome info.

TheMadScientist420 said:
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations
Click to expand...
Click to collapse
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.

samep said:
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I've been trying to reply to this for 2 days. You see it's not the way my phone runs that is the issue it is my network that is completely raped. I can't lose my parasite. I screwed up my bootloader petty bad when I was learning about Samsung. If you ask how to unlock a bootloader the most common answer you get is "you don't, you use auto root". Auto root is as amazing for sure but I can tell there is a lot of people who don't read anything and just do. The the disclaimer is "don't use this with a locked boot loader, you will likely brick your device." As i mentioned I'm a flash junky. I didn't know once you blew the hole in thy boot you only needed a custom recovery forever. I like changing roms so i rooted with it a couple more times. Things for real bad after I ran the kitkat auto root on lollipop. I could use one of my back ups and add plasma kernel for a few months until the next update. Worse than that i flashed a something from an unlock sight with a special version of Odin. I didn't even need to because i had all ready changed the csc to xas so my apns were open. The effects were scary but cool. I got locked out of my phone for awhile except for virtual access on my puter screen. My home network for straight raped after that. I had everything set to home and share because i didn't think there would be even more bored than me so as to waste there life watching my life. There is and they are smart as #. I go in intervals of being angry to amazed. I thought they were gone but no. I was not keen on interweb when i got on here. Now that i could protect myself I can't keep the evil at bay because it lurks in the dark spaces I can't reach. FlashFire says it can remove the seemles. It is incredible to but I don't think so. It definitely can't mine. What's crazy is I've had a couple new bootloaderers since then but it remains. I'm with out root at the moment and am able to look at some of the data and dev were files. I can see the usb files that block adb is in but still no. Even though auto root totally changes the way and where from the device boots, I'm needing to extract or other wise terminate what is probably one card a ftp or smb. I can see in my win logs that if uses a machine to confuse the system in a barrage of security log ins while opening a door for daddy. I had the xml explaing how it's done but then a brand new 125gb card magically went to sleep forever. Some script out there is beyond amazing to me. Virtual net adapters that aren't on top of actual hardware blow my mind. It would have never crossed my mind in a million years they there is going to be a need for antivirus software on hardware like a Bluetooth keyboard.

planb234 said:
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.
Click to expand...
Click to collapse
this device had a bad iemi person i got it from said they didnt pay for it on the sprint ezpay.
i checked and that was the truth. so i changed the iemi with another old sammy i had and put the sticker in for my records. so i know what the new iemi is without the device being turned on.
im trying to sim unlock it so i can use it on domestic gsm but no go sofar always invalid sim.
i guess i need to take this dissussion to another thread as so i dont get to far off the orig topic here

@planb234
I'm not following well what you've tried since getting a PIT file. Did you get the PIT file from Sammobile yet? Did you try the latest stock tar? If older ones, which ones fail?
If Odin fails, can you post the log and text on screen?
I believe what you're talking about is not needing to root if flashing a custom ROM. After a stock tar, you could Odin TWRP and flash a custom ROM. Custom ROMs include root and su. If using Chainfire Auto Root for Note 4, make sure to use the right one and latest for Lollipop and Marshmallow. KitKat had its own Auto Root. But the auto root uses a modified stock recovery which may make its use redundant if flashing a custom or even wanting just TWRP for backups if stock rooted.
Some fun facts for you:
The bootloader on Sprint Note 4 is unlocked. Flashing a stock tar will un-root it. Factory reset will cause you to lose systemless root. But flashing a full stock tar successfully will replace the bootloader. If you're trying to flash OB7 or older KitKat stock tar, your bootloader won't be replaced. As far as OTA, it patches existing baseband, bootloader and effected system files and partitions that need patched. Even if it's just a revision number in the update, it gets rolled up to match the update revision. While I feel stock tar updates are full and need no patching, the patching is sequential and should match the Odin'd bootloader and baseband once sequentially rolled up accordingly. So IMO, a patched bootloader is same as newly Odin'd bootloader. I could be wrong about the patching so not necessarily a fact.
I think your problem is unsuccessful flash of full stock tar. A blown eFuse may cause that but from what I've read in past posts of others that had issues back then is that flashing the correct stock tar after full wipe in stock recovery overcomes the flash. It leads me to believe it's only activating reset protection to try to roll the bootloader back to OB7 or KitKat. Maybe I'm wrong but if your phone isn't suffering a hardware issue, you should be able to recover it.
Other bootloaders between OB7 and OG5 like OE1 and OF5 were also exhibiting an inability to downgrade but bootloaders OG5 and up can so far can be downgraded to OG5. I haven't tried downgrading bootloader to OE1 or OF5 though.
I've seen phone info from posters claiming to roll their bootloader back to OB7 or older and they've actually reported a newer bootloader, post OB7.
As far as I know, the only true way to get KitKat ROM to flash and boot is to flash a newer kernel after ROM flash, but prior to initial boot attempt. Currently, I'm only aware of Android 5.1.1 kernel and post OB7 bootloader booting a KitKat ROM after bootloader is updated beyond OB7.
If you're capable of doing otherwise, I'd like to see legit screenshot of phone info or galaxy tools application.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SM-N910P using Tapatalk