Develop Bugs

(STEP BY STEP GUIDE) How to get Jellybean on Galaxy S3 I747M (Bell/Rogers/Telus/ATT)

Ive decided to post a new thread as members wanted a Step by Step to get Jellybean's latest leak working on their 747M devices. So here goes.
This is meant to be flashed over a Samsung based rom (NOT AOSP or CM10). I can't confirm whether it will work on other rooms. Please revert to a touchwiz rom before you attempt this. Also, dont forget, this is a leaked rom, so there might be bugs. I will try to compile them at the beginning of this thread for all of us to see. I have now been using this ROM for 3 days without any MAJOR issues. Small bugs do exist here and there.
Step by Step Guide: This has been confirmed to be working for ATT variants as well, but the standard disclaimer applies and any flashing or mods done to your phone are your responsibility. This guide would not be possible without the repacked OTA package from Radeon_X. Thanks a lot to him for this.
1. Download the LALH1 firmware for Bell/telus
Telus
Bell
2. Download Odin 3.07 here: http://d-h.st/hSj. Kick your phone into download mode (turn off --> volume down, home and power). Connect to USB and then start ODIN.
3. Leave all the checks as is. Click on PDA, unzip the Firmware file you downloaded above and choose the md5 file.
4. Click Start and let the phone complete the process.
5. Once the phone reboots, put it in download mode once again, and flash Clockwork Mod Recovery found here: http://forum.xda-developers.com/attachment.php?attachmentid=1303041&d=1346812021
6. Boot up the phone once that is done, and transfer the OTA compiled by Radeon_X (which now also includes Root) to your phone, boot into recovery and install the ota and voila, you have Jellybean: https://hotfile.com/dl/170842913/3b61dbd/d2can_JB_OTA_keeproot.zip.html
7. ATT users can flash a native modem, however, some users have reported to use LH1 without problems. Look in this thread: http://forum.xda-developers.com/showthread.php?t=1831898
Noticeable Changes:
* yes, it is a little laggy, but the touchwiz launcher is SOOOO zippy. It Flies
* everything so far seems to be fine, no error messages
* lock screen allows 5 shortcuts
* wifi tether works
* root works using the package here: http://download.chainfire.eu/212/Sup...etrieve_file=1
* the lock screen has a grey hue to it, can someone else please confirm this for me?
* long pressing the power button brings up a new menu, see attached screenshots
* the status bar is not edge to edge, it is centered and the last few pixels on the left AND the right, and not used. --- not sure what this is
* dormant mode is relabelled to be "Blocking Mode"
* settings>wireless> has a better looking setup
* pressing and holding icons in touchwiz now gives the menu to delete/app info at the top instead of the bottom
* the notification bar has minute little detailed changes, ie. the clear button is smaller etc.
* a lot more widgets - sizes and new widgets both
* MOST IMPORTANT - YES GOOGLE NOW WORKS PERFECTLY SO FAR
* New multitasking menu
*BUGS*
*the screenshot "SHARE" button is initially blocked and you must scroll up with two fingers and expand it again to show it sometimes
*music player crashes when you hit the shuffle button at the top of the list
*playing audio through bluetooth seems to be wonky and doesnt work very frequently.
*grey status bar
*uncentered status bar icons
Thanks to:
Radeon_X for recompiling the OTA and providing root access as well.
jebise101 - for the Original Firmware Files

Also att users must flash a modem.
Sent from my SGH-I747M using xda premium

meleii said:
Also att users must flash a modem.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Thanks, can you please provide a link to the modem you used? I'll provide a link for it in the opening post.

Which modem you use depends on location. Here's a link to the modem sticky post.
http://forum.xda-developers.com/showthread.php?t=1831898

So just to clarify....even if i'm on AT&T as a carrier...this doesn't work with USA phones....right? SGH-I747

rpavich said:
So just to clarify....even if i'm on AT&T as a carrier...this doesn't work with USA phones....right? SGH-I747
Click to expand...
Click to collapse
im not sure what you are asking here....it does work on ATT carriers, just need to flash a new modem as stated in the opening post. Hope this helps

