Develop Bugs

[Q] Odin after ND8 upgrade

So this isn't really a problem for me yet, but yesterday I tried to flash MK3 with odin while on Stock ND8 because I was worried about having L710VPUDND8 which I got from here as a download, when the version Sprint is suppost to be rolling out is L710VPUCND8. Not sure why the OTA would differ from the one I got here, but anyways I tried flashing back to MK3 so I could just get the update when it was pushed to my cell and the flash failed after it got to the "aboot" part. Im wondering if this is because the version I have is higher then the version I want? And is there any way to circumvent this and go back to MK8. Also does anyone have any information about the difference between PUCND8 and PUDND8? Im worried because I want to make sure I get future updates such as 4.4.3 which Im sure they will come out with. So as you see its not really a problem right now, but could become one in the future possibly.

Ryan92394 said:
So this isn't really a problem for me yet, but yesterday I tried to flash MK3 with odin while on Stock ND8 because I was worried about having L710VPUDND8 which I got from here as a download, when the version Sprint is suppost to be rolling out is L710VPUCND8. Not sure why the OTA would differ from the one I got here, but anyways I tried flashing back to MK3 so I could just get the update when it was pushed to my cell and the flash failed after it got to the "aboot" part. Im wondering if this is because the version I have is higher then the version I want? And is there any way to circumvent this and go back to MK8. Also does anyone have any information about the difference between PUCND8 and PUDND8? Im worried because I want to make sure I get future updates such as 4.4.3 which Im sure they will come out with. So as you see its not really a problem right now, but could become one in the future possibly.
Click to expand...
Click to collapse
DO NOT ODIN MK3 IF YOU ARE ON ND8, flash a custom ROM if you wanna go to MK3, do not flash the firmware, and I doubt there will be anymore updates. This won't work because the Knox Bootloader won't let you downgrade your firmware and you can easily brick your device trying to do so.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
DO NOT ODIN MK3 IF YOU ARE ON ND8, flash a custom ROM if you wanna go to MK3, do not flash the firmware, and I doubt there will be anymore updates
Click to expand...
Click to collapse
Okay, so just install a custom recovery and use that to flash a zipped custom rom then use odin to flash MK3?

Ryan92394 said:
Okay, so just install a custom recovery and use that to flash a zipped custom rom then use odin to flash MK3?
Click to expand...
Click to collapse
No you can't downgrade to MK3 firmware you will brick. Knox won't allow it. Install a custom recovery, flash an MK3 ROM if that's what you want, but you can't go back to factory MK3.

bilgerryan said:
No you can't downgrade to MK3 firmware you will brick. Knox won't allow it. Install a custom recovery, flash an MK3 ROM if that's what you want, but you can't go back to factory MK3.
Click to expand...
Click to collapse
Okay, then the only thing left to ask is if you know of what the difference between PUCND8 and PUDND8 is? That is really my main concern. I just wanted to go back to mk3 to get the OTA update from sprint instead of from the zip file I downloaded from here. Could it be that Sprint made a mistake on their website showing L710PUCND8 when the version is actually PUDND8?

lol I just noticed your name is Ryan <3 awesome name =-D lol we even have the same join date oct 2011. Thatd be crazy if we had the same birthdate lmao im Sept '87 was I close? lmao

Ryan92394 said:
Okay, then the only thing left to ask is if you know of what the difference between PUCND8 and PUDND8 is? That is really my main concern. I just wanted to go back to mk3 to get the OTA update from sprint instead of from the zip file I downloaded from here. Could it be that Sprint made a mistake on their website showing L710PUCND8 when the version is actually PUDND8?
Click to expand...
Click to collapse
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.

bilgerryan said:
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.
Click to expand...
Click to collapse
from here: https://community.sprint.com/baw/message/782055#782055
and alternately here: http://support.sprint.com/support/a...ndUpdateTheSoftwareVersionOnYourSamsungGalaxy

bilgerryan said:
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.
Click to expand...
Click to collapse
Any ideas?

Ryan92394 said:
Any ideas?
Click to expand...
Click to collapse
The PUC is based on Sprint's official OTA source code. PUD is based on Samsung source code for all Sprint devices (Virgin Mobile, Boost, etc). That is the only difference from what I understand.

[Q] Moving beyond Cyanogenmod 10

I just rooted my wife's Sprint Galaxy S3 (d2spr) and managed to install Cyanogenmod 10. Back when we were on another carrier, I had installed later versions of the ROM, but only after a LOT of reading. Running the latest CWM, running the latest TWRP, doesn't matter. I cannot install later versions. The wiki says:
WARNING: Firmware update notice
CM10.1 and newer are not compatible with ICS bootloaders on this device. Update your device's firmware or you will get assert failures in recovery.
That is exactly my problem, but how do I perform this firmware update? I hope it's not an issue of reverting to stock, because Knox was enough trouble to overcome. I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
What am I missing? Where do I get this firmware? Once updated, will I then be able to avoid further Status 7 errors? (Editing the updater-script every time seems like a hoaky band-aid when one has downloaded the exact, correct, tailor-made ROM.) Thanks a lot to the community. I've learned everything I know from these forums, and I felt like I had hit enough of a dead end to ask for help.

I think you would have to odin a stock jb .tar, NOT KITKAT and then you reroot and flash whatever rom you want. Some of your concerns might be alleviated if you use tibu and back-up apps to an external sd, as well as nandroid to an external sd.
Edit: CNexus or Freeza might have their stock .tars for jb versions around here, they even come rooted too
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
I suggest waiting until someone else confirms though (but if I'm right you'll want the link that says "firmware/modem/baseband update", the 5th link)
Sent from my SPH-L710 using XDA Free mobile app

sevenpioverthree said:
I think you would have to odin a stock jb .tar, NOT KITKAT and then you reroot and flash whatever rom you want. Some of your concerns might be alleviated if you use tibu and back-up apps to an external sd, as well as nandroid to an external sd.
Edit: CNexus or Freeza might have their stock .tars for jb versions around here, they even come rooted too
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
I suggest waiting until someone else confirms though (but if I'm right you'll want the link that says "firmware/modem/baseband update", the 5th link)
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
why not the KK stock ND8 tar?

6th_Hokage said:
why not the KK stock ND8 tar?
Click to expand...
Click to collapse
Because i have read a bit about it and i believe that flashing the firmware might wipe internal data and it comes with knox as well. And from what you posted, all you need is a jb firmware. But that's also why I said to wait until someone more knowledgeable confirms what I'm saying
Sent from my SPH-L710 using XDA Free mobile app

sevenpioverthree said:
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
Click to expand...
Click to collapse
Just confirming, that's the correct one.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

You people are awesome!
Thank you. I will try it tomorrow, and check back. Samsung has done a lot to thwart rooting lately, and I didn't want to close any doors by installing something TouchWiz-based.

Argh!
Link #5 is broken. Crap. Back to reading...

badmojorayman said:
Link #5 is broken. Crap. Back to reading...
Click to expand...
Click to collapse
If you go to that same thread and find the spoiler under "old versions" (bottom of post #1) you can flash the "MB1 firmware/modem/baseband update" as well
Sent from my SPH-L710 using XDA Free mobile app

badmojorayman said:
I just rooted my wife's Sprint Galaxy S3 (d2spr) and managed to install Cyanogenmod 10. Back when we were on another carrier, I had installed later versions of the ROM, but only after a LOT of reading. Running the latest CWM, running the latest TWRP, doesn't matter. I cannot install later versions. The wiki says:
WARNING: Firmware update notice
CM10.1 and newer are not compatible with ICS bootloaders on this device. Update your device's firmware or you will get assert failures in recovery.
That is exactly my problem, but how do I perform this firmware update? I hope it's not an issue of reverting to stock, because Knox was enough trouble to overcome. I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
What am I missing? Where do I get this firmware? Once updated, will I then be able to avoid further Status 7 errors? (Editing the updater-script every time seems like a hoaky band-aid when one has downloaded the exact, correct, tailor-made ROM.) Thanks a lot to the community. I've learned everything I know from these forums, and I felt like I had hit enough of a dead end to ask for help.
Click to expand...
Click to collapse
Hold the phone! (Pun intended) There are two context clues in your op that lead me to believe that you should under no circumstances flash any firmware found in that firmware thread linked here.
1
badmojorayman said:
Knox was enough trouble to overcome.
Click to expand...
Click to collapse
If you have Knox your bootloader cannot be downgraded.
2
badmojorayman said:
I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
Click to expand...
Click to collapse
The only time I've personally witnessed this behavior is on the ND8 bootloader. If you don't know which bootloader you're on already you would be wise to find out before flashing any firmware file.

You've all given good advice, but the best advice came too late. The phone no longer powers on because of the baseband update I was attempting. I'm now waiting for a MicroSD card to show up so that I can attempt this:
http://forum.xda-developers.com/showthread.php?t=2345860&page=63

[Q] 4.4.4 NH7 No sound?

Hello everyone!
Recently I've decided to flash over to the new NH7 Update because I wanted to try out the 4.4.4 Modem. After flashing both the ROM and Modem, I no longer have any sound. I'm a "bit" new to some of this so I'm hoping I could get some help. I've flashed plenty of other ROMS and Modems before without an issue (At least issues I could fix) but I can't seem to find any information on how one would fix this problem. I'm assuming the problem is the 4.4.4 Modem?
I'm also having the lockscreen freeze up on me when I try to unlock the phone. If I let the phone set for a while it settles down but it's still really buggy. Seems to do this with any ROM I flash and random things FC on me.
Lastly, Not sure if this helps with the problem but every time I boot into recovery and go to start the phone, it tells me that I lost root and gives me the option to fix. If I choose not to fix, I still have root. No idea why it prompts me about this?
Anyway, here's some info on what I did.
Flashed this ROM and used the modem provided in the thread - http://forum.xda-developers.com/gal...-4-4-4-nh7-insane-kit-kat-v1-9-14-14-t2876946
1 Wiped Cache, Dalvik, Data, Factory reset with TWRP
2 Flashed ROM with TWRP
3 Put phone in download mode and flashed the NON-HLOS.bin
4 Restarted then booted download and flashed Modem.bin
5 Restarted normally and setup phone like normal.
6 No sound :/
Used the latest version of TWRP I could find. (2.8.1 I believe?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway, thanks for any help you guys can give!
Jeff

Try the double flash method (start from phone off, flash without auto reboot, pull battery, boot back to ODIN, flash again, pull battery, boot normally). Some bits may not have updated. This will fix it.
The thing about losing root is I believe a known TWRP bug in that version.
Marc

Hi Marc
I've tried the method you describe with no luck
Oh, I suppose it's worth mentioning that I'm using ODIN version 3.0.7
Thanks,
Jeff

For Sickness' 4.4.4 ROM you have to be on the NH7 bootloader for it to fully work with no issues
And also, try TWRP 2.7.0.0. I use TWRP 2.6.3.1 and never have had an issue

Kriptik210 said:
For Sickness' 4.4.4 ROM you have to be on the NH7 bootloader for it to fully work with no issues
And also, try TWRP 2.7.0.0. I use TWRP 2.6.3.1 and never have had an issue
Click to expand...
Click to collapse
Hey Kriptik210
For the bootloader I'm not exactly sure where to find it. (I have a link to what I think is a bootloader but I'm not allowed to post it until 10 posts)
If you look at my screenshot. It says Baseband Version m919uvufnh7. Isnt this the bootloader?
Sorry if I sound silly. I've never really had to update stuff like this before. It's really new to me.
Thanks,
Jeff

jeffreythe00 said:
Hey Kriptik210
For the bootloader I'm not exactly sure where to find it. (I have a link to what I think is a bootloader but I'm not allowed to post it until 10 posts)
If you look at my screenshot. It says Baseband Version m919uvufnh7. Isnt this the bootloader?
Sorry if I sound silly. I've never really had to update stuff like this before. It's really new to me.
Thanks,
Jeff
Click to expand...
Click to collapse
Baseband is the modem, build number is the bootloader. I don't see a screenshot anywhere

Ok, thank you for clarifying.
I'm going to download the 4.4.4 OTA and flash it VIA ODIN, then re-root. I've read towelroot v2 can root 4.4.4 without tripping knox.

jeffreythe00 said:
Ok, thank you for clarifying.
I'm going to download the 4.4.4 OTA and flash it VIA ODIN, then re-root. I've read towelroot v2 can root 4.4.4 without tripping knox.
Click to expand...
Click to collapse
You can't do OTA if you don't have the stock firmware already on your phone. But you can Odin.
You can use this link if you need anything...
http://www.droidviews.com/update-t-mobile-galaxy-s4-to-android-4-4-4-kitkat-and-root-it/

I got it. Sound is working now. I was apparently on the MDL bootloader. I used this thread http://forum.xda-developers.com/galaxy-s4-tmobile/help/nb4-to-nh7-firmware-upgrade-via-odin-t2880284 to get updated and re-rooted. Thanks for the help. I never would have known about the bootloader if it had not of been for this thread. I think I can handle the rest from here
Cheers!
Jeff

If you are unsure of your bootloader, there is a Phone Info Samsung app in the play store. IT will show you your boot loader version, modem baseband, etc..

Kriptik210 said:
Baseband is the modem, build number is the bootloader. I don't see a screenshot anywhere
Click to expand...
Click to collapse
Build number is the software version. It's defined in the build prop. Has nothing to do with the bootloader. Can make it say whatever you want. Unless That is Samsung is stealing mine and sickness' rom names and making bootloaders called HispAsian rom and Insane 4.4.4 haha in which I better be receiving a check
To find your bootloader version, download android terminal emulator from the playstore and type
getprop ro.bootloader
And hit enter.

ShinySide said:
Build number is the software version. It's defined in the build prop. Has nothing to do with the bootloader. Can make it say whatever you want. Unless That is Samsung is stealing mine and sickness' rom names and making bootloaders called HispAsian rom and Insane 4.4.4 haha in which I better be receiving a check
To find your bootloader version, download android terminal emulator from the playstore and type
getprop ro.bootloader
And hit enter.
Click to expand...
Click to collapse
Part of me knew this.....lol

Edit....................

Help! Push notifications work half the time with certain apps

Issue after 4.3 Auto Upgrade:
I have looked through many, many questions on this forum group relative to push notifications but most do not have an answer (or reply). I had learned that developers must update their apps to comply to 4.3 notification process that is part of 4.3 (POS). Is that my problem? I don't know.
I have tried 10 different reminder apps that notify me of events I have created that repeat, are persistent and stick to the notification drawer, but rarely, if even do. Sometimes they work, sometimes they don't. Other apps have similar behavior: one message comes through and 5 after will not. I am baffled.
I am rooted: Odin 3.09 root66 tar
Samsung Galaxy S III LTE
Any help is greatly appreciated. I do NOT have the funds to get a new phone and am stuck with the S3. Thank you in advance.

After doing tons of research on the push notifications, I have installed DynamicNotifications, removed any other lock screen app, customized DynamicNotifications and hopefully this will do the trick. So for anyone coming to this forum about 4.3 and push notifications issues .. take heed that you won't get a reply but try DynamicNotifications and uninstall any app you have that uses a lock screen. I was using CM Locker. DynamicNotifications has a built-in lock screen. You can read about the app in the Market/Play Store. I would also recommend watching a few YT vids on DynamicNotifications.

This app will help as well:
http://forum.xda-developers.com/showthread.php?t=2142503

Could the notification problem be related to your rooted ROM? I'm not sure.

Good Read:
https://productforums.google.com/forum/#!topic/nexus/fslYqYrULto

audit13 said:
Could the notification problem be related to your rooted ROM? I'm not sure.
Click to expand...
Click to collapse
I am not using a ROM. I am rooted with no ROM installed.

marinazar said:
I am not using a ROM. I am rooted with no ROM installed.
Click to expand...
Click to collapse
You might want to read the article I just posted.

I had a look at the article and noticed that it was published on September 9, 2013.
You must have a ROM installed on your phone; otherwise, the phone would not boot, no?

More help: http://www.digitalinternals.com/mobile/fix-wifi-push-notifications-delay-android/361/

I rooted with Odin 3.09 and root66 tar. That's it.
audit13 said:
I had a look at the article and noticed that it was published on September 9, 2013.
You must have a ROM installed on your phone; otherwise, the phone would not boot, no?
Click to expand...
Click to collapse

Of course its from 2013. I am on o/s 4.3. That is when all the push notifications began to disappear. This is the reason:
http://www.digitalinternals.com/mobile/fix-wifi-push-notifications-delay-android/361/
Trust me, if there were a way I could get off 4.3 I would but I am stuck with the S3.
audit13 said:
I had a look at the article and noticed that it was published on September 9, 2013.
You must have a ROM installed on your phone; otherwise, the phone would not boot, no?
Click to expand...
Click to collapse

I am using PNF (root), DynamicNotifications, have checked the TCP timeout, and everything inbetween. Will have to do a factory reset next, but I've read that didn't help at all.
"In a nutshell, Google’s push notifications service work by making a connection on TCP port 5228 between the phone and Google servers."

The latest T-mobile NF4 ROM came out in October, 2014. You could move to a custom Lollipop ROM to see if that solves the issue.
The fact that the Root66 ROM is rooted may have something to do with the push notifications.
Looks like the solution may require changing TCP time outs on a wifi router.

Unfortunately, my Netgear genie does not allow for TCP parameter changes.
I will try a ROM change next but I cannot even tell you how many hours I have invested in this device since it auto upgraded to 4.3 - ridiculous.
audit13 said:
The latest T-mobile NF4 ROM came out in October, 2014. You could move to a custom Lollipop ROM to see if that solves the issue.
The fact that the Root66 ROM is rooted may have something to do with the push notifications.
Looks like the solution may require changing TCP time outs on a wifi router.
Click to expand...
Click to collapse

have you tried a stock rom without root to see what happens?

I haven't. What steps would I need to take knowing I have root66? Speak in noob, audit
audit13 said:
have you tried a stock rom without root to see what happens?
Click to expand...
Click to collapse

Download the latest rom from sammobile.com and use Odin to flash it.
Did you use Odin to flash root66?
http://forum.xda-developers.com/showthread.php?t=1949687

I did.
In another thread you had sent me a link for firmware for my device. I've attached the screenshot.
So I really don't want to brick my phone Are you thinking I should find a new ROM, install with Odin, or revert back to stock? I am lost on what to do now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
audit13 said:
Did you use Odin to flash root66?
http://forum.xda-developers.com/showthread.php?t=1949687
Click to expand...
Click to collapse

I found these instructions for converting back to stock with Odin:
http://androidromupdate.com/2013/12...-official-4-3-stock-t-mo-galaxy-s3-lte-t999l/

The phone doesn't look like it is running the latest firmware.
How did the phone get an ota update if it was rooted?

Bricked ?

Got stuck with boot loop and this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would appreciate any help....

erik077 said:
Got stuck with boot loop and this
I would appreciate any help....
Click to expand...
Click to collapse
Could you explain what you were on, what you did to get you to where you are and what was used that prompted that message?

Updated from 4.4 to Lolipop and tried to root it...

erik077 said:
Updated from 4.4 to Lolipop and tried to root it...
Click to expand...
Click to collapse
Which version of lollipop did you try to ODIN ?

This http://forum.xda-developers.com/note-4-sprint/development/romstockishno-knox-8-7-15-sprint-t3174350

erik077 said:
This http://forum.xda-developers.com/note-4-sprint/development/romstockishno-knox-8-7-15-sprint-t3174350
Click to expand...
Click to collapse
You didnt have the correct Baseband for that.
FLash this first
http://forum.xda-developers.com/note-4-sprint/general/n910p-c0g5-tar-files-return-to-stock-t3174291
then
samep said:
Just the opposite with OG5: power down Odin stock tar (auto boot enabled), Odin TWRP (auto boot disabled- pull battery and USB when done), boot recovery to flash freeza kernel, recovery flash SuperSU zip.
Click to expand...
Click to collapse

Downloading...
Just to explain: I managed to update to Lolipop but this first happened when trying to root. After root failed I tried link I provided but that restore gave me same error

erik077 said:
Downloading...
Just to explain: I managed to update to Lolipop but this first happened when trying to root. After root failed I tried link I provided but that restore gave me same error
Click to expand...
Click to collapse
Indeed, just dont forget the kernel before rooting this time and you should be good.
https://www.androidfilehost.com/?fid=24052804347789588

xxSTARBUCKSxx said:
You didnt have the correct Baseband for that.
FLash this first
http://forum.xda-developers.com/note-4-sprint/general/n910p-c0g5-tar-files-return-to-stock-t3174291
then
Click to expand...
Click to collapse
You'll love this... Now the theory is to stay on OB7 or lower bootloader, and Odin flash the OG5 modem only and then flash OG5 custom ROM to stay away from reactivation locked bootloader.
I'm not sure at what point giving up the unlocked (for reactivation) bootloader is worth keeping once updates justify waving bye to KitKat or original OB7 ROMs in favor of attaining full functionality or compatibility with updates? Sitting back a little longer to decide if update fully with tar or just bump the modem to OG5 is best. Stay tuned for more ever evolving theories, workarounds and "what the bricks?" is this.
Who knows, there may be more value in having the older bootloader if considering a near term sell to upgrade.
BTW, looks like the kernel exploit is currently only available in freeza's new OG5 stock ROM.
Sent from my SM-N910P using Tapatalk

samep said:
You'll love this... Now the theory is to stay on OB7 or lower bootloader, and Odin flash the OG5 modem only and then flash OG5 custom ROM to stay away from reactivation locked bootloader.
I'm not sure at what point giving up the unlocked (for reactivation) bootloader is worth keeping once updates justify waving bye to KitKat or original OB7 ROMs in favor of attaining full functionality or compatibility with updates? Sitting back a little longer to decide if update fully with tar or just bump the modem to OG5 is best. Stay tuned for more ever evolving theories, workarounds and what the bricks?
Who knows, there may be more value in having the older bootloader if considering a near term sell to upgrade.
BTW, looks like the kernel exploit is currently only available in freeza's new OG5 stock ROM.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
*facepalm* Werll, at least hell be able to get back on his feet from the stock tar.. and go from there....
i was actually thinking about that myself very often in the past weeks.. the resell value that is.
This whole thing is odd, people with the same hardware having to perform the same basic operations, but in different steps for the same end- result is just insane....

xxSTARBUCKSxx said:
Indeed, just dont forget the kernel before rooting this time and you should be good.
https://www.androidfilehost.com/?fid=24052804347789588
Click to expand...
Click to collapse
Should I root with "CF-Auto-Root-trltespr-trltespr-smn910p" ?

erik077 said:
Should I root with "CF-Auto-Root-trltespr-trltespr-smn910p" ?
Click to expand...
Click to collapse
This works
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1
Sent from my SM-N910P using Tapatalk

Might as well make it a useful post...
Did you at least get back on solid ground @erik077 ??

And... freeza just refreshed the exploited kernel link
https://www.androidfilehost.com/?fid=24052804347789588
Sent from my SM-N910P using Tapatalk

Thank you all, this has been resolved. I am just not sure which ROM are safe for me to flash now. Suggestions?

Making backup right now and I will experiment with some.

erik077 said:
Making backup right now and I will experiment with some.
Click to expand...
Click to collapse
Good deal. Glad youre out of that funk you were just in. Thats the best you can do at the moment. Kinda skim the end of the threads first as well as the OP before experimenting. Or experiment away! Youll have your backup.
Im hesitant to make any suggestions being on NK2 myself.

Thank you so much for your help

Last question: Can I go from OG5 to OF5 or not? If yes how.... if not I hope some room are coming soon...

erik077 said:
Last question: Can I go from OG5 to OF5 or not? If yes how.... if not I hope some room are coming soon...
Click to expand...
Click to collapse
Early reports from OTA OG5 to OF5 was no. Freeza has one and is working on custom.
Some ROMs like Sacs, Noterized or CM12 have been claimed to flash but IMO that gets away from the fixes and security that makes OG5 Android 5.1.1 I'd stay with stock or freeza OG5 stock until custom OG5 ROMs show up.
Sent from my SM-N910P using Tapatalk