Develop Bugs

your help urgent please

i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks

And here we go again...... What version software was installed before trying to update? Were you rooted?

zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....

done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS

zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?

rooted thru odin
now i can't get to OS ,just show samsung sign and loops

Flash whatever firmware u was on in odin

zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.

tried to do thru sd card ,but i get :
dm-verity verification failed

can i just go back to 5.1 lollipop with an official stock rom via odin ?

zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom

any firmware can get me back to lollipop with odin !!!

zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk

samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.

xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk

i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip

[ROM] [ODIN] [HYBRID_OB7sbl_SPT_N910PVPU4COG5] [8/10/15]

I made this custom OG5 rom package for myself and I wanted to share it with those of you who want to stay on your older OB7 bootloader and be fully updated to Android 5.1 OG5. There is absolutely nothing changed from the stock rom/partitions except for the bootloader. This rom includes knox, itson, etc just like the official rom tar does. This simply gets you updated properly so you can proceed to root, flash recovery, flash rooted kernel, SuperSU, etc... and keep your unlocked OB7 bootloader. Please Note: If you have already taken either the OE1. OF5 or OG5 Android 5.1 ota update or odin flashed one of these official Samsung ROM rom tars, then you will not be able to go back to an older bootloader and this package will most likely not work for you. For the rest of us who where patient and who want to properly update to 5.1 and keep our unlocked OB7 bootloader then please keep reading.
The point of this odin package is very simple. Unless you flash the official 5.1 OG5 rom tar or take the 5.1 ota update from your phone then you will not be able to fully update to 5.1 the way it needs to be done. There are device partitions other than "system" and "cache" that must be written/overwritten with updated img.ext4's. Without extracting and comparing the img's there's no way to know what differences there are between the new 5.1 and the older softwares. So it goes without saying that it would be a wise choice to make sure your device has all of these carrier partitions etc updated for piece of mind. Again, I did this for my own personal use and not because I was bored. I want to share this with those of you who can benefit from it. So let's get started with the details/Instructions.
If you understand what the purpose of this odin package is then proceed: If not then do your homework or leave your phone alone. Here are the simple steps to fully update to 5.1 and retain the OB7 bootloader.
1. Install and use Odin 3.10.6
2. download and install 7zip
3. download and extract this OG5 odin rom package in a location of your choice. (VERIFY THE MD5 BEFORE YOU EXTRACT!!!)
4. Wipe your phone in your current TWRP or do a factory data reset in the stock bootloader. or proceed without wiping your partitions. (this can result in leftover data and cause issues so wipe if at all possible for a good clean slate).
5. Reboot your phone into download mode. (With phone turned of, press and hold the home, volume down and power button until the phone boots).
6. Open Odin 3.10.6 THEN connect your phone via USB and wait for it to connect.
Leave all defaults as they are and then press the big "AP" button to select the odin package you want to flash then press start. Wait for it to finish and it will let you know when all items flashed successfully. Unplug your usb and wait for first boot.
7. Setup your device as usual. Done.
You are now fully upgraded to Android 5.1 (OG5) with all partitions correctly written to your phone as per the OG5 update.
Download​HYBRID_OB7sbl_SPT_N910PVPU4COG5​

Thank you!
Out of curiosity are there plans for a deodexed version?
Sent from my SM-N910P using XDA Free mobile app

@tx_dbs_tx
Firstly I'm still on the OB7 Bootloader. I've upgraded to 5.1.1 using freezas OG5 Baseband flash & OG5 zip. Currently I am able to restore via TWRP Recovery to OG5 or Alliance (OB7) at will with no apparent problems. Now my question:
You've made reference to partitions that should be created to properly install OG5. Once this is done (you saying it needs doing is good enough for me btw) and I nand backup in TWRP can I then expect to have issues restoring an OB7 ROM from an OG5 ROM or vice-versa or will these changes be contained within the backups?
Again cannot thank you enough for all you've done for us.

thearch1tect said:
Thank you!
Out of curiosity are there plans for a deodexed version?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
That's out of the scope of this odin package. The sole purpose for this hybrid rom tar is to properly upgrade to 5.1 without being forced upon the new secure bootloaders. After you flash this tar you can proceed to root, flash roms, kernels, etc with confidence knowing that all of your partitions have been properly updated. Any other means of going to 5.1 without updating these partitions is not a complete upgrade to 5.1. So if you want a deodexed/custom 5.1 rom you'll have to wait for some of us to build them. But in the meantime you really should flash this and get this out of the way while you're waiting for new 5.1 roms, mods, kernels, etc.
kenjesse said:
@tx_dbs_tx
Firstly I'm still on the OB7 Bootloader. I've upgraded to 5.1.1 using freezas OG5 Baseband flash & OG5 zip. Currently I am able to restore via TWRP Recovery to OG5 or Alliance (OB7) at will with no apparent problems. Now my question:
You've made reference to partitions that should be created to properly install OG5. Once this is done (you saying it needs doing is good enough for me btw) and I nand backup in TWRP can I then expect to have issues restoring an OB7 ROM from an OG5 ROM or vice-versa or will these changes be contained within the backups?
Again cannot thank you enough for all you've done for us.
Click to expand...
Click to collapse
You will have no problem flashing back and forth between roms after flashing this odin package. It will retain your OB7 bootloader and update ALL of your partitions. You will then be completely stock unrooted OG5 with the exception of having the OB7 bootloader. From there you can restore a nandroid, flash a OB7/OG5 rom, etc.

That makes sense.
Im currently running hybrid x 1.07 with NK2 bootloader. Do I need to first upgrade the bootloaderto OB7 or does this package include the OB7 bootloader?
Sent from my SM-N910P using XDA Free mobile app

thearch1tect said:
That makes sense.
Im currently running hybrid x 1.07 with NK2 bootloader. Do I need to first upgrade the bootloaderto OB7 or does this package include the OB7 bootloader?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Yes. This package includes the OB7 bootloader. It will replace your NK2 bootloader but if I'm not mistaken you would still be able to odin an older NK2 tar and go back to that bootloader... not that it really makes any difference. I would say that the OB7 bootloader is what you want to go with since it's more current and still unlocked. However, If you're happy with your current setup then you can just wait for the custom OG5 roms to come out and decide then if you want to flash another rom.

tx_dbs_tx said:
Yes. This package includes the OB7 bootloader. It will replace your NK2 bootloader but if I'm not mistaken you would still be able to odin an older NK2 tar and go back to that bootloader... not that it really makes any difference. I would say that the OB7 bootloader is what you want to go with since it's more current and still unlocked. However, If you're happy with your current setup then you can just wait for the custom OG5 roms to come out and decide then if you want to flash another rom.
Click to expand...
Click to collapse
Failed for me....
Edit i dont kow why the pic is sideways

Failed for me as well

I'd like to flash this rom for the reasons you named but I am on the OF5 bootloader which is also unlocked since I used CF root to root it. Question : would you do a version of this rom including the OF5 bootloader or one that would use the bootloader already installed on the note?

To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.

flyhighx said:
To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.
Click to expand...
Click to collapse
Im on ob7 bootloader... but i did flash the og5 modem and freezas rom... just wanted to do this cause he said we missed somethings with update just flashing modem...

Since this TAR has led to confusion -- I wanted to state that I am on OB7 bootloader, and the TAR worked perfectly for me.

I'm also on OB7 bootloader and had flashed OF5 bits to use another rom. This worked perfect, now on freeza's stockish.

I flashed this last night when you first posted it in your Hybrid X thread, I was on OB7 running 2.3
I Odined all the way back to NK2 then flashed OB7 again, then this one, I flashed TWRP and Freeza's Kernel then installed Super SU from playstore and I'm not having any issues whatsoever, it runs very smooth (seems like they did a good job with this update)
I'm patiently waiting for you to make a new OG5 Hybrid X rom, I didn't want to flash Freeza's rom cause I've noticed there's a few bugs and issues.
And since it's stockish I see no point of doing so until there's new OG5 roms.
Thank You Sir!! :good::good:

Just to be clear for me. After updating to this ROM, can u root it? Or do we have to wait for something other than CF Root? All my apps are backed up and no way to restore just yet, thx
Disregard, installed TWRP, then flashed Freeza Mod Kernal and SU.

twynn said:
I'd like to flash this rom for the reasons you named but I am on the OF5 bootloader which is also unlocked since I used CF root to root it. Question : would you do a version of this rom including the OF5 bootloader or one that would use the bootloader already installed on the note?
Click to expand...
Click to collapse
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
xyojimbox said:
Failed for me....
Edit i dont kow why the pic is sideways
Click to expand...
Click to collapse
.
whiteyman24 said:
Failed for me as well
Click to expand...
Click to collapse
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
flyhighx said:
To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.
Click to expand...
Click to collapse
Exactly.
kbrn said:
I flashed this last night when you first posted it in your Hybrid X thread, I was on OB7 running 2.3
I Odined all the way back to NK2 then flashed OB7 again, then this one, I flashed TWRP and Freeza's Kernel then installed Super SU from playstore and I'm not having any issues whatsoever, it runs very smooth (seems like they did a good job with this update)
I'm patiently waiting for you to make a new OG5 Hybrid X rom, I didn't want to flash Freeza's rom cause I've noticed there's a few bugs and issues.
And since it's stockish I see no point of doing so until there's new OG5 roms.
Thank You Sir!! :good::good:
Click to expand...
Click to collapse
Thats exactly how you do it. Thanks for sharing your feedback.

tx_dbs_tx said:
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
.
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
Exactly.
Thats exactly how you do it. Thanks for sharing your feedback.
Click to expand...
Click to collapse
I am pretty sure I'm on ob7 bootloader cause I just flashed the of5 baseband I didn't take Ota and didn't mess with oe1 either....

tx_dbs_tx said:
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
.
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
Exactly.
Thats exactly how you do it. Thanks for sharing your feedback.
Click to expand...
Click to collapse
If you mean the bootloader is locked on OF5 I don't see how it could be since I rooted OF5 with CF Root. I think it's not possible to do that if the bootloader is locked

twynn said:
If you mean the bootloader is locked on OF5 I don't see how it could be since I rooted OF5 with CF Root. I think it's not possible to do that if the bootloader is locked
Click to expand...
Click to collapse
It doesn't matter if bootloader is locked I believe. You can still root but you can't downgrade with any tar if bootloader is locked.

I thought sprint never locked the bootloader?

Noob idiot here need help

Ok I dont know the fancy terms so please bear with me as I explain what I did.
I wanted to root my note 4 I downloaded odin v 3.07 and followed the "easy" online steps.
so it did its thing odin said pass then the phone started resetting this just looped and looped. so I tried and tried again and no success . I factory wiped the phone and still nothing, I fear I bricked this thing can someone help me I feel like a complete idiot. Thanks

From the top, what update version were you rooting? What did you Odin?
If you're on a recent update OE1 and up, the bootloaders have a reactivation lock that keeps you from successfully downgrading. Even the OG5 bootloader will prevent going back a single update from what I've read. You should be using Odin 3.10.7 or latest using the OEM unlock in option tab. The ROM itself may be locked to reactivation in Settings/Security. You should also enable developer mode and make sure USB debugging is enabled.
Also, OG5 stock kernel blocks typical root methods. You need the exploited kernel for that plus SuperSU zip. Technically, you'd only need custom recovery flashed in Odin then flash either the zips or pre-rooted ROM with the kernel and SuperSU included in flash.
There's even a guide posted for that:
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Sent from my SM-N910P using Tapatalk

samep said:
From the top, what update version were you rooting? What did you Odin?
If you're on a recent update OE1 and up, the bootloaders have a reactivation lock that keeps you from successfully downgrading. Even the OG5 bootloader will prevent going back a single update from what I've read. You should be using Odin 3.10.7 or latest using the OEM unlock in option tab. The ROM itself may be locked to reactivation in Settings/Security. You should also enable developer mode and make sure USB debugging is enabled.
Also, OG5 stock kernel blocks typical root methods. You need the rooted kernel for that plus SuperSU zip. Technically, you'd only need custom recovery flashed in Odin then flash either the zips or pre-rooted ROM with the kernel and SuperSU included in flash.
There's even a guide posted for that:
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I believe i had the latest update 5.1.1 I got the phone working again. I found the latest Md5 and used odin 10.7. I am so new to this its stupid its taken me 2 hours to fix my first mistake I basically lost everything but im ok with that. Thanks let me give this another try i was scared id be at sprint in the morning buying a new phone.

Rooted 5.0.1 to 5.1.1 Custom Rom

Hey everyone,
I've been curious about upgrading my rooted Note 4 from Lollipop 5.0.1 to a custom rom in 5.1.1, but I don't want to take a risk and brick my phone because I didn't know what I was doing. I'm not sure what steps to get to 5.1.1 and I know for a fact that if I attempt to install a 5.1.1 rom onto a 5.0.1, I am sure that I'll run into some issues.
Can anyone assist me in getting to 5.1.1? I'm not too sure of the terminology, all I know is that I'm on an OB7.

GreenFire999 said:
Hey everyone,
I've been curious about upgrading my rooted Note 4 from Lollipop 5.0.1 to a custom rom in 5.1.1, but I don't want to take a risk and brick my phone because I didn't know what I was doing. I'm not sure what steps to get to 5.1.1 and I know for a fact that if I attempt to install a 5.1.1 rom onto a 5.0.1, I am sure that I'll run into some issues.
Can anyone assist me in getting to 5.1.1? I'm not too sure of the terminology, all I know is that I'm on an OB7.
Click to expand...
Click to collapse
Id download the latest noterized (from Android Development) and put that zip on your sd card.
Go to recovery and make a backup.
While in recovery go to wipe, advanced and wipe everything x3 except for Micro SD
Then go to install and flash the noterized zip file.
An Unlocked bootloader is such a terrible thing to waste.
If you dont like it, all you have to do is repeat the wiping procedures in recovery and restore backup.
Or beforehand, if you run into some bumps, use the search feature while in that thread to see if any problems youre running into have already been asked and answered.
Glad you brought that up, i meant to mention that also @ the loss of xposed on 5.1.1

You have a phone that some would rather have than one they have if the bootloader is OB7. If that is the last full update you took, it should be OB7.
If Xposed framework and modules or staying on an unlocked bootloader that allows downgrade to KitKat isn't your thing, the full update to OG5 would be OK to flash to reactivation locked bootloader. (If true, skip next paragraph)
If keeping the OB7 bootloader, there are two recommended methods to update to OG5 while retaining OB7 bootloader. One is to flash the OG5 modem then flash a OG5 ROM. See freeza ROM OP in development for his modem, kernel and ROMs for OG5. The second method is to Odin the OB7 to OG5 tar ball by tx_dbs_tx in development. Follow the OPs for instructions.
There's a guide if you just want to upgrade and root OG5. If it's a custom OG5 ROM you're looking for, you can just do the Odin flash OF5 stock tar and custom recovery. In recovery, flash a pre-rooted OG5 ROM. I'd suggest a clean install with either method.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Edit: one last comment. If you do want Xposed, it's not yet available for TW 5.1.1
Sent from my SM-N910P using Tapatalk
---------- Post added at 12:22 AM ---------- Previous post was at 12:16 AM ----------
xxSTARBUCKSxx said:
Id download the latest noterized (from Android Development) and put that zip on your sd card.
Go to recovery and make a backup.
While in recovery go to wipe, advanced and wipe everything x3 except for Micro SD
Then go to install and flash the noterized zip file.
An Unlocked bootloader is such a terrible thing to waste.
If you dont like it, all you have to do is repeat the wiping procedures in recovery and restore backup.
Or beforehand, if you run into some bumps, use the search feature while in that thread to see if any problems youre running into have already been asked and answered.
Click to expand...
Click to collapse
Good advice. Posted while I was thinking somewhat on the same point of view regarding OB7.
Sent from my SM-N910P using Tapatalk

So I'm guessing once when I upgrade to OG5 I'm taking away the unlocked bootloader feature? What is OG5 technically doing to the Note 4?

GreenFire999 said:
So I'm guessing once when I upgrade to OG5 I'm taking away the unlocked bootloader feature? What is OG5 technically doing to the Note 4?
Click to expand...
Click to collapse
Reactivation lock is a theft preventative mandate. If you set it, a password is required to overwrite your locked device and account. A would be thief wouldn't be able to unlock it or flash it to become the new owner. He would brick it trying. Am I wrong? I still haven't adopted the new bootloader to see any of this first hand.
The lesser security bootloaders are blocked to Odin. Updating means you can't go back to OB7 or KitKat complete tars. Noterized can be flashed because it doesn't attempt to make your device fully compatible with OB7. But that's not making an OG5 reactivation bootloader compatible with OB7 ROMs to freely flash at will. Semi bricking occurs when users try to flash full tars or go back to KitKat. Some even make the mistake of thinking going to Noterized frees them to flash other ROMs and tars that they shouldn't. Despite some claims of success, no history of a proven method exists outside of wasted time and confusion and bricks some users couldn't figure out even with help given.
I haven't been on a reactivation bootloader but going by claims of others and reading, it appears to be something new each update. OE1 didn't get a tar so users that rooted were stuck until OF5 official tar was released. When OG5 came out, some posted OF5 backups were not flashing. OG5 also blocks root by the traditional CFAutoRoot used in prior updates for KitKat and Lollipop. It takes the exploit of kernel plus SuperSU zip to root OG5.
All this has brought the added wait until development catches up concept to update prior to taking something like an OTA if you value root. And some have reported rooting has even defeated the ability to take OTA updates as well. Add to the the latest claim that the stock OG5 kernel is required in order to Odin a fresh OG5 tar over rooted OG5 means you have to be up on current events to avoid boot loops on OG5.
No Xposed on TW 5.1.1 means I'm staying away a little longer.
Got all that? Some of it is just theory. The guide I referenced earlier also had some more advice for OG5. I believe it's as short but exhaustive as possible in a single post. It's important for newcomers to make informed decisions. Best wishes on making the right one for you. Personally, I'm on OB7 deodexed for Xposed Lollipop and Wi-Fi Calling. I chose to stay with lollipop because Wi-Fi Calling is not very good on KitKat. Otherwise, KitKat is very good but development is following the recent updates.
Sent from my SM-N910P using Tapatalk

samep said:
Reactivation lock is a theft preventative mandate. If you set it, a password is required to overwrite your locked device and account. A would be thief wouldn't be able to unlock it or flash it to become the new owner. He would brick it trying. Am I wrong? I still haven't adopted the new bootloader to see any of this first hand.
The lesser security bootloaders are blocked to Odin. Updating means you can't go back to OB7 or KitKat complete tars. Noterized can be flashed because it doesn't attempt to make your device fully compatible with OB7. But that's not making an OG5 reactivation bootloader compatible with OB7 ROMs to freely flash at will. Semi bricking occurs when users try to flash full tars or go back to KitKat. Some even make the mistake of thinking going to Noterized frees them to flash other ROMs and tars that they shouldn't. Despite some claims of success, no history of a proven method exists outside of wasted time and confusion and bricks some users couldn't figure out even with help given.
I haven't been on a reactivation bootloader but going by claims of others and reading, it appears to be something new each update. OE1 didn't get a tar so users that rooted were stuck until OF5 official tar was released. When OG5 came out, some posted OF5 backups were not flashing. OG5 also blocks root by the traditional CFAutoRoot used in prior updates for KitKat and Lollipop. It takes the exploit of kernel plus SuperSU zip to root OG5.
All this has brought the added wait until development catches up concept to update prior to taking something like an OTA if you value root. And some have reported rooting has even defeated the ability to take OTA updates as well. Add to the the latest claim that the stock OG5 kernel is required in order to Odin a fresh OG5 tar over rooted OG5 means you have to be up on current events to avoid boot loops on OG5.
No Xposed on TW 5.1.1 means I'm staying away a little longer.
Got all that? Some of it is just theory. The guide I referenced earlier also had some more advice for OG5. I believe it's as short but exhaustive as possible in a single post. It's important for newcomers to make informed decisions. Best wishes on making the right one for you. Personally, I'm on OB7 deodexed for Xposed Lollipop. I chose to stay with lollipop because it's not very good on KitKat. Otherwise, KitKat is very good but development is following the recent updates.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you for the great description. I think I will stick with OB7 a little longer until I find a better reason to change to OG5. Sounds like it would be more of a hassle trying to troubleshoot on OG5 if I do screw something up. I might just go down your route and pick up Xposed to see where that takes me.

GreenFire999 said:
Thank you for the great description. I think I will stick with OB7 a little longer until I find a better reason to change to OG5. Sounds like it would be more of a hassle trying to troubleshoot on OG5 if I do screw something up. I might just go down your route and pick up Xposed to see where that takes me.
Click to expand...
Click to collapse
For TW Lollipop, you'll need a deodexed ROM for Xposed framework.
Stable using official alpha 3 v4
xposed-v65-sdk21-arm-arter97-V5-krait.ziphttp://forum.xda-developers.com/show...20&postcount=1
arter97-V6 for Xposed-v71 is available but I haven't tried it. There are reports of boot loops on various devices; IDK if anyone else has had success with this phone yet? I'd suggest what's stable until you know otherwise.
Install Xposed Installer as sideload. (Install browsing to it with a root browser and tap file, selecting install.) Flash the arter zip in recovery. Initial boot after flash and the framework should be installed and ready for adding modules. Reboot to apply modules.
Sent from my SM-N910P using Tapatalk

Back to 5.1.1?

Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!

Ind3lible said:
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Click to expand...
Click to collapse
Yes you can odin back to 5.1.1. Just make sure you flash the correct tar.

Ind3lible said:
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Click to expand...
Click to collapse
Better not. You can go up in version , but not down.

yes
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.

chrisresponsibility said:
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
Click to expand...
Click to collapse
Viper works fine on MM. Either flash viper installation zip than the subpolicy zip from here, http://forum.xda-developers.com/showthread.php?t=3355270 .Or a permissive kernel like beastmode, from here http://forum.xda-developers.com/showthread.php?t=3284505 .

chrisresponsibility said:
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
Click to expand...
Click to collapse
Awesome, thank you so much!! So OK1 was the last lollipop right? I have the TAR but where is the twrp. I have not rooted the note 4 ever. So don't know much how to get TWRP on it yet.

Ind3lible said:
Awesome, thank you so much!! So OK1 was the last lollipop right? I have the TAR but where is the twrp. I have not rooted the note 4 ever. So don't know much how to get TWRP on it yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=66903690
Sent from my SM-N910P using Tapatalk

samep said:
http://forum.xda-developers.com/showthread.php?p=66903690
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks brotha!

i Have a bootloop when flash OK1 From PD1...... On What Version may Downgrade From PD1?

michael_0302 said:
i Have a bootloop when flash OK1 From PD1...... On What Version may Downgrade From PD1?
Click to expand...
Click to collapse
You flashed the full stock tar OK1 and got a bootloop? Just a guess but since Lollipop and Marshmallow differ on app optimization, I think you have to wipe data to get it to boot. Factory reset in stock recovery or wipe data in custom recovery.
If that's the case, you can take data to marshmallow (it seems to anticipate that but may still need factory reset adb ItsOn completely removed after root for some rooted users but also factory reset seemed to apply to PC1 OTA for un-rooted users). But maybe you can't take optimized apps back to Lollipop? Confirm that if it works.
Lollipop may be trying to rebuild the dalvik-cache but gets tripped up by the odex files in the oat folders of every app in data partition. Result could be bad boot. Loops.
Sent from my SM-N910P using Tapatalk

Thread moved to correct forums.

samep said:
You flashed the full stock tar OK1 and got a bootloop? Just a guess but since Lollipop and Marshmallow differ on app optimization, I think you have to wipe data to get it to boot. Factory reset in stock recovery or wipe data in custom recovery.
If that's the case, you can take data to marshmallow (it seems to anticipate that but may still need factory reset adb ItsOn completely removed after root for some rooted users but also factory reset seemed to apply to PC1 OTA for un-rooted users). But maybe you can't take optimized apps back to Lollipop? Confirm that if it works.
Lollipop may be trying to rebuild the dalvik-cache but gets tripped up by the odex files in the oat folders of every app in data partition. Result could be bad boot. Loops.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Did you get this working? I still have not flashed but am scared now lol =(

Ind3lible said:
Did you get this working? I still have not flashed but am scared now lol =(
Click to expand...
Click to collapse
Not sure of your question but in context, what I did was flash the OK1 bootloader, factory reset and restore Lollipop TWRP backup. I suggested to the user I quoted that his boot loop was caused by app optimization of MM. He could confirm that by factory resetting and attempt to boot. I didn't get a confirmation.
The advice I would give is to first backup and then make a clean break with Marshmallow data if intent is to temporarily go back to Lollipop. The bootloader method is ideal for users with Lollipop backup to restore but for those without the Lollipop backup, I think the full tar is best.
But remember to make sure reactivation lock in Settings/Security is disabled before flashing and remove fingerprints before backups or restore to avoid issues with those features. If you follow the forums, you can verify that it is possible to go back to Android 5.1 from Android 6.0 using Odin full tar.
I've been on MM since PD1 update. Currently on PE1 Odexed with Xposed framework.
Edit: didn't realize you were the OP. Sorry. I'd just recommend the factory reset but first disable reactivation lock and delete fingerprints and make a backup. If you have the Lollipop TWRP backup to restore, the OK1 bootloader is in the development forum for Sprint Note 4 in a thread by freeza: baseband and bootloader thread.
Sent from my SM-N910P using Tapatalk

samep said:
Not sure of your question but in context, what I did was flash the OK1 bootloader, factory reset and restore Lollipop TWRP backup. I suggested to the user I quoted that his boot loop was caused by app optimization of MM. He could confirm that by factory resetting and attempt to boot. I didn't get a confirmation.
The advice I would give is to first backup and then make a clean break with Marshmallow data if intent is to temporarily go back to Lollipop. The bootloader method is ideal for users with Lollipop backup to restore but for those without the Lollipop backup, I think the full tar is best.
But remember to make sure reactivation lock in Settings/Security is disabled before flashing and remove fingerprints before backups or restore to avoid issues with those features. If you follow the forums, you can verify that it is possible to go back to Android 5.1 from Android 6.0 using Odin full tar.
I've been on MM since PD1 update. Currently on PE1 Odexed with Xposed framework.
Edit: didn't realize you were the OP. Sorry. I'd just recommend the factory reset but first disable reactivation lock and delete fingerprints and make a backup. If you have the Lollipop TWRP backup to restore, the OK1 bootloader is in the development forum for Sprint Note 4 in a thread by freeza: baseband and bootloader thread.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I don't have any finger print and I am not sure what reactivation lock it. But I am fully stock PE1 at the moment. I would go back to lollipop for good. MM doesn't have anything that lollipop does for me at least.

Ind3lible said:
I don't have any finger print and I am not sure what reactivation lock it. But I am fully stock PE1 at the moment. I would go back to lollipop for good. MM doesn't have anything that lollipop does for me at least.
Click to expand...
Click to collapse
Reactivation Lock is in Settings/Security. Uncheck it before flashing.
No TWRP backup? Then I would suggest backing up what you want to keep, factory reset in TWRP and wipe internal memory and power down.
Odin OK1 stock tar in Odin and disable automatic updates in Settings/System update. Install TWRP, follow OP; make sure auto update remains disabled. If you don't disable auto updates stock enough, the update becomes persistent; you'll have to Google how to stop the persistent update notice if that happens.
One additional step I recommend after flashing custom ROM is to search your root folder for itson; delete what your search results. You may find a leftover folder at /carrier/ItsOn and a dalvik-cache belonging to an application in that folder in /data/dalvik-cache; that can cause a lot if persistent reboot demands after a factory reset despite the ROM not having ItsOn- this is a trace residue left in internal memory that gets added when you flash the stock tar in Odin. Enjoy Lollipop.
Personally, I think you'll want to come back to Marshmallow despite not seeing anything you want right now. You could make that TWRP backup and save TWRP folder to PC, just in case. To come back, all you would need to do is update the bootloader and baseband, factory reset and restore the backup.
Marshmallow is stricter but still manageable. Just takes some getting accustomed to. Once the tools and methods are achieved with proven compatibility, there may soon be custom ported ROMs for Note 4 on Marshmallow. At the moment it's thought to be a matter of when, not if. Time will tell if that thought is true.
Sent from my SM-N910P using Tapatalk