mixxy said:
im not sure what you are asking here....it does work on ATT carriers, just need to flash a new modem as stated in the opening post. Hope this helps
Click to expand...
Click to collapse
Ok...I'll try and re-clarify.
I have a US phone on ATT. This seems like it's just for Canada phone users so I'm wondering if this is now ok for US phones.
I'm running I747UCLEM

rpavich said:
Ok...I'll try and re-clarify.
I have a US phone on ATT. This seems like it's just for Canada phone users so I'm wondering if this is now ok for US phones.
I'm running I747UCLEM
Click to expand...
Click to collapse
Yes it will work. I have been running it on a us att i-747 since yesterday.
Sent from my SGH-I747M using xda premium

meleii said:
Yes it will work. I have been running it on a us att i-747 since yesterday.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Woo hoo!! thanks!
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Is there any particular one that US AT&T users should use? (Bell, Telus, or Rogers)?

rpavich said:
Woo hoo!! thanks!
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Is there any particular one that US AT&T users should use? (Bell, Telus, or Rogers)?
Click to expand...
Click to collapse
The telus one is the cleanest in my opinion. Has no bloat. Both Bell and Rogers have their branded apps. Id recommend the Telus one.

mixxy said:
The telus one is the cleanest in my opinion. Has no bloat. Both Bell and Rogers have their branded apps. Id recommend the Telus one.
Click to expand...
Click to collapse
Telus version on the AT&T S3?
Is this a 100% stock JellyBean Rom?
Any Bugs?

613BulletProof said:
Telus version on the AT&T S3?
Is this a 100% stock JellyBean Rom?
Any Bugs?
Click to expand...
Click to collapse
100% stock, no mods other than root. Bugs do exist since this is not the final release, but its stable and works great.

Will this work coming from an AOSP ROM or should we be going from stock to this?
TIA
sent from my iPhone killer using tapatalk 2

jethro650 said:
Will this work coming from an AOSP ROM or should we be going from stock to this?
TIA
sent from my iPhone killer using tapatalk 2
Click to expand...
Click to collapse
You must flash back to one of the stock roms in step one in the op.

Can we use the pro version of mobile Odin?
Sent from my SAMSUNG-SGH-I747 using xda premium

Ok....something's wrong.
I've tried to install the firmware to get this process started 3 times now and it fails immediately.
I'm on US AT&T...
Can someone suggest something to help?
this is the message:
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

rpavich said:
Ok....something's wrong.
I've tried to install the firmware to get this process started 3 times now and it fails immediately.
I'm on US AT&T...
Can someone suggest something to help?
this is the message:
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Ditto This. I'm on AT&T USA SIII and running CM10 with CWM. I've tried reflashing stock recovery, no go.

What step are you on that you got that info?
rpavich said:
Ok....something's wrong.
I've tried to install the firmware to get this process started 3 times now and it fails immediately.
I'm on US AT&T...
Can someone suggest something to help?
this is the message:
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
---------- Post added at 02:24 PM ---------- Previous post was at 02:21 PM ----------
If I can ever get the Telus firmware to download I will report back what my findings are.
Have to flash this in ODIN first and then move forward from there...
Joe1981AL said:
Ditto This. I'm on AT&T USA SIII and running CM10 with CWM. I've tried reflashing stock recovery, no go.
Click to expand...
Click to collapse

,
Im using the Telus S3, followed all instrutions, flashed the proper image, installed CWM, when I go into cwm to install the JB update. it gives me erorr "7"
any suggestions

Do you have root?
7ilmi said:
Im using the Telus S3, followed all instrutions, flashed the proper image, installed CWM, when I go into cwm to install the JB update. it gives me erorr "7"
any suggestions
Click to expand...
Click to collapse

[Q] Can't Flash Modem

So, I updated to 4.4 Kit Kat with this Play Edition ROM. But after the flash, now I'm not getting 3G. After I register on the T-Mobile network, it works until the phone goes to sleep. Everyone in the thread says to flash I9505XXUEMKE_Modem as a solution. But when I try, in Odin I get
<ID:0/007> NAND Write Start!!
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it'self, it also says "SECURE CHECK FAIL: mdm"
Am I using the wrong modem or what? Is there some trick I'm missing?

This in the modem I flashed. Worked great. http://forum.xda-developers.com/showthread.php?t=2544612
Sent from my SGH-M919 using XDA Premium 4 mobile app

Pharylon said:
So, I updated to 4.4 Kit Kat with this Play Edition ROM. But after the flash, now I'm not getting 3G. After I register on the T-Mobile network, it works until the phone goes to sleep. Everyone in the thread says to flash I9505XXUEMKE_Modem as a solution. But when I try, in Odin I get
<ID:0/007> NAND Write Start!!
<ID:0/007> Transmission Complete..
<ID:0/007> Now Writing.. Please wait about 2 minutes
<ID:0/007> Receive Response from boot-loader
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it'self, it also says "SECURE CHECK FAIL: mdm"
Am I using the wrong modem or what? Is there some trick I'm missing?
Click to expand...
Click to collapse
You are lucky that failed. If's the wrong modem for your phone. Flashing that could have killed the device. At best it would have soft bricked it and you would have had do an Odin flash back to stock.
Be very careful what you try to flash. The i9505 is very similar to the T Mobile model but it's not the same. The ROM's are mostly interchangable but the modems and recoveries and kernels and stuff like that aren't. You absolutely need the T MObile specific versions of those kinds of things.
The thread Okcxb linked for you is your salvation. It shoudl work fine. But be careful in the future with what you flash.

okcxb said:
This in the modem I flashed. Worked great. http://forum.xda-developers.com/showthread.php?t=2544612
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You, sir, are a gentleman and a scholar.

Skipjacks said:
The thread Okcxb linked for you is your salvation. It shoudl work fine. But be careful in the future with what you flash.
Click to expand...
Click to collapse
Thanks for the kind words Skip
Sent from my SGH-M919 using XDA Premium 4 mobile app

[Q] Phone is dead

rooted my S3 (4.1) and installed clockwork mod.
created a backup of my S3 using clockwork.
installed Jellybomb ROM.
recovered S3 backup using clockwork.
infinite boot....
I can still get into download mode and clockwork recovery but I'm unable to restore my S3.
Odin ( versions 1.83 - 3.09) fails all attempts to install roms, and clockwork is no longer able to read my ext sd card.
Now I have no way of installing anything to the phone.
Any advice?

westnine9 said:
rooted my S3 (4.1) and installed clockwork mod.
created a backup of my S3 using clockwork.
installed Jellybomb ROM.
recovered S3 backup using clockwork.
infinite boot....
I can still get into download mode and clockwork recovery but I'm unable to restore my S3.
Odin ( versions 1.83 - 3.09) fails all attempts to install roms, and clockwork is no longer able to read my ext sd card.
Now I have no way of installing anything to the phone.
Any advice?
Click to expand...
Click to collapse
have you tried using adb push?
look at these steps http://android-revolution-hd.blogspot.com/2013/12/how-to-copy-rom-zip.html
skip 9,10,11,12 because you don't need to create any folders and you are using 4.1.2
I hope that helps

jdelano said:
have you tried using adb push?
look at these steps...
skip 9,10,11,12 because you don't need to create any folders and you are using 4.1.2
I hope that helps
Click to expand...
Click to collapse
Thank you.
At least now I can push roms to the device.
It seems that no matter what rom I attempt to install I get these lines in clockwork:
-- Installing: /sdcard/rom.zp
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried 2 custom roms and Samsungs 4.1 stock Jellybean rom.
Same lines every time.
Am I missing something?

Jessooca said:
Is Odin failing in the middle of flashing a tar file or what is going on exactly.
Did your phone ever reboot or get stuck at the Samsung logo prior to this semi bricked issue?
Any details you can provide will help us better to help you.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Odin begins to write and then fails a few seconds afterwards.
After a failed write of any rom I get the boot error screen with the yellow triangle on the device.
Yes, It did get stuck at the Samsung screen prior to my clockwork mod no longer reading my ext sd card.

Jessooca said:
Try a usb port in the back of your computer and a different cable. I got one from my dollar tree and it's great.
Are you sure you aren't trying to flash an older tar file? Once you update to the newest update you have to flash the newest SPRINT SPH-L710 stock tar, I'm sure you know this already. Perhaps you've inadvertently downloaded the wrong tar!?
I have checked marked everything including wiping the efs in Odin 1.87 and it fixed a data issue someone had
This has to be fixable with Odin. I'd flash flash and try flashing again until Odin finishes without an error.
** also since you're on 4.1 why not try the latest tar file, not md5 and Odin that then root with CF Auto Root?
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 04:15 PM ---------- Previous post was at 03:52 PM ----------
One other thing...
Don't use twrp or cwm, use Philz recovery. Twrp works but on some roms it's flaky
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the quick response.
I have tried different cables and usb ports (front and rear of PC case).
I'm also positive that I have the latest stock .tar from Samsung.
Also, I've tried checking "phone EFS clear" in Odin 1.87 as you've mentioned. (I've tried writing roms with all available versions of Odin as well. Versions 1.83 - 3.09 get me the same failed results)
lol, as far as flashing, flashing, and flashing until it works? I've tried. I've become quite desperate.
Here are the lines I get in Odin if it's of any help.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Jessooca said:
** also since you're on 4.1 why not try the latest tar file, not md5 and Odin that then root with CF Auto Root?
Click to expand...
Click to collapse
I'm not clear as to what you mean by this.
Would you please explain this to me?

westnine9 said:
Thank you.
At least now I can push roms to the device.
It seems that no matter what rom I attempt to install I get these lines in clockwork:
-- Installing: /sdcard/rom.zp
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I've tried 2 custom roms and Samsungs 4.1 stock Jellybean rom.
Same lines every time.
Am I missing something?
Click to expand...
Click to collapse
Is there a status # given when it fails?

jdelano said:
Is there a status # given when it fails?
Click to expand...
Click to collapse
No status codes were displayed
Jessooca said:
Download Odin 1.87
Use a download manager to download the latest stock 4.3 TAR file
Put your phone into download mode.
Don't check repartition in Odin and don't use a pit file. Just the tar file in the pda slot.
Let me know where things go wrong this time
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 05:14 PM ---------- Previous post was at 04:59 PM ----------
... here's a link to the tar file
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Aha!
That little package did the trick!
My S3 is now up and running 4.1
Hmm, I still can't put my finger on what was causing the write fails with the standalone Odin and 4.1 rom.
..Maybe I didn't have the latest Samsung rom like I thought?
In any case that's irrelevant now.
Thank you very much Jessooca. :laugh:

Problem in Root " FAp Lock On "

Hello
I Tried 2 Known Root method
Like
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/root-5-1-1-dummies-t3144105
But When i try Write with odin it Give me error " Custom binary Wrote failed " Fap lock = on "
here Odin logs
Code:
<ID:0/014> Added!!
<ID:0/014> Odin engine v(ID:3.1005)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> boot.img
<ID:0/014> NAND Write Start!!
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/014> Removed!!
can any one help in Fix , I update Phone With UVU2COF6

You need to enable OEM bootloader unlock in your developer options.
Sent from my SM-G925T using Tapatalk

Also, it's FRP, not FAP.
Factory Reset Protection.

It's telling you that you need to FAP before rooting ?
Sent from my SM-G925T using XDA Free mobile app

Suprised it took that many comments

What the FAP you talking about?
Pp.

PanchoPlanet said:
What the FAP you talking about?
Pp.
Click to expand...
Click to collapse
Now that's FAPing funny

Tiffany84 said:
Now that's FAPing funny
Click to expand...
Click to collapse
OK Tiffany84, just because you have more posts than me doesn't mean you can FAP me ! :what:
Pp.

How to reset FRP lock from ON to OFF without having ANY SYSTEM.
Can only turn on to DOWNLOD green scree which shows in upper right:
ODIN MODE
PRODUCT NAME: SM-G920T
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: B:3 K:2 S:2
I can get to RECOVERY Menu screen as well but niether wipe cach nor factory reset works.
The screen shows:
The Android stesem recovery <3e>
LMY47X.G920TUVU3DOI1
The SYSTEM was wiped accidently. How to get it back in. ODIN give FAIL.
Please help this mother FAPper.

FRP locks up the phone for good, keeping you out so you can't flash or get phone working again.
Try going to your carrier maybe they have something from Samsung to unlock it.
Just show proof of ownership. If not Samsung.
Pp.

I had this exact problem with my s6. I ended up odining almost every odin file indiviually (ie; modem. Then bootloader. Then etc...). Until finally it let me odin a stock system back on.

I was able to flash the factory rom in this thread with FRP On. Worth a shot
http://forum.xda-developers.com/showthread.php?t=3144105
Sent from my SM-G925T using Tapatalk

Malnilion said:
You need to enable OEM bootloader unlock in your developer options.
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
I do not see that option in developer options. I'm on 5.02. Is there a procedure to open that option?
Yes I said option allot
Sent from my SM-G925T using XDA Free mobile app

njdevils28 said:
I do not see that option in developer options. I'm on 5.02. Is there a procedure to open that option?
Yes I said option allot
Sent from my SM-G925T using XDA Free mobile app
Click to expand...
Click to collapse
That option wasn't available with 5.0.2. only 5.1.
Pp.

how to off FAP(GRAND PRIME SM-G531H)

raazandongol said:
how to off FAP(GRAND PRIME SM-G531H)
Click to expand...
Click to collapse
If your phone is still operating go to "About phone" tap on build many times and you will enable developer option, there you will see "OEM unlocking" tick it on.
If stuck on boot screen with FRP activated then start flashing stock firmware with odin many many times and if your lucky you may escape the FRP zone.
Pp.

Don't do this.
Pp.

Very easy to fix simply use Smart Switch Emergency Recovery. Get your Serial Number from the Download mode. Reboot phone and you can FAP all you want.

jmc302005 said:
Very easy to fix simply use Smart Switch Emergency Recovery. Get your Serial Number from the Download mode. Reboot phone and you can FAP all you want.
Click to expand...
Click to collapse
That's fapulous and if you can't access d/l mode get serial # from the box your phone came in.
Pp.

I can remove FRP Lock on almost all samsung devices.
raazandongol said:
how to off FAP(GRAND PRIME SM-G531H)
Click to expand...
Click to collapse
See Jcunlocks.com i can remove almost all devices frp lock

Bricked my phone...

I accidently wiped /system
1.I've tried Odin, couldn't get it flash AT ALL. I don't know if its the zip or what. But i cant for the life of me get it to work.
2.I've tried sideloading, I'm not sure if that worked or not, after i did that, it wont go past the Samsung Galaxy note 4 screen, just keeps booting then stops and goes the battery charging screen(I'm assuming my OS is back on the phone? i also don't get the NO OS installed! error when booting up)
I'm completely out of ideas on what to do here.

yo try to get the zip from samsung or from a trusted source,that happend to me before (note 5)
Sent from my SM-N920T using Tapatalk

6eral said:
yo try to get the zip from samsung or from a trusted source,that happend to me before (note 5)
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Ive looked EVERYWHERE for a zip. I just took one off here.
Could you by chance link me to the correct zip?

what kind of phone and carrier?
Sent from my SM-N920T using Tapatalk

I thought i would also post the Odin logs
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU1BOB7_N910PSPT1BOB7_N910PVPU1BOB7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
6eral said:
what kind of phone and carrier?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Note 4 sprint

let me see what i can find
Sent from my SM-N920T using Tapatalk

6eral said:
let me see what i can find
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Cool thanks

try this and let me know,it's supposed to work on most Samsung devices
Sent from my SM-N920T using Tapatalk

6eral said:
try this and let me know,it's supposed to work on most Samsung devices
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I don't think you linked me to it..

yo cant send you the link because I'm a new user,well the thing is you have to do it via Kies 3 check on youtube how to unbrick note 4 via kies 3
Sent from my SM-N920T using Tapatalk

6eral said:
yo cant send you the link because I'm a new user,well the thing is you have to do it via Kies 3 check on youtube how to unbrick note 4 via kies 3
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I tried this but I cant get my S / N.

damn,let me see if i can find anything else
Sent from my SM-N920T using Tapatalk

I believe the Odin stock tar you're looking for is OK1 from this link:
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
Most likely, the case is, you can't go from reactivation locked bootloader to reactivation unlocked bootloader. It's in the upgrade notes. Also check your phone display in download mode. If you were on one of those updates, your phone should say reactivation lock is disabled or something like that. It means the bootloader will allow a compatible flash. Enabled reactivation status would block even a compatible flash to protect original user from theft if he knowingly or unwittingly chose to enable it. You have to be careful because that's been described as an efuse. It could cripple your main board if flashing with it enabled. Maybe it takes multiple attempts to blow it, IDK but respect it... Try to get in the habit of checking phone display before Odin flashing.
Hopefully, it is not booting simply because there's still no OS. You wiped it and failed to flash because wrong tar was selected. I can say that the OB7 tar you flashed has a non-reactivation locked bootloader. So you cannot go backwards in Odin to it, if that's the case.
If your looking to flash an older ROM in recovery from the reactivation bootloader, it's been reported to be possible if you flash a 5.1.1 kernel after the old ROM flash in recovery. Stability and compatibility may vary by user and ROM. The question was even asked in this forum-KitKat Bobcat ROM IIRC- if possible to flash KitKat ROM and then Lollipop Android Touchwiz kernel and confirmed by at least one user. Nonetheless, no reason to doubt that but I recommend latest custom ROMs for compatibility.
Sent from my SM-N910P using Tapatalk

Bump
Still looking for help.
Tried 0din, and the same error comes up as the post before.
Tried Kies but I need s/n and I don't have my box and no s/n on the back behind my battery.
currently downloading sammoblie rom. Hopefully this works.
the only other thing I can think of is putting a rom on my SD card and installing from TWRP

AnonDreams said:
Bump
Still looking for help.
Tried 0din, and the same error comes up as the post before.
Tried Kies but I need s/n and I don't have my box and no s/n on the back behind my battery.
currently downloading sammoblie rom. Hopefully this works.
the only other thing I can think of is putting a rom on my SD card and installing from TWRP
Click to expand...
Click to collapse
That may work too if you flash the right kernel with it. Well, that applies only if using an older ROM as I mentioned in my first reply... Did you read it yet?
BTW, KIES usually does that for rooted phones. It may only work if you set it up with same phone before root but unsure.
Sent from my SM-N910P using Tapatalk

samep said:
I believe the Odin stock tar you're looking for is OK1 from this link:
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
Most likely, the case is, you can't go from reactivation locked bootloader to reactivation unlocked bootloader. It's in the upgrade notes. Also check your phone display in download mode. If you were on one of those updates, your phone should say reactivation lock is disabled or something like that. It means the bootloader will allow a compatible flash. Enabled reactivation status would block even a compatible flash to protect original user from theft if he knowingly or unwittingly chose to enable it. You have to be careful because that's been described as an efuse. It could cripple your main board if flashing with it enabled. Maybe it takes multiple attempts to blow it, IDK but respect it... Try to get in the habit of checking phone display before Odin flashing.
Hopefully, it is not booting simply because there's still no OS. You wiped it and failed to flash because wrong tar was selected. I can say that the OB7 tar you flashed has a non-reactivation locked bootloader. So you cannot go backwards in Odin to it, if that's the case.
If your looking to flash an older ROM in recovery from the reactivation bootloader, it's been reported to be possible if you flash a 5.1.1 kernel after the old ROM flash in recovery. Stability and compatibility may vary by user and ROM. The question was even asked in this forum-KitKat Bobcat ROM IIRC- if possible to flash KitKat ROM and then Lollipop Android Touchwiz kernel and confirmed by at least one user. Nonetheless, no reason to doubt that but I recommend latest custom ROMs for compatibility.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I can type out all the "download" screen info if needed.
But RA lock is off.

AnonDreams said:
I can type out all the "download" screen info if needed.
But RA lock is off.
Click to expand...
Click to collapse
That's OK, don't need it. That confirms you have you a newer bootloader. That tar is blocked in Odin, for you. Best to move forward with Odin rather than backward.
Some stock tars later than OB7 have even been reported to be blocked but being on OK1, I only know I can go back OJ6 in Odin. Didn't try another because of that fact and OJ6 and OK1 are the best lollipop updates, IMO.
Sent from my SM-N910P using Tapatalk

samep said:
That's OK, don't need it. That confirms you have you a newer bootloader. That tar is blocked in Odin, for you. Best to move forward with Odin rather than backward.
Some stock tars later than OB7 have even been reported to be blocked but being on OK1, I only know I can go back OJ6 in Odin. Didn't try another because of that fact and OJ6 and OK1 are the best lollipop updates, IMO.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Dude.. it worked. SO MUCH THANKS